US 7305442

Summary of U.S. Patent 7,305,442

Title: Asynchronous user-authorized advertising

Assignee: The original assignee was Sprint Spectrum L.P. As of the latest assignment recorded on August 23, 2022, the assignee is Sprint Spectrum LLC, along with several other related entities.

Inventors: Michael T. Lundy

Filing Date: October 12, 2001

Issue Date: December 4, 2007

Abstract: A system and method for advertising on a subscriber terminal. A server may send an advertising authorization request to the subscriber terminal. The advertising authorization request may comprise options that a user may select for accepting or rejecting an advertisement to be sent to the subscriber terminal. If the subscriber terminal accepts the advertisement, the server or subscriber terminal may wait for one or more triggering events to occur. The triggering events may include the subscriber terminal being idle, substantially stationary, and/or a specific time of day. Upon occurrence of the one or more triggering events, the subscriber terminal may display the advertisement on its display screen.

Plain-Language Overview of Independent Claims

As of today's date, May 12, 2026, a search of the CAFC 2026 dockets for "7305442" revealed no pending or recent litigation for this patent.

The patent has three independent claims:

• Claim 1: Describes a method for advertising on a mobile device. First, a request for authorization to send an ad is sent to the mobile device. After receiving a reply that authorizes the ad, the system waits for the mobile device to be both "idle" and "substantially stationary." Once both conditions are met, the advertisement is sent to the device.

• Claim 7: This claim also outlines a method for mobile advertising. It starts by sending an ad authorization request and receiving an affirmative reply. However, in this method, the advertisement is sent to the mobile device immediately after receiving authorization. The mobile device then stores the ad and waits to display it until the device is both "idle" and "substantially stationary."

• Claim 9: This claim is similar to claim 7 but with a different starting point. Instead of actively sending a new authorization request, the method begins by retrieving a previously stored reply from memory that already authorizes advertisements for that mobile device. Once this authorization is retrieved, the ad is sent to the device, which then waits to display it until the device is both "idle" and "substantially stationary."

Litigation Search

As of May 12, 2026, a comprehensive search of patent litigation databases, including PACER, Unified Patents, and CAFC dockets, reveals no known litigation where US patent 7,305,442 has been asserted.

While the original and current assignees, Sprint Spectrum L.P. and Sprint Spectrum LLC, have been parties in various legal disputes, none of these cases involve an assertion of US patent 7,305,442. These other cases have dealt with matters such as contract disputes over access charges, infringement allegations concerning different patents, and TCPA (Telephone Consumer Protection Act) class actions.

Therefore, there is no litigation history to report for this specific patent.

Proceedings Overview

There have been zero AIA trial proceedings filed against US patent 7,305,442. This provides a defendant with a clean slate, as no claims have been previously challenged or validated at the PTAB, and no estoppel applies from prior art that could have been raised in such a proceeding.

Strategic Summary

The complete absence of PTAB challenges against US patent 7,305,442 means all claims—both independent (1, 7, 9) and dependent (2-6, 8)—remain untested in post-grant proceedings. For a defendant, this is a double-edged sword. On one hand, the patent is not "hardened" by surviving an IPR, and the full universe of prior art patents and printed publications is available for a potential validity challenge. On the other hand, there is no existing record of the Patent Owner's arguments or the Board's analysis on claim construction or validity, which can sometimes provide a roadmap for a defense.

From an estoppel perspective, a defendant is in a strong position. Because no IPRs have been filed, the estoppel provisions of 35 U.S.C. § 315(e)(2) do not apply. A defendant is free to petition for IPR on any grounds based on prior art patents or printed publications that it can identify, without concern that those grounds were or could have been raised in a prior proceeding. The lack of PTAB activity is itself a notable data point; patents that are frequently asserted often attract defensive IPR petitions from defendants or third-party groups like Unified Patents. The silence here could suggest a lack of aggressive assertion by the patent owner.

Recommended Next Steps

For a defendant facing an assertion of US patent 7,305,442, the key takeaway is that no inter partes review (IPR), post-grant review (PGR), or covered business method (CBM) review has ever been filed.

This means:

• All validity challenge options are on the table. A defendant can conduct a prior art search and, if strong art is found, file an IPR petition at the PTAB without any procedural bars from previous trials.
• The patent's strength is unknown. Without a prior challenge, it is difficult to gauge how the Patent Trial and Appeal Board might construe the claims or view the patent's validity over the prior art.
• No pre-existing record. A defendant and its counsel would need to develop their invalidity contentions from scratch, without the benefit of seeing how the patent owner has previously defended the patent's claims at the PTAB.

Given this situation, the immediate and most critical next step for any defendant is to commission a thorough prior art search focused on the asserted claims. The outcome of that search will dictate the viability of filing a new IPR petition and will be the foundation of any invalidity defense in district court.

Inventors

• Michael T. Lundy: The sole inventor listed on the patent. The initial assignment of his interest was to Sprint Spectrum, L.P. (Reel 012490/0793), indicating he was likely an employee or contractor for Sprint at the time of the invention. There are no unusual patterns, such as inventor departure, discernible from the public record.

Original assignee

The original assignee was Sprint Spectrum, L.P., a major US telecommunications company that built and operated a national wireless network. The company's primary business was providing mobile phone and data services to consumers and businesses. As an operating company in the mobile communications space, Sprint's commercial services were directly related to the subject matter of the patent. Sprint was later acquired by T-Mobile USA, Inc., in a merger that closed on April 1, 2020, and its brand and operations have since been integrated into T-Mobile.

Assignment timeline

• 2001-10-12 (executed) / recorded 2002-01-22 — Reel 012490/0793

  • Conveyance: Assignment
  • Assignor: Michael T. Lundy
  • Assignee: Sprint Spectrum, L.P.
  • Correspondent: Donald D. Prohaska; Sprint; 6391 Sprint Parkway Mailstop: KSOPHT0101-Z2100; Overland Park, KS 66251-2100
  • Context: Standard assignment of invention from an inventor to their employer.

• 2017-02-15 (executed) / recorded 2017-03-03 — Reel 038743/0733

  • Conveyance: Security Agreement (Grant of Security Interest)
  • Assignor: Sprint Spectrum L.P.
  • Assignee: Deutsche Bank Trust Company Americas
  • Correspondent: Duane Morris LLP; Docketing Department; 1901 L Street, N.W. Suite 700; Washington, DC 20036
  • Context: Sprint pledged this patent, among others, as collateral for a financial transaction, a common form of corporate securitization.

• 2020-04-01 (executed) / recorded 2020-04-02 — Reel 050674/0239

  • Conveyance: Security Agreement
  • Assignor: Sprint Spectrum L.P. (and numerous other Sprint/T-Mobile entities)
  • Assignee: Deutsche Bank Trust Company Americas
  • Correspondent: Morrison & Foerster LLP; 425 Market Street; San Francisco, CA 94105
  • Context: A new security agreement was recorded, likely related to financing following the T-Mobile merger which closed on April 1, 2020.

• 2020-04-02 (executed) / recorded 2020-04-03 — Reel 050682/0255

  • Conveyance: Release
  • Assignor: Deutsche Bank Trust Company Americas
  • Assignee: Sprint Spectrum L.P.
  • Correspondent: Duane Morris LLP; Docketing Department; 1901 L Street, N.W. Suite 700; Washington, DC 20036 (Same correspondent as the 2017 security agreement).
  • Context: The security interest from the 2017 agreement was terminated and released, returning full rights to Sprint.

• (N/A) (executed) / recorded 2022-02-11 — Reel 062638/0333

  • Conveyance: Change of Name
  • Assignor: Sprint Spectrum L.P.
  • Assignee: Sprint Spectrum LLC
  • Correspondent: T-Mobile, US, Inc.; 12920 SE 38th Street; Docketing Department; Bellevue, WA 98006
  • Context: An internal corporate restructuring changing the legal entity type from a Limited Partnership (L.P.) to a Limited Liability Company (LLC).

• 2022-08-15 (executed) / recorded 2022-08-23 — Reel 066376/0001

  • Conveyance: Release of Security Interest
  • Assignor: Deutsche Bank Trust Company Americas
  • Assignee: Sprint Spectrum LLC (and numerous other Sprint/T-Mobile entities)
  • Correspondent: Morrison & Foerster LLP; Trademark/Copyright/Patent Docketing; 425 Market Street; San Francisco, CA 94105-2482 (Same correspondent as the 2020 security agreement).
  • Context: The security interest from the 2020 agreement was released, returning full rights to the Sprint/T-Mobile entities.

Timeline diagram

timeline
    title Ownership of US 7305442
    2001 : Invented by M. Lundy
    2002 : Assigned to Sprint Spectrum L.P.
    2007 : Patent Issued
    2017 : Security interest to Deutsche Bank
    2020 : Security interest released
         : New security interest to Deutsche Bank
    2022 : Sprint Spectrum L.P. name change to LLC
         : Security interest released

NPE / troll-pattern signals

1. Shell-entity transfer: Not present. All assignees are either the original operating company (Sprint), its post-merger parent (T-Mobile), or a major financial institution (Deutsche Bank) for a security agreement. The final change of name to an LLC was an internal reorganization, not a transfer to a licensing-only entity.

2. Known asserter in the chain: Not present. Sprint/T-Mobile is an operating company. Deutsche Bank is a financial institution and not known as a patent asserter.

3. Repeat correspondent across the chain: Present, but not in a way that suggests NPE activity. Duane Morris LLP and Morrison & Foerster LLP appear multiple times, but each acted consistently for one side of a financial transaction (Duane Morris for the 2017 security interest and its 2020 release; Morrison & Foerster for the 2020 security agreement and its 2022 release). This reflects standard corporate counsel relationships for securitization rather than a single attorney managing a web of shell LLCs.

4. Cascading transfers: Not present. The transfers are spaced years apart and are related to distinct corporate financing and restructuring events.

5. Pre-litigation transfer: Not present. There is no record of litigation involving this patent.

6. Bankruptcy fire-sale: Not present. Sprint was acquired by T-Mobile, not liquidated through bankruptcy.

7. Privateering: Not present. The patent has remained with the original operating company and its corporate successor.

8. Defensive aggregator (anti-NPE): Not present. The patent is not assigned to any known defensive aggregator.

Verdict

Insufficient data

The assignment record shows the patent was created and has remained within a single large operating company (Sprint, now part of T-Mobile). The only transfers of interest are standard security agreements with a major bank (Reels 038743/0733 and 050674/0239), which were subsequently released. There are no signals whatsoever of a transfer to a non-practicing or assertion-focused entity. The patent remains the property of an operating company.

A full record of the assignment chain can be viewed at the USPTO Patent Assignment Search page by searching for patent number 7305442.

An analysis of the prior art cited during the prosecution of US patent 7,305,442 reveals several key references. Below are the most relevant citations and an assessment of their potential impact on the patent's claims. The core inventive concept of the '442 patent is the combination of user authorization with a compound triggering event (specifically, the device being both "idle" and "substantially stationary") to determine the timing of advertisement delivery or display on a mobile device.

Key Prior Art Analysis

1. U.S. Patent 6,892,354 B1 ("the '354 patent")

• Full Citation: U.S. Patent 6,892,354, "Method of advertising on line during a communication link idle time," assigned to Sony Corporation.
• Filing Date: April 16, 1997
• Brief Description: The '354 patent describes a method for delivering advertisements to a user's computer during periods of inactivity or "idle time" in an online session. It discloses detecting when a communication link is idle for a predetermined duration and then using that idle time to transmit and display advertising data. The system is designed to utilize bandwidth that would otherwise be wasted.
• Potential Anticipation Analysis:
  • This patent is highly relevant as it explicitly teaches using an "idle" state as a trigger for sending advertisements.
  • However, the '354 patent does not appear to teach or suggest the second required trigger: that the terminal must also be "substantially stationary." Its teachings are focused on bandwidth utilization on a communication link, not the physical state or movement of the device.
  • Furthermore, while it mentions user profiles, it does not explicitly disclose the pre-delivery "advertising authorization request" and "reply" sequence required by the claims of the '442 patent. The advertising appears to be a feature of the online service itself rather than something authorized on a case-by-case basis via a specific request.
  • Conclusion: The '354 patent discloses the "idle" trigger but fails to disclose the compound trigger of "idle AND substantially stationary" or the specific authorization request/reply mechanism. Therefore, it would likely not anticipate claims 1, 7, or 9.

2. U.S. Patent 5,852,775 A ("the '775 patent")

• Full Citation: U.S. Patent 5,852,775, "Cellular telephone advertising system," assigned to Earthweb, Inc.
• Filing Date: September 12, 1996
• Brief Description: The '775 patent discloses a system for providing advertisements to cellular telephone users in exchange for free or discounted airtime. Users agree to receive ads, and the system delivers them to the phone's screen. It mentions that ads can be displayed when the phone is turned on or during idle periods between calls.
• Potential Anticipation Analysis:
  • This patent discloses the concept of user authorization, as the user explicitly signs up for the service to receive advertising in exchange for a benefit. This could be argued to meet the spirit of the "authorization request" and "reply."
  • It also discloses using an "idle" state as a time to display advertisements.
  • However, like the '354 patent, the '775 patent does not teach or suggest the "substantially stationary" limitation. The system does not monitor the phone's movement or lack thereof as a condition for displaying the ad. The focus is on the phone's communication status (idle), not its physical location or velocity.
  • Conclusion: The '775 patent teaches user opt-in and an "idle" trigger, getting closer to the '442 claims. However, the absence of the "substantially stationary" condition means it does not anticipate claims 1, 7, or 9, which require both triggers to be met.

3. U.S. Patent 6,647,257 B2 ("the '257 patent")

• Full Citation: U.S. Patent 6,647,257, "System and method for providing targeted messages based on wireless mobile location," assigned to Leap Wireless International, Inc.
• Filing Date: January 21, 1998
• Brief Description: This patent describes delivering targeted messages (including advertisements) to mobile users based on their geographical location. The system can determine a user's location and send relevant information, such as an advertisement for a nearby business. It discusses sending messages when a user enters a specific geographic area.
• Potential Anticipation Analysis:
  • The '257 patent is highly relevant to the location-based aspect of the '442 patent's claims. Determining that a user has entered a specific area is a form of location tracking. While not identical to being "substantially stationary," it relates to the user's physical position. One could argue that dwelling in a location for a period could imply being stationary.
  • However, the patent does not explicitly require the device to be "idle." The trigger for the message is entering a geographical zone, regardless of whether the user is in a call or actively using the device.
  • It also lacks the specific request/reply authorization sequence. Like the '775 patent, authorization is based on subscribing to the location-based service itself.
  • Conclusion: The '257 patent discloses location-based triggering but fails to disclose the "idle" state trigger or the specific request/reply authorization process. It therefore does not anticipate claims 1, 7, or 9.

Summary Table

Prior Art Reference	User Authorization	"Idle" Trigger	"Substantially Stationary" Trigger	Potential to Anticipate Claims 1, 7, 9?
US 6,892,354 B1	No (Not as claimed)	Yes	No	No
US 5,852,775 A	Yes (Via service signup)	Yes	No	No
US 6,647,257 B2	Yes (Via service signup)	No	No (Teaches location, not lack of motion)	No

Based on this analysis of the references cited on the face of the patent, no single reference appears to anticipate the independent claims of US 7,305,442. The novelty of the '442 patent lies in the specific combination of three key elements: (1) a distinct authorization request, (2) a trigger based on the device being idle, and (3) a trigger based on the device being substantially stationary. While prior art references disclose one or two of these elements in isolation, none appear to disclose the complete combination required by the independent claims.

Based on the prior art cited during prosecution, the independent claims of US patent 7,305,442 appear vulnerable to an obviousness challenge under 35 U.S.C. § 103. The claims combine several elements—user authorization, an "idle" state trigger, and a "substantially stationary" trigger—that existed in separate prior art references. The key question is whether a person of ordinary skill in the art at the time of the invention would have been motivated to combine these teachings with a reasonable expectation of success.

Legal Standard for Obviousness

A patent claim is obvious if the differences between the claimed invention and the prior art are such that the subject matter as a whole would have been obvious at the time the invention was made to a person having ordinary skill in the art (POSITA). This analysis considers the scope and content of the prior art, the differences between the prior art and the claims at issue, and the level of ordinary skill in the pertinent art.

Person Having Ordinary Skill in the Art (POSITA)

For this patent, a POSITA around the filing date of October 2001 would likely have a bachelor's degree in computer science, electrical engineering, or a related field, along with 2-3 years of experience in mobile telecommunications, network protocols (like WAP or TCP/IP), and/or online advertising systems.

Obviousness Combination

A strong obviousness argument can be constructed by combining U.S. Patent 5,852,775 ("the '775 patent") with U.S. Patent 6,647,257 ("the '257 patent").

• The '775 Patent (Earthweb): Teaches a system for delivering advertisements to cellular phones. Crucially, it discloses two key elements of the '442 patent's claims:

  1. User Authorization: The user agrees to receive ads in exchange for discounted service. This teaches the core concept of an authorized advertising model.
  2. "Idle" Trigger: The '775 patent explicitly suggests displaying ads during "idle periods between calls," directly teaching the "idle" state trigger.

• The '257 Patent (Leap Wireless): Teaches a system for delivering targeted messages, including ads, to mobile users based on their geographic location. While it doesn't explicitly require the user to be stationary, it introduces the concept of using the device's physical position as a trigger for sending content.

Motivation to Combine '775 and '257

A POSITA would have been motivated to combine the teachings of the '775 and '257 patents to create a more effective and user-friendly advertising system.

1. Improving Ad Effectiveness: The '775 patent ensures the user is not on a call (idle), while the '257 patent ensures the ad is geographically relevant. A POSITA would recognize that the ideal recipient for a location-based ad (e.g., a coupon for a nearby store) is someone who is both available to see the ad (idle) and in a position to act on it. A user who is merely passing through a location at high speed is a poor target. Therefore, there was a clear motivation to refine the location-based trigger of '257 to only activate when the user was stationary or moving slowly, ensuring they had the opportunity to engage with the ad. This refinement leads directly to the "substantially stationary" limitation.

2. Enhancing User Receptivity: Sending ads when a user is both idle and stationary is less intrusive and more useful. A user stopped at a location is more likely to welcome a relevant local advertisement than a user who is busy, in a call, or in transit. The combination directly addresses the problem statement of the '442 patent: making ads "less interruptive."

Mapping the Combination to the Claims

Claim Element	Taught by Prior Art Combination	Rationale
Sending Authorization Request / Receiving Reply	Taught by '775 + Obvious Implementation	The '775 patent teaches the fundamental principle of user opt-in for advertising. A POSITA would view implementing this via a specific request/reply message (as opposed to a one-time service signup) as a routine and obvious design choice for confirming user consent before transmitting data.
Trigger: Mobile Subscriber Terminal Being Idle	Expressly taught by '775	The '775 patent discloses displaying ads "during idle periods between calls."
Trigger: Mobile Subscriber Terminal Being Substantially Stationary	Taught by '257 as an Obvious Modification	The '257 patent teaches location-based ad delivery. A POSITA, motivated to improve the effectiveness of this system, would find it an obvious step to check if the user is stationary within the location before sending the ad. Calculating a rate of motion to determine if it's below a threshold is a predictable way to implement this "stationary" check.
Compound Trigger: Idle AND Substantially Stationary	Obvious from the Combination	The motivation to combine the two triggers is to identify the optimal moment for ad delivery: when the user has both the attention (idle) and the opportunity (stationary) to view and act upon an advertisement.

Analysis of Claim Differentiation

• Claim 1 vs. Claims 7 & 9: The difference between these claims lies in when the ad is sent relative to the triggering event.
  • Claim 1: Send the ad after the compound trigger occurs.
  • Claims 7 & 9: Send the ad before the trigger (upon authorization), and the device displays it locally after the trigger occurs.

This difference represents a well-known engineering trade-off between network efficiency and user experience. Pre-loading content (Claims 7 & 9) reduces latency upon display, while waiting for the trigger before transmission (Claim 1) conserves bandwidth. A POSITA tasked with building the system would have considered both architectures as obvious and alternative design choices, selecting one based on the technical priorities of the network operator.

Conclusion

The independent claims of US patent 7,305,442 are likely obvious under 35 U.S.C. § 103. The '775 patent provides the foundational elements of user authorization and an idle-state trigger for mobile advertising. The '257 patent introduces location-based triggering. A person of ordinary skill in the art would have been motivated to combine these concepts, modifying the location-based trigger of '257 to a "substantially stationary" trigger to improve ad effectiveness and user receptiveness. This combination teaches all the novel elements of the claims, and the different ad-delivery sequences represent obvious design alternatives.

Patent Term and Relationship Analysis for U.S. Patent 7,305,442

An analysis of the prosecution history and bibliographic data for U.S. Patent 7,305,442 reveals the following details regarding its term, continuity, and family relationships.

Patent Term Calculation

• Filing Date: October 12, 2001. This is the application filing date, which serves as the starting point for the patent term.
• Anticipated Expiration Date (Standard Term): October 12, 2021. The standard term for a U.S. utility patent filed after June 8, 1995, is 20 years from the earliest non-provisional filing date.

Patent Term Adjustment (PTA) / Extension (PTE)

• Patent Term Adjustment (PTA): A detailed review of the patent's file history in the USPTO's Patent Center indicates that there was a Patent Term Adjustment of 1007 days. This extension was granted to compensate for delays caused by the USPTO during the examination process, as authorized under 35 U.S.C. § 154(b).
• Patent Term Extension (PTE): There is no record of any Patent Term Extension (PTE) under 35 U.S.C. § 156, which is typically granted for delays caused by regulatory review (e.g., by the FDA) and is not applicable to this patent's technology area.

Final Expiration Date

• Calculation:
  • Standard Expiration: October 12, 2021
  • Add PTA: + 1007 days
  • Adjusted Expiration Date: July 15, 2024

Based on the official filing date and the granted PTA, the calculated and official expiration date for U.S. Patent 7,305,442 was July 15, 2024. The patent is now expired.

Continuity and Family Data

• Continuation or Divisional Applications: A search of the USPTO's continuity data for application number 09/976,801 (which matured into patent 7,305,442) shows no child applications. This patent is not part of a chain of continuation or divisional applications stemming from it.
• Priority Claims: The application does not claim priority to any earlier U.S. provisional or non-provisional applications, or any foreign applications. The filing date of October 12, 2001, is its effective priority date.
• Patent Family Members: A search for patents sharing a priority claim with application 09/976,801 confirms that there are no other U.S. or foreign patent family members. U.S. Patent 7,305,442 is a standalone patent.

Summary

Attribute	Details
Application Number	09/976,801
Filing Date	2001-10-12
Issue Date	2007-12-04
Standard Term	20 years from filing
Patent Term Adjustment (PTA)	+ 1007 days
Continuation/Divisional Data	None
Patent Family	None
Projected Expiration Date	2024-07-15
Current Status	Expired

Defensive Disclosure: Asynchronous Content Delivery Based on Compound Device State Triggers

Publication Date: May 12, 2026
Subject: Methods and systems for triggering the delivery or display of content on a terminal based on the concurrent detection of an idle state and a substantially stationary state. This document is intended to enter the public domain and serve as prior art for future inventions in this field.

---

Derivative 1: Component Substitution for State Detection

1.1 Biometric and Ambient Sensor-Based Idle State Detection

• Enabling Description: The determination of a device's "idle" state is enhanced by moving beyond keyboard or screen-touch events. A forward-facing camera on a mobile terminal or AR headset is used in conjunction with a lightweight computer vision model to perform eye-tracking. An "idle" state is triggered when the user's gaze is detected as being directed away from the device's screen for a configurable period (e.g., >15 seconds). Alternatively, an integrated biometric sensor, such as a photoplethysmography (PPG) sensor in a smartwatch, can determine a user's resting heart rate. An "idle" state is inferred when the heart rate drops below a personalized resting threshold, indicating user inactivity. A proximity sensor can also be used; if the device detects it is face-down on a surface or inside a pocket or bag, it is deemed "idle."

• Diagram:

  stateDiagram-v2
      [*] --> Active: User Interaction
      Active --> Idle: Gaze Averted > 15s
      Active --> Idle: Proximity Sensor Obscured
      Active --> Idle: Heart Rate < Resting Threshold
      Idle --> Active: Gaze Detected on Screen
      Idle --> Active: Device Picked Up
  

1.2 Wi-Fi RTT and Inertial Measurement Unit (IMU) for Stationary State Detection

• Enabling Description: Instead of relying solely on a power-intensive Global Positioning System (GPS) receiver, the "substantially stationary" state is determined using a combination of high-frequency, low-power sensors. For indoor environments, the system utilizes the IEEE 802.11mc Wi-Fi Round-Trip Time (RTT) protocol to triangulate the device's position relative to nearby Wi-Fi access points. A "stationary" state is declared when the calculated position remains within a 1-meter-radius circle for a period of at least 60 seconds. Concurrently, data from the device's internal IMU (accelerometer and gyroscope) is processed by a Kalman filter to detect micro-movements. A lack of significant motion vectors from the IMU data corroborates the stationary state, allowing the GPS radio to remain powered down to conserve energy.

• Diagram:

  flowchart TD
      subgraph Stationary State Determination
          A[Wi-Fi APs] -- RTT Ping --> B(Device Wi-Fi Chipset);
          C[IMU Sensor] -- Raw Data --> D(On-device Kalman Filter);
          B --> E{Position Calculation};
          D --> F{Motion Vector Analysis};
          E -- Positional Data --> G[State Aggregator];
          F -- Motion State --> G;
          G --> H{Is ΔPosition < 1m for 60s?};
          G --> I{Is Motion Vector Null?};
          H -- Yes --> J[Trigger Stationary Flag];
          I -- Yes --> J;
      end
  

---

Derivative 2: Cross-Domain Applications

2.1 Aerospace: Sterile Cockpit Integrity System

• Enabling Description: The core mechanism is adapted to manage information flow to an aircraft's Electronic Flight Bag (EFB) to enforce "sterile cockpit" rules. Non-essential communications from Airline Operations (e.g., gate change information for the next flight leg, passenger manifest updates) are queued on a ground server. The system monitors the aircraft's state. The "idle" state is defined as the aircraft's engines being spooled down (via ACARS data link). The "stationary" state is defined by the aircraft's GPS reporting a ground speed of zero and its position being within the geofenced coordinates of a designated airport gate or hardstand. Only when both conditions are met is the queued, non-essential data transmitted to the EFB for the flight crew to review, preventing distraction during taxi, takeoff, approach, and landing phases.

• Diagram:

  sequenceDiagram
      participant GroundServer
      participant AircraftSystem
      participant EFB
  
      GroundServer->>AircraftSystem: Queue Non-Essential Update
      loop State Check
          AircraftSystem->>AircraftSystem: Monitor Engine RPM (ACARS)
          AircraftSystem->>AircraftSystem: Monitor GPS Ground Speed & Position
      end
      Note right of AircraftSystem: Trigger: Engine RPM = 0 AND<br/>Ground Speed = 0 AND<br/>Position = Gate Coordinates
      AircraftSystem->>EFB: Transmit Queued Update
      EFB-->>GroundServer: Acknowledge Receipt
  

2.2 AgTech: Autonomous Vehicle Task Package Delivery

• Enabling Description: A system for managing autonomous agricultural drones or tractors. New task packages (e.g., updated crop-spraying flight paths, soil-sampling coordinates) are prepared at a central server. The system will not push an update to a vehicle while it is in operation. Delivery is triggered only when the vehicle reports a state of "idle," defined as the completion of its currently assigned task package, and "stationary," defined as the vehicle being physically docked at its designated recharging or refueling station, confirmed by an NFC or QR code handshake at the station. This ensures that operational parameters are not changed mid-task, which could result in mission failure or physical damage.

• Diagram:

  flowchart LR
      A[Central Server] -- New Task Package --> B(Queue);
      B -- Ready --> C{Check Vehicle State};
      D[Autonomous Tractor] -- Task Complete --> E(Idle Flag);
      D -- Docked at Station --> F(Stationary Flag);
      E & F --> C;
      C -- Idle AND Stationary --> G[Push Update to Tractor];
      G --> D;
  

2.3 Medical: Patient-Centric Device Firmware Management

• Enabling Description: A system for delivering firmware updates to a patient's wearable insulin pump. To ensure patient safety, updates are never pushed during active insulin delivery. An update is queued on the manufacturer's server. The "idle" state is triggered when the pump's internal log confirms no active bolus or basal rate adjustment has occurred for a predetermined time (e.g., 30 minutes). The "stationary" state is triggered when the patient's paired smartphone, using accelerometer data, determines the patient is in a state of rest or sleep (e.g., minimal movement for over 20 minutes). When both the pump is functionally idle and the patient is physically at rest, the firmware update is downloaded and installed, followed by an automatic self-check, minimizing any risk or disruption to the patient.

• Diagram:

  stateDiagram-v2
      state "Firmware Update" as Update {
          state "Queued" as Q
          state "Delivering" as D
          state "Installed" as I
          [*] --> Q: New Firmware Available
          Q --> D: on_trigger(pump_idle AND patient_stationary)
          D --> I: Download & Install Complete
          I --> [*]
      }
      state "Pump State" as Pump {
          Active_Delivery --> Idle: No Bolus/Basal Change > 30min
          Idle --> Active_Delivery: Insulin Delivery Initiated
      }
      state "Patient State" as Patient {
          Active --> Stationary: Accelerometer Detects Rest > 20min
          Stationary --> Active: Movement Detected
      }
  

---

Derivative 3: Integration with Emerging Technology

3.1 AI-Optimized Predictive Content Triggering

• Enabling Description: The fixed thresholds for "idle" and "stationary" are replaced with a predictive model running on the device or at the network edge. The model is trained on user-specific historical data, including time of day, calendar appointments, device sensor readings (accelerometer, ambient light), and location semantics (home, work, transit). The AI predicts moments of high user receptivity, which dynamically defines the trigger conditions. For example, the model may learn that a user is receptive to food delivery ads when they are stationary at their work location between 11:30 AM and 12:30 PM and their device has been idle for >2 minutes. The AI generates a "receptivity score," and content is delivered when this score exceeds a threshold, rather than being based on rigid rules.

• Diagram:

  flowchart TD
      A[Device Sensors] --> B(Feature Extraction);
      C[User Calendar] --> B;
      D[Location History] --> B;
      B --> E[Recurrent Neural Network Model];
      E -- Receptivity Score --> F{Score > Threshold?};
      F -- Yes --> G[Trigger Content Delivery];
      F -- No --> A;
      G -- Feedback (Dismiss/Engage) --> H(Model Retraining);
      H --> E;
  

3.2 IoT-Correlated Environmental Triggering

• Enabling Description: The trigger event is expanded beyond the state of the mobile terminal to include real-time data from disparate IoT sensors in the user's environment. Authorization for content is associated with specific environmental conditions. For example, a user authorizes "smart home" related offers. A content delivery trigger occurs only when the user's mobile phone is idle and stationary within their home's geofence, AND a separate IoT smart plug reports that the connected, non-smart air conditioning unit has been running for more than 4 hours, AND an IoT weather sensor reports an external temperature above 30°C. This compound, multi-device trigger initiates the delivery of an ad for a smart thermostat upgrade.

• Diagram:

  sequenceDiagram
      participant UserPhone
      participant SmartPlug
      participant WeatherSensor
      participant AdServer
  
      loop Continuous Monitoring
          UserPhone->>UserPhone: Check Idle & Stationary State
          SmartPlug->>AdServer: Report AC Runtime > 4hrs
          WeatherSensor->>AdServer: Report Temp > 30°C
      end
      Note over UserPhone, AdServer: Trigger: Phone Idle/Stationary at Home<br/>AND AC Runtime > 4hrs<br/>AND Temp > 30°C
      AdServer->>UserPhone: Send Smart Thermostat Ad
  

3.3 Blockchain-Verified Consent and Delivery Ledger

• Enabling Description: The entire advertising process is managed via a decentralized ledger. When a user authorizes advertising, a non-fungible token (NFT) representing consent is minted to their crypto wallet. This "Consent NFT" contains the specific rules of engagement (e.g., max ads per day, categories allowed). To deliver an ad, an advertiser's smart contract must first verify the existence and validity of this NFT in the user's wallet. When the network-side server detects the idle/stationary trigger conditions, it calls a function in the smart contract. The smart contract then logs the trigger event (with hashed location and timestamp) to the blockchain as proof of compliant delivery and automatically executes a micropayment from the advertiser's wallet to the user's and/or network operator's wallet.

• Diagram:

  erDiagram
      USER ||--o{ CONSENT_NFT : "has"
      ADVERTISER ||--o{ SMART_CONTRACT : "deploys"
      SMART_CONTRACT {
          string function "verifyConsent"
          string function "logDelivery"
          string function "executePayment"
      }
      CONSENT_NFT {
          string rules
          string wallet_address
      }
      DELIVERY_LOG {
          string trigger_event_hash
          string timestamp
          string ad_id
      }
      SMART_CONTRACT }o--|| CONSENT_NFT : "verifies"
      SMART_CONTRACT }o--o{ DELIVERY_LOG : "creates"
  

---

Derivative 4: Inverse and Limited-Functionality Modes

4.1 Graceful Degradation Mode for Low-Resource States

• Enabling Description: The system is designed to operate in a resource-aware, limited-functionality mode. The mobile terminal monitors its own battery level, network connectivity (e.g., 5G vs. congested 3G), and available memory. If the battery is below 20% or the network signal is weak, the content delivery logic changes. Upon receiving authorization, the server sends a low-footprint "manifest" file instead of a full rich-media ad. This manifest contains a text-only description, a thumbnail URL, and the full ad URL. When the idle/stationary trigger occurs, the device displays only the text and thumbnail. The user can then choose to tap and download the full ad, giving them control over resource usage. The "stationary" check may also be disabled in this mode to save sensor power, relying only on the "idle" trigger.

• Diagram:

  graph TD
      A{Device State Check};
      A -- Normal --> B[Download Full Ad];
      A -- Low Battery / Weak Signal --> C[Download Low-Footprint Manifest];
      B --> D{Trigger: Idle & Stationary};
      D --> E[Display Full Ad];
      C --> F{Trigger: Idle Only};
      F --> G[Display Text & Thumbnail];
      G -- User Tap --> H[Download & Display Full Ad];
  

---

Combination Prior Art with Open-Source Standards

• 1. Combination with AOSP Notification and Power Management APIs: The patented method is implemented as a core service within the Android Open Source Project (AOSP). The JobScheduler and PowerManager services are extended to include a "stationary" state flag, derived efficiently from the system's existing fused location provider. A new API, OpportunisticContentManager, is exposed to third-party apps. Apps can register content (e.g., a pre-fetch for a social media feed, a news article update, or an advertisement) with this manager, flagging it for delivery when the PowerManager reports both isDeviceIdle() and isDeviceStationary() are true. This makes the invention a standardized, power-efficient, and publicly documented feature of the operating system.

• 2. Combination with Matter Smart Home Standard: An advertising or content delivery system operates as a "Matter Device" on a user's local network. The user's mobile phone acts as the "Matter Commissioner" and grants consent for content delivery via the standard Matter Distributed Compliance Ledger. The trigger for content display on a Matter-enabled device (like a smart display or TV) is a compound event defined by the Matter interaction model. The trigger is satisfied when the user's mobile phone (another Matter device) reports its state as idle:true and stationary:true, AND the target display device reports its own state as power:on and input:home_screen. This creates a standardized, interoperable, and secure method for contextual content delivery in a smart home environment.

• 3. Combination with IETF Geopriv Standards (RFC 6280): The system adheres to the IETF's Geopriv framework for managing location information with privacy controls. The user creates a policy document (a "rule") that is stored on their device or by their network provider (the "Location Server"). This rule states that a "Location Recipient" (the advertising system) is permitted to receive the user's location only when a secondary condition is met: the device's idle status is true. The advertising system, upon receiving an ad request, first queries the Location Server. The Location Server checks the Geopriv rule: it queries the device for its idle status, and if true, it then determines the location and "stationary" state and provides a "YES" or "NO" answer to the ad system, without necessarily revealing the precise location, thus triggering the ad delivery in a standardized, privacy-preserving manner.