BATA Executive Patent Position
Technology Alignment Assessment · Prepared for Agero
04 / 16
Patent Position

Protecting the Architecture That Converts a Roadside Incident Into a Governed Digital Event

The BATA patent position is directed to an integrated system and method for capturing, interpreting, structuring and orchestrating roadside incidents across multiple participants, services and workflows.

The inventive position resides in the coordinated operation of the architecture, rather than in any isolated dispatch, booking, mapping or provider-management function.

Australian Provisional Patent Application No. 2026905919Patent Pending
Incident capture
AI interpretation
Structured incident record
Safety logic
Provider matching
Pricing and dispatch
Downstream workflows
Audit and lifecycle history
BATA Patent Position

Patent Position Summary

The BATA patent position concerns the technical process through which roadside incident information is received from one or more sources, interpreted to determine incident characteristics, converted into a structured incident record and used to coordinate the operational response.

The structured incident record may then be updated as the incident progresses and used to control provider selection, safety actions, pricing, dispatch, communication and downstream resolution workflows.

The core position is the use of a persistent incident-level digital control object to coordinate the complete operational lifecycle of a roadside event.

The Inventive Concept

Structured Incident Record
Inputs to the record

Incident Understanding

Receive and interpret multimodal information to determine the nature, condition, location, urgency and service requirements of the roadside event.

TextVoiceImagesVideoLocationVehicle dataConnected system dataParticipant updates

Core Inventive Concepts

Each concept below is a distinct technical element of the filed position. Expand a module for the executive description, why it matters operationally and commercially, and to capture a note against that concept.

Executive description

Interpreted outputs populate a single persistent incident-level record holding identity, classification, participants, safety status, vehicle state, required response, workflow state and event history.

Claims 1, 5–7 · Figure 4
Why it matters
  • Establishes one authoritative operational object for the entire event.
  • Every downstream decision references the same governed state.
  • Provides the continuity that transaction-based systems cannot maintain.
Supporting sources and evidentiary notes

Public sources reviewed July 2026. Cited as publicly available material only.

Protectable architecture layers

Select a layer to open it in the protectable architecture breakdown below.

Executive note · IC-03
0 characters
Saved to this device and tied to IC-03.

Claim-to-Concept Coverage Matrix

A compact read of which inventive concept modules support which claim areas. Filled markers indicate a concept that is central to the claim area; outlined markers indicate supporting coverage. Select any marker for the rationale.

Concept module1.11.21.31.42.12.22.32.42.53.13.23.33.43.5
IC-01Capture
IC-02Interpretation
IC-03Structured record
IC-04Safety
IC-05Orchestration
IC-06Lifecycle
Central to the claim areaSupporting coverageClaim areas 1.x core position · 2.x functional depth · 3.x downstream breadth

Select a marker to read why that concept module supports that claim area. Hovering a row or claim reference isolates its coverage across the matrix.

The structured incident record (IC-03) carries coverage across every claim tier, which is consistent with its role as the anchoring element of the filed position.

The Patent Position Resides in the Combination

The Value Lies in the Architecture, Data Flow and Control Logic

Isolated Technology Functions

Image recognitionLocation detectionProvider databaseDispatch softwarePricing engineInsurer interfaceRepair workflowAudit log

Individual functions may be known or available independently within roadside, mobility and insurance environments.

Protectable Architecture — Interactive Breakdown

The invention framework is expressed as six interdependent layers. Select a layer to review its definition and what is protectable within it, then select any component for its formal definition and operational function.

Layer 03

Structured Incident Record

Definition
A persistent, uniquely identified and continuously updated digital representation of the incident containing defined fields for participants, vehicle, location, safety state, service requirements, commercial status, workflow state and event history.
What is protectable
The record operating as the control mechanism for the entire workflow — every decision reads from it and every action writes back to it.
Patent support
Claim set — structured incident recordSpecification — record domainsFigures — record schema
Interdependence
Components

Core Patent Elements

The BATA Patent Boundary

Within the patent boundary
CaptureInterpretationRecord creationSafety assessmentDecision logicProvider matchingPricingOrchestrationLifecycle updatesAudit history
External participants and systems
MotoristVehicleInsurerAutomotive manufacturerService providerTowing operatorRepairerEmergency servicesExternal software platforms

External systems can interact with the architecture without becoming the central control architecture.

Technical Interdependence

Capture Without Interpretation

Information remains unstructured and cannot reliably drive the operational response.

The patent position derives strength from the technical relationship between the layers and the continuous operation of the incident record throughout the event.

Claim Architecture

Primary system position

Integrated Roadside Incident Management System

  • One or more data-receiving interfaces
  • One or more processors
  • Incident interpretation logic
  • Structured incident record generation
  • Operational decision logic
  • Provider and service orchestration
  • Incident update and lifecycle management
Primary method position

Computer-Implemented Method for Managing a Roadside Incident

  • Receiving incident information
  • Analysing the information
  • Generating a structured incident record
  • Determining incident requirements
  • Selecting a response
  • Initiating one or more workflows
  • Monitoring the incident
  • Updating the record
  • Progressing the event to resolution

The claim structure is intended to preserve the central integrated architecture while supporting multiple technical and commercial embodiments.

Claim Development Direction

The provisional filing establishes the priority date. The claim roadmap below sets the intended development order through to the complete specification and international filing. Select sub-claims to assemble an indicative claim set for discussion.

Priority 1 — intent

Secure the broadest defensible independent claim to the integrated system and method for capturing, interpreting, structuring and orchestrating a roadside incident through a persistent incident record.

Selected claim set
03

sub-claims selected across 4 priority tiers

Priority 1
  • 1.1 Independent system claim
  • 1.2 Independent method claim
  • 1.3 Structured incident record
Claim scope is developed progressively: the core architectural position is secured first, functional depth and downstream breadth follow as dependent and continuation claims, and jurisdictional expansion proceeds through the PCT pathway within the priority year.

Claim-to-Architecture Mapping

Select an architecture component to see which claim directions it supports, and how each direction relates to that component. Hovering a claim direction highlights every other component it also covers.

Structured record — supported claim directions
Structured incident record

A persistent, uniquely identified record holding participants, vehicle state, safety state, required response, workflow state and event history.

1.1Independent system claimPrimary
Priority 1 · Core architectural position

The record is the structural element that binds every other component of the system.

1.3Structured incident recordPrimary
Priority 1 · Core architectural position

Directed to the composition and persistence of the record itself.

1.4Computer-readable medium claimPrimary
Priority 1 · Core architectural position

Instruction claim covering creation and maintenance of the record on one or more processors.

2.5Event-driven record updatingDependent
Priority 2 · Functional depth

State transitions and audit entries generated as participants and systems report events.

Each architecture component maps to more than one claim direction, and several directions span multiple components. That overlap is deliberate: it reflects the interdependence of the layers and supports a claim set that is difficult to design around by substituting any single component.

Breadth of the Patent Position

Structured Incident Record

The architecture is capable of operating across different incident types, service networks and enterprise environments without being limited to one consumer interface or one roadside service.

Technology-Neutral Implementation

01

Not dependent on one specific mobile application

02

Not dependent on one specific artificial intelligence model

03

Not dependent on one specific mapping provider

04

Not dependent on one specific insurer

05

Not dependent on one specific provider network

06

Not dependent on one specific vehicle manufacturer

The architecture can be implemented across different interfaces, software platforms, artificial intelligence systems, provider networks and enterprise environments.

The patent position is directed to the technical process and orchestration architecture, not to a single branded implementation.

Official Filing Information

Particulars as recorded on the IP Australia notice of filing dated 30 June 2026. These are the official details of the provisional application underlying this presentation.

Official title of invention

DATA COMMUNICATIONS NETWORK AND METHOD FOR MANAGING ROADSIDE INCIDENTS

Australian Provisional Patent Application No. 2026905919 · Filed 30 June 2026

Application number
2026905919
Application type
Provisional patent application
Filing office
IP Australia (Australian Government)
Filing date
30 June 2026
Priority period expires
30 June 2027
Applicant
Bata Holdings Pty Ltd
Applicant address
Suite 6, 15 Boree St, Ulladulla NSW 2539, Australia
Inventor
Henderson, Donald
Attorney of record
Murray Trento & Associates Pty Ltd
Attorney reference
35079AU1
Specification as filed
  • Description
  • Claim(s)
  • Drawing(s)

A complete application or PCT application must be filed on or before 30 June 2027 to claim priority from this filing.

Public register

Application details are viewable on Australian Patent Search (AusPat).

Open Australian Patent Search

Address for correspondence and legal service: PO Box 2191, Blackburn South VIC 3130, Australia.

The provisional filing establishes the priority date of 30 June 2026 for the disclosed architecture and methods.

Current Patent Status

  1. Stage 01Completed

    Australian Provisional Patent Application Filed

    Australian Provisional Patent Application No. 2026905919

    The provisional filing establishes the initial priority position for the disclosed BATA architecture and associated methods.

  2. Stage 02Current Development

    Patent Position Refinement

    The architecture, technical embodiments, commercial applications and supporting claim positions continue to be developed within the priority period.

  3. Stage 03Next Filing Stage

    International Patent Application

    The anticipated next stage is the preparation and filing of an international patent application claiming priority from the provisional filing.

  4. Stage 04Future Jurisdictional Stage

    National and Regional Patent Phases

    Selected national and regional patent applications may subsequently be pursued according to the commercial value, market relevance and strategic pathway of the technology.

Relevance of the Patent Position to Agero

Agero's established operations across roadside assistance, provider dispatch, connected vehicles, accident management, repair coordination and enterprise integrations create a commercially relevant environment for considering the BATA architecture.

Architecture Extension

The BATA position may extend incident management from discrete service workflows into a common incident-level orchestration architecture.

Incident Data Continuity

The structured incident record may support continuity across roadside, recovery, repair, insurer and claims processes.

Integrated Decision Logic

Safety, provider suitability, commercial rules and workflow sequencing may operate from a common digital incident representation.

Strategic Patent Access

The patent position creates a basis for considering licensing, integration, collaboration, acquisition or another strategic transaction structure.

Patent Position Findings

01

The BATA position is directed to an integrated technical architecture rather than an isolated roadside-service feature.

02

The structured incident record is the central control object through which incident information, decisions and workflows are coordinated.

03

The inventive position includes the continuous use and updating of the incident record throughout the operational lifecycle.

04

The architecture integrates incident interpretation, safety, provider suitability, commercial logic and downstream workflow management.

05

The position is capable of supporting multiple technical embodiments, service categories and enterprise integrations.

06

The current provisional filing provides the foundation for continued claim development and broader international patent protection.

Patent Position

The BATA patent position protects the architecture through which a roadside incident is transformed from fragmented information into a structured, intelligent and continuously governed digital event.

The central inventive concept is the creation and use of the structured incident record as the operational control object for interpreting, deciding, orchestrating and resolving the incident.

The patent position is not centred on one roadside transaction. It is centred on the technical architecture that governs the complete incident.