9 MCVideo configuration management documents

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

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

9.1 Introduction

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

MCVideo UE configuration document;

MCVideo user profile configuration document; and

MCVideo service configuration document.

9.2 MCVideo UE configuration document

9.2.1 General

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

MCVideo UE configuration documents of a MCVideo 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 MCVideo ID, as the user has been already authenticated. A MCVideo UE configuration document corresponding to a specific MCVideo UE the MCVideo user has used to authenticate and is authorised to use the MCVideo service with is placed in the user directory of the MCVideo user.

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

9.2.1A MCVideo client access to MCVideo UE configuration documents

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

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

CMSXCAPROOTURI/org.3gpp.mcvideo.ue-config/users/sip:MCVIDEOID/MCSUEID

9.2.2 Coding

9.2.2.1 Structure

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

The <mcvideo-UE-configuration> document:

1) shall include a "domain" attribute;

2) may include a <mcvideo-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 an <MCVideo-Private-Call> element containing:

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

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

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

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

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

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

1) an <MCVideo-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-MCVideo-Group> elements containing:

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

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

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

The <mcvideo-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.

9.2.2.2 Application Unique ID

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

9.2.2.3 XML Schema

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

<xs:schema xmlns:mcvideouep="urn:3gpp:mcvideo:mcvideoUEConfig:1.0"

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

targetNamespace="urn:3gpp:mcvideo:mcvideoUEConfig: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="mcvideo-UE-configuration">

<xs:complexType>

<xs:sequence>

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

<xs:element name="mcvideo-UE-id" type="mcvideouep:MCVIDEOUEIDType"/>

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

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

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

</xs:choice>

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

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

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

<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="mcvideouep:IndexType"/>

</xs:extension>

</xs:simpleContent>

</xs:complexType>

<xs:complexType name="MCVIDEOUEIDType">

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

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

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

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

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

</xs:choice>

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

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

</xs:complexType>

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

<xs:sequence>

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

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

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

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

</xs:choice>

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

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

</xs:sequence>

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

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

</xs:complexType>

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

<xs:sequence>

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

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

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

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

</xs:sequence>

<xs:attributeGroup ref="mcvideouep: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="mcvideouep:tac-baseType">

<xs:attributeGroup ref="mcvideouep: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="mcvideouep:snr-baseType">

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

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

</xs:extension>

</xs:simpleContent>

</xs:complexType>

<xs:complexType name="CommonType">

<xs:sequence>

<xs:element name="MCVIDEO-Private-Call">

<xs:complexType>

<xs:sequence>

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

</xs:sequence>

</xs:complexType>

</xs:element>

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

<xs:complexType>

<xs:sequence>

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

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

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

<xs:complexType>

<xs:sequence>

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

<xs:complexType>

<xs:sequence>

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

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

</xs:sequence>

</xs:complexType>

</xs:element>

</xs:sequence>

</xs:complexType>

</xs:element>

</xs:sequence>

</xs:complexType>

</xs:element>

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

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

</xs:sequence>

<xs:attributeGroup ref="mcvideouep: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-MCVIDEO-Group" type="mcvideouep:Relayed-MCVIDEO-GroupType"/>

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

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

</xs:sequence>

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

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

</xs:complexType>

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

<xs:sequence>

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

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

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

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

</xs:sequence>

</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>

9.2.2.4 Default Document Namespace

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

9.2.2.5 MIME type

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

9.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 9.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 MCVideo UE configuration document shall conform to the XML Schema described in clause 9.2.2.3.

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

The <mcvideo-UE-configuration> element shall contain either:

1) one <common> element only;

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

3) one <on-network> element only.

If the <mcvideo-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 <mcvideo-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-Nc10> element of the <MCVideo-Private-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 <Max-Simul-Call-Nc4> element, or <Max-Simul-Trans-Nc5> element of the <MCVideo-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 <MCVideo-Group-ID> element of the <MCVideo-group-priority> element or <Relayed-MCVideo-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 <MCVideo-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-MCVideo-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".

9.2.2.7 Data Semantics

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

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

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

If one or more optional <Instance-ID-URN> elements is included in the <mcvideo-UE-id> element then the MCVideo UE configuration document applies to the MCVideo 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 MCVideo UE.

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

If an optional <SNR-range> element is included within the <IMEI-range> element then the MCVideo UE configuration document applies to all MCVideo 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 MCVideo UE configuration document applies to all the MCVideo UE(s) with the Type Allocation Code contained within the <TAC> element of the <IMEI-range> element.

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

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

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

In the <common> element:

1) the <Max-Simul-Call-Nc10> element of the <MCVideo-Private-Call> element contains an integer indicating the number of simultaneous calls (N10) allowed for an on-network or off-network private call and corresponds to the "MaxCallNc10" element of clause 12.2.5B in 3GPP TS 24.483 [4];

2) the <Max-Simul-Call-Nc4> element of the <MCVideo-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 "MaxCallNc4" element of clause 12.2.7 in 3GPP TS 24.483 [4];

3) the <Max-Simul-Trans-Nc5> element of the <MCVideo-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 "MaxTransmissionNc5" element of clause 12.2.8 in 3GPP TS 24.483 [4]; and

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

a) <MCVideo-Group-ID> element identifying an MCVideo group that corresponds to the "MCVideoGroupID" element of clause 12.2.11 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 MCVideo group with 0 being the lowest priority and 7 being the highest priority and corresponds to the "MCVideoGroupPriorityHierarchy" element of clause 12.2.12 in 3GPP TS 24.483 [4].

In the <on-network> element:

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

2) an <IPv6Preferred> element which corresponds to the "IPv6Preferred" element of clause 12.2.15 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-MCVideo-Groups> element of the <Relay-Service> element which corresponds to the "RelayedMCVideoGroup" element of clause 12.2.16 in 3GPP TS 24.483 [4] contains:

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

i) "MCVideo-Group-ID" attribute identifying an MCVideo group that is allowed to be used via a relay and corresponds to the "MCVideoGroupID" element of clause 12.2.18 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 12.2.19 in 3GPP TS 24.483 [4].

9.2.2.8 Naming Conventions

The present document defines no naming conventions.

9.2.2.9 Global documents

The present document requires no global documents.

9.2.2.10 Resource interdependencies

There are no resource interdependencies.

9.2.2.11 Authorization Policies

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

9.2.2.12 Subscription to Changes

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

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

9.3 MCVideo user profile configuration document

9.3.1 General

The MCVideo user profile configuration document is specified in this clause. The MCVideo user profile configuration document content is based on requirements of Annex A.3 of 3GPP TS 23.281 [27], and structure and procedures of OMA OMA-TS-XDM_Core-V2_1-20120403-A [2]. In this case, the term "user" in the XCAP sense refers to the MCVideo ID, as the user has been already authenticated. The usage of an MCVideo user profile in the MCVideo service is described in 3GPP TS 24.281 [28]. The schema definition is provided in clause 9.3.2.

MCVideo 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].

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

9.3.1A MCVideo client access to MCVideo user profile documents

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

CMSXCAPROOTURI/org.3gpp.mcvideo.user-profile/users/sip:MCVIDEOID/mcvideo-user-profile-INDEX.xml

Where INDEX is the index of the MCVideo user profile as defined in clause 9.3.2.8.

9.3.2 Coding

9.3.2.1 Structure

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

The <mcvideo-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 <MCVideoUserID> element that contains a <uri-entry> element;

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

i) a <PrivateCallList> element that contains:

A) zero or more <PrivateCallOnNetwork> elements that each contain:

I) a <PrivateCallURI> element than contains an <entry> element; and

II) a <PrivateCallKMSURI> element that contains an <entry> element; and

B) zero or more <PrivateCallOffNetwork> elements that each contain:

I) a <PrivateCallProSeUser> element than contains a <DiscoveryGroupID> element and a <User‑Info‑ID> element; and

II) a <PrivateCallKMSURI> element that contains an <entry> element; and

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

A) an <entry> element; and

B) a <ProSeUserID-entry> element;

e) shall include one <MCVideo-group-call> element containing:

i) one <MaxSimultaneousCallsN6> element;

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

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

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

v) one <Priority> element;

f) may include one <ParticipantType> element;

g) shall include one <MissionCriticalOrganization> indicating the name of the mission critical organization the MCVideo User belongs to; and

h) may include an <anyExt> element;

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

a) shall have an "index" attribute;

b) shall include one or more <MCVideoGroupInfo> elements each containing:

i) an <MCVideo-Group-ID> element;

ii) an <GMS-Serv-Id> element;

iii) an <IdMS-Token-Endpoint> element;

iv) one <RelativePresentationPriority> element; and

v) a <GroupKMSURI> element;

c) shall include one <MaxAffiliationsN2>element;

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

e) may include a <MaxSimultaneousVideoStreams> element

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

g) shall include one <RemoteGroupSelectionURIList> element, each containing one or more <entry> elements; and

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

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

ii) 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; and

iii) a <user-max-simultaneous-authorizations> element;

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

a) shall contain an "index" attribute;

b) shall include one or more <MCVideoGroupInfo> elements each containing:

i) one <MCVideo-Group-ID> element;

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

iii) one <IdMS-Token-Endpoint> element;

iv) one <RelativePresentationPriority> element; and

v) one <GroupKMSURI> element;

11) shall include 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]; and

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-request-affiliated-groups> element;

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

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

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

xxvii) an <allow-regroup> element;

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

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

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

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

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

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

xxxiv) an <anyExt> element which may contain:

A) an <allow-request-remote-initiated-ambient-viewing> element;

B) an <allow-request-locally-initiated-ambient-viewing> element;

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

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

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

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

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.

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.

9.3.2.2 Application Unique ID

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

9.3.2.3 XML Schema

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

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

<xs:schema

xmlns:mcvideoup="urn:3gpp:ns:mcvideo:user-profile:1.0"

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

targetNamespace="urn:3gpp:ns:mcvideo: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="mcvideo-user-profile">

<xs:complexType>

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

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

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

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

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

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

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

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

<xs:element name="anyExt" type="mcvideoup: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="mcvideoup:UserAliasType"/>

<xs:element name="MCVideoUserID" type="mcvideoup:EntryType"/>

<xs:element name="PrivateCall" type="mcvideoup:MCVideoPrivateCallType"/>

<xs:element name="MCVideo-group-call" type="mcvideoup:MCVideoGroupCallType"/>

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

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

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

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

</xs:choice>

<xs:attributeGroup ref="mcvideoup: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="mcvideoup:AliasEntryType"/>

<xs:element name="anyExt" type="mcvideoup: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="mcvideoup:IndexType"/>

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

</xs:extension>

</xs:simpleContent>

</xs:complexType>

<xs:complexType name="MCVideoPrivateCallType">

<xs:sequence>

<xs:element name="PrivateCallList" type="mcvideoup:PrivateCallListType"/>

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

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

<xs:sequence>

<xs:element name="PrivateCallOnNetwork" type="mcvideoup:PrivateCallOnNetworkType" minOccurs="0" maxOccurs="unbounded"/>

<xs:element name="PrivateCallOffNetwork" type="mcvideoup:PrivateCallOffNetworkType" minOccurs="0" maxOccurs="unbounded"/>

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

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

</xs:sequence>

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

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

</xs:complexType>

<xs:complexType name="PrivateCallOnNetworkType">

<xs:sequence>

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

<xs:element name="PrivateCallKMSURI" type="mcvideoup:PrivateCallKMSURIEntryType"/>

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

<xs:sequence>

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

<xs:element name="PrivateCallKMSURI" type="mcvideoup:PrivateCallKMSURIEntryType"/>

<xs:element name="anyExt" type="mcvideoup: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="mcvideoup:anyExtType" minOccurs="0"/>

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

</xs:sequence>

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

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

</xs:complexType>

<xs:complexType name="PrivateCallKMSURIEntryType">

<xs:sequence>

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

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

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

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

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

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

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

<xs:element name="Priority" type="mcvideoup:PriorityType"/>

<xs:element name="anyExt" type="mcvideoup: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="MCVideoGroupInitiation" type="mcvideoup:MCVideoGroupInitiationEntryType"/>

<xs:element name="MCVideoPrivateRecipient" type="mcvideoup:MCVideoPrivateRecipientEntryType"/>

<xs:element name="anyExt" type="mcvideoup: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="MCVideoGroupInitiation" type="mcvideoup:MCVideoGroupInitiationEntryType"/>

<xs:element name="anyExt" type="mcvideoup: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="mcvideoup:EntryType"/>

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

<xs:choice>

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

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

<xs:sequence>

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

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

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

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

<xs:element name="MCVideoGroupInfo" type="mcvideoup:MCVideoGroupInfoType"/>

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

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

<xs:element name="MaxSimultaneousVideoStreams" type="xs:positiveInteger" minOccurs="0"/>

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

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

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

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

</xs:choice>

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

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

</xs:complexType>

<xs:complexType name="OffNetworkType">

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

<xs:element name="MCVideoGroupInfo" type="mcvideoup:MCVideoGroupInfoType"/>

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

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

</xs:choice>

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

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

</xs:complexType>

<xs:complexType name="MCVideoGroupInfoType">

<xs:sequence>

<xs:element name="MCVideo-Group-ID" type="mcvideoup:EntryType"/>

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

<xs:element name="IdMS-Token-Endpoint" type="mcvideoup:EntryType"/>

<xs:element name="RelativePresentationPriority" type="mcvideoup:PriorityType"/>

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

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

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

<xs:minInclusive value="0"/>

<xs:maxInclusive value="255"/>

</xs:restriction>

</xs:simpleType>

<xs:complexType name="ListEntryType">

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

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

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

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

</xs:choice>

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

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

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

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

</xs:sequence>

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

<xs:attributeGroup ref="mcvideoup: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:simpleType name="protectionType">

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

<xs:enumeration value="Normal"/>

<xs:enumeration value="Encrypted"/>

</xs:restriction>

</xs:simpleType>

<xs:complexType name="GeographicalAreaChangeType">

<xs:sequence>

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

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

<xs:element name="anyExt" type="mcvideoup: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="mcvideoup:PolygonAreaType" minOccurs="0"/>

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

<xs:element name="anyExt" type="mcvideoup: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="mcvideoup:PointCoordinateType" minOccurs="3" maxOccurs="15"/>

<xs:element name="anyExt" type="mcvideoup: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="mcvideoup: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="mcvideoup:anyExtType" minOccurs="0"/>

</xs:sequence>

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

</xs:complexType>

<xs:complexType name="PointCoordinateType">

<xs:sequence>

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

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

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

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

<xs:element name="threebytes" type="mcvideoup:tThreeByteType" minOccurs="0"/>

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

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

</xs:choice>

<xs:attribute name="type" type="mcvideoup:protectionType"/>

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

</xs:complexType>

<!– anyExt elements for "PointCoordinateType" –>

<xs:element name="altitude" type="mcvideoup:tCoordinateType2Bytes"/>

<xs:complexType name="tCoordinateType2Bytes">

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

<xs:element name="twobytes" type="mcvideoup:tTwoByteType" minOccurs="0"/>

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

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

</xs:choice>

<xs:attribute name="type" type="mcvideoup:protectionType"/>

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

</xs:complexType>

<xs:simpleType name="tThreeByteType">

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

<xs:minInclusive value="0"/>

<xs:maxInclusive value="16777215"/>

</xs:restriction>

</xs:simpleType>

<xs:simpleType name="tTwoByteType">

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

<xs:minInclusive value="-32768"/>

<xs:maxInclusive value="32767"/>

</xs:restriction>

</xs:simpleType>

<xs:complexType name="RulesForAffiliationManagementType">

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

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

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

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

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

</xs:choice>

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

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

</xs:sequence>

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

</xs:complexType>

<!– anyExt elements for Functional Alias–>

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

<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="MaxSimultaneousEmergencyGroupCalls" type="xs:positiveInteger"/>

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

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

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

<!– anyExt elements for Functional Alias for Location change–>

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

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

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

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

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

<!– anyExt elements for Functional Alias for Affiliation change–>

<!– Note: anyExt elements for Functional Alias for Affiliation change include speed and heading–>

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

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

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

<!– anyExt elements for Private call lists–>

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

<xs:complexType name="PrivateCallListEntryType">

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

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

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

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

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

</xs:choice>

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

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

</xs:complexType>

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

<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-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-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-manual-off-network-switch" 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="allow-request-remote-initiated-ambient-viewing" type="xs:boolean"/>

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

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

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

<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>

9.3.2.4 Default Document Namespace

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

9.3.2.5 MIME type

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

9.3.2.6 Validation Constraints

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

The value of the "XUI-URI" attribute of the <mcvideo-user-profile> element shall be the same as the XUI value of the Document URI for the MCVideo 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 MCVideo user profile configuration document shall comply with naming convention: mcvideo‑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: ‘mcvideo-user-profile-<profile-index>.xml’".

The value of the <RelativePresentationPriority> element of the <MCVideoGroupInfo> 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 <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 MCVideo user profile document is specified for the MCVideo user in the "XDM collections" in the user’s directory, then only one MCVideo user profile document shall contain the <Pre-selected-indication> element. If there is only one MCVideo user profile specified for the MCVideo user in the user’s directory, then it is optional to include the <Pre-selected-indication> element. If a MCVideo user profile document containing the <Pre-selected-indication> element already exists for the MCVideo 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 MCVideo user profile document that already contains the <Pre-selected-indication> element.

If the <allow-unlimited-video-streams> element is set to "true" and the MCVideo user profile contains a <MaxSimultaneousVideoStreams> element, then the value contained in the <MaxSimultaneousVideoStreams> element is ignored.

The value of the <ReceptionPriority> element of the <Common> 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 "ReceptionPriority value out of range".

9.3.2.7 Data Semantics

The <Name> element is of type "token" and corresponds to the "Name" element of clause 13.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 MCVideo user and corresponds to the leaf nodes of the "UserAlias" element of clause 13.2.13 in 3GPP TS 24.483 [4].

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

– <entry> element of the <MCVideoUserID> element of the <Common> element, contains the MCVideo user identity (MCVideo ID) of the MCVideo user, and corresponds to the "MCVideoUserID" element of clause 13.2.7 in 3GPP TS 24.483 [4];

– the <entry> element of the the <PrivateCallURI> element of the <PrivateCallOnNetwork> element of the <PrivateCallList> element of the <PrivateCall> list element indicates an MCVideo ID of an MCVideo user that the MCVideo user is authorised to initiate a private call to and corresponds to the "MCVideoID" element of clause 13.2.38I5 in 3GPP TS 24.483 [4];

– the <entry> element of the <MCVideoGroupInitiation> element of the <EmergencyCall> element of the <MCVideo-group-call> element indicates the MCVideo group used on initiation of an MCVideo emergency group call and corresponds to the "GroupID" element of the "MCVideoGroupInitiation" element of clause 13.2.38D3 in 3GPP TS 24.483 [4];

– the <entry> element of the <MCVideoGroupInitiation> element of the <ImminentPerilCall> element of the <MCVideo-group-call> element indicates the MCVideo group used on initiation of an MCVideo imminent peril group call and corresponds to the "GroupID" element of clause 13.2.38G3 in 3GPP TS 24.483 [4];

– the <entry> element of the <MCVideoPrivateRecipient> of the <EmergencyCall> element of the <PrivateCall> element indicates the recipient MCVideo user for an on-network MCVideo emergency private call and corresponds to the "ID" element of clause 13.2.38T in 3GPP TS 24.483 [4];

– the <entry> element of the <EmergencyAlert> element of the <MCVideo-group-call> element, indicates the MCVideo group for an on-network MCVideo emergency group alert and corresponds to the "ID" element of clause 13.2.38A5 in 3GPP TS 24.483 [4];

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

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

– the <GroupKMSURI> element of the <MCVideoGroupInfo> element of the <OnNetwork> element contains the URI used to contact the key management server associated with the MCVideo Group ID in the <MCVideo-Group-ID> element and corresponds to the "GroupKMSURI" element of clause 13.2.50D in 3GPP TS 24.483 [4]. If the entry element is empty, the KMS URI present in the MCS initial configuration document is used;

– the <GroupKMSURI> element of the <MCVideoGroupInfo> element of the <OffNetwork> element contains the URI used to contact the key management server associated with the MCVideo Group ID in the <MCVideo-Group-ID> element and corresponds to the "GroupKMSURI" element of clause 13.2.100C in 3GPP TS 24.483 [4]. If the entry element is empty, the KMS URI present in the MCS initial configuration document is used;

– the <entry> element of the <PrivateCallKMSURI> element of the <PrivateCallOnNetwork> element of the <PrivateCallList> element of the <PrivateCall> element of the <Common> element contains the URI used to contact the KMS associated with the MCVideo ID contained in the <PrivateCallURI> element of the same <PrivateCallOnNetwork> element of the <PrivateCallList> element of the <PrivateCall> element of the <Common> element and corresponds to the "PrivateCallKMSURI" element of clause 13.2.38I9 in 3GPP TS 24.483 [4]; If the entry element is empty, the KMS URI present in the MCS initial configuration document is used;

– the <entry> element of the <PrivateCallKMSURI> element of the <PrivateCallOffNetwork> element of the same <PrivateCallList> element of the <PrivateCall> element of the <Common> element contains the URI used to contact the KMS associated with the User-Info-ID contained in the <PrivateCallProSeUser> element of the same <PrivateCallOffNetwork> element of the <PrivateCallList> element of the <PrivateCall> element of the <Common> element and corresponds to the "PrivateCallKMSURI" element of clause 13.2.38I9 in 3GPP TS 24.483 [4]; If the entry element is empty, the KMS URI present in the MCS initial configuration document is used;

– the <MCVideo-Group-ID> element of the <MCVideoGroupInfo> element of the <OnNetwork> element contains the MCVideo group ID of an on-network MCVideo group for use by the configured MCVideo user, and corresponds to the "MCVideoGroupID" element of clause 13.2.43 in 3GPP TS 24.483 [4];

– the <MCVideo-Group-ID> element of the <MCVideoGroupInfo> element of the <OffNetwork> element contains the MCVideo group ID of an off-network MCVideo group for use by the configured MCVideo user, and corresponds to the "MCVideoGroupID" element of clause 13.2.93 in 3GPP TS 24.483 [4];

– the <GMS-Serv-Id> element of the <MCVideoGroupInfo> element of the <OnNetwork> element, contains the URI of the group management server hosting the on-network MCVideo group identified by the <MCVideo-Group-ID> element, and corresponds to the "GMSServId" element of clause 13.2.47 in 3GPP TS 24.483 [4];

– the <IdMS-Token-Endpoint> element of the <MCVideoGroupInfo> element of the <OnNetwork> element, contains the URI used to contact the identity management server token endpoint for the on-network MCVideo group identified by the <MCVideo-Group-ID> element, and corresponds to the "IdMSTokenEndPoint" element of clause 13.2.50 in 3GPP TS 24.483 [4]. If the entry element is empty, the idms-auth-endpoint and idms-token-endpoint present in the MCS UE initial configuration document are used;

– the <GMS-Serv-Id> element of the <MCVideoGroupInfo> element of the <OffNetwork> element, contains the URI of the group management server hosting the off-network MCVideo group identified by the <MCVideo-Group-ID> element, and corresponds to the "GMSServId" element of clause 13.2.97 in 3GPP TS 24.483 [4];

– the <IdMS-Token-Endpoint> element of the <MCVideoGroupInfo> element of the <OffNetwork> element, contains the URI used to contact the identity management server token endpoint for the off-network MCVideo group identified by the <MCVideo-Group-ID> element, and corresponds to the "IdMSTokenEndPoint" element of clause 13.2.100 in 3GPP TS 24.483 [4]. If the entry element is empty, the idms-auth-endpoint and idms-token-endpoint present in the MCS UE initial configuration document are used; and

– the <entry> element of the <ImplicitAffiliations> list element of the <OnNetwork> element indicates an MCVideo group ID of an MCVideo group that the MCVideo user is implicitly affiliated with, and corresponds to the "MCVideoGroupID" element of clause 13.2.55 in 3GPP TS 24.483 [4];

– the <entry> element of the <FunctionalAliasList> list element of the <anyExt> element of the <OnNetwork> element contains a functional alias that the MCVideo user is authorised to activate and corresponds to the "FunctionalAlias" element of clause 13.2.87A6 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 MCVideo 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 subclause 13.2.87A7E 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 MCVideo user is authorised to receive a call, if it has activated and is using the parent functional alias (see <FunctionalAliasList> element);

– the <PrivateCallURI> element of the <IncomingPrivateCallList> element of the <anyExt> element of the <OnNetwork> element indicates an MCVideo ID of an MCVideo user from whom the MCVideo user is authorised to receive a private call and corresponds to the "MCVideoID" element of clause 13.2.87C3 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 MCVideo 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 "MCVideoIDKMSURI" element of clause 13.2.87C4 in 3GPP TS 24.483 [4]; and

– 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 MCVideo IDs contained in the PrivateCallURI elements of the <IncomingPrivateCallList> element and corresponds to the "MCVideoIDKMSURI" element of clause 13.2.87C4 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 <display-name> element is of type "string", contains a human readable name and when it appears within:

– the <MCVideo-Group-ID> element of the <MCVideoGroupInfo> element of the <OnNetwork> element contains the name of an on-network MCVideo group for use by the configured MCVideo user, and corresponds to the "DisplayName" element of clause 13.2.44 in 3GPP TS 24.483 [4];

– the <MCVideo-Group-ID> element of the <MCVideoGroupInfo> element of the <OffNetwork> element contains the name of an off-network MCVideo group for use by the configured MCVideo user, and corresponds to the "DisplayName" element of clause 13.2.94 in 3GPP TS 24.483 [4];

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

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

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

– the <entry> element of the <MCVideoGroupInitiation> element of the <ImminentPerilCall> element of the <MCVideo-group-call> element indicates the name of the MCVideo group used on initiation of an MCVideo imminent peril group call and corresponds to the "DisplayName" element of clause 13.2.38G4 in 3GPP TS 24.483 [4];

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

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

– the <entry> element of the <PrivateCallURI> of the <PrivateCallList> element indicates the name of an MCVideo ID of an MCVideo user that the MCVideo user is authorised to initiate a private call to and corresponds to the "DisplayName" element of clause 13.2.38I8 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 MCVideo user profile is enabled or disabled and corresponds to the "Status" element of clause 13.2.103 in 3GPP TS 24.483 [4]. When set to "true" this MCVideo user profile is enabled. When set to "false" this MCVideo user profile is disabled.

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

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

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

The "XUI-URI" attribute is of type "anyURI" that contains the XUI of the MCVideo user for whom this MCVideo 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 MCVideo user (e.g., first responder, second responder, dispatch, dispatch supervisor). The <ParticipantType> element corresponds to the "ParticipantType" element of clause 13.2.15 in 3GPP TS 24.483 [4].

The <MissionCriticalOrganization> element of the <Common> element is of type "string" and indicates the name of the mission critical organization the MCVideo User belongs to. The <MissionCriticalOrganization> element corresponds to the "Organization" element of clause 13.2.16 in 3GPP TS 24.483 [4].

The <RelativePresentationPriority> element is of type "nonNegativeInteger" and when it appears in:

– the <MCVideoGroupInfo> 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 13.2.51 in 3GPP TS 24.483 [4];

– the <MCVideoGroupInfo> 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 13.2.101 in 3GPP TS 24.483 [4];

The <MaxAffiliationsN2> element is of type "nonNegativeInteger", and indicates the maximum number of MCVideo groups that the MCVideo user is authorised to affiliate with, and corresponds to the "MaxAffiliationsNc2" element of clause 13.2.67 in 3GPP TS 24.483 [4].

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

The <MaxSimultaneousVideoStreams> element of the <OnNetwork> element is of type "unsignedShort" and contains maximum number of simultaneous video streams that can be received by the MCVideo user, and corresponds to the "MaxStreams" element of clause 13.2.74 in 3GPP TS 24.483 [4].

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 MCVideo emergency group calls for the specific functional alias, and corresponds to the "MaxSimultaneousEmergencyGroupCalls" element of clause 13.2.87A7A in 3GPP TS 24.483 [4].

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 13.2.87A6A in 3GPP TS 24.483 [4] and consists of the following sub-elements:

– <EnterSpecificArea> element is of type "mcvideoup: 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) <anyExt> element containing a <Speed> element; and

d) <anyExt> element containing a <Heading> element.

– <ExitSpecificArea> element is of type "mcvideoup: 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 13.2.87A6B in 3GPP TS 24.483 [4] and consists of the following sub-elements:

– <EnterSpecificArea> element is of type "mcvideoup: 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 "mcvideoup: 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 13.2.87A6C in 3GPP TS 24.483 [4]. When set to "true" the MCVideo 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 <MCVideoGroupInfo> element of the <OnNetwork> element indicates upon a change in geographical area or a change in functional alias activation status to the MCVideo client to evaluate the rules. If for any rule any location criteria is fulfilled and any functional alias criteria is fulfilled the MCVideo client triggers the group affiliation. It corresponds to the "RulesForAffiliation" element of clause 13.2.43A in 3GPP TS 24.483 [4] and consists of the following sub-elements:

– <ListOfLocationCriteria> element is of type "mcvideoup: 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 "mcvideoup: 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) an <anyExt> optional element containing 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 13.2.43A19 in 3GPP TS 24.483 [4]; and

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 13.2.43A20 in 3GPP TS 24.483 [4]; and

iv) an <anyExt> optional element containing 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 "MinimumHeading" element of clause 13.2.43A22 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 "MaximumHeading" element of clause 13.2.43A23 in 3GPP TS 24.483 [4]; and

b) <ExitSpecificArea> element is of type "mcvideoup: 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 containg the <anyExt> element set to the functional alias whose activation or deactivation triggers evaluation of the rules and corresponds to the "FunctionalAlias" element of clause 13.2.43A47 in 3GPP TS 24.483 [4];

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

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

The <manual-deaffiliation-not-allowed-if-affiliation-rules-are-met> element within the <anyExt> element of the <entry> element within the <MCVideoGroupInfo> element of the <anyExt> element of the <OnNetwork> element is of type "Boolean" and corresponds to the "ManualDeaffiliationNotAllowedIfAffiliationRulesAreMet" element of clause 13.2.43C in 3GPP TS 24.483 [4]. When set to "true" the MCVideo user is not allowed to deaffiliate from the group if the rules for affiliation are met.

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

– the <ProSeUserID-entry> element of the <MCVideoPrivateRecipient> 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 MCVideo user for an MCVideo emergency private call and corresponds to the "UserInfoID" element of clause 13.2.38V in 3GPP TS 24.483 [4]; and

– 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 MCVideo user that the MCVideo user is authorised to initiate a private call to and corresponds to the "UserInfoID" element of clause 13.2.38I7 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 <MCVideoPrivateRecipient> element of the <EmergencyCall> element, it identifies the Discovery Group ID that the MCVideo UE uses to initiate an off-network MCVideo emergency private call and corresponds to the "DiscoveryGroupID" element of clause 13.2.38U in 3GPP TS 24.483 [4]; and

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

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

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

a) the MCVideo user currently selected MCVideo 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 <MCVideoGroupInitiation> 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 MCVideo user has no currently selected MCVideo group;

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

a) an MCVideo ID of an MCVideo user that is selected by the MCVideo 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 <MCVideoPrivateRecipient> 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 <MCVideoPrivateRecipient> for an off-network emergency private call, if the "entry-info"attribute has the value of ‘UsePreConfigured’;

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

a) the MCVideo user currently selected MCVideo 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 <MCVideoGroupInitiation> for an on-network imminent peril call, if the "entry-info" attribute has the value of:

i) ‘DedicatedGroup’; or

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

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

a) the MCVideo user currently selected MCVideo 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 MCVideo user has no currently selected MCVideo group.

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

a) the MCVideo ID of an MCVideo user that is selected by the MCVideo 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 MCVideo user has no currently selected MCVideo user.

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 MCVideo user.

The <allow-presence-status> element is of type Boolean, as specified in table 9.3.2.7-1, and corresponds to the "AllowedPresenceStatus" element of clause 13.2.69 in 3GPP TS 24.483 [4].

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Table Table 9.3.2.7-6: Values of <allow-private-call>

"true"	instructs the MCVideo server performing the originating participating MCVideo function for the MCVideo user, that the MCVideo user is authorised to request a private call request using the procedures defined in 3GPP TS 24.281 [28].
"false"	instructs the MCVideo server performing the originating participating MCVideo function for the MCVideo user, to reject private call request using the procedures defined in 3GPP TS 24.281 [28]. 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 9.3.2.7-7, and corresponds to the "ManualCommence" element of clause 13.2.38J in 3GPP TS 24.483 [4].

Table 9.3.2.7-7: Values of <allow-manual-commencement>

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

The <allow-automatic-commencement> element is of type Boolean, as specified in table 9.3.2.7-8, corresponds to the "AutoCommence" element of clause 13.2.38K in 3GPP TS 24.4283 [4].

Table 9.3.2.7-8: Values of <allow-automatic-commencement>

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

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

Table 9.3.2.7-9: Values of <allow-force-auto-answer>

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

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

Table 9.3.2.7-10: Values of <allow-failure-restriction>

"true"	instructs the MCVideo server performing the originating participating MCVideo function for the MCVideo user, that the MCVideo user is authorised to restrict the notification of a call failure reason for a private call using the procedures defined in 3GPP TS 24.281 [28].
"false"	instructs the MCVideo server performing the originating participating MCVideo function for the MCVideo user, that the MCVideo user is not authorised to restrict the notification of a call failure reason for a private call using the procedures defined in 3GPP TS 24.281 [28].

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

Table 9.3.2.7-11: Values of <allow-emergency-group-call>

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

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

Table 9.3.2.7-12: Values of <allow-emergency-private-call>

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

The <allow-cancel-group-emergency> element is of type Boolean, as specified in table 9.3.2.7-13, and corresponds to the "CancelMCVideoGroup" element of clause 13.2.38D in 3GPP TS 24.483 [4].

Table 9.3.2.7-13: Values of <allow-cancel-group-emergency>

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

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

Table 9.3.2.7-14: Values of <allow-cancel-private-emergency-call>

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

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

Table 9.3.2.7-15: Values of <allow-imminent-peril-call>

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

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

Table 9.3.2.7-16: Values of <allow-cancel-imminent-peril>

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

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

Table 9.3.2.7-17: Values of <allow-activate-emergency-alert>

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

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

Table 9.3.2.7-18: Values of <allow-cancel-emergency-alert>

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

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

Table 9.3.2.7-19: Values of <allow-offnetwork>

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

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

Table 9.3.2.7-20: Values of <allow-imminent-peril-change>

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

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

Table 9.3.2.7-21: Values of <allow-private-call-media-protection>

"true"	instructs the MCVideo server performing the originating participating MCVideo function for the MCVideo user, that the MCVideo 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 MCVideo server performing the originating participating MCVideo function for the MCVideo user, that the MCVideo user is not authorised to protect the confidentiality and integrity of media for on-network and off-network private calls.

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

Table 9.3.2.7-22: Values of <allow-request-affiliated-groups>

"true"	Instructs the MCVideo server performing the originating participating MCVideo function for the MCVideo user, that the MCVideo user is authorised to request the list of MCVideo groups to which a specified MCVideo user is affiliated.
"false"	Instructs the MCVideo server performing the originating participating MCVideo function for the MCVideo user, that the MCVideo user is not authorised to request the list of MCVideo groups to which the a specified MCVideo user is affiliated.

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

Table 9.3.2.7-23: Values of <allow-request-to-affiliate-other-users>

"true"	Instructs the MCVideo server performing the originating participating MCVideo function for the MCVideo user, that the MCVideo user is authorised to request specified MCVideo user(s) to be affiliated to/deaffiliated from specified MCVideo group(s).
"false"	instructs the MCVideo server performing the originating participating MCVideo function for the MCVideo user, that the MCVideo user is not authorised to request specified MCVideo user(s) to be affiliated to/deaffiliated from specified MCVideo group(s).

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

Table 9.3.2.7-24: Values of <allow-recommend-to-affiliate-other-users>

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

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

Table 9.3.2.7-25: Values of <allow-private-call-to-any-user>

"true"	instructs the MCVideo server performing the originating participating MCVideo function for the MCVideo user, that the MCVideo user is authorised to request a private call request using the procedures defined in 3GPP TS 24.281 [28]. The recipient is not constrained to MCVideo users identified in <entry> elements of the <PrivateCall> element i.e., to any MCVideo users.
"false"	instructs the MCVideo server performing the originating participating MCVideo function for the MCVideo user, to reject private call requests using the procedures defined in 3GPP TS 24.281 [28]. 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 9.3.2.7-26, and corresponds to the "AllowedRegroup" element of clause 13.2.68 in 3GPP TS 24.483 [4].

Table 9.3.2.7-26: Values of <allow-regroup>

"true"	instructs the MCVideo server performing the originating participating MCVideo function for the MCVideo user, that the MCVideo user is locally authorised to send a dynamic regrouping request according to the procedures defined in 3GPP TS 24.481 [5].
"false"	instructs the MCVideo server performing the participating MCVideo function for the MCVideo user, that the MCVideo 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 9.3.2.7-27, and corresponds to the "EnabledParticipation" element of clause 13.2.87A in 3GPP TS 24.483 [4].

Table 9.3.2.7-27: Values of <allow-private-call-participation>

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

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

Table 9.3.2.7-28: Values of <allow-manual-off-network-switch>

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

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

Table 9.3.2.7-29: Values of <allow-off-network-group-call-change-to-emergency>

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

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

Table 9.3.2.7-30: Values of <allow-revoke-transmit>

"true"	instructs the MCVideo server performing the participating MCVideo function for the MCVideo user, that the MCVideo user is authorised to revoke the permission to transmit of another participant.
"false"	instructs the MCVideo server performing the participating MCVideo function for the MCVideo user, that the MCVideo 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 9.3.2.7-31, and corresponds to the "Authorised" element of clause 13.2.18 in 3GPP TS 24.483 [4].

Table 9.3.2.7-31: Values of <allow-create-group-broadcast-group>

"true"	indicates that the MCVideo 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 MCVideo 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 9.3.2.7-32, and corresponds to the "Authorised" element of clause 13.2.20 in 3GPP TS 24.483 [4].

Table 9.3.2.7-32: Values of <allow-create-user-broadcast-group>

"true"	indicates that the MCVideo 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 MCVideo 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-remote-initiated-ambient-viewing> element is of type Boolean, as specified in table 9.3.2.7-33, and corresponds to the "AllowedRemoteInitiatedAmbientViewing" element of clause 13.2.87A1 in 3GPP TS 24.483 [4].

Table 9.3.2.7-33: Values of <allow-request-remote-initiated-ambient-viewing>

"true"	instructs the MCVideo server performing the controlling MCVideo function for the MCVideo user, that the MCVideo user is authorised to request a remote initiated ambient viewing call using the procedures defined in 3GPP TS 24.281 [28].
"false"	instructs the MCVideo server performing the controlling MCVideo function for the MCVideo user, that the MCVideo user is not authorised to request a remote initiated ambient viewing call using the procedures defined in 3GPP TS 24.281 [28].

The <allow-request-locally-initiated-ambient-viewing> element is of type Boolean, as specified in table 9.3.2.7-34, and corresponds to the "AllowedLocallyInitiatedAmbientViewing" element of clause 13.2.87A2 in 3GPP TS 24.483 [4].

Table 9.3.2.7-34: Values of <allow-request-locally-initiated-ambient-viewing>

"true"	instructs the MCVideo server performing the controlling MCVideo function for the MCVideo user, that the MCVideo user is authorised to request a locally initiated ambient viewing call using the procedures defined in 3GPP TS 24.281 [28].
"false"	instructs the MCVideo server performing the controlling MCVideo function for the MCVideo user, that the MCVideo user is not authorised to request a locally initiated ambient viewing call using the procedures defined in 3GPP TS 24.281 [28].

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

Table 9.3.2.7-35: Values of <allow-query-functional-alias-other-user>

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

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

Table 9.3.2.7-36: Values of <allow-takeover-functional-alias-other-user>

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

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

Table 9.3.2.7-37: Values of <allow-to-receive-private-call-from-any-user>

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

The <allow-functional-alias-binding-with-group> element is of type Boolean, as specified in table 9.3.2.7-37, and corresponds to the "AllowedFunctionalAliasGroupBinding" element of clause 13.2.87A10 in 3GPP TS 24.483 [4].

Table 9.3.2.7-37: Values of <allow-functional-alias-binding-with-group>

"true"	instructs the originating participating MCVideo function, serving the MCVideo user, that the MCVideo 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.281 [28].
"false"	instructs the originating participating MCVideo function, serving the MCVideo user, that the MCVideo 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.281 [28].

9.3.2.8 Naming Conventions

The name of user profile configuration document shall be in the format of a static "mcvideo-user-profile" string concatenated with the value of <user-profile-index> attribute and including ".xml" filetype. For instance, "mcvideo-user-profile-9.xml" is the user profile document name for an MCVideo user profile with the index value of 9.

9.3.2.9 Global documents

The present document requires no global documents.

9.3.2.10 Resource interdependencies

This Application Usage is interdependent on user profile data in the MCVideo Database and the MCVideo Management Object.

9.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".

9.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.

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

9.4 MCVideo service configuration document

9.4.1 General

The MCVideo service configuration document is specified in this clause. The MCVideo service configuration document content is based on requirements of Annex A.5 of 3GPP TS 23.281 [27], and structure and procedures of OMA OMA-TS-XDM_Core-V2_1-20120403-A [2]. The usage of an MCVideo service configuration in the MCVideo service is described in 3GPP TS 24.281 [28] and 3GPP TS 24.581 [29]. The schema definition is provided in clause 9.4.2.3. Each mission critical organization is configured with an MCVideo service configuration document.

9.4.2 Coding

9.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 <signalling-protection> element containing:

a) a <confidentiality-protection> element; and

b) an <integrity-protection> element;

2) may contain a <protection-between-mcvideo-servers> element containing:

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

b) an <allow-transmission-control-protection> element;

3) shall include one <emergency-resource-priority> element containing:

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

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

4) shall include one <imminent-peril-resource-priority> element containing:

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

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

5) shall include one <normal-resource-priority> element containing:

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

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

6) may contain an <anyExt> element containing:

a) a <functional-alias-list> element containing:

i) one or more <functional-alias-entry> elements each containing:

A) a <functional-alias> element;

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

C) an <allow-takeover> element;

D) an <mcvideo-user-list> element; and

E) a <functional-alias-priority> element ,and

b) a <max-simultaneous-authorizations> element.

The <off-network> element:

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

a) an <mcvideo-private-call-signalling> element;

b) an <mcvideo-private-call-media> element;

c) an <mcvideo-emergency-private-call-signalling> element; and

d) an <mcvideo-emergency-private-call-media> element; and

2) may contain a <private-call> element containing:

a) an <mcvideo-max-duration> element.

9.4.2.2 Application Unique ID

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

9.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:mcvideoServiceConfig:1.0"

xmlns:mcvideosc="urn:3gpp:ns:mcvideoServiceConfig: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="mcvideosc: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="mcvideosc:service-configuration-params-Type" minOccurs="0"/>

<xs:element name="anyExt" type="mcvideosc: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="mcvideosc:commonType" minOccurs="0" maxOccurs="unbounded"/>

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

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

<xs:element name="anyExt" type="mcvideosc: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="mcvideosc:broadcast-groupType" minOccurs="0"/>

<xs:element name="anyExt" type="mcvideosc: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="signalling-protection" type="mcvideosc:signalling-protectionType" minOccurs="0"/>

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

<xs:element name="emergency-resource-priority" type="mcvideosc:resource-priorityType"/>

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

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

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

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

</xs:sequence>

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

</xs:complexType>

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

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

<xs:sequence>

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

<xs:element name="private-call" type="mcvideosc:private-callType" minOccurs="0"/>

<xs:element name="num-levels-priority-hierarchy" type="mcvideosc:priorityhierarchyType" minOccurs="0"/>

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

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

</xs:sequence>

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

</xs:complexType>

<!– anyExt elements for on-network element to support functional alias –>

<xs:element name="functional-alias-list" type="mcvideosc:functional-alias-listType"/>

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

<xs:sequence>

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

<xs:element name="anyExt" type="mcvideosc: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="mcvideo-user-list" type="mcvideosc:ListEntryType"/>

<xs:element name="anyExt" type="mcvideosc: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:complexType name="ListEntryType">

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

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

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

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

</xs:choice>

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

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

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

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

</xs:sequence>

<xs:attributeGroup ref="mcvideosc: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="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="mcvideosc: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="mcvideo-private-call-signalling" type="xs:unsignedShort" minOccurs="0"/>

<xs:element name="mcvideo-private-call-media" type="xs:unsignedShort" minOccurs="0"/>

<xs:element name="mcvideo-emergency-private-call-signalling" type="xs:unsignedShort" minOccurs="0"/>

<xs:element name="mcvideo-emergency-private-call-media" type="xs:unsignedShort" minOccurs="0"/>

<xs:element name="anyExt" type="mcvideosc: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="mcvideo-max-duration" type="xs:duration" minOccurs="0"/>

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

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

<xs:minInclusive value="4"/>

<xs:maxInclusive value="256"/>

</xs:restriction>

</xs:simpleType>

<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="mcvideosc: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-transmission-control-protection" type="xs:boolean" minOccurs="0" default="true"/>

<xs:element name="anyExt" type="mcvideosc: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="mcvideosc:anyExtType" minOccurs="0"/>

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

</xs:sequence>

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

</xs:complexType>

<xs:complexType name="anyExtType">

<xs:sequence>

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

</xs:sequence>

</xs:complexType>

</xs:schema>

9.4.2.4 Default Document Namespace

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

9.4.2.5 MIME type

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

9.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 9.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 9.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 <mcvideo-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 Bc1 defined in Annex E of 3GPP TS 22.280 [30].

The value of the <num-levels-user-hierarchy> element in the <broadcast-group> element refers to variable Bc2 defined in Annex E of 3GPP TS 22.280 [30].

If the values of the <min-length-alias>, the <num-levels-group-hierarchy> element or the <num-levels-user-hierarchy> 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 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 higher or equal priority than the priority 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 higher or equal priority than the priority 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 IETF RFC 8101 [20] defines the priority levels for the MCPTT namespaces, which are applicable to all MC services.

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

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

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

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

The default value for the <allow-transmission-control-protection> element of the <protection-between-mcvideo-servers> element is "true" indicating that transmission control protection between MCVideo servers is enabled.

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

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

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

1) <mcvideo-max-duration>.

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 5: "xs:duration" allows the use of decimal notation 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".

9.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 MCVideo users by the MCVideo administrator, which corresponds to the "MinLengthAliasID" element as specified in clause 14.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 14.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 14.2.8 of 3GPP TS 24.483 [4];

In the <on-network> element:

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

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

3) the <allow-signalling-protection> element of the <protection-between-mcvideo-servers> element contains a boolean indicating whether protection of MCVideo signalling is enabled between MCVideo servers;

4) the <allow-transmission-control-protection> element of the <protection-between-mcvideo-servers> element contains a boolean indicating whether protection of MCVideo transmission control signalling is enabled between MCVideo servers;

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

5) the <emergency-resource-priority> element within the <on-network> element indicates how a Resource-Priority header field is to be populated for MCVideo emergency calls;

6) the <imminent-peril-resource-priority> element within the <on-network> element indicates how a Resource-Priority header field is to be populated for MCVideo imminent peril calls;

7) the <normal-resource-priority> element within the <on-network> element indicates how a Resource-Priority header field is to be populated when downgrading to normal priority from an MCVideo emergency call or MCVideo imminent peril call;

8) 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;

9) 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;

10) 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 MCVideo user is allowed for a currently activated functional alias contained in the corresponding <functional-alias> element;

11) the <entry> element of the <mcvideo-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 MCVideo ID of an MCVideo user that is allowed to activate the functional alias contained in the corresponding <functional-alias> element; and

12) the <functional-alias-priority> element of the <functional-alias-entry> element of the <functional-alias-list> element of 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 2: The usage of this parameter by the MCVideo server is up to implementation.

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

In the <off-network> element:

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

a) <mcvideo-private-call-signalling> element, which corresponds to the "MCVideoPrivateCallSignalling" element as specified in clause 14.2.12 of 3GPP TS 24.483 [4];

b) <mcvideo-private-call-media> element, which corresponds to the "MCVideoPrivateCallMedia" element as specified in clause 14.2.13 of 3GPP TS 24.483 [4];

c) <mcvideo-emergency-private-call-signalling> element, which corresponds to the "MCVideoEmergencyPrivateCallSignalling" element as specified in clause 14.2.14 of 3GPP TS 24.483 [4]; and

d) <mcvideo-emergency-private-call-media> element, which corresponds to the "MCVideoEmergencyPrivateCallMedia" element as specified in clause 14.2.15 of 3GPP TS 24.483 [4];

2) the <private-call> element contains configuration values for off-network private calls, for each of the following constituent elements:

a) <mcvideo-max-duration> element contains the maximum duration allowed for an off-network private call, as specified in clause 14.2.17 of 3GPP TS 24.483 [4]; and

3) 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 MCVideo transmission, which corresponds to the "NumLevelHierarchy" element as specified in clause 14.2.18 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.

9.4.2.8 Naming Conventions

The MCVideo service configuration document name shall be called "mcvideo-service-config.xml".

9.4.2.9 Global documents

The MCVideo 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 differentMC Video 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.mcvideo.service-config/global/mcvideo-service-config.xml

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

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

Since the MCVideo 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.

9.4.2.10 Resource interdependencies

There are no resource interdependencies.

9.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".

9.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.