🔥🔥 Don’t Miss Out on Our End of Autumn Sale. If you have any questions, feel free to click the bottom right corner to contact our customer service..

Concat us[email protected]
Shopping Cart

No products in the cart.

🔍
BS ISO/IEC 29341-26-16:2017

BS ISO/IEC 29341-26-16:2017

$189.07

Information technology. UPnP Device Architecture – Telephony device control protocol. Level 2. Presence service

Published By Publication Date Number of Pages
BSI 2017 50
PDF Format Searchable Printable Preview Now
Guaranteed Safe Checkout
Category:

If you have any questions, feel free to reach out to our online customer service team by clicking on the bottom right corner. We’re here to assist you 24/7.
Email:[email protected]

This service definition is compliant with the [1]. It defines a service type referred to herein as Presence service.

The Presence service is a UPnP service that allows control points, or better known as Telephony Control Points (TelCP), to manage presence information through a Telephony Server (TS) device or a Telephony Client (TC) device (in the role of UPnP server device for Presence service). This service provides control points with the following functionality:

  • Presence of contacts, access the presence information of contacts, as provided by the UPnP Telephony Server device. Contacts referenced by the Presence service may be managed via PhoneManagement service and the Phone Data Model.

  • Managing presence information, update the presence status stored in the TS;

This service does not provide the following functionality:

  • To update the presence status of the local UPnP network, from the UPnP server device to remote presence servers (i.e. outside the local UPnP network).

  • To retrieve the presence information of contacts from remote presence servers (i.e. outside the local UPnP network).

When the features provided by the Presence service are associated to the PhoneManagement features, then an integrated management of the address book and the presence of contacts in the address book can be delivered.

PDF Catalog

PDF Pages PDF Title
2 National foreword
7 Foreword
15 1 Scope
2 Normative references
16 3 Terms, definitions, symbols and abbreviated terms
3.1 Provisioning terms
17 3.2 Symbols
3.3 General terms
3.4 Abbreviated terms
4 Notations and conventions
4.1 Text conventions
18 4.1.1 Data Types
4.2 Vendor-defined Extensions
5 Service Modeling Definitions
5.1 Service Type
5.2 Presence Service Architecture
19 5.3 State Variables
5.3.1 State Variable Overview
20 5.3.2.1 XML Schema Definition
5.3.2.2 Description of fields in the UserPresenceInfo structure
21 5.3.3.1 XML Schema Definition
5.3.3.2 Description of fields in the PresenceOfContactsUpdate structure
23 5.3.4.1 XML Schema Definition
5.3.4.2 Description of fields in the A_ARG_TYPE_UserPresenceInfo structure
24 5.3.5.1 XML Schema Definition
5.3.5.2 Description of fields in the A_ARG_TYPE_PresenceOfContactsList structure
25 5.3.6.1 Description of fields in the A_ARG_TYPE_ContactId
26 5.3.9.1 Description of fields in the Watcher
27 5.3.10.1 Description of fields in the A_ARG_TYPE_WatcherList
28 5.4 Eventing and Moderation
5.4.1 Eventing of UserPresenceInfo
29 5.4.2 Eventing of PresenceOfContactsUpdate
5.4.3 Eventing of Watcher
5.5 Actions
5.5.1.1 Arguments
5.5.1.2 Argument Descriptions
30 5.5.1.3 Service Requirements
5.5.1.4 Control Point Requirements When Calling The Action
5.5.1.5 Dependency on Device State
5.5.1.6 Effect on Device State
5.5.1.7 Errors
5.5.2.1 Arguments
5.5.2.2 Argument Descriptions
5.5.2.3 Service Requirements
5.5.2.4 Control Point Requirements When Calling The Action
31 5.5.2.5 Dependency on Device State
5.5.2.6 Effect on Device State
5.5.2.7 Errors
5.5.3.1 Arguments
5.5.3.2 Argument Descriptions
5.5.3.3 Service Requirements
5.5.3.4 Control Point Requirements When Calling The Action
5.5.3.5 Dependency on Device State
5.5.3.6 Effect on Device State
32 5.5.3.7 Errors
5.5.4.1 Arguments
5.5.4.2 Argument Descriptions
5.5.4.3 Service Requirements
5.5.4.4 Control Point Requirements When Calling The Action
5.5.4.5 Dependency on Device State
5.5.4.6 Effect on Device State
5.5.4.7 Errors
33 5.5.5.1 Arguments
5.5.5.2 Argument Descriptions
5.5.5.3 Service Requirements
5.5.5.4 Control Point Requirements When Calling The Action
5.5.5.5 Dependency on Device State
5.5.5.6 Effect on Device State
5.5.5.7 Errors
34 5.5.6.1 Arguments
5.5.6.2 Argument Descriptions
5.5.6.3 Service Requirements
5.5.6.4 Control Point Requirements When Calling The Action
5.5.6.5 Dependency on Device State
5.5.6.6 Effect on Device State
35 5.5.6.7 Errors
5.5.7.1 Arguments
5.5.7.2 Argument Descriptions
5.5.7.3 Service Requirements
5.5.7.4 Control Point Requirements When Calling The Action
36 5.5.7.5 Dependency on Device State
5.5.7.6 Effect on Device State
5.5.7.7 Errors
5.5.8 Error Code Summary
5.6 Service Behavioral Model
6 XML Service Description

Related products

BS ISO/IEC 29341-26-16:2017
$189.07