9 MCData UE configuration MO
24.4833GPPMission Critical Services (MCS) Management Object (MO)Release 18TS
9.1 General
The MCData UE configuration Management Object (MO) is used to configure MCData Client behaviour for the on-network or off-network MCData Service. The MCData UE configuration parameters may be stored in the ME, or in the USIM as specified in 3GPP TS 31.102 [10], or in both the ME and the USIM. If both the ME and the USIM contain the same parameters, the values stored in the USIM shall take precedence.
The Management Object Identifier is: urn:oma:mo:ext-3gpp-MCData-UE-configuration:1.0.
Protocol compatibility: This MO is compatible with OMA OMA DM 1.2 [3].
The OMA DM ACL property mechanism (see OMA OMA-ERELD-DM-V1_2 [2]) may be used to grant or deny access rights to OMA DM servers in order to modify nodes and leaf objects of the MCData UE configuration MO.
The following nodes and leaf objects are possible under the MCData UE configuration node as described in figure 9.1.1 and figure 9.1.2.
Figure 9.1.1: The MCData UE configuration MO (1 of 2)
Figure 9.1.2: The MCData UE configuration MO (2 of 2)
9.2 MCData UE configuration MO parameters
9.2.1 General
This clause describes the parameters for the MCData UE configuration Management Object (MO).
9.2.2 Node: <x>
Table 9.2.2.1: Node: <x>
<x> |
|||||
Status |
Occurrence |
Format |
Min. Access Types |
||
Required |
OneOrMore |
node |
Get |
||
This interior node acts as a placeholder for the MCData UE configuration Management Object (MO). For the MCData UE configuration MO, the namespace specific string is: "urn:oma:mo:oma-dm-mcdata-ue-configuration:1.0" |
– Values: N/A
9.2.3 /<x>/Name
Table 9.2.3.1: /<x>/Name
Name |
|||||
Status |
Occurrence |
Format |
Min. Access Types |
||
Required |
ZeroOrOne |
chr |
Get |
||
The Name leaf is a name for the MCData UE configuration settings. |
– Values: <User displayable name>
9.2.4 /<x>/Ext/
Table 9.2.4.1: /<x>/Ext/
Ext |
|||||
Status |
Occurrence |
Format |
Min. Access Types |
||
Optional |
ZeroOrOne |
node |
Get, Replace |
||
The Ext is an interior node for where the vendor specific information about the MCData UE configuration MO is being placed. |
Usually the vendor extension is identified by vendor specific name under the ext node and contains the vendor meaning application vendor, device vendor etc. The tree structure under the vendor identified is not defined and can therefore include one or more un-standardized sub-trees.
– Values: N/A
9.2.5 /<x>/Common
Table 9.2.5.1: /<x>/Common
Common |
|||||
Status |
Occurrence |
Format |
Min. Access Types |
||
Required |
ZeroOrOne |
node |
Get, Replace |
||
This interior node represents a container for the common network operation which means both on-network operation and off-network operation. |
9.2.6 /<x>/Common/MCDataGroupTxns
Table 9.2.6.1: /<x>/Common/MCDataGroupTxns
Common/MCDataGroupTxns |
|||||
Status |
Occurrence |
Format |
Min. Access Types |
||
Required |
One |
node |
Get, Replace |
||
This interior node is a placeholder for the MCData group transactions configuration. |
9.2.7 /<x>/Common/MCDataGroupTxns/MaxSDSNc4
Table 9.2.7.1: /<x>/Common/MCDataGroupTxns/MaxSDSNc4
Common/MCDataGroupTxns/MaxSDSNc4 |
|||||
Status |
Occurrence |
Format |
Min. Access Types |
||
Required |
One |
int |
Get, Replace |
||
This leaf node indicates the maximum number of simultaneous SDS transactions. |
– Values: 0-255
9.2.8 /<x>/Common/MCDataGroupTxns/SDSPresentationPriority
Table 9.2.8.1: /<x>/Common/MCDataGroupTxns/SDSPresentationPriority
Common/MCDataGroupTxns/SDSPresentationPriority |
|||||
Status |
Occurrence |
Format |
Min. Access Types |
||
Required |
ZeroOrOne |
node |
Get, Replace |
||
This interior node is a placeholder for the prioritized MCData SDS configuration. |
9.2.9 /<x>/Common/MCDataGroupTxns/SDSPresentationPriority/<x>
Table 9.2.9.1: /<x>/Common/MCDataGroupTxns/SDSPresentationPriority/<x>
Common/MCDataGroupTxns/SDSPresentationPriority/<x> |
|||||
Status |
Occurrence |
Format |
Min. Access Types |
||
Required |
OneOrMore |
node |
Get, Replace |
||
This interior node is a placeholder for one or more prioritized MCData SDS configuration. |
9.2.10 /<x>/Common/MCDataGroupTxns/SDSPresentationPriority/
<x>/MCDataGroupID
Table 9.2.10.1: /<x>/Common/MCDataGroupTxns/SDSPresentationPriority/<x>/MCDataGroupID
Common/MCDataGroupTxns/SDSPresentationPriority/<x>/MCDataGroupID |
|||||
Status |
Occurrence |
Format |
Min. Access Types |
||
Required |
One |
chr |
Get, Replace |
||
This leaf node indicates the associated MCData group ID. |
The value is a "uri" attribute specified in OMA OMA-TS-XDM_Group-V1_1 [4].
9.2.11 /<x>/Common/MCDataGroupTxns/SDSPresentationPriority/
<x>/MCDataGroupPriorityHierarchy
Table 9.2.11.1: /<x>/Common/MCDataGroupTxns/SDSPresentationPriority/<x>/
MCDataGroupPriorityHierarchy
Common/MCDataGroupTxns/SDSPresentationPriority/<x>/MCDataGroupPriorityHierarchy |
|||||
Status |
Occurrence |
Format |
Min. Access Types |
||
Required |
One |
int |
Get, Replace |
||
This leaf node indicates the requested presentation priority of SDS transactions. |
– Values: 0-255
The group with the lowest MCDataGroupPriorityHierarchy value shall be considered as the group having the lowest priority among the groups.
9.2.12 /<x>/Common/MCDataGroupTxns/MaxFDNc4
Table 9.2.12.1: /<x>/Common/MCDataGroupTxns/MaxFDNc4
Common/MCDataGroupTxns/MaxFDNc4 |
|||||
Status |
Occurrence |
Format |
Min. Access Types |
||
Required |
One |
int |
Get, Replace |
||
This leaf node indicates the maximum number of simultaneous FD transactions. |
– Values: 0-255
9.2.13 /<x>/Common/MCDataGroupTxns/FDPresentationPriority
Table 9.2.13.1: /<x>/Common/MCDataGroupTxns/FDPresentationPriority
Common/MCDataGroupTxns/FDPresentationPriority |
|||||
Status |
Occurrence |
Format |
Min. Access Types |
||
Required |
ZeroOrOne |
node |
Get, Replace |
||
This interior node is a placeholder for the prioritized MCData FD configuration. |
9.2.14 /<x>/Common/MCDataGroupTxns/FDPresentationPriority/<x>
Table 9.2.14.1: /<x>/Common/MCDataGroupTxns/FDPresentationPriority/<x>
Common/MCDataGroupTxns/FDPresentationPriority /<x> |
|||||
Status |
Occurrence |
Format |
Min. Access Types |
||
Required |
OneOrMore |
node |
Get, Replace |
||
This interior node is a placeholder for one or more prioritized MCData FD configuration. |
9.2.15 /<x>/Common/MCDataGroupTxns/FDPresentationPriority/
<x>/MCDataGroupID
Table 9.2.15.1: /<x>/Common/MCDataGroupTxns/FDPresentationPriority/<x>/MCDataGroupID
Common/MCDataGroupTxns/FDPresentationPriority/<x>/MCDataGroupID |
|||||
Status |
Occurrence |
Format |
Min. Access Types |
||
Required |
One |
chr |
Get, Replace |
||
This leaf node indicates the associated MCData group ID. |
The value is a "uri" attribute specified in OMA OMA-TS-XDM_Group-V1_1 [4].
9.2.16 /<x>/Common/MCDataGroupTxns/FDPresentationPriority/
<x>/MCDataGroupPriorityHierarchy
Table 9.2.16.1: /<x>/Common/MCDataGroupTxns/FDPresentationPriority/<x>/
MCDataGroupPriorityHierarchy
Common/MCDataGroupTxns/FDPresentationPriority/<x>/MCDataGroupPriorityHierarchy |
|||||
Status |
Occurrence |
Format |
Min. Access Types |
||
Required |
One |
int |
Get, Replace |
||
This leaf node indicates the requested presentation priority of FD transactions. |
– Values: 0-255
The group with the lowest MCDataGroupPriorityHierarchy value shall be considered as the group having the lowest priority among the groups.
9.2.17 /<x>/Common/MCDataGroupTxns/ConversationPresentationPriority
Table 9.2.17.1: /<x>/Common/MCDataGroupTxns/ConversationPresentationPriority
Common/MCDataGroupTxns/ConversationPresentationPriority |
|||||
Status |
Occurrence |
Format |
Min. Access Types |
||
Required |
ZeroOrOne |
node |
Get, Replace |
||
This interior node is a placeholder for the prioritized MCData conversation management configuration. |
9.2.18 /<x>/Common/MCDataGroupTxns/
ConversationPresentationPriority/<x>
Table 9.2.18.1: /<x>/Common/MCDataGroupTxns/ConversationPresentationPriority/<x>
Common/MCDataGroupTxns/ConversationPresentationPriority /<x> |
|||||
Status |
Occurrence |
Format |
Min. Access Types |
||
Required |
OneOrMore |
node |
Get, Replace |
||
This interior node is a placeholder for one or more prioritized MCData conversation management configuration. |
9.2.19 /<x>/Common/MCDataGroupTxns/
ConversationPresentationPriority/<x>/MCDataGroupID
Table 9.2.19.1: /<x>/Common/MCDataGroupTxns/ConversationPresentationPriority/<x>/
MCDataGroupID
Common/MCDataGroupTxns/ConversationPresentationPriority/<x>/MCDataGroupID |
|||||
Status |
Occurrence |
Format |
Min. Access Types |
||
Required |
One |
chr |
Get, Replace |
||
This leaf node indicates the associated MCData group ID. |
The value is a "uri" attribute specified in OMA OMA-TS-XDM_Group-V1_1 [4].
9.2.20 /<x>/Common/MCDataGroupTxns/
ConversationPresentationPriority/<x>/
MCDataGroupPriorityHierarchy
Table 9.2.20.1: /<x>/Common/MCDataGroupTxns/ConversationPresentationPriority/<x>/
MCDataGroupPriorityHierarchy
Common/MCDataGroupTxns/ConversationPresentationPriority/<x>/MCDataGroupPriorityHierarchy |
|||||
Status |
Occurrence |
Format |
Min. Access Types |
||
Required |
One |
int |
Get, Replace |
||
This leaf node indicates the requested presentation priority of conversation management transactions. |
– Values: 0-255
The group with the lowest MCDataGroupPriorityHierarchy value shall be considered as the group having the lowest priority among the groups.
9.2.21 /<x>/Common/MCDataGroupTxns/MaxTCNc4
Table 9.2.21.1: /<x>/Common/MCDataGroupTxns/MaxTCNc4
Common/MCDataGroupTxns/MaxTCNc4 |
|||||
Status |
Occurrence |
Format |
Min. Access Types |
||
Required |
One |
int |
Get, Replace |
||
This leaf node indicates the maximum number of simultaneous data transmissions. |
– Values: 0-255
9.2.22 /<x>/Common/MCDataGroupTxns/MaxTCNc5
Table 9.2.22.1: /<x>/Common/MCDataGroupTxns/MaxTCNc5
Common/MCDataGroupTxns/MaxTCN5 |
|||||
Status |
Occurrence |
Format |
Min. Access Types |
||
Required |
One |
int |
Get, Replace |
||
This leaf node indicates the maximum number of data transmissions in a group. |
– Values: 0-255
9.2.23 /<x>/Common/MCDataGroupTxns/DataPresentationPriority
Table 9.2.23.1: /<x>/Common/MCDataGroupTxns/DataPresentationPriority
Common/MCDataGroupTxns/DataPresentationPriority |
|||||
Status |
Occurrence |
Format |
Min. Access Types |
||
Required |
ZeroOrOne |
node |
Get, Replace |
||
This interior node is a placeholder for the prioritized MCData Transmission Control configuration. |
9.2.24 /<x>/Common/MCDataGroupTxns/DataPresentationPriority/
<x>
Table 9.2.24.1: /<x>/Common/MCDataGroupTxns/DataPresentationPriority/<x>
Common/MCDataGroupTxns/DataPresentationPriority/<x> |
|||||
Status |
Occurrence |
Format |
Min. Access Types |
||
Required |
OneOrMore |
node |
Get, Replace |
||
This interior node is a placeholder for one or more prioritized MCData Transmission Control configuration. |
9.2.25 /<x>/Common/MCDataGroupTxns/DataPresentationPriority/
<x>/MCDataGroupID
Table 9.2.25.1: /<x>/Common/MCDataGroupTxns/DataPresentationPriority/<x>/MCDataGroupID
Common/MCDataGroupTxns/DataPresentationPriority/<x>/MCDataGroupID |
|||||
Status |
Occurrence |
Format |
Min. Access Types |
||
Required |
One |
chr |
Get, Replace |
||
This leaf node indicates the associated MCData group ID. |
The value is a "uri" attribute specified in OMA OMA-TS-XDM_Group-V1_1 [4].
9.2.26 /<x>/Common/MCDataGroupTxns/DataPresentationPriority/
<x>/MCDataGroupPriorityHierarchy
Table 9.2.26.1: /<x>/Common/MCDataGroupTxns/DataPresentationPriority/<x>/
MCDataGroupPriorityHierarchy
Common/MCDataGroupTxns/DataPresentationPriority/<x>/MCDataGroupPriorityHierarchy |
|||||
Status |
Occurrence |
Format |
Min. Access Types |
||
Required |
One |
int |
Get, Replace |
||
This leaf node indicates the requested presentation priority of data received. |
– Values: 0-255
The group with the lowest MCDataGroupPriorityHierarchy value shall be considered as the group having the lowest priority among the groups.
9.2.27 /<x>/Common/MCDataGroupTxns/MaxRCNc4
Table 9.2.27.1: /<x>/Common/MCDataGroupTxns/MaxRCNc4
Common/MCDataGroupTxns/MaxRCNc4 |
|||||
Status |
Occurrence |
Format |
Min. Access Types |
||
Required |
One |
int |
Get, Replace |
||
This leaf node indicates the maximum number of simultaneous data receptions. |
– Values: 0-255
9.2.28 /<x>/Common/MCDataGroupTxns/MaxRCNc5
Table 9.2.28.1: /<x>/Common/MCDataGroupTxns/MaxRCNc5
Common/MCDataGroupTxns/MaxRCN5 |
|||||
Status |
Occurrence |
Format |
Min. Access Types |
||
Required |
One |
int |
Get, Replace |
||
This leaf node indicates the maximum number of data receptions in a group. |
– Values: 0-255
9.2.29 /<x>/OnNetwork
Table 9.2.29.1: /<x>/OnNetwork
OnNetwork |
|||||
Status |
Occurrence |
Format |
Min. Access Types |
||
Required |
ZeroOrOne |
node |
Get, Replace |
||
This interior node represents a container for on-network operation. |
9.2.30 /<x>/OnNetwork/RelayService
Table 9.2.30.1: /<x>/OnNetwork/RelayService
OnNetwork/RelayService |
|||||
Status |
Occurrence |
Format |
Min. Access Types |
||
Required |
One |
bool |
Get, Replace |
||
This leaf node indicates the authorisation to use a relay service. |
When set to "true" the MCData group is allowed to use a relay service.
When set to "false" the MCData group is not allowed to use a relay service.
9.2.31 /<x>/OnNetwork/IPv6Preferred
Table 9.2.31.1: /<x>/OnNetwork/IPv6Preferred
OnNetwork/IPv6Preferred |
|||||
Status |
Occurrence |
Format |
Min. Access Types |
||
Required |
One |
bool |
Get, Replace |
||
This leaf node indicates whether IPv6 is preferred over IPv4 for on-network operation when the MCData UE has both IPv4 and IPv6 host configuration. |
If the MCData UE has both IPv4 and IPv6 host configuration and:
– if IPv6Preferred is set to "true" then the UE uses IPv6 for all on‑network signalling and media; otherwise
– if IPv6Preferred is set to "false" then the UE uses IPv4 for all on‑network signalling and media.
9.2.32 /<x>/OnNetwork/RelayedMCDataGroup
Table 9.2.32.1: /<x>/OnNetwork/RelayedMCDataGroup
OnNetwork/RelayedMCDataGroup |
|||||
Status |
Occurrence |
Format |
Min. Access Types |
||
Optional |
ZeroOrOne |
node |
Get, Replace |
||
This interior node is a placeholder for the allowed relayed MCData groups. |
9.2.33 /<x>/OnNetwork/RelayedMCDataGroup/<x>
Table 9.2.33.1: /<x>/OnNetwork/RelayedMCDataGroup/<x>
OnNetwork/RelayedMCDataGroup/<x> |
|||||
Status |
Occurrence |
Format |
Min. Access Types |
||
Required |
OneOrMore |
node |
Get, Replace |
||
This interior node is a placeholder for one or more allowed relayed MCData groups. |
9.2.34 /<x>/OnNetwork/RelayedMCDataGroup/<x>/MCDataGroupID
Table 9.2.34.1: /<x>/OnNetwork/RelayedMCDataGroup/<x>/MCDataGroupID
OnNetwork/RelayedMCDataGroup/<x>/MCDataGroupID |
|||||
Status |
Occurrence |
Format |
Min. Access Types |
||
Required |
One |
chr |
Get, Replace |
||
This leaf node indicates the associated MCData group ID. |
The value is a "uri" attribute specified in OMA OMA-TS-XDM_Group-V1_1 [4].
9.2.35 /<x>/OnNetwork/RelayedMCDataGroup/<x>/RelayServiceCode
Table 9.2.35.1: /<x>/OnNetwork/RelayedMCDataGroup/<x>/RelayServiceCode
OnNetwork/RelayedMCDataGroup/<x>/RelayServiceCode |
|||||
Status |
Occurrence |
Format |
Min. Access Types |
||
Required |
One |
chr |
Get, Replace |
||
This leaf node indicates the connectivity service that the ProSe UE-to-network relay provides to public safety applications as specified in 3GPP TS 23.303 [6]. |