U.S. Patent Position Review — 19/476,586
DATA COMMUNICATIONS NETWORK AND METHOD FOR PROVIDING TASK SCHEDULES TO SERVICE PROVIDERS
Published international application: PCT/AU2024/050370 / WO2024216337A1
Section 20 — TR-20
Where Technical Alignment Appears Strongest
A consolidated view of the functions in which publicly observable Taskrabbit technology corresponds most closely to the architecture described in the application. Each entry links to the full function page and to the underlying public evidence.
Executive Finding
Alignment is strongest where the architecture describes structured data operating as an operative constraint — capability, geography, availability — and where a confirmed schedule is generated and transmitted to the provider; it weakens wherever the determination passes to a human or depends on intelligence that is not publicly disclosed.
Provider Capability
Tasker skills and experience are maintained and exposed to customers.
Geographic Operating Area
Taskers define a Work Area Map affecting customer visibility and direct invitations.
Availability
Taskers maintain explicit calendar availability that affects hiring and search eligibility.
Provider Subset
Taskrabbit publicly states that an algorithm produces customer-visible Tasker lists using multiple variables.
Customer Provider Selection
The customer chooses a Tasker from the options presented.
Appointment / Booking
Real-time appointment windows, Bid and Book workflows are exposed through the Partner API.
Combination View
- Task
- Location
- Provider Skill
- Work Area
- Availability
- Algorithmic Tasker Population
- Customer Selection
- Appointment
- Booking
MATERIAL ARCHITECTURAL CORRESPONDENCE WARRANTING DETAILED LEGAL AND TECHNICAL REVIEW
This is a technical correspondence observation. It is not a statement of infringement.
Strong Technical Alignment
Provider-declared availability is reconciled against existing commitments and the customer's requested date and time before options are presented, making this one of the strongest observed alignment areas in the review.
Taskrabbit captures category, task description, service address, supplies, access constraints and preferred timing before any provider is presented, corresponding closely to the service-recipient and task-information layer of the patent architecture.
Customer address and provider-configured work area jointly determine the eligible provider population before any option is presented, which is a direct functional correspondence with the patent's geographic-region element.
Structured, provider-declared categories and skill areas operate as a hard constraint on which Taskers may be presented, aligning closely with the patent's skills element — but skills, qualifications and experience are treated here as three separate concepts, and only skills is strongly evidenced.
The publicly described workflow — estimate, availability, bid, book, project — maps stage for stage onto the schedule-generation and transmission portion of the patent architecture.
Material Technical Alignment
Taskrabbit publicly evidences eligibility filtering by category, work area and availability and indicates ranking factors including rate and business metrics, corresponding to the patent's identification of a subset of suitable providers — while final selection remains with the customer.
Public evidence establishes that Taskrabbit recommends and ranks but leaves final provider selection to the customer, which is a material difference from an architecture in which the system determines the provider and issues the schedule.
Why These Functions Rank Highest
- Each rests on Tier 1 primary sources — official website material, customer help documentation or provider help documentation — rather than on third-party reporting.
- In each, the data in question demonstrably constrains an outcome rather than merely being displayed to a user.
- Each corresponds to a claimed element of the application rather than only to specification or embodiment disclosure.
- The sequence in which they operate matches the operative order described in the architecture, which carries more analytical weight than any function considered alone.
Technical alignment is an analytical assessment of publicly observable functionality and does not constitute a legal conclusion regarding infringement.