Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x
Top   in Index   Prev   Next

TS 24.166
3GPP IMS Conferencing
Management Object (MO)

V16.0.0 (PDF)  2018/12  12 p.
V15.0.0  2018/06  12 p.
V14.0.0  2017/03  12 p.
V13.0.0  2015/12  12 p.
V12.0.0  2014/09  11 p.
V11.0.0  2012/09  12 p.
V10.0.0  2011/04  12 p.
V9.2.0  2011/04  12 p.
Rapporteur:
Mr. Monrad, AtleEricsson LM

Content for  TS 24.166  Word version:  16.0.0

Here   Top

1  ScopeWord‑p. 5

This document defines the IMS conferencing management object. The management object is compatible with OMA Device Management protocol specifications, version 1.2 and upwards, and is defined using the OMA DM Device Description Framework as described in the Enabler Release Definition OMA-ERELD_DM-V1_2 [3].
The IMS conferencing management object consists of relevant parameters that can be managed for IMS conferencing capabilities.

2  References

The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
  • References are either specific (identified by date of publication, edition number, version number, etc.) or non specific.
  • For a specific reference, subsequent revisions do not apply.
  • For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1]
TR 21.905: "Vocabulary for 3GPP Specifications".
[2]
TS 24.147: "Conferencing using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3".
[3]
OMA-ERELD-DM-V1_2-20070209-A: "Enabler Release Definition for OMA Device Management, Version 1.2".
[4]
RFC 4579  (August 2006): "Session Initiation Protocol Call Control - Conferencing for User Agents".
Up

3  Definitions and abbreviations

3.1  Definitions

For the purposes of the present document, the terms and definitions given in TR 21.905 apply.
 
The following terms and definitions given in RFC 4579 apply:
Conference Factory URI

3.2  Abbreviations

For the purposes of the present document, the following abbreviations apply:
CN
Core Network
DDF
Device Description Framework
DM
Device Management
IMS
IP Multimedia core network Subsystem
IP
Internet Protocol
MO
Management Object
OMA
Open Mobile Alliance
SIP
Session Initiation Protocol
UE
User Equipment

4  IMS conferencing management objectWord‑p. 6

The IMS conferencing management object is used to manage configuration settings of the UE for IMS conferencing. The management object covers parameters for IMS conferencing related capabilities. The management object enables the management of the settings on behalf of the end user.
The Management Object Identifier is:
urn:oma:mo:ext-3gpp-conf:1.0
 
Protocol compatibility:
This MO is compatible with OMA DM 1.2.
(not reproduced yet)
Figure 1: The 3GPP Conferencing Management Object
Up

5  Management object parameters

5.1  General

This clause describes the parameters for the IMS conferencing management object.

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
  • Values: N/A
The interior node is mandatory if the UE supports one or more IMS conferencing capabilities. Support for a UE is defined by the related roles as defined by the related IMS conferencing service.

5.3  /<X>/Name

The Name leaf is a name for the conferencing settings.
  • Occurrence: ZeroOrOne
  • Format: chr
  • Access Types: Get
  • Values: <User displayable name>

5.4  /<X>/Conf_Factory_URIWord‑p. 7

The Conf_Factory_URI leaf defines a Conference Factory URI as defined by RFC 4579 that is supported by a subscriber's network as described in TS 24.147.
  • Occurrence: ZeroOrOne
  • Format: chr
  • Access Types: Get, Replace
  • Values: <A Conference Factory URI>

5.5  /<X>/Ext

The Ext is an interior node for where the vendor specific information about the IMS conferencing management 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

A  Management object DDFWord‑p. 8

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> IMS conferencing </NodeName>
  <DFProperties>
   <AccessType>
    <Get/>
   </AccessType>
   <Description>IMS conferencing configuration parameters</Description>
   <DFFormat>
    <node/>
   </DFFormat>
   <Occurrence>
    <OneOrMore/>
   </Occurrence>
   <Scope>
    <Permanent/>
   </Scope>
   <DFTitle>The IMS conferencing Management Object.</DFTitle>
   <DFType>
    <DDFName>urn:oma:mo:ext-3gpp-conf:1.0</DDFName>
   </DFType>
  </DFProperties>
  <Node>
   <NodeName>Conference_Factory_URI</NodeName>
   <DFProperties>
    <AccessType>
     <Get/>
     <Replace/>
    </AccessType>
    <DFFormat>
     <chr/>
    </DFFormat>
    <Occurrence>
     <ZeroOrOne/>
    </Occurrence>
    <Scope>
     <Dynamic/>
    </Scope>
    <DFTitle>The Confernece Factory URI.</DFTitle>
    <DFType>
     <MIME>text/plain</MIME>
    </DFType>
   </DFProperties>
  </Node>
  <Node>
   <NodeName>Ext</NodeName>
   <!-- The Extension node starts here. -->
   <DFProperties>
    <AccessType>
     <Get/>
     <Replace/>
    </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>
Up

$  Change historyWord‑p. 9


Up   Top