Patent 10516775

Obviousness

Combinations of prior art that suggest the claimed invention would have been obvious under 35 U.S.C. § 103.

Active provider: Google · gemini-2.5-flash

Obviousness

Combinations of prior art that suggest the claimed invention would have been obvious under 35 U.S.C. § 103.

✓ Generated

The following analysis addresses the obviousness of US patent 10516775 under 35 U.S.C. § 103, based on the provided patent text and its "Prior art" section. The current date is April 26, 2026.

Person Having Ordinary Skill in the Art (PHOSITA)

A person having ordinary skill in the art (PHOSITA) in the context of US10516775 would be a software engineer or developer with expertise in mobile application development, human-computer interaction (HCI), and communication systems. This individual would be familiar with:

  • Developing user interfaces for mobile devices.
  • Implementing text-to-speech (TTS) and speech recognition technologies.
  • Integrating with mobile operating system APIs for notifications, messaging (SMS, email, messenger apps), and phone calls.
  • Designing user experiences for "limited distraction" environments, such as driving or exercising.
  • Common mobile interaction paradigms, including gestures (taps, swipes).

Prior Art References

The patent US10516775 itself identifies and discusses the limitations of the following prior art references in its "BACKGROUND SECTION OF THE INVENTION":

  1. US 2013/0275899: This reference discloses "a limited-distraction user interface that includes providing for display fewer selectable user interface objects than are displayed in a non-limited user interface for the respective application, and in accordance With a determination that the device is not being operated in a limited distraction context, provides a non-limited user interface for the respective application". However, US10516775 notes that it "relies on substantial input from the user even in the limited-distraction context, making it difficult for a user to use a mobile phone in such context".
  2. U.S. Pat. Nos. 8,364,183, 8,526,973, and 8,359,014 (referred to as "Busykey patents"): These patents disclose "A cell phone which has been modified by the addition of software which responds to the press of one or more Busykeys by automatically sending a pre-typed text message to the sender of the latest text message just received or automatically answering an incoming call immediately upon pressing the Busy key and playing a pre-recorded audio message". US10516775 criticizes these patents for not allowing responses beyond pre-typed messages and still requiring "substantial input from the user since the user has to choose and press on a Busykey button".

Additionally, general knowledge in the art at the priority date (November 21, 2014) includes:

  • Text-to-Speech (TTS) technology: Widespread availability of TTS APIs in mobile operating systems (e.g., Android's TextToSpeech API, iOS's AVSpeechSynthesizer) for converting text into spoken audio.
  • Context awareness: Mobile devices could detect location, motion, and connect to vehicle systems (e.g., Bluetooth for hands-free calling), allowing for rudimentary context determination.
  • Gesture-based interaction: Tapping and swiping on touchscreens were common and intuitive input methods.
  • Standard message parsing: Email and text message clients routinely parse messages into sender, subject (for email), and body.

Obviousness Analysis

Let's consider the broadest method claim presented in the "SUMMARY SECTION OF THE INVENTION" of US10516775, which encompasses the core inventive concept:

"A computer implemented method to be carried out with a processor, a memory, and a touch screen, comprising:
a) determining without any input by a user that a text message, an email, or a message from a messenger application, has arrived while the user is engaged in an activity;
b) informing the user without any input by the user that the text message, the email, or the message from the messenger application has arrived from a sender; and
c) proceeding with a step selected from the group consisting of (i) and (ii):
i) allowing the user time to take an affirmative action to stop reading aloud to the user a body of the text message, the email, or the message from the messenger application; and in accordance with not receiving an input corresponding to the affirmative action from the user, reading aloud the body of the text message, the email, or the message from the messenger application to the user;
ii) allowing the user time to take an affirmative action to command reading a body of the text message, the email, or the message from the messenger application aloud to the user; and in accordance with receiving an input corresponding to the affirmative action from the user, reading aloud the body of the text message, the email, or the message from the messenger application to the user."

Combination of Prior Art for Obviousness:
A combination of US 2013/0275899, the Busykey patents (U.S. Pat. Nos. 8,364,183, 8,526,973, and 8,359,014), and general knowledge of TTS technology would render the above claim obvious to a PHOSITA.

Motivation for Combination:

A PHOSITA would be motivated to combine these references to overcome the explicit shortcomings of the prior art while improving user safety and convenience in hands-free environments.

  • Problem Identification: US 2013/0275899 highlights the problem of "substantial input from the user even in the limited-distraction context". The Busykey patents, while offering some automation, still required users to "choose and press on a Busykey button", implying an undesirable level of manual and visual interaction.
  • Solving the Problem: The motivation would be to create a truly hands-free messaging experience in limited-distraction environments (e.g., driving), specifically by minimizing or eliminating direct visual and manual interaction, and maximizing audio interaction.

Analysis of Claim Elements based on the Combination:

  1. "a) determining without any input by a user that a text message, an email, or a message from a messenger application, has arrived while the user is engaged in an activity;"

    • Determining message arrival without user input: This is standard functionality in any modern mobile messaging application. Notifications for new messages (SMS, email, messenger) are inherently automatic.
    • "while the user is engaged in an activity": US 2013/0275899 explicitly teaches determining a "limited distraction context". A PHOSITA would readily recognize that activities like driving, exercising, or working constitute such contexts. Detecting these activities (e.g., via GPS for driving, accelerometer for exercising, or user selection of a "mode" as in US10516775 itself) was well-known in the art. The problem identified in US 2013/0275899 directly motivates tailoring message delivery to these contexts.
  2. "b) informing the user without any input by the user that the text message, the email, or the message from the messenger application has arrived from a sender;"

    • The Busykey patents demonstrate the concept of automatically playing a "pre-recorded audio message" upon an incoming communication event (e.g., a call). This establishes the idea of audio notification without active user input beyond the initial communication event.
    • Prior to 2014, caller ID announcement for incoming phone calls was a common feature. A PHOSITA, aiming to reduce distraction in messaging, would find it obvious to apply the widely available Text-to-Speech (TTS) technology to dynamically read aloud the sender's identity (name, email address, etc.) for text messages, emails, or messenger messages, rather than just a generic alert or pre-recorded message. This improves upon the Busykey patents by providing relevant, dynamic information without requiring visual lookup.
  3. "c) proceeding with a step selected from the group consisting of (i) and (ii):"

    • "i) allowing the user time to take an affirmative action to stop reading aloud to the user a body of the text message, the email, or the message from the messenger application; and in accordance with not receiving an input corresponding to the affirmative action from the user, reading aloud the body of the text message, the email, or the message from the messenger application to the user;"
      • Combining the audio output of the Busykey patents with general TTS technology makes it technically feasible and obvious to read the body of a message aloud.
      • The default "read aloud" (opt-out) mechanism, where the message body is read unless the user takes affirmative action to stop it, is an obvious design choice for a PHOSITA specifically trying to solve the "substantial input" problem of US 2013/0275899. In limited-distraction contexts, users often want to hear the full message. Providing an automatic read-aloud with a brief pause for an easy-to-perform "stop" action (e.g., a single tap or swipe, as supported by general knowledge of gesture-based interaction) significantly reduces the user input required compared to an explicit "read" command. This improves efficiency and reduces cognitive load in such environments.
    • "ii) allowing the user time to take an affirmative action to command reading a body of the text message, the email, or the message from the messenger application aloud to the user; and in accordance with receiving an input corresponding to the affirmative action from the user, reading aloud the body of the text message, the email, or the message from the messenger application to the user."
      • This "opt-in" approach is even more directly rendered obvious by the Busykey patents, which describe a user "press[ing]... one or more Busykeys" to trigger an automated audio message. A PHOSITA would simply replace the "pre-recorded audio message" with a dynamically generated TTS reading of the actual message body, utilizing known TTS capabilities. The "affirmative action" would be a low-distraction input (e.g., a tap or swipe, which were common touchscreen gestures) replacing the physical button press, a natural evolution for mobile interfaces.

Further Obvious Elements within US10516775:

  • Single Queue for Multiple Message Types: The practice of aggregating notifications from various sources (email, SMS, messenger apps) into a unified queue for chronological processing is a fundamental data management technique for a PHOSITA designing a comprehensive messaging application.
  • Suppression of Visual Display: If looking at the screen is hazardous (e.g., in Drive Mode), the idea of not displaying any portion of the message is an obvious safety-driven extension of US 2013/0275899's "limited-distraction user interface" (which provides "fewer selectable user interface objects"). Car infotainment systems prior to 2014 often limited display functionality when the vehicle was in motion.
  • Simplified Gesture Input: Limiting user input to simple taps or swipes without requiring visual attention is an obvious improvement over physical button presses (as in the Busykey patents) when aiming for hands-free, low-distraction interaction in a touchscreen-dominated mobile world.
  • Prompting to Call Sender: After reading a message, vocally asking the user if they want to call the sender is a logical next step in a hands-free communication workflow, drawing on common voice assistant functionalities (e.g., Siri, Google Now, which existed prior to 2014).
  • Automatic "User Busy" Response: The Busykey patents explicitly disclose "automatically sending a pre-typed text message to the sender". Using this capability to send an "I'm busy" message in a limited-distraction mode (like driving) is a direct and obvious application of this prior art.

Conclusion:

The core features of US10516775, including the automatic determination and announcement of messages, followed by either opt-out or opt-in reading of message bodies in a context-aware manner with minimal user input, would have been obvious to a PHOSITA. This conclusion is based on the motivation to solve the identified limitations in prior art (US 2013/0275899's "substantial input" and the Busykey patents' reliance on physical buttons and pre-recorded messages), by applying known technologies like TTS and common UI/UX design patterns for hands-free interaction, especially in safety-critical contexts like driving.

Generated 5/23/2026, 12:49:31 AM