AU2023201021A1

AU2023201021A1 - IntegTech is an extension to block chain processing (ie for consistent asynchronous, non-linear, localized, state-driven and/or condition-based procedurality in distributed systems (and enabling safer application of AI learning)) with further models and functionality for enabling collaboratively developed and enforced data standards in potentially spatially distributed systems of block chain capable devices (incl a CleanStaple tag) that can be updated across networks connected atleast intermittently and allowing legal delegations where needed. Also models for ordering, voting, public coords.

Info

Publication number: AU2023201021A1
Application number: AU2023201021A
Authority: AU
Inventors: Julianne Cripps Clark
Original assignee: Individual
Current assignee: Individual
Priority date: 2018-04-24
Filing date: 2023-02-21
Publication date: 2023-04-20
Also published as: AU2022209201A1; AU2018100540A4; AU2021202215A1; AU2019201903A1; AU2021261831A1; AU2021232845A1; AU2023200086A1; AU2022209202A1; AU2024200474A1; AU2023204006A1; AU2022228135A1; AU2022203235A1; AU2021286396A1; AU2022228224A1; AU2024204058A1; AU2023203178A1; AU2023204365A1; AU2022202704A1; AU2021252607A1; AU2023201205A1

Abstract

IntegTech is an extension to block chain processing (ie for consistent asynchronous, non-linear, localized, state-driven and/or condition-based procedurality in distributed systems (and enabling safer application of Al learning)) with further models and functionality for enabling collaboratively developed and enforced data standards in potentially spatially distributed systems of block chain capable devices (including where required a CleanStaple tag) that can be updated across networks connected atleast intermittently and allowing legal delegations where required. Data models for ordering, voting and implementing public co-ordination are included.

Description

IntegTech

AUSTRALIA

Patents Act 1990

Description

REFERENCE TO RELATED APPLICATIONS

AsSecPAI: separate Australian provisional patent IP#2023900320

ConfidOrder: separate Australian Provisional patent IP#2023900226

PoA: separate Australian Provisional patent IP#2023900197

TranVec: separate Australian Provisional patent IP#2023900144

Heap: separate Australian Provisional patent IP#2023900027

ClarZ: separate Australian Provisional patent IP#2023900010

C-oops: separate Australian Provisional patent IP#2022903846

EQoStaple: separate Australian Provisional patent IP#2022903800

PAL: separate Australian Provisional patent IP#2022903799

ActiPALQ: separate Australian Provisional patent IP#2022903798 ParCent: separate Australian Provisional patent IP#2022903608

CleanStaple: separate Australian Provisional patent IP#2022903460

DevBauxSoak : separate Australian Provisional patent IP#2022903444

DevAuxSoak : separate Australian Provisional patent IP#2022903315

QMake-GenPofAdd : separate Australian Provisional patent IP#2022259783

ShyAuBotlntX : separate Australian standard patent IP#2022228224

DaoCanRock :separate Australian standard patent IP#2022228135

ShingleMake :separate Australian standard patent IP#2022224795

AuMake : separate Australian standard patentIP#2022215299

AuTic8 :separate Australian provisional patentIP#2022902158

ProTic8 :separate Australian provisional patent IP#2022901447

QMake: separate Australian standard patentIP#2022209202

DigEMake: separate Australian standard patentIP#2022209201 Optilso: separate Australian provisional patent IP#2022205250

Voxerve: separate Australian provisional patentIP#2022901956

BACdiv: separate Australian standard patent IP#2022201926

DetPatDiv : separate Australian standard patentIP#2022203235

DigiKeyP : separate Australian provisional patent IP#2021901862

ParkCare: separate Australian provisional patent #2021902928

H4Z : separate Australian standard patentIP#2021261831

FunjMakBrake : separate Australian provisional patent #2021901953, Standard patent #2022202704

DigETrace : separate Australian provisional patent IP#2022900156

CGro : separate Australian provisional patent IP#2022900489

AuBotlntX : separate Australian provisional patent IP#2022900696

DigiKeyPLUS : separate Australian provisional patent IP#2022900409

MakTrck : separate Australian provisional patent #2021902872

MkMkT: separate Australian provisional patent IP#2021904151

MkMkTtrailer : separate Australian provisional patent IP#2022900410

SpecQBook :separate Australian provisional patent #2021902885

TickTraceE separate Australian provisional patent IP#2021901140

JicCrack(TT+) : separate Australian provisional patent IP#2022900980

DaoCon: separate Australian provisional patent IP#2022900007 TickerTag : separate Australian provisional patent #2021902946

SafeXShare: separate Australian standard patentIP#2021900281

PartTime: separate Australian provisional patentIP#2021900732

PredEPrev : separate Australian standard patent #2021218217

HoHoBal: separate Australian provisional patent IP#2021903942

DigEMed : separate Australian provisional patent IP#2022900074

ProTic8 : separate Australian provisional patent IP#2022201447

Shyny :separate Australian provisional patent IP#2022900769

EAllln :separate Australian provisional patent IP#2022900883

ECool :separate Australian provisional patent IP#2022900770

QMo :separate Australian provisional patentIP#2022900256

Enco :separate Australian provisional patentIP#2021900934

FlowMake : separate Australian standard patentIP#2021286396 GlobMake: separate Australian provisional patent IP#2021904017

SourceMonitor : separate Australian provisional patentIP#2021900153

SauceMonitor :separate Australian innovations patentIP#2021104349

TickTrackPLUS :separate Australian standard patent IP#2021232845

TranspairPLUS :separate Australian standard patent IP#2021236587

SafeEShare : separate Australian innovations patent#2020100425

DiagML : separate Australian innovations patent#2020901672

PCMF : separate Australian innovations patent#2020902071

IncentiHealth : separate Australian innovations patent#2021103255

BAC : separate Australian provisional patent#2020902146, innovations patent#2021103348

DetPatDIV : separate Australian standard/divisional patent IP#2021202215 (prioritized by

IP#2018100540)

DetPat : separate Australian standard/divisional patentIP#2021202215 (prioritized by IP#2018100540)

AN ONLINE TOOL ALLOWING COMMERCIAL COLLABORATIONS...: separate Australian innovations

patent#2018100747

FIELD OF THE INVENTION

Embodiments of the present invention are in any field of information system processing benefitting

from known quality of data because of the possible sensitivity to data quality of usage outcomes or

because it may be necessary to preserve military or commercial value of authentic data that has been produced carefully, can be understood to the degree necessary (including having capacity to know of

any biases that may exist, especially if the data might be used for Al learning. Al learning systems are not

included) and is constituted with less risk of having been altered. For design consideration purposes a

basic scheme for a community-wide protect-life function has been included in this specification.

BACKGROUND OF THE INVENTION

This is another use of the invention DETPAT (separate Australian Provisional patent IP#2021202215) and

or DETPATDIV (separate Australian Provisional patent IP#2022203235) which each, where developed

and asserted in full, include various data and processing models containing information that needs to be

properly understood by those using that information in other contexts and protected from

indiscriminant and possibly damaging (the data itself or its commercial value) accesses.

It is therefore proposed as not inappropriate to assert it so that it can be included :

M As a patent of addition (eg on 2021202215). Being a data structure it may arguably only be an

unpatentable business method but nonetheless the necessary change to its relevant beneficial

models is being elucidated here in order to enable a cleaner patenting result (if appropriate) and

or to explicitly encourage standardization catering to equitable automation and information

development outcomes.

M As a bibliographically associated patent object for patents not yet closed off (eg any of the

family of inventions related to 2022203235) to that purpose under Australian patenting

procedures and or international agreements.

The entire disclosures of the following referenced applications are hereby incorporated in their

entireties herein including:

ConfidOrder: separate Australian Provisional patent IP#2023900226

PoA: separate Australian Provisional patent IP#2023900197

TranVec: separate Australian Provisional patent IP#2023900144

Heap: separate Australian Provisional patent IP#2023900027

ParCent: separate Australian Provisional patent IP#2022903608

CleanStaple: separate Australian Provisional patent IP#2022903460

Claims

1) The claim for a basic IntegTech method uses DETPAT techniques and particular data standards for

acceptance, interpretation, storage and processing for implementing components of distributed

systems for a range of purposes including where any legal delegations and forms of closely coordinated multi-device processing (including redundancy) or information system processing

related to formalizing order by independent or regulated processes and publically accountable

means can be controlled via DETPAT block chainprocessing implemented on distributed block

chain capable devices (including where required a CleanStaple tag) that can be updated across

networks atleast intermittently.

2) Claims for method for implementing particular data standards for acceptance, interpretation,

storage and processing that can process on local devices may include one or more of :

a) Systemizing, use and/or embed local remedial and or interoperability processing when

operational data is presented as out-of-range of a configured prescribed safe/reliable limit

(tranvec);

b) Systemizing preconfigured translations, scaling, limits, offsets and or other particular filtering

and or categorisations and or processing of messaged inputs to allow multivendor or "overlapping" systems to reference data from compatible or near-compatible data source

devices (tranvec);

c) Systemizing launch of message transactions to complete complex calculations including

consolidation of ranges or probability based processing of records, self-arbitration or voting by

control devices using multiple sources including itself, same or different devices (tranvec);

d) Systemizing bands with limits eg in SCADA systems (tranvec);

e) Systemising performance of summations and "integrations" for surveying, financial,

scheduling, planning and estimating with conditional scaling for alternative graphical

representations using various paramaterised characteristics (tranvec);

f) Safe (ie retrievably) systemizing of varying, diverse and distributed underlying transactions as simple single step records hiding other alternate transactions enabling future analysis that

includes the underlying complexity (tranvec);

g) Systemisation of implemented retests, automated reset-test sequences for a device (tranvec);

h) Systemisation of implemented requests for confirmation from a different device or set of

devices including for a majority vote evaluation and or dialogues with a human (tranvec);

i) Systemising to be able to use a bias checking system (Heap);

j) Functions conforming to DigEStruct Functions related to checking, recording, and or

maintaining data quality in data to be shared or reused (Heap);

k) Systemisation of implemented obligatory standardized block chain technology or technique

that preserves information related to the identity of a source device of an item of information

by placing it in a further protected part of the block chain record as processed on this device

being preserved for this data (Heap);

I) Systemisation of an implemented mechanism to not allow block chain processes to up-quality any source or other data related to quality in block chain transaction data (Heap); m) Systemisation of a standard block chain leaf structure that maintains assurance of data quality embodied by a nominal technical standard of full block chain data quality security across environments in which it is or may be used (Heap), including : i) environments that may allow access to data that is not strictly limited to being via messaging only, ii) that allows messages to be functionally simulated without data quality rules included, or iii) where block chain architecture is not a strict architectural reality; n) Systemisations to implement regulated devices in any jurisdiction electing to preserve the verity or quality of its data according to the provisions of capability in this specification such that those devices are able to launch other devices as verified devices or jurisdictionally verified devices, and optionally able to register other devices with the same standard of verification

(Heap);

o) Systemisations to implement structures in block chain leaf structures referenced by

instructions within device-authenticating pieces of code that enable a record of information

related to the identity and nature of the information processed to be further protected by the

block chain (Heap);

p) Systemisations to implement block chain defaults to a designation meaning "subjective assessment" unless the information is produced under authority of a particular device that is

authoritatively programmed to upgrade the quality of the information otherwise (Heap);

q) Systemisations to implement a foreign key into block chain protected records about

information being processed or transferred that refers to block chain protected DETPAT

consistent structures able to provide context for the information (Heap);

r) Systemisations to implement DETPAT-consistent structures able to provide context for partially

centralized or peer-to-peer controlled produced and used information including for standard

data definitions, production of scientific or commercial reference catalogues and collaboration

process catalogues (Heap);

s) Systemisations to implement a CROCO-informed "skillhistory-person" table access function

(Heap);

t) Systemisations to implement a standard drone registration protocol function (Heap);

u) Systemisations to implement program to populate DETPAT-consistent defined tables or other structured data by output from devices running special programs including pivot tables such

that the device accepts screen-based categorization inputs or other inputs sequenced into one or more structured outputs from a dialogue populating one or more measurement vectors being recorded or reported within records and DigEStructs configured for the purpose (Heap); v) Systemisations to implement DETPAT-consistent structures for block chained distributed emergency planning, checking, monitoring and launching of activities, alerts and or processes to protect living creatures (Heap) including any of: i) hazard, threat, exposure, impact taxonomies, ii) response taxonomies, iii) escalation taxonomies, iv) location based taxonomies, v) function based taxonomies, vi) automation based automation or alert taxonomies, vii) decision-making taxonomies, viii) budget decision-making taxonomies, ix) networking taxonomies, x) working and conflating these into protections at all scales in diverse ways including those from longterm exposures, xi) integrating public care-response systems with the public hospital and ambulance systems, xii) integrating public care-planning systems with public adult education systems and local government; w) Systemisations to implement block chain public care systems with starlink communications

(Heap);

x) Systemisations to implement block chain protected public care systems communicating with

personal worn devices (Heap);

y) Systemisations to use personally configurable data sharing taxonomies with taxonomies,

measures and or assessments in medical or other monitoring systems for the purpose of

monitoring the health or activities of any or one or more of people, animals, plants and or

systems (Heap);

z) Can develop operations (ParCent) with

i) mandatory and agreed methods for developing operations structures including for:

(1) Identifying each separate relevant processing unit function location being used for designed operations as processing units performing one or more location-specific functions for the purpose of seating particular strands and stages of distributed data processing,

(2) (For each separate operation) mapping data entities to their data derivatives with life

of instance paths required by each operation's contributed distributed system outputs

from its distributed inputs that may be updateable by other unknown inputs and that

therefore may be being updated by other unknown devices, beginning at single data

point collection sources and all further connected processing operations including

single data point processing (eg digitizing, filtering, averaging, timed accumulations)

and as required any further combinatory (eg gating, array assembly, addition,

multiplication), logical processing (eg array assembly, array processing, reset, masking,

gating) and output processing,

(3) A developer DigEStruct for ensuring shared maintenance remains consistent across

operations,

(4) Imposing message acceptance boundaries (For each device in the path of an

operation),

(5) Imposing device code update acceptance protocols and conditions for every operation

on DETPATprogrammed devices; ii) agreed MANDATORY Sufficient authorization protocols related to agreed development

architectures and methods;

iii) agreed MANDATORY structure and interface for the system maintained operation-by

operation (ie centralized for each particular system operation being developed or

maintained) with a register of packages of determined systems of operation being

referenced by that operation as an operation-on-device pairing including any paths of

redundancy where agreed as infrastructure for maintaining or developing an operation;

aa) Systemisations for imposing message acceptance (For each device in the path of an operation)

boundaries including conditions for possible arbitrating of alternative message sources for

updates and or outputs (ParCent);

bb) Systemisations for setting up defined alternative information flow paths arbitration triggers

(where there are alternative paths within an operation) between relevant data-collection

devices, detect-and-initiate devices and other-inline-system-consulted devices required to initiate functions within the operation including where controlled sharing and segregation of

data applies each separate matrix process operation as designed via the DETPAT method

(IP#2021202215, IP#2022203235) and break processing into separate modules with any path

arbitration being set up using restriction conditions based on design estimates of the shortest

path in time, the least cost path and both costed and timed or (in the absence of this

information) estimated ranges for likely and acceptable costs and timings of paths (ParCent);

cc) Systemisations for defining particular variations of or to the DETPAT techniques defined in the

DETPAT method specifications (IP#2021202215, IP#2022203235) (ParCent);

dd) Systemisations supporting agreements (ParCent) on :

i) Sufficient authorization protocols related to agreed development architectures and

methods on 'centralised' platforms that may easily hide dangerous complexity and network

latency,

ii) Use of system maintained operation-by-operation (ie centralized for each particular system

operation being developed or maintained) registers of packages of determined systems of

operation being referenced by that operation as an operation-on-device pairing including

paths of redundancy where it is an agreed (by the operation owner as well as its

developers and/or maintainers) part of the infrastructure for maintaining or developing an

operation,

iii) standard operation maintenance infrastructure structures and formats, message formats, block chain types and embedded structures including security mechanisms protecting

those that contain and authenticate transmitted source code, and

iv) Use of any other agreed items of infrastructure for maintaining or developing an operation

or operations including :

(1) certain or standardized diagnosis modes and protocols,

(2) agreed consistent locations in messages for processing more efficient operation,

(3) agreed consistent locations in messages implementing different block chain regulatory

standardizations in different jurisdictions,

(4) restrictions on types of processing allowed on types of devices;

ee) Systemisations to implement certain standard diagnosis modes and protocols (ParCent);

ff) Systemisations to implement other agreed items of infrastructure for an operations method

(ParCent).

3) Claims for legal delegations that can process on local devices and may include one or more of:

a) Defining and implementing transactions by statutory authorities of types of delegation and

other legal processes ('the legal transaction');

b) Making and maintaining definitions, controls and audit requirements within the legal

transaction;

c) Specifying the devices acceptable to statutory authorities for such legal transactions;

d) Specifying the (sub-)transactions that can and or should be made in 'host' systems to

implement a component of a legal transaction;

e) Implementing the mapping of (sub-)transactions that might be to be made in 'host' systems

into statutory systems;

f) Implementing Reporting to statutory authorities;

g) Implementing audit trails;

h) Implementing maintenance controls;

i) Testing, Authorising and Registering a (sub-) transaction in a host system;

j) Reporting.

4) Claims for closely-coordinated multi-device processing may include part centralization involving

certain common functions including one or more of :

a) Common outputs (timed images from the same device) eg changes in monitored space

detected from image/map comparisons;

b) Common outputs (paired devices at the same time) eg stereo vision for 3D targeting;

c) Controlled sharing of outputs eg space monitor map processed as an unknown change (a

potential meteor) being transmitted as quickly as possible across various networks to perform

any of or similar tasks to :

i) processing of an agreed international standard possible-meteor alert function train,

ii) a domestic seek technical identification function, as well as

iii) launch a sovereign owned or standard international satellite interrogation;

d) Segregation of controlled outputs eg shared general access to a space monitored image/map

(monitored changes) and possibly other processed versions or conflations (eg different

wavelengths, responses from other data enquiries), but only military access to subsequent 'missile confirmed' map being derived from extra conflations on that same processed

image/map;

e) Redundancyeg by multiple different satellites, measure references (eg different moon bases); f) Common inputs (multiple sources) such as Switching satellite feeds, Switching frames of

reference eg positioning relative to only currently visible earth geo signals or star signals;

g) Common inputs (different times/needs) such as Switching satellite feeds, Changing

components eg updating array element processing configurations (change in processing

path/requirements);

h) Agreed turn-off or self destruction protocols if these are ever implemented in satellites or

missiles;

i) Agreed device message collection protocols (eg triggered by specific detections for

appropriately ready devices).

) Claims for formalizing order by independent or regulated processes and publically accountable

means on coordinating localised devices may include one or more of:

a) Defining and implementing by statutory authorities of Ordering transactions for different types

of Regulated Ordering ('a legal Ordering'), with allowance for the multiplicity of ready-made

constituencies and or jurisdiction under which a body operates and or may have been

constituted;

b) Specifying the (sub-)transactions that can and or should be made in Regulated Ordering

systems to implement an Ordering or Election, recognizing the full range of required different

combinations of ready-made or other constituencies or jurisdictions under which a group of

individuals or a body operates and or may have been constituted;

c) Implementing the objects and mapping of (sub-)transactions that might be required for an

election in a 'host' ordering (eg racing) or election system;

d) Implementing Reporting to regulatory/statutory authorities;

e) Implementing audit trails;

f) Implementing maintenance controls;

g) Testing, Authorising and Registering a (sub-) transaction in a host system;

h) Reporting.

6) Claims for a CleanStaple tag include it being configured as a device operating with a DigiKeyP OS or

a DigiKeyP OS-like operating system and/or after deregistration as a CleanStaple device can be

optionally further reconfigured to be suitable for use and thus for designation as any of:

a) A DevBauxSoak device;

b) A container device with a restricted set of functions used to shield a non-container device;

c) a QMake device;

d) a DigEMake device;

e) an enhanced CleanStaple device graphically capable and able to display settings pertinent to

the relationship/s and or functions currently operating via the device.

7) Claims for a CleanStaple tag may further include optionally enhancing The basic H4ZPlus method of

claim 1 of IP#2021261831 (H4ZPLUS) with any one or more of:

a) setting up a CleanStaple device;

b) using standard DigEStructs for emissions tracking;

c) implementing tax neutral tagging by transferring any tax processing that may existed or was

implied by existing dedicated non-CleanStaple H4Z tags to non-H4Z-tag processing for

reflection on non-H4Z product tags only, and thereafter using a CleanStaple tag to represent a

non-taxed mechanism of a substituted CleanStaple tag that represents the sinking of a

designated amount of emissions numerically equivalent to the agreed and designated amount

of emissions due to be produced as a result of future processing of the quantity of specific

product tagged and thereafter altering non-ClearStaple H4Z tags where required to by law to

include a detectable and or clearly visible flag on non-ClearStaple H4Z tags denoting that the

particular record and or tag may have tax implications in some jurisdictions;

d) an ability to be decommissioned and then recommissioned with software for other block chain

controlled functions;

e) an ability to protect current and historical transactions against cyber attack in a standard but

safe way.