IP Library Granted Patent US 7,426,535
Granted Patent B2
US 7,426,535 · App. 10/265,740 · Granted Sep 16, 2008

Coordination of data received from one or more sources over one or more channels into a single context

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 7,426,535
App. No.
10/265,740
Granted
Sep 16, 2008
Kind
B2
Abstract

A middleware messaging system is connected between user devices and content providers possibly through one or more networks. The middleware messaging system includes a coordination manager for coordinating partial messages transmitted between the user devices and the content providers. Partial messages are received by the middleware messaging system from one or more sources through one or more channels. Partial messages that are associated with each other comprise a single context and as such are coordinated and transmitted to one or more destinations through one or more channels.

Claims (79)

1. A method for coordinating data from one or more sources, the method comprising steps of:

receiving a request for data from a user device at a coordination manager, said request for data lacking information needed to service said request for data by said coordination manager;

determining whether said request for data lacks information needed to service said request for data, wherein said request for data includes data to be coordinated with other associated data;

coordinating said data with said associated data in response to said request for data lacking information needed to service said request for data, said coordinating forming a message comprised of said data and said associated data; and

determining whether all data to be coordinated is received.

2. The method of claim 1 , wherein the step of coordinating further comprises:

combining said received data and said associated data into a single message.

3. The method of claim 2 , wherein:

said single message is one of a request for data, said request including data received from one or more sources on one or more channels and a response to a request for data transmitted to one or more destinations on one or more channels.

4. The method of claim 1 , further comprising:

transmitting the coordinated data to at least one destination if all said data to be coordinated is received.

5. The method of claim 4 , further comprising steps of:

storing said received data if all the data to be coordinated is not received; and

repeatedly performing said steps of receiving, determining and coordinating until all said data to be coordinated is received.

6. The method of claim 4 , further comprising steps of:

determining whether to generate said request for data if all said data to be coordinated is not received;

transmitting said request for data to at least one source in response to generating said request for data; and

waiting for incoming data.

7. The method of claim 1 , further comprising steps of:

storing said associated data in a memory; and

storing said partial data in said memory, such that said partial data and said associated data are retrievable from said memory for coordination.

8. A method of coordinating data received from one or more sources through one or more channels, the data being transmitted to one or more destinations, the method comprising steps of:

receiving said data at a user device in response to a request for data from said user device at a coordination manager, said request for data lacking information needed to service said request for data by said coordination manager;

determining whether said received data is partial data, wherein partial data includes data to be coordinated with other associated data; and

determining whether said associated data is received in response to said received data being partial data;

coordinating said received data with said associated data in response to said associated data being received; and

determining whether all said data to be coordinated is received.

9. The method of claim 8 , wherein the step of coordinating further comprises:

generating a message including said received data and said associated data, wherein said message is to be transmitted to said one or more destinations.

10. The method of claim 8 , further comprising:

transmitting said coordinated data in a message to each of said one or more destinations in response to all said data to be coordinated being received.

11. The method of claim 10 , further comprising:

determining whether to generate said request for data if all said data to be coordinated is not received;

transmitting said request for data to at least one source in response to generating said request for data; and

waiting for incoming data.

12. The method of claim 10 , wherein the step of determining whether all the data to be coordinated is received further comprises:

determining whether all said data to be coordinated is received using one of message header information and an XML DTD associated with said received data.

13. The method of claim 8 , wherein the step of determining whether the received data is partial data further comprises:

determining whether said received data is partial data using one of message header information and an XML DTD associated with said received data.

14. A messaging system, comprising:

a plurality of user devices connected to a plurality of content providers through one or more networks; and

a coordination manager, said coordination manager comprising:

a module to receive a request for data from a user device, said request for data lacking information needed to service messages requesting data,

a module to coordinate said data with other associated data in messages that are associated with each other, said coordinating forming a message comprised of said data and said associated data,

a module to determine whether all data to be coordinated is received, and

a module to combine all data to be coordinated into at least one coordinated response message.

15. The messaging system of claim 14 , wherein:

said coordination manager includes software stored in a middleware messaging system, wherein said middleware messaging system receives said messages that are associated with each other and transmits said at least one combined message to at least one destination.

16. The messaging system of claim 15 , wherein:

said at least one combined message comprises a single message including data from said messages that are associated with each other.

17. The messaging system of claim 15 , wherein:

said at least one combined message includes a plurality of messages, each transmitted to one of a plurality of destinations.

18. The messaging system of claim 14 , wherein:

said coordination manager determines whether received messages are associated based upon one of message header information and an XML DTD associated with said received messages.

19. The messaging system of claim 15 , wherein:

said content providers include one or more servers connected to said middleware messaging system through one of a direct connection or a connection through said one or more networks.

20. The messaging system of claim 19 , wherein:

said middleware message system is connected to said plurality of user devices through said one or more networks.

21. An apparatus for coordinating messages comprising:

at least one computing device receiving data from one of a content provider and a request for data from a user device, said request for data including data to be coordinated with other associated data, said at least one computing device further to determining whether said received request for data lacks information needed to service said request for data;

a database connected to said at least one computing device and storing said received data and said other associated data; and

a coordination manager, said coordination manager comprising:

a module to receive a request for data from said user device, said request for data lacking information needed to service messages requesting data,

a module to coordinate said data with other associated data in messages that are associated with each other, said coordination manager forming a message comprised of said data and said associated data,

a module to determine whether all data to be coordinated is received, and

a module to combine all data to be coordinated into at least one coordinated response message.

22. The apparatus of claim 21 , wherein:

said at least one computing device retrieving said other associated data from said database for coordinating said other associated data with said received data.

23. The apparatus of claim 22 , wherein:

said received data and said other associated data are coordinated into a single message for transmission to one of a user device and a content provider.

24. An apparatus for coordinating data from one or more sources, the apparatus comprising:

means for receiving a request for data from a user device at a coordination manager;

means for determining whether said request for data lacks information needed to service said request for data, wherein said request for data includes data to be coordinated with other associated data;

means for coordinating said data with said associated data in response to said request for data lacking information needed to service said request for data, said means for coordinating forming a message comprised of said data and said associated data; and

means for determining whether all data to be coordinated is received.

25. The apparatus of claim 24 , wherein:

said means for coordinating combines said received data and said associated data into a single message.

26. The apparatus of claim 25 , wherein:

said single message is one of a request for data, said request including data received from one or more sources on one or more channels and a response to a request for data transmitted to one or more destinations on one or more channels.

Assignments (13)
SECURITY INTEREST Recorded Nov 16, 2018
From: COMTECH TELECOMMUNICATIONS CORP.; COMTECH EF DATA CORP.; COMTECH XICOM TECHNOLOGY, INC.; COMTECH SYSTEMS, INC.; COMTECH PST CORP.; COMTECH MOBILE DATACOM CORPORATION; ANGELS ACQUISITION CORP.; ARMER COMMUNICATIONS ENGINEERING SERVICES, INC.; COMTECH AEROASTRO, INC.; COMTECH ANTENNA SYSTEMS, INC.; COMTECH COMMUNICATIONS CORP.; COMTECH COMSTREAM, INC.; COMTECH SYSTEMS INTERNATIONAL, INC.; COMTECH TOLT TECHNOLOGIES, INC.; TIERNAN RADYNE COMSTREAM, INC.; COMTECH CPI ELECTRON DEVICES CORP.; COMTECH CPI MICROWAVE CORP.; TELECOMMUNICATION SYSTEMS, INC.; NETWORKS IN MOTION, INC.; SOLVERN INNOVATIONS, INC.; MICRODATA, LLC; MICRODATA GIS, INC.; MAPLE ACQUISITION LLC; NEXTGEN COMMUNICATIONS, INC., A CORPORATION OF MARYLAND; NEXTGEN COMMUNICATIONS, INC., A CORPORATION OF VIRGINIA; OLIVE ACQUISITION LLC
To: CITIBANK, N.A.
Reel/Frame 048104/0080 →
RELEASE OF SECURITY INTEREST Recorded Mar 3, 2016
From: SILICON VALLEY BANK
To: TELECOMMUNICATION SYSTEMS, INC.; LONGHORN ACQUISITION, LLC; SOLVEM INNOVATIONS, INC.; QUASAR ACQUISITION, LLC; NETWORKS IN MOTION, INC.
Reel/Frame 037994/0113 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 8, 2014
From: TELECOMMUNICATION SYSTEMS, INC.
To: III HOLDINGS 2, LLC
Reel/Frame 033496/0193 →
RELEASE OF SECURITY INTEREST Recorded May 29, 2014
From: SILICON VALLEY BANK
To: TELECOMMUNICATION SYSTEMS, INC.; SOLVERN INNOVATIONS, INC.; NETWORKS IN MOTION, INC.; MICRODATA GIS, INC.; MICRODATA, LLC; NEXTGEN COMMUNICATIONS, INC.
Reel/Frame 033053/0766 →
CONFIRMATORY ASSIGNMENT Recorded May 2, 2014
From: TELECOMMUNICATION SYSTEMS CORPORATION OF MARYLAND
To: TELECOMMUNICATION SYSTEMS, INC.
Reel/Frame 032814/0172 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 16, 2014
From: GERSHMAN, GREG; MILLER, MICHAEL J.; DARDAMANIS, GEORGE
To: AETHER SYSTEMS, INC.
Reel/Frame 032683/0420 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 16, 2014
From: TELECOMMUNICATION SYSTEMS CORPORATION OF MARYLAND
To: TELECOMMUNICATION SYSTEMS, INC.
Reel/Frame 032683/0641 →
CHANGE OF NAME Recorded Apr 16, 2014
From: TSYS ACQUISITION CORP.
To: TELECOMMUNICATION SYSTEMS CORPORATION OF MARYLAND
Reel/Frame 032695/0746 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 16, 2014
From: AETHER SYSTEMS, INC.
To: TSYS ACQUISITION CORP.
Reel/Frame 032683/0503 →
SECURITY AGREEMENT Recorded Jan 29, 2010
From: TELECOMMUNICATION SYSTEMS, INC.; LONGHORN ACQUISITION, LLC; SOLVERN INNOVATIONS, INC.; QUASAR ACQUISITION, LLC; NETWORKS IN MOTION, INC.
To: SILICON VALLEY BANK, AGENT
Reel/Frame 023870/0484 →
CORRECTIVE ASSIGNMENT TO CORRECT THE RECEIVING PARTY NAME, PREVIOUSLY RECORDED AT REEL 017165, FRAME 0351. Recorded Feb 25, 2008
From: TSYS ACQUISITION CORP.
To: TELECOMMUNICATION SYSTEMS, INC.
Reel/Frame 020594/0627 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 5, 2006
From: TELECOMMUNICATION SYSTEMS CORPORATION OF MARYLAND
To: TELECOMMUNICATION SYSTEMS, INC.
Reel/Frame 018350/0155 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 26, 2004
From: GERSHMAN, GREG; MILLER, MICHAEL J.
To: TSYS ACQUISITION CORP.
Reel/Frame 015378/0101 →