# US 6,732,360 B1 · System and method for providing connection between client and heterogeneous database management systems

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

- Number: US 6,732,360 B1
- Document ID: US6732360B1
- Status: Granted
- Kind: B1
- Application number: 09/455,931
- Filed: 1999-12-07
- Granted: 2004-05-04
- Earliest claimed: 1998-12-07
- Assignees: Korea Telecom
- Inventors: Jung-Min Seo; Ju-Won Song; Eun-Sook Jin; Su-Young Yoon; Moon-Haeng Huh
- Web page: https://patentgrep.com/patent/US6732360B1

## CPC

- H04L 41/022: Multivendor or multi-standard integration
- H04L 41/024: {using relational databases for representation of network management data, e.g. managing via structured query language [SQL]}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A method for providing a connection between a client and heterogeneous database management systems, includes the steps of: a) generating a thread in response to a request message transmitted from the client; b) determining what is the request message and operating a database driver to process the request message by referring to a client information management table; and c) registering identification information of a client and a database in the client information management table and transmitting an execution result corresponding to the request message from the database driver to the client.

## Claims

### Claim 1

A method of providing a connection between a client and heterogeneous database management systems, comprising:
a) generating a thread in response to a request message transmitted from the client;
b) determining what is the request message and operating a database driver to process the request message by referring to a client information management table; and
c) registering identification information of a client and a database in the client information management table and transmitting an execution result corresponding to the request message from the database driver to the client, including:
c1) receiving a response message corresponding to the requesting message from the database driver;
c2) determining whether the response message is related to the database driver operation request message or the connection complete request message;
c3) if the response message is related to the database driver operation request message, registering the identification information of the client and the database in the client information management table;
c4) if the response message is related to the connection complete request message, deleting a database information entry related to the client in the client information management table; and
c5) transmitting the execution result corresponding the request message from the database driver to the client.

### Claim 2 (depends on 1)

The method as recited in claim 1, wherein said step a) includes:
a1) receiving the request message from the client;
a2) determining whether the request message is a client connection request message;
a3) if the request message is the client connection request message, transmitting information related to a socket state to the client; and
a4) if the request message is not the client connection request message, generating the thread in response to the request message.

### Claim 3 (depends on 2)

The method as recited in claim 2, wherein said step b) includes:
b1) determining what is the request message:
b2) if the request message is a client register request message, generating a client entry in the client information management table;
b3) if the request message is an unregister request message, deleting the client entry in the client information management table;
b4) if the request message is a connection complete request message, generating a commit or abort request statement and transmitting the commit or abort request statement to the database driver; and
b5) if the request message is a database driver operation request message, operating the database driver to process the request message by referring to the client information management table.

### Claim 4 (depends on 1)

The method as recited in claim 1, wherein said step c1) includes:
c1-a) transmitting the request message to the database driver;
c1-b) calling a request processing function and a database interface within the request processing function and transmitting a query statement to a database management system;
c1-c) receiving the response message corresponding to the query statement from the database management system;
c1-d) determining whether a format of the response message should be changed;
c1-e) if the format of the response message should be changed, changing the format of the response message; and
c1-f) receiving the response message in the form of the format changed from the database driver.

### Claim 5 (depends on 4)

The method as recited in claim 4, wherein said client information management table includes a database pointer related to the database connected to the client; identification information of the database currently connected to the client; identification information of said database driver currently connected to the database; and a next client information pointer.

### Claim 6

A computer-readable medium for providing a connection between a client and heterogeneous database management systems, comprising the steps of:
a) generating a thread in response to a request message transmitted from the client;
b) determining what is the request message and operating a database driver to process the request message by referring to a client information management table; and
c) registering identification information of a client and a database in the client information management table and transmitting an execution result corresponding to the request message from the database driver to the client, including:
c1) receiving a response message corresponding to the requesting message from the database driver;
c2) determining whether the response message is related to the database driver operation request message or the connection complete request message;
c3) if the response message is related to the database driver operation request message, registering the identification information of the client and the database in the client information management table;
c4) if the response message is related to the connection complete request message, deleting a database information entry related to the client in the client information management table; and
c5) transmitting the execution result corresponding the request message from the database driver to the client.

### Claim 7 (depends on 6)

The computer-readable medium as recited in claim 6, wherein said step a) includes:
a1) receiving the request message from the client;
a2) determining whether the request message is a client connection request message;
a3) if the request message is the client connection request message, transmitting information related to a socket state to the client; and
a4) if the request message is not the client connection request message, generating the thread in response to the request message.

### Claim 8 (depends on 7)

The computer-readable medium as recited in claim 7, wherein said step b) includes:
b1) determining what is the request message;
b2) if the request message is a client register request message, generating a client entry in the client information management table;
b3) if the request message is an unregister request message, deleting the client entry in the client information management table;
b4) if the request message is a connection complete request message, generating a commit or abort request statement and transmitting the commit or abort request statement to the database driver; and
b5) if the request message is a database driver operation request message, operating the database driver to process the request message by referring to the client information management table.

### Claim 9 (depends on 6)

The computer-readable medium as recited in claim 6, wherein said step c1) includes:
c1-a) transmitting the request message to the database driver;
c1-b) calling a request processing function and a database interface within the request processing function and transmitting a query statement to a database management system;
c1-c) receiving the response message corresponding to the query statement from the database management system;
c1-d) determining whether a format of the response message should be changed;
c1-e) if the format of the response message should be changed, changing the format of the response message; and
c1-f) receiving the response message in the form of the format changed from the database driver.

### Claim 10 (depends on 9)

The computer-readable medium as recited in claim 9, wherein said client information management table includes a database pointer related to the database connected to the client; identification information of the database currently connected to the client; identification information of said database driver currently connected to the database; and a next client information pointer.
