# US 2008/0077560 A1 · Systems, methods, and language for selection and retrieval of information from databases

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2008/0077560 A1
- Document ID: US20080077560A1
- Status: Published application
- Kind: A1
- Application number: 11/534,402
- Filed: 2006-09-22
- Published: 2008-03-27
- Earliest claimed: 2006-09-22
- Assignees: Raytheon Company
- Inventors: Gabriel D. Comi; Kelly L. Peterman
- Web page: https://patentgrep.com/patent/US20080077560A1

## CPC

- G06F 16/8358: {Query translation}
- G06F 16/2433: {Query languages}
- G06F 16/2452: Query translation
- Y10S 707/99942: Manipulating data structure, e.g. compression, compaction, compilation
- Y10S 707/99943: Generating database or data structure, e.g. via user interface
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- Y10S: TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS

## Abstract

The invention provides a system configured to enable a first entity to query a second entity for a result, the system comprising a language specification component and an interface between the first entity and the second entity. The language specification component defines a communications language by which the first and second entities can communicate with each other. The interface is operable to receive from the second entity an instance of a generic request that is specific to the second entity, the instance of the generic request providing information about at least one query element that is supported in a second-entity specific request; and convert a first query from the first entity to the second entity into a second query, wherein the second query includes the at least one query element that is supported in the second-entity specific request.

## Claims

### Claim 1

A method for a client to query a data source, the method comprising:
receiving from the data source an instance of a generic request that is specific to the data source, the instance of the generic request providing information about at least one query element that is supported in a data source specific request; and
converting a first query from the client to the data source, the first query having a first format, to a second query to the data source, where the second query has a second format that includes the at least one query element that is supported in the data source specific request.

### Claim 2 (depends on 1)

The method of claim 1, further comprising analyzing the instance of the generic request to determine at least one publicly accessible query element supported at the data source.

### Claim 3 (depends on 1)

The method of claim 1, wherein the query element comprises at least one element selected from the group consisting of a field, class, interface, and method.

### Claim 4 (depends on 1)

The method of claim 1, wherein the first format is a format different from the second format.

### Claim 5 (depends on 1)

The method of claim 1, wherein the first format comprises a format associated with a predetermined communications language.

### Claim 6 (depends on 5)

The method of claim 5, further comprising:
receiving an initial request from the client to the data source, the initial request being written in a first language;
if the first language is not the same as the predetermined communications language, converting the initial request into a corresponding initial request written in the predetermined communications language; and
using the initial request as the first query.

### Claim 7 (depends on 5)

The method of claim 5, wherein the predetermined communications language is constructed and arranged to enable a client and a data source to communicate with each other without substantial advanced knowledge of each other's architecture or interfaces.

### Claim 8 (depends on 5)

The method of claim 5, wherein the predetermined communications language is characterized by at least one standard to which both the client and the data source agree to adhere.

### Claim 9 (depends on 8)

The method of claim 8, wherein at the least one standard defines a message written in the predetermined communications language, the message selected from the group consisting of request messages and response messages.

### Claim 10 (depends on 8)

The method of claim 8, wherein the at least one standard includes a repository of variables used by at least one of the client and the data source, the repository of variables comprising at least one variable selected from the group consisting of parameters, parameter names, parameter precision, parameter value, parameter units, parameter relationships, types, filters, minimum values, maximum values, ranges, and units of measurement.

### Claim 11 (depends on 1)

The method of claim 1, wherein the first query defines a format in which a response to the query should be returned.

### Claim 12 (depends on 1)

The method of claim 1, further comprising:
querying the data source using the second query;
receiving an initial response from the data source; and
if the initial response is not written in the predetermined communications language, converting the initial response into an initial response written in a predetermined communications language.

### Claim 13 (depends on 12)

The method of claim 12, further comprising:
providing a requested format for results; and
formatting the initial response in accordance with the requested format for results.

### Claim 14

A system configured to enable a first entity to query a second entity for a result the system comprising:
a language specification component defining a communications language by which the first and second entities can communicate with each other;
an interface between the first entity and the second entity, the interface operable to:
receive from the second entity an instance of a generic request that is specific to the second entity, the instance of the generic request providing information about at least one query element that is supported in a second-entity specific request; and
convert a first query from the first entity to the second entity into a second query, wherein the second query includes the at least one query element that is supported in the second-entity specific request.

### Claim 15 (depends on 14)

The system of claim 14, wherein the language specification component further comprises:
a repository of information relating to at least one parameter used in the system; and
a message format for messages written in the communications language, the message format comprising a data description section defining, for a query, the preferred format of a result and defining, for a response to the query, the actual format of a returned result.

### Claim 16 (depends on 15)

The system of claim 15 wherein, the interface is further operable to convert a query message written in the communications language into a format specific to the second entity.

### Claim 17 (depends on 16)

The system of claim 16 wherein the repository further comprises at least one parameter name and wherein the interface is operable to convert the message provided that the second entity uses the at least one parameter name specified in the repository.

### Claim 18 (depends on 17)

The system of claim 17 wherein the interface is operable to convert the message provided that the second entity implements an interface capable of saving the state of an object in a manner that enables the object to be recreated at a different place or time.

### Claim 19

A system enabling a requester to query a data source, the system comprising:
means for defining a communications language that allows the requester and data source to communicate with little or no a priori knowledge of each other's architecture or interfaces; and
means for converting a message written in the communications language to a format usable by either or both of the requester and the data source.

### Claim 20 (depends on 19)

The system of claim 19, further comprising means for formatting a response from the data source into a format compatible with requested format provided in a query from the requester.
