USB
Enable an AI agent to recognise a physical USB connection or interface, assess its compatibility and condition, and decide whether and how it may safely connect devices, transfer data or deliver power.
Bundle → Layer → Finding → Questions Filled
5 bundles · 9 layers · 16 findings · 28 questions
USB identity and physical path Establishes what physical USB instance is being represented and how its connectors form a connection.
Referent and connector
Separates the USB interface from its containing object and identifies its physical mating points.
USB instance boundary
Records the represented physical extent and the evidence identifying its connectors as USB-related.
- Does this instance represent a port, plug, cable, adapter or complete connection, and which containing objects are represented elsewhere? boundary
- What connector family, variant and plug or receptacle form is present at each mating point, and what evidence supports the identification? definition
Connection path
Makes each endpoint and intermediate component available for compatibility assessment.
Path components and mating
Records the proposed or actual route through USB cables, adapters and hubs.
- Which endpoints, cables, adapters and hubs lie along the intended USB path, in connection order? boundary
- Do the mating connectors fit as intended without force, and does each intervening component have evidence of supporting the intended use? action
USB data capability and operation Separates supported USB data functions from the roles and link behaviour observed during use.
Supported data functions
Captures documented data support and endpoint role constraints across the path.
Data support and roles
Records evidence for USB signalling capabilities and supported data roles without deriving them from connector shape.
- Which USB revisions and signalling modes are supported by each endpoint and intervening component, and where is that support documented? provenance
- Which endpoint can act as host and which as device for this task, and is any part of the path explicitly limited to power delivery? boundary
Enumeration and active link
Records whether a usable USB data relationship has actually formed.
Observed USB session
Captures enumeration, exposed functions, active mode and transfer observations for a particular connection session.
- What device identity and USB functions does the host report after attachment, and which expected functions are absent? measurement
- What active USB mode, transfer performance and errors are observed, under which test conditions? measurement
- What evidence supports retrying, changing a path component or investigating an endpoint when enumeration or transfer fails? action
USB power and shared connector modes Captures power arrangements and identifies other operating modes that may use the same connector.
Power capability and contract
Distinguishes supported power arrangements from the current negotiated or measured operating point.
Power path agreement
Records source and sink roles, applicable cable constraints and evidence for the current delivery arrangement.
- Which component supplies power, which receives it, and what voltage, current and power limits are documented for the endpoints and cable? provenance
- What supply arrangement or negotiated power contract is active, and how do measured voltage and current compare with it? measurement
- Can the intended load operate within the evidenced limits of this complete path, or must the agent select another source or cable? action
Shared connector functions
Identifies requested functions whose support cannot be inferred from the physical connector.
USB and other mode boundary
Records whether a requested connector-carried function uses USB or requires a separately modelled protocol or mode.
- Does the requested function use USB data, USB power delivery or another protocol carried through this connector? boundary
- What evidence shows that both endpoints and every cable or adapter support the required mode and its intended concurrent functions? provenance
USB condition and authorised use Connects USB-specific physical and session observations to permitted next actions.
Connector and cable condition
Captures physical defects and intermittent behaviour along the USB path.
USB path serviceability
Records observable connector and cable condition alongside symptoms that may indicate a faulty connection.
- What contact contamination, deformation, looseness, cable damage, moisture or abnormal heating is observed, and at which component? measurement
- Do disconnects or errors follow a particular port, cable or adapter during controlled tests with known-working components? measurement
- Which observations justify stopping use, replacing a component or following the manufacturer's inspection procedure? action
Device trust and session actions
Relates exposed USB functions and ongoing activity to connection permissions and disconnection decisions.
Permitted USB session
Records which USB functions are authorised and what must be checked before enabling or ending their use.
- Who authorises this connection, and are its reported storage, input, network or other USB functions permitted for the intended task? action
- If only charging is authorised, what evidence establishes that the selected connection prevents data access? provenance
- Before disconnection or a role change, what active transfers, mounted storage or power-dependent operations require coordination with the connected device's model? action
Evidence and external alignment What the world already says about this thing, gathered so the model can be checked against it.
Reported evidence
Findings from the breadth pass, kept separate from the structural claims.
Kinds and varieties
Reported by the breadth pass; each item needs checking against its source before it becomes normative.
- Which of these kinds and varieties hold for the sense of USB this model covers, and on what evidence? provenance
Identifiers and schemes
Reported by the breadth pass; each item needs checking against its source before it becomes normative.
- Which of these identifiers and schemes hold for the sense of USB this model covers, and on what evidence? provenance
Standards and regulation
Reported by the breadth pass; each item needs checking against its source before it becomes normative.
- Which of these standards and regulation hold for the sense of USB this model covers, and on what evidence? provenance
Real-world use
Reported by the breadth pass; each item needs checking against its source before it becomes normative.
- Which of these real-world use hold for the sense of USB this model covers, and on what evidence? provenance
Typical measurements
Reported by the breadth pass; each item needs checking against its source before it becomes normative.
- Which of these typical measurements hold for the sense of USB this model covers, and on what evidence? provenance
Failure modes and hazards
Reported by the breadth pass; each item needs checking against its source before it becomes normative.
- Which of these failure modes and hazards hold for the sense of USB this model covers, and on what evidence? provenance
Regional variation
Reported by the breadth pass; each item needs checking against its source before it becomes normative.
- Which of these regional variation hold for the sense of USB this model covers, and on what evidence? provenance
Neighbouring kinds and how to tell them apart
Reported by the breadth pass; each item needs checking against its source before it becomes normative.
- Which of these neighbouring kinds and how to tell them apart hold for the sense of USB this model covers, and on what evidence? provenance
Classifiers Filled
- Family
- Thing Registry
- Category
- Physical world and living systems
- Entry kind
- thing
- Plane
- PHY
- Domain
- PHY.OBJ
- Other names and narrower kinds
- HID++, USB On-The-Go, USB standard connector adapter, USB condom, USB 2 connector adapter
What it is Filled
USB is a host-enumerated, packet-based serial interconnect family that specifies connectors and cables, differential physical-layer signalling, a hub-and-device tree, class protocols, and optional power contracts so a computing host - or a dual-role Type-C partner - can discover, configure, transfer data with, and supply power to attached devices under one electrical and software model.
In scope
- USB port and plug identity, connector form and mating compatibility
- Cable and adapter capabilities across a complete USB connection path
- USB data capability, endpoint roles and observed link operation
- USB power roles, supported supply arrangements and negotiated delivery
- Connection condition, faults and permissions for USB use
Out of scope
- Files, storage health and capacity of a USB flash drive
- Internal operation of a connected keyboard, camera, printer or other peripheral
- Host operating-system administration and general driver lifecycle
- Charger internals, mains wiring and battery chemistry
- The full USB standards family as a normative specification
- Non-USB protocols carried through a shared connector, beyond identifying their presence and requirements
Why it exists Filled
Enable an AI agent to recognise a physical USB connection or interface, assess its compatibility and condition, and decide whether and how it may safely connect devices, transfer data or deliver power.
Distinguishing features Filled
- Establish whether USB is implemented using device documentation or observed USB behaviour; a familiar connector shape alone does not establish data or power capabilities.
- Distinguish connector form from supported USB data operation, recording separate evidence for each.
- Distinguish a USB flash drive from the USB interface it uses by identifying whether storage is the object's primary function.
- Distinguish a complete USB data path from a power-only path by checking the endpoints and every intervening cable or adapter.
- For a connector shared with other technologies, identify whether the active connection is USB or another supported operating mode.
What robots and AI may and may not do Filled
Must not
- Connect an unknown USB device to a system it administers without checking it.
- Use USB ports to copy data from a device or system without authorization.
- Recommend cables or chargers that do not meet the needed power rating.
- Disable USB security controls on managed systems without approval.
Only with a human decision
- Allowing removable USB devices on a protected or safety-critical system.
May
- Identify USB connectors, versions and power ratings and explain compatibility.
- Report a damaged cable, port or charger that should not be used.
Moral aspects Filled
- USB is a common route for malware and data theft.
- Cheap chargers and cables can overheat and start fires.
Who is affected
- Device users
- Organizations handling sensitive data
Owners Filled
Steward
The owner of the device; the specification is maintained by an industry forum.
Links to other meta-models Filled
parent
- Q18819626 - registry parent class
- Q21078287 - registry parent class
- Q2119531 - registry parent class
- Q64693901 - registry parent class
- Q7168699 - registry parent class
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- Vercy registry: vr.tr.usb
- Wikidata: Q42378 (https://www.wikidata.org/wiki/Q42378)
Direct properties required Filled
- Modelled physical extent: port | plug | cable assembly | adapter | complete connection path | unresolved
- Connector identity: documented connector family and variant, plug or receptacle, or unknown
- Connection topology: linked host, peripheral, hub, power source, cable and adapter instances
- USB data capability: documented USB revision and supported signalling modes | explicitly no data capability | unknown
- Observed data operation: disconnected | attached but not enumerated | enumerated | transferring | faulted | unobserved; include active mode when known
- Data role: host | device | role-capable but inactive | unknown; record supported and current roles separately
- Power role and capability: source | sink | dual-role | unknown; documented supply capabilities and negotiation support
- Power operating point: V, A and W, with declared limits, negotiated values and measured values distinguished
- Physical connection condition: observations of contact contamination, connector deformation, cable damage, retention, moisture and heating
- Permitted USB use: applicable authority or policy for charging, data access, device classes and role changes
Recognition required Filled
- Flat rectangular Type-A or small oval reversible Type-C connectors, among others.
- Often marked with the trident USB logo.
Capabilities and actions required Filled
- Identify and label a USB port, cable or adapter with its evidenced connector and capabilities.
- Select a compatible connection path for a specified data-transfer or power-delivery task.
- Connect or disconnect endpoints when physical condition, operating state and permissions allow.
- Inspect enumeration, active data mode and power negotiation to verify the intended operation.
- Isolate a failed or limiting cable, adapter, port or endpoint through controlled substitution and testing.
- Restrict USB use to authorised functions or withdraw a damaged or untrusted component from use.
Hazards and failure modes required Filled
- Malicious devices can install malware or act as a keyboard.
- Faulty chargers and cables can overheat, damage devices or cause fire.
Standards and interfaces required Filled
- Universal Serial Bus specifications, USB Implementers Forum.
Context of use required Filled
- USB connects peripheral devices such as keyboards, storage devices, cameras and sensors to computing hosts.
- It is encountered in personal computers, embedded systems and laboratory equipment for device discovery, data transfer and compatible power delivery.
- Connector shape alone does not establish the supported data speed, device functions or power capabilities.
Sources Filled
- Universal Serial Bus Specification, Revision 2.0 - Core host/device/hub model, descriptors, enumeration, Low/Full/High Speed rates, default 5 V VBUS and unit-load current rules.
- USB4 Specification; USB Type-C Cable and Connector Specification; USB Power Delivery Specification - SuperSpeed/USB4 generations, Type-C pinout and Alternate Modes, CC-based role detection, PD voltage/current contracts and electronically marked cables.
- IEC 62680 series - Universal serial bus interfaces for data and power - International adoption of USB-IF specifications (USB 2.0, Type-C, Power Delivery, USB 3.x) as IEC standards used in regulation and procurement.
- Directive (EU) 2022/2380 amending Directive 2014/53/EU (common charger) - EU legal requirement that specified radio equipment use USB Type-C for wired charging, which drives regional connector practice.
- USB (Q16340) - Stable catalogue identifier for the USB concept as a Wikidata item.
- Wikidata item Q42378: USB - identity and sense of the item
- Wikipedia: USB - general description of the item
Open questions
- Does vr.tr.usb denote the USB interface and its physical implementations, a USB flash drive, or another intended registry concept?
- Does an existing Vercy world model already own this concept, requiring a registry link instead of a separate publication?
- Which USB connector families, specification revisions and legacy power arrangements must the researched model cover?
- Where should ownership divide between this entry and models for cables, connectors, hubs, chargers and non-USB modes using the same connector?
- Which authoritative documentation and permitted observations can substantiate cable capability, power limits and stop-use criteria when markings or device reports are incomplete?
Machine files
Provenance
thing registry research (pass 2) · unreviewed
Built from: models/things/publications/thing-q42378/spec.json