14 MCVideo service configuration MO

24.4833GPPMission Critical Services (MCS) Management Object (MO)Release 18TS

14.1 General

The MCVideo service configuration Management Object (MO) is used to configure MCVideo Client behaviour for the on-network or off-network MCVideo Service. The MCVideo 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-MCVideo-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 MCVideo service configuration MO.

The following nodes and leaf objects are possible under the MCVideo service configuration node as described in figure 14.1.1.

Figure 14.1.1: The MCVideo service configuration MO

14.2 MCVideo service configuration MO parameters

14.2.1 General

This clause describes the parameters for the MCVideo service configuration Management Object (MO).

14.2.2 Node: <x>

Table 14.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 MCVideo service configuration Management Object (MO).

For the MCVideo service configuration MO, the namespace specific string is: "urn:oma:mo:oma-dm-mcvideo-service configuration:1.0"

– Values: N/A

14.2.3 /<x>/Name

Table 14.2.3.1: /<x>/Name

Name

Status

Occurrence

Format

Min. Access Types

Required

ZeroOrOne

chr

Get

The Name leaf is a name for the MCVideo service configuration settings.

– Values: <User displayable name>

14.2.4 /<x>/Ext/

Table 14.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 MCVideo 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

14.2.5 /<x>/Common

Table 14.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.

14.2.6 /<x>/Common/BroadcastMCVideoGroupCall

Table 14.2.6.1: /<x>/Common/BroadcastMCVideoGroupCall

Common/BroadcastMCVideoGroupCall

Status

Occurrence

Format

Min. Access Types

Required

One

node

Get, Replace

This interior node is a placeholder for Broadcast MCVideo Group Call configuration.

14.2.7 /<x>/Common/BroadcastMCVideoGroupCall/
NumLevelGroupHierarchy

Table 14.2.7.1: /<x>/Common/BroadcastMCVideoGroupCall/NumLevelGroupHierarchy

Common/BroadcastMCVideoGroupCall/NumLevelGroupHierarchy

Status

Occurrence

Format

Min. Access Types

Required

One

int

Get, Replace

This leaf node indicates the number of levels of group hierarchy for group-broadcast groups.

– Values: 0-255

The group-broadcast group with the lowest NumLevelGroupHierarchy value shall be considered as the group-broadcast group having the lowest level among the groups.

14.2.8 /<x>/Common/BroadcastMCVideoGroupCall/
NumLevelUserHierarchy

Table 14.2.8.1: /<x>/Common/BroadcastMCVideoGroupCall/NumLevelUserHierarchy

Common/BroadcastMCVideoGroupCall/NumLevelUserHierarchy

Status

Occurrence

Format

Min. Access Types

Required

One

int

Get, Replace

This leaf node indicates the number of levels of user hierarchy for user-broadcast groups.

– Values: 0-255

The user-broadcast group with the lowest NumLevelUserHierarchy value shall be considered as the user-broadcast group the lowest level among the groups.

14.2.9 /<x>/Common/MinLengthAliasID

Table 14.2.9.1: /<x>/Common/MinLengthAliasID

Common/MinLengthAliasID

Status

Occurrence

Format

Min. Access Types

Required

One

int

Get, Replace

This leaf node indicates minimum length of an alphanumeric identifier (i.e., alias) assigned by an MCVideo administrator.

– Values: 0-255

14.2.10 /<x>/OffNetwork

Table 14.2.10.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.

14.2.11 /<x>/OffNetwork/DefaultPPPP

Table 14.2.11.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.

14.2.12 /<x>/OffNetwork/DefaultPPPP/MCVideoPrivateCallSignalling

Table 14.2.12.1: /<x>/OffNetwork/DefaultPPPP/MCVideoPrivateCallSignalling

OffNetwork/DefaultPPPP/MCVideoPrivateCallSignalling

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 MCVideo private call signalling.

– Values: 1-8

The MCVideo user data with the lowest ProSe Per-Packet Priority value shall be considered as the MCVideo user data having the highest priority among the MCVideo user data.

14.2.13 /<x>/OffNetwork/DefaultPPPP/MCVideoPrivateCallMedia

Table 14.2.13.1: /<x>/OffNetwork/DefaultPPPP/MCVideoPrivateCallMedia

OffNetwork/DefaultPPPP/MCVideoPrivateCallMedia

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 MCVideo private call media.

– Values: 1-8

The MCVideo user data with the lowest ProSe Per-Packet Priority value shall be considered as the MCVideo user data having the highest priority among the MCVideo user data.

14.2.14 /<x>/OffNetwork/DefaultPPPP/
MCVideoEmergencyPrivateCallSignalling

Table 14.2.14.1: /<x>/OffNetwork/DefaultPPPP/MCVideoEmergencyPrivateCallSignalling

OffNetwork/DefaultPPPP/MCVideoEmergencyPrivateCallSignalling

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 MCVideo emerency private call signalling.

– Values: 1-8

The MCVideo user data with the lowest ProSe Per-Packet Priority value shall be considered as the MCVideo user data having the highest priority among the MCVideo user data.

14.2.15 /<x>/OffNetwork/DefaultPPPP/
MCVideoEmergencyPrivateCallMedia

Table 14.2.15.1: /<x>/OffNetwork/DefaultPPPP/MCVideoEmergencyPrivateCallMedia

OffNetwork/DefaultPPPP/MCVideoEmergencyPrivateCallMedia

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 MCVideo emerency private call media.

– Values: 1-8

The MCVideo user data with the lowest ProSe Per-Packet Priority value shall be considered as the MCVideo user data having the highest priority among the MCVideo user data.

14.2.16 /<x>/OffNetwork/PrivateCall

Table 14.2.16.1: /<x>/OffNetwork/PrivateCall

OffNetwork/PrivateCall

Status

Occurrence

Format

Min. Access Types

Required

One

node

Get, Replace

This interior node is a placeholder for private call configuration.

14.2.17 /<x>/OffNetwork/PrivateCall/MaxDuration

Table 14.2.17.1: /<x>/OffNetwork/PrivateCall/MaxDuration

OffNetwork/PrivateCall/MaxDuration

Status

Occurrence

Format

Min. Access Types

Required

One

int

Get, Replace

This leaf node indicates max private call duration.

– Values: 0-65535

The MaxDuration time is in seconds.

14.2.18 /<x>/OffNetwork/NumLevelHierarchy

Table 14.2.18.1: /<x>/OffNetwork/NumLevelHierarchy

OffNetwork/NumLevelHierarchy

Status

Occurrence

Format

Min. Access Types

Required

One

int

Get, Replace

This leaf node indicates the number of levels of hierarchy for transmission control override in off-network.

– Values: 4-256

The request with the lowest NumLevelHierarchy value shall be considered as the request having the lowest priority level given to override an active transmission among the requests.

Annex A (informative):
MCPTT UE configuration MO DDF

This DDF is the standardized minimal set. A vendor can define its own DDF for the complete device. This DDF can include more features than this minimal standardized version. The DDF is included as an XML file.

Annex B (informative):
MCPTT user profile MO DDF

This DDF is the standardized minimal set. A vendor can define its own DDF for the complete device. This DDF can include more features than this minimal standardized version. The DDF is included as an XML file.

Annex C (informative):
MCS group configuration MO DDF

This DDF is the standardized minimal set. A vendor can define its own DDF for the complete device. This DDF can include more features than this minimal standardized version. The DDF is included as an XML file.

Annex D (informative):
MCPTT service configuration MO DDF

This DDF is the standardized minimal set. A vendor can define its own DDF for the complete device. This DDF can include more features than this minimal standardized version. The DDF is included as an XML file.

Annex E (informative):
MCS UE initial configuration MO DDF

This DDF is the standardized minimal set. A vendor can define its own DDF for the complete device. This DDF can include more features than this minimal standardized version. The DDF is included as an XML file.

Annex F (informative):
MCVideo UE configuration MO DDF

This DDF is the standardized minimal set. A vendor can define its own DDF for the complete device. This DDF can include more features than this minimal standardized version. The DDF is included as an XML file.

Annex G (informative):
MCVideo user profile configuration MO DDF

This DDF is the standardized minimal set. A vendor can define its own DDF for the complete device. This DDF can include more features than this minimal standardized version. The DDF is included as an XML file.

Annex H (informative):
MCVideo service configuration MO DDF

This DDF is the standardized minimal set. A vendor can define its own DDF for the complete device. This DDF can include more features than this minimal standardized version. The DDF is included as an XML file.

Annex I (informative):
MCData UE configuration MO DDF

This DDF is the standardized minimal set. A vendor can define its own DDF for the complete device. This DDF can include more features than this minimal standardized version. The DDF is included as an XML file.

Annex J (informative):
MCData user profile configuration MO DDF

This DDF is the standardized minimal set. A vendor can define its own DDF for the complete device. This DDF can include more features than this minimal standardized version. The DDF is included as an XML file.

Annex K (informative):
MCData service configuration MO DDF

This DDF is the standardized minimal set. A vendor can define its own DDF for the complete device. This DDF can include more features than this minimal standardized version. The DDF is included as an XML file.

Annex L (normative):
MO specific concepts for the support of mission critical services over 5GS