Communication system

• US 20080183828A1
• Filed: 01/23/2008
• Published: 07/31/2008
• Est. Priority Date: 01/30/2007
• Status: Abandoned Application

• Current Assignee: Markport Limited (Mavenir Group Holdings Ltd.)
• Original Assignee: Markport Limited (Mavenir Group Holdings Ltd.)
• Inventors: Sehgal, Amit, Rijhwani, Mukesh, Sharma, Sunil
• Application Number:
  US12/010,252
• Publication Number:
  US 20080183828A1
• Time in Patent Office: Days
• US Class Current: 709/206
• CPC Class Codes: H04L 12/1822 Conducting the conference, e.g. admission, detection, selection or grouping of participants, correlating users to one or more conference sessions, prioritising transmission
• CPC Class Codes: H04L 12/1845 broadcast or multicast in a specific location, e.g. geocast protocols for adapting network applications to user terminal location H04L67/52; services specially adapted for wireless communication networks making use of the location of users or terminals H04W4/02
• CPC Class Codes: H04L 12/189 in combination with wireless systems selective distribution or broadcast in wireless communication networks H04W4/06
• CPC Class Codes: H04L 51/04 Real-time or near real-time messaging, e.g. instant messaging [IM]
• CPC Class Codes: H04L 51/222 using geographical location information, e.g. messages transmitted or received in proximity of a certain spot or area
• CPC Class Codes: H04L 51/58 Message adaptation for wireless communication
• CPC Class Codes: H04L 67/52 specially adapted for the location of the user terminal
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04L 67/564 Enhancement of application control based on intercepted application data
• CPC Class Codes: H04W 4/02 Services making use of location information
• CPC Class Codes: H04W 4/023 using mutual or relative location information between multiple location based services [LBS] targets or of distance thresholds
• CPC Class Codes: H04W 4/029 Location-based management or tracking services

Abstract

A real time message broker (1) comprises classification (2), pairing (4), and location-seeking functionality (3) to perform real time information interchange. The broker (1) interacts automatically and in real time between mobile devices For example, it could perform real time brokering between two people going to a common destination from the same airport terminal, and looking for a partner to share a cab with; or a person willing to sell a movie ticket and another person looking for the movie ticket. Once a request message, written in natural language (need not have a pre-fixed format), using existing cellular technology, is passed on to the broker (1), it is picked up by the classification engine (2), which categorizes the message using a real time classification algorithm. The pairing engine (4) picks up the filtered and categorized data and maps it to another request message. The logic of classification and pairing is combined with the geographical proximity of the devices to enable real time information interchange.

Claims

1. A message broker comprising:

an interface comprising means for receiving, via a mobile network, request messages originating in subscriber mobile devices;

a location identification engine;

a classification engine comprising means for, in real time, determining from the location identification engine locations of originating mobile devices for received messages, and for classifying each received message according to category of request and location of the originating device, to provide filtered requests;

a pairing engine comprising means for, in real time, matching filtered requests; and

an interface comprising means for sending, in real time, messages to at least two originating mobile devices according to said matching to provide real time information interchange, said messages including information identifying matching requests.

2. The message broker as claimed in claim 1, wherein the classification engine comprises means for parsing incoming messages to determine their content.

3. The message broker as claimed in claim 1, wherein the classification engine comprises means for parsing incoming messages to determine their content;

and wherein the parsing means identifies keywords, and the classification engine also comprises means for associating identified key words with a category according to a category table.

4. The message broker as claimed in claim 1 wherein the classification engine comprises means for parsing incoming messages to determine their content;

and wherein the parsing means identifies keywords, and the classification engine also comprises means for associating identified key words with a category according to a category table; and

wherein the table associates a plurality of key words with some categories.

5. The message broker as claimed in claim 4, wherein each key word has a weighting according to its relevance to the category.

6. The message broker as claimed in claim 1, wherein the classification engine comprises means for parsing incoming messages to determine their content;

and wherein the parsing means identifies keywords, and the classification engine also comprises means for associating identified key words with a category according to a category table; and

wherein there is a category for each of a plurality of request types.

7. The message broker as claimed in claim 1, wherein the classification engine comprises means for parsing incoming messages to determine their content;

and wherein the parsing means identifies keywords, and the classification engine also comprises means for associating identified key words with a category according to a category table; and

wherein the categories are inter-linked by parent/child associations.

8. The message broker as claimed in claim 7, wherein the pairing engine comprises means for identifying successive category pairs in parent/child hierarchy traversal.

9. The message broker as claimed in claim 1, wherein the classification engine comprises means for parsing incoming messages to determine their content;

and wherein the parsing means identifies keywords, and the classification engine also comprises means for associating identified key words with a category according to a category table; and

wherein the key words include pre-allocated text tags.

10. The message broker as claimed in claim 1, wherein the classification engine comprises means for parsing incoming messages to determine their content;

and wherein the parsing means recognises words from different natural languages, and the pairing engine comprises means for matching requests having different natural languages.

11. The message broker as claimed in claim 1, wherein the classification engine comprises means for assigning a time-to-live value to a request message, and the broker attempts matching of the message only during the time span of the time-to-live value.

12. The message broker as claimed in claim 11, wherein the classification engine comprises means for determining the time-to-live value according to request message category.

13. The message broker as claimed in claim 1, wherein the pairing engine comprises means for interrogating a database to identify matches, the database storing tables of pairing categories.

14. The message broker as claimed in claim 1, wherein the pairing engine comprises means for interrogating a database to identify matches, the database storing tables of pairing categories;

and wherein the database comprises means for maintaining a transaction table of paired messages.

15. The message broker as claimed in claim 1, wherein the pairing engine comprises means for interrogating a database to identify matches, the database storing tables of pairing categories;

and wherein the database comprises means for maintaining a transaction table of paired messages; and

wherein the broker comprises means for updating the database with status data indicating status of an information interchange.

16. The message broker as claimed in claim 1, wherein the pairing engine comprises means for interrogating a database to identify matches, the database storing tables of pairing categories;

and wherein the database comprises means for maintaining a transaction table of paired messages; and

wherein the broker comprises means for updating the database with status data indicating status of an information interchange; and

wherein the broker comprises means for updating the status data in response to receiving a termination instruction from a user device.

17. The message broker as claimed in claim 1, wherein the pairing engine comprises means for interrogating a database to identify matches, the database storing tables of pairing categories;

and wherein the database comprises means for maintaining a transaction table of paired messages; and

wherein the broker comprises means for updating the database with status data indicating status of an information interchange; and

wherein the broker further comprises a purging engine for purging the database of old transaction data.

18. The message broker as claimed in claim 17, wherein the purging engine comprises means for purging on the basis of the time-to-live values.

19. The message broker as claimed in claim 1, wherein the location identification engine is a client of an external location server.

20. The message broker as claimed in claim 1, wherein the classification engine comprises means for determining location of a subscriber by parsing a received message including a field including a location identifier.

21. The message broker as claimed in claim 1, wherein the interface comprises plug-in modules each for communication with a type of external entity;

and wherein the interface further comprises a message handler for receiving and routing messages to and from the interface and to and from internal components of the broker.

22. The message broker as claimed in claim 1 wherein the classification engine comprises at least one application and an application factory for dynamically instantiating application instances in real time;

and wherein the pairing engine comprises logic code coupled with application instances.

23. The message broker as claimed in claim 1, further comprising post-matching messaging means for performing message interchange between matched subscribers for them to communicate after being matched.

24. The message broker as claimed in claim 25, wherein the post-matching messaging means comprises means for passing messages between the matched subscribers without need for either subscriber to address the other subscriber;

and wherein the post-matching messaging means comprises means for accessing addressing and matching information stored during the pre-matching operations.

25. The computer readable medium comprising software code for performing operations of a message broker as claimed in claim 1 when executing on a digital processor.