01 — Claim-element gap analysis
Claim elements requiring deployment-level corroboration
The granted claims are directed to a combination of elements. This section sets out that combined architecture, the elements the Woosmap public record presently evidences, and the elements requiring deployment-level corroboration.
The combined architecture
- 01Retailer / business
- 02Consumer device
- 03Previously collected user information
- 04Relevance / matching
- 05Retailer targeting criteria
- 06Retailer-associated location
- 07Geographic condition
- 08Temporal condition
- 09Automatic communication logic
- 10Relevant consumer notification
Already strongly evidenced from Woosmap
- Consumer-device location monitoring
- Store / POI geofencing
- Entry and exit detection
- Historical visits
- Recurrent locations
- Zones of Interest
- Geographic clustering
- Temporal clustering
- ETA processing
- Time-based / isochrone geofences
- Automatic software events
- Contextual notification capability
Elements where deployment evidence could strengthen the mapping
- Relevance / matching using previously collected user information
- Retailer-controlled consumer selection
- Demographic or user-property criteria
- Purchase information
- Search information
- Customer segmentation
- Campaign / journey logic
- Precise time and location notification gating
- Communication enablement and disablement
- Complete operation within one deployed architecture
Evidence-strength system used throughout
- DIRECT PUBLIC EVIDENCE
- Official technical documentation or a named customer disclosure directly establishes the function.
- STRONG PUBLIC INDICATION
- Multiple authoritative public disclosures strongly support the conclusion.
- INTEGRATION CAPABILITY
- The functionality is publicly documented as available through an integration, but specific customer use is not established.
- DEPLOYMENT DEPENDENT
- Specific implementation evidence is required before the position can be taken further.
- NOT YET ESTABLISHED
- No sufficient public evidence has been identified.
United States status categories
- CONFIRMED U.S. DEPLOYMENT
- A reliable public source establishes that the relevant implementation is deployed or used in the United States.
- GLOBAL / NON-U.S. DEPLOYMENT
- The implementation is publicly established, but the disclosed market is outside the United States.
- TECHNICAL INTEGRATION AVAILABLE FOR U.S. DEPLOYMENT
- The capability is publicly documented and available to any implementer; no specific United States customer use is established.
- U.S. STATUS NOT YET ESTABLISHED
- No public source examined addresses whether the implementation operates in the United States.
NO SUFFICIENT PUBLIC U.S. DEPLOYMENT EVIDENCE IDENTIFIED AT THIS STAGE
Capability, integration, deployment and United States evidence are distinct
PRODUCT CAPABILITY
What Woosmap states its technology can do.
Extensively established across the Claim 1, Claim 10 and Claim 19 review environments.
INTEGRATION CAPABILITY
What Woosmap states can be connected to another platform.
Established by four official integration guides: Salesforce Marketing Cloud, Braze, Batch and Airship.
DEPLOYMENT EVIDENCE
What a publicly identified customer is reported to actually use.
Established for several named customers, most substantially the Phoenix Nhance loyalty application.
U.S. DEPLOYMENT EVIDENCE
What is publicly established as occurring in the United States.
NO SUFFICIENT PUBLIC U.S. DEPLOYMENT EVIDENCE IDENTIFIED AT THIS STAGE