ONVIF Implementation Conformance Statement for Device Version Panasonic

Transcription

1 ONVIF Implementation onformance Statement for Device Version Panasonic

2 2 ONVIF-2.4.1:2017 Table of ontent 1. SOPE REFERENES NORATIVE REFERENES ONVIF Profile Specification ONVIF Network Interface Specification Set, version INFORATIVE REFERENES TERINOLOGY AND ONVENTIONS ONVENTIONS DEFINITIONS ABBREVIATIONS INTRODUTION WEB SERVIE FRAE WORK WEB SERVIES ERROR HANDLING SEURITY IP ONFIGURATION DEVIE DISOVERY GENERAL ODES OF OPERATION DISOVERY DEFINITIONS REOTE DISOVERY EXTENSIONS DEVIE ANAGEENT APABILITIES NETWORK SYSTE SEURITY INPUT/OUTPUT (I/O) (IF SUPPORTED) AUXILIARY OPERATION (IF SUPPORTETD) ONITORINGEVENTS DEVIEIO SERVIE VIDEOOUTPUTS VIDEOOUTPUTONFIGURATION VIDEOSOURES VIDEOSOUREONFIGURATION AUDIOOUTPUTS AUDIOOUTPUTONFIGURATION AUDIOSOURES AUDIOSOUREONFIGURATION RELAY OUTPUTS DIGITAL INPUTS SERIALPORTS APABILITIES EVENTS IAGING ONFIGURATION IAGING SETTINGS OANDS APABILITIES EVENTS EDIA ONFIGURATION EDIA ONFIGURATION VIDEO ONFIGURATION AUDIO ONFIGURATION Audio streaming (if supported) Audio output (if supported) VIDEO ANALYTIS ONFIGURATION ONVIF_IS_for_Device.doc

3 3 ONVIF-2.4.1: ETADATA ONFIGURATION OTHER STREA ONFIGURATION APABILITIES EVENTS LIVE STREAING EDIA STREA PROTOOL EDIA TRANSPORT RTP RTP for etadata stream RTP JPEG over RTP EDIA ONTROL PROTOOL BAK HANNEL ONNETION PLAYBAK (IF SUPPORTED STORAGE) RTSP DESRIBE RTP HEADER EXTENSION RTP FEATURE TAG INITIATING PLAYBAK REVERSE REPLAY RTSP KEEPALIVE URRENTLY REORDING FOOTAGE END OF FOOTAGE GO TO TIE USE OF REEIVER ONFIGURATION DISPLAY SERVIE EVENT HANDLING BASI NOTIFIATION INTERFAE REAL-TIE PULL-POINT NOTIFIATION INTERFAE NOTIFIATION STREAING INTERFAE OTHERS APABILITIES PTZ ONTROL (IF SUPPORTED) PTZ NODE PTZ ONFIGURATION OVE OPERATION PRESET OPERATIONS (IF SUPPORTED) HOE POSITION OPERATION AUXILIARY OPERATIONS (IF SUPPORTED) PRESET TOURS OPERATIONS PT ONTROL DIRETION ONFIGURATION APABILITIES EVENTS VIDEO ANALYTIS SENE DESRIPTION INTERFAE RULE INTERFAE ANALYTIS ODULES INTERFAE APABILITIES ANALYTIS DEVIE OVERVIEW ANALYTIS ENGINE INPUT VIDEO ANALYTIS ONFIGURATION ANALYTIS ENGINES ANALYTIS ENGINE ONTROL GETANALYTISSTATE OUTPUT STREAING ONFIGURATION APABILITIES SEURITY ONVIF_IS_for_Device.doc

4 4 ONVIF-2.4.1: TRANSPORT LEVEL SEURITY REORDING ONTROL (IF SUPPORTED STORAGE) DYNAI REORDING REORDING ONTROL OANDS APABILITIES EVENTS REORDINGSEARH (IF SUPPORTED STORAGE) OANDS APABILITIES EVENTS ONVIF-REPLAYONTROL (IF SUPPORTED STORAGE) OANDS APABILITIES ATION ENGINE SERVIE ONVIF_IS_for_Device.doc

5 5 ONVIF-2.4.1: Scope The scope of this document is in accordance with the ONVIF ore Specification Version The Implementation onformance Statement might be used for ONVIF interoperability testing. Thus the scope of this document is, to provide our partners with the fundament for ONVIF end-to-end interoperability testing. Another significant intent of this document is also to be used as a base for discussions with our partners to explore any such requirements that might not be clearly defined in the specifications of ONVIF with respect to interoperability. ONVIF_IS_for_Device.doc

6 6 ONVIF-2.4.1: s 2.1. rmative s ONVIF Profile Specification ONVIF Profile A Specification - Release andidate ONVIF Profile Q Specification ONVIF Profile G specification ONVIF Profile Specification ONVIF Profile S Specification ONVIF_IS_for_Device.doc

7 7 ONVIF-2.4.1: ONVIF Network Interface Specification Set, version ore Specification [ore] ONVIF ore Specification Data Format Specification ONVIF Streaming Specification - Export File Format Service Specifications - Access ontrol [Action] Action Engine - Advanced Security 1.pdf [Display] Analytics Device IO Display Door ontrol [Imaging] [PTZ] [Receiver] Imaging edia PTZ Receiver ONVIF_IS_for_Device.doc

8 8 ONVIF-2.4.1: [Recording] [Search] [Replay] [Analytics Device] Recording ontrol Recording Search Replay ontrol Video Analytics Device -v211.pdf 2.2. Informative s ne ONVIF_IS_for_Device.doc

9 9 ONVIF-2.4.1: Terminology and onventions 3.1. onventions The key words UST, UST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD NOT, REOENDED, AY, and OPTIONAL in this document are to be interpreted as described in [RF2119]. All sections and appendixes, except Scope and Introduction, are normative, unless they are explicitly indicated to be informative Definitions ne 3.3. Abbreviations SR lient- Static onformance uirement Device uirement. Device had been called as Network Video transmitter until ore Spec 2.1. lient uirement. lient had been called as Network Video lient until ore Spec 2.1. ONVIF_IS_for_Device.doc

10 10 ONVIF-2.4.1: Introduction This document defines the static conformance requirement for the ONVIF lient Protocol based on the ONVIF core specification. It defines the mandatory and OPTIONAL functionality at the transaction level. In addition, this document identifies the mandatory and OPTIONAL functionalities the various services provide. This document is described based on the requirement of Profile-S which is defined for network camera or encoder. For covering Profile-G (for recording features), it is indicated by adding convention with parenthesis if Profile-G has higher requirement than Profile-S. The / lient- column follows the following conventions: onvention Key words in [RF2119] R andatory requirements for Device or lient Recommended requirements UST, UST NOT, REQUIRED, SHALL, SHALL NOT SHOULD, SHOULD NOT, REOENDED O Optional requirements AY, OPTIONAL N/A t Applicable - /R onditional andatory requirements which are mandatory IF the pre-requisite optional requirements are supported. onditional Recommended requirements which are recommended IF the pre-requisite optional requirements are supported. UST, UST NOT, REQUIRED, SHALL, SHALL NOT SHOULD, SHOULD NOT, REOENDED ONVIF_IS_for_Device.doc

11 11 ONVIF-2.4.1: Web Service frame work 5.1. Web Services Follow the guidelines in the WS-I Basic Profile 2.0 [ore] 5 Device management [ore] Event Service [ore] Respond to all commands defined in the corresponding service WDL. [ore] Respond to a request with the error codes for not supported command [ore] Error Handling use appropriate RTSP and HTTP protocol defined status codes for error reporting and handling SOAP errors shall be reported and handled through SOAP fault messages use SOAP 1.2 fault message handling as specified in ONVIF specification follow the WS-I Basic Profile 2.0 fault handling recommendations. define additional fault subcodes for use by applications. O handle all the ONVIF generic fault codes If the Device waits for the start of the inbound message and no SOAP message is received, the Device shall NOT generate a SOAP fault and instead sends an HTTP error response. [ore] [ore] [ore] [ore] [ore] [ore] [ore] ONVIF_IS_for_Device.doc

12 12 ONVIF-2.4.1: Security digest authentication according to [RF 2617] O () User name token profile [WS-UsernameToken] [ore] 5.12 [ore] 5.12/ X.509 security token profile [WS-X.509Token] O [ore] 5.12 SAL token profile [WS-SALToken] O [ore] 5.12 Kerberos token profile [WS-KerberosToken] O [ore] 5.12 Rights Expression Language (REL) Token Profile [WS-RELToken] For user defined with the UserNameToken profile, digest authentication [RF 2617] shall be used for RTSP and HTTP. HTTP should only be used as a transport protocol and the device shall not authenticate a WS request at this level. O [ore] 5.12 [ore] 5.12 [ore] 5.12 if HTTP is used to tunnel the RTSP request the device shall not authenticate at this level. [ore] 5.12 It shall be possible to define the exact access security policy by the Device user or by a system administrator. By default, the device should enforce the following default access policy, which gives an acceptable level of security in many systems. The default access policy builds upon the access classes that are associated to the services and grants access rights in the following way. A user of level c shall be granted access to a service associated to access class r if and only if an "X" is present in the cell at column c and row r in Table 7. use both nonce and timestamps as defined in [WS-UsernameToken]. reject any Username Token not using both nonce and creation timestamps. If server supports both digest authentication as specified in [RF 2617] and the user name token profile as specified in WS-Security the following behavior (Figure 2: Authentication of a WS request by a server) shall be adapted. R N/A N/A [ore] [ore] [ore] [ore] [ore] [ore] 5.12 ONVIF_IS_for_Device.doc

13 13 ONVIF-2.4.1: IP configuration have at least one network interface that gives it IP network connectivity. [ore] 6 IPv4 based network communication [ore] 6 IPv6 based network communication R [ore] 6 possible to make static IP configuration on the Device using a network or local configuration interface dynamic IP configuration of link-local addresses according to [RF3927] stateless IP configuration according to [RF4862] : IPv6 neighbour discovery according to [RF4861]. : IPv6 dynamic IP configuration according to [RF 2131]. (IPv4) Stateful IP configuration according to [RF3315]. : IPv6 [ore] 6 R [ore] 6 [ore] 6 [ore] 6 [ore] 6 [ore] 6 any additional IP configuration mechanism O [ore] 6 Possible to make Device IP configurations through the parameter configuration interface specified in Section 8.2. The default Device configuration SHALL be to have both DHP and dynamic link-local (stateless) address configuration enabled Even if the device is configured through a static address configuration it should have the link-local address default enabled When a Device is connected to an IPv4 network, address assignment priorities (link local versus routable address) SHOULD be done as recommended in [RF3927]. [ore] 6 [ore] 6 R [ore] 6 R [ore] 6 ONVIF_IS_for_Device.doc

14 14 ONVIF-2.4.1: Device discovery 7.1. General Implement the Target Service role as specified in [WS-Discovery] If necessary Implement the lient role as specified in [WS-Discovery]. Discovery Proxy role as described in [WS-Discovery] shall NOT be supported. This specification defines a new Discovery Proxy role. [ore] 7.1 N/A N/A [ore] 7.1 N/A [ore] odes of operation Device shall be able to operate in two modes: Discoverable and n-discoverable Device in discoverable mode sends multicast Hello messages once connected to the network or sends its Status changes according to [WS-Discovery]. A device in non-discoverable shall not listen to [WS-Discovery] messages or send such messages. [ore] 7.2 [ore] 7.2 [ore] 7.2 Device default behaviour shall be the discoverable mode. [ore] Discovery definitions Use a stable, globally unique identifier that is constant across network interfaces as part of the property of its endpoint reference. An ONVIF compliant device shall include the scope <d:scopes> attribute with the scopes of the device in the Hello message. A device shall include at least one entry of the profile, location, hardware and name categories respectively in the scopes list. Supprt [ore] [ore] [ore] Hello [ore] A device shall include the device management service port [ore] type, i.e. tds:device, in the <d:types> declaration For backward compatibility reason an ONVIF compliant device shall also include dn:networkvideotransmitter in 9.1 the <d:types> declaration Probe and Probe atch [ore] at least support the scope matching rule. [ore] include the <d:xaddrs> element with the addresses for the device service in a matching probe match message. [ore] Device should implement the resolve match response. R [ore] Device should send a one-way Bye message when it prepares to leave a network R [ore] ONVIF_IS_for_Device.doc

15 15 ONVIF-2.4.1:2017 If an error exists with the multicast packet, the Device and lient should silently discard and ignore the request. If an Device receives a unicast Probe message and it does not support the matching rule, then the Device AY choose not to send a Probe atch, and instead generate a SOAP fault. A device compliant to the Profile S shall include a scope entry with this value in its scope list. Profile/Streaming A device compliant to the Profile G shall include a scope entry with this value in its scope list. Profile/G R [ore] O [ore] Remote discovery extensions remote discovery extensions O [ore] 7.4 It must be possible to enable/disable the Device remote discovery registration. : support remote discovery [ore] Implement the remote Hello disable/enable operation : support remote discovery A Device that is not configured with a home DP address or a Device with remote Hello disabled SHALL NOT send a remote Hello. : support remote discovery If a Device has remote discovery enabled but lacks remote DP address configuration, it UST try to make a DNS SRV lookup for the home DP. : support remote discovery The remote Hello and Probe and Probe atch messages UST be sent over HTTPS. : support remote discovery [ore] [ore] [ore] [ore] ONVIF_IS_for_Device.doc

16 16 ONVIF-2.4.1: Device management 8.1. apabilities GetWsdlUrl GetServices GetServiceapabilities Getapabilities [ProfieG] Network GetHostname SetHostname SetHostnameFromDHP : signalled via the HostnameFromDHP capability. GetDNS SetDNS GetNTP :NTP SetNTP :NTP GetDynamicDNS :DynamicDNS as specified in [RF 2136] and [RF 4702] SetDynamicDNS :DynamicDNS as specified in [RF 2136] and [RF 4702] GetNetworkInterfaces SetNetworkInterfaces GetNetworkProtocols SetNetworkProtocols GetNetworkDefaultGateway SetNetworkDefaultGateway GetZeroonfiguration :dynamic IP configuration according to [RF3927] SetZeroonfiguration :dynamic IP configuration according to [RF3927] GetIPAddressFilter :access control based on IP filtering rules SetIPAddressFilter :access control based on IP filtering rules [ore] ONVIF_IS_for_Device.doc

17 17 ONVIF-2.4.1:2017 AddIPAddressFilter :access control based on IP filtering rules RemoveIPAddressFilter :access control based on IP filtering rules IEEE configuration : IEEE support, SSID : IEEE support, Station ode : IEEE support, The device AY support the ad-hoc network station mode. O ultiple wireless network configuration : IEEE support, Security configuration : IEEE support, [ore] [ore] [ore] [ore] [ore] [ore] the device shall, in accordance with the [IEEE ] specification, support the P algorithm and the device AY support the TKIP algorithm. [ore] The device shall support both the manually and the automatically selected mode. [ore] ne mode : IEEE support, [ore] PSK mode : IEEE support, [ore] IEEE 802.1X-2004 ode : IEEE support, /R [ore] GetIEEE802.11apabilities :IEEE support [ore] GetDot11Status :IEEE support [ore] ScanAvailable802.11Networks : IEEE support /R [ore] System GetDeviceInformation GetSystemUris : allows retrieval of system logs, support information or system backup data [ore] GetSystemBackup R [ore] RestoreSystem R [ore] StartSystemRestore R [ore] GetSystemDateAndTime SetSystemDateAndTime [ore] SetSystemFactoryDefault ONVIF_IS_for_Device.doc

18 18 ONVIF-2.4.1: UpgradeSystemFirmware R [ore] StartFirmwareUpgrade R [ore] GetSystemLog R [ore] GetSystemInformation O [ore] SystemReboot GetScopes SetScopes AddScopes RemoveScopes GetDiscoveryode SetDiscoveryode GetRemoteDiscoveryode [ore] :Remote Discovery SetRemoteDiscoveryode [ore] :Remote Discovery GetDPAddresses :Remote Discovery SetDPAddresses :Remote Discovery [ore] [ore] Security GetAccessPolicy :access policy settings based on WS-Security authentication SetAccessPolicy :access policy settings based on WS-Security authentication GetUsers reateusers DeleteUsers SetUser reatedot1xonfiguration : support IEEE 802.1x SetDot1Xonfiguration : support IEEE 802.1x GetDot1Xonfiguration : support IEEE 802.1x GetDot1Xonfigurations : support IEEE 802.1x DeleteDot1Xonfigurations : support IEEE 802.1x [ore] [ore] [ [ore] [ore] [ore] [ore] [ore] ONVIF_IS_for_Device.doc

19 19 ONVIF-2.4.1:2017 reateertificate : support TLS : onboard public key pair generation Getertificates : support TLS server certificates and IEEE 802.1X client certificates GetAertificates : support either TLS client authentication or IEEE 802.1x GetertificatesStatus : support TLS SetertificatesStatus : support TLS GetPkcs10uest : support onboard key pair generation that supports either TLS or IEEE 802.1X using client certificate Getlientertificateode : support TLS Setlientertificateode : support TLS Loadertificates : onboard key pair generation that support either TLS or IEEE 802.1X LoadertificateWithPrivateKey : a device does not support onboard key pair generation and support either TLS or IEEE 802.1X using client certificate A device that support onboard keypair generation AY support this command (LoadertificateWithPrivateKey). GetertificateInformation : a device supports either TLS or IEEE 802.1X LoadAertificates : support either TLS or IEEE 802.1X A device that support this command shall support at least DER format as supported format type. Deleteertificates : support TLS GetRemoteUser : supporting remote user handling SetRemoteUser : supporting remote user handling GetEndpoint R [ore] [ore] /R [ore] [ore] [ore] [ore] [ore] [ore] [ore] [ore] [ore] [ore] [ore] [ore] [ore] [ore] [ore] [ore] Input/Output (I/O) (if supported) GetRelayOutputs SetRelayOutputSettings SetRelayOutputState ONVIF_IS_for_Device.doc

20 20 ONVIF-2.4.1: Auxiliary operation (if supportetd) SendAuxiliaryommand : indicates auxiliary service capability tt:wiper On : supports wiper tt:wiper Off : supports wiper tt:washer On : supports washer tt:washer Off : supports washer tt:washingprocedure On : supports washer tt:washingprocedure Off : supports washer [ore] 8.6 [ore] 8.6 [ore] 8.6 [ore] 8.6 [ore] 8.6 [ore] 8.6 [ore] onitoringevents Processor Usage : supports monitoring of processing unit usage Link Status : supports monitoring of the Link Status Upload Status : supports monitoring of its upload firmware Operating Time: DefinedLimitReached : supporting operation time events Operating Time: eantimebetweenfailuresdefaultlimitreached : supporting operation time events Operating Time: eantimebetweenfailuresoperationlimitreached : supporting operation time events Operating Time: LastReset : supporting operation time events Operating Time: LastReboot : supporting operation time events Operating Time: LastlockSynchronization : supporting operation time events Operating Time: aintenance/last : supporting operation time events Operating Time: aintenance/nextscheduled : supporting operation time events Operating Time: Backup/Last : supporting operation time events Operating Time: AreaOfOperation/OutsideertifiedArea : supporting operation time events Operating Time: AreaOfOperation/OutsideonfiguredArea : supporting operation time events Environmental onditions: Environmentalonditions/RelativeHumidity : measurements of environmental conditions are supported Environmental onditions: Environmentalonditions/Temperature /R [ore] /R [ore] /R [ore] /R [ore] /R [ore] /R [ore] /R [ore] /R [ore] /R [ore] /R [ore] /R [ore] /R [ore] R [ore] /R [ore] /R [ore] /R [ore] ONVIF_IS_for_Device.doc

21 21 ONVIF-2.4.1:2017 : measurements of environmental conditions are supported Battery capacity : measurements of the battery level are supported Device anagement tns1:device/operationode/shutdowninitiated tns1:device/operationode/uploadinitiated tns1:device/hardwarefailure/fanfailure tns1:device/hardwarefailure/powersupplyfailure tns1:device/hardwarefailure/storagefailure tns1:device/hardwarefailure/temperatureritical /R [ore] R [ore] ONVIF_IS_for_Device.doc

22 22 ONVIF-2.4.1: DeviceIO Service 9.1. VideoOutputs GetVideoOutputs : the device has one or more physical video outputs VideoOutputonfiguration GetVideoOutputonfiguration : the device has one or more physical video outputs SetVideoOutputonfiguration : the device has one or more physical video outputs GetVideoOutputonfigurationOptions : the device has one or more physical video outputs VideoSources GetVideoSources : the device has one or more physical video inputs VideoSourceonfiguration GetVideoSourceonfiguration : the device has one or more physical video sources SetVideoSourceonfiguration : the device has one or more physical video sources GetVideoSourceonfigurationOptions : the device has one or more physical video sources AudioOutputs GetAudioOutputs : the device has one or more physical audio outputs ONVIF_IS_for_Device.doc

23 23 ONVIF-2.4.1: AudioOutputonfiguration GetAudioOutputonfiguration : the device has one or more physical audio outputs SetAudioOutputonfiguration : the device has one or more physical audio outputs GetAudioOutputonfigurationOptions : the device has one or more physical audio outputs AudioSources GetAudioSources : the device has one or more physical audio sources AudioSourceonfiguration GetAudioSourceonfiguration : the device has one or more physical audio inputs SetAudioSourceonfiguration : the device has one or more physical audio sources GetAudioSourceonfigurationOptions : the device has one or more physical audio sources Relay Outputs GetRelayOutputs : the device has I/O ports GetRelayOutputOptions : the device has I/O ports SetRelayOutputSettings : the device has I/O ports SetRelayOutputState : the device has I/O ports Digital Inputs GetDigitalInputs : have physical digital inputs ONVIF_IS_for_Device.doc

24 24 ONVIF-2.4.1: SerialPorts GetSerialPorts : have physical serial ports GetSerialPortonfiguration : have physical serial ports SetSerialPortonfiguration : have physical serial ports GetSerialPortonfigurationOptions : have physical serial ports SendReceiveSerialommand : indicates generic serial communication service capability O O apabilities apabilities: VideoSources O apabilities: VideoOutputs 0 only apabilities: AudioSources O apabilities: AudioOutputs O apabilities: RelayOutputs O apabilities: DigitalInputs O apabilities: SerialPorts O GetServiceapabilities O O () Events DigitalInput State hange tns1:device/trigger/digitalinput :signals support for digital inputs in its capabilities Relay Output Trigger tns1:device/trigger/relay :signals support for RelayOutput in its capabilities R/ onfiguration hange R onfiguration hange; VideoSourceonfiguration R onfiguration hange; VideoOutputonfiguration R onfiguration hange; AudioSourceonfiguration R ONVIF_IS_for_Device.doc

25 25 ONVIF-2.4.1:2017 onfiguration hange; AudioOutputonfiguration R ONVIF_IS_for_Device.doc

26 26 ONVIF-2.4.1: Imaging configuration Imaging Settings Backlightompensation WideDynamicRange unsupported model only O Brightness O olorsaturation O Sharpness O ontrast O Exposure O Focus O Ir cut filter O IrutFilterAutoAdjustment O Whitebalance O WideDynamicRange O Image Stabilization ed by the specific model. See ImageStabilization capabilites O [Imaging] 5.1 [Imaging] 5.1 [Imaging] 5.1 [Imaging] 5.1 [Imaging] 5.1 [Imaging] 5.1 [Imaging] 5.1 [Imaging] 5.1 [Imaging] 5.1 [Imaging] 5.1 [Imaging] 5.1 [Imaging] ommands GetImagingSettings : implementing the imaging service SetImagingSetting : implementing the imaging service GetOptions : implementing the imaging service ove : support for remote focus control GetoveOptions : implementing the imaging service Stop : support for focus GetStatus : support for focus move control R R [Imaging] [Imaging] [Imaging] [Imaging] [Imaging] [Imaging] [Imaging] ONVIF_IS_for_Device.doc

27 27 ONVIF-2.4.1: apabilities apabilities: ImageStabilization : ImageStabilization support model GetServiceapabilities O () [Imaging] [Imaging] Events Tampering: ImageTooBlurry : supports this feature Tampering: ImageTooDark : support this feature Tampering: ImageTooBright : support this feature Tampering: GlobalScenehange : support this feature Tampering: SignalLoss : support this feature otionalarm tns1:videosource/otionalarm : support motion detection /R /R /R /R /R /R [Imaging] [Imaging] [Imaging] [Imaging] [Imaging] [Imaging] ONVIF_IS_for_Device.doc

28 28 ONVIF-2.4.1: edia configuration edia configuration A Device shall provide at least one media profile at boot. 5.2 A Device should provide ready to use profiles for the most common media configurations that the device offers. media profile SHALL be persistent (remain after reboot). reateprofile A created profile shall be deletable and a Device USTshall set the fixed attribute to false in the returned Profile. GetProfiles A Device USTshall include the fixed attribute in all the returned Profile elements. GetProfile AddVideoSourceonfiguration AddVideoEncoderonfiguration AddPTZonfiguration (if supported PTZ) RemoveVideoSourceonfiguration Video source configurations should only be removed after removing a VideoEncoderonfiguration from the media profile. RemoveVideoEncoderonfiguration Audio source configurations should only be removed after removing an AudioEncoderonfiguration from the media profile. RemovePTZonfiguration (if supported PTZ) DeleteProfile R 5.2 R R N/A N/A Video configuration JPEG QVGA 5.1 G.711μ Law (Simplex-amera icrophone Only, 1ch) : Audio 5.1 GetVideoSources GetVideoSourceonfigurations GetVideoSourceonfiguration ONVIF_IS_for_Device.doc

29 29 ONVIF-2.4.1:2017 GetompatibleVideoSourceonfigurations GetVideoSourceonfigurationOptions SetVideoSourceonfiguration GetVideoEncoderonfigurations GetVideoEncoderonfiguration GetompatibleVideoEncoderonfigurations GetVideoEncoderonfigurationOptions SetVideoEncoderonfiguration GetGuaranteedNumberOfVideoEncoderInstances ONVIF_IS_for_Device.doc

30 30 ONVIF-2.4.1: Audio configuration Audio streaming (if supported) GetAudioSources GetAudioSourceonfigurations GetAudioSourceonfiguration AddAudioSourceonfiguration RemoveAudioSourceonfiguration GetompatibleAudioSourceonfigurations GetAudioSourceonfigurationOptions SetAudioSourceonfiguration GetAudioEncoderonfigurations GetAudioEncoderonfiguration AddAudioEncoderonfiguration RemoveAudioEncoderonfiguration GetompatibleAudioEncoderonfigurations GetAudioEncoderonfigurationOptions SetAudioEncoderonfiguration Audio output (if supported) AddAudioOutputonfiguration : Audio decode AddAudioDecoderonfiguration : Audio decode RemoveAudioOutputonfiguration : Audio decode RemoveAudioDecoderonfiguration : Audio decode GetAudioOutputs :Audio decode GetAudioOutputonfigurations :Audio decode GetAudioOutputonfiguration :Audio decode ONVIF_IS_for_Device.doc

31 31 ONVIF-2.4.1:2017 GetompatibleAudioOutputonfigurations :Audio decode GetAudioOutputonfigurationOptions :Audio decode SetAudioOutputonfiguration :Audio decode A decoder shall decode every data it receives (according to its capabilities). :Audio decode GetAudioDecoderonfigurations :Audio decode GetAudioDecoderonfiguration :Audio decode GetompatibleAudioDecoderonfigurations :Audio decode GetAudioDecoderonfigurationOptions :Audio decode SetAudioDecoderonfiguration :Audio decode An optional Send-Primacy Parameter inside the AudioOutputonfiguration indicates which direction is currently active. :Audio decode O Video analytics configuration AddVideoAnalytics : Analytics RemoveVideoAnalyticsonfiguration : Analytics GetVideoAnalyticsonfigurations :Analytics GetVideoAnalyticsonfiguration :Analytics GetompatibleVideoAnalyticsonfigurations :Analytics SetVideoAnalyticsonfiguration :Analytics etadata configuration Getetadataonfigurations Getetadataonfiguration Addetadataonfiguration Removeetadataonfiguration Getompatibleetadataonfigurations GetetadataonfigurationOptions ONVIF_IS_for_Device.doc

32 32 ONVIF-2.4.1:2017 Setetadataonfiguration Other stream configuration GetStreamUri The InvalidAfteronnect, InvalidAfterReboot and Timeout Parameter should be set accordingly (InvalidAfteronnect=false, InvalidAfterReboot=false, timeout=pt0s). For full compatibility with other ONVIF services a device should not generate Uris longer than 128 octets. GetSnapshotUri R The ValidUntilonnect, ValidUntilReboot and Timeout Parameter shall be set accordingly (ValidUntilonnect=false, ValidUntilReboot=false, timeout=pt0s). StartulticastStreaming : ulticast The streaming shall continue after a reboot of the Device until a StopulticastStreaming request is received. : ulticast ulticast streaming may stop when the corresponding profile is deleted or one of its onfigurations is altered via one of the set configuration methods. R R R O StopulticastStreaming : support multicast SetSynchronizationPoint : support PEG-4 or H.264 GetVideoSourceode : capability of VideoSourceode SetVideoSourceode : capability of VideoSourceode reateosd : OSD capability DeleteOSD : OSD capability GetOSDs : OSD capability GetOSD : OSD capability SetOSD : OSD capability GetOSDOptions : OSD capability ONVIF_IS_for_Device.doc

33 33 ONVIF-2.4.1: apabilities apabilities: RTPulticast : support of UDP multicasting apabilities: RTP_TP : supports for RTP over TP apabilities: RTP_RTSP_TP : support for RTP/RTSP/TP transport apabilities: naggregateontrol : support for non aggregate RTSP control apabilities: RTSPStreaming : does not support for live media streaming via RTSP apabilities: aximumnumberofprofiles apabilities: SnapshotUri : support for GetSnapshotUri apabilities: Rotation : support for the Rotation feature apabilities: VideoSourceode : support for changing video source mode apabilities: OSD : support for OSD configuration GetServiceapabilities Events onfiguration: Profile tns1:onfiguration/profile onfiguration: VideoEncoderonfiguration tns1:onfiguration/videoencoderonfigration onfiguration: VideoSourceonfiguration tns1:onfiguration/videosourceonfigration/ediaser vice onfiguration: VideoOutputonfiguration tns1:onfiguration/videooutputonfigration/ediaser vice onfiguration: AudioEncoderonfiguration tns1:onfiguration/audioencoderonfigration onfiguration: AudioSourceonfiguration tns1:onfiguration/audiosourceonfigration/ediase rvice onfiguration: AudioOutputonfiguration tns1:onfiguration/audiooutputonfigration/ediaser vice onfiguration: etadataonfiguration tns1:onfiguration/etadataonfigration onfiguration: PTZonfiguration tns1:onfiguration/ptzonfigration onfiguration: VideoAnalyticsonfiguration tns1:onfiguration/videoanalyticsonfigration Active onnections tns1:onitoring/profile/activeonnections R R R R R R R R R R R ONVIF_IS_for_Device.doc

34 ONVIF_IS_for_Device.doc 34 ONVIF-2.4.1:2017

35 35 ONVIF-2.4.1: Live Streaming edia stream protocol RTP/UDP unicast RTP/UDP multicasting R RTP/TP O RTP/TP shall conform to [RF 4571] (Framing Real-time Transport Protocol and RTP ontrol Protocol [RTP] Packets over onnection-oriented Transport). : RTP/TP media streaming transfer using RTP/RTSP to traverse a firewall RTP/RTSP shall conform to [RF 2326] Section : RTP/RTSP/TP RTP/RTSP/HTTP/TP RTP/RTSP/HTTPS/TP :TLS 1.0 protocol shall conform to [RF 2326] (RTSP Section 10.12: Embedded [Interleaved] Binary Data). : RTP/RTSP/TP Tunnelling method shall conform to QuickTime available from Apple Inc. : RTP/RTSP/HTTP/TP R edia Transport RTP All media streams shall conform to [RF 3550], [RF 3551], [RF 3984], [RF 3016] and JPEG overrtp(11.1.3) RTP for etadata stream A dynamic payload type (96-127) shall be used for payload type which is assigned in the process of a RTSP session setup. RTP marker bit shall be set to 1 when the XL document is closed. It is REOENDED to use an RTP timestamp representing the creation time of the RTP packet with a RTP clock rate of Hz. Only UT timestamps UST be used within the metadata stream. The synchronization of video and audio data streams is done using RTP. When a synchronization point is requested for the stream, the previous XL document UST be closed and a new one started. R ONVIF_IS_for_Device.doc

36 36 ONVIF-2.4.1:2017 It is REOENDED to start new XL documents after 1 second, at the longest. A device can select which of the etadata parts SHOULD be multiplexed into the etadata during the edia onfiguration. Each part can appear multiple times in arbitrary order within the document. A etadata connection can be bi-directional using the backchannel mechanism R R O RTP RTP protocol shall conform to [RF 3550]. For a feedback request, RF4585 and RF 5104 should be supported. R lient AY receive audio and video streams simultaneously from more than one device. N/A N/A RTP Sender Report for media synchronization Wall clock should be common in the device and each timestamp value should be determined properly. R In case of multiple devices, the NTP timestamp should be common to all devices, and the NTP server should be required in the system R PLI messages as described in [RF 4585] to request a SynchronizationPoint. R JPEG over RTP Syntax for transmitting JPEG streams follows [RF 2435]. The syntax does allow embedding additional data, beyond the limits of RF 2435, by using an optional RTP header Transmitter shall use only greyscale and Ybr colour space R lient shall support both greyscale and Ybr. N/A N/A Sampling factord for Ybr shall correspond to the values supported by [RF 2435] sampling factor of 4.2.0(preferred) R ONVIF_IS_for_Device.doc

37 37 ONVIF-2.4.1:2017 sampling factor of R edia control protocol RTSP (RF2326) for session initiation and playback control. RTSP shall use TP SDP (onform to RF4566) OPTIONS(R->T) DESRIBE(R->T) SETUP(R->T) PLAY(R->T) PAUSE(R->T) (LIVE) O PAUSE(R->T) (Replay) TEARDOWN(R->T) GET_PARAETER(R->T) O GET_PARAETER(T->R) O SET_PARAETER(R->T) O SET_PARAETER(T->R) O Devices shall support aggregate stream control, in which PLAY commands are sent to the control URI for the whole session. Devices may support non aggregate stream control, in which PLAY commands are sent separately to the stream control URIs in the media sections of the SDP file. O Set the Timeout parameter (in seconds) using the Set<configurationEntity>Encoderonfiguration command, otherwise a default value of 60 is used. O In all RTSP SETUP responses, transmitter should include the Timeout value according to [RF 2326] Section and the transmitter should use the Timeout value for keep-alive. To keep the RTSP Session alive, client shall call the RTSP server using any RTSP method or send RTP receiver reports. SET_PARAETER is the REOENDED R Include Range field in the RTSP PLAY response R R N/A N/A ONVIF_IS_for_Device.doc

38 38 ONVIF-2.4.1:2017 Include RTP-info field in the RTSP PLAY response R ulticast streaming; A device shall include a valid multicast address in the "c=" field of a DESRIBE response according to RF ulticast streaming; hapter 10.7 TEARDOWN of [RF 2326] states that a device shall stop the stream delivery for the given URI on tear down. ulticast streaming; the device shall stop sending packets for a multicast configuration when no more RTSP sessions are using the same multicast configuration nor its AutoStart flag has been set. The RTSP over HTTP/HTTPS shall be supported in order to traverse a firewall Back hannel onnection understand the backchannel tag: :backchannel include the a=sendonly or the a=recvonly attributes in each media section of the SDP file to indicate the direction as configured in its edia Profile. :backchannel list all supported decoding codecs as own media section :backchannel When the backchannel data stream is sent via RTSP/HTTP/TP, a client shall use HTTP GET connection which is defined for sending the data stream without base64 encoding 5.3 ulticast streaming; If the client intents to send its data in multicast it uses the transport parameter in the SETUP request to tell the server the multicast address and port. O N/A ONVIF_IS_for_Device.doc

39 39 ONVIF-2.4.1: Playback (if supported storage) RTP/RTSP/HTTP/TP shall be supported by the server. 6 The server shall support the unicast RTP/UDP transport for streaming. The server AY elect not to send RTP packets during replay. 6 O RTSP describe The SDP returned by the RTSP describe command shall include the Track for each track of the recording to allow a client to map the tracks presented in the SDP to tracks of the recording The tag shall use the following format: a:x-onvif-track:<track> RTP header extension The replay header extension shall be present in the first packet of every access unit (e.g. video frame). It AY NOT be present in subsequent packets of an access unit. 6.2 The NTP timestamps in the RTP extension header shall increase monotonically over successive packets within a single RTP stream They should correspond to wallclock time as measured at the original transmitter of the stream, adjusted if necessary to preserve monotonicity. R The replay header extension may co-exist with the header extension used by the JPEG RTP profile; this is necessary to allow replay of JPEG streams that use this extension. O RTP Feature Tag The Replay Server shall accept a SETUP command that includes a uire header containing the onvif-replay feature tag. 6.3 ONVIF_IS_for_Device.doc

40 40 ONVIF-2.4.1: Initiating Playback ONVIF devices AY support reverse playback. Reverse playback is indicated using the Scale header field with a negative value. O 6.4 If a device supports reverse playback it shall accept a Scale header with a value of A device AY accept other values for the Scale parameter. O If Rate-ontrol is set to no, the Scale parameter, if it is present, shall be either 1.0 or 1.0, to indicate forward or reverse playback respectively. If it is not present, forward playback is assumed. The Range field shall be expressed using absolute times only; the other formats defined by [RF 2326] shall NOT be used by ONVIF replay clients. Servers may choose to support other formats also. Absolute times are expressed using the utc-range from [RF 2326]. Either open or closed ranges may be used. O The direction of the range shall correspond to the value of the Scale header. When replaying multiple tracks of a single recording, started by a single RTSP PLAY command and not using rate-control, the data from the tracks should be multiplexed in time in the same order as they were recorded. An ONVIF compliant RTSP server shall support operation with Rate-ontrol=no for playback. The Frames header field may be used to reduce the number of frames that are transmitted, for example to lower bandwidth or processing load. Three modes are possible: Intra frames only. O Intra frames and predicted frames only. O All frames. This is the default. O R O The interval argument shall NOT be present unless the Frames option is intra The server shall support the Frames header field. The implementation of the Scale header field may vary between different server implementations, as stated by [RF 2326]. An ONVIF compliant RTSP server shall support the Frames parameters intra and all for playback. N/A N/A The transmitted video stream shall begin at a synchronization point ONVIF_IS_for_Device.doc

41 41 ONVIF-2.4.1:2017 If the requested start time is within a section of recorded footage, the stream starts with the first clean point at or before the requested start time. If the requested start time is within a gap in recorded footage and playback is being initiated in the forwards direction, the stream starts with the first clean point in the section following the requested start time. If the requested start time is within a gap in recorded footage and playback is being initiated in the reverse direction, the stream starts with the last clean point in the section preceding the requested start time. : reverse Reverse replay During reverse playback, GOPs shall be sent in reverse order, but packets within a GOP shall be sent in forward order. : Reverse replay The first packet of each GOP shall have the discontinuity bit set in its RTP extension header. : Reverse replay The last packet of a GOP immediately following a gap (or the beginning of available footage) shall have the E bit set in its RTP extension header. : Reverse replay In this case the packets within each frame shall be again sent in forward order, while the frames themselves shall be sent in reverse order. : Reverse replay Audio and metadata streams AY be transmitted in an order mirroring that of the video stream. : Reverse replay The RTP sequence numbers of packets transmitted during reverse playback shall increment monotonically in the order of delivery, not in the intended order of playback. : Reverse replay The server AY use the same RTP timestamps that were originally received when the stream was recorded. : Reverse replay O If Rate-ontrol is yes, the RTP timestamps of packets transmitted during reverse playback shall indicate the times at which each frame should be rendered at the client. : Reverse replay ONVIF_IS_for_Device.doc

42 42 ONVIF-2.4.1: RTSP Keepalive When rate control is disabled and the RTP stream is tunneled through the RTSP connection (i.e. using the RTP/RTSP/TP or RTP/RTSP/HTTP/TP transports), the client must be aware that it may not be able to receive the response to any request if for example replay is paused. N/A urrently recording footage If the client commences playback from the current real world time or shortly before it, it can end up playing footage in real time as it is being recorded. In this event the server simply continues to send stream data to the client as it receives it. O End of footage If playback reaches a point after which there is no further data in one or more of the streams being sent, it stops transmitting data but does not enter the paused state. If the server resumes recording after this has happened, delivery will resume with the new data as it is received. O Go To Time If the server receives a PLAY command with the Immediate header set to yes, it will immediately start playing from the new location, cancelling any existing PLAY command. 6.9 The first packet sent from the new location shall have the D (discontinuity) bit set in its RTP extension header. 6.9 An ONVIF compliant RTSP server shall support the immediate header field for playback. 6.9 ONVIF_IS_for_Device.doc

43 43 ONVIF-2.4.1: Use of If Rate ontrol is enabled (see section 6.4.2), RTP packets shall be constructed and transmitted as specified in [RF 3550]. In particular, the NTP timestamp in a sender report indicates the current wallclock time, and is not related to the NTP timestamps embedded in the RTP extension headers in the data streams. : send RTP packets 6.10 If Rate ontrol is not enabled, both the NTP timestamp and RTP timestamp in each sender report shall be set to zero. : send RTP packets 6.10 ONVIF_IS_for_Device.doc

44 44 ONVIF-2.4.1: Receiver onfiguration ONVIF_IS_for_Device.doc

45 45 ONVIF-2.4.1: Display Service ONVIF_IS_for_Device.doc

46 46 ONVIF-2.4.1: Event handling A device shall provide an event services as defined in [ONVIF Event WSDL]. [ore] 9 Both a Device and lient shall support [WS-Addressing] for event services. [ore] 9 basic notification interface [ore] 9 Real-time Pull-Point tification Interface [ore] 9 tification Streaming Interface [ore] Basic tification Interface Event Service and the Subscription anager should be instantiated on a device. tificationproducer Interface An ONVIF compliant device shall support the tificationproducer Interface of the [WS-Basetification]. R [ore] [ore] tificationproducer Resource Properties O [ore] TopicExpression and essageontent filters [ore] tify(ws-basetification) The Device UST be able to provide notifications using the tify wrapper of the [WS-Basetification] specification. Although the [WS-Basetification] has urrenttime and TerminationTime as optional elements in a SubscribeResponse, an ONVIF compliant device shall list them in SubscribeResponses. (WS-Basetification) [ore] [ore] Geturrentessage(WS-Basetification) O [ore] Pull-Point Interface of the [WS-Basetification] O [ore] Base Subscription anager Interface of the [WS-Basetification] [ore] Renew (WS-Basetification) [ore] Unsubscribe (WS-Basetification) [ore] Pausable Subscription anager Interface (WS-Basetification) The implementation of Subscriptions as WS-Resources is OPTIONAL. An ONVIF compliant device shall support time values in request parameters that are given in utc with the 'Z' indicator and respond all time values as utc including the 'Z' indicator. O [ore] O [ore] [ore] Real-time Pull-Point tification Interface ONVIF_IS_for_Device.doc