5 Management object parameters

24.4173GPPManagement Object (MO) for Originating Identification Presentation (OIP) and Originating Identification Restriction (OIR) using IP Multimedia (IM) Core Network (CN) subsystemRelease 17TS

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

5.1 General

This clause describes the parameters for the Originating Identification Presentation (OIP) and Originating Identification Restriction (OIR) MO.

5.2 Node: /<X>

This interior node acts as a placeholder for the OIP and OIR services MO.

For the OIP-OIR services configuration MO, the namespace specific string is: "urn:oma:mo:ext-3gpp-oipoir:1.0"

– Occurrence: OneOrMore

– Format: node

– Access Types: Get, Replace

– Values: N/A

Support for a UE is defined by the UE role as specified in 3GPP TS 24.607 [3].

NOTE: One node is normally used.

5.3 /<X>/Name

The Name leaf is a name for the OIP and OIR services settings.

– Occurrence: ZeroOrOne

– Format: chr

– Access Types: Get, Replace

– Values: <User displayable name>

5.4 /<X>/FromPreferred

The FromPreferred leaf indicates operator’s originating party identity determination policy.

– Occurrence: One

– Format: bool

– Access Types: Get, Replace

– Values: 0, 1

0 – Indicates that the From header field is not used for determination of the originating party identity in OIP service.

1 – Indicates that the identity provided within the From header field is used for determination of the originating party identity in OIP service, regardless the presence or absence of the P-Asserted-Identity header field.

The default value is ‘0’.

Use of the FromPreferred leaf is specified in 3GPP TS 24.607 [3].

5.5 /<x>/Ext/

The Ext is an interior node for where the vendor specific information about the OIP and OIR services 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.

– Occurrence: ZeroOrOne

– Format: node

– Access Types: Get

– Values: N/A

5.6 /<X>/SNPN_Configuration

This interior node contains configuration parameters regarding a UE operating in SNPN access operation mode.

– Occurrence: ZeroOrOne

– Format: node

– Access Types: Get, Replace

– Values: N/A

5.7 /<X>/SNPN_Configuration/<X>

This interior node acts as a placeholder for a list of:

a) SNPN identity; and

b) configuration parameters.

NOTE: For each of the elements in the list, a) must be present and at least one parameter of b) needs to appear.

A configuration parameter in an /<X>/SNPN_Configuration/<X> node other than the SNPN_identifier, is applicable when the UE selects an entry of "list of subscriber data" with the SNPN identity of the subscribed SNPN which is the same as the SNPN identity in the SNPN_identifier leaf.

– Occurrence: OneOrMore

– Format: node

– Access Types: Get, Replace

– Values: N/A

5.8 /<X>/SNPN_Configuration/<X>/SNPN_identifier

This leaf indicates the SNPN identity of the subscribed SNPN for which the list of configuration parameters are applicable.

– Occurrence: One

– Format: chr

– Access Types: Get, Replace

– Values: <PLMN><NID>

The PLMN and NID are in the format defined by 3GPP TS 23.003 [4], with each digit of the MCC and MNC of the PLMN and each digit of the assignment mode and NID value of the NID encoded as an ASCII character.

5.9 /<X>/SNPN_Configuration/<X>/FromPreferred

The FromPreferred leaf indicates operator’s originating party identity determination policy.

– Occurrence: One

– Format: bool

– Access Types: Get, Replace

– Values: 0, 1

0 – Indicates that the From header field is not used for determination of the originating party identity in OIP service.

The default value is ‘0’.

Use of the FromPreferred leaf is specified in 3GPP TS 24.607 [3].

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>

<Get/>

</AccessType>

<Description>OIP-OIR Services settings</Description>

<node/>

</DFFormat>

</Occurrence>

<DFTitle>The OIP-OIR Services Management Object.</DFTitle>

<DDFName>urn:oma:mo:ext-3gpp-oipoir:1.0</DDFName>

</DFType>

</DFProperties>

<Node>

<Get/>

</AccessType>

<chr/>

</DFFormat>

</Occurrence>

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

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>FromPreferred</NodeName>

<Get/>

</AccessType>

<bool/>

</DFFormat>

<One/>

</Occurrence>

<DFTitle>This leaf specifies a preference of the operator to enable the presentation of the identity in the From header.</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>SNPN_Configuration</NodeName>

<Get/>

</AccessType>

<node/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>SNPN Configuration.</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

<Node>

<Get/>

</AccessType>

<node/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>SNPN configuration parameters.</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

<Node>

<NodeName>SNPN_identifier</NodeName>

<Get/>

</AccessType>

<chr/>

</DFFormat>

<One/>

</Occurrence>

<Scope>

</Scope>

<DFTitle>Identifier of the SNPN.</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>FromPreferred</NodeName>

<Get/>

</AccessType>

<bool/>

</DFFormat>

<One/>

</Occurrence>

<DFTitle>This leaf specifies a preference of the operator to enable the presentation of the identity in the From header.</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	Meeting	TDoc	CR	Rev	Cat	Subject/Comment	New version
2016-05	CT1#98	C1-162939				Initial proposal	0.0.0
2016-06	CT1#98	C1-162939 C1-162511				Included skeleton from C1-162939 and scope from C1-162511	0.1.0
2016-07	CT1#99	C1-163947				description of the MO parameters and the DDF schema	0.2.0
2016-11						Editorial changes	0.2.1
2016-11	CT-74	CP-160706				Version 1.0.0 created for presentation for information to CT plenary	1.0.0
2017-02	CT1#102	C1-170616 C1-171066				Incorporating correction to DDF and Access type Removal of Editor’s Note for MOID registration to OMNA.	1.1.0
2017-02	CT-75	CP-170160				Version 2.0.0 created for presentation for approval to CT plenary	2.0.0
2017-03	CT-75					Version 14.0.0 created after approval at CT plenary	14.0.0
2018-06	SA-80	–	–	–	–	Update to Rel-15 version (MCC)	15.0.0
2018-12	CT-82	CP-183077	0001		F	Addition of the object identifier in the DDF of the 3GPP Management Object	16.0.0
2022-04	–	–	–	–	–	Update to Rel-17 version (MCC)	17.0.0
2022-06	CT#96	CP-221249	0002	1	B	SNPN configuration for OIP/OIR	17.1.0