Patent 9665705
Derivative works
Defensive disclosure: derivative variations of each claim designed to render future incremental improvements obvious or non-novel.
Active provider: Google · gemini-2.5-pro
Derivative works
Defensive disclosure: derivative variations of each claim designed to render future incremental improvements obvious or non-novel.
As a Senior Patent Strategist and Research Engineer, I have analyzed US Patent 9,665,705. The following defensive disclosure document details a series of derivative works and improvements designed to expand upon the core concepts of the patent, thereby creating a body of prior art that anticipates future incremental innovations in this technological domain. This disclosure focuses exclusively on novel variations and combinations.
Defensive Disclosure: Derivative Embodiments of a Biometric-Input Security System
This document discloses enhancements and alternative implementations of a secure access system where a biometric sensor is used for both user authentication and administrative command input. The core concept involves interpreting a series of timed or counted biometric sensor interactions as instructions, such as for enrolling new users.
Axis 1: Material & Component Substitution
Derivative 1.1: System with Flexible Piezoresistive Polymer Biometric Sensor
Enabling Description: The biometric sensor (121) is replaced with a conformable piezoresistive polymer matrix laminated onto a flexible substrate. This sensor measures the pressure distribution of a fingerprint's ridges and valleys. The transmitter sub-system controller (107) is programmed to not only match the static pressure map against stored templates but also to interpret dynamic pressure changes. An "enrollment" command is generated by a unique pressure sequence, such as a "light tap," followed by a "medium tap," followed by a "firm, prolonged press." This provides a multi-dimensional input (X, Y, pressure, time) that is more difficult to replicate than simple presence detection. The controller's firmware utilizes a pressure-thresholding algorithm to differentiate between light, medium, and firm presses, mapping these sequences to specific instructions in a command look-up table stored in ROM (1006).
Mermaid Diagram:
sequenceDiagram participant User participant PiezoresistiveSensor as Piezoresistive Sensor (121) participant Controller as Controller (107) participant Database as User DB (105) User->>PiezoresistiveSensor: Executes pressure sequence (tap-tap-press) PiezoresistiveSensor->>Controller: Transmits raw pressure/time data stream Controller->>Controller: Analyze pressure thresholds and timing alt Is Enrollment Command? Controller->>Controller: Map sequence to "Enter Enrollment Mode" instruction Controller->>User: Signal enrollment mode (e.g., LED feedback) User->>PiezoresistiveSensor: Presents new biometric for enrollment PiezoresistiveSensor->>Controller: Capture new biometric pressure map Controller->>Database: Store new biometric template else Is Authentication Request? Controller->>Database: Request template matching Database-->>Controller: Return Match/No-Match result end
Derivative 1.2: System with Hermetically Sealed Housing and Sapphire Sensor Surface
Enabling Description: The transmitter sub-system (116) is housed in a unibody chassis machined from a Ti-6Al-4V titanium alloy, providing high strength and corrosion resistance for industrial or marine environments. The housing is hermetically sealed to an IP69K rating. All power is supplied via an internal inductive charging coil, eliminating physical ports. The biometric sensor (121) is an optical sensor, but its external surface is a synthetic sapphire lens, providing a hardness of 9 on the Mohs scale for extreme scratch resistance. The "enrollment" command (e.g., a sequence of three taps within two seconds) is detected through the sapphire lens. This combination is designed for environments where the device is exposed to chemicals, abrasives, and high-pressure washing.
Mermaid Diagram:
graph TD A[User presents finger] --> B{Sapphire Lens}; B --> C[Optical Sensor Module]; C --> D[Controller (107)]; D -- Biometric Data --> E{Matching Logic}; E -- Stored Templates --> F[User DB (105)]; D -- Tap/Hold Sequence --> G{Command Interpreter}; G -- Instruction --> H[Enrollment/Admin Function]; H -- Write --> F; I[Inductive Charging Coil] --> J[Power Management IC]; J --> D; subgraph Hermetically Sealed Ti-6Al-4V Housing B;C;D;E;F;G;H;I;J end
Axis 2: Operational Parameter Expansion
Derivative 2.1: Cryogenic Environment Access Control
Enabling Description: The system is designed for controlling access to cryogenic storage facilities (e.g., liquid nitrogen freezers) operating at temperatures down to -196°C. The transmitter sub-system controller (107) and memory (1006) are implemented using radiation-hardened silicon-on-insulator (SOI) components rated for extreme cold. The biometric sensor is an ultrasonic scanner, as capacitive sensors are unreliable at such temperatures. The system's firmware includes a temperature compensation algorithm. The database (105) stores multiple biometric templates for each user, captured at various temperatures, to account for changes in skin elasticity and blood flow. The enrollment command (a specific tap/hold sequence) must be held for a longer duration, as configured in the system's parameters, to compensate for user difficulty in manipulating the sensor with insulated gloves.
Mermaid Diagram:
stateDiagram-v2 [*] --> Idle Idle --> Reading: Finger Detected Reading --> Processing: Read Complete Processing --> Authenticated: Match Found Processing --> Idle: No Match Authenticated --> Unlocked: Send Access Signal Unlocked --> Idle: Timeout Idle --> Admin_Listen: Admin Sequence Start (e.g., long press) Admin_Listen --> Admin_Listen: Tap received Admin_Listen --> Enrollment_Mode: Correct Sequence Admin_Listen --> Idle: Sequence Timeout/Incorrect Enrollment_Mode --> Idle: Enrollment Complete Enrollment_Mode: Temp-Compensated Enrollment Protocol Active
Axis 3: Cross-Domain Application
Derivative 3.1: AgTech Vehicle Immobilization and Authorization
Enabling Description: The system is integrated into the control panel of agricultural machinery like combines and tractors. The transmitter sub-system (116) is a ruggedized module connected to the vehicle's CAN bus. The biometric sensor (121) is embedded in the ignition switch or joystick. A farm manager enrolls operators by placing the system in enrollment mode via a specific sequence (e.g., five rapid taps on the sensor). The "accessibility attribute" stored in the database (105) is a multi-field record containing not only the user's biometric template but also a bitmask indicating which specific implements (e.g., sprayer, harvester head, seeder) they are authorized to operate. Upon successful authentication, the controller (107) sends a command via the CAN bus to the vehicle's ECU to disengage the immobilizer and enable control for the authorized implements.
Mermaid Diagram:
graph LR subgraph CombineHarvester A[Operator] --> B(Biometric Sensor on Joystick); B --> C{Transmitter Module (116)}; C --> D{User & Permissions DB (105)}; C --CAN Bus Signal--> E[Vehicle ECU]; E --> F[Immobilizer]; E --> G[Implement Controller]; end subgraph EnrollmentProcess H[Farm Manager] -- 5 Taps --> B; C --Enters Admin Mode--> C; C --Prompts Manager--> I(Manager authenticates); C --Ready to Enroll--> C; A --Presents Finger--> B; C --Stores Template & Permissions--> D; end
Derivative 3.2: Smart Textile for Sterile Environment Access Control
Enabling Description: The entire transmitter sub-system is implemented on a flexible, washable electronic textile platform. The biometric sensor consists of conductive threads woven into a capacitive grid at the cuff of a lab coat or cleanroom garment. The controller and a thin-film battery are encapsulated in a flexible silicone pod integrated into the garment's seam. To enroll a user to the garment, an administrator uses a master NFC device to put the garment into pairing mode. The new user then performs a "rub-and-hold" gesture on the textile sensor, which the controller recognizes as the enrollment command. Authentication for access to a secure lab or electronic notebook is performed by a simple touch of the cuff sensor. The system can transmit a "duress" attribute if integrated physiological sensors in the garment detect a sudden spike in heart rate combined with a valid authentication.
Mermaid Diagram:
flowchart TD subgraph Garment [Smart Lab Coat] A[Conductive Thread Sensor] B[Flexible Controller & NFC] C[Thin-Film Battery] end subgraph Enrollment D[Admin NFC Device] --Tap--> B; B --Enters Enrollment Mode--> B; E[New User] --Rub-and-Hold Gesture--> A; A --Signal--> B; B --Stores Template--> F[On-Garment Secure Memory]; end subgraph Operation E --Touches Cuff--> A; A --Signal--> B; B --Authenticate--> F; B --Wireless Signal (e.g., BLE)--> G[Lab Door/PC Receiver]; end
Axis 4: Integration with Emerging Tech
Derivative 4.1: AI-Driven Behavioral Biometric Enrollment
Enabling Description: This derivative moves beyond static fingerprint matching. The controller (107) incorporates a lightweight AI inference engine (e.g., TensorFlow Lite). The "biometric signal" is now a combination of the fingerprint and the behavioral characteristic of the press itself—pressure, angle of approach, and duration, captured by a force-sensitive sensor array. The enrollment process, initiated by a standard tap/hold sequence, requires the user to interact with the sensor 5-10 times. The AI model builds a composite template of both the physical print and the behavioral "press signature." During authentication, the AI checks for both. This can detect a "duress" situation if a user's print is correct but their press signature deviates significantly from the norm, indicating coercion.
Mermaid Diagram:
classDiagram class Controller { +TensorFlowLite_Engine +processBiometricSignal() +mapSignalToInstruction() } class BiometricTemplate { +staticFingerprintData +behavioralPressSignature } class ForceSensitiveSensor { +readFingerprint() +readPressureCurve() +readAngle() } Controller "1" -- "1" BiometricTemplate : Manages Controller "1" -- "1" ForceSensitiveSensor : Reads
Derivative 4.2: Blockchain-Based Access Control Ledger
Enabling Description: The system is integrated with a private blockchain for immutable access logs and decentralized identity management. The transmitter sub-system (116), upon a successful biometric match, does not store a simple "access" attribute. Instead, it holds the user's private key in its secure element. The enrollment process (via sensor gestures) authorizes the controller to generate a new key pair and create a "newUser" transaction on the blockchain, binding the public key to a hash of the user's biometric template. To grant access, the receiver sub-system (117) presents a challenge (a nonce). The transmitter sub-system signs the nonce with the user's private key, creating a signature. The receiver verifies this signature against the user's public key on the blockchain and checks their permissions via a smart contract.
Mermaid Diagram:
sequenceDiagram participant Fob as Transmitter Fob (116) participant Lock as Receiver/Lock (117) participant Blockchain Fob->>Lock: Request Access (sends user public key) Lock->>Lock: Generate Challenge (Nonce) Lock->>Fob: Send Challenge Fob->>Fob: User authenticates via Biometrics Fob->>Fob: Sign Challenge with Private Key Fob->>Lock: Return Signed Challenge Lock->>Blockchain: Verify Signature and Permissions(PublicKey, Signature, Nonce) Blockchain-->>Lock: Verification Result (Access/Deny) alt Access Granted Lock->>Lock: Activate Controlled Item (e.g., Unlock Door) end
Axis 5: The "Inverse" or Failure Mode
Derivative 5.1: Duress-Triggered "Honey-pot" Access Mode
Enabling Description: A specific finger (e.g., the little finger), when enrolled, is flagged with a "duress" attribute in the database (105). The enrollment process for this is a unique gesture, e.g., a long press followed by two quick taps. When this duress finger is used for authentication, the system provides two outputs. First, the transmitter sends a standard "access granted" signal using the normal rolling code to the primary receiver (109), which opens the door. Simultaneously, it uses a secondary, low-power transmitter (e.g., LoRaWAN) to send an encrypted, high-priority alert packet to a separate security monitoring system. If the controlled item is a computer, authenticating with the duress finger logs the user into a sandboxed desktop environment with no network access to sensitive shares, appearing normal to an observer but protecting critical data.
Mermaid Diagram:
flowchart TD A[User presents "Duress" finger] --> B{Biometric Sensor}; B --> C{Controller}; C --> D{DB Match (Duress Flag Detected)}; D --> E[Transmit 'Access' signal via Rolling Code]; D --> F[Transmit 'Duress Alert' via LoRaWAN]; E --> G[Primary Receiver -> Unlock Door]; F --> H[Security Center Receiver -> Silent Alarm];
Combination Prior Art Scenarios
FIDO2/WebAuthn Integration: The transmitter sub-system is a FIDO2-compliant security key. The biometric sensor authenticates the user for passwordless login. The administrative command gesture (e.g., a triple-tap on the sensor) is used to broadcast a Bluetooth Low Energy (BLE) advertisement signal, putting the key into "pairing mode" to be registered with a new host computer or service provider. This eliminates the need for a separate pairing button, using the sensor for a standards-based administrative function.
MQTT for Legacy System Integration: The receiver sub-system (117) acts as an MQTT client. It subscribes to a specific topic on an MQTT broker (e.g.,
access/door/1/command). The transmitter fob (116) connects to the same network (e.g., via WiFi) and, after successful biometric authentication, publishes a signed JSON payload to that topic. A separate hardware gateway subscribes to the topic, validates the payload, and translates it into a dry-contact relay closure or a Wiegand signal for a legacy door controller. The entire communication is secured by TLS and managed by the open-source MQTT protocol.RISC-V Microcontroller with Custom Gesture-Decoding Instruction: The transmitter controller (107) is implemented using a low-power, 32-bit core based on the open-source RISC-V ISA (e.g., RV32IMC). A custom instruction,
bsense.gesture, is added to the ISA. This instruction takes a memory address pointing to a stream of time-stamped sensor events as input. When executed, it uses dedicated hardware logic to parse the stream and returns a value corresponding to a recognized gesture (e.g., 0x01 for single tap, 0x02 for double tap, 0x10 for long press). This offloads the complex timing logic from software, allowing the main processor to remain in a deep-sleep state until a complete gesture is decoded, drastically reducing power consumption.
Generated 5/3/2026, 6:04:13 PM