10.2 MCData UE configuration document

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

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

10.2.1 General

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

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

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

10.2.1A MCData client access to MCData UE configuration documents

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

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

CMSXCAPROOTURI/org.3gpp.mcdata.ue-config/users/sip:MCDATAID/MCSUEID

10.2.2 Coding

10.2.2.1 Structure

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

The <mcdata-UE-configuration> document:

1) shall include a "domain" attribute;

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

3) may include a <name> element;

4) shall include a <common> element;

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

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

The <common> element:

1) shall contain a <short-data-service> element containing:

a) a <Max-Simul-SDS-Txns-Nc4> element; and

b) a <SDS-Presentation-Priority> element containing:

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

A) an <MCData-Group-ID> element; and

B) a <group-priority-hierarchy> element;

2) shall contain a <file-distribution> element containing:

a) a <Max-Simul-FD-Txns-Nc4> element; and

b) a <FD-Presentation-Priority> element containing:

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

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

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

3) shall contain a <conversation-management> element containing:

a) a <Conversation-Presentation-Priority> element containing:

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

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

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

4) shall contain a <transmission-control> element containing:

a) a <Max-Simul-Data-Transmissions-Nc4> element;

b) a <Max-Data-Transmissions-In-Group-Nc5> element; and

c) a <Data-Presentation-Priority> element containing:

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

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

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

5) shall contain a <reception-control> element containing:

a) a <Max-Simul-Data-Receptions-Nc4> element; and

b) a <Max-Data-Receptions-In-Group-Nc5> 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-MCData-Group> elements containing:

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

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

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

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

10.2.2.2 Application Unique ID

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

10.2.2.3 XML Schema

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

<xs:schema xmlns:mcdatauep="urn:3gpp:mcdata:mcdataUEConfig:1.0"

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

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

<xs:complexType>

<xs:sequence>

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

<xs:element name="mcdata-UE-id" type="mcdatauep:MCDataUEIDType"/>

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

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

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

</xs:choice>

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

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

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

</xs:extension>

</xs:simpleContent>

</xs:complexType>

<xs:complexType name="MCDataUEIDType">

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

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

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

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

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

</xs:choice>

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

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

</xs:complexType>

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

<xs:sequence>

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

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

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

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

</xs:choice>

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

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

</xs:sequence>

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

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

</xs:complexType>

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

<xs:sequence>

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

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

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

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

</xs:sequence>

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

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

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

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

</xs:extension>

</xs:simpleContent>

</xs:complexType>

<xs:complexType name="CommonType">

<xs:sequence>

<xs:element name="short-data-service">

<xs:complexType>

<xs:sequence>

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

<xs:element name="SDS-Presentation-Priority">

<xs:complexType>

<xs:sequence>

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

<xs:complexType>

<xs:sequence>

<xs:element name="MCData-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="file-distribution">

<xs:complexType>

<xs:sequence>

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

<xs:element name="FD-Presentation-Priority">

<xs:complexType>

<xs:sequence>

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

<xs:complexType>

<xs:sequence>

<xs:element name="MCData-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="conversation-management">

<xs:complexType>

<xs:sequence>

<xs:element name="Conversation-Presentation-Priority">

<xs:complexType>

<xs:sequence>

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

<xs:complexType>

<xs:sequence>

<xs:element name="MCData-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="transmission-control">

<xs:complexType>

<xs:sequence>

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

<xs:element name="Max-Data-Transmissions-In-Group-Nc5" type="xs:positiveInteger"/>

<xs:element name="Data-Presentation-Priority">

<xs:complexType>

<xs:sequence>

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

<xs:complexType>

<xs:sequence>

<xs:element name="MCData-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="reception-control">

<xs:complexType>

<xs:sequence>

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

<xs:element name="Max-Data-Receptions-In-Group-Nc5" type="xs:positiveInteger"/>

</xs:sequence>

</xs:complexType>

</xs:element>

</xs:sequence>

<xs:attributeGroup ref="mcdatauep: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-MCData-Group" type="mcdatauep:Relayed-MCData-GroupType" minOccurs="0"/>

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

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

</xs:sequence>

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

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

</xs:complexType>

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

<xs:sequence>

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

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

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

10.2.2.4 Default Document Namespace

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

10.2.2.5 MIME type

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

10.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 10.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 MCData UE configuration document shall conform to the XML Schema described in clause 10.2.2.3.

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

The <mcdata-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 <mcdata-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 <mcdata-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 <MCData-Group-ID> element of the <MCData-group-priority> element of the <SDS-Presentation-Priority> element, <FD-Presentation-Priority> element, <Conversation-Presentation-Priority> element or <Data-Presentation-Priority> 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 <MCData-group-priority> element of the <SDS-Presentation-Priority> element, <FD-Presentation-Priority> element, <Conversation-Presentation-Priority> element or <Data-Presentation-Priority> 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".

If the <Relay-Service> element of the <On-Network> element does not contains 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-MCData-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 contains 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".

10.2.2.7 Data Semantics

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

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

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

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

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

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

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

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

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

In the <common> element:

1) the <Max-Simul-SDS-Txns-Nc4> element of the <short-data-service> element contains an integer indicating the maximum number of simultaneous SDS transactions (Nc4) allowed for an MCData UE for on-network or off-network group SDS and corresponds to the "MaxSDSNc4" element of clause 9.2.7 in 3GPP TS 24.483 [4];

2) the <SDS-Presentation-Priority> element of the <short-data-service> element corresponds to the "SDSPresentationPriority" element of clause 9.2.8 in 3GPP TS 24.483 [4] and contains a list of <MCData-Group-Priority> elements that contains:

a) <MCData-Group-ID> element identifying an MCData group that corresponds to the "MCDataGroupID" element of clause 9.2.10 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 MCData group with 0 being the lowest priority and 255 being the highest priority and corresponds to the "MCDataGroupPriorityHierarchy" element of clause 9.2.11 in 3GPP TS 24.483 [4].

3) the <Max-Simul-FD-Txns-Nc4> element of the <file-distribution> element contains an integer indicating the maximum number of simultaneous FD transactions (Nc4) allowed for an MCData UE for on-network or off-network group FD and corresponds to the "MaxFDNc4" element of clause 9.2.12 in 3GPP TS 24.483 [4];

4) the <FD-Presentation-Priority> element of the <file-distribution> element corresponds to the "FDPresentationPriority" element of clause 9.2.13 in 3GPP TS 24.483 [4] and contains a list of <MCData-Group-Priority> elements that contains:

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

5) the <Conversation-Presentation-Priority> element of the <conversation-management> element corresponds to the "ConversationPresentationPriority" element of clause 9.2.17 in 3GPP TS 24.483 [4] and contains a list of <MCData-Group-Priority> elements that contains:

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

6) the <Max-Simul-Data-Transmissions-Nc4> element of the <transmission-control> element contains an integer indicating the maximum number of simultaneous data transmissions (Nc4) allowed for an MCData UE for on-network or off-network group data transmissions and corresponds to the "MaxTCNc4" element of clause 9.2.21 in 3GPP TS 24.483 [4];

7) the <Max-Data-Transmissions-In-Group-Nc5> element of the <transmission-control> element contains an integer indicating the maximum number of data transmissions in a group (Nc5) allowed for an MCData UE for on-network or off-network group data transmission and corresponds to the "MaxTCNc5" element of clause 9.2.22 in 3GPP TS 24.483 [4];

8) the <Data-Presentation-Priority> element of the <transmission-control> element corresponds to the "DataPresentationPriority" element of clause 9.2.23 in 3GPP TS 24.483 [4] and contains a list of <MCData-Group-Priority> elements that contains:

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

9) the <Max-Simul-Data-Receptions-Nc4> element of the <reception-control> element contains an integer indicating the maximum number of simultaneous data receptions (Nc4) allowed for an MCData UE for on-network or off-network group data transmissions and corresponds to the "MaxRCNc4" element of clause 9.2.27 in 3GPP TS 24.483 [4];

10) the <Max-Data-Receptions-In-Group-Nc5> element of the <transmission-control> element contains an integer indicating the maximum number of data receptions in a group (Nc5) allowed for an MCData UE for on-network or off-network group data transmission and corresponds to the "MaxRCNc5" element of clause 9.2.28in 3GPP TS 24.483 [4];

In the <on-network> element:

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

2) an <IPv6Preferred> element which corresponds to the "IPv6Preferred" element of clause 9.2.31 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; and

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-MCData-Groups> element of the <Relay-Service> element which corresponds to the "RelayedMCDataGroup" element of clause 9.2.32 in 3GPP TS 24.483 [4] contains:

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

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

10.2.2.8 Naming Conventions

The present document defines no naming conventions.

10.2.2.9 Global documents

The present document requires no global documents.

10.2.2.10 Resource interdependencies

There are no resource interdependencies.

10.2.2.11 Authorization Policies

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

10.2.2.12 Subscription to Changes

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

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