Dependent Method Claims 2–6 — Detailed Mapping
Additional Method-Claim Limitations Assessed Against Publicly Disclosed iRacing Functionality. Each dependent claim carries two separate findings: the additional limitation, and the dependent claim as a whole including every limitation inherited from Claim 1. No percentage scoring is used and no infringement conclusion is drawn.
Granted U.S. Patent —US 12,528,021 B2
View Issued Claims 2–6Opening legal framework
Dependent Claims Incorporate Claim 1
Claims 2–6 each depend from independent Claim 1. Each therefore incorporates all limitations of Claim 1 and adds a further technical requirement.
Governing legal structure
CLAIM 1 + ADDITIONAL DEPENDENT-CLAIM LIMITATION = DEPENDENT CLAIM
A dependent claim cannot be treated as completely mapped unless both Claim 1 and the additional dependent limitation are established.
Claim 1 — Base Method Architecture
Claim 2
+ user performance data
Claim 3
+ 2D or 3D representation
Claim 4
+ modifiable environmental / physical conditions
Claim 5
+ user-modifiable virtual equipment
Claim 6
+ specified virtual racing landscape
The additional limitation may exhibit strong correspondence with publicly disclosed iRacing technology even where complete correspondence with the dependent claim as a whole remains unestablished, because one or more limitations inherited from Claim 1 remain unresolved. This distinction is fundamental.
Methodology
Dual Assessment Format — Two Separate Findings Per Claim
A. Additional limitation assessment
How strongly does the additional limitation correspond with the identified iRacing functionality?
B. Whole dependent claim assessment
Does the currently available public evidence establish the dependent claim as a whole, including all inherited limitations of Claim 1?
These assessments are never merged. For example: the additional Claim 3 limitation is publicly established, but Claim 3 as a whole is not established from current public disclosures because complete Claim 1 correspondence has not been established. This format is used consistently for Claims 2–6.
No percentage-overlap scoring is used anywhere in this section, and no infringement conclusion is drawn. Assessments are descriptive technical statements about the current public record only.
Dependent claim 02
Claim 2 — User Performance Data
Exact issued claim language
“The method according to claim 1, further including receiving, by the one or more processors, data relating to performance of one or more users who virtually participate in the racing event.”
Controlling text: the issued claim set of US 12,528,021 B2.
Technical requirement
- One or more processors receive data.
- The data relates to performance of one or more users.
- Those users virtually participate in the racing event.
The additional limitation does not merely require user identity; it requires data concerning user performance. The claim broadly requires performance-related user data — not every possible performance metric listed below is required.
Potential categories, where supported by evidence
- lap time
- race results
- telemetry
- speed
- braking
- throttle
- steering
- safety performance
- race incidents
- driver rating
- session performance
- race history
Not every possible performance metric is treated as required; the claim broadly requires performance-related user data.
Public evidence
Identified First-Party Evidence — Claim 2 Additional Limitation
iRacing states that Safety Rating is a driver safety/performance indicator determined using incident points, corner counts and session information, is maintained separately across racing disciplines, and is currently described on a scale running from 0.00 to 4.99.
iRacing SupportiRacing How-To: Safety Rating (support documentation)Last modified 15 July 2026
iRacing describes incident points as recorded per-session events arising from contact and off-track excursions, forming the input to the safety metric.
iRacing First PartyiRacing 101: Incident Points20 June 2024 (historical disclosure; feature described as current)
iRacing's 2025 Season 1 Vehicle Telemetry Update describes a dedicated anonymized race data telemetry collection system: race data telemetry is automatically generated while participating in selected official series, telemetry from opted-in participants is collected after the session, and the data is used to support future iRacing improvements and features.
iRacing Release Documentation2025 Season 1 Vehicle Telemetry Update [2025.02.18.01]18 February 2025 (last modified 25 February 2025)
iRacing publicly provides lap timing, race results, driver positions, session information, performance history and user telemetry output as part of ordinary participation and post-session review.
iRacing Sporting CodeiRacing support documentation and Official Sporting Code (driver skill ratings, race procedures)Sporting Code V.2025.09.09; accessed for this review August 2026
iRacing's February 2026 development update states that the newer in-sim UI includes live telemetry capability, including brake and throttle traces over time, to help users understand their own driving performance.
iRacing Release DocumentationiRacing development update, February 2026February 2026
Claim 2 — technical flow
User Performance Data Handling
User participates in iRacing session
Driver input / performance
Lap times · Throttle · Brake · Steering · Incidents · Race result · Telemetry
iRacing system
Performance data received / recorded / processed
Strong public evidence of performance-data handling.
A. Additional limitation assessment
Additional Claim 2 Limitation
Publicly available iRacing materials establish that iRacing receives, stores and/or processes multiple categories of data concerning users' performance during virtual racing activity.
This corresponds strongly with the additional performance-data requirement of Claim 2.
Descriptive assessment only. No numerical or percentage scoring is applied.
Important distinction
User performance telemetry is not physical-event participant telemetry
iRacing's internal user telemetry strongly supports Claim 2's additional performance-data limitation. It does not establish Claim 1's external physical-event data feed. User performance telemetry and physical-event participant telemetry must be kept separate at all times.
B. Whole dependent claim assessment
Claim 2 as a Whole — Not Yet Established
Claim 2 incorporates all limitations of Claim 1.
Section 06 identified unresolved Claim 1 requirements, particularly the event data feed from a corresponding physical racing event, event-derived virtual participant representation, participant movement according to corresponding physical movement, and user competition against those event-derived participants.
Strong correspondence with Claim 2's additional performance-data limitation therefore does not establish Claim 2 as a whole.
Unresolved Claim 1 requirements carried forward (Section 06)
- Event data feed from a corresponding physical racing event
- Event-derived virtual participant representation
- Participant movement according to corresponding physical movement
- User competition against those event-derived participants
Dependent claim 03
Claim 3 — 2D / 3D Representation of the Physical Racing Environment
Exact issued claim language
“The method according to claim 1, wherein the multi-dimensional virtual environment is either a three dimensional or two dimensional representation of the physical environment of the racing event.”
Controlling text: the issued claim set of US 12,528,021 B2.
Technical requirement
- The virtual environment takes a specified dimensional form: three-dimensional or two-dimensional.
- That environment represents the physical environment of the racing event.
For iRacing, the principal relevant implementation is clearly three-dimensional.
Public evidence
Identified First-Party Evidence — Claim 3 Additional Limitation
iRacing publicly describes a highly detailed three-dimensional simulation environment, with track-building technology using real-world scan data and modelling to recreate physical racing circuits.
iRacing First PartyiRacing Track Technology (first-party)Evergreen product page; accessed for this review August 2026
Section 06 established strong public evidence relating to physical track geometry, track surfaces, elevation, camber, bumps, surrounding structures and the racing environment.
iRacing First PartySection 06 — Claim 1 mapping (internal cross-reference)This review, August 2026
The 2026 Season 3 release identifies a full rebuild of WeatherTech Raceway Laguna Seca using new scan data and artwork, while other tracks received fully modelled 3D curbs and updated surfaces.
iRacing Release DocumentationiRacing 2026 Season 3 release documentation2026 Season 3
The 2026 Season 1 release similarly describes new scans and complete environment rebuilding for multiple circuits.
iRacing Release DocumentationiRacing 2026 Season 1 release documentation2026 Season 1
iRacing publicly lists a large catalogue of recreated real-world circuits in numerous configurations.
iRacing First PartyiRacing Tracks (first-party)Evergreen product page; accessed for this review August 2026
A. Additional limitation assessment
Additional Claim 3 Limitation
There is strong first-party public evidence that iRacing provides three-dimensional representations of physical racing environments.
Current release documentation shows continued rebuilding of those environments from updated physical scan data.
The additional Claim 3 limitation is one of the strongest individual areas of correspondence identified in the present analysis.
Descriptive assessment only. No numerical or percentage scoring is applied.
B. Whole dependent claim assessment
Claim 3 as a Whole — Not Yet Established
The dependent claim includes Claim 1.
The unresolved event-feed and event-participant requirements identified in Section 06 remain unaddressed on the present public record.
Unresolved Claim 1 requirements carried forward (Section 06)
- Event data feed from a corresponding physical racing event
- Event-derived virtual participant representation
- Participant movement according to corresponding physical movement
- User competition against those event-derived participants
Dependent claim 04
Claim 4 — Modifiable Event Conditions
Exact issued claim language
“The method according to claim 1, wherein the multi-dimensional virtual environment that substantially simulates the physical environment of the racing event is modifiable to simulate any defined environmental and/or physical conditions.”
Controlling text: the issued claim set of US 12,528,021 B2.
Technical requirement
- The virtual environment is modifiable.
- The modification simulates defined environmental conditions and/or physical conditions.
The terms 'environmental' and 'physical conditions' should not be narrowly construed without counsel review. The specification may provide examples, but the issued language controls.
Public evidence
Identified First-Party Evidence — Claim 4 Additional Limitation
iRacing documents three weather generation modes — Static Weather (parameters including cloud cover, track moisture and temperature), Forecasted Weather (users may define conditions or allow iRacing to generate realistic weather using historical weather data sourced from the selected track) and Timeline Weather (conditions configured across a session timeline). Rainfall and wet conditions are modelled for supported cars and tracks.
iRacing SupportiRacing Weather System & Rain (support documentation)Last modified 9 September 2025
Current iRacing release documentation describes dynamic track behaviour including track surface temperature, solar-energy effects, moisture, water drainage, dust, effects from vehicle tyres and changing racing-surface properties.
iRacing Release DocumentationiRacing 2026 Season 3 release documentation (dynamic track model)2026 Season 3
iRacing's AI race setup documentation states that users may configure weather, track conditions, track options, time of day, cars and event structure.
iRacing SupportHow To Use iRacing AI (support documentation)Accessed for this review August 2026
A. Additional limitation assessment
Additional Claim 4 Limitation
iRacing publicly discloses sophisticated configurable and dynamically evolving environmental and physical conditions within its virtual racing environments.
Evidence includes weather, rain, temperature, track moisture, historical weather modelling, dynamic track state, water drainage, surface temperature and track evolution.
The virtual environment is therefore not merely a fixed geometric model: physical racing conditions can evolve computationally during a session.
Descriptive assessment only. No numerical or percentage scoring is applied.
Important distinction
Environmental modification does not establish the Claim 1 event data feed
The fact that iRacing can modify environmental conditions does not establish that the underlying environment has been generated from the event data feed required by Claim 1. Separately, historical weather data used to create realistic iRacing weather must not be confused with historical racing-event data under Claim 1: iRacing's weather documentation states that automatic forecast mode may use historical weather data from the selected track, which is highly relevant to Claim 4's environmental modelling but does not by itself establish Claim 1's racing-event data feed.
B. Whole dependent claim assessment
Claim 4 as a Whole — Not Yet Established
The additional limitation is strongly established on the public record.
The incorporated Claim 1 requirements remain incomplete on present public evidence.
Unresolved Claim 1 requirements carried forward (Section 06)
- Event data feed from a corresponding physical racing event
- Event-derived virtual participant representation
- Participant movement according to corresponding physical movement
- User competition against those event-derived participants
Dependent claim 05
Claim 5 — Virtual Equipment Modified by User Input
Exact issued claim language
“The method according to claim 1, wherein the multi-dimensional virtual environment further includes virtual equipment that is/are modifiable in part, or whole, according to user input entered prior to and/or during the racing event.”
Controlling text: the issued claim set of US 12,528,021 B2.
Technical requirement
- The virtual environment includes virtual equipment.
- That equipment is modifiable in part or in whole.
- The modification occurs according to user input.
- The user input may be entered prior to and/or during the racing event.
This is broader than merely selecting a car: the analysis identifies actual virtual vehicle/equipment parameters that users may modify.
Public evidence
Identified First-Party Evidence — Claim 5 Additional Limitation
iRacing support documentation explains that users may modify extensive vehicle setup parameters, including ride height, spring rate, damper settings, aerodynamic settings, tyre pressure, brake settings and suspension-related settings; the iRacing garage permits setup changes, and setups may be loaded, imported, shared and modified.
iRacing SupportiRacing Setup: A Beginner's Guide on How to Get Started (support documentation)Last modified 24 October 2025
The first-party iRacing Setup Guide enumerates user-adjustable chassis and aerodynamic parameters including tyres, camber, caster, toe, roll bars, brake bias, spring perch offset, corner weights, wings, springs, dampers and gearing.
iRacing First PartyiRacing Setup Guide (first-party PDF)First-party publication; accessed for this review August 2026
A 2024 rain-system hotfix expressly confirms that rain-ready cars can change tyre compounds in fixed-setup events, and iRacing release documentation identifies brake-bias adjustment during fixed-setup sessions, pit-stop-adjustable aerodynamic parameters on certain cars, refuelling and tyre changes.
iRacing Release DocumentationiRacing rain-system hotfix release documentation2024 hotfix (historical disclosure; feature described as current)
A 2026 release states that certain vehicles support rain tyres that can be equipped and changed during pit stops.
iRacing Release DocumentationiRacing 2026 release documentation2026
Claim 5 — virtual equipment flow
User-Directed Equipment Modification
User
Garage / vehicle setup
Virtual equipment
Tyres · Suspension · Ride height · Aerodynamics · Brake settings · Fuel / strategy · Other permitted parameters
Race session
Permitted in-race modification
Tyre changes · Brake bias · Pit adjustments · Other supported settings
A. Additional limitation assessment
Additional Claim 5 Limitation
iRacing publicly establishes user-driven modification of virtual vehicle/equipment parameters both before racing activity and, for supported parameters, during racing activity.
This is one of the stronger dependent-claim additional limitations, and is directly responsive to the 'prior to and/or during' wording of the issued claim.
Descriptive assessment only. No numerical or percentage scoring is applied.
Important distinction
Developer model updates are not user modification
The claim requires virtual equipment modifiable according to user input. iRacing developers updating tyre physics or a vehicle model is not equivalent to a user modifying virtual equipment. The primary evidence is therefore garage setup, user tyre changes, brake bias, pit-stop changes and similar user-directed functionality.
B. Whole dependent claim assessment
Claim 5 as a Whole — Not Yet Established
Claim 5 incorporates every limitation of Claim 1.
The unresolved event-data-feed and event-derived participant-movement requirements identified in Section 06 remain, so the dependent claim as a whole is not established.
Unresolved Claim 1 requirements carried forward (Section 06)
- Event data feed from a corresponding physical racing event
- Event-derived virtual participant representation
- Participant movement according to corresponding physical movement
- User competition against those event-derived participants
Dependent claim 06
Claim 6 — Specified Virtual Racing Landscape
Exact issued claim language
“The method according to claim 1, wherein the multi-dimensional virtual environment includes a virtual racing landscape selected from any one or more of a race track, an animal race track, an automobile race track, a dirt road, a sports court/arena, a marathon track, a rally (race car) track, a ski/snow field or a body of water.”
Controlling text: the issued claim set of US 12,528,021 B2.
Technical requirement
- The virtual environment includes a virtual racing landscape.
- That landscape is selected from one or more of the enumerated categories.
The claim uses a selection from one or more listed categories. For the iRacing mapping the relevant categories include at least automobile race track, race track, dirt road and rally (race car) track. iRacing is not mapped against categories it does not support — animal racing, marathon events, skiing and bodies of water are not asserted, absent identified evidence.
Public evidence
Identified First-Party Evidence — Claim 6 Additional Limitation
iRacing publicly lists primary racing disciplines including NASCAR oval racing, Formula racing, sports-car road racing, Rallycross, Dirt Oval, Off-Road and Hillclimb.
iRacing First PartyiRacing Racing Disciplines (first-party)Evergreen product page; accessed for this review August 2026
iRacing contains more than 100 tracks in numerous configurations and publicly describes precision recreation of real-world circuits — corresponding with the automobile race track / race track categories.
iRacing First PartyiRacing Tracks (first-party)Evergreen product page; accessed for this review August 2026
The current Official Sporting Code identifies Dirt Road as a racing discipline involving cars/trucks operating on non-circular tracks composed at least partly of dirt racing surfaces, and current 2026 releases continue to add Dirt Road configurations.
iRacing Sporting CodeiRacing Official Sporting Code V.2025.09.09; 2026 release documentation9 September 2025; 2026 releases
iRacing maintains a dedicated Rallycross discipline involving combinations of dirt and pavement, jumps, real-world rallycross venues and purpose-designed layouts.
iRacing First PartyiRacing Rallycross (first-party)Evergreen product page; accessed for this review August 2026
iRacing supports extensive dirt oval racing, including real-world tracks and multiple dirt racing vehicles. 'Dirt oval' is not separately enumerated verbatim in Claim 6 and is treated here as relevant to the broader 'race track' category rather than forced into 'dirt road'.
iRacing First PartyiRacing Dirt Racing (first-party)Evergreen product page; accessed for this review August 2026
A. Additional limitation assessment
Additional Claim 6 Limitation
iRacing clearly operates virtual racing landscapes falling within multiple categories expressly identified in Claim 6, including automobile race tracks, race tracks, dirt-road environments and rally/race-car environments.
The existence of unsupported alternatives within the claim list does not require all alternatives to be present, because the claim permits selection of one or more categories.
Descriptive assessment only. No numerical or percentage scoring is applied.
B. Whole dependent claim assessment
Claim 6 as a Whole — Not Yet Established
Claim 6 incorporates Claim 1.
The unresolved Claim 1 event-feed and participant-movement architecture remains, so the dependent claim as a whole is not established.
Unresolved Claim 1 requirements carried forward (Section 06)
- Event data feed from a corresponding physical racing event
- Event-derived virtual participant representation
- Participant movement according to corresponding physical movement
- User competition against those event-derived participants
Claim 6 — category-by-category
iRacing Supports Multiple Relevant Racing Landscapes
iRacing publicly lists primary disciplines including NASCAR oval racing, Formula racing, sports-car road racing, Rallycross, Dirt Oval, Off-Road and Hillclimb — directly establishing use of multiple forms of virtual racing environment.
Only the landscapes actually supported by iRacing are mapped. No correspondence is asserted with animal racing, marathon events, skiing or bodies of water.
Automobile race tracks
Publicly establishediRacing contains more than 100 tracks in numerous configurations and publicly describes precision recreation of real-world circuits. This strongly corresponds with the automobile race track / race track categories.
iRacing TracksAccessed August 2026
Dirt road
Publicly establishedThe current Official Sporting Code identifies Dirt Road as a racing discipline involving cars/trucks operating on non-circular tracks composed at least partly of dirt racing surfaces. Current 2026 releases continue to add Dirt Road configurations.
Official Sporting Code V.2025.09.099 September 2025
Rallycross / rally-type environments
Publicly established / strong correspondenceiRacing maintains a dedicated Rallycross discipline involving combinations of dirt, pavement, jumps, real-world rallycross venues and purpose-designed layouts. This is highly relevant to the claim's reference to a rally (race car) racing landscape.
iRacing RallycrossAccessed August 2026
Dirt racing (dirt oval)
Relevant to the broader race-track categoryiRacing supports extensive dirt oval racing, including real-world tracks and multiple dirt racing vehicles. “Dirt oval” is not separately enumerated verbatim in Claim 6; it is treated as relevant to the broader “race track” category and is not forced into “dirt road” where that would be technically inaccurate.
iRacing Dirt RacingAccessed August 2026
Master dependent-claim table
Claims 2–6 — Dual Assessment Summary
| Claim | Additional requirement | iRacing public evidence | Additional limitation | Claim as a whole |
|---|---|---|---|---|
| Claim 2 | User performance data. | Safety Rating, telemetry, lap information, race data collection, live input traces. | Established / Strong | Not yet established |
| Claim 3 | 2D or 3D representation of physical racing environment. | 3D laser-scanned circuits, updated physical scan data, three-dimensional racing environments. | Established / Very Strong | Not yet established |
| Claim 4 | Modifiable environmental / physical conditions. | Weather, rain, track moisture, temperature, historical weather, Dynamic Track Model. | Established / Very Strong | Not yet established |
| Claim 5 | User-modifiable virtual equipment before and/or during event. | Garage setup, tyres, suspension, aero, tyre pressure, brake bias, pit adjustments, tyre changes. | Established / Very Strong | Not yet established |
| Claim 6 | Specified virtual racing landscape. | Automobile circuits, dirt roads, Rallycross, dirt racing, road racing. | Established / Very Strong | Not yet established |
Descriptive assessments only. A dependent claim is not described as fully established merely because its additional limitation is publicly established.
Important commercial finding
The Dependent Features Are Not the Principal Public-Evidence Problem
The present review identifies substantial public correspondence between iRacing and each of the additional limitations introduced by Claims 2–6.
The central unresolved issue remains the base architecture inherited from Claim 1, particularly:
Physical race event
Event data feed
Event-derived virtual participants
Movement corresponding to physical participant movement
User competition against those participants
This is an important analytical conclusion: the separation lies upstream of the dependent simulation features, not within them.
Why this matters strategically
iRacing Already Possesses Many of the Downstream Components
Claim 2
User performance data
→ iRacing: strong existing capability
Claim 3
3D racing environment
→ iRacing: strong existing capability
Claim 4
Dynamic environmental conditions
→ iRacing: strong existing capability
Claim 5
User-modifiable virtual equipment
→ iRacing: strong existing capability
Claim 6
Relevant racing landscapes
→ iRacing: strong existing capability
Remaining strategic bridge
Real physical event data
Real participant movement
Event-driven virtual participants
This demonstrates why the granted patent could have strategic relevance even though complete Claim 1 mapping has not yet been established on the public record.
Methodological warnings
Analytical Rules Governing Claims 2–6
Do not misstate Claim 4
Historical weather data used to create realistic iRacing weather must not be confused with historical racing-event data under Claim 1. iRacing's weather documentation states that automatic forecast mode may use historical weather data from the selected track. That is highly relevant to Claim 4's environmental modelling. It does not by itself establish Claim 1's historical racing-event feed. This distinction is critical.
Do not misstate Claim 2 telemetry
iRacing's internal user telemetry strongly supports Claim 2's additional performance-data limitation. It does not establish Claim 1's external physical-event data feed. User performance telemetry must be separated from physical-event participant telemetry at all times.
Do not misstate Claim 5 equipment
The claim requires virtual equipment modifiable according to user input. iRacing developers updating tyre physics is not equivalent to a user modifying virtual equipment. Garage setup, user tyre changes, brake bias, pit-stop changes and similar user-directed functionality are the primary evidence.
Do not misstate Claim 6
Map only the racing landscapes actually supported by iRacing. Do not imply support for animal racing, marathon events, skiing or bodies of water unless evidence is identified. The existence of those alternatives in Claim 6 does not require all alternatives to be present: the claim permits selection from one or more listed categories.
Section 07 evidence repository
Identified Sources — Claims 2–6
| Topic | Source | Provenance | Date |
|---|---|---|---|
| Issued Patent Claims 2–6 | US 12,528,021 B2 — issued claim set | Issued U.S. Patent | Granted patent record; accessed August 2026 |
| User performance data | iRacing How-To: Safety Rating | iRacing Support | Last modified 15 July 2026 |
| Incident points (historical disclosure) | iRacing 101: Incident Points | iRacing First Party | 20 June 2024 |
| Vehicle telemetry collection | 2025 Season 1 Vehicle Telemetry Update [2025.02.18.01] | iRacing Release Documentation | 18 February 2025 |
| Live user telemetry | iRacing development update — in-sim UI live telemetry | iRacing Release Documentation | February 2026 |
| Weather / environmental conditions | iRacing Weather System & Rain | iRacing Support | Last modified 9 September 2025 |
| Dynamic track model | iRacing 2026 Season 3 release documentation | iRacing Release Documentation | 2026 Season 3 |
| User-configurable AI session conditions | How To Use iRacing AI | iRacing Support | Accessed August 2026 |
| Vehicle setup | iRacing Setup: A Beginner's Guide / iRacing Setup Guide | iRacing Support | Last modified 24 October 2025 |
| During-race equipment changes | iRacing release documentation (rain hotfix; 2026 releases) | iRacing Release Documentation | 2024 hotfix; 2026 releases |
| Racing landscapes | iRacing Racing Disciplines | iRacing First Party | Accessed August 2026 |
| Rallycross | iRacing Rallycross (official page) | iRacing First Party | Accessed August 2026 |
| Dirt / Dirt Road | iRacing Dirt Racing; Official Sporting Code V.2025.09.09 | iRacing Sporting Code | 9 September 2025; accessed August 2026 |
Evidence date discipline. Historical disclosures are not presented as necessarily current without confirming continued support. Current 2025–2026 first-party sources are preferred; where a feature was disclosed historically and appears to remain present, both the original disclosure and the current evidence are identified.
Section 07 visual summary
Additional Dependent-Claim Limitations
Claim 2
Performance data
→ Strong
Claim 3
3D environment
→ Very strong
Claim 4
Environmental modification
→ Very strong
Claim 5
Virtual equipment modification
→ Very strong
Claim 6
Racing landscape
→ Very strong
But each claim still incorporates Claim 1
Complete dependent-claim correspondence therefore remains unresolved, because the base physical-event-data architecture has not yet been established.
These are descriptive technical assessments only, and are not a numerical rating system.
Legal review note
Dependent Claim Analysis — Legal Qualification
The additional dependent limitations appear, based upon the identified public evidence, to correspond substantially with multiple established iRacing functions. This does not constitute a conclusion that Claims 2–6 are infringed or fully practised. Each dependent claim incorporates Claim 1 and must be assessed as a complete combination under applicable U.S. patent law.
Commercial / strategic — clearly labelled
Strategic Observation
The public record indicates that iRacing already possesses sophisticated implementations of many of the additional capabilities expressly contemplated by the dependent method claims. These include:
- performance data capture;
- 3D physical environment reconstruction;
- dynamic environmental simulation;
- configurable physical conditions;
- user-modifiable virtual racing equipment;
- multiple claimed categories of racing landscape.
Accordingly, the principal technological separation between current publicly disclosed iRacing functionality and the broader granted method-claim architecture appears to lie not in these downstream simulation features, but in the specific real-world-event-data-to-virtual-participant relationship identified in Claim 1.
Section closing
Claims 2–6 — Current Public-Evidence Position
The additional limitations of Claims 2–6 demonstrate substantial correspondence with publicly disclosed iRacing functionality.
However, because each claim depends from Claim 1, complete correspondence with Claims 2–6 as a whole cannot presently be established until the unresolved limitations of Claim 1 are addressed.
Claim 1 base architecture
+ Strongly corresponding dependent features
Strategic patent relevance
But
Not yet complete whole-claim mapping.
Next
Independent Claim 7 — System Claim
Full limitation-by-limitation system mapping
The next section will separately assess the issued system claim, including the claimed hardware, processor, communication, display, data-feed and user-participation architecture.
The Claim 1 result is not reused: Claim 7 must be independently mapped.