5 MO configuration parameters
24.2753GPPManagement Object (MO) for Basic Communication Part (BCP) of IMS Multimedia Telephony (MMTEL) communication serviceRelease 17TS
5.1 General
This clause describes the configuration parameters for the MO for BCP of MMTEL communication service.
5.2 Node: /<X>
This interior node acts as a placeholder for one or more accounts for a fixed node.
– Occurrence: OneOrMore
– Format: node
– Access Types: Get, Replace
– Values: N/A
The interior node is mandatory for a UE supporting the UE role specified in 3GPP TS 24.173 [3].
NOTE: One node is normally used. More nodes are only used in case the terminal supports multiple UICCs.
Child nodes of this interior node which are not defined in this version of the present document are ignored.
5.3 /<X>/Name
This leaf is a name for the settings for BCP of MMTEL communication service.
– Occurrence: ZeroOrOne
– Format: chr
– Access Types: Get, Replace
– Values: <User displayable name>
5.4 /<X>/Timer_RequestTimeout
The Timer_RequestTimeout leaf defines the time between sending of an initial INVITE request and receipt of any SIP response.
– Occurrence: One
– Format: int
– Access Types: Get, Replace
– Values: <The time for INVITE request timeout>
The Timer_RequestTimeout leaf is the time between sending from the UE the initial INVITE request and the receptions of any SIP responce. The timer value shall be given in seconds. The configurable value is between 5 and 15 seconds referring to 3GPP TS 24.173 [3]. The Timer_RequestTimeout is a 16 bits unsigned integer.
5.5 /<X>/Ext/
The Ext is an interior node for where the vendor specific information about the 3GPP-IMS 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
– Values: N/A
5.6 /<X>/3GPP_PS_data_off
The interior node contains configuration parameters for 3GPP PS data off.
– Occurrence: ZeroOrOne
– Format: node
– Access Types: Get, Replace
– Values: N/A
5.7 /<X>/3GPP_PS_data_off/MMTEL_voice_exempt
The leaf indicates whether the MMTEL voice is a 3GPP PS data off exempt service.
– Occurrence: One
– Format: bool
– Access Types: Get, Replace
– Values: 0, 1
0 – Indicates that the MMTEL voice is not a 3GPP PS data off exempt service.
1 – Indicates that the MMTEL voice is a 3GPP PS data off exempt service.
NOTE: This MO is used when the UE is in the home PLMN or the EHPLMN, or the UE is in the VPLMN and the MMTEL_voice_roaming_exempt node is not configured.
5.7a /<X>/3GPP_PS_data_off/MMTEL_voice_roaming_exempt
The leaf indicates whether the MMTEL voice is a 3GPP PS data off exempt service when the UE is in the VPLMN.
– Occurrence: ZeroOrOne
– Format: bool
– Access Types: Get, Replace
– Values: 0, 1
0 – Indicates that the MMTEL voice is not a 3GPP PS data off roaming exempt service.
1 – Indicates that the MMTEL voice is a 3GPP PS data off roaming exempt service.
5.8 /<X>/3GPP_PS_data_off/MMTEL_video_exempt
The leaf indicates whether the MMTEL video is a 3GPP PS data off exempt service.
– Occurrence: One
– Format: bool
– Access Types: Get, Replace
– Values: 0, 1
0 – Indicates that the MMTEL video is not a 3GPP PS data off exempt service.
1 – Indicates that the MMTEL video is a 3GPP PS data off exempt service.
NOTE: This MO is used when the UE is in the home PLMN or the EHPLMN, or the MMTEL_video_roaming_exempt node is not configured when the UE is in the VPLMN.
5.8a /<X>/3GPP_PS_data_off/MMTEL_video_roaming_exempt
The leaf indicates whether the MMTEL video is a 3GPP PS data off exempt service when the UE is in the VPLMN.
– Occurrence: ZeroOrOne
– Format: bool
– Access Types: Get, Replace
– Values: 0, 1
0 – Indicates that the MMTEL video is not a 3GPP PS data off roaming exempt service.
1 – Indicates that the MMTEL video is a 3GPP PS data off roaming exempt service.
5.9 /<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.10 /<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.11 /<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 [6], 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.12 /<X>/SNPN_Configuration/<X>/Timer_RequestTimeout
The Timer_RequestTimeout leaf defines the time between sending of an initial INVITE request and receipt of any SIP response.
– Occurrence: One
– Format: int
– Access Types: Get, Replace
– Values: <The time for INVITE request timeout>
The Timer_RequestTimeout leaf is the time between sending from the UE the initial INVITE request and the receptions of any SIP responce. The timer value shall be given in seconds. The configurable value is between 5 and 15 seconds referring to 3GPP TS 24.173 [3]. The Timer_RequestTimeout is a 16 bits unsigned integer.
5.13 /<X>/SNPN_Configuration/<X>/3GPP_PS_data_off
The interior node contains configuration parameters for 3GPP PS data off.
– Occurrence: ZeroOrOne
– Format: node
– Access Types: Get, Replace
– Values: N/A
5.14 /<X>/SNPN_Configuration/<X>/3GPP_PS_data_off/
MMTEL_voice_exempt
The leaf indicates whether the MMTEL voice is a 3GPP PS data off exempt service.
– Occurrence: One
– Format: bool
– Access Types: Get, Replace
– Values: 0, 1
0 – Indicates that the MMTEL voice is not a 3GPP PS data off exempt service.
1 – Indicates that the MMTEL voice is a 3GPP PS data off exempt service.
NOTE: This MO is used when the UE is in a subscribed SNPN, or the UE is in a non-subscribed SNPN and the MMTEL_voice_non-subscribed_exempt node is not configured.
5.15 /<X>/SNPN_Configuration/<X>/3GPP_PS_data_off/
MMTEL_voice_non-subscribed_exempt
The leaf indicates whether the MMTEL voice is a 3GPP PS data off exempt service when the UE is in a non-subscribed SNPN.
– Occurrence: ZeroOrOne
– Format: bool
– Access Types: Get, Replace
– Values: 0, 1
0 – Indicates that the MMTEL voice is not a 3GPP PS data off non-subscribed exempt service.
1 – Indicates that the MMTEL voice is a 3GPP PS data off non-subscribed exempt service.
5.16 /<X>/SNPN_Configuration/<X>/3GPP_PS_data_off/
MMTEL_video_exempt
The leaf indicates whether the MMTEL video is a 3GPP PS data off exempt service.
– Occurrence: One
– Format: bool
– Access Types: Get, Replace
– Values: 0, 1
0 – Indicates that the MMTEL video is not a 3GPP PS data off exempt service.
1 – Indicates that the MMTEL video is a 3GPP PS data off exempt service.
NOTE: This MO is used when the UE is in a subscribed SNPN, or the MMTEL_video_non-subscribed_exempt node is not configured when the UE is in the non-subscribed SNPN.
5.17 /<X>/SNPN_Configuration/<X>/3GPP_PS_data_off/
MMTEL_video_non-subscribed_exempt
The leaf indicates whether the MMTEL video is a 3GPP PS data off exempt service when the UE is in a non-subscribed SNPN.
– Occurrence: ZeroOrOne
– Format: bool
– Access Types: Get, Replace
– Values: 0, 1
0 – Indicates that the MMTEL video is not a 3GPP PS data off non-subscribed exempt service.
1 – Indicates that the MMTEL video is a 3GPP PS data off non-subscribed exempt service.
Annex A (informative):
DDF of MO for BCP of MMTEL communication service
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">
<MgmtTree>
<VerDTD>1.2</VerDTD>
<Man>–The device manufacturer–</Man>
<Mod>–The device model–</Mod>
<Node>
<NodeName/>
<DFProperties>
<AccessType>
<Get/>
<Replace/>
</AccessType>
<Description>Configuration parameters for BCP of MMTEL communication service</Description>
<DFFormat>
<node/>
</DFFormat>
<Occurrence>
<OneOrMore/>
</Occurrence>
<Scope>
<Permanent/>
</Scope>
<DFTitle>The Management Object (MO) for Basic Communication Part (BCP) of IMS Multimedia Telephony(MMTEL) communication service.</DFTitle>
<DFType>
<DDFName>urn:oma:mo:ext-3gpp-bcp:1.0</DDFName>
</DFType>
</DFProperties>
<Node>
<NodeName>Name</NodeName>
<DFProperties>
<AccessType>
<Get/>
<Replace/>
</AccessType>
<DFFormat>
<chr/>
</DFFormat>
<Occurrence>
<ZeroOrOne/>
</Occurrence>
<Scope>
<Dynamic/>
</Scope>
<DFTitle>The name for BCP of MMTEL communication service.</DFTitle>
<DFType>
<MIME>text/plain</MIME>
</DFType>
</DFProperties>
</Node>
<Node>
<NodeName>Timer_RequestTimeout</NodeName>
<DFProperties>
<AccessType>
<Get/>
<Replace/>
</AccessType>
<DFFormat>
<int/>
</DFFormat>
<Occurrence>
<One/>
</Occurrence>
<Scope>
<Permanent/>
</Scope>
<DFTitle>Timer RequestTimeout.</DFTitle>
<DFType>
<MIME>text/plain</MIME>
</DFType>
</DFProperties>
</Node>
<Node>
<NodeName>3GPP_PS_data_off</NodeName>
<DFProperties>
<AccessType>
<Get/>
<Replace/>
</AccessType>
<DFFormat>
<node/>
</DFFormat>
<Occurrence>
<ZeroOrOne/>
</Occurrence>
<Scope>
<Dynamic/>
</Scope>
<DFTitle>Configuration parameters for 3GPP PS data off.</DFTitle>
<DFType>
<DDFName/>
</DFType>
</DFProperties>
<Node>
<NodeName>MMTEL_voice_exempt</NodeName>
<DFProperties>
<AccessType>
<Get/>
<Replace/>
</AccessType>
<DFFormat>
<bool/>
</DFFormat>
<Occurrence>
<One/>
</Occurrence>
<Scope>
<Dynamic/>
</Scope>
<DFTitle>Whether the MMTEL voice is a 3GPP PS data off exempt service.</DFTitle>
<DFType>
<MIME>text/plain</MIME>
</DFType>
</DFProperties>
</Node>
<Node>
<NodeName>MMTEL_voice_roaming_exempt</NodeName>
<DFProperties>
<AccessType>
<Get/>
<Replace/>
</AccessType>
<DFFormat>
<bool/>
</DFFormat>
<Occurrence>
<ZeroOrOne/>
</Occurrence>
<Scope>
<Dynamic/>
</Scope>
<DFTitle>Whether the MMTEL voice is a 3GPP PS data off roaming exempt service.</DFTitle>
<DFType>
<MIME>text/plain</MIME>
</DFType>
</DFProperties>
</Node>
<Node>
<NodeName>MMTEL_video_exempt</NodeName>
<DFProperties>
<AccessType>
<Get/>
<Replace/>
</AccessType>
<DFFormat>
<bool/>
</DFFormat>
<Occurrence>
<One/>
</Occurrence>
<Scope>
<Dynamic/>
</Scope>
<DFTitle>Whether the MMTEL video is a 3GPP PS data off exempt service.</DFTitle>
<DFType>
<MIME>text/plain</MIME>
</DFType>
</DFProperties>
</Node>
<Node>
<NodeName>MMTEL_video_roaming_exempt</NodeName>
<DFProperties>
<AccessType>
<Get/>
<Replace/>
</AccessType>
<DFFormat>
<bool/>
</DFFormat>
<Occurrence>
<ZeroOrOne/>
</Occurrence>
<Scope>
<Dynamic/>
</Scope>
<DFTitle>Whether the MMTEL video is a 3GPP PS data off roaming exempt service.</DFTitle>
<DFType>
<MIME>text/plain</MIME>
</DFType>
</DFProperties>
</Node>
</Node>
<Node>
<NodeName>SNPN_Configuration</NodeName>
<DFProperties>
<AccessType>
<Get/>
<Replace/>
</AccessType>
<DFFormat>
<node/>
</DFFormat>
<Occurrence>
<ZeroOrOne/>
</Occurrence>
<Scope>
<Permanent/>
</Scope>
<DFTitle>SNPN Configuration.</DFTitle>
<DFType>
<MIME>text/plain</MIME>
</DFType>
</DFProperties>
<Node>
<NodeName/>
<DFProperties>
<AccessType>
<Get/>
</AccessType>
<DFFormat>
<node/>
</DFFormat>
<Occurrence>
<OneOrMore/>
</Occurrence>
<Scope>
<Dynamic/>
</Scope>
<DFTitle>SNPN configuration parameters.</DFTitle>
<DFType>
<MIME>text/plain</MIME>
</DFType>
</DFProperties>
<Node>
<NodeName>Timer_RequestTimeout</NodeName>
<DFProperties>
<AccessType>
<Get/>
<Replace/>
</AccessType>
<DFFormat>
<int/>
</DFFormat>
<Occurrence>
<One/>
</Occurrence>
<Scope>
<Permanent/>
</Scope>
<DFTitle>Timer RequestTimeout.</DFTitle>
<DFType>
<MIME>text/plain</MIME>
</DFType>
</DFProperties>
</Node>
<Node>
<NodeName>SNPN_identifier</NodeName>
<DFProperties>
<AccessType>
<Get/>
<Replace/>
</AccessType>
<DFFormat>
<chr/>
</DFFormat>
<Occurrence>
<One/>
</Occurrence>
<Scope>
<Permanent/>
</Scope>
<DFTitle>Identifier of the SNPN.</DFTitle>
<DFType>
<MIME>text/plain</MIME>
</DFType>
</DFProperties>
</Node>
<Node>
<NodeName>3GPP_PS_data_off</NodeName>
<DFProperties>
<AccessType>
<Get/>
<Replace/>
</AccessType>
<DFFormat>
<node/>
</DFFormat>
<Occurrence>
<ZeroOrOne/>
</Occurrence>
<Scope>
<Dynamic/>
</Scope>
<DFTitle>Configuration parameters for 3GPP PS data off.</DFTitle>
<DFType>
<DDFName/>
</DFType>
</DFProperties>
<Node>
<NodeName>MMTEL_voice_exempt</NodeName>
<DFProperties>
<AccessType>
<Get/>
<Replace/>
</AccessType>
<DFFormat>
<bool/>
</DFFormat>
<Occurrence>
<One/>
</Occurrence>
<Scope>
<Dynamic/>
</Scope>
<DFTitle>Whether the MMTEL voice is a 3GPP PS data off exempt service.</DFTitle>
<DFType>
<MIME>text/plain</MIME>
</DFType>
</DFProperties>
</Node>
<Node>
<NodeName>MMTEL_voice_non-subscribed_exempt</NodeName>
<DFProperties>
<AccessType>
<Get/>
<Replace/>
</AccessType>
<DFFormat>
<bool/>
</DFFormat>
<Occurrence>
<ZeroOrOne/>
</Occurrence>
<Scope>
<Dynamic/>
</Scope>
<DFTitle>Whether the MMTEL voice is a 3GPP PS data off non-subscribed exempt service.</DFTitle>
<DFType>
<MIME>text/plain</MIME>
</DFType>
</DFProperties>
</Node>
<Node>
<NodeName>MMTEL_video_exempt</NodeName>
<DFProperties>
<AccessType>
<Get/>
<Replace/>
</AccessType>
<DFFormat>
<bool/>
</DFFormat>
<Occurrence>
<One/>
</Occurrence>
<Scope>
<Dynamic/>
</Scope>
<DFTitle>Whether the MMTEL video is a 3GPP PS data off exempt service.</DFTitle>
<DFType>
<MIME>text/plain</MIME>
</DFType>
</DFProperties>
</Node>
<Node>
<NodeName>MMTEL_video_non-subscribed_exempt</NodeName>
<DFProperties>
<AccessType>
<Get/>
<Replace/>
</AccessType>
<DFFormat>
<bool/>
</DFFormat>
<Occurrence>
<ZeroOrOne/>
</Occurrence>
<Scope>
<Dynamic/>
</Scope>
<DFTitle>Whether the MMTEL video is a 3GPP PS data off non-subscribed exempt s ervice.</DFTitle>
<DFType>
<MIME>text/plain</MIME>
</DFType>
</DFProperties>
</Node>
</Node>
</Node>
</Node>
<Node>
<NodeName>Ext</NodeName>
<!– The Extension node starts here. –>
<DFProperties>
<AccessType>
<Get/>
</AccessType>
<DFFormat>
<node/>
</DFFormat>
<Occurrence>
<ZeroOrOne/>
</Occurrence>
<Scope>
<Dynamic/>
</Scope>
<DFTitle>A collection of all Extension objects.</DFTitle>
<DFType>
<DDFName/>
</DFType>
</DFProperties>
</Node>
</Node>
</MgmtTree>
Annex B (informative):
Change history
Change history |
|||||||
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
2016-11 |
Description of the new MO. |
0.1.0 |
|||||
2016-11 |
CT-74 |
CP-160780 |
Version 1.0.0 created for presentation for information to CT plenary. |
1.0.0 |
|||
2016-12 |
CT-74 |
CP-160830 |
Version 1.0.1 (with TS-number added) created for presentation for information to CT plenary. |
1.0.1 |
|||
2017-01 |
CT1-101BIS |
C1-170328 |
Version 1.1.0 created for adding MMTEL voice and MMTEL video configuration for PS data off |
1.1.0 |
|||
2017-02 |
CT1-102 |
C1-170602 |
Version 1.2.0 created to remove editor’s note for MO identifier (C1-170602) and to remove additional line |
1.2.0 |
|||
2017-02 |
CT-75 |
CP-170159 |
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 CT75 |
14.0.0 |
||||
2018-06 |
CT-80 |
CP-181074 |
0001 |
2 |
B |
MMTEL voice and MMTEL video configuration for 3GPP PS Data Off2 |
15.0.0 |
2018-12 |
CT-82 |
CP-183077 |
0002 |
F |
Addition of the object identifier in the DDF of the 3GPP Management Object |
16.0.0 |
|
2022-03 |
CT-95e |
CP-220237 |
0003 |
1 |
B |
SNPN configuration of MMTel basic communication |
17.0.0 |