Service Template 2 - upnp.· Service Template Version: ... ConfigurationManagement service for defining

  • View
    212

  • Download
    0

Embed Size (px)

Text of Service Template 2 - upnp.· Service Template Version: ... ConfigurationManagement service for...

  • PhoneManagement:2

    For UPnP Version 1.0

    Status: Standardized DCP (SDCP)

    Date: December 10, 2012

    Document Version: 1.0

    Service Template Version: 2.00

    This Standardized DCP has been adopted as a Standardized DCP by the Steering Committee of the UPnP Forum, pursuant to Section 2.1(c)(ii) of the UPnP Forum Membership Agreement. UPnP Forum Members have rights and licenses defined by Section 3 of the UPnP Forum Membership Agreement to use and reproduce the Standardized DCP in UPnP Compliant Devices. All such use is subject to all of the provisions of the UPnP Forum Membership Agreement.

    THE UPNP FORUM TAKES NO POSITION AS TO WHETHER ANY INTELLECTUAL PROPERTY RIGHTS EXIST IN THE STANDARDIZED DCPS. THE STANDARDIZED DCPS ARE PROVIDED "AS IS" AND "WITH ALL FAULTS". THE UPNP FORUM MAKES NO WARRANTIES, EXPRESS, IMPLIED, STATUTORY, OR OTHERWISE WITH RESPECT TO THE STANDARDIZED DCPS, INCLUDING BUT NOT LIMITED TO ALL IMPLIED WARRANTIES OF MERCHANTABILITY, NON-INFRINGEMENT AND FITNESS FOR A PARTICULAR PURPOSE, OF REASONABLE CARE OR WORKMANLIKE EFFORT, OR RESULTS OR OF LACK OF NEGLIGENCE.

    2012 UPnP Forum. All Rights Reserved.

    Authors a Company

    Yoshiki Nishikawa NTT

    Hiroshi Jinzenji NTT

    Yuji Morinishi NTT

    Hisashi Matsukawa NTT

    Davide Moreo Telecom Italia

    Enrico Grosso Telecom Italia

    Massimo Messore Telecom Italia

    Alessandro De Vincentis Telecom Italia

    Mahfuzur Rahman (Chair) Samsung Electronics

    Mayuresh Patil (Editor) Samsung Electronics

    Jeyoung Maeng Samsung Electronics

    Jooyeol Lee Samsung Electronics

    Yu Zhu Huawei

    Andreas Kraft Deutsche Telekom

    Vivien Helmut Deutsche Telekom

    Fabrice Fontaine France Telecom

    JangW oong Park LGE

  • PhoneManagement:2 2

    Copyright UPnP Forum 2012. All rights reserved.

    Authors a Company

    a The UPnP Forum in no way guarantees the accuracy or completeness of this aut hor list and in no way implies any

    rights for or support from those members listed. This list is not the specif ications contributor list that is kept on

    the UPnP Forums website.

  • PhoneManagement:2 3

    Copyright UPnP Forum 2012. All rights reserved.

    CONTENTS

    1 Scope...................................................................................................................... 3

    2 Normative references ............................................................................................... 4

    3 Terms, definitions, symbols and abbreviated terms..................................................... 5

    4 Notations and conventions ........................................................................................ 6

    4.1 Notation .......................................................................................................... 6

    4.1.1 Data Types ........................................................................................... 6

    4.2 Vendor-defined Extensions ............................................................................... 6

    5 ConfigurationManagement Service Profile .................................................................. 7

    5.1 Service Type ................................................................................................... 7

    5.2 PhoneManagement Architecture ....................................................................... 7

    5.2.1 Phone Management .............................................................................. 7

    5.2.2 Phone Data Model ................................................................................ 8

    5.3 State Variables ................................................................................................ 9

    5.4 Actions ......................................................................................................... 10

    5.4.1 Introduction ........................................................................................ 10

    5.4.2 GetSelectedValues() ........................................................................... 11

    5.4.3 SetValues() ........................................................................................ 11

    5.4.4 CreateInstance() ................................................................................. 11

    5.4.5 DeleteInstance() ................................................................................. 12

    5.4.6 SetAttributes() .................................................................................... 12

    6 XML Service Description......................................................................................... 12

    Annex A (normative) Phone Data Model ....................................................................... 13

    Annex B (informative) Theory of Operation ................................................................... 60

    Annex C (informative) Bibliography .............................................................................. 74

    Figure 1 PhoneManagement v ia CMS and Phone Data Model ....................................... 7

    Figure A.1 Overview of the Phone Data Model ........................................................... 14

    Table 1 State Variables for Eventing ......................................................................... 10

    Table 2 Actions ........................................................................................................ 10

    Table A.1 The Phone Data Model .............................................................................. 15

    1 Scope

    This document specifies the PhoneManagement profile of the ConfigurationManagement Service defined in [7].

    The PhoneManagement profile can be used for managing the configuration of the UPnP TelephonyServer device (i.e. a telephone), with tasks such as managing an address book, configuring the settings of the phone, configuring the ringing modes, checking the battery level of the phone. This profile is compliant with the UPnP Telephony Architectur e defined in [9].

  • PhoneManagement:2 4

    Copyright UPnP Forum 2012. All rights reserved.

    PhoneManagement defines

    A profile of the CMS in order to satisfy the requirements for PhoneManagement (see clause 5).

    The Phone Data Model to perform configuration management of the specific features of a phone (see Annex A) by reusing the CMS data model (see [7], Annex B).

    The ConfigurationManagement service offers a general purpose data model and a set of configuration management operations for retrieving and managing the actual configuration parameters of a device. These features are completely reused from CMS in the PhoneManagement.

    The ConfigurationManagement service defines the functions for manipulating the configuration and status parameters that are exposed by the device hosting the ConfigurationManagement service. These actions and state variables defined in the ConfigurationManagement service are reused in order to manage the configuration parameters of a TelephonyServer device for e.g. phone, defined in the data model of the PhoneManagement.

    The main goal of this specification is to define the data model (called herein as Phone Data Model) for the TelephonyServer device like Phone, according to the rules defined by the ConfigurationManagement service for defining a new data model.

    The Phone Data Model is organized as a hierarchical tree of parameter sets, where each set represent a feature of a TelephonyServer (e.g. address book, ringing modes etc) that can be managed by a TelCP.

    2 Normative references

    The following documents, in whole or in part, are normatively referenced in this document and are indispensable for its application. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies.

    [1] UPnP Device Architecture, version 1.0, UPnP Forum, October 15, 2008. Available at: http://www.upnp.org/specs/arch/UPnP-arch-DeviceArchitecture-v1.0-20081015.pdf. Latest version available at: http://www.upnp.org/specs/arch/UPnP-arch-DeviceArchitecture-v1.0.pdf.

    [2] Data elements and interchange formats Information interchange -- Representation of dates and times, International Standards Organization, December 21, 2000. Available at: ISO 8601:2000.

    [3] IETF RFC 2119, Key words for use in RFCs to Indicate Requirement Levels, S. Bradner, 1997. Available at: http://www.faqs.org/rfcs/rfc2119.html .

    [4] IETF RFC 3339, Date and Time on the Internet: Timestamps, G. Klyne, Clearswift Corporation, C. Newman, Sun Microsystems, July 2002. Available at: http://www.ietf.org/rfc/rfc3339.txt .

    [5] Extensible Markup Language (XML) 1.0 (Third Edition), Franois Yergeau, Tim Bray, Jean Paoli, C. M. Sperberg-McQueen, Eve Maler, eds., W3C Recommendation, February 4, 2004. Available at: http://www.w3.org/TR/2004/REC-xml-20040204.

    http://www.upnp.org/specs/arch/UPnP-arch-DeviceArchitecture-v1.0-20081015.pdfhttp://www.upnp.org/specs/arch/UPnP-arch-DeviceArchitecture-v1.0.pdfhttp://www.upnp.org/specs/arch/UPnP-arch-DeviceArchitecture-v1.0.pdfhttp://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=26780&ICS1=1&ICS2=140&ICS3=30http://www.faqs.org/rfcs/rfc2119.htmlhttp://www.ietf.org/rfc/rfc3339.txthttp://www.w3.org/TR/2004/REC-xml-20040204/

  • PhoneManagement:2 5

    Copyright UPnP Forum 2012. All rights reserved.

    [6] XML Schema Part 2: Data Types, Second Edition, Paul V. Biron, Ashok Malhotra, W3C Recommendation, 28 October 2004. Available at: http://www.w