5 Management Object parameters

24.2863GPPIP Multimedia (IM) Core Network (CN) subsystem Centralized Services (ICS)Management Object (MO)Release 17TS

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

5.1 General

This clause describes the parameters for the IMS Centralised Services Management Object (MO).

5.2 Node: <X>

This interior node acts as a placeholder for the IMS Centralised Services Management Object (MO).

– Occurrence: ZeroOrOne

– Format: node

– Access Types: Get

– Values: N/A

5.3 /<X>/Name

The Name leaf is a name for the IMS Centralised Services settings.

– Occurrence: ZeroOrOne

– Format: chr

– Access Types: Get

– Values: <User displayable name>

5.4 /<X>/ICS_Capabilities_Enabled

The ICS_Capabilities_Enabled leaf indicates an operator’s preference to enable or disable IMS Centralised Services.

– Occurrence: One

– Format: bool

– Access Types: Get, Replace

– Values: 0, 1

0 – Indicates that IMS Centralised Services capabilities over Gm are enabled.

1 – Indicates that IMS Centralised Services capabilities over Gm are disabled.

The default value is that IMS Centralised Services over Gm are disabled when the IMS Centralised Services Management Object is not provisioned. Use of the ICS_Capabilities_Enabled leaf is specified in 3GPP TS 24.292 [3].

5.5 /<X>/I1_Capabilities_Enabled

The I1_Capabilities_Enabled leaf indicates an operator’s preference to enable or disable support for the I1 protocol.

– Occurrence: One

– Format: int

– Access Types: Get, Replace

– Values: 0, 1

0 – Indicates that IMS Centralised Services capabilities over I1 are disabled.

1 – Indicates that IMS Centralised Services capabilities over I1 are enabled if concurrent use of CS RAT and PS RAT is not supported.

The default value is that IMS Centralised Services over I1 are disabled when the IMS Centralised Services Management Object is not provisioned. Use of the I1_Capabilities_Enabled leaf is specified in 3GPP TS 24.292 [3].

5.6 /<X>/Ext/

The Ext is an interior node for where the vendor specific information about the IMS Centralised Services MO is being placed (vendor meaning application vendor, device vendor etc.). Usually the vendor extension is identified by vendor specific name under the ext node. The tree structure under the vendor identified is not defined and can therefore include one or more un-standardized sub-trees.

– Occurrence: ZeroOrOne

– Format: node

– Access Types: Get, Replace

– Values: N/A

Annex A (informative):
Management Object 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.

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

<!DOCTYPE MgmtTree PUBLIC "-//OMA//DTD-DM-DDF 1.2//EN"

"http://www.openmobilealliance.org/tech/DTD/dm_ddf-v1_2.dtd">

<Node>

<NodeName>IMS Centralised Services</NodeName>

<Get/>

</AccessType>

<Description> IMS Centralised Services settings</Description>

<node/>

</DFFormat>

</Occurrence>

<DFTitle>The IMS Centralised Services Management Object.</DFTitle>

</DFType>

<Node>

<Get/>

</AccessType>

<chr/>

</DFFormat>

</Occurrence>

<DFTitle>User displayable name for the node</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>ICS_Capabilities_Enabled</NodeName>

<Get/>

</AccessType>

<bool/>

</DFFormat>

<One/>

</Occurrence>

<DFTitle>This leaf specifies an operator’s preference to enable or disable IMS Centralised Services capabilities.</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>I1_Capabilities_Enabled</NodeName>

<Get/>

</AccessType>

<int/>

</DFFormat>

<One/>

</Occurrence>

<DFTitle>This leaf specifies an operator’s preference to enable or disable I1 capabilities.</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<!– The Extension node starts here. –>

<Get/>

</AccessType>

<node/>

</DFFormat>

</Occurrence>

<DFTitle>A collection of all Extension objects.</DFTitle>

</DFType>

</DFProperties>

</Node>

</MgmtTree>

Annex B (informative):
Change history

Change history
Date	TSG #	TSG Doc.	CR	Rev	Subject/Comment	Old	New
2009-11					Version 0.0.1: Preliminary proposal		0.0.1
2009-11					Version 0.0.2: Revision based on comments in CT1#62		0.0.2
2009-11					Version 0.0.3: Revision based on further comments in CT1#62		0.0.3
2009-11					Version 0.0.4: Cleanup of whitespace and styles and specification number (24.xyz)		0.0.4
2009-11					Further editorial cleanups	0.0.4	0.0.5
2009-11					Further editorial cleanups	0.05	0.0.6
2009-12	CT-46				V1.0.0 created by MCC for presentation to CT-46 for information and approval	0.0.6	1.0.0
2009-12	CT-46				V8.0.0 created by MCC after approval at CT-46	1.0.0	8.0.0
2009-12	CT-46				Upgrade to Rel-9	8.0.0	9.0.0
2009-12	CT-46				Editorial correction	9.0.0	9.0.1
2010-03	CT-47	CP-100137	0001	1	Enable use of I1 when the home operator has configured it to do so	9.0.1	9.1.0
2011-03	CT-51	CP-110170	0006		MO identifier registered by OMNA	9.1.0	9.2.0
2011-03	CT-51				Upgrade to Rel-10	9.2.0	10.0.0
2012-09	CT-57				Upgrade to Rel-11	10.0.0	11.0.0
2014-09	CT-65				Upgrade to Rel-12	11.0.0	12.0.0
2015-12	CT-70				Upgrade to Rel-13	12.0.0	13.0.0

Change history
Date	Meeting	TDoc	CR	Rev	Cat	Subject/Comment	New version
2017-03	CT-75					Upgrade to Rel-14	14.0.0
2018-06	SA-80	–	–	–		Update to Rel-15 version (MCC)	15.0.0
2020-07	SA-88e	–	–	–		Update to Rel-16 version (MCC)	16.0.0
2022-03	CT-95	–	–	–	–	Update to Rel-17 version (MCC)	17.0.0