11 MCData service configuration MO
24.4833GPPMission Critical Services (MCS) Management Object (MO)Release 18TS
11.1 General
The MCData service configuration Management Object (MO) is used to configure MCData Client behaviour for the on-network or off-network MCData Service. The MCData service 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-service-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 service configuration MO.
The following nodes and leaf objects are possible under the MCData service configuration node as described in figure 11.1.1.
Figure 11.1.1: The MCData service configuration MO
11.2 MCData service configuration MO parameters
11.2.1 General
This clause describes the parameters for the MCData service configuration Management Object (MO).
11.2.2 Node: <x>
Table 11.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 service configuration Management Object (MO). For the MCData service configuration MO, the namespace specific string is: "urn:oma:mo:oma-dm-mcdata-service configuration:1.0" |
– Values: N/A
11.2.3 /<x>/Name
Table 11.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 service configuration settings. |
– Values: <User displayable name>
11.2.4 /<x>/Ext/
Table 11.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 service 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
11.2.5 /<x>/Common
Table 11.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. |
11.2.6 /<x>/Common/TxRxControl
Table 11.2.6.1: /<x>/Common/TxRxControl
Common/TxRxControl |
|||||
Status |
Occurrence |
Format |
Min. Access Types |
||
Required |
One |
node |
Get, Replace |
||
This interior node is a placeholder for transmission and reception control configuration. |
11.2.7 /<x>/Common/TxRxControl/TimeTempDataWaiting
Table 11.2.7.1: /<x>/Common/TxRxControl/TimeTempDataWaiting
Common/TxRxControl/TimeTempDataWaiting |
|||||
Status |
Occurrence |
Format |
Min. Access Types |
||
Required |
One |
int |
Get, Replace |
||
This leaf node indicates the time limit for the temporarily stored data that is waiting to be delivered to a receiving user. |
– Values: 0-65535
The TimeTempDataWaiting is in minutes.
11.2.8 /<x>/Common/TxRxControl/TimePeriodicAnnouncement
Table 11.2.8.1: /<x>/Common/TxRxControl/TimePeriodicAnnouncement
Common/TxRxControl/TimePeriodicAnnouncement |
|||||
Status |
Occurrence |
Format |
Min. Access Types |
||
Required |
One |
int |
Get, Replace |
||
This leaf node indicates the timer for the periodic announcement which contains a list of available recently invited data group communications. |
– Values: 0-65535
The TimePeriodicAnnouncement is in minutes.
11.2.9 /<x>/OffNetwork
Table 11.2.9.1: /<x>/OffNetwork
OffNetwork |
|||||
Status |
Occurrence |
Format |
Min. Access Types |
||
Required |
ZeroOrOne |
node |
Get, Replace |
||
This interior node represents a container for off-network operation. |
11.2.10 /<x>/OffNetwork/DefaultPPPP
Table 11.2.10.1: /<x>/OffNetwork/DefaultPPPP
OffNetwork/DefaultPPPP |
|||||
Status |
Occurrence |
Format |
Min. Access Types |
||
Required |
One |
node |
Get, Replace |
||
This interior node is a placeholder for the default ProSe Per-Packet Priority (PPPP) configuration. |
11.2.11 /<x>/OffNetwork/DefaultPPPP/MCDataOneToOneCallSignalling
Table 11.2.11.1: /<x>/OffNetwork/DefaultPPPP/MCDataOneToOneCallSignalling
OffNetwork/DefaultPPPP/MCDataOneToOneCallSignalling |
|||||
Status |
Occurrence |
Format |
Min. Access Types |
||
Required |
One |
int |
Get, Replace |
||
This leaf node indicates the default ProSe Per-Packet Priority (PPPP) value (as specified in 3GPP TS 23.303 [6]) for the MCData one-to-one call signalling. |
– Values: 1-8
The MCData user data with the lowest ProSe Per-Packet Priority value shall be considered as the MCData user data having the highest priority among the MCData user data.
11.2.12 /<x>/OffNetwork/DefaultPPPP/MCDataOneToOneCallMedia
Table 11.2.12.1: /<x>/OffNetwork/DefaultPPPP/MCDataOneToOneCallMedia
OffNetwork/DefaultPPPP/MCDataOneToOneCallMedia |
|||||
Status |
Occurrence |
Format |
Min. Access Types |
||
Required |
One |
int |
Get, Replace |
||
This leaf node indicates the default ProSe Per-Packet Priority (PPPP) value (as specified in 3GPP TS 23.303 [6]) for the MCData private call media. |
– Values: 1-8
The MCData user data with the lowest ProSe Per-Packet Priority value shall be considered as the MCData user data having the highest priority among the MCData user data.
11.2.13 /<x>/OnNetwork
Table 11.2.13.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. |
11.2.14 /<x>/OnNetwork/NotificationServers
Table 11.2.14.1: /<x>/OnNetwork/NotificationServers
<x>/OnNetwork/NotificationServers |
|||||
Status |
Occurrence |
Format |
Min. Access Types |
||
Optional |
One |
node |
Get, Replace |
||
This interior node is a placeholder for a list of hostnames of the Notification servers. |
11.2.15 /<x>/OnNetwork/NotificationServers/<x>
Table 11.2.15.1: /<x>/OnNetwork/NotificationServers/<x>
<x>/OnNetwork/NotificationServers/<x> |
|||||
Status |
Occurrence |
Format |
Min. Access Types |
||
Optional |
OneOrMore |
node |
Get, Replace |
||
This interior node is a placeholder for one or more hostnames of the Notification servers. |
11.2.16 /<x>/OnNetwork/NotificationServers/<x>/NotificationServer
Table 11.2.16.1: /<x>/OnNetwork/NotificationServers/<x>/NotificationServer
<x>/OnNetwork/NotificationServers/<x>/NotificationServer |
|||||
Status |
Occurrence |
Format |
Min. Access Types |
||
Required |
One |
chr |
Get, Replace |
||
This leaf node indicates a hostname of the Notification server. |