Browse Prior Art Database

System and method for monitoring and perform QoS control of mobile notification messages

IP.com Disclosure Number: IPCOM000234176D
Publication Date: 2014-Jan-16
Document File: 4 page(s) / 217K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed is a system and method for monitoring and performing Quality of Service (QoS) control of mobile notification messages. When a push notification is delivered from a notification service provider to a mobile client, the notification is first sent to a notification proxy server which acts as a delegate for the original mobile client. This notification proxy server then passes the notification to the mobile client via a lightweight protocol. In this way, notification messages can be monitored and QoS can be controlled in the notification proxy server.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 35% of the total text.

Page 01 of 4

System and method for monitoring and perform QoS control of mobile notification messages


A. BACKGROUND OF INVENTION: Figure 1 is the architecture of today's push notification service. It shows that when a notification need to be pushed to an end-user client application, application service provider will first send the notification to the corresponding push notification service provider, i.e., Apple Push Notification service (APNs) [1] or Google Cloud Messaging (GCM) [2], depending on what platform the mobile device uses. Then the push notification service provider takes the responsibility of pushing the notification to the end-user mobile device.

Figure 1. traditional push notification service architecture

There are two drawbacks within this traditional architecture:

    1. More battery power consumption on end-users' mobile devices:
Most of the push notification service providers, including Apple, Google, and Microsoft, require each of their mobile devices to establish a persistent connection with its corresponding notification server. This persistent connection consumes extra battery power of the mobile device.

    2. Low level of Quality of Service: Most of the current notification service providers do not guarantee on 1) the order of generating notifications at the application service providers being consistent with the order of receiving notifications at the end-user mobile device, and 2) notifications are not lost due to inactivity of mobile devices (i.e., a mobile device does not retrieve notifications and those notifications are expired in the end).

    The key idea of this invention is to introduce a notification proxy, which is quite similar to existing reverse proxies but focuses on existing message notification services. When a mobile device enters the realm controlled by the notification proxy, it delegates the notification proxy to receive notifications (from various applications) on behalf of itself. The notification proxy creates a hybrid ID based on the mobile device ID, and uses this hybrid ID to register at the notification service. As a result, subsequent notifications are delivered to the notification proxy.

This has many benefits:

    1. Notification Proxy can examine the notification message and perform message filtering/validation/manipulation based on predefined rules.

    2. Notification Proxy can reorder the messages based on message priority. It also prevents notification lost due to inactivity of mobile device. This serves higher level of QoS.

    3. Battery power consumption of mobile devices are saved. Each mobile device no longer needs to setup a persistent connection with its notification service provider. Notification Proxy can use a lightweight communication protocol to deliver the messages to the mobile device.

    Finally, when the mobile device leaves the realm, the notification agent re-initiates the registration process, so that subsequent notifications are delivered to the mobile device directly.

Key claim points of t...