BS ISO/IEC 29341-20-11:2017
$215.11
Information technology. UPnP Device Architecture – Audio video device control protocol. Level 4. Connection manager service
Published By | Publication Date | Number of Pages |
BSI | 2017 | 86 |
This service definition is compliant with the UPnP Device Architecture version 1.0 [14].
This service-type enables modeling of streaming capabilities of A/V devices, and binding of those capabilities between devices. Each device that is able to send or receive a stream according to the UPnP AV Architecture will have 1 instance of the ConnectionManager service. This service provides a mechanism for control points to:
-
Perform capability matching between source/server devices and sink/renderer devices,
-
Find information about currently ongoing transfers in the network,
-
Setup and teardown connections between devices (when required by the streaming protocol).
The ConnectionManager service is generic enough to properly abstract different kinds of s treaming mechanisms, such as HTTP- based streaming, RTSP/RTP-based and 1394-based streaming.
The ConnectionManager enables control points to abstract from physical media interconnect technology when making connections. The term ‘stream’ used in this service template refers to both analog and digital data transfer.
PDF Catalog
PDF Pages | PDF Title |
---|---|
2 | National foreword |
8 | Foreword |
15 | 1 Scope 2 Normative references |
18 | 3 Terms, definitions, symbols and abbreviations 3.1 Provisioning terms |
19 | 3.2 Symbols 4 Notations and Conventions 4.1 Notation 4.1.1 Data Types |
20 | 4.1.2 Strings Embedded in Other Strings 4.1.3 Extended Backus-Naur Form 4.1.3.1 Typographic conventions for EBNF |
21 | 4.2 Derived Data Types 4.2.1 Summary 4.2.2 CSV Lists |
22 | 4.3 Management of XML Namespaces in Standardized DCPs |
26 | 4.3.1 Namespace Prefix Requirements |
27 | 4.3.2 Namespace Names, Namespace Versioning and Schema Versioning |
29 | 4.3.3 Namespace Usage Examples 4.4 Vendor-defined Extensions 4.4.1 Vendor-defined Action Names 4.4.2 Vendor-defined State Variable Names |
30 | 4.4.3 Vendor-defined XML Elements and attributes 4.4.4 Vendor-defined Property Names 5 Service Modeling Definitions 5.1 ServiceType |
31 | 5.2 State Variables |
42 | 5.3 Eventing and Moderation 5.4 Actions |
43 | 5.4.2.1 Arguments 5.4.2.2 Dependency on State 5.4.2.3 Effect on State 5.4.2.4 Errors |
44 | 5.4.3.1 Arguments 5.4.3.2 Dependency on State 5.4.3.3 Effect on State |
45 | 5.4.3.4 Errors |
46 | 5.4.4.1 Arguments 5.4.4.2 Dependency on State 5.4.4.3 Effect on State 5.4.4.4 Errors 5.4.5.1 Arguments 5.4.5.2 Dependency on State |
47 | 5.4.5.3 Effect on State 5.4.5.4 Errors 5.4.6.1 Arguments 5.4.6.2 Dependency on State 5.4.6.3 Effect on State |
48 | 5.4.6.4 Errors 5.4.7.1 Arguments 5.4.7.2 Dependency on State 5.4.7.3 Effect on State |
49 | 5.4.7.4 Errors 5.4.8.1 Arguments 5.4.8.2 Dependency on State 5.4.8.3 Effect on State 5.4.8.4 Errors 5.4.9 Common Error Codes |
50 | 6 XML Service Description |
54 | 7 Test |