{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/onvif-profile-g-edge-recording-acceptance-testing/", "item": { "id": "https://update.dsesecurity.com/updates/onvif-profile-g-edge-recording-acceptance-testing/", "slug": "onvif-profile-g-edge-recording-acceptance-testing", "url": "https://update.dsesecurity.com/updates/onvif-profile-g-edge-recording-acceptance-testing/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/onvif-profile-g-edge-recording-acceptance-testing.md", "json": "https://update.dsesecurity.com/api/v1/posts/onvif-profile-g-edge-recording-acceptance-testing/" }, "title": "ONVIF Profile G acceptance testing for edge recording and retrieval", "summary": "Profile G standardizes important recording and retrieval interfaces, but a resilient edge-recording design still needs capacity, outage, recovery, and evidence tests.", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "advisory", "name": "Advisory" }, "featured": false, "topics": [ { "slug": "business-continuity", "name": "Business Continuity", "url": "https://update.dsesecurity.com/topic/business-continuity/" }, { "slug": "networks-infrastructure", "name": "Networks & Infrastructure", "url": "https://update.dsesecurity.com/topic/networks-infrastructure/" }, { "slug": "video-surveillance", "name": "Video Surveillance", "url": "https://update.dsesecurity.com/topic/video-surveillance/" } ], "author": { "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "name": "Detection Systems & Engineering", "url": "https://dsesecurity.com/" }, "published_at": "2026-07-19T21:28:39+00:00", "modified_at": "2026-07-19T21:28:39+00:00", "reviewed_on": "2026-07-19", "reading_minutes": 2, "word_count": 435, "potentially_affected": "Video systems using camera or encoder storage, recording-capable devices, NVRs, VMS clients, or edge recording as a primary recorder or network-outage safeguard.", "dse_recommendation": "Verify exact Profile G conformance and run controlled storage, outage, retrieval, and reintegration tests against the real camera, media, and VMS combination.", "primary_source": { "name": "ONVIF — Profile G", "url": "https://www.onvif.org/profiles/profile-g/", "published_on": null, "authority": "ONVIF" }, "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usage_info": "https://update.dsesecurity.com/usage/", "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "content_html": "

What Profile G covers

\n

Source fact: ONVIF Profile G is designed for IP-based video storage and retrieval. A conformant device, such as a network camera or encoder, can record video over the network or on the device itself. A conformant client, such as VMS software, can configure, request, and control recording from a Profile G device.

\n

ONVIF’s 2014 release announcement describes a broader recording workflow that includes on-board storage, search, retrieval, and media playback. The current profile page also identifies receipt of audio and metadata streams when the client supports those features. That conditional wording is important: a Profile G label alone does not establish that every client accepts audio or metadata.

\n

Profile G provides standardized interfaces, not a storage-service guarantee. It does not assign an SD-card endurance rating, calculate retention, promise uninterrupted capture for every outage, validate timestamps, or certify that a VMS will reconcile every edge recording after connectivity returns. Those outcomes depend on the exact device, media, client, configuration, clock source, network behavior, and supported features.

\n\n

Define the recovery use case

\n

First decide why edge storage exists. It may be the primary recording destination, a short network-failure buffer, or a secondary evidence source. Define the expected recording mode, event triggers, frame rate, bitrate, audio and metadata needs, retention target, and maximum anticipated outage. Use manufacturer endurance and compatibility information for the actual media rather than deriving capacity from Profile G.

\n

Conformance must be checked for both sides of the intended workflow and for their exact installed versions. A feature list should be reviewed before testing so a conditional function is not mistaken for a universal requirement.

\n\n

DSE acceptance checklist

\n

DSE recommendation: This checklist is DSE operational synthesis; ONVIF does not prescribe this site-test sequence.

\n
    \n
  1. Verify the exact device and client versions in ONVIF’s registry and retain their feature documents.
    2. \n
  2. Confirm supported media, health monitoring, usable capacity, overwrite behavior, and time synchronization from current manufacturer guidance.
    3. \n
  3. Create known recordings and prove search, retrieval, playback, timestamps, and export from the client.
    4. \n
  4. Where required, confirm that audio and metadata survive the complete recording and retrieval path.
    5. \n
  5. Simulate an approved network interruption, keep it within the designed duration, and document device behavior.
    6. \n
  6. Restore connectivity and verify discovery, backlog availability, chronology, duplicates, gaps, and VMS reconciliation.
    7. \n
  7. Test full, removed, failed, or replaced media using safe procedures supported by the manufacturer.
    8. \n
  8. Record the tested limits and schedule periodic health and retrieval checks.
    9. \n
\n\n

Official references

\n", "content_text": "What Profile G covers\nSource fact: ONVIF Profile G is designed for IP-based video storage and retrieval. A conformant device, such as a network camera or encoder, can record video over the network or on the device itself. A conformant client, such as VMS software, can configure, request, and control recording from a Profile G device.\nONVIF’s 2014 release announcement describes a broader recording workflow that includes on-board storage, search, retrieval, and media playback. The current profile page also identifies receipt of audio and metadata streams when the client supports those features. That conditional wording is important: a Profile G label alone does not establish that every client accepts audio or metadata.\nProfile G provides standardized interfaces, not a storage-service guarantee. It does not assign an SD-card endurance rating, calculate retention, promise uninterrupted capture for every outage, validate timestamps, or certify that a VMS will reconcile every edge recording after connectivity returns. Those outcomes depend on the exact device, media, client, configuration, clock source, network behavior, and supported features.\n\nDefine the recovery use case\nFirst decide why edge storage exists. It may be the primary recording destination, a short network-failure buffer, or a secondary evidence source. Define the expected recording mode, event triggers, frame rate, bitrate, audio and metadata needs, retention target, and maximum anticipated outage. Use manufacturer endurance and compatibility information for the actual media rather than deriving capacity from Profile G.\nConformance must be checked for both sides of the intended workflow and for their exact installed versions. A feature list should be reviewed before testing so a conditional function is not mistaken for a universal requirement.\n\nDSE acceptance checklist\nDSE recommendation: This checklist is DSE operational synthesis; ONVIF does not prescribe this site-test sequence.\n\nVerify the exact device and client versions in ONVIF’s registry and retain their feature documents.\nConfirm supported media, health monitoring, usable capacity, overwrite behavior, and time synchronization from current manufacturer guidance.\nCreate known recordings and prove search, retrieval, playback, timestamps, and export from the client.\nWhere required, confirm that audio and metadata survive the complete recording and retrieval path.\nSimulate an approved network interruption, keep it within the designed duration, and document device behavior.\nRestore connectivity and verify discovery, backlog availability, chronology, duplicates, gaps, and VMS reconciliation.\nTest full, removed, failed, or replaced media using safe procedures supported by the manufacturer.\nRecord the tested limits and schedule periodic health and retrieval checks.\n\nOfficial references\n\nProfile G — current device, client, recording, audio, and metadata scope.\nONVIF Releases Profile G for Video Storage and Recording — the July 2, 2014 storage, search, retrieval, and playback release scope.\nConformant Products — exact product and version verification.", "content_markdown": "## What Profile G covers\n\nSource fact: ONVIF Profile G is designed for IP-based video storage and retrieval. A conformant device, such as a network camera or encoder, can record video over the network or on the device itself. A conformant client, such as VMS software, can configure, request, and control recording from a Profile G device.\n\nONVIF’s 2014 release announcement describes a broader recording workflow that includes on-board storage, search, retrieval, and media playback. The current profile page also identifies receipt of audio and metadata streams when the client supports those features. That conditional wording is important: a Profile G label alone does not establish that every client accepts audio or metadata.\n\nProfile G provides standardized interfaces, not a storage-service guarantee. It does not assign an SD-card endurance rating, calculate retention, promise uninterrupted capture for every outage, validate timestamps, or certify that a VMS will reconcile every edge recording after connectivity returns. Those outcomes depend on the exact device, media, client, configuration, clock source, network behavior, and supported features.\n\n## Define the recovery use case\n\nFirst decide why edge storage exists. It may be the primary recording destination, a short network-failure buffer, or a secondary evidence source. Define the expected recording mode, event triggers, frame rate, bitrate, audio and metadata needs, retention target, and maximum anticipated outage. Use manufacturer endurance and compatibility information for the actual media rather than deriving capacity from Profile G.\n\nConformance must be checked for both sides of the intended workflow and for their exact installed versions. A feature list should be reviewed before testing so a conditional function is not mistaken for a universal requirement.\n\n## DSE acceptance checklist\n\nDSE recommendation: This checklist is DSE operational synthesis; ONVIF does not prescribe this site-test sequence.\n\n- Verify the exact device and client versions in ONVIF’s registry and retain their feature documents.\n\n- Confirm supported media, health monitoring, usable capacity, overwrite behavior, and time synchronization from current manufacturer guidance.\n\n- Create known recordings and prove search, retrieval, playback, timestamps, and export from the client.\n\n- Where required, confirm that audio and metadata survive the complete recording and retrieval path.\n\n- Simulate an approved network interruption, keep it within the designed duration, and document device behavior.\n\n- Restore connectivity and verify discovery, backlog availability, chronology, duplicates, gaps, and VMS reconciliation.\n\n- Test full, removed, failed, or replaced media using safe procedures supported by the manufacturer.\n\n- Record the tested limits and schedule periodic health and retrieval checks.\n\n## Official references\n\n- [Profile G](https://www.onvif.org/profiles/profile-g/) — current device, client, recording, audio, and metadata scope.\n\n- [ONVIF Releases Profile G for Video Storage and Recording](https://www.onvif.org/pressrelease/onvif-releases-profile-g-for-video-storage-and-recording/) — the July 2, 2014 storage, search, retrieval, and playback release scope.\n\n- [Conformant Products](https://www.onvif.org/conformant-products/) — exact product and version verification." }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo.png" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/onvif-profile-g-edge-recording-acceptance-testing/", "url": "https://update.dsesecurity.com/updates/onvif-profile-g-edge-recording-acceptance-testing/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-07-19" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/onvif-profile-g-edge-recording-acceptance-testing/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "ONVIF Profile G acceptance testing for edge recording and retrieval", "item": "https://update.dsesecurity.com/updates/onvif-profile-g-edge-recording-acceptance-testing/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/onvif-profile-g-edge-recording-acceptance-testing/#article", "identifier": "https://update.dsesecurity.com/updates/onvif-profile-g-edge-recording-acceptance-testing/", "url": "https://update.dsesecurity.com/updates/onvif-profile-g-edge-recording-acceptance-testing/", "headline": "ONVIF Profile G acceptance testing for edge recording and retrieval", "description": "Profile G standardizes important recording and retrieval interfaces, but a resilient edge-recording design still needs capacity, outage, recovery, and…", "abstract": "Profile G standardizes important recording and retrieval interfaces, but a resilient edge-recording design still needs capacity, outage, recovery, and evidence tests.", "articleBody": "What Profile G covers\nSource fact: ONVIF Profile G is designed for IP-based video storage and retrieval. A conformant device, such as a network camera or encoder, can record video over the network or on the device itself. A conformant client, such as VMS software, can configure, request, and control recording from a Profile G device.\nONVIF’s 2014 release announcement describes a broader recording workflow that includes on-board storage, search, retrieval, and media playback. The current profile page also identifies receipt of audio and metadata streams when the client supports those features. That conditional wording is important: a Profile G label alone does not establish that every client accepts audio or metadata.\nProfile G provides standardized interfaces, not a storage-service guarantee. It does not assign an SD-card endurance rating, calculate retention, promise uninterrupted capture for every outage, validate timestamps, or certify that a VMS will reconcile every edge recording after connectivity returns. Those outcomes depend on the exact device, media, client, configuration, clock source, network behavior, and supported features.\n\nDefine the recovery use case\nFirst decide why edge storage exists. It may be the primary recording destination, a short network-failure buffer, or a secondary evidence source. Define the expected recording mode, event triggers, frame rate, bitrate, audio and metadata needs, retention target, and maximum anticipated outage. Use manufacturer endurance and compatibility information for the actual media rather than deriving capacity from Profile G.\nConformance must be checked for both sides of the intended workflow and for their exact installed versions. A feature list should be reviewed before testing so a conditional function is not mistaken for a universal requirement.\n\nDSE acceptance checklist\nDSE recommendation: This checklist is DSE operational synthesis; ONVIF does not prescribe this site-test sequence.\n\nVerify the exact device and client versions in ONVIF’s registry and retain their feature documents.\nConfirm supported media, health monitoring, usable capacity, overwrite behavior, and time synchronization from current manufacturer guidance.\nCreate known recordings and prove search, retrieval, playback, timestamps, and export from the client.\nWhere required, confirm that audio and metadata survive the complete recording and retrieval path.\nSimulate an approved network interruption, keep it within the designed duration, and document device behavior.\nRestore connectivity and verify discovery, backlog availability, chronology, duplicates, gaps, and VMS reconciliation.\nTest full, removed, failed, or replaced media using safe procedures supported by the manufacturer.\nRecord the tested limits and schedule periodic health and retrieval checks.\n\nOfficial references\n\nProfile G — current device, client, recording, audio, and metadata scope.\nONVIF Releases Profile G for Video Storage and Recording — the July 2, 2014 storage, search, retrieval, and playback release scope.\nConformant Products — exact product and version verification.", "datePublished": "2026-07-19T21:28:39+00:00", "dateModified": "2026-07-19T21:28:39+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/onvif-profile-g-edge-recording-acceptance-testing/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@id": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": "https://update.dsesecurity.com/assets/dse-updates-share.png", "articleSection": [ "Business Continuity", "Networks & Infrastructure", "Video Surveillance" ], "keywords": [ "Business Continuity", "Networks & Infrastructure", "Video Surveillance", "Guide", "Advisory priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "Business Continuity", "url": "https://update.dsesecurity.com/topic/business-continuity/" }, { "@type": "Thing", "name": "Networks & Infrastructure", "url": "https://update.dsesecurity.com/topic/networks-infrastructure/" }, { "@type": "Thing", "name": "Video Surveillance", "url": "https://update.dsesecurity.com/topic/video-surveillance/" } ], "wordCount": 435, "timeRequired": "PT2M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "ONVIF — Profile G", "url": "https://www.onvif.org/profiles/profile-g/" } } ] } }