Prior art — US Patent 12254103

Analysis of Prior Art for U.S. Patent No. 12,254,103

This analysis reviews the prior art cited by the USPTO examiner during the prosecution of U.S. Patent No. 12,254,103. The focus is on determining whether any single reference anticipates the patent's independent claims (Claims 1, 11, and 16) under 35 U.S.C. § 102, which requires that a single prior art document disclose every element of a claim.

The core inventive concept of patent 12,254,103 appears to be the interactive method where a mobile device's eID wallet advertises multiple data sources ("namespaces") along with their specific security rules, allowing an external reader (or "verifier") to evaluate these rules and select the most appropriate namespace for a given transaction. This shifts some of the decision-making logic to the reader, which can then choose a namespace based on its own capabilities and the level of trust required.

Based on the examiner-cited references, the following are the most relevant prior art.

1. US Patent Application Publication No. 2015/0040180 A1

Full Citation: US 2015/0040180 A1, "Information firewall," assigned to Palo Alto Research Center Incorporated.
Date: Published February 5, 2015 (filed August 1, 2013). This qualifies as prior art.
Brief Description: This reference discloses an "information firewall" for a device, which can be a mobile device. The firewall intercepts requests for data and applies policies to control what information is released. These policies can be associated with specific collections of data, analogous to the "namespaces" in patent 12,254,103. The system is designed to protect a user's private data by enforcing rules before any information is shared with an external requester.
Potential Anticipation Analysis:
- Claim 1: This reference teaches associating security policies with data collections on a mobile device and having a requester (reader) communicate with that device. However, it does not appear to disclose the key step where the reader selects a namespace based on the security policies. In the '180 application, the firewall on the mobile device enforces policies against an incoming request. It does not describe a preliminary step where the device advertises its data collections and their corresponding policies to allow the reader to make an informed selection beforehand.
- Claims 11 and 16: The specific back-and-forth communication protocols detailed in claims 11 and 16 are not described. The '180 application does not teach a mobile device receiving a list of selected namespaces and then returning the security rules for them, nor the comprehensive negotiation process outlined in claim 16. The policy evaluation and enforcement happen entirely on the mobile device after a request is made.

Conclusion: This reference is relevant for its disclosure of policy-based data access on a mobile device but fails to anticipate the claims because it lacks the crucial element of the reader selecting a namespace based on policies communicated from the mobile device.

2. US Patent Application Publication No. 2012/0159195 A1

Full Citation: US 2012/0159195 A1, "Writing application data to a secure element," assigned to Google Inc.
Date: Published June 21, 2012 (filed December 17, 2010). This qualifies as prior art.
Brief Description: This application describes a system for managing access to a secure element (SE) on a mobile device. It involves a trusted service manager that defines and enforces access control rules for different applications wanting to read from or write to the SE. This establishes a framework for applying security policies to data stored in a protected area of a mobile device.
Potential Anticipation Analysis:
- Claim 1: The '195 application discloses security policies for data on a mobile device. However, its focus is on managing application permissions, typically during installation or provisioning, rather than facilitating a real-time eID transaction with a reader. It does not describe a reader discovering multiple namespaces (e.g., different ID types like a driver's license and a university ID) and choosing one based on their respective security policies.
- Claims 11 and 16: The interactive model is fundamentally different. The '195 application concerns a trusted manager controlling application access, not an eID reader negotiating access with an eID wallet as described in the detailed steps of claims 11 and 16. The specific query-response flow for security policies is not present.

Conclusion: While this reference relates to security policies on mobile devices, it addresses a different technical problem (secure application management) and does not disclose the claimed method of a reader dynamically selecting a namespace for an eID transaction based on advertised security rules.

3. US Patent Application Publication No. 2006/0265508 A1

Full Citation: US 2006/0265508 A1, "System for administering a multiplicity of namespaces containing state information and services," listing Franklin J. Angel as the inventor.
Date: Published November 23, 2006 (filed May 2, 2005). This qualifies as prior art.
Brief Description: This reference details a server-based system for managing and controlling access to multiple, distinct namespaces. An administration server enforces policies that govern how different entities can access the data and services within each namespace. The system is designed to provide secure, isolated data environments.
Potential Anticipation Analysis:
- Claim 1: The '508 application teaches the concept of associating policies with namespaces. However, the policy enforcement and access control logic are centralized in an "administration server." It does not describe the specific architecture of patent 12,254,103, where a mobile device communicates policies to a reader, and the reader makes the selection. In this reference, the server enforces the rules, rather than the client/reader choosing which set of rules it wants to comply with.
- Claims 11 and 16: The reference does not describe a mobile device eID wallet or the specific communication protocols where the device sends security rules to a reader in response to a selection. The system architecture and interaction flow are different from what is claimed.

Conclusion: This reference is relevant for its use of "namespaces" and "policies" but does not anticipate the claims because its centralized, server-driven enforcement model is distinct from the reader-driven selection process claimed in U.S. Patent No. 12,254,103.