🔥🔥 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-12:2017

BS ISO/IEC 29341-26-12:2017

$215.11

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

Published By Publication Date Number of Pages
BSI 2017 84
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 [1]. It defines a service type referred to herein as Messaging service.

The Messaging service is a UPnP service that allows control points to use the messaging features provided by a Telephony Server (TS) or a Telephony Client (TC).

It provides in the UPnP network the overall se t of messaging capabilities of a phone (e.g., smartphone, IP phone, VoIP gateway, etc.), as the role of a TS. Additionally, or as an alternative, a device with the role of a TC can provide the Messaging service via UPnP Telephony.

This service provides the control points with the following functionalities:

  • Page Mode Messaging (e.g., e-Mail, SMS, MMS, etc.): notification of incoming messages, reading messages, sending a message, deleting a message.

  • Session Mode Messaging (e.g., Instant Messaging, SMS, etc.): notification of incoming messages, retrieving and sending the messages within a session, creating, modifying or closing a messaging session.

  • File transfer session, to transfer the files in near real time.

This service does not provide the following functionalities:

  • Connection to a remote server for sending or receiving the messages (e.g., WAN side);

  • Rendering of message notifications and messages to the end user;

  • Configuring the Messaging service with account for connecting to remote servers;

PDF Catalog

PDF Pages PDF Title
2 National foreword
8 Foreword
15 1 Scope
2 Normative references
16 3 Terms, definitions, symbols and abbreviated terms
18 4 Notations and conventions
4.1 Text conventions
4.2 Data Types
19 4.3 Vendor-defined Extensions
5 Service Modeling Definitions
5.1 Service Type
5.2 Messaging Service Architecture
20 5.3 State Variables
5.3.1 State Variable Overview
21 5.3.2.1 XML Schema Definition
5.3.2.2 Description of fields in the MessagingCapabilities structure
22 5.3.3.1 XML Schema Definition
5.3.3.2 Description of fields in the NewMessages structure
23 5.3.4.1 XML Schema Definition
5.3.4.2 Description of fields in the SessionUpdates structure
27 5.3.10.1 XML Schema Definition
5.3.10.2 Description of fields in the Message structure
29 5.3.11.1 XML Schema Definition
5.3.11.2 Description of fields in the MessageList structure
31 5.3.14.1 XML Schema Definition
5.3.14.2 Description of fields in the RecipientsList structure
32 5.3.15.1 XML Schema Definition
5.3.15.2 Description of fields in the SessionInfo structure
34 5.3.16.1 XML Schema Definition
35 5.3.16.2 Description of fields in the SessionsList structure
36 5.3.20.1 XML Schema Definition
5.3.20.2 Description of fields in the FileInfoList structure
38 5.4 Eventing and Moderation
5.4.1 Eventing of NewMessages
5.4.2 Eventing of SessionUpdates
39 5.5 Actions
40 5.5.1.1 Arguments
5.5.1.2 Argument Descriptions
41 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
42 5.5.2.3 Service Requirements
5.5.2.4 Control Point Requirements When Calling The Action
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
43 5.5.3.5 Dependency on Device State
5.5.3.6 Effect on Device State
5.5.3.7 Errors
5.5.4.1 Arguments
5.5.4.2 Argument Descriptions
44 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
45 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
46 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
47 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
5.5.7.5 Dependency on Device State
5.5.7.6 Effect on Device State
48 5.5.7.7 Errors
5.5.8.1 Arguments
5.5.8.2 Argument Descriptions
5.5.8.3 Service Requirements
49 5.5.8.4 Control Point Requirements When Calling The Action
5.5.8.5 Dependency on Device State
5.5.8.6 Effect on Device State
5.5.8.7 Errors
5.5.9.1 Arguments
5.5.9.2 Argument Descriptions
50 5.5.9.3 Service Requirements
5.5.9.4 Control Point Requirements When Calling The Action
5.5.9.5 Dependency on Device State
5.5.9.6 Effect on Device State
5.5.9.7 Errors
5.5.10.1 Arguments
51 5.5.10.2 Argument Descriptions
5.5.10.3 Service Requirements
5.5.10.4 Control Point Requirements When Calling The Action
5.5.10.5 Dependency on Device State
5.5.10.6 Effect on Device State
5.5.10.7 Errors
5.5.11.1 Arguments
5.5.11.2 Argument Descriptions
52 5.5.11.3 Service Requirements
5.5.11.4 Control Point Requirements When Calling The Action
5.5.11.5 Dependency on Device State
5.5.11.6 Effect on Device State
5.5.11.7 Errors
5.5.12.1 Arguments
5.5.12.2 Argument Descriptions
53 5.5.12.3 Service Requirements
5.5.12.4 Control Point Requirements When Calling The Action
5.5.12.5 Dependency on Device State
5.5.12.6 Effect on Device State
5.5.12.7 Errors
5.5.13.1 Arguments
5.5.13.2 Argument Descriptions
54 5.5.13.3 Service Requirements
5.5.13.4 Control Point Requirements When Calling The Action
5.5.13.5 Dependency on Device State
5.5.13.6 Effect on Device State
5.5.13.7 Errors
5.5.14.1 Arguments
5.5.14.2 Argument Descriptions
5.5.14.3 Service Requirements
55 5.5.14.4 Control Point Requirements When Calling The Action
5.5.14.5 Dependency on Device State
5.5.14.6 Effect on Device State
5.5.14.7 Errors
5.5.15.1 Arguments
5.5.15.2 Argument Descriptions
5.5.15.3 Service Requirements
56 5.5.15.4 Control Point Requirements When Calling The Action
5.5.15.5 Dependency on Device State
5.5.15.6 Effect on Device State
5.5.15.7 Errors
5.5.16.1 Arguments
5.5.16.2 Argument Descriptions
5.5.16.3 Service Requirements
57 5.5.16.4 Control Point Requirements When Calling The Action
5.5.16.5 Dependency on Device State
5.5.16.6 Effect on Device State
5.5.16.7 Errors
5.5.17.1 Arguments
5.5.17.2 Argument Descriptions
5.5.17.3 Service Requirements
5.5.17.4 Control Point Requirements When Calling The Action
58 5.5.17.5 Dependency on Device State
5.5.17.6 Effect on Device State
5.5.17.7 Errors
5.5.18.1 Arguments
5.5.18.2 Argument Descriptions
5.5.18.3 Service Requirements
5.5.18.4 Control Point Requirements When Calling The Action
5.5.18.5 Dependency on Device State
59 5.5.18.6 Effect on Device State
5.5.18.7 Errors
5.5.19 Error Code Summary
60 5.6 Service Behavioral Model
5.6.1 State Diagrams
5.6.1.1 Message Lifecycle
5.6.1.2 Session Lifecycle
61 6 XML Service Description

Related products

BS ISO/IEC 29341-26-12:2017
$215.11