Browse Prior Art Database

Technique for message selector suggestions to a Message Consumer based on qualifying message properties on a message

IP.com Disclosure Number: IPCOM000233145D
Publication Date: 2013-Nov-26
Document File: 7 page(s) / 85K

Publishing Venue

The IP.com Prior Art Database

Abstract

In today’s message environment, the message publisher creates a message and adds set of message properties which can define the content, need and intended users of the message and its data. These message properties on the message play a vital role when it comes to the message filtering by the message subscribers. A lot of times, subscriber would want to know what could be the best matching selection criterion that helps to get correct message for its need. At present, in messaging world, there’s no way where a message consumer gets suggestions on selection criteria improvement. Its always Subscribers interest to form the message selection criteria, which can be understood with the fact of de-coupled system between the Publisher and Subscribers. But Message engine can also extend its role to provide suggestions on message selection criteria to help subscribers get right messages.

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

Page 01 of 7

Technique for message selector suggestions to a Message Consumer based on qualifying message properties on a message

In today's message environment, the message publisher creates a message and adds set of message properties which can define the content, need and intended users of the message and its data. These message properties on the message play a vital role when it comes to the message filtering by the message subscribers. A lot of times, subscriber would want to know what could be the best matching selection criterion that helps to get correct message for its need. At present, in messaging world, there's no way where a message consumer gets suggestions on selection criteria improvement. Its always Subscribers interest to form the message selection criteria, which can be understood with the fact of de-coupled system between the Publisher and Subscribers. But Message engine can also extend its role to provide suggestions on message selection criteria to help subscribers get right messages.

Example1:

Publisher creates two messages with the weather information as follows

MsgB.City = Bangalore

MsgB.Country = India

MsgB.Temperature = 25C

MsgB.Humidity = 50Percentage

MsgB.Rainfall = MAYBE

MsgD.City = Delhi

MsgD.Country = India

MsgD.Temperature = 50C

MsgD.Humidity = 80Percentage

MsgD.Rainfall = MAYBE

When both messages are published onto a topic "World Weather Agency"

Assuming, we have a subscriber, who's message selection criteria is "Country=India", with the current messaging infrastructure, it would get both the messages. But, what if subscriber wants only the messages that belong to Bangalore weather? In which case the correct message selector criteria could have been "Country=India & City=Bangalore". At present, there's no one who makes this suggestion to the Subscriber and this is left to the interest and knowledge of subscriber on the topic.

Another aspect in this is, when a message publisher is adding message properties, it can guess the intended users and what the purpose that message could give. With this knowledge, Message publisher can classify the properties on the message as best suited for selection. So that, Messaging Engine can take this input from Message Publisher and provide this as a suggestion on best selection criteria to the Message Subscribers. At present, the message publisher adds message properties based on the purpose that message could provide but there's no guarantee that the message has found its right way to the

1


Page 02 of 7

right subscriber.

Following are some of the techniques we have found on the prior-art search

1. Delivering Messages in an Enterprise Messaging System using Message Selector Hierarchy

This mainly speaks on a tree based selector hierarchy for grouping the similar consumers for the message delivery. Word "Similar Consumers" must be understood as Consumers that have similar type of selectors. For example

ConsumerA = "ITEM = SPORTS";

ConsumerB = "ITEM = SPORTS & CATEGORY=FOOTBALL"

...