Obviousness

An analysis of the obviousness of US Patent 11,653,183 ("the '183 patent") under 35 U.S.C. § 103 requires examining whether the differences between the claimed invention and the prior art are such that the claimed invention as a whole would have been obvious at the time the invention was made to a person having ordinary skill in the art (PHOSITA). The priority date of the '183 patent is July 24, 2007.

The core concept of the '183 patent is a messaging system that intelligently selects between a packet-switched message service (PSMS) and a traditional SMS bearer. This selection is based on querying a server to determine a recipient's status as a PSMS subscriber and, crucially, whether a threshold of undelivered messages for that recipient has been exceeded. The system is designed to fall back to the more reliable, albeit limited, SMS bearer if the preferred PSMS delivery fails or is likely to fail.

A PHOSITA in July 2007 would have been familiar with mobile messaging technologies including SMS, MMS, and the burgeoning field of mobile Instant Messaging (IM) over packet-switched data networks like GPRS and early 3G. They would also understand concepts of presence (knowing a user's online/offline status) and store-and-forward messaging.

Based on these principles, the claims of the '183 patent would have been obvious in view of a combination of prior art references.

Prior Art References

• US Patent 7,822,437 ("Potter '437"): Filed August 4, 2005. Potter discloses a unified messaging system where a sender's device can send a message using a preferred, cheaper bearer (like an IP network) if the recipient is available on that network. It explicitly teaches querying a "presence and routing server" to determine the recipient's status. If the recipient is not online or available via the IP network, the system automatically "causes the message to be sent as an SMS message." This establishes the fundamental concept of checking a recipient's status with a server and falling back to SMS if the preferred data network is not viable.

• US Patent 7,933,590 ("Mäenpää '590"): Filed April 22, 2002. Mäenpää describes a messaging system that attempts to deliver a message via a packet-based service (like WAP push or MMS) first. It details a "store-and-forward" function where if the recipient is not reachable, the message is stored. Mäenpää teaches that after a "predetermined number of delivery attempts... have been made" or a "predetermined time limit... has been exceeded," the system can convert the message to a different format, such as an SMS, and send it to the user. This reference introduces the concept of a threshold (number of attempts or time) triggering a fallback to SMS after initial delivery failures.

• US Patent Application Publication 2006/0292998 ("Forstall '998"): Filed June 23, 2005. Forstall, related to Apple's development of the iPhone's messaging application, discloses a unified messaging user interface. It describes a "unified message screen" or "chat-style view" where messages from different services (e.g., SMS, IM, MMS) are "displayed in a single, scrollable screen." This teaches the concept of displaying messages sent via different bearers in the same messaging client, as required by the '183 patent's claims.

Obviousness Analysis

Analysis of Independent Claims 1 and 7

Independent claims 1 and 7 describe a system and method for checking if a recipient is a PSMS subscriber and, if so, sending a message via PSMS/WLAN only if an "undelivered message threshold" has not been exceeded. Otherwise, the system falls back to SMS.

A PHOSITA would have found it obvious to combine the teachings of Potter '437 and Mäenpää '590.

1. Motivation to Combine: A PHOSITA, starting with the system in Potter '437, would recognize its primary limitation: it only accounts for the recipient's current online/offline status. It does not handle the scenario where a user is a subscriber but is temporarily offline for an extended period. Messages sent to such a user would simply fail or be queued indefinitely on the server without notifying the sender of a persistent delivery problem. Mäenpää '590 directly addresses this issue by introducing a mechanism for handling undeliverable messages based on a threshold (time or number of attempts). A PHOSITA would be motivated to integrate Mäenpää's threshold-based fallback logic into Potter's presence-based system to create a more robust and reliable messaging service. This combination would provide a better user experience by ensuring messages are eventually delivered via SMS if the preferred data channel remains unavailable for too long, a predictable and desirable outcome.

2. Mapping to Claim Elements:

   • Sending via SMS or PSMS (Claim 1): Taught by Potter '437, which uses an IP network (analogous to the claimed PSMS) and an SMS bearer.
   • Querying a Server for Subscriber Status (Claim 1): Taught by Potter '437's "presence and routing server," which checks if a user is available on the IP network. This is analogous to checking for a PSMS subscriber with an active status.
   • Fallback to SMS if Not a Subscriber (Claim 1): Explicitly taught by Potter '437.
   • Undelivered Message Threshold (Claim 1): The novel aspect of this claim is taught by Mäenpää '590. Mäenpää discloses that after a "predetermined number of delivery attempts" or a "predetermined time limit" (i.e., a threshold) is exceeded for a queued message, the system falls back to SMS. It would have been a simple and obvious modification for the server in Potter '437 to maintain a count of undelivered messages for offline users (as taught by Mäenpää's store-and-forward function) and include this count in its response to the sender's query. If the count exceeds a set maximum, the server would instruct the sender to use SMS, precisely as claimed.
   • Same Messaging Client (Claim 1): While not the focus of Potter or Mäenpää, the concept of a unified interface was well-known. A PHOSITA implementing this combined system would naturally turn to a solution like that described in Forstall '998 to present the messages to the user in a coherent, chat-style view, regardless of the underlying delivery bearer.

Analysis of Independent Claims 14 and 20

Independent claims 14 and 20 describe a system and method where a first message is sent via PSMS/WLAN, but if that message goes undelivered, a subsequent message is sent via SMS. This is a direct application of a failover mechanism.

This functionality would have been obvious from Mäenpää '590 alone, or in combination with Potter '437.

1. Motivation: The motivation is inherent in creating a reliable messaging system. When a sender sends a message, they expect it to be delivered. If the preferred, feature-rich packet-switched delivery method fails, it is a matter of common sense and sound engineering to fall back to a more universally available method like SMS for subsequent communications until the primary channel is restored.

2. Mapping to Claim Elements:

   • Sending a first message via PSMS (Claims 14, 20): This is the preferred "packet-based service" in Mäenpää '590.
   • First message is undelivered (Claims 14, 20): Mäenpää '590 explicitly describes queuing messages when the recipient is not reachable and attempting redelivery. This state is equivalent to the message being "undelivered."
   • Server sends a second, different response (Claim 14): In Mäenpää's system, the server is aware that the first message failed. It would be an obvious design choice for the server, upon receiving a query for a second message to the same recipient, to return a response indicating the prior failure and recommending an alternative bearer. This change in the server's state (from "recipient is available" to "recipient has undelivered messages") would naturally result in a "different response."
   • Sending a second message via SMS bearer (Claims 14, 20): Mäenpää '590 explicitly teaches converting the message to SMS after the delivery threshold is met. Applying this same logic to a new message being sent to that same unreachable recipient is a simple, obvious extension of the same principle: if the data channel is known to be failing for this user, use SMS instead.

Conclusion

The claims of US Patent 11,653,183 represent an obvious combination of known elements in the art prior to July 2007. The fundamental concept of checking recipient presence and falling back to SMS was established by references like Potter '437. The specific innovation of using an undelivered message count as a threshold to trigger this fallback was taught by Mäenpää '590's disclosure of using a number of failed attempts or a time limit. Combining these teachings to create a more robust messaging system would have been a predictable and logical step for a person having ordinary skill in the art at the time. Finally, presenting these messages in a unified interface was also a known technique, as shown in Forstall '998. Therefore, the claims of the '183 patent are invalid as obvious under 35 U.S.C. § 103.