US7216181B1
Expired / Lapsed
US
⏱️ 0.0 years remaining
Middleware brokering system
Assignee: T Mobile Innovations LLC
•
Filing: 2001-07-31
•
Granted: 2007-05-08
•
Expires: 2021-07-31
Abstract
Abstract The present invention, known as the Middleware Brokering System, brokers messages between middleware computing products. Each middleware service can send data to the Middleware Brokering System in its native data format and programming syntax. The Middleware Brokering System converts the data transmitted from the different platforms into a standard format known as a structured event. Messages are then transmitted to and stored in an underlying, commercially available publish/subscribe engine. The Middleware Brokering System contains internal logic that determines whether any subscribers are interested in the messages. If an interested subscriber is found, the Middleware Brokering System retrieves the message from the publish/subscribe engine, converts the data from the structured event into the native format of the receiving application, and sends the message to the appropriate application.
Inventors
- 👤 Shrikant Jannu
- 👤 Dora Potluri
- 👤 Denis Tsai
- 👤 Wing Lee
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-10-29 23:40
CPC Classifications
H; H04; H04L; H04L12/00; H04L12/02; H04L12/16; H04L12/18; H04L12/1859; H04L51/00; H04L51/06; H04L51/066; H04L67/00; H04L67/50; H04L67/56; H04L67/565
Claims Analysis
Total Claims: 17
Claim 1
Independent Claim
225 words
A method for asynchronous brokering of messages between middleware computing systems, comprising: a) receiving a message sent from a first application into a first middleware computing system, the first middleware computing system facilitating data exchange among a first group of disparate applications comprising the first application and one or more applications; b) converting the message from a native language format of the first application to a native language format of the first middleware computing system; c) receiving the message sent from the first middleware computing system into a middleware brokering server; d) converting the message from the native language format of the first middleware computing system to a standard format of the middleware brokering server; e) converting the message from the standard format of the middleware brokering server to a native language format of a second middleware computing system, the second middleware computing system facilitating data exchange among a second group of disparate applications comprising a second application and one or more applications; f) sending the message from the middleware brokering server to the second middleware computing system that receives the message; g) converting the message from the native language format of the second middleware computing system to a native language format of the second application; and h) sending the message from the second middleware computing system to the second application that receives the message.
Claim 2
Independent Claim
225 words
A method for asynchronous brokering of messages between middleware computing systems, comprising: a) receiving a message sent from a first application into a first middleware computing system, the first middleware computing system facilitating data exchange among a first group of disparate applications comprising the first application and one or more applications; b) converting the message from a native language format of the first application to a native language format of the first middleware computing system; c) receiving the message sent from the first middleware computing system into a middleware brokering server; d) converting the message from the native language format of the first middleware computing system to a standard format of the middleware brokering server; e) converting the message from the standard format of the middleware brokering server to a native language format of a second middleware computing system, the second middleware computing system facilitating data exchange among a second group of disparate applications comprising a second application and one or more applications; f) sending the message from the middleware brokering server to the second middleware computing system that receives the message; g) converting the message from the native language format of the second middleware computing system to a native language format of the second application; and h) sending the message from the second middleware computing system to the second application that receives the message.
Claim 3
Dependent Claim
37 words
The method of claim 1 wherein the sending first middleware computing system and the receiving second middleware computing system are selected from the group consisting of a mainframe system, a CORBA compliant system, and a JMS system.
Claim 4
Dependent Claim
42 words
The method of claim 2 wherein the sending first middleware computing system communicates with the middleware brokering server via point to point messaging and wherein the middleware brokering server communicates with the receiving second middleware computing system via publish and subscribe messaging.
Claim 5
Dependent Claim
27 words
The method of claim 3 wherein the sending first middleware computing system of a first message is the receiving second middleware computing system of a second message.
Claim 6
Dependent Claim
27 words
The method of claim 3 wherein the receiving second middleware computing system of a first message is the sending first middleware computing system of a second message.
Claim 7
Dependent Claim
22 words
The method of claim 3 wherein the publish and subscribe messaging further comprises a push-pull paradigm across at least one messaging channel.
Claim 8
Dependent Claim
16 words
The method of claim 6 further comprising designating quality of service attributes when configuring the channel.
Claim 9
Dependent Claim
44 words
The method of claim 1 wherein the message is converted from the native language format of the sending first middleware computing system by mapping a plurality of fields in the native format into corresponding fields in the standard format of the middleware brokering server.
Claim 10
Dependent Claim
38 words
The method of claim 8 wherein the native language format of the sending first middleware computing system is selected from the group consisting of a Cobol copybook, JMS TextMessage, JMS BytesMessage; JMS MapMessage; JMS ObjectMessage; and JMS StreamMessage.
Claim 11
Dependent Claim
25 words
The method of claim 8 wherein the sending first middleware computing system is a mainframe system and the native language format is a COBOL copybook.
Claim 12
Dependent Claim
25 words
The method of claim 8 wherein the sending first middleware computing system is a JMS system and the native language format is a JMS MapMessage.
Claim 13
Dependent Claim
44 words
The method of claim 1 wherein the message is converted from the standard format of the middleware brokering server by mapping a plurality of fields in the standard format into corresponding fields in the native language format of the receiving second middleware computing system.
Claim 14
Dependent Claim
38 words
The method of claim 12 wherein the native language format of the receiving second middleware computing system is selected from the group consisting of a Cobol copybook, JMS TextMessage, JMS BytesMessage; JMS MapMessage; JMS ObjectMessage; and JMS StreamMessage.
Claim 15
Dependent Claim
25 words
The method of claim 12 wherein the receiving second middleware computing system is a mainframe system and the native language format is a COBOL copybook.
Claim 16
Dependent Claim
25 words
The method of claim 12 wherein the receiving second middleware computing system is a JMS system and the native language format is a JMS MapMessage.
Claim 17
Dependent Claim
20 words
The method of claim 1 wherein the standard format of the middleware brokering server is a structured event message format.
References Cited (Backward Citations)
US5680551A
Cited
US5764750A
Cited
US20010014910A1
Cited
US5790809A
Cited
US5987497A
Cited
US6381644B2
Cited
US6738975B1
Cited
US6772413B2
Cited
US6956865B1
Cited
US6877023B1
Cited
US6954799B2
Cited
US6868441B2
Cited
US6922685B2
Cited
US20010049702A1
Cited
US6721779B1
Cited
US6782540B1
Cited
US20040221292A1
Cited
US20030163585A1
Cited
US6904598B2
Cited
US6910216B2
Cited
US6948174B2
Cited
US20030037174A1
Cited
US7010609B1
Cited
US6978461B2
Cited
US7051334B1
Cited
US20040122892A1
Cited
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 2010-05-07 | 2010-11-06 | 2011-05-08 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2014-05-07 | 2014-11-06 | 2015-05-08 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2018-05-07 | 2018-11-06 | 2019-05-08 | $7700.00 | Window Closed / Lapsed |