8 MCPTT configuration management documents

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

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

8.1 Introduction

This clause defines the structure, default document namespace, AUID, XML schema, MIME type, validation constraints and data semantics following documents;

MCPTT UE configuration document;

MCPTT user profile configuration document; and

MCPTT service configuration document.

8.2 MCPTT UE configuration document

8.2.1 General

The MCPTT UE configuration document is specified in this clause. The MCPTT UE configuration document content is based on requirements of Annex A.2 of 3GPP TS 23.379 [8], in accordance with OMA OMA-TS-XDM_Core-V2_1-20120403-A [2]. The usage of an MCPTT UE configuration document in the MCPTT service is described in 3GPP TS 24.379 [9] and 3GPP TS 24.380 [10]. The schema definition is provided in clause 8.2.2.3. An MCPTT UE configuration document may apply to all MCPTT UEs of a mission critical organization or apply to specific MCPTT UEs identified in the <mcptt-UE-id> element. If there is no <mcptt-UE-id> element in the MCPTT UE configuration document, then by default the MCPTT UE configuration document applies to all MCPTT UEs of the mission critical organization that are not specifically identified in the <mcptt-UE-id> element of another MCPTT UE configuration document of the mission critical organization. Each MCPTT UE of a mission critical organization is configured with an MCPTT UE configuration document that is identified by the instance ID of the MCPTT UE.

MCPTT UE configuration documents of a MCPTT user are contained as "XDM collections" in the user’s directory of the users tree, in accordance with OMA OMA-TS-XDM_Core-V2_1-20120403-A [2]. In this case, the term "user" in the XCAP sense refers to the MCPTT ID, as the user has been already authenticated. A MCPTT UE configuration document corresponding to a specific MCPTT UE the MCPTT user has used to authenticate and is authorised to use the MCPTT service with is placed in the user directory of the MCPTT user.

The MCPTT UE configuration document acts as a template for the CMS to generate UE configuration documents that are downloaded to specific MCPTT UEs. The MCPTT UE configuration document that acts as a template is referred to as a "master MCPTT UE configuration document". The master MCPTT UE configuration document is stored in the users tree of that MCPTT system administrator. The master MCPTT UE configuration document does not directly apply to a specific MCPTT UE, but instead acts as template that the CMS uses to populate the MCPTT UE configuration documents of MCPTT UEs identified by elements of the <MCPTT-UE-id> element. For MCPTT UE configuration documents that correspond to a specific MCPTT UE, the name of the MCPTT UE configuration document is created from a value defined by the corresponding element that identifies the MCPTT UE within the <MCPTT-UE-id> element. For a master MCPTT UE configuration documents that does not contain a <MCPTT-UE-id> element, the name of the MCPTT UE configuration document stored in the user directory is "DEFAULT-MCPTT-UE.xml".

8.2.1A MCPTT client access to MCPTT UE configuration documents

The MCPTT UE configuration document is accessed using the same XCAP URI, regardless of whether the MCPTT UE has a specific MCPTT UE configuration document configured or the master MCPTT UE configuration document applies. The CMS shall generate the UE’s MCPTT UE configuration document from the master MCPTT UE configuration document if the MCPTT administrator did not provision a specific MCPTT UE configuration document. In this generated document, the <MCPTT-UE-id> element shall be set to the MCPTT client’s UE ID. The UE’s MCPTT UE configuration document shall always be stored with the filename corresponding to the UE’s MCPTT UE ID under the user’s directory of the users tree.

The XCAP URI used by the MCPTT client to access the UE’s MCPTT UE configuration document shall be:

CMSXCAPROOTURI/org.3gpp.mcptt.ue-config/users/sip:MCPTTID/MCSUEID

8.2.2 Coding

8.2.2.1 Structure

The MCPTT UE configuration document structure is specified in this clause.

The <mcptt-UE-configuration> document:

1) shall include a "domain" attribute;

2) may include a <mcptt-UE-id> element;

3) may include a <name> element;

4) shall include a <common> element;

5) shall include an <on-network> element; and

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

The <common> element:

1) shall contain a <private-call> element containing:

a) a <Max-Simul-Call-N10> element; and

2) shall contain an <MCPTT-Group-Call> element containing:

a) a <Max-Simul-Call-N4> element;

b) a <Max-Simul-Trans-N5> element; and

c) a <Prioritized-MCPTT-Group> element containing:

i) a list of <MCPTT-Group-Priority> elements containing:

1) an <MCPTT-Group-ID> element; and

2) a <group-priority-hierarchy> element.

The <on-network> element:

1) shall contain a <IPv6Preferred> element;

2) shall contain a <Relay-Service> element; and

3) may contain a list of <Relayed-MCPTT-Group> elements containing:

a) a <MCPTT-Group-ID> element; and

b) a <Relay-Service-Code> element.

NOTE: When the <Relay-Service> element is set to "false" a list of <Relayed-MCPTT-Group> elements is not needed.

The <mcptt-UE-id> element:

1) may contain a list of <Instance-ID-URN> elements; and

2) may contain a list of <IMEI-range> elements.

The <IMEI-range> element:

1) shall contain a <TAC> element;

2) may contain a list of <SNR> elements; and

3) may contain <SNR-range> element.

The <SNR-range> element:

1) shall contain a <Low-SNR> element; and

2) shall contain a <High-SNR> element.

8.2.2.2 Application Unique ID

The AUID shall be set to "org.3gpp.mcptt.ue-config".

8.2.2.3 XML Schema

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

<xs:schema xmlns:mcpttuep="urn:3gpp:mcptt:mcpttUEConfig:1.0"

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

targetNamespace="urn:3gpp:mcptt:mcpttUEConfig:1.0"

elementFormDefault="qualified" attributeFormDefault="unqualified">

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

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

<xs:element name="mcptt-UE-configuration">

<xs:complexType>

<xs:sequence>

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

<xs:element name="mcptt-UE-id" type="mcpttuep:MCPTTUEIDType"/>

<xs:element name="name" type="mcpttuep:NameType"/>

</xs:choice>

<xs:element name="common" type="mcpttuep:CommonType"/>

<xs:element name="on-network" type="mcpttuep:On-networkType"/>

<xs:element name="anyExt" type="mcpttuep: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:attribute name="XUI-URI" type="xs:anyURI"/>

<xs:attribute name="Instance-ID-URN" type="xs:anyURI"/>

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

</xs:complexType>

</xs:element>

<xs:complexType name="NameType">

<xs:simpleContent>

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

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

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

</xs:extension>

</xs:simpleContent>

</xs:complexType>

<xs:complexType name="MCPTTUEIDType">

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

<xs:element name="Instance-ID-URN" type="xs:anyURI"/>

<xs:element name="IMEI-range" type="mcpttuep:IMEI-rangeType"/>

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

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

</xs:choice>

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

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

</xs:complexType>

<xs:complexType name="IMEI-rangeType">

<xs:sequence>

<xs:element name="TAC" type="mcpttuep:tacType"/>

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

<xs:element name="SNR" type="mcpttuep:snrType"/>

<xs:element name="SNR-range" type="mcpttuep:SNR-rangeType"/>

</xs:choice>

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

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

</xs:sequence>

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

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

</xs:complexType>

<xs:complexType name="SNR-rangeType">

<xs:sequence>

<xs:element name="Low-SNR" type="mcpttuep:snrType"/>

<xs:element name="High-SNR" type="mcpttuep:snrType"/>

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

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

</xs:sequence>

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

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

</xs:complexType>

<xs:simpleType name="tac-baseType">

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

<xs:totalDigits value="8"/>

</xs:restriction>

</xs:simpleType>

<xs:complexType name="tacType">

<xs:simpleContent>

<xs:extension base="mcpttuep:tac-baseType">

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

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

</xs:extension>

</xs:simpleContent>

</xs:complexType>

<xs:simpleType name="snr-baseType">

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

<xs:totalDigits value="6"/>

</xs:restriction>

</xs:simpleType>

<xs:complexType name="snrType">

<xs:simpleContent>

<xs:extension base="mcpttuep:snr-baseType">

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

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

</xs:extension>

</xs:simpleContent>

</xs:complexType>

<xs:complexType name="CommonType">

<xs:sequence>

<xs:element name="private-call">

<xs:complexType>

<xs:sequence>

<xs:element name="Max-Simul-Call-N10" type="xs:positiveInteger"/>

</xs:sequence>

</xs:complexType>

</xs:element>

<xs:element name="MCPTT-Group-Call">

<xs:complexType>

<xs:sequence>

<xs:element name="Max-Simul-Call-N4" type="xs:positiveInteger"/>

<xs:element name="Max-Simul-Trans-N5" type="xs:positiveInteger"/>

<xs:element name="Prioritized-MCPTT-Group">

<xs:complexType>

<xs:sequence>

<xs:element name="MCPTT-Group-Priority" maxOccurs="unbounded">

<xs:complexType>

<xs:sequence>

<xs:element name="MCPTT-Group-ID" type="xs:anyURI"/>

<xs:element name="group-priority-hierarchy" type="xs:nonNegativeInteger"/>

</xs:sequence>

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

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

</xs:complexType>

</xs:element>

</xs:sequence>

</xs:complexType>

</xs:element>

</xs:sequence>

</xs:complexType>

</xs:element>

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

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

</xs:sequence>

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

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

</xs:complexType>

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

<xs:sequence>

<xs:element name="IPv6Preferred" type="xs:boolean"/>

<xs:element name="Relay-Service" type="xs:boolean"/>

<xs:element name="Relayed-MCPTT-Group" type="mcpttuep:Relayed-MCPTT-GroupType" minOccurs="0" maxOccurs="unbounded"/>

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

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

</xs:sequence>

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

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

</xs:complexType>

<xs:complexType name="Relayed-MCPTT-GroupType">

<xs:sequence>

<xs:element name="MCPTT-Group-ID" type="xs:anyURI"/>

<xs:element name="Relay-Service-Code" type="xs:string"/>

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

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

</xs:sequence>

<xs:attributeGroup ref="mcpttuep: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="anyExtType">

<xs:sequence>

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

</xs:sequence>

</xs:complexType>

</xs:schema>

8.2.2.4 Default Document Namespace

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

8.2.2.5 MIME type

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

8.2.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 8.2.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 MCPTT UE configuration document shall conform to the XML Schema described in clause 8.2.2.3.

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

The <mcptt-UE-configuration> element shall contain one <common> element and one <on-network> element.

If the <mcptt-UE-configuration> element does not conform to one of the three 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".

If an <Instance-ID-URN> element of the <mcptt-UE-id> element does not conform to a valid Instance ID as specified in 3GPP TS 23.003 [16], 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 Instance ID URN" and contain the non-conformant <Instance-ID-URN> element.

If the <TAC> element of an <IMEI-range> element does not conform to a valid 8 digit Type Allocation Code as specified in 3GPP TS 23.003 [16], 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 Type Allocation Code" and contain the non-conformant <TAC> element.

If a <SNR> element of an <IMEI-range> element does not conform to a valid 6 digit Serial Number as specified in 3GPP TS 23.003 [16], 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 Serial Number" and contain the non-conformant <SNR> element.

If a <Low-SNR> element or a <High-SNR> element of a <SNR-range> element does not conform to a valid 6 digit Serial Number as specified in 3GPP TS 23.003 [16], 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 Serial Number range" and contain the non-conformant <Low-SNR> or <High-SNR> element.

If the <Max-Simul-Call-N10> element of the <private-call> element contains a value less than 1 and greater than 4, 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".

If the <Max-Simul-Call-N4> element, or <Max-Simul-Trans-N5> element of the <MCPTT-Group-Call> element contains a value less than 1, 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".

If the <MCPTT-Group-ID> element of the <MCPTT-group-priority> element or <Relayed-MCPTT-Group> element does not conform to the syntax of a "uri" attribute specified in OMA OMA-TS-XDM_Group-V1_1[17], 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 <group-priority-hierarchy> element of the <MCPTT-group-priority> element contains a value less than 8 and greater than or equal to 0, 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".

If the <Relay-Service> element of the <On-Network> element does not contain a value of "true" or "false", 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".

If the <Relay-Service-Code> element of the <Relayed-MCPTT-Group> element does not conform to the syntax of a valid Relay service code as defined in 3GPP TS 24.333 [12], 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 <IPv6-Preferred> element of the <On-Network> element does not contain a value of "true" or "false, 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".

8.2.2.7 Data Semantics

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

The <name> element of the <mcptt-UE- configuration> element contains the user displayable name of the MCPTT UE configuration document and corresponds to the "Name" element of clause 4.2.3 in 3GPP TS 24.483 [4].

The creator of the MCPTT UE configuration document may include an <mcptt-UE-id> element in the version of the MCPTT UE configuration document that is uploaded to the CMS and may also appear in the MCPTT UE configuration document when downloaded by the MCPTT system administrator. The <mcptt-UE-id> element does not appear in the MCPTT UE configuration document that is configured to the MCPTT UE. If an <mcptt-UE-id> element is included then the MCPTT UE configuration document applies only to the MCPTT UE(s) identified by the <mcptt-UE-id> element. If no <mcptt-UE-id> element is included then the MCPTT UE configuration document t applies to all the MCPTT UEs of the domain.

If one or more optional <Instance-ID-URN> elements is included in the <mcptt-UE-id> element then the MCPTT UE configuration document applies to the MCPTT UE with an instance ID equal to the instance ID contained in the <Instance-ID-URN> element.

The <TAC> element of the <IMEI-range> element contains the Type Allocation Code of the MCPTT UE.

The optional <SNR> element of the <IMEI-range> element contains the individual serial number uniquely identifying MCPTT UE within the Type Allocation Code contained in the <TAC> element that the MCPTT UE configuration document applies to.

If an optional <SNR-range> element is included within the <IMEI-range> element then the MCPTT UE configuration document applies to all MCPTT UEs within the Type Allocation Code contained in the <TAC> element with the serial number equal or greater than the serial number contained in the <Low-SNR> element and less than or equal to the serial number contained in the <High-SNR> element.

If no <SNR> element nor <SNR-range> element is included within the <IMEI-range> element then the MCPTT UE configuration document applies to all the MCPTT UE(s) with the Type Allocation Code contained within the <TAC> element of the <IMEI-range> element.

If no <mcptt-UE-id> element is included then the MCPTT UE configuration document applies to all MCPTT UEs of the mission critical organization identified in the "domain" attribute.

The <common> element contains MCPTT UE configuration data common to both on and off network operation.

The <on-network> element contains MCPTT UE configuration data for on-network operation only.

In the <common> element:

1) the <Max-Simul-Call-N10> element of the <private-call> element contains an integer indicating the maximum number of simultaneous calls (N10) allowed for an on-network or off-network private call with floor control and corresponds to the "MaxCallN10" element of clause 4.2.7 in 3GPP TS 24.483 [4];

2) the <Max-Simul-Call-N4> element of the <MCPTT-Group-Call> element contains an integer indicating the number of simultaneous calls (N4) allowed for an on-network or off-network group call and corresponds to the "MaxCallN4" element of clause 4.2.9 in 3GPP TS 24.483 [4];

3) the <Max-Simul-Trans-N5> element of the <MCPTT-Group-Call> element contains an integer indicating the maximum number of allowed simultaneous transmissions for an on-network or off-network group call and corresponds to the "MaxTransmissionN5" element of clause 4.2.10 in 3GPP TS 24.483 [4]; and

4) the <Prioritized-MCPTT-Group> element of the <MCPTT-Group-Call> element corresponds to the "PrioritizedMCPTTGroup" element of clause 4.2.11 in 3GPP TS 24.483 [4] contains a list of <MCPTT-Group-Priority> elements that contains:

a) <MCPTT-Group-ID> element identifying an MCPTT group that corresponds to the "MCPTTGroupID" element of clause 4.2.13 in 3GPP TS 24.483 [4]; and

b) a <group-priority-hierarchy> element that contains an integer that identifies the relative priority level of that MCPTT group with 0 being the lowest priority and 7 being the highest priority and corresponds to the "MCPTTGroupPriorityHierarchy" element of clause 4.2.14 in 3GPP TS 24.483 [4].

In the <on-network> element:

1) if the <Relay-Service> element is set to "true" the MCPTT UE is allowed to offer a relay service, and if set to "false" the MCPTT UE is not allowed to offer relay service. This attribute corresponds to the "RelayService" element of clause 4.2.16 in 3GPP TS 24.483 [4];

2) an <IPv6Preferred> element which corresponds to the "IPv6Preferred" element of clause 4.2.17 in 3GPP TS 24.483 [4],

a) if the UE has both IPv4 and IPv6 host configuration::

i) if IPv6Preferred is set to true then the UE shall use IPv6 for all on‑network signalling and media; otherwise

ii) if IPv6Preferred is set to false then the UE shall use IPv4 for all on‑network signalling and media;

b) if the UE has only IPv4 host configuration then the UE shall use IPv4 for all on‑network signalling and media; and

c) if the UE has only IPv6 host configuration then the UE shall use IPv6 for all on‑network signalling and media; and

3) the <Relayed-MCPTT-Groups> element of the <Relay-Service> element which corresponds to the "RelayedMCPTTGroup" element of clause 4.2.18 in 3GPP TS 24.483 [4] contains:

a) a list of <Relay-MCPTT-Group-ID> elements that contains:

i) "MCPTT-Group-ID" attribute identifying an MCPTT group that is allowed to be used via a relay and corresponds to the "MCPTTGroupID" element of clause 4.2.20 in 3GPP TS 24.483 [4]; and

ii) a <Relay-Service-Code> element as specified in 3GPP TS 24.333 [12] which corresponds to the "RelayServiceCode" element of clause 4.2.21 in 3GPP TS 24.483 [4].

8.2.2.8 Naming Conventions

The present document defines no naming conventions.

8.2.2.9 Global documents

The present document requires no global documents.

8.2.2.10 Resource interdependencies

There are no resource interdependencies.

8.2.2.11 Authorization Policies

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

8.2.2.12 Subscription to Changes

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

MCPTT UE configuration documents are kept as XDM collections. Therefore, it is possible to subscribe to all MCPTT UE configuration documents of a MCPTT user according to XCAP URI construction convention of a trailing ‘/’, as specified in IETF RFC 5875 [11].

8.3 MCPTT user profile configuration document

8.3.1 General

The MCPTT user profile configuration document is specified in this clause. The MCPTT user profile configuration document content is based on requirements of Annex A.3 of 3GPP TS 23.379 [8], and structure and procedures of OMA OMA-TS-XDM_Core-V2_1-20120403-A [2]. The usage of an MCPTT user profile in the MCPTT service is described in 3GPP TS 24.379 [9]. The schema definition is provided in clause 8.3.2.

MCPTT user profile documents are "XDM collections" in the user’s directory of the users tree, in accordance with OMA OMA-TS-XDM_Core-V2_1-20120403-A [2]. In this case, the term "user" in the XCAP sense refers to the MCPTT ID, as the user has been already authenticated.

The name of the MCPTT user profile document matches the value of the <ProfileName> element in the MCPTT user profile document.

8.3.1A MCPTT client access to MCPTT user profile documents

The XCAP URI used by the MCPTT client to access the MCPTT user’s MCPTT user profile documents shall be:

CMSXCAPROOTURI/org.3gpp.mcptt.user-profile/users/sip:MCPTTID/mcptt-user-profile-INDEX.xml

Where INDEX is the index of the MCPTT user profile as defined in clause 8.3.2.8.

8.3.2 Coding

8.3.2.1 Structure

The MCPTT user profile configuration document structure is specified in this clause.

The <mcptt-user-profile> document:

1) shall include an "XUI-URI" attribute;

2) may include a <Name> element;

3) shall include one <Status> element;

4) shall include a "user-profile-index" attribute;

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

6) may include one <ProfileName> element;

7) may include a <Pre-selected-indication> element;

8) shall include one <Common> element, which:

a) shall have an "index" attribute;

b) shall include one <UserAlias> element containing one or more <alias-entry> elements;

c) shall include one <MCPTTUserID> element that contains a <uri-entry> element;

d) shall include one <PrivateCall> element. The <PrivateCall> element contains:

i) a <PrivateCallList> element that contains one or more of the following:

A) a <PrivateCallURI> element that contains one <uri-entry> element, which contains:

I) an <anyExt> element that may contain a <PrivateCallKMSURI> element that contains one <PrivateCallKMSURI> element that contains one <uri-entry> element;

B) a <PrivateCallProSeUser> element that contains one <User‑Info‑ID> element; and

C) an <anyExt> element which may contain:

I) a <PrivateCallKMSURI> element that contains one <PrivateCallKMSURI> element that contains one <uri-entry> element; and

ii) one <EmergencyCall> element containing one <MCPTTPrivateRecipient> element that contains:

A) an <entry> element; and

B) a <ProSeUserID-entry> element;

e) shall contain one <MCPTT-group-call> element containing:

i) one <MaxSimultaneousCallsN6> element;

ii) one <EmergencyCall> element containing one <MCPTTGroupInitiation>element that contains an <entry> element;

iii) one <ImminentPerilCall> element containing one <MCPTTGroupInitiation> element that contains an <entry> element;

iv) one <EmergencyAlert> element containing an <entry> element; and

v) one <Priority> element;

f) may contain one <ParticipantType> element; and

g) shall contain one <MissionCriticalOrganization> element indicating the name of the mission critical organization the MCPTT User belongs to;

9) shall include zero or one <OffNetwork> element which:

a) shall contain an "index" attribute; and

b) shall include one <MCPTTGroupInfo> element, containing one or more <entry> elements;

10) shall include zero or one <OnNetwork> element which:

a) shall have an "index" attribute;

b) shall include one <MCPTTGroupInfo> element, containing one or more <entry> elements;

c) shall include one <MaxAffiliationsN2>element;

d) may include one <ImplicitAffiliations> element, containing one or more <entry> elements;

e) shall include one <MaxSimultaneousTransmissionsN7> element;

f) shall include one <PrivateEmergencyAlert> element containing an <entry> element; and

g) an <anyExt> element which may contain:

i) one <RemoteGroupSelectionURIList> element which contains one or more <entry> elements;

ii) one <FunctionalAliasList> element which contains one or more <entry> elements;

iii) one <IncomingPrivateCallList> element that contains one or more of the following:

A) a <PrivateCallURI> element that contains one <uri-entry> element, which contains:

I) an <anyExt> element that may contain a <PrivateCallKMSURI> element, which contains one <PrivateCallKMSURI> element that contains one <uri-entry> element; and

B) an <anyExt> element which may contain a <PrivateCallKMSURI> element that contains one <PrivateCallKMSURI> element, which contains one <uri-entry> element;

iv) an <AllowedMCPTTIdsForCallTransfer> element which contains one or more <entry> elements;

v) an <AllowedFunctionalAliasesForCallTransfer> element which contains one or more <entry> elements;

vi) a <call-forwarding-no-answer-timeout> element;

vii) a <call-forwarding-condition> element;

viii) a <call-forwarding-target> element; and

ix) a <user-max-simultaneous-authorizations> element.

11) a <ruleset> element conforming to IETF RFC 4745 [13] containing a sequence of zero or more <rule> elements:

a) the <conditions> of a <rule> element may include the <identity> element as described in IETF RFC 4745 [13];

b) the <actions> child element of any <rule> element may contain:

i) an <allow-presence-status> element;

ii) an <allow-request-presence> element;

iii) an <allow-query-availability-for-private-calls> element;

iv) an <allow-enable-disable-user> element;

v) an <allow-enable-disable-UE> element;

vi) an <allow-create-delete-user-alias> element;

vii) an <allow-private-call> element;

viii) an <allow-manual-commencement> element;

ix) an <allow-automatic-commencement> element;

x) an <allow-force-auto-answer> element;

xi) an <allow-failure-restriction> element;

xii) an <allow-emergency-group-call> element;

xiii) an <allow-emergency-private-call> element;

xiv) an <allow-cancel-group-emergency> element;

xv) an <allow-cancel-private-emergency-call> element;

xvi) an <allow-imminent-peril-call> element;

xvii) an <allow-cancel-imminent-peril> element;

xviii) an <allow-activate-emergency-alert> element;

xix) an <allow-cancel-emergency-alert> element;

xx) an <allow-offnetwork> element;

xxi) an <allow-imminent-peril-change> element;

xxii) an <allow-private-call-media-protection> element;

xxiii) an <allow-private-call-floor-control-protection> element;

xxiv) an <allow-request-affiliated-groups> element;

xxv) an <allow-request-to-affiliate-other-users> element;

xxvi) an <allow-recommend-to-affiliate-other-users> element;

xxvii) an <allow-private-call-to-any-user> element;

xxviii) an <allow-regroup> element;

xxix) an <allow-private-call-participation> element;

xxx) an <allow-override-of-transmission> element;

xxxi) an <allow-manual-off-network-switch> element;

xxxii) an <allow-listen-both-overriding-and-overridden> element;

xxxiii) an <allow-transmit-during-override> element;

xxxiv) an <allow-off-network-group-call-change-to-emergency> element;

xxxv) an<allow-revoke-transmit> element;

xxxvi) an <allow-create-group-broadcast- group> element;

xxxvii) an <allow-create-user-broadcast-group> element; and

xxxviii) an <anyExt> element which may contain:

A) an <allow-request-private-call-call-back> element;

B) an <allow-cancel-private-call-call-back> element;

C) an <allow-request-remote-initiated-ambient-listening> element;

D) an <allow-request-locally-initiated-ambient -listening> element;

E) an <allow-request-first-to-answer-call> element;

F) an <allow-request-remote-init-private-call> element;

G) an <allow-request-remote-init-group-call> element;

H) an <allow-query-functional-alias-other-user> element;

I) an <allow-takeover-functional-alias-other-user> element;

J) an <allow-location-info-when-talking> element;

K) an <allow-to-receive-private-call-from-any-user> element;

L) an <allow-to-receive-non-acknowledged-users-information> element;

M) an <allow-call-transfer> element;

N) an <allow-call-transfer-to-any-user> element;

O) an <allow-call-forwarding> element;

P) a <call-forwarding-on> element;

Q) a <forward-to-functional-alias> element;

R) an <allow-call-forward-manual-input> element; and

S) an <allow-functional-alias-binding-with-group> element.

12) may include any other element for the purposes of extensibility.

The <entry> elements:

1) shall contain a <uri-entry> element;

2) shall contain an"index" attribute;

3) may contain a <display-name> element;

4) may contain an "entry-info" attribute; and

5) may include an <anyExt> element which may contain:

a) a <LocationCriteriaForActivation> element containing:

i) one or more <EnterSpecificArea> elements, each containing a <PolygonArea> element or an <EllipsoidArcArea> element, and may include an <anyExt> element with a <Speed> element and a <Heading> element; and

ii) one or more <ExitSpecificArea> elements, each containing a <PolygonArea> element or an <EllipsoidArcArea> element, and may include an <anyExt> element with a <Speed> element and a <Heading> element.

b) a <LocationCriteriaForDeactivation> element containing:

c) a <manual-deactivation-not-allowed-if-location-criteria-met> element;

d) one <MaxSimultaneousEmergencyGroupCalls> element;

e) a <RulesForAffiliation> element containing:

i) one <ListOfLocationCriteria> element containing;

A) one or more <EnterSpecificArea> elements each containing a <PolygonArea> element or an <EllipsoidArcArea> element, and may include an <anyExt> element with a <Speed> element and a <Heading> element; and

B) one or more <ExitSpecificArea> elements each containing a <PolygonArea> element or an <EllipsoidArcArea> element, and may include an <anyExt> element with a <Speed> element and a <Heading> element; and

ii) zero or one <ListOfActiveFunctionalAliasCriteria> element which contains one or more <entry> elements;

f) a <RulesForDeaffiliation> element containing;

i) zero or one <ListOfLocationCriteria> element containing;

ii) zero or one <ListOfActiveFunctionalAliasCriteria> element which contains one or more <entry> elements;

g) a <manual-deaffiliation-not-allowed-if-affiliation-rules-are-met> element.

h) a <ListOfAllowedFAsToCall> element which contains one or more <entry> elements; and

i) a <ListOfAllowedFAsToBeCalledFrom> element which contains one or more <entry> elements;

j) a <GroupServerInfo> element containing:

i) one <GMS-Serv-Id> element;

ii) one <IDMS-token-endpoint> element; and

iii) one <GroupKMSURI> element; and

k) a <RelativePresentationPriority> element.

The <PolygonArea> elements shall contain 3 up to 15 <PointCoordinateType> elements.

The <EllipsoidArcArea> elements shall contain:

1) a <Center> element that contains a <PointCoordinateType> element;

2) a <Radius> element;

3) an <OffsetAngle> element; and

4) an <IncludedAngle> element.

The <PointCoordinateType> elements shall contain a <Longitude> element and a <Latitude> element.

The <Longitude> elements shall contain a <CoordinateType> element.

The <Latitude> elements shall contain a <CoordinateType> element.

The <Speed> elements shall contain a <MinimumSpeed> element and <MaximumSpeed> element.

The <Heading> elements shall contain a <MinimumHeading> element and <MaximumHeading> element.

The <ProSeUserID-entry> elements:

1) shall contain a <DiscoveryGroupID> element;

2) shall contain an <User-Info-ID> element; and

3) shall contain an "index" attribute.

8.3.2.2 Application Unique ID

The AUID shall be "org.3gpp.mcptt.user-profile".

8.3.2.3 XML Schema

The MCPTT user profile configuration document shall be composed according to the following XML schema:

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

<xs:schema

xmlns:mcpttup="urn:3gpp:mcptt:user-profile:1.0"

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

targetNamespace="urn:3gpp:mcptt:user-profile:1.0"

elementFormDefault="qualified" attributeFormDefault="unqualified">

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

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

<!– This import brings in common policy namespace from RFC 4745 –>

<xs:import namespace="urn:ietf:params:xml:ns:common-policy"

schemaLocation="http://www.iana.org/assignments/xml-registry/schema/common-policy.xsd"/>

<xs:element name="mcptt-user-profile">

<xs:complexType>

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

<xs:element name="Name" type="mcpttup:NameType"/>

<xs:element name="Status" type="xs:boolean"/>

<xs:element name="ProfileName" type="mcpttup:NameType"/>

<xs:element name="Pre-selected-indication" type="mcpttup:emptyType"/>

<xs:element name="Common" type="mcpttup:CommonType"/>

<xs:element name="OffNetwork" type="mcpttup:OffNetworkType"/>

<xs:element name="OnNetwork" type="mcpttup:OnNetworkType"/>

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

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

</xs:choice>

<xs:attribute name="XUI-URI" type="xs:anyURI" use="required"/>

<xs:attribute name="user-profile-index" type="xs:unsignedByte" use="required"/>

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

</xs:complexType>

</xs:element>

<xs:complexType name="NameType">

<xs:simpleContent>

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

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

</xs:extension>

</xs:simpleContent>

</xs:complexType>

<xs:complexType name="CommonType">

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

<xs:element name="UserAlias" type="mcpttup:UserAliasType"/>

<xs:element name="MCPTTUserID" type="mcpttup:EntryType"/>

<xs:element name="PrivateCall" type="mcpttup:MCPTTPrivateCallType"/>

<xs:element name="MCPTT-group-call" type="mcpttup:MCPTTGroupCallType"/>

<xs:element name="MissionCriticalOrganization" type="xs:string"/>

<xs:element name="ParticipantType" type="xs:string"/>

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

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

</xs:choice>

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

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

</xs:complexType>

<xs:complexType name="MCPTTPrivateCallType">

<xs:sequence>

<xs:element name="PrivateCallList" type="mcpttup:PrivateCallListEntryType"/>

<xs:element name="EmergencyCall" type="mcpttup:EmergencyCallType" minOccurs="0"/>

<xs:element name="anyExt" type="mcpttup: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="PrivateCallListEntryType">

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

<xs:element name="PrivateCallURI" type="mcpttup:EntryType"/>

<xs:element name="PrivateCallProSeUser" type="mcpttup:ProSeUserEntryType"/>

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

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

</xs:choice>

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

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

</xs:complexType>

<xs:complexType name="UserAliasType">

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

<xs:element name="alias-entry" type="mcpttup:AliasEntryType"/>

<xs:element name="anyExt" type="mcpttup: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="AliasEntryType">

<xs:simpleContent>

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

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

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

</xs:extension>

</xs:simpleContent>

</xs:complexType>

<xs:complexType name="ListEntryType">

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

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

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

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

</xs:choice>

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

<xs:attributeGroup ref="mcpttup: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="mcpttup:DisplayNameElementType" minOccurs="0"/>

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

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

</xs:sequence>

<xs:attribute name="entry-info" type="mcpttup:EntryInfoTypeList"/>

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

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

</xs:complexType>

<xs:complexType name="GeographicalAreaChangeType">

<xs:sequence>

<xs:element name="EnterSpecificArea" type="mcpttup:GeographicalAreaType" minOccurs="0" maxOccurs="unbounded"/>

<xs:element name="ExitSpecificArea" type="mcpttup:GeographicalAreaType" minOccurs="0" maxOccurs="unbounded"/>

<xs:element name="anyExt" type="mcpttup: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="GeographicalAreaType">

<xs:choice>

<xs:element name="PolygonArea" type="mcpttup:PolygonAreaType" minOccurs="0"/>

<xs:element name="EllipsoidArcArea" type="mcpttup:EllipsoidArcType" minOccurs="0"/>

<xs:element name="anyExt" type="mcpttup: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="PolygonAreaType">

<xs:sequence>

<xs:element name="Corner" type="mcpttup:PointCoordinateType" minOccurs="3" maxOccurs="15"/>

<xs:element name="anyExt" type="mcpttup: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="EllipsoidArcType">

<xs:sequence>

<xs:element name="Center" type="mcpttup:PointCoordinateType"/>

<xs:element name="Radius" type="xs:nonNegativeInteger"/>

<xs:element name="OffsetAngle" type="xs:unsignedByte"/>

<xs:element name="IncludedAngle" type="xs:unsignedByte"/>

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

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

</xs:sequence>

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

</xs:complexType>

<xs:complexType name="PointCoordinateType">

<xs:sequence>

<xs:element name="Longitude" type="mcpttup:CoordinateType"/>

<xs:element name="Latitude" type="mcpttup:CoordinateType"/>

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

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

</xs:sequence>

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

</xs:complexType>

<xs:simpleType name="CoordinateType">

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

<xs:minInclusive value="0"/>

<xs:maxInclusive value="16777215"/>

</xs:restriction>

</xs:simpleType>

<xs:complexType name="RulesForAffiliationManagementType">

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

<xs:element name="ListOfLocationCriteria" type="mcpttup:GeographicalAreaChangeType"/>

<xs:element name="ListOfActiveFunctionalAliasCriteria" type="mcpttup:ListEntryType"/>

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

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

</xs:choice>

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

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

</xs:complexType>

<xs:complexType name="SpeedType">

<xs:sequence>

<xs:element name="MinimumSpeed" type="xs:unsignedShort"/>

<xs:element name="MaximumSpeed" type="xs:unsignedShort"/>

<xs:element name="anyExt" type="mcpttup: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="HeadingType">

<xs:sequence>

<xs:element name="MinimumHeading" type="xs:unsignedShort"/>

<xs:element name="MaximumHeading" type="xs:unsignedShort"/>

<xs:element name="anyExt" type="mcpttup: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="ProSeUserEntryType">

<xs:sequence>

<xs:element name="DiscoveryGroupID" type="xs:hexBinary" minOccurs="0"/>

<xs:element name="User-Info-ID" type="xs:hexBinary"/>

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

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

</xs:sequence>

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

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

</xs:complexType>

<xs:simpleType name="EntryInfoTypeList">

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

<xs:enumeration value="UseCurrentlySelectedGroup"/>

<xs:enumeration value="DedicatedGroup"/>

<xs:enumeration value="UsePreConfigured"/>

<xs:enumeration value="LocallyDetermined"/>

</xs:restriction>

</xs:simpleType>

<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="MCPTTGroupCallType">

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

<xs:element name="MaxSimultaneousCallsN6" type="xs:positiveInteger"/>

<xs:element name="EmergencyCall" type="mcpttup:EmergencyCallType"/>

<xs:element name="ImminentPerilCall" type="mcpttup:ImminentPerilCallType"/>

<xs:element name="EmergencyAlert" type="mcpttup:EmergencyAlertType"/>

<xs:element name="Priority" type="xs:unsignedShort"/>

<xs:element name="anyExt" type="mcpttup: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="EmergencyCallType">

<xs:sequence>

<xs:choice>

<xs:element name="MCPTTGroupInitiation" type="mcpttup:MCPTTGroupInitiationEntryType"/>

<xs:element name="MCPTTPrivateRecipient" type="mcpttup:MCPTTPrivateRecipientEntryType"/>

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

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

</xs:choice>

</xs:sequence>

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

</xs:complexType>

<xs:complexType name="ImminentPerilCallType">

<xs:sequence>

<xs:element name="MCPTTGroupInitiation" type="mcpttup:MCPTTGroupInitiationEntryType"/>

<xs:element name="anyExt" type="mcpttup: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="EmergencyAlertType">

<xs:sequence>

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

<xs:element name="anyExt" type="mcpttup: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="MCPTTGroupInitiationEntryType">

<xs:choice>

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

<xs:element name="anyExt" type="mcpttup: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="MCPTTPrivateRecipientEntryType">

<xs:sequence>

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

<xs:element name="ProSeUserID-entry" type="mcpttup:ProSeUserEntryType"/>

<xs:element name="anyExt" type="mcpttup: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="OffNetworkType">

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

<xs:element name="MCPTTGroupInfo" type="mcpttup:ListEntryType"/>

<xs:element name="User-Info-ID" type="xs:hexBinary"/>

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

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

</xs:choice>

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

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

</xs:complexType>

<xs:complexType name="OnNetworkType">

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

<xs:element name="MCPTTGroupInfo" type="mcpttup:ListEntryType"/>

<xs:element name="MaxAffiliationsN2" type="xs:nonNegativeInteger"/>

<xs:element name="MaxSimultaneousTransmissionsN7" type="xs:nonNegativeInteger"/>

<xs:element name="ImplicitAffiliations" type="mcpttup:ListEntryType"/>

<xs:element name="PrivateEmergencyAlert" type="mcpttup:EmergencyAlertType"/>

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

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

</xs:choice>

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

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

</xs:complexType>

<!– Child elements to the <actions> element defined in this specification –>

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

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

<xs:element name="allow-query-availability-for-private-calls" type="xs:boolean"/>

<xs:element name="allow-enable-disable-user" type="xs:boolean"/>

<xs:element name="allow-enable-disable-UE" type="xs:boolean"/>

<xs:element name="allow-create-delete-user-alias" type="xs:boolean"/>

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

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

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

<xs:element name="allow-force-auto-answer" type="xs:boolean"/>

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

<xs:element name="allow-emergency-group-call" type="xs:boolean"/>

<xs:element name="allow-emergency-private-call" type="xs:boolean"/>

<xs:element name="allow-cancel-group-emergency" type="xs:boolean"/>

<xs:element name="allow-cancel-private-emergency-call" type="xs:boolean"/>

<xs:element name="allow-imminent-peril-call" type="xs:boolean"/>

<xs:element name="allow-cancel-imminent-peril" type="xs:boolean"/>

<xs:element name="allow-activate-emergency-alert" type="xs:boolean"/>

<xs:element name="allow-cancel-emergency-alert" type="xs:boolean"/>

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

<xs:element name="allow-imminent-peril-change" type="xs:boolean"/>

<xs:element name="allow-private-call-media-protection" type="xs:boolean"/>

<xs:element name="allow-private-call-floor-control-protection" type="xs:boolean"/>

<xs:element name="allow-request-affiliated-groups" type="xs:boolean"/>

<xs:element name="allow-request-to-affiliate-other-users" type="xs:boolean"/>

<xs:element name="allow-recommend-to-affiliate-other-users" type="xs:boolean"/>

<xs:element name="allow-private-call-to-any-user" type="xs:boolean"/>

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

<xs:element name="allow-private-call-participation" type="xs:boolean"/>

<xs:element name="allow-override-of-transmission" type="xs:boolean"/>

<xs:element name="allow-manual-off-network-switch" type="xs:boolean"/>

<xs:element name="allow-listen-both-overriding-and-overridden" type="xs:boolean"/>

<xs:element name="allow-transmit-during-override" type="xs:boolean"/>

<xs:element name="allow-off-network-group-call-change-to-emergency" type="xs:boolean"/>

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

<xs:element name="allow-create-group-broadcast-group" type="xs:boolean"/>

<xs:element name="allow-create-user-broadcast-group" type="xs:boolean"/>

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

<!– Elements included in anyExt elements –>

<xs:element name="allow-request-private-call-call-back" type="xs:boolean"/>

<xs:element name="allow-cancel-private-call-call-back" type="xs:boolean"/>

<xs:element name="allow-request-remote-initiated-ambient-listening" type="xs:boolean"/>

<xs:element name="allow-request-locally-initiated-ambient-listening" type="xs:boolean"/>

<xs:element name="allow-request-first-to-answer-call" type="xs:boolean"/>

<xs:element name="allow-request-remote-init-private-call" type="xs:boolean"/>

<xs:element name="allow-request-remote-init-group-call" type="xs:boolean"/>

<xs:element name="allow-query-functional-alias-other-user" type="xs:boolean"/>

<xs:element name="allow-takeover-functional-alias-other-user" type="xs:boolean"/>

<xs:element name="allow-location-info-when-talking" type="xs:boolean"/>

<xs:element name="allow-to-receive-private-call-from-any-user" type="xs:boolean"/>

<xs:element name="allow-to-receive-non-acknowledged-users-information" type="xs:boolean"/>

<xs:element name="AllowedMCPTTIdsForCallTransfer" type="mcpttup:ListEntryType"/>

<xs:element name="AllowedFunctionalAliasesForCallTransfer" type="mcpttup:ListEntryType"/>

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

<xs:element name="allow-call-transfer-to-any-user" type="xs:boolean"/>

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

<xs:element name="call-forwarding-on" type="xs:boolean"/>

<xs:element name="call-forwarding-no-answer-timeout" type="xs:duration" minOccurs="0"/>

<xs:element name="call-forwarding-condition" type="xs:string"/>

<xs:element name="call-forwarding-target" type="xs:anyURI"/>

<xs:element name="forward-to-functional-alias" type="xs:boolean"/>

<xs:element name="allow-call-forward-manual-input" type="xs:boolean"/>

<xs:element name="allow-functional-alias-binding-with-group" type="xs:boolean"/>

<xs:element name="RemoteGroupSelectionURIList" type="mcpttup:ListEntryType"/>

<xs:element name="GroupServerInfo" type="mcpttup:GroupServerInfoType"/>

<xs:element name="FunctionalAliasList" type="mcpttup:ListEntryType"/>

<xs:element name="ListOfAllowedFAsToCall" type="mcpttup:ListEntryType"/>

<xs:element name="ListOfAllowedFAsToBeCalledFrom" type="mcpttup:ListEntryType"/>

<xs:element name="LocationCriteriaForActivation" type="mcpttup:GeographicalAreaChangeType"/>

<xs:element name="LocationCriteriaForDeactivation" type="mcpttup:GeographicalAreaChangeType"/>

<xs:element name="manual-deactivation-not-allowed-if-location-criteria-met" type="xs:boolean"/>

<xs:element name="RulesForAffiliation" type="mcpttup:RulesForAffiliationManagementType"/>

<xs:element name="RulesForDeaffiliation" type="mcpttup:RulesForAffiliationManagementType"/>

<xs:element name="Speed" type="mcpttup:SpeedType"/>

<xs:element name="Heading" type="mcpttup:HeadingType"/>

<xs:element name="manual-deaffiliation-not-allowed-if-affiliation-rules-are-met" type="xs:boolean"/>

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

<xs:element name="MaxSimultaneousEmergencyGroupCalls" type="xs:positiveInteger"/>

<xs:element name="IncomingPrivateCallList" type="mcpttup:PrivateCallListEntryType"/>

<xs:complexType name="GroupServerInfoType">

<xs:sequence>

<xs:element name="GMS-Serv-Id" type="mcpttup:EntryType"/>

<xs:element name="IDMS-token-endpoint" type="mcpttup:EntryType"/>

<xs:element name="GroupKMSURI" type="mcpttup:EntryType"/>

<xs:element name="anyExt" type="mcpttup: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="PrivateCallKMSURI" type="mcpttup:PrivateCallKMSURIEntryType"/>

<xs:complexType name="PrivateCallKMSURIEntryType">

<xs:sequence>

<xs:element name="PrivateCallKMSURI" type="mcpttup:EntryType"/>

<xs:element name="anyExt" type="mcpttup: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="RelativePresentationPriority" type="mcpttup:PriorityType"/>

<xs:simpleType name="PriorityType">

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

<xs:minInclusive value="0"/>

<xs:maxInclusive value="255"/>

</xs:restriction>

</xs:simpleType>

<xs:attributeGroup name="IndexType">

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

</xs:attributeGroup>

<!– empty complex type –>

<xs:complexType name="emptyType"/>

<xs:complexType name="anyExtType">

<xs:sequence>

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

</xs:sequence>

</xs:complexType>

</xs:schema>

8.3.2.4 Default Document Namespace

The default document namespace used in evaluating .URIs shall be "urn:3gpp:mcptt:user-profile:1.0".

8.3.2.5 MIME type

The MIME type for the MCPTT user profile configuration document shall be "application/vnd.3gpp.mcptt-user-profile+xml".

8.3.2.6 Validation Constraints

The MCPTT user profile configuration document shall conform to the XML Schema described in clause 8.3.2.3 "XML Schema", with the clarifications given in this clause.

The value of the "XUI-URI" attribute of the <mcptt-user-profile> element shall be the same as the XUI value of the Document URI for the MCPTT user profile configuration document. If not, the XDMS shall return an HTTP "409 Conflict" response as described in IETF RFC 4825 [14], including the <constraint-failure> error element. If included, the "phrase" attribute should be set to "Wrong User Profile URI".

The document name of the MCPTT user profile configuration document shall comply with the naming convention: mcptt‑user‑profile‑<profile‑index>.xml. If not, the XDMS shall return an HTTP "409 Conflict" response as described in IETF RFC 4825 [14], including the <constraint-failure> error element. If included, the "phrase" attribute should be set to "The user profile document name does not comply with the format: ‘mcptt-user-profile-<profile-index>.xml’".

The value of the <RelativePresentationPriority> element of the <anyExt> element of the <entry> element of the <MCPTTGroupInfo> element of the <OnNetwork> element shall be within the range of 0 to 255. If not, the XDMS shall return an HTTP "409 Conflict" response as described in IETF RFC 4825 [14], including the <constraint-failure> error element. If included, the "phrase" attribute should be set to "Priority value out of range".

The value of the <RelativePresentationPriority> element of the <anyExt> element of the <entry> element of the <MCPTTGroupInfo> element of the <OffNetwork> element shall be within the range of 0 to 255. If not, the XDMS shall return an HTTP "409 Conflict" response as described in IETF RFC 4825 [14], including the <constraint-failure> error element. If included, the "phrase" attribute should be set to "Priority value out of range".

The value of the <Priority> element of the <MCPTT-group-call> element shall be within the range of 0 to 255. If not, the XDMS shall return an HTTP "409 Conflict" response as described in IETF RFC 4825 [14], including the <constraint-failure> error element. If included, the "phrase" attribute should be set to "Priority value out of range".

The value of the <DiscoveryGroupID> shall be 3 octets expressed in hexadecimal format. If not, the XDMS shall return an HTTP "409 Conflict" response as described in IETF RFC 4825 [14], including the <constraint-failure> error element. If included, the "phrase" attribute should be set to "Invalid Discovery Group ID".

The value of the <User-Info-ID> shall be 6 octets expressed in hexadecimal format. If not, the XDMS shall return an HTTP "409 Conflict" response as described in IETF RFC 4825 [14], including the <constraint-failure> error element. If included, the "phrase" attribute should be set to "Invalid User Info ID".

If more than one MCPTT user profile document is specified for the MCPTT user in the "XDM collections" in the user’s directory, then only one MCPTT user profile document shall contain the <Pre-selected-indication> element. If there is only one MCPTT user profile specified for the MCPTT user in the user’s directory, then it is optional to include the <Pre-selected-indication> element. If a MCPTT user profile document containing the <Pre-selected-indication> element already exists for the MCPTT user in the "XDM collections" the XDMS shall return an HTTP "409 Conflict" response as described in IETF RFC 4825 [14], including the <constraint-failure> error element. If included, the "phrase" attribute should be set to "Pre-selected User Profile Indication already exists in:" including the contents of the <Profile-Name> element of the MCPTT user profile document that already contains the <Pre-selected-indication> element.

8.3.2.7 Data Semantics

The <Name> element is of type "token", and corresponds to the "Name" element of clause 5.2.3 in 3GPP TS 24.483 [4].

The <alias-entry> element of the <UserAlias> element is of type "token" and indicates an alphanumeric alias of the MCPTT user, and corresponds to the leaf nodes of the "UserAlias" element of clause 5.2.8 in 3GPP TS 24.483 [4].

The <uri-entry> element is of type "anyURI" and when it appears within:

– the <MCPTTUserID> element contains the MCPTT user identity (MCPTT ID) of the MCPTT user, and corresponds to the "MCPTTUserID" element of clause 5.2.7 in 3GPP TS 24.483 [4];

– the <entry> element of the <MCPTTGroupInitiation> element of the <EmergencyCall> element of the <MCPTT-group-call> element, indicates the MCPTT group used on initiation of an MCPTT emergency group call and corresponds to the "GroupID" element of the "MCPTTGroupInitiation" element of clause 5.2.34B in 3GPP TS 24.483 [4];

– the <entry> element of the <MCPTTPrivateRecipient> of the <EmergencyCall> element of the <PrivateCall> element indicates the recipient MCPTT user for an MCPTT emergency private call and corresponds to the "ID" element of clause 5.2.29B in 3GPP TS 24.483 [4];

– the <entry> element of the <MCPTTGroupInitiation> element of the <ImminentPerilCall> element of the <MCPTT-group-call> element, indicates the MCPTT group used on initiation of an MCPTT imminent peril group call and corresponds to the "GroupID" element of clause 5.2.39B in 3GPP TS 24.483 [4];

– the <entry> element of the <EmergencyAlert> element of the <MCPTT-group-call> element, indicates the MCPTT group recipient for an MCPTT emergency Alert and corresponds to the "ID" element of clause 5.2.43B in 3GPP TS 24.483 [4];

– the <entry> element of the <EmergencyAlert> element of the <PrivateEmergencyAlert> element indicates the MCPTT user recipient for an on-network MCPTT emergency private alert and corresponds to the "ID" element of clause 5.2.48J4 in 3GPP TS 24.483 [4];

– the <PrivateCallURI> of the <PrivateCall> list element indicates an MCPTT ID of an MCPTT user that the MCPTT user is authorised to initiate a private call to and corresponds to the "MCPTTID" element of clause 5.2.17 in 3GPP TS 24.483 [4];

– the <uri-entry> element of the <PrivateCallKMSURI> element of the <PrivateCallKMSURI> element of the <anyExt> element of the <PrivateCallList> element of the <PrivateCall> element of the <Common> element contains the URI used to contact the KMS associated with the MCPTT IDs contained in the PrivateCallURI elements of the <PrivateCallList> element and corresponds to the "PrivateCallKMSURI" element of clause 5.2.19B in 3GPP TS 24.483 [4]; If the <uri-entry> element is empty, the KMS present in the MCS initial configuration document is used;

– The <PrivateCallKMSURI> element of the <anyExt> element of the <PrivateCallURI> element of the <PrivateCallList> element of the <Common> element is only present if the URI of the KMS for the associated MCPTT ID is different from the KMS URI in <uri-entry> element of the <PrivateCallKMSURI> element of the <PrivateCallKMSURI> element of the <anyExt> element of the <PrivateCallList> element of the <PrivateCall> element of the <Common> element and corresponds to the "PrivateCallKMSURI" element of clause 5.2.19B in 3GPP TS 24.483 [4];

– the <entry> element of the <ImplicitAffiliations> list element indicates an MCPTT group ID of an MCPTT group that the MCPTT user is implicitly affiliated with and corresponds to the "MCPTTGroupID" element of clause 5.2.48C4 in 3GPP TS 24.483 [4];

– the <entry> element of the <MCPTTGroupInfo> element of the <OnNetwork> element indicates an MCPTT group ID of an MCPTT group that the MCPTT user is authorised to affiliate with during on-network operation and corresponds to the "MCPTTGroupID" element of clause 5.2.48B4 in 3GPP TS 24.483 [4];

– the <entry> element of the <RemoteGroupSelectionURIList> list element of the <anyExt> element of the <OnNetwork> element indicates an MCPTT ID of an MCPTT user whose selected group is authorised to be remotely changed by the MCPTT user and corresponds to the "MCPTTID" element of clause 5.2.48U4 in 3GPP TS 24.483 [4];

– the <GMS-Serv-Id> element of the <GroupServerInfo> element of the <anyExt> element of the <entry> element of the <MCPTTGroupInfo> element of the <OnNetwork> element contains the URI used to contact the group management server for the MCPTT group ID in the <uri-entry> element of the <entry> element of the <MCPTTGroupInfo> element and corresponds to the "GMSServID" element of clause 5.2.48B8 in 3GPP TS 24.483 [4];

– the <IDMS-token-endpoint> element of the <GroupServerInfo> element of the <anyExt> element of the <entry> element of the <MCPTTGroupInfo> element of the <OnNetwork> element contains the URI used to contact the identity management server token endpoint for the MCPTT group ID in the <uri-entry> element of the <entry> element of the <MCPTTGroupInfo> element and corresponds to the "IDMSTokenEndPoint" element of clause 5.2.48B9 in 3GPP TS 24.483 [4]. If the entry element is empty, the idms-auth-endpoint and idms-token-endpoint present in the MCS initial configuration document are used;

– the <GroupKMSURI> element of the <GroupServerInfo> element of the <anyExt> element of the <entry> element of the <MCPTTGroupInfo> element of the <OnNetwork> element contains the URI used to contact the key management server for the MCPTT group ID in the <uri-entry> element of the <entry> element of the <MCPTTGroupInfo> element and corresponds to the "GroupKMSURI" element of clause 5.2.48B10 in 3GPP TS 24.483 [4]. If the entry element is empty, the kms present in the MCS initial configuration document is used;

– the <PrivateCallURI> element of the <IncomingPrivateCallList> element of the <anyExt> element of the <OnNetwork> element indicates an MCPTT ID of an MCPTT user from whom the MCPTT user is authorised to receive a private call and corresponds to the "MCPTTID" element of clause 5.2.48Y4 in 3GPP TS 24.483 [4];

– the <PrivateCallKMSURI> element of the <PrivateCallKMSURI> of the <anyExt> element of the <PrivateCallURI> element of the <IncomingPrivateCallList> element of the <anyExt> element of the <OnNetwork> element is only present if the URI of the KMS for the associated MCPTT ID is different from the KMS URI in <uri-entry> element of the <PrivateCallKMSURI> element of the <PrivateCallKMSURI> element of the <anyExt> element of the <IncomingPrivateCallList> element of the <OnNetwork> element and corresponds to the "PrivateCallKMSURI" element of clause 5.2.48Y5 in 3GPP TS 24.483 [4];

– the <PrivateCallKMSURI> element of the <PrivateCallKMSURI> element of the <anyExt> element of the <IncomingPrivateCallList> element of the <OnNetwork> element contains the URI used to contact the KMS associated with the MCPTT IDs contained in the PrivateCallURI elements of the <IncomingPrivateCallList> element and corresponds to the "PrivateCallKMSURI" element of clause 5.2.48Y5 in 3GPP TS 24.483 [4]; If the <uri-entry> element is empty, the KMS present in the MCS initial configuration document is used;

– the <entry> element of the <FunctionalAliasList> list element of the <anyExt> element of the <OnNetwork> element contains a functional alias that the MCPTT user is authorised to activate and corresponds to the "FunctionalAlias" element of clause 5.2.48W6 in 3GPP TS 24.483 [4];

– the <entry> element of the <ListOfAllowedFAsToCall> element in the <anyExt> element of the <FunctionalAliasList> element within the <anyExt> element of the <OnNetwork> element contains a target functional alias that the MCPTT user is authorised to call, if it has activated and is using the parent functional alias (see <FunctionalAliasList> element), and corresponds to the "FunctionalAlias" element of clause 5.2.48W7E in 3GPP TS 24.483 [4];

– the <entry> element of the <ListOfAllowedFAsToBeCalledFrom> element in the <anyExt> element of the <FunctionalAliasList> element within the <anyExt> element of the <OnNetwork> element contains a functional alias from which the MCPTT user is authorised to receive a call, if it has activated and is using the parent functional alias (see <FunctionalAliasList> element);

– the <GMS-Serv-Id> element of the <GroupServerInfo> element of the <anyExt> element of the <entry> element of the <MCPTTGroupInfo> element of the <OffNetwork> element contains the URI used to contact the group management server for the MCPTT group ID in the <uri-entry> element of the <entry> element of the <MCPTTGroupInfo> element and corresponds to the "GMSServID" element of clause 5.2.53C in 3GPP TS 24.483 [4];

– the <IDMS-token-endpoint> element of the <GroupServerInfo> element of the <anyExt> element of the <entry> element of the <MCPTTGroupInfo> element of the <OffNetwork> element contains the URI used to contact the identity management server for the MCPTT group ID in the <uri-entry> element of the <entry> element of the <MCPTTGroupInfo> element and corresponds to the "IDMSTokenEndPoint" element of clause 5.2.53D8A9 in 3GPP TS 24.483 [4]. If the entry element is empty, the idms-auth-endpoint and idms-token-endpoint present in the MCS initial configuration document are used;

– the <GroupKMSURI> element of the <GroupServerInfo> element of the <anyExt> element of the <entry> element of the <MCPTTGroupInfo> element of the <OffNetwork> element contains the URI used to contact the key management server for the MCPTT group ID in the <uri-entry> element of the <entry> element of the <MCPTTGroupInfo> element and corresponds to the "GroupKMSURI" element of clause 5.2.53E in 3GPP TS 24.483 [4]. If the entry element is empty, the kms present in the MCS initial configuration document is used;

– the <entry> element of the <AllowedMCPTTIdsForCallTransfer> list element of the <anyExt> element of the <OnNetwork> element indicates an MCPTT ID that is allowed to be used as target ID for a private call transfer and and does not appear in the MCPTT user profile configuration managed object specified in 3GPP TS 24.483 [4];

– the <entry> element of the <AllowedFunctionalAliasesForCallTransfer> list element of the <anyExt> element of the <OnNetwork> element contains a functional alias that is allowed to be used as target ID for a private call transfer and and does not appear in the MCPTT user profile configuration managed object specified in 3GPP TS 24.483 [4]; and

– the <call-forwarding-target> element within the <anyExt> element of the <OnNetwork> element is of type "anyURI" and indicates the target MCPTT ID or functional alias of the call forwarding and does not appear in the MCPTT user profile configuration managed object specified in 3GPP TS 24.483 [4].

The <DiscoveryGroupID> element is of type "hexBinary" and is used as the Discovery Group ID in the ProSe discovery procedures as specified in 3GPP TS 23.303 [18] and 3GPP TS 23.334 [19]. When it appears within:

– the <MCPTTPrivateRecipient> element of the <EmergencyCall> element it identifies the Discovery Group ID that the MCPTT UE uses to initiate an off-network MCPTT emergency private call and corresponds to the "DiscoveryGroupID" element of clause 5.2.29C in 3GPP TS 24.483 [4]; and

– the <PrivateCallProSeUser> element of the <PrivateCallList> element it identifies the Discovery Group ID that the MCPTT UE uses to initiate a private call during off-network operation and corresponds to the "DiscoveryGroupID" element of clause 5.2.18 in 3GPP TS 24.483 [4].

The <display-name> element is of type "string", contains a human readable name and when it appears within:

– the <entry> element of the <MCPTTGroupInitiation> element of the <EmergencyCall> element of the <MCPTT-group-call> element, indicates the name of the MCPTT group used on initiation of an MCPTT emergency group call and corresponds to the "DisplayName" element of the "MCPTTGroupInitiation" element of clause 5.2.34C in 3GPP TS 24.483 [4];

– the <entry> element of the <MCPTTPrivateRecipient> of the <EmergencyCall> element of the <PrivateCall> element indicates the name of the recipient MCPTT user for an MCPTT emergency private call and corresponds to the "DisplayName" element of clause 5.2.29E in 3GPP TS 24.483 [4];

– the <entry> element of the <MCPTTGroupInitiation> element of the <ImminentPerilCall> element of the <MCPTT-group-call> element, indicates the name of the MCPTT group used on initiation of an MCPTT imminent peril group call and corresponds to the "DisplayName" element of clause 5.2.39C in 3GPP TS 24.483 [4];

– the <entry> element of the <EmergencyAlert> element of the <MCPTT-group-call> element, indicates the name of the MCPTT group recipient for an MCPTT emergency Alert and corresponds to the "DisplayName" element of clause 5.2.43D in 3GPP TS 24.483 [4];

– the <entry> element of the <EmergencyAlert> element of the <PrivateEmergencyAlert> element indicates the name of the MCPTT user recipient for an on-network MCPTT emergency private alert and corresponds to the "DisplayName" element of clause 5.2.48J5 in 3GPP TS 24.483 [4];

– the <PrivateCallURI> of the <PrivateCallList> element indicates the name of an MCPTT ID of an MCPTT user that the MCPTT user is authorised to initiate a private call to and corresponds to the "DisplayName" element of clause 5.2.19A in 3GPP TS 24.483 [4];

– the <entry> element of the <MCPTTGroupInfo> element of the <OnNetwork> element indicates the name of an MCPTT group ID of an MCPTT group that the MCPTT user is authorised to affiliate with during on-network operation and corresponds to the "DisplayName" element of clause 5.2.48B5 in 3GPP TS 24.483 [4]; and

– the <ImplicitAffiliations> list element indicates the name of of an MCPTT group that the MCPTT user is implicitly affiliated with and corresponds to the "DisplayName" element of clause 5.2.48C5 in 3GPP TS 24.483 [4]; and

– the <entry> element of the <MCPTTGroupInfo> element of the <OffNetwork> element indicates the name of an off-network MCPTT group that the MCPTT user is authorised to join during off-network operation and corresponds to the "DisplayName" element of clause 5.2.53A in 3GPP TS 24.483 [4].

The "index" attribute is of type "token" and is included within some elements for uniqueness purposes, and does not appear in the user profile configuration managed object specified in 3GPP TS 24.483 [4].

The <Status> element is of type "Boolean" and indicates whether this particular MCPTT user profile is enabled or disabled and corresponds to the "Status" element of clause 5.2.59 in 3GPP TS 24.483 [4]. When set to "true" this MCPTT user profile is enabled. When set to "false" this MCPTT user profile is disabled.

The "user-profile-index" is of type "unsignedByte" and indicates the particular MCPTT user profile configuration document in the collection and corresponds to the "MCPTTUserProfileIndex" element of clause 5.2.7A in 3GPP TS 24.483 [4].

The <ProfileName> element is of type "token" and specifies the name of the MCPTT user profile configuration document in the MCPTT user profile XDM collection and corresponds to the "MCPTTUserProfileName" element of clause 5.2.7B in 3GPP TS 24.483 [4].

The <Pre-selected-indication> element is of type "mcpttup:emptyType". Presence of the <Pre-selected-indication> element indicates that this particular MCPTT user profile is designated to be the pre-selected MCPTT user profile as defined in 3GPP TS 23.379 [8], and corresponds to the "PreSelectedIndication" element of clause 5.2.7C in 3GPP TS 24.483 [4]. Absence of the <Pre-selected-indication> element indicates that this MCPTT user profile is not designated as the pre-selected MCPTT user profile within the collection of MCPTT user profiles for the MCPTT user or is the only MCPTT user profile within the collection and is the pre-selected MCPTT user profile by default.

The "XUI-URI" attribute is of type "anyURI" that contains the XUI of the MCPTT user for whom this MCPTT user profile configuration document is intended and does not appear in the user profile configuration managed object specified in 3GPP TS 24.483 [4].

The <ParticipantType> element of the <Common> element is of type "token" and indicates the functional category of the MCPTT user (e.g., first responder, second responder, dispatch, dispatch supervisor). The <ParticipantType> element corresponds to the "ParticipantType" element of clause 5.2.10 in 3GPP TS 24.483 [4].

The <RelativePresentationPriority> element of the <anyExt> element of the <entry> element when it appears in:

– the <MCPTTGroupInfo> element of the <OnNetwork> element, contains an integer value between 0 and 255 indicating the presentation priority of the on-network group relative to other on-network groups and on-network users, and corresponds to the "RelativePresentationPriority" element of clause 5.2.48B7 in 3GPP TS 24.483 [4]; and

– the <MCPTTGroupInfo> element of the <OffNetwork> element, contains an integer value between 0 and 255 indicating the presentation priority of the off-network group relative to other off-network groups and off-network users, and corresponds to the "RelativePresentationPriority" element of clause 5.2.53B in 3GPP TS 24.483 [4].

The <MaxAffiliationsN2> element is of type "nonNegativeInteger", and indicates to the MCPTT server the maximun number of MCPTT groups that the MCPTT user is authorised to affiliate with.

The <MaxSimultaneousCallsN6> element of the <MCPTT-group-call> element is of type "positiveInteger" and indicates the maximum number of simultaneously received MCPTT group calls, and corresponds to the "MaxSimultaneouCallsN6" element of clause 5.2.31 in 3GPP TS 24.483 [4].

The <MaxSimultaneousTransmissionsN7> element is of type "positiveInteger", and indicates to the MCPTT server the maximum number of simultaneous transmissions received in one MCPTT group call for override.

The <MaxSimultaneousEmergencyGroupCalls> element of the <anyExt> element within the <entry> element of the <FunctionalAliasList> list element of the <anyExt> element within the <OnNetwork> element is of type "positiveInteger" and indicates the maximum number of simultaneous MCPTT emergency group calls for the specific functional alias, and corresponds to the "MaxSimultaneousEmergencyGroupCalls" element of clause 5.2.48W7A in 3GPP TS 24.483 [4].

The <Priority> element of the <MCPTT-group-call> element is of a type "nonNegativeInteger", indicates the priority of the MCPTT user for initiating and receiving MCPTT calls and corresponds to the "Priority" element of clause 5.2.44 in 3GPP TS 24.483 [4].

The <User-Info-ID> element is of type "hexBinary". When the <User-Info-ID> element appears within:

– the <ProSeUserID-entry> element of the <MCPTTPrivateRecipient> of the <EmergencyCall> element indicates the ProSe "User Info ID" as defined in 3GPP TS 23.303 [18] and 3GPP TS 24.334 [19] of the recipient MCPTT user for an MCPTT emergency private call and corresponds to the "UserInfoID" element of clause 5.2.29D in 3GPP TS 24.483 [4];

– the <PrivateCallProSeUser> element of the <PrivateCallList> element, indicates a ProSe "User Info ID" as defined in 3GPP TS 23.303 [18] and 3GPP TS 24.334 [19] of another MCPTT user that the MCPTT user is authorised to initiate a private call to and corresponds to the "UserInfoID" element of clause 5.2.19 in 3GPP TS 24.483 [4]; and

– the <OffNetwork> element, indicates the ProSe "User Info ID" as defined in 3GPP TS 23.303 [18] and 3GPP TS 24.334 [19] of the MCPTT UE for off-network operation and corresponds to the "UserInfoID" element of clause 5.2.58 in 3GPP TS 24.483 [4].

The "entry-info" attribute is of type "string" and when it appears within:

– the <entry> element of the <MCPTTGroupInitiation> element of the <EmergencyCall> element of the <MCPTT-group-call> element, it corresponds to the "Usage" element of clause 5.2.34D in 3GPP TS 24.483 [4] and indicates to use as the destination address for an emergency group call:

a) the MCPTT user currently selected MCPTT group if the "entry-info"attribute has the value of ‘UseCurrentlySelectedGroup’; or

b) the value in the <uri-entry> element within the <entry> element of the <MCPTTGroupInitiation> element for an on-network emergency group call, if the "entry-info" attribute has the value of ‘DedicatedGroup’ or if the "entry-info"attribute has the value of ‘UseCurrentlySelectedGroup’ and the MCPTT user has no currently selected MCPTT group;

– the <entry> element of the <MCPTTPrivateRecipient> element of the <EmergencyCall> element of the <PrivateCall> element, it corresponds to the "Usage" element of clause 5.2.29F in 3GPP TS 24.483 [4] and indicates to use as the destination address for an emergency private call:

a) an MCPTT ID of an MCPTT user that is selected by the MCPTT user if the "entry-info"attribute has the value of ‘LocallyDetermined’;

b) the value in the <uri-entry> element within the <entry> element of the <MCPTTPrivateRecipient> for an on-network emergency private call, if the "entry-info"attribute has the value of ‘UsePreConfigured’; or

c) the value in the <User-Info-ID> element within the <ProSeUserID-entry> element of the <MCPTTPrivateRecipient> for an off-network emergency private call, if the "entry-info"attribute has the value of ‘UsePreConfigured’;

– the <entry> element of the <MCPTTGroupInitiation> element of the <ImminentPerilCall> element of the <MCPTT-group-call> element, it corresponds to the "Usage" element of clause 5.2.39D in 3GPP TS 24.483 [4] and indicates to use as the destination for the MCPTT imminent peril group call:

a) the MCPTT user currently selected MCPTT group if the "entry-info" attribute has the value of ‘UseCurrentlySelectedGroup’; or

b) the value in the <uri-entry> element within the <entry> element of the <MCPTTGroupInitiation> for an on-network imminent peril call, if the "entry-info" attribute has the value of:

i) ‘DedicatedGroup’; or

ii) ‘UseCurrentlySelectedGroup’ and the MCPTT user has no currently selected MCPTT group; and

– the <entry> element within the <EmergencyAlert> element, it corresponds to the "Usage" element of clause 5.2.43E in 3GPP TS 24.483 [4] and indicates to use as the destination address for a group emergency alert:

a) the MCPTT user currently selected MCPTT group if the "entry-info"attribute has the value of ‘UseCurrentlySelectedGroup’;

b) the value in the <uri-entry> element within the <entry> element of the <EmergencyAlert> element for an on-network group emergency alert, if the "entry-info" attribute has the value of:

i) ‘DedicatedGroup’; or

ii) ‘UseCurrentlySelectedGroup’ and the MCPTT user has no currently selected MCPTT group.

– the <entry> element within the <PrivateEmergencyAlert> element, it corresponds to the "Usage" element of clause 5.2.48J6 in 3GPP TS 24.483 [4] and indicates to use as the destination address for on-network private emergency alert:

a) the MCPTT ID of an MCPTT user that is selected by the MCPTT user if the "entry-info"attribute has the value of ‘LocallyDetermined’; and

b) the value in the <uri-entry> element within the <entry> element of the <PrivateEmergencyAlert> element, if the "entry-info" attribute has the value of:

i) ‘UsePreConfigured’; or

ii) ‘LocallyDetermined’ and the MCPTT user has no currently selected MCPTT user.

The <LocationCriteriaForActivation> element within the <anyExt> element of the <entry> element within the <FunctionalAliasList> list element of the <anyExt> element of the <OnNetwork> element indicates the geographical area changes that trigger the functional alias activation. It corresponds to the "LocationCriteriaForActivation" element of clause 5.2.48W6A in 3GPP TS 24.483 [4] and consists of the following sub-elements:

– <EnterSpecificArea> element is of type "mcpttup: GeographicalAreaType". It is an optional element indicating a geographical area which when entered triggers the functional alias activation. The <EnterSpecificArea> element has the following sub-elements:

a) <PolygonArea>, an optional element specifying the area as a polygon specified in clause 5.2 in 3GPP TS 23.032 [31];

b) <EllipsoidArcArea>, an optional element specifying the area as an Ellipsoid Arc specified in clause 5.7 in 3GPP TS 23.032 [31];

c) an <anyExt> element which may contain a <Speed> element; and

d) an <anyExt> element which may contain a <Heading> element.

– <ExitSpecificArea> element is of type "mcpttup: GeographicalAreaType". It is an optional element indicating a geographical area which when exited triggers the functional alias activation and has the same sub-elements as <EnterSpecificArea>.

The <LocationCriteriaForDeactivation> element within the <anyExt> element of the <entry> element within the <FunctionalAliasList> list element of the <anyExt> element of the <OnNetwork> element indicates the geographical area changes that trigger the functional alias de-activation. It corresponds to the "LocationCriteriaForDeactivation" element of clause 5.2.48W6B in 3GPP TS 24.483 [4] and consists of the following sub-elements:

– <EnterSpecificArea> element is of type "mcpttup: GeographicalAreaType". It is an optional element specifying a geographical area which when entered triggers the functional alias de-activation; and

– <ExitSpecificArea> element is of type "mcpttup: GeographicalAreaType". It is an optional element specifying a geographical area which when exited triggers the functional alias de-activation.

The <manual-deactivation-not-allowed-if-location-criteria-met> element within the <anyExt> element of the <entry> element within the <FunctionalAliasList> list element of the <anyExt> element of the <OnNetwork> element is of type "Boolean" and corresponds to the "ManualDeactivationNotAllowedIfLocationCriteriaMet" element of clause 5.2.48W6C in 3GPP TS 24.483 [4]. When set to "true" the MCPTT user is not allowed to deactivate the functional alias while the location criteria for activation are met.

The <RulesForAffiliation> element within the <anyExt> element of the <entry> element within the <MCPTTGroupInfo> element of the <OnNetwork> element indicates upon a change in geographical area or a change in functional alias activation status to the MCPTT client to evaluate the rules. If for any rule any location criteria is fulfilled and any functional alias criteria is fulfilled the MCPTT client triggers the group affiliation. It corresponds to the "RulesForAffiliation" element of clause 5.2.48B4A in 3GPP TS 24.483 [4] and consists of the following sub-elements:

– <ListOfLocationCriteria> element is of type "mcpttup: GeographicalAreaChangeType". It is an optional element indicating the location related criteria of a rule. The <ListOfLocationCriteria> element has the following sub-elements:

a) <EnterSpecificArea> element is of type "mcpttup: GeographicalAreaType". It is an optional element indicating a geographical area which when entered triggers the evaluation of the rules. If any rule is fulfilled it triggers the group affiliation. The <EnterSpecificArea> element has the following sub-elements:

i] <PolygonArea>, an optional element specifying the area as a polygon specified in clause 5.2 in 3GPP TS 23.032 [31];

ii) <EllipsoidArcArea>, an optional element specifying the area as an Ellipsoid Arc specified in clause 5.7 in 3GPP TS 23.032 [31];

iii <anyExt> optional element which may contain a <Speed> element that has the following sub-elements:

A) <MinimumSpeed> is of type "unsignedShort", indicates the minimum speed that is considered in the evaluation of a rule for a specific area that would trigger affiliation and corresponds to the "MinimumSpeed" element of clause 5.2.48B4A19 in 3GPP TS 24.483 [4].

B) <MaximumSpeed> is of type "unsignedShort", indicates the maximum speed that is considered in the evaluation of a rule for a specific area that would trigger affiliation and corresponds to the "MaximumSpeed" element of clause 5.2.48B4A20 in 3GPP TS 24.483 [4].

iv) <anyExt> optional element which may contain a <Heading> element that has the following sub-elements:

A) <MinimumHeading> is of type "unsignedShort", indicates the minimum heading that is considered in the evaluation of a rule for a specific area that would trigger affiliation and corresponds to the "Minimum" element of clause 5.2.48B4A22 in 3GPP TS 24.483 [4]; and

B) <MaximumHeading> is of type "unsignedShort", indicates the maximum heading that is considered in the evaluation of a rule for a specific area that would trigger affiliation and corresponds to the "Maximum" element of clause 5.2.48B4A23 in 3GPP TS 24.483 [4].

b) <ExitSpecificArea> element is of type "mcpttup: GeographicalAreaType". It is an optional element indicating a geographical area which when exited triggers the evaluation of the rules- If any rule is fulfilled it triggers it triggers the group affiliation. It has the same sub-elements as <EnterSpecificArea>.

– <ListOfActiveFunctionalAliasCriteria> containing one or more <entry> elements containing the <anyExt> element set to the functional alias whose activation or deactivation trigger evaluation of the rules and corresponds to the "FunctionalAlias" element of clause 5.2.48B4A47 in 3GPP TS 24.483 [4];

The <RulesForDeaffiliation> element within the <anyExt> element of the <entry> element within the <MCPTTGroupInfo> element of the <OnNetwork> element indicates upon a change in geographical area or a change in functional alias activation status to the MCPTT client to evaluate the rules. If for any rule any location criteria is fulfilled and any functional alias criteria is fulfilled the MCPTT client triggers the group deaffiliation. It corresponds to the "RulesForDeaffiliation" element of clause 5.2.48B4B in 3GPP TS 24.483 [4] and consists of the following sub-elements:

– <ListOfLocationCriteria> element is of type "mcpttup: GeographicalAreaChangeType". It is an optional element indicating the location related criteria of a rule.

– <ListOfActiveFunctionalAliasCriteria> containing one or more <entry> elements containg the <anyExt> element set to the functional alias whose activation or deactivation trigger evaluation of the rules and corresponds to the "FunctionalAlias" element of clause 5.2.48B4B47 in 3GPP TS 24.483 [4];

The <manual-deaffiliation-not-allowed-if-affiliation-rules-are-met> element within the <anyExt> element element within the <MCPTTGroupInfo> element of the <anyExt> element of the <OnNetwork> element is of type "Boolean" and corresponds to the "ManualDeaffiliationNotAllowedIfAffiliation RulesAreMet" element of clause 5.2.48B6 in 3GPP TS 24.483 [4]. When set to "true" the MCPTT user is not allowed to deaffiliate from the group if the rules for affiliation are met.

The <call-forwarding-no-answer-timeout> element within the <anyExt> element of the <OnNetwork> element is of type "duration" and indicates the duration of the no answer timer for call forwarding and does not appear in the MCPTT user profile configuration managed object specified in 3GPP TS 24.483 [4];

The <call-forwarding-condition> element within the <anyExt> element of the <OnNetwork> element is of type "string", and indicates the condition of the call forwarding and does not appear in the MCPTT user profile configuration managed object specified in 3GPP TS 24.483 [4]:

– set to a value of "immediate" for call forwarding immediate; or

– set to a value of "no-answer" for call forwarding no answer.

The <user-max-simultaneous-authorizations> element of the <anyExt> element contained in the <OnNetwork> element is of type "positiveInteger" and indicates the maximum allowed number of simultaneous service authorizations for the MCPTT user.The <allow-presence-status> element is of type Boolean, as specified in table 8.3.2.7-1, and corresponds to the "AllowedPresenceStatus" element of clause 5.2.48E in 3GPP TS 24.483 [4].

Table 8.3.2.7-1: Values of <allow-presence-status>

"true"	indicates to the MCPTT user that their presence on the network is available.
"false"	indicates to the MCPTT user that their presence on the network is not available

The <allow-request-presence> element is of type Boolean, as specified in table 8.3.2.7-2, and corresponds to the "AllowedPresence" element of clause 5.2.48F in 3GPP TS 24.483 [4].

Table 8.3.2.7-2: Values of <allow-request-presence>

"true"	indicates that the MCPTT user is locally authorised to request whether a particular MCPTT User is present on the network.
"false"	indicates that the MCPTT user is not locally authorised to request whether a particular MCPTT User is present on the network.

The <allow-query-availability-for-private-calls> element is of type Boolean, as specified in table 8.3.2.7-3, and does not appear in the MCPTT user profile configuration managed object specified in 3GPP TS 24.483 [4].

Table 8.3.2.7-3: Values of <allow-query-availability-for-private-calls>

"true"	indicates that the MCPTT user is locally authorised to query the availability of other MCPTT users to participate in a private call.
"false"	indicates that the MCPTT user is not locally authorised to query the availability of other MCPTT users to participate in a private call.

The <allow-enable-disable-user> element is of type Boolean, as specified in table 8.3.2.7-4, and does not appear in the MCPTT user profile configuration managed object specified in 3GPP TS 24.483 [4].

Table 8.3.2.7-4: Values of <allow-enable-disable-user>

"true"	indicates that the MCPTT user is locally authorised to enable/disable other MCPTT users from receiving MCPTT service.
"false"	indicates that the MCPTT user is not locally authorised to enable/disable other MCPTT users from receiving MCPTT service.

The <allow-enable-disable-UE> element is of type Boolean, as specified in table 8.3.2.7-5, and does not appear in the MCPTT user profile configuration managed object specified in 3GPP TS 24.483 [4].

Table 8.3.2.7-5: Values of <allow-enable-disable-UE>

"true"	indicates that the MCPTT user is locally authorised to enable/disable other MCPTT UEs from receiving MCPTT service.
"false"	indicates that the MCPTT user is not locally authorised to enable/disable other MCPTT UEs from receiving MCPTT service.

The <allow-create-delete-user-alias> element is of type Boolean, as specified in table 8.3.2.7-6, and corresponds to the "AuthorisedAlias" element of clause 5.2.9 in 3GPP TS 24.483 [4].

Table 8.3.2.7-6: Values of <allow-create-delete-user-alias>

"true"	indicates that the MCPTT user is locally authorised to create or delete aliases of an MCPTT user and its associated user profiles.
"false"	indicates that the MCPTT user is not locally authorised to create or delete aliases of an MCPTT user and its associated user profiles.

The <allow-private-call> element is of type Boolean, as specified in table 8.3.2.7-7, and corresponds to the "Authorised" element of clause 5.2.13 in 3GPP TS 24.483 [4].

Table 8.3.2.7-7: Values of <allow-private-call>

"true"

instructs the MCPTT server performing the originating participating MCPTT function for the MCPTT user, that the MCPTT user is authorised to request a private call request using the procedures defined in 3GPP TS 24.379 [9]. The recipient must be a MCPTT user identified in a <entry> element of the <PrivateCall> element, which corresponds to leaf nodes of "UserList" in clause 5.2.16 in 3GPP TS 24.483 [4].

"false"

instructs the MCPTT server performing the originating participating MCPTT function for the MCPTT user, to reject private call request using the procedures defined in 3GPP TS 24.379 [9]. This shall be the default value taken in the absence of the element;

The <allow-manual-commencement> element is of type Boolean, as specified in table 8.3.2.7-8, and corresponds to the "ManualCommence" element of clause 5.2.20 in 3GPP TS 24.483 [4].

Table 8.3.2.7-8: Values of <allow-manual-commencement>

"true"	instructs the MCPTT server performing the originating participating MCPTT function for the MCPTT user, that the MCPTT user is authorised to request a private call with manual commencement using the procedures defined in 3GPP TS 24.379 [9].
"false"	instructs the MCPTT server performing the originating participating MCPTT function for the MCPTT user, that the MCPTT user is not authorised to request a private call with manual commencement using the procedures defined in 3GPP TS 24.379 [9].

The <allow-automatic-commencement> element is of type Boolean, as specified in table 8.3.2.7-9, corresponds to the "AutoCommence" element of clause 5.2.21 in 3GPP TS 24.483 [4].

Table 8.3.2.7-9: Values of <allow-automatic-commencement>

"true"	instructs the MCPTT server performing the originating participating MCPTT function for the MCPTT user, that the MCPTT user is authorised to request a private call with automatic commencement using the procedures defined in 3GPP TS 24.379 [9].
"false"	instructs the MCPTT server performing the originating participating MCPTT function for the MCPTT user, that the MCPTT user is not authorised to request a private call with automatic commencement using the procedures defined in 3GPP TS 24.379 [9].

The <allow-force-auto-answer> element is of type Boolean, as specified in table 8.3.2.7-10, and corresponds to the "AutoAnswer" element of clause 5.2.22 in 3GPP TS 24.483 [4].

Table 8.3.2.7-10: Values of <allow-force-auto-answer>

"true"	instructs the MCPTT server performing the originating participating MCPTT function for the MCPTT user, that the MCPTT user is authorised to request a private call and force automatic commencement using the procedures defined in 3GPP TS 24.379 [9].
"false"	instructs the MCPTT server performing the originating participating MCPTT function for the MCPTT user, that the MCPTT user is not authorised to request a private call and force automatic commencement using the procedures defined in 3GPP TS 24.379 [9].

The <allow-failure-restriction> element is of type Boolean, as specified in table 8.3.2.7-11, and corresponds to the "FailRestrict" element of clause 5.2.23 in 3GPP TS 24.483 [4].

Table 8.3.2.7-11: Values of <allow-failure-restriction>

"true"	instructs the MCPTT server performing the originating participating MCPTT function for the MCPTT user, that the MCPTT user is authorised to restrict the notification of a call failure reason for a private call (with or without floor control) using the procedures defined in 3GPP TS 24.379 [9].
"false"	instructs the MCPTT server performing the originating participating MCPTT function for the MCPTT user, that the MCPTT user is not authorised to restrict the notification of a call failure reason for a private call (with or without floor control) using the procedures defined in 3GPP TS 24.379 [9].

The <allow-emergency-group-call> element is of type Boolean, as specified in table 8.3.2.7-12, and corresponds to the "Enabled" element of clause 5.2.33 in 3GPP TS 24.483 [4].

Table 8.3.2.7-12: Values of <allow-emergency-group-call>

"true"	instructs the MCPTT server performing the originating participating MCPTT function for the MCPTT user, that the MCPTT user is authorised to request an emergency group call using the procedures defined in 3GPP TS 24.379 [9].
"false"	instructs the MCPTT server performing the originating participating MCPTT function for the MCPTT user, that the MCPTT user is not authorised to request an emergency group call using the procedures defined in 3GPP TS 24.379 [9].

The <allow-emergency-private-call> element is of type Boolean, as specified in table 8.3.2.7-13, and corresponds to the "Authorised" element of clause 5.2.27 in 3GPP TS 24.483 [4].

Table 8.3.2.7-13: Values of <allow-emergency-private-call>

"true"	instructs the MCPTT server performing the originating participating MCPTT function for the MCPTT user, that the MCPTT user is authorised to request an emergency private call using the procedures defined in 3GPP TS 24.379 [9].
"false"	instructs the MCPTT server performing the originating participating MCPTT function for the MCPTT user, that the MCPTT user is not authorised to request an emergency private call using the procedures defined in 3GPP TS 24.379 [9].

The <allow-cancel-group-emergency> element is of type Boolean, as specified in table 8.3.2.7-14, and corresponds to the "CancelMCPTTGroup" element of clause 5.2.35 in 3GPP TS 24.483 [4].

Table 8.3.2.7-14: Values of <allow-cancel-group-emergency>

"true"	instructs the MCPTT server performing the originating participating MCPTT function for the MCPTT user, that the MCPTT user is authorised to cancel an emergency group call using the procedures defined in 3GPP TS 24.379 [9].
"false"	instructs the MCPTT server performing the originating participating MCPTT function for the MCPTT user, that the MCPTT user is not authorised to cancel an emergency group call using the procedures defined in 3GPP TS 24.379 [9].

The <allow-cancel-private-emergency-call> element is of type Boolean, as specified in table 8.3.2.7-15, and corresponds to the "CancelPriority" element of clause 5.2.28 in 3GPP TS 24.483 [4].

Table 8.3.2.7-15: Values of <allow-cancel-private-emergency-call>

"true"	instructs the MCPTT server performing the originating participating MCPTT function for the MCPTT user, that the MCPTT user is authorised to cancel an emergency priority in an emergency private call using the procedures defined in 3GPP TS 24.379 [9].
"false"	instructs the MCPTT server performing the originating participating MCPTT function for the MCPTT user, that the MCPTT user is not authorised to cancel an emergency priority in an emergency private call using the procedures defined in 3GPP TS 24.379 [9].

The <allow-imminent-peril-call> element is of type Boolean, as specified in table 8.3.2.7-16, and corresponds to the "Authorised" element of clause 5.2.37 in 3GPP TS 24.483 [4].

Table 8.3.2.7-16: Values of <allow-imminent-peril-call>

"true"	instructs the MCPTT server performing the originating participating MCPTT function for the MCPTT user, that the MCPTT user is authorised to request an imminent peril group call using the procedures defined in 3GPP TS 24.379 [9].
"false"	instructs the MCPTT server performing the originating participating MCPTT function for the MCPTT user, that the MCPTT user is not authorised to request an imminent peril group call using the procedures defined in 3GPP TS 24.379 [9].

The <allow-cancel-imminent-peril> element is of type Boolean, as specified in table 8.3.2.7-17, and corresponds to the "Cancel" element of clause 5.2.38 in 3GPP TS 24.483 [4].

Table 8.3.2.7-17: Values of <allow-cancel-imminent-peril>

"true"	instructs the MCPTT server performing the originating participating MCPTT function for the MCPTT user, that the MCPTT user is authorised to cancel an imminent peril group call using the procedures defined in 3GPP TS 24.379 [9].
"false"	instructs the MCPTT server performing the originating participating MCPTT function for the MCPTT user, that the MCPTT user is not authorised to cancel an imminent peril group call using the procedures defined in 3GPP TS 24.379 [9].

The <allow-activate-emergency-alert> element is of type Boolean, as specified in table 8.3.2.7-18, and corresponds to the "Authorised" element of clause 5.2.41 in 3GPP TS 24.483 [4].

Table 8.3.2.7-18: Values of <allow-activate-emergency-alert>

"true"	instructs the MCPTT server performing the originating participating MCPTT function for the MCPTT user, that the MCPTT user is authorised to activate an emergency alert using the procedures defined in 3GPP TS 24.379 [9].
"false"	instructs the MCPTT server performing the originating participating MCPTT function for the MCPTT user, that the MCPTT user is not authorised to activate an emergency alert using the procedures defined in 3GPP TS 24.379 [9].

The <allow-cancel-emergency-alert> element is of type Boolean, as specified in table 8.3.2.7-19, and corresponds to the "Cancel" element of clause 5.2.42 in 3GPP TS 24.483 [4].

Table 8.3.2.7-19: Values of <allow-cancel-emergency-alert>

"true"	instructs the MCPTT server performing the originating participating MCPTT function for the MCPTT user, that the MCPTT user is authorised to cancel an emergency alert using the procedures defined in 3GPP TS 24.379 [9].
"false"	instructs the MCPTT server performing the originating participating MCPTT function for the MCPTT user, that the MCPTT user is not authorised to cancel an emergency alert using the procedures defined in 3GPP TS 24.379 [9].

The <allow-offnetwork> element is of type Boolean, as specified in table 8.3.2.7-20, and corresponds to the "Authorised" element of clause 5.2.50 in 3GPP TS 24.483 [4].

Table 8.3.2.7-20: Values of <allow-offnetwork>

"true"	instructs the MCPTT server performing the originating participating MCPTT function for the MCPTT user, that the MCPTT user is authorised for off-network operation using the procedures defined in 3GPP TS 24.379 [9].
"false"	instructs the MCPTT server performing the originating participating MCPTT function for the MCPTT user, that the MCPTT user is not authorised for off-network operation using the procedures defined in 3GPP TS 24.379 [9].

The <allow-imminent-peril-change> element is of type Boolean, as specified in table 8.3.2.7-21, and corresponds to the "ImminentPerilCallChange" element of clause 5.2.57 in 3GPP TS 24.483 [4].

Table 8.3.2.7-21: Values of <allow-imminent-peril-change>

"true"	instructs the MCPTT server performing the originating participating MCPTT function for the MCPTT user, that the MCPTT user is authorised to change an off-network MCPTT group call in-progress to an off-network imminent peril group call using the procedures defined in 3GPP TS 24.379 [9]. The default value for the <allow-imminent-peril-change> element is "true"
"false"	instructs the MCPTT server performing the originating participating MCPTT function for the MCPTT user, that the MCPTT user is not authorised to change an off-network MCPTT group call in-progress to an off-network imminent peril group call using the proceduresdefined in 3GPP TS 24.379 [9].

The <allow-private-call-media-protection> element is of type Boolean, as specified in table 8.3.2.7-22, and corresponds to the "AllowedMediaProtection" element of clause 5.2.24 in 3GPP 24.483 [4];

Table 8.3.2.7-22: Values of <allow-private-call-media-protection>

"true"	instructs the MCPTT server performing the originating participating MCPTT function for the MCPTT user, that the MCPTT user is authorised to protect the confidentiality and integrity of media for on-network and off-network private calls. The default value for the <allow-private-call-media-protection> element is "true".
"false"	instructs the MCPTT server performing the originating participating MCPTT function for the MCPTT user, that the MCPTT user is not authorised to protect the confidentiality and integrity of media for on-network and off-network private calls.

The <allow-private-call-floor-control-protection> element is of type Boolean, as specified in table 8.3.2.7-23, and corresponds to the "AllowedFloorControlProtection" element of clause 5.2.25 in 3GPP 24.483 [4];

Table 8.3.2.7-23: Values of <allow-private-call-floor-control-protection>

"true"	instructs the MCPTT server performing the originating participating MCPTT function for the MCPTT user, that the MCPTT user is authorised to protect the confidentiality and integrity of floor control signalling for both on-network and off-network private calls
"false"	instructs the MCPTT server performing the originating participating MCPTT function for the MCPTT user, that the MCPTT user is not authorised to protect the confidentiality and integrity of floor control signalling for both on-network and off-network private calls

The <allow-request-affiliated-groups> element is of type Boolean, as specified in table 8.3.2.7-24, and does not appear in the user profile configuration managed object specified in 3GPP TS 24.483 [4].

Table 8.3.2.7-24: Values of <allow-request-affiliated-groups>

"true"	Indicates that the MCPTT user is authorised to request the list of MCPTT groups to which a specified MCPTT user is affiliated.
"false"	Indicates that the MCPTT user is not authorised to request the list of MCPTT groups to which the a specified MCPTT user is affiliated.

The <allow-request-to-affiliate-other-users> element is of type Boolean, as specified in table 8.3.2.7-25, and does not appear in the MCPTT user profile configuration managed object specified in 3GPP TS 24.483 [4].

Table 8.3.2.7-25: Values of <allow-request-to-affiliate-other-users>

"true"	Indicates that the MCPTT user is authorised to request specified MCPTT user(s) to be affiliated to/deaffiliated from specified MCPTT group(s).
"false"	Indicates that the MCPTT user is not authorised to request specified MCPTT user(s) to be affiliated to/deaffiliated from specified MCPTT group(s).

The <allow-recommend-to-affiliate-other-users> element is of type Boolean, as specified in table 8.3.2.7-26, and does not appear in the MCPTT user profile configuration managed object specified in 3GPP TS 24.483 [4].

Table 8.3.2.7-26: Values of <allow-recommend-to-affiliate-other-users>

"true"	Instructs the MCPTT server performing the originating participating MCPTT function for the MCPTT user, that the MCPTT user is authorised to recommend to specified MCPTT user(s) to affiliate to specified MCPTT group(s).
"false"	instructs the MCPTT server performing the originating participating MCPTT function for the MCPTT user, that the MCPTT user is not authorised to recommend tospecified MCPTT user(s) to affiliate to specified MCPTT group(s).

The <allow-private-call-to-any-user> element is of type Boolean, as specified in table 8.3.2.7-27, and corresponds to the "AuthorisedAny" element of clause 5.2.14 in 3GPP TS 24.483 [4].

Table 8.3.2.7-27: Values of <allow-private-call-to-any-user>

"true"	instructs the MCPTT server performing the originating participating MCPTT function for the MCPTT user, that the MCPTT user is authorised to request a private call request using the procedures defined in 3GPP TS 24.379 [9]. The recipient is not constrained to MCPTT users identified in <entry> elements of the <PrivateCall> element i.e., to any MCPTT users.
"false"	instructs the MCPTT server performing the originating participating MCPTT function for the MCPTT user, to reject private call requests using the procedures defined in 3GPP TS 24.379 [9]. This shall be the default value taken in the absence of the element;

The <allow-regroup> element is of type Boolean, as specified in table 8.3.2.7-28, and corresponds to the "AllowedRegroup" element of clause 5.2.48D in 3GPP TS 24.483 [4].

Table 8.3.2.7-28: Values of <allow-regroup>

"true"	instructs the MCPTT server performing the originating participating MCPTT function for the MCPTT user, that the MCPTT user is locally authorised to send a dynamic regrouping request according to the procedures defined in 3GPP TS 24.481 [5].
"false"	instructs the MCPTT server performing the participating MCPTT function for the MCPTT user, that the MCPTT user is not locally authorised to send a dynamic regrouping request according to the procedures defined in 3GPP TS 24.481 [5].

The <allow-private-call-participation> element is of type Boolean, as specified in table 8.3.2.7-29, and corresponds to the "EnabledParticipation" element of clause 5.2.48G in 3GPP TS 24.483 [4].

Table 8.3.2.7-29: Values of <allow-private-call-participation>

"true"	instructs the MCPTT server performing the terminating participating MCPTT function for the MCPTT user, that the MCPTT user is authorised to participate in private calls that they are invited to using the procedures defined in 3GPP TS 24.379 [9].
"false"	instructs the MCPTT server performing the terminating participating MCPTT function for the MCPTT user, that the MCPTT user to reject private call requests that they are invited to using the procedures defined in 3GPP TS 24.379 [9].

The <allow-override-of-transmission> element is of type Boolean, as specified in table 8.3.2.7-30, and corresponds to the "AllowedTransmission" element of clause 5.2.48H in 3GPP TS 24.483 [4].

Table 8.3.2.7-30: Values of <allow-override-of-transmission>

"true"	instructs the MCPTT server performing the participating MCPTT function for the MCPTT user, that the MCPTT user is authorised to override transmission in a private call.
"false"	instructs the MCPTT server performing the participating MCPTT function for the MCPTT user, that the MCPTT user is not authorised to override transmission in a private call

The <allow-manual-off-network-switch> element is of type Boolean, as specified in table 8.3.2.7-31, and corresponds to the "AllowedManualSwitch" element of clause 5.2.48I in 3GPP TS 24.483 [4].

Table 8.3.2.7-31: Values of <allow-manual-off-network-switch>

"true"	instructs the MCPTT server performing the participating MCPTT function for the MCPTT user, that the MCPTT user is authorised to manually switch to off-network operation while in on-network operation using the procedures defined in 3GPP TS 24.379 [9].
"false"	instructs the MCPTT server performing the participating MCPTT function for the MCPTT user, that the MCPTT user is not authorised to manually switch to off-network operation while in on-network operation using the procedures defined in 3GPP TS 24.379 [9].

The <allow-listen-both-overriding-and-overridden> element is of type Boolean, as specified in table 8.3.2.7-32, and corresponds to the "AllowedListen" element of clause 5.2.54 in 3GPP TS 24.483 [4].

Table 8.3.2.7-32: Values of <allow-listen-both-overriding-and-overridden>

"true"	Indicates that the MCPTT user is allowed to listen both overriding and overriden transmissions during off-network operation.
"false"	Indicates that the MCPTT user is not allowed to listen both overriding and overriden transmissions during off-network operation.

The <allow-transmit-during-override> element is of type Boolean, as specified in table 8.3.2.7-33, and corresponds to the "AllowedTransmission" element of clause 5.2.55 in 3GPP TS 24.483 [4].

Table 8.3.2.7-33: Values of <allow-transmit-during-override>

"true"	Indicates that the MCPTT user is allowed to transmit in case of override (overriding and/or overridden).during off-network operation.
"false"	Indicates that the MCPTT user is not allowed to transmit in case of override (overriding and/or overridden).during off-network operation.

The <allow-off-network-group-call-change-to-emergency> element is of type Boolean, as specified in table 8.3.2.7-34, and corresponds to the "EmergencyCallChange" element of clause 5.2.56 in 3GPP TS 24.483 [4].

Table 8.3.2.7-34: Values of <allow-off-network-group-call-change-to-emergency>

"true"	Indicates that the MCPTT user is allowed to to change an off-network group call in-progress to an off-network MCPTT emergency group call.
"false"	Indicates that the MCPTT user is not allowed to change an off-network group call in-progress to an off-network MCPTT emergency group call.

The <allow-revoke-transmit> element is of type Boolean, as specified in table 8.3.2.7-35, and does not appear in the MCPTT user profile configuration managed object specified in 3GPP TS 24.483 [4].

Table 8.3.2.7-35: Values of <allow-revoke-transmit>

"true"	instructs the MCPTT server performing the participating MCPTT function for the MCPTT user, that the MCPTT user is authorised to revoke the permission to transmit of another participant.
"false"	instructs the MCPTT server performing the participating MCPTT function for the MCPTT user, that the MCPTT user is not authorised to revoke the permission to transmit of another participant.

The <allow-create-group-broadcast-group> element is of type Boolean, as specified in table 8.3.2.7-36, and corresponds to the "Authorised" element of clause 5.2.46 in 3GPP TS 24.483 [4].

Table 8.3.2.7-36: Values of <allow-create-group-broadcast-group>

"true"	indicates that the MCPTT user is locally authorised to send a request to create a group-broadcast group according to the procedures of 3GPP TS 24.481 [5].
"false"	Indicates that the MCPTT user is not locally authorised to send a request to create a group-broadcast group according to the procedures of 3GPP TS 24.481 [5].

The <allow-create-user-broadcast-group> element is of type Boolean, as specified in table 8.3.2.7-37, and corresponds to the "Authorised" element of clause 5.2.48 in 3GPP TS 24.483 [4].

Table 8.3.2.7-37: Values of <allow-create-user-broadcast-group>

"true"	indicates that the MCPTT user is locally authorised to send a request to create a user-broadcast group according to the procedures of 3GPP TS 24.481 [5].
"false"	Indicates that the MCPTT user is not locally authorised to send a request to create a user-broadcast group according to the procedures of 3GPP TS 24.481 [5].

The <allow-request-private-call-call-back> element is of type Boolean, as specified in table 8.3.2.7-38, and corresponds to the "AllowedCallBackRequest" element of clause 5.2.48P in 3GPP TS 24.483 [4].

Table 8.3.2.7-38: Values of <allow-request-private-call-call-back>

"true"	indicates that the MCPTT user is authorised to request a private call call-back using the procedures defined in 3GPP TS 24.379 [9].
"false"	indicatesthat the MCPTT user is not authorised to request a private call call-back using the procedures defined in 3GPP TS 24.379 [9].

The <allow-cancel-private-call-call-back > element is of type Boolean, as specified in table 8.3.2.7-39, and corresponds to the "AllowedCallBackCancelRequest" element of clause 5.2.48Q in 3GPP TS 24.483 [4].

Table 8.3.2.7-39: Values of <allow-cancel-private-call-call-back>

"true"	indicates that the MCPTT user is authorised to cancel a private call call-back cancel using the procedures defined in 3GPP TS 24.379 [9].
"false"	indicates that the MCPTT user is not authorised to cancel a private call call-back using the procedures defined in 3GPP TS 24.379 [9].

The <allow-request-remote-initiated-ambient-listening> element is of type Boolean, as specified in table 8.3.2.7-40, and corresponds to the "AllowedRemoteInitiatedAmbientListening" element of clause 5.2.48R in 3GPP TS 24.483 [4].

Table 8.3.2.7-40: Values of <allow-request-remote-initiated-ambient-listening>

"true"	indicates that the MCPTT user is authorised to request a remote initiated ambient listening call using the procedures defined in 3GPP TS 24.379 [9].
"false"	indicates that the MCPTT user is not authorised to request a remote initiated ambient listening call using the procedures defined in 3GPP TS 24.379 [9].

The <allow-request-locally-initiated-ambient-listening> element is of type Boolean, as specified in table 8.3.2.7-41, and corresponds to the "AllowedLocallyInitiatedAmbientListening" element of clause 5.2.48S in 3GPP TS 24.483 [4].

Table 8.3.2.7-41: Values of <allow-request-locally-initiated-ambient-listening>

"true"	indicates that the MCPTT user is authorised to request a locally initiated ambient listening call using the procedures defined in 3GPP TS 24.379 [9].
"false"	indicates that the MCPTT user is not authorised to request a locally initiated ambient listening call using the procedures defined in 3GPP TS 24.379 [9].

The <allow-request-first-to-answer-call> element is of type Boolean, as specified in table 8.3.2.7-42, and corresponds to the "AllowedRequestFirstToAnswerCall" element of clause 5.2.48T in 3GPP TS 24.483 [4].

Table 8.3.2.7-42: Values of <allow-request-first-to-answer-call>

"true"	indicates that the MCPTT user is authorised to request a first-to-answer call using the procedures defined in 3GPP TS 24.379 [9].
"false"	indicates that the MCPTT user is not authorised to request a first-to-answer call using the procedures defined in 3GPP TS 24.379 [9].

The <allow-request-remote-init-private-call> element is of type Boolean, as specified in table 8.3.2.7-43, and corresponds to the "AllowedRequestRemoteInitPrivateCall" element of clause 5.2.48W1 in 3GPP TS 24.483 [4].

Table 8.3.2.7-43: Values of <allow-request-remote-init-private-call>

"true"	instructs the MCPTT server performing the participating MCPTT function for the MCPTT user, that the MCPTT user is authorised to request a remotely initiated private call using the procedures defined in 3GPP TS 24.379 [9].
"false"	instructs the MCPTT server performing the participating MCPTT function for the MCPTT user, that the MCPTT user is not authorised to request a remotely initiated private call using the procedures defined in 3GPP TS 24.379 [9].

The <allow-request-remote-init-group-call> element is of type Boolean, as specified in table 8.3.2.7-44, and corresponds to the "AllowedRequestRemoteInitGroupCall" element of clause 5.2.48W2 in 3GPP TS 24.483 [4].

Table 8.3.2.7-44: Values of <allow-request-remote-init-group-call>

"true"	instructs the MCPTT server performing the participating MCPTT function for the MCPTT user, that the MCPTT user is authorised to request a remotely initiated group call using the procedures defined in 3GPP TS 24.379 [9].
"false"	instructs the MCPTT server performing the participating MCPTT function for the MCPTT user, that the MCPTT user is not authorised to request a remotely initiated group call using the procedures defined in 3GPP TS 24.379 [9].

The <allow-query-functional-alias-other-user> element is of type Boolean, as specified in table 8.3.2.7-45, and corresponds to the "AllowedQueryFunctionalAliasOtherUser" element of clause 5.2.48W8 in 3GPP TS 24.483 [4].

Table 8.3.2.7-45: Values of <allow-query-functional-alias-other-user>

"true"	instructs the MCPTT server performing the participating MCPTT function for the MCPTT user, that the MCPTT user is authorised to query the functional alias(es) activated by another MCPTT user using the procedures defined in 3GPP TS 24.379 [9].
"false"	instructs the MCPTT server performing the participating MCPTT function for the MCPTT user, that the MCPTT user is not authorised to query the functional alias(es) activated by another MCPTT user using the procedures defined in 3GPP TS 24.379 [9].

The <allow-takeover-functional-alias-other-user> element is of type Boolean, as specified in table 8.3.2.7-46, and corresponds to the "AllowedTakeoverFunctionalAliasOtherUser" element of clause 5.2.48W9 in 3GPP TS 24.483 [4].

Table 8.3.2.7-46: Values of <allow-takeover-functional-alias-other-user>

"true"	instructs the MCPTT server performing the participating MCPTT function for the MCPTT user, that the MCPTT user is authorised to take over the functional alias(es) previously activated by another MCPTT user using the procedures defined in 3GPP TS 24.379 [9].
"false"	instructs the MCPTT server performing the participating MCPTT function for the MCPTT user, that the MCPTT user is not authorised to take over the functional alias(es) previously activated by another MCPTT user using the procedures defined in 3GPP TS 24.379 [9].

The <allow-location-info-when-talking> element is of type Boolean, as specified in table 8.3.2.7-47, and corresponds to the "AllowedLocationInfoWhenTalking" element of clause 5.2.48W10 in 3GPP TS 24.483 [4].

Table 8.3.2.7-47: Values of <allow-location-info-when-talking>

"true"

instructs the MCPTT user that it is authorised to send its location information on the signalling it uses to request the floor on a call;

instructs the MCPTT server performing the participating MCPTT function for the MCPTT user that the location information for the MCPTT user is authorised to be sent to the MCPTT server performing the controlling MCPTT function for the call;

instructs the MCPTT server performing the controlling MCPTT function for the call that it is authorised to send the location information for the MCPTT user, when the MCPTT user is talking, to other MCPTT users.

"false"

instructs the MCPTT user that it is not authorised to send its location information on the signalling it uses to request the floor on a call;

instructs the MCPTT server performing the participating MCPTT function for the MCPTT user that the location information for the MCPTT user is not authorised to be sent to the MCPTT server performing the controlling MCPTT function for the call;

instructs the MCPTT server performing the controlling MCPTT function for the call that it is not authorised to send the location information for the MCPTT user, when the MCPTT user is talking, to other MCPTT users on the call.

The <allow-to-receive-private-call-from-any-user> element is of type Boolean, as specified in table 8.3.2.7-28, and corresponds to the "AuthorisedIncomingAny" element of clause 5.2.48X in 3GPP TS 24.483 [4].

Table 8.3.2.7-48: Values of <allow-to-receive-private-call-from-any-user>

"true"	instructs the MCPTT server performing the terminating participating MCPTT function for the MCPTT user, that the MCPTT user is authorised to receive a private call request using the procedures defined in 3GPP TS 24.379 [9]. The recipient is not constrained to be called by MCPTT users identified in <entry> elements of the <IncomingPrivateCallList> element i.e., by any MCPTT user.
"false"	instructs the MCPTT server performing the terminating participating MCPTT function for the MCPTT user, to reject private call requests using the procedures defined in 3GPP TS 24.379 [9]. This shall be the default value taken in the absence of the element;

The <allow-to-receive-non-acknowledged-users-information> element is of type Boolean, as specified in table 8.3.2.7-49, and corresponds to the "AuthorisedReceiveNonAcknowledged" element of clause 5.2.48Z in 3GPP TS 24.483 [4].

Table 8.3.2.7-49: Values of <allow-to-receive-non-acknowledged-users-information>

"true"	instructs the MCPTT server performing the controlling MCPTT function for the MCPTT user, that the MCPTT user is authorised to receive information of all the users that did not acknowledge an invitation to a group call, and were affiliated and marked with the <on-network-required> on the group document.
"false"	instructs the MCPTT server performing the controlling MCPTT function for the MCPTT user, that the MCPTT user is not authorised to receive information of the users that did not acknowledge an invitation to a group call, and were affiliated and marked with the <on-network-required> on the group document.

The <allow-call-transfer> element is of type Boolean, as specified in table 8.3.2.7-50, and corresponds to the "AllowedCallTransfer" element of clause 5.2.48T1 in 3GPP TS 24.483 [4].

Table 8.3.2.7-50: Values of <allow-call-transfer>

"true"	instructs the MCPTT server performing the originating participating MCPTT function for the MCPTT user, that the MCPTT user is authorised to request a transfer of a private call using the procedures defined in 3GPP TS 24.379 [9].
"false"	instructs the MCPTT server performing the originating participating MCPTT function for the MCPTT user, to reject call transfer requests of private calls using the procedures defined in 3GPP TS 24.379 [9]. This shall be the default value taken in the absence of the element;

The <allow-call-transfer-to-any-user> element is of type Boolean, as specified in table 8.3.2.7-51, and corresponds to the "AllowedCallTransferAny" element of clause 5.2.48T2 in 3GPP TS 24.483 [4].

Table 8.3.2.7-51: Values of <allow-call-transfer-to-any-user>

"true"

instructs the MCPTT server performing the originating participating MCPTT function for the MCPTT user, that the MCPTT user is authorised to request the transfer of a private call to any user using the procedures defined in 3GPP TS 24.379 [9]. For call transfers to MCPTT IDs, the target is not constrained to be identified in <entry> elements of the <AllowedTargetMCPTTIDList> element, and for call transfers to functional aliases the target is not constrained to be identified in <entry> elements of the <AllowedTargetFunctionalAliasIDList> element i.e., to any MCPTT user.

"false"

instructs the MCPTT server performing the originating participating MCPTT function for the MCPTT user, to reject private call transfer requests to target users that are not present as entry elements in the lists of allowed targets for private call transfers (<AllowedTargetMCPTTIDList>/<AllowedTargetFunctionalAliasIDList>) using the procedures defined in 3GPP TS 24.379 [9]. This shall be the default value taken in the absence of the element;

The <allow-call-forwarding> element is of type Boolean, as specified in table 8.3.2.7-52, and does not appear in the MCPTT user profile configuration managed object specified in 3GPP TS 24.483 [4].

Table 8.3.2.7-52: Values of <allow-call-forwarding>

"true"	instructs the MCPTT server performing the terminating participating MCPTT function for the MCPTT user, that the MCPTT user is authorised to request forwarding immediate and no answer of a private call using the procedures defined in 3GPP TS 24.379 [9].
"false"	instructs the MCPTT server performing the terminating participating MCPTT function for the MCPTT user, to reject call forwarding immediate and no answer of private calls using the procedures defined in 3GPP TS 24.379 [9]. This shall be the default value taken in the absence of the element;

The <call-forwarding-on> element is of type Boolean, as specified in table 8.3.2.7-53, and does not appear in the MCPTT user profile configuration managed object specified in 3GPP TS 24.483 [4].

Table 8.3.2.7-53: Values of <call-forwarding-on>

"true"	instructs the MCPTT server performing the terminating participating MCPTT function for the MCPTT user, that the MCPTT user has forwarding immediate or call forwarding no answer of private calls using the procedures defined in 3GPP TS 24.379 [9] enabled.
"false"	instructs the MCPTT server performing the terminating participating MCPTT function for the MCPTT user, that the MCPTT user has call forwarding immediate or call forwarding no answer of private calls using the procedures defined in 3GPP TS 24.379 [9] disabled. This shall be the default value taken in the absence of the element;

The <forward-to-functional-alias> element is of type Boolean, as specified in table 8.3.2.7-54, and does not appear in the MCPTT user profile configuration managed object specified in 3GPP TS 24.483 [4].

Table 8.3.2.7-54: Values of <forward-to-functional-alias>

"true"	indicates that the target of the private call forwarding is a functional alias using the procedures defined in 3GPP TS 24.379 [9].
"false"	indicates that the target of the private call forwarding is a MCPTT ID using the procedures defined in 3GPP TS 24.379 [9]. This shall be the default value taken in the absence of the element;

The <allow-call-forward-manual-input> element is of type Boolean, as specified in table 8.3.2.7-55, and corresponds to the "AllowedCallForwardManualInput" element of clause 5.2.48T3 in 3GPP TS 24.483 [4].

Table 8.3.2.7-55: Values of <allow-call-forward-manual-input>

"true"	instructs the MCPTT server performing the originating participating MCPTT function for the MCPTT user, that the MCPTT user is authorised to request call forwarding based on manual user input of a private call to any MCPTT user using the procedures defined in 3GPP TS 24.379 [9].
"false"	instructs the MCPTT server performing the originating participating MCPTT function for the MCPTT user, to reject private call forwarding based on manual user input requests to any MCPTT user;

The <allow-functional-alias-binding-with-group> element is of type Boolean, as specified in table 8.3.2.7-56, and corresponds to the "AllowedFunctionalAliasGroupBinding" element of clause 5.2.48W11 in 3GPP TS 24.483 [4].

Table 8.3.2.7-56: Values of <allow-functional-alias-binding-with-group>

"true"	instructs the originating participating MCPTT function, serving the MCPTT user, that the MCPTT user is authorised to request the binding of a particular functional alias with a group or list of groups using the procedures defined in 3GPP TS 24.379 [9].
"false"	instructs the originating participating MCPTT function, serving the MCPTT user, that the MCPTT user is not authorised to request the binding of a particular functional alias with a group or list of groups and reject such requests using the procedures defined in 3GPP TS 24.379 [9].

8.3.2.8 Naming Conventions

The name of user profile configuration document shall be in the format of a static "mcptt-user-profile"- string concatenated with the value of <user-profile-index> attribute and including ".xml" filetype. For instance, "mcptt-user-profile-9.xml" is the user profile document name for a profile with the index value of 9.

8.3.2.9 Global documents

The present document requires no global documents.

8.3.2.10 Resource interdependencies

This Application Usage is interdependent on user profile data in the MCPTT Database and the MCPTT Management Object.

8.3.2.11 Access Permissions Policies

The authorization and access policies for a user profile configuration document shall conform to those described in OMA OMA-TS-XDM_Core-V2_1-20120403-A [2] clause 5.1.5 "Authorization"and clause 5.6.7 "Access Permissions Document" with the following exceptions:

1) The Principal (i.e., the user) of the user profile configuration document shall have permission to create, modify, or delete <alias-entry> child elements of the <UserAlias> elements, if the rule of the Access Permissions document associated with the user profile configuration document contains the action element <allow-any-operation-own-data>, as specified in OMA OMA-TS-XDM_Core-V2_1-20120403-A [2] clause 5.6.7 "Access Permissions Document".

8.3.2.12 Subscription to Changes

The User Access Policy Application Usage shall support subscription to changes as specified in clause 6.3.13.3.

MCPTT user profile configuration documents are kept as XDM collections. Therefore, it is possible to subscribe to all MCPTT user profile configuration documents of a MCPTT user according to XCAP URI construction convention of a trailing ‘/’, as specified in IETF RFC 5875 [11].

8.4 MCPTT service configuration document

8.4.1 General

The MCPTT service configuration document is specified in this clause. The MCPTT service configuration document content is based on requirements of Annex A.5 of 3GPP TS 23.379 [8], and structure and procedures of OMA OMA-TS-XDM_Core-V2_1-20120403-A [2]. The usage of an MCPTT service configuration in the MCPTT service is described in 3GPP TS 24.379 [9] and 3GPP TS 24.380 [10]. The schema definition is provided in clause 8.4.2.3. Each mission critical organization is configured with an MCPTT service configuration document.

8.4.2 Coding

8.4.2.1 Structure

The 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 <min-length-alias> element;

2) may contain a <broadcast-group> element containing:

a) a <num-levels-group-hierarchy> element; and

b) a <num-levels-user-hierarchy> element;

The <on-network> element:

1) may contain a <emergency-call> element containing:

a) a <private-cancel-timeout> element; and

b) a <group-time-limit> element.

2) may contain a <private-call> element containing:

a) a <hang-time> element;

b) a <max-duration-with-floor-control> element; and

c) a <max-duration-without-floor-control> element;

3) may contain a <num-levels-hierarchy> element;

4) may contain a <transmit-time> element containing:

a) a <time-limit> element; and

b) a <time-warning> element;

5) may contain a <hang-time-warning> element;

6) may contain a <floor-control-queue> element containing:

a) a <depth> element; and

b) a <max-user-request-time> element; and

7) shall contain a <fc-timers-counters> element containing:

a) a <T1-end-of-rtp-media> element;

b) a <T3-stop-talking-grace> element;

c) a <T7-floor-idle> element;

d) a <T8-floor-revoke> element;

e) a <T11-end-of-RTP-dual> element;

f) a <T12-stop-talking-dual> element;

g) a <T15-conversation> element;

h) a <T16-map-group-to-bearer> element;

i) a <T17-unmap-group-to-bearer> element;

j) a <T20-floor-granted> element;

k) a <T55-connect> element;

l) a<T56-disconnect> element;

m) a <C7-floor-idle> element;

n) a <C17-unmap-group-to-bearer> element;

o) a <C20-floor-granted> element;

p) a <C55-connect> element; and

q) a <C56-disconnect> element;

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

a) a <confidentiality-protection> element; and

b) an <integrity-protection> element;

9) shall include one <emergency-resource-priority> element containing:

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

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

10) shall include one <imminent-peril-resource-priority> element containing:

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

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

11) shall include one <normal-resource-priority> element containing:

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

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

12) may contain a <protection-between-mcptt-servers> element containing:

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

b) an <allow-floor-control-protection> element; and

13) may contain an <anyExt> element containing:

a) 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 <mcptt-user-list> element; and

v) may contain an <anyExt> element containing a <functional-alias-priority> element; and

b) a <max-simultaneous-authorizations> element; and

c) a <max-immediate-forwardings> element.

The <off-network> element:

1) may contain a <emergency-call> element containing:

a) a <private-cancel-timeout> element; and

b) a <group-time-limit> element.

2) may contain a <private-call> element containing:

a) a <hang-time> element; and

b) a <max-duration-with-floor-control> element;

3) may contain a <num-levels-hierarchy> element;

4) may contain a <transmit-time> element containing:

a) a <time-limit> element; and

b) a <time-warning> element.

5) may contain a <hang-time-warning> element;

6) may contain a <default-prose-per-packet-priority> element; and

7) may contain a <allow-log-metadata> element.

8.4.2.2 Application Unique ID

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

8.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:mcpttServiceConfig:1.0"

xmlns:mcpttsc="urn:3gpp:ns:mcpttServiceConfig: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="mcpttsc: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="mcpttsc:service-configuration-params-Type" minOccurs="0"/>

<xs:element name="anyExt" type="mcpttsc: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="mcpttsc:commonType" minOccurs="0" maxOccurs="unbounded"/>

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

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

<xs:element name="anyExt" type="mcpttsc: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="min-length-alias" type="xs:unsignedShort" minOccurs="0"/>

<xs:element name="broadcast-group" type="mcpttsc:broadcast-groupType" minOccurs="0"/>

<xs:element name="anyExt" type="mcpttsc: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="emergency-call" type="mcpttsc:emergency-callType" minOccurs="0"/>

<xs:element name="private-call" type="mcpttsc:private-callType" minOccurs="0"/>

<xs:element name="num-levels-priority-hierarchy" type="mcpttsc:priorityhierarchyType" minOccurs="0"/>

<xs:element name="transmit-time" type="mcpttsc:transmit-timeType" minOccurs="0"/>

<xs:element name="hang-time-warning" type="xs:duration" minOccurs="0"/>

<xs:element name="floor-control-queue" type="mcpttsc:floor-control-queueType" minOccurs="0"/>

<xs:element name="fc-timers-counters" type="mcpttsc:fc-timers-countersType"/>

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

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

<xs:element name="emergency-resource-priority" type="mcpttsc:resource-priorityType"/>

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

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

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

<xs:sequence>

<xs:element name="emergency-call" type="mcpttsc:emergency-callType" minOccurs="0"/>

<xs:element name="private-call" type="mcpttsc:private-callType" minOccurs="0"/>

<xs:element name="num-levels-priority-hierarchy" type="mcpttsc:priorityhierarchyType" minOccurs="0"/>

<xs:element name="transmit-time" type="mcpttsc:transmit-timeType" minOccurs="0"/>

<xs:element name="hang-time-warning" type="xs:duration" minOccurs="0"/>

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

<xs:element name="allow-log-metadata" type="xs:boolean" minOccurs="0"/>

<xs:element name="anyExt" type="mcpttsc: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="private-callType">

<xs:sequence>

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

<xs:element name="max-duration-with-floor-control" type="xs:duration" minOccurs="0"/>

<xs:element name="max-duration-without-floor-control" type="xs:duration" minOccurs="0"/>

<xs:element name="anyExt" type="mcpttsc: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="broadcast-groupType">

<xs:sequence>

<xs:element name="num-levels-group-hierarchy" type="xs:unsignedShort" minOccurs="0"/>

<xs:element name="num-levels-user-hierarchy" type="xs:unsignedShort" minOccurs="0"/>

<xs:element name="anyExt" type="mcpttsc: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="fc-timers-countersType">

<xs:sequence>

<xs:element name="T1-end-of-rtp-media" type="xs:duration"/>

<xs:element name="T3-stop-talking-grace" type="xs:duration"/>

<xs:element name="T7-floor-idle" type="xs:duration"/>

<xs:element name="T8-floor-revoke" type="xs:duration"/>

<xs:element name="T11-end-of-RTP-dual" type="xs:duration"/>

<xs:element name="T12-stop-talking-dual" type="xs:duration"/>

<xs:element name="T15-conversation" type="xs:duration"/>

<xs:element name="T16-map-group-to-bearer" type="xs:duration"/>

<xs:element name="T17-unmap-group-to-bearer" type="xs:duration"/>

<xs:element name="T20-floor-granted" type="xs:duration"/>

<xs:element name="T55-connect" type="xs:duration"/>

<xs:element name="T56-disconnect" type="xs:duration"/>

<xs:element name="C7-floor-idle" type="xs:unsignedShort"/>

<xs:element name="C17-unmap-group-to-bearer" type="xs:unsignedShort"/>

<xs:element name="C20-floor-granted" type="xs:unsignedShort"/>

<xs:element name="C55-connect" type="xs:unsignedShort"/>

<xs:element name="C56-disconnect" type="xs:unsignedShort"/>

<xs:element name="anyExt" type="mcpttsc: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="emergency-callType">

<xs:sequence>

<xs:element name="private-cancel-timeout" type="xs:duration" minOccurs="0"/>

<xs:element name="group-time-limit" type="xs:duration" minOccurs="0"/>

<xs:element name="anyExt" type="mcpttsc: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="transmit-timeType">

<xs:sequence>

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

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

<xs:element name="anyExt" type="mcpttsc: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="floor-control-queueType">

<xs:sequence>

<xs:element name="depth" type="xs:unsignedShort" minOccurs="0"/>

<xs:element name="max-user-request-time" type="xs:duration" minOccurs="0"/>

<xs:element name="anyExt" type="mcpttsc: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="mcptt-private-call-signalling" type="xs:unsignedShort" minOccurs="0"/>

<xs:element name="mcptt-private-call-media" type="xs:unsignedShort" minOccurs="0"/>

<xs:element name="mcptt-emergency-private-call-signalling" type="xs:unsignedShort" minOccurs="0"/>

<xs:element name="mcptt-emergency-private-call-media" type="xs:unsignedShort" minOccurs="0"/>

<xs:element name="anyExt" type="mcpttsc: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="mcpttsc: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="allow-floor-control-protection" type="xs:boolean" minOccurs="0" default="true"/>

<xs:element name="anyExt" type="mcpttsc: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="mcpttsc:anyExtType" minOccurs="0"/>

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

</xs:sequence>

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

</xs:complexType>

<!– simple type for priority element –>

<xs:simpleType name="priorityhierarchyType">

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

<xs:minInclusive value="4"/>

<xs:maxInclusive value="256"/>

</xs:restriction>

</xs:simpleType>

<xs:element name="functional-alias-list" type="mcpttsc:functional-alias-listType"/>

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

<xs:sequence>

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

<xs:element name="anyExt" type="mcpttsc: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="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="mcptt-user-list" type="mcpttsc:ListEntryType"/>

<xs:element name="anyExt" type="mcpttsc: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-priority" type="xs:positiveInteger"/>

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

<xs:element name="max-immediate-forwardings" type="xs:positiveInteger"/>

<xs:complexType name="ListEntryType">

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

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

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

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

</xs:choice>

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

<xs:attributeGroup ref="mcpttsc: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="mcpttsc:DisplayNameElementType" minOccurs="0"/>

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

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

</xs:sequence>

<xs:attributeGroup ref="mcpttsc: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>

8.4.2.4 Default Document Namespace

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

8.4.2.5 MIME type

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

8.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 8.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".

The service configuration document shall conform to the XML Schema described in clause 8.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 <mcptt-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".

The value of the <min-length-alias> element in the <common> element refers to variable N3 defined in Annex A of 3GPP TS 22.179 [3] and contains a value between 0 and 255.

If the <min-length-alias> element of the <common> element contains a value greater than 255, 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".

The value of the <num-levels-group-hierarchy> element in the <broadcast-group> element refers to variable B1 defined in Annex A of 3GPP TS 22.179 [3].

The value of the <num-levels-user-hierarchy> element in the <broadcast-group> element refers to variable B2 defined in Annex A of 3GPP TS 22.179 [3].

The value of the <min-length-alias>, the <num-levels-group-hierarchy> element, the <num-levels-user-hierarchy> element or the <depth> element do not contain a semantically valid value, 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 <off-network> element contains a <private-call> element with a <max-duration-without-floor-control> element, it shall be ignored.

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].

The "resource-priority-priority" element contained in the "normal-resource-priority" element shall have a value that is a priority level specified in IETF RFC 8101 [20].

NOTE 3: 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 MCPTT operator and the network operator.

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

1) <hang-time>;

2) <hang-time-warning>;

3) <max-duration-with-floor-control>;

4) <max-duration-without-floor-control>;

5) <private-cancel-timeout>;

6) <group-time-limit>;

7) <max-user-request-time>;

8) <time-limit>;

9) <time-warning>;

10) <T1-end-of-rtp-media>;

11) <T3-stop-talking-grace>;

12) <T7-floor-idle>;

13) <T8-floor-revoke>;

14) <T11-end-of-RTP-dual>;

15) <T12-stop-talking-dual>;

16) <T15-conversation>;

17) <T16-map-group-to-bearer>;

18) <T17-unmap-group-to-bearer>;

19) <T20-floor-granted>;

20) <T55-connect>; and

21) <T56-disconnect>.

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.

NOTE 4: "xs:duration" allows the use of decimal notion for seconds, e.g. 300ms is represented as <PT0.3S>.

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".

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 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".

8.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 <min-length-alias> element contains the minimum length (N3) of alphanumeric names assigned to MCPTT users by the MCPTT administrator, which corresponds to the "MinLengthAliasID" element as specified in clause 7.2.9 of 3GPP TS 24.483 [4];

2) the <num-levels-group-hierarchy> element of the <broadcast-group> element contains an integer indicating the number levels of group hierarchy for group-broadcast groups, which corresponds to the "NumLevelGroupHierarchy" element as specified in clause 7.2.7 of 3GPP TS 24.483 [4]; and

3) the <num-levels-user-hierarchy> element of the <broadcast-group> element contains an integer indicating the number levels of user hierarchy for user-broadcast groups, which corresponds to the "NumLevelUserHierarchy" element as specified in clause 7.2.8 of 3GPP TS 24.483 [4];

In the <on-network> element:

1) the <private-cancel-timeout> element of the <emergency-call> element contains the timeout value for the cancellation of an in-progress on-network emergency private call;

2) the <group-time-limit> element of the <emergency-call> element contains the time limit for an in-progress on-network emergency call on an MCPTT group;

3) the <hang-time> element of the <private-call> element contains the value of the hang timer for on-network private calls;

NOTE 1: The hang time is a configurable maximum length of the inactivity (silence) period between consecutive MCPTT transmissions within the same call.

4) the <max-duration-with-floor-control> element of the <private-call> element contains the maximum duration allowed for an on-network private call with floor control;

5) the <max-duration-without-floor-control > element of the <private-call> element contains the maximum duration allowed for an on-network private call without floor control;

6) the <num-levels-priority-hierarchy> element contains a priority hierarchy for determining what participants, participant types, and urgent transmission types shall be granted a request to override an active on-network MCPTT transmission. Absence of the <num-levels-priority-hierarchy> element in the <on-network> element indicates that the lowest possible value is used according to the schema, to represent the priority hierarchy;

NOTE 2: The higher the value from the priority hierarchy assigned to a participant, the higher the priority given to override an active transmission.

7) the <time-limit> element of the <transmit-time> element contains the transmit time limit in an on-network group or private call transmission;

8) the <time-warning> element of the <transmit-time> element contains the warning time before the on-network transmit time is reached;

9) the <hang-time-warning> element contains the warning time before the on-network hang time is reached;

10) the <depth> element of the <floor-control-queue> element contains the maximum size of the floor control queue;

11) the <max-user-request-time> element of the <floor-control-queue> element contains the maximum time for a user’s floor control request to be queued;

12) the <T1-end-of-rtp-media> element of the <fc-timers-counters> element contains the maximum allowed time between RTP media packets;

13) the <T3-stop-talking-grace> element of the <fc-timers-counters> element contains the maximum time the floor control server shall forward RTP media packets after that the permission to send RTP media is revoked;

14) the <T7-floor-idle> element of the <fc-timers-counters> element contains the retransmission interval of the Floor Idle message when the floor is idle. The maximum number of times the Floor Idle is retransmitted is controlled by the counter in the <C7-floor-idle> element;

15) the <T8-floor-revoke> element of the <fc-timers-counters> element contains the retransmission interval time of the Floor Revoke message until the Floor Release message is received;

16) the <T11-end-of-RTP-dual> element of the <fc-timers-counters> element contains the maximum allowed time between RTP media packets for the interrupting participant during dual floor operations;

17) the <T12-stop-talking-dual> element of the <fc-timers-counters> element contains the transmit time limit in an on-network group for the interrupting participant during dual floor operations;

18) the <T15-conversation> element of the <fc-timers-counters> element contains the maximum allowed time of silence in a group session involving an MBMS bearer before the MBMS subchannel shall be released;

19) the <T16-map-group-to-bearer> element of the <fc-timers-counters> element contains the retransmission interval of the Map Group To Bearer message;

20) the <T17-unmap-group-to-bearer> element of the <fc-timers-counters> element contains the retransmission interval of the Unmap Group To Bearer message;

21) the <T20-floor-granted> element of the <fc-timers-counters> element contains the time the floor control server shall wait before retransmitting the Floor Granted message until the Floor Request message is received. The number of times the Floor Granted message shall be sent is controlled by the counter in <C20-floor-granted> element;

22) the <T55-connect> element of the <fc-timers-counters> element contains the retransmission interval of the Connect message. The number of times the Connect message is retransmitted is controlled by the counter in <C56-disconnect> element;

23) the <T56-disconnect> element of the <fc-timers-counters> element contains the retransmission interval of the Disconnect message. The number of times the Disconnect message is retransmitted is controlled by the counter in <C55-connect> element;

24) the <C7-floor-idle> element of the <fc-timers-counters> element contains the maximum number of times the Floor Idle shall be sent;

25) the <C17-unmap-group-to-bearer> element of the <fc-timers-counters> element contains the retransmission interval of the Unmap Group To Bearer message;

26) the <C20-floor-granted> element of the <fc-timers-counters> element contains the maximum times the Floor Granted message shall be retransmitted.

27) the <C55-connect> element of the <fc-timers-counters> element contains the maximum number of times the Connect message is retransmitted;

28) the <C56-disconnect> element of the <fc-timers-counters> element contains the maximum number of times the Disconnect message is retransmitted;

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

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

31) The <emergency-resource-priority> element is of type "resource-priorityType" and indicates how a Resource-Priority header field is to be populated for MCPTT emergency calls;

32) The <imminent-peril-resource-priority> element is of type "resource-priorityType" and indicates how a Resource-Priority header field is to be populated for MCPTT Imminent Peril calls;

33) The <normal-resource-priority> 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 MCPTT emergency call or MCPTT imminent peril call;

34) the <allow-signalling-protection> element of the <protection-between-mcptt-servers> element contains a boolean indicating whether protection of MCPTT signalling is enabled between MCPTT servers; and

35) the <allow-floor-control-protection> element of the <protection-between-mcptt-servers> element contains a boolean indicating whether protection of MCPTT floor control signalling is enabled between MCPTT servers;

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

37) the <max-simultaneous-activations> element of the <functional-alias-entry> element of the <functional-alias-list> element of the <anyExt> 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;

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

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

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

NOTE 3: The usage of this parameter by the MCPTT server is up to implementation.

41) 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 MCPTT user.

NOTE 4: 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".

42) the <max-immediate-forwardings> element of the <anyExt> element is of type "positiveInteger" and indicates the maximum allowed number of immediate call forwardings.

In the <off-network> element:

1) the <private-cancel-timeout> element of the <emergency-call> element contains the timeout value for the cancellation of an in-progress off-network emergency private call, which corresponds to the "CancelTimeout" element as specified in clause 7.2.14 of 3GPP TS 24.483 [4];

2) the <group-time-limit> element of the <emergency-call> element contains the time limit for an in-progress off-network emergency call on an MCPTT group, which corresponds to the "MCPTTGroupTimeout" element as specified in clause 7.2.16 of 3GPP TS 24.483 [4];

3) the <hang-time> element of the <private-call> element contains the value of the hang timer for off-network private calls, which corresponds to the "HangTime" element as specified in clause 7.2.13 of 3GPP TS 24.483 [4];

4) the <max-duration-with-floor-control> element of the <private-call> element contains the maximum duration allowed for an off-network private call with floor control, which and corresponds to the "MaxDuration" element as specified in clause 7.2.12 of 3GPP TS 24.483 [4];

5) the <num-levels-priority-hierarchy> element contains a priority hierarchy for determining what participants, participant types, and urgent transmission types shall be granted a request to override an active off-network MCPTT transmission, which corresponds to the "NumLevelHierarchy" element as specified in clause 7.2.17 of 3GPP TS 24.483 [4]. Absence of the <num-levels-priority-hierarchy> element in the <off-network> element indicates that the lowest possible value is used according to the schema to represent the priority hierarchy;

NOTE 4: The higher the value from the priority hierarchy assigned to a participant, the higher the priority given to override an active transmission;

6) the <time-limit> element of the <transmit-time> element contains the transmit time limit in an off-network group or private call transmission, which corresponds to the "TransmitTimeout" element as specified in clause 7.2.18 of 3GPP TS 24.483 [4];

7) the <time-warning> element of the <transmit-time> element contains the warning time before the off-network transmit time is reached, which corresponds to the "TransmissionWarning" element as specified in clause 7.2.19 of 3GPP TS 24.483 [4];

8) the <hang-time-warning> element contains the warning time before the off-network hang time is reached, which corresponds to the "HangTimeWarning" element as specified in clause 7.2.20 of 3GPP TS 24.483 [4];

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

a) mcptt private call signalling which corresponds to the "MCPTTPrivateCallSignalling" element as specified in clause 7.2.22 of 3GPP TS 24.483 [4];

b) mcptt private call media which corresponds to the "MCPTTPrivateCallMedia" element as specified in clause 7.2.23 of 3GPP TS 24.483 [4];

c) mcptt emergency private call signalling which corresponds to the "MCPTTEmergencyPrivateCallSignalling" element as specified in clause 7.2.24 of 3GPP TS 24.483 [4]; and

d) mcptt emergency private call media which corresponds to the "MCPTTEmergencyPrivateCallMedia" element as specified in clause 7.2.25 of 3GPP TS 24.483 [4]; and

10) the <allow-log-metadata> element which corresponds to the "LogMetadata" element as specified in clause 7.2.26 of 3GPP TS 24.483 [4] and contains one of the following values:

a) "true" which indicates that logging of metadata for MCPTT group calls, MCPTT private calls and non-call activities from MCPTT UEs operating in off-network mode, is enabled; and

b) "false" which indicates that logging of metadata for MCPTT group calls, MCPTT private calls and non-call activities from MCPTT UEs operating in off-network mode, is not enabled.

8.4.2.8 Naming Conventions

The service configuration document name is called service-config.xml.

8.4.2.9 Global documents

The 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 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.mcptt.service-config/global/service-config.xml

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

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

Since the 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.

8.4.2.10 Resource interdependencies

There are no resource interdependencies.

8.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".

8.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.