
ISO 29341:2017
ISO 29341:2017 Information technology – UPnP Device Architecture – Part 26-13: Telephony device control protocol – Level 2 – Phone management service
CDN $0.00
Description
ISO/IEC 29341-26-13:2017 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 Architecture defined in [9].
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.
Edition
1
Published Date
2017-09-13
Status
PUBLISHED
Pages
71
Format 
Secure PDF
Secure – PDF details
- Save your file locally or view it via a web viewer
- Viewing permissions are restricted exclusively to the purchaser
- Device limits - 3
- Printing – Enabled only to print (1) copy
See more about our Environmental Commitment
Abstract
ISO/IEC 29341-26-13:2017 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 Architecture defined in [9].
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.
Previous Editions
Can’t find what you are looking for?
Please contact us at:
Related Documents
-

ISO 80000:2025 Quantities and units – Part 13: Information science and technology
CDN $214.00 Add to cart -

ISO 80004:2011 Nanotechnologies – Vocabulary – Part 7: Diagnostics and therapeutics for healthcare
CDN $124.00 Add to cart -

ISO 80000:2019 Quantities and units – Part 11: Characteristic numbers
CDN $336.00 Add to cart -

ISO 5053:2019 Industrial trucks – Vocabulary – Part 2: Fork arms and attachments
CDN $379.00 Add to cart







