Camera Generated Events in 3dEYE

    3dEYE can receive and process camera‑generated events without requiring a 3dEYE Cloud Analytics subscription. This allows customers to use the built‑in analytics capabilities of their cameras while still bringing those events into the 3dEYE platform for viewing, searching, and integration.

    Supported camera‑generated events may include:

    • Line crossing

    • Intrusion detection

    • Motion detection

    • Region‑based detection

    • Person or vehicle detection

    • Other supported edge‑analytics events

    The availability of specific event types depends on the camera model, firmware, and supported event protocols.

    How Camera‑Generated Events Work

    When a compatible camera detects an event, the camera processes the detection locally and generates the event. The event is then communicated to 3dEYE using a supported protocol.

    Workflow

    Camera detects event → Camera generates event → Event is sent to 3dEYE → 3dEYE registers and processes the event → Event becomes available in the platform
    The video stream and the event are separate components:
    • The camera continuously streams video to 3dEYE.
    • The camera’s own analytics or event rules generate events independently.
    This means 3dEYE Cloud Analytics is not required simply to receive camera‑generated events.

    Using Camera Edge Analytics (ONVIF Profile M)

    3dEYE can also utilize supported edge analytics and metadata when the camera complies with ONVIF Profile M.

    Profile M provides standardized mechanisms for transmitting:  
    • Analytics metadata
    • Object classifications
    • Event notifications
    For example, if a camera performs line‑crossing detection locally, it can generate the event and communicate the supported event information to 3dEYE without requiring the corresponding 3dEYE Cloud Analytics module.
    This is especially useful when customers already have cameras with capable onboard analytics and want to leverage those capabilities within their 3dEYE deployment.

    How Camera‑Generated Events Are Used in 3dEYE

    Once supported events are received, 3dEYE registers them and makes them available through:

    • 3dEYE Video Portal

    • Admin Portal

    • Event logs

    • APIs

    • Webhooks and other integrations

    Camera‑generated events can participate in workflows, automation, and integrations even without Cloud Analytics.

    Example: Line‑Crossing Detection

    A camera monitors a restricted entrance and has a line‑crossing rule configured.

    When a person crosses the line:

    1. The camera detects the event.

    2. The camera generates the event locally.

    3. The event is communicated to 3dEYE.

    4. 3dEYE registers and displays the event.

    5. The associated video is available for review based on retention settings.

    No 3dEYE Cloud Analytics module is required for this detection.

    Camera Analytics vs. 3dEYE Cloud Analytics


    Camera / Edge Analytics

    3dEYE Cloud Analytics

    Processing performed on the camera

    Processing performed in the 3dEYE cloud

    Uses camera’s built‑in analytics

    Uses 3dEYE’s cloud‑based analytics

    Events generated locally

    Events generated by cloud analytics

    Supported events can be sent to 3dEYE

    Provides additional detection capabilities

    Does not require Cloud Analytics

    Requires applicable cloud analytics module

    Event‑Based Recording

    3dEYE Continuous Recording

    Camera records only when an event is detected

    Camera continuously streams video

    Event is sent to the VMS to trigger recording

    Video is continuously recorded in the cloud

    Only event‑based clips may be retained

    Recording is retained according to configured retention

    Missed or undetected incidents may have no footage

    Footage exists even if no event is generated

    Events determine when recording occurs

    Events help identify relevant footage


    Customers can use:

    • Camera analytics only

    • 3dEYE Cloud Analytics only

    • A combination of both (when supported)

    Requirements and Compatibility

    Camera‑generated event support depends on:

    • Camera model

    • Firmware version

    • Supported ONVIF profiles

    • Event types supported by the camera

    • Camera’s implementation of ONVIF Profile M

    • Metadata format and protocol compatibility

    ⚠️Important: ONVIF Profile M support alone does not guarantee that all analytics features on a camera will be supported. Compatibility must be confirmed for the specific model and event type.


    Tags
    camera events cloud analytics
    Published