We use cookies to give you the best experience and to help improve our website

Find out what cookies we use and how to disable them

79/635/NP, PNW 79-635: Alarm systems - Video Surveillance Systems (VSS) for use in security applications - Part 2-11: Interop profiles for VMS- and cloud VSaaS-systems for safe-cities and law-enforceme

Scope

This standard shall define requirement profiles for Video Management- (VMS) and Cloud Video-Surveillance-as-a- Service (VSaaS) Systems to standardize interfacing with third-party

- security operations centers,

- professional remote video monitoring,

- remote access by law-enforcement and authorities, for sharing their video resources.

Based on the IP video features offered by the IEC 62676-2 protocol standard series, such as

- live video-, audio- and metadata-streaming,

- video-replay, -export and forensic metadata search

- alarm eventing, camera control incl. PTZ,

- device health status checks,

- interconnections incl. cloud- and IoT-enabled connectivity,

hierarchical requirement profiles of VMS feature-sets are defined for local and remote video access. This allows sharing of video not only within the organization owning and operating the VS System, but as well interorganizationally e.g by providing access to authorities in charge of public security.

This standard defines minimum VMS interoperability levels from video export to exclusive video control from remote e.g. in crisis situations, in order to support regulating governmental organizations, national law enforcement, private security service companies, public transport operators and other authorities.

This standard will specifiy as well requirements for platform independent Video clients, such as HTML5 browser based, to give temporary access to certain sites without any special technical prerequsites, SW-installations, network and firewall configurations as required by law-enforcement of different countries e.g. in Germany.

This shall allow to forward alarm events incl. access to the associated live video and incident recordings to the concerned police-departments and allow only the them access to the incident site. Different levels of access will be defined in the specifications incl. the exlusive or shared handling of video and sites.

Detailed functions offered in local and remote control rooms shall be accordingly categorized in these Interop profiles.

The standard will provide requirements for the geolocation information of sensor devices, how, when (in absolute time) and where the data on location and field of view (FoV) is produced, stored and visualized in interactive site-, building- and CAD-maps. This applies to fixed, moving, cloud connected surveillances cameras, in- and outdoor, on-board (of cars, busses, trains, …), mobile, drone- or body-worn-cameras (BWC), with local video storage and mobile streaming capabilities, possibly through wireless networks. Available protocols shall be referenced and where no format or protocol standards are available, a detailed requirement specification is given to initiate such technical standardization in a second step.

For forensic metadata search an example use case is: “Red car with license plate X, speeding at 60kph” within a certain area and time range of video recordings"

This standard is not limited to image capturing devices such as cameras offering multiple types of information, but can be applied to other sensors

This standard is intended to define the common technical basis for national regulations requiring interorganizational remote-, local- or on-site access e.g. by authorities to VSS, possibly granted only temporary e.g. in case of emergancy situations. As such, this standard is ecpected to supersede ISO 22311 standard (Societal Security — Video-surveillance — Export interoperability).

This standard defines as well the requirements on the remote client & system configuration integrity to maintain anytime full functional video access e.g. by means of camera-, NVR- and connection-health monitoring.

Additionally, standardized alarm, condition and video content analytic (VCA) event codes are introduced to allow seamless integration into 3rd party security management systems (SMS)

The available video metadata formats and attributes are referenced and if needed extended within the available and standarized schemas.

Recommendations are given for the use of VMS in local, wide area and enterprise networks or cloud based VSaaS in public internet and private MPLS environments.

Following is the focus of this specification:

- VMS-Interop profiles from basic to advanced

- geolocation mapping of cameras, sensors and objects

- referencing available IP video standards and file formats - VMS Operator Client Feature Profiles e.g. for remote law-enforcement

This standard does not specify any detailed requirements on application guidance and video observation objectives, on system availability, cyber security, privacy, national and legal constraints, operational procedures, environmental conditions or technical protocols.

Purpose

Today there is a lack in directive standards giving precise requirements for VSS in certain applications involving third parties (and especially the authorities), compared to intrusion or fire detection alarm systems, while video applications are more and more important for public security.

With this standard the national authorities, security system owners and operators are able to exactly define the details of the VSS and it´s interoperation requiremnets by the simple selection of profile levels. This will simplify and hamonize the whole planing, design, procurement, implementation and integration process for all involved parties.

Revision / Replacement of ISO 22311

Comment on proposal

Required form fields are indicated by an asterisk (*) character.


Please email further comments to: debbie.stead@bsigroup.com

Follow standard

You are now following this standard. Weekly digest emails will be sent to update you on the following activities:

You can manage your follow preferences from your Account. Please check your mailbox junk folder if you don't receive the weekly email.

Unfollow standard

You have successfully unsubscribed from weekly updates for this standard.

Error