{"id":343813,"date":"2024-10-20T00:08:16","date_gmt":"2024-10-20T00:08:16","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bs-en-62676-2-22014\/"},"modified":"2024-10-25T23:27:42","modified_gmt":"2024-10-25T23:27:42","slug":"bs-en-62676-2-22014","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bs-en-62676-2-22014\/","title":{"rendered":"BS EN 62676-2-2:2014"},"content":{"rendered":"
IEC 62676-2-2:2013 specifies a compliant IP video protocol based on HTTP and REST services. Video transmission devices are often equipped with web servers that respond to HTTP requests. The HTTP response may contain XML content (for GET actions), XML response information (for SET actions), or various text\/binary content (for retrieval of configuration data, etc.). REST is an approach to creating services that expose all information as resources in a uniform way. A video transmission device supporting compliance to the requirements of this standard based on HTTP and REST Services as described in this document is declared as compatible to \u00b4IEC 62676-2 HTTP and REST interoperability.\u00b4<\/p>\n
PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
---|---|---|---|---|---|---|---|
7<\/td>\n | English CONTENTS <\/td>\n<\/tr>\n | ||||||
9<\/td>\n | INTRODUCTION <\/td>\n<\/tr>\n | ||||||
10<\/td>\n | 1 Scope 2 Normative references <\/td>\n<\/tr>\n | ||||||
11<\/td>\n | 3 Abbreviations <\/td>\n<\/tr>\n | ||||||
13<\/td>\n | 4 Overview 5 Design considerations 5.1 General <\/td>\n<\/tr>\n | ||||||
14<\/td>\n | 5.2 REST overview 5.3 Conformance 5.3.1 General 5.3.2 Minimum API set 5.3.3 XML requirements <\/td>\n<\/tr>\n | ||||||
15<\/td>\n | 5.3.4 Protocol requirements 5.4 HTTP methods and REST 5.5 HTTP status codes and REST Tables Table 1 \u2013 HTTP methods <\/td>\n<\/tr>\n | ||||||
16<\/td>\n | Table 2 \u2013 HTTP status codes and REST <\/td>\n<\/tr>\n | ||||||
17<\/td>\n | 5.6 Unique identifiers 5.7 ID encoding <\/td>\n<\/tr>\n | ||||||
18<\/td>\n | 6 Architecture and namespace Figures Figure 1 \u2013 PSIA service architecture example <\/td>\n<\/tr>\n | ||||||
19<\/td>\n | Table 3 \u2013 Resource names Table 4 \u2013 Service URLs <\/td>\n<\/tr>\n | ||||||
20<\/td>\n | 7 System flow 7.1 General <\/td>\n<\/tr>\n | ||||||
21<\/td>\n | 7.2 Service discovery 7.3 Persistent connections <\/td>\n<\/tr>\n | ||||||
22<\/td>\n | 7.4 Authentication 7.5 Access restrictions <\/td>\n<\/tr>\n | ||||||
23<\/td>\n | 7.6 Setting configurations 7.7 Getting configurations <\/td>\n<\/tr>\n | ||||||
24<\/td>\n | 7.8 Getting capabilities <\/td>\n<\/tr>\n | ||||||
25<\/td>\n | 7.9 Uploading data 7.10 Receiving data 7.11 Operations <\/td>\n<\/tr>\n | ||||||
26<\/td>\n | 7.12 Diagnostics 7.13 Response status 7.13.1 General 7.13.2 Status code Table 5 \u2013 HTTP requests <\/td>\n<\/tr>\n | ||||||
27<\/td>\n | 7.13.3 Status string 7.13.4 ID 7.14 Processing rules 8 XML modeling 8.1 File format 8.2 Data structures 8.3 Lists 8.4 Capabilities <\/td>\n<\/tr>\n | ||||||
28<\/td>\n | Table 6 \u2013 Capability attributes <\/td>\n<\/tr>\n | ||||||
29<\/td>\n | 9 Custom services and resources 10 Interface design 10.1 General 10.2 Protocol <\/td>\n<\/tr>\n | ||||||
30<\/td>\n | 10.3 Hostname 10.4 Port 10.5 URI 10.6 Query string 10.7 Resource description <\/td>\n<\/tr>\n | ||||||
31<\/td>\n | 11 Standard resource descriptions 11.1 General 11.2 index 11.3 indexr <\/td>\n<\/tr>\n | ||||||
32<\/td>\n | 11.4 description 11.5 capabilities 11.6 Schemas 11.6.1 General <\/td>\n<\/tr>\n | ||||||
33<\/td>\n | 11.6.2 ResourceDescription 11.6.3 ResourceList 11.6.4 QueryStringParameterList 11.6.5 responseStatus <\/td>\n<\/tr>\n | ||||||
34<\/td>\n | 11.6.6 service.xsd <\/td>\n<\/tr>\n | ||||||
37<\/td>\n | Annex A (normative) IP Media Device API Specification Version 1.0 <\/td>\n<\/tr>\n | ||||||
111<\/td>\n | Figure A.1 \u2013 Motion detection grid with two detection regions <\/td>\n<\/tr>\n | ||||||
125<\/td>\n | Bibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Video surveillance systems for use in security applications – Video transmission protocols. IP interoperability implementation based on HTTP and REST services<\/b><\/p>\n |