Inter-application data transmitting system and method

Details Inter-application data transmitting system and method Inter-application data transmitting system and method

2000-11-22

2004-08-24

Alam, Shahid (Department: 2172)

Data processing: database and file management or data structures

Database design

Data structure types

C707S793000, C707S793000, C707S793000, C709S202000, C709S223000, C715S252000, C715S252000

Reexamination Certificate

active

06782403

ABSTRACT:

BACKGROUND OF THE INVENTION
1. Field of the Invention
The present invention relates to an inter-application data transmitting system for transmitting data among multiple application systems interconnected over a network, and more particularly, an embodiment of the present invention relates to an inter-application data transmitting system which exchanges data among various types of applications of the business application systems by using the functions of the various types of applications mutually.
2. Description of the Related Art
FIG. 52
of the accompanying drawings shows a block diagram illustrating a conventional architecture of integrated application systems having business applications of different types from each other, which appears in “High-tech Software Dictionary”, page 514, Ohm Press (May 1991 issue).
Referring now to
FIG. 52
, a reference numeral
1
denotes a shared user interface A which is used by a user of a business application A for entering data in order to use the function of the business application A and for receiving an output result from the business application A. The shared user interface A is a type of user interface which is designed for applying commonly to different kinds of business applications. A reference numeral
2
denotes the business application A. A reference numeral
3
denotes a shared communication protocol. The shared communication protocol (
3
) is used for exchanging commands and data between the shared user interface A (
1
) and the business application A (
2
) through a communication channel. The shared communication protocol (
3
) allows the business application A (
2
) to communicate with another business application of a different type. A reference numeral
4
denotes a shared API business program A. The shared API business program A (
4
) is provided with a business program having a data processing function and a shared Application Program Interface (API). The shared Application Program Interface (API) allows the business application A (
2
) to use the function of another business application (e.g., a business application B of
FIG. 52
, which will be discussed later in this embodiment), as a communicating partner. In other words, with reference to
FIG. 52
, the shared API business program A (
4
) of the business application A (
2
) and the shared API business program B of the business application B are provided with the same Application Program Interface (API) function. A reference numeral
5
denotes a data base A for storing business data. The business application A (
2
) is composed of the shared communication protocol (
3
) and the shared API business program A (
4
).
The business application A (
2
) uses a standard data base access language called Structured Query Language (SQL), for example, in order to gain access to the data base A (
5
). Similarly, reference numeral
6
through reference numeral
10
denote elements of a system relating to the business application B (
7
). The business application B (
7
) is provided with the same elements in function as those of the business application A (
2
). A reference numeral
11
denotes a network which connects the business application A (
2
) and the business application B (
7
).
Now, the operation of the above mentioned conventional example is discussed.
In the case of a single use of the business application A (
2
) alone involving no network connection through the network (
11
), the user who intends to use the business application A (
2
) operates the shared user interface A (
1
) so as to use the function of the shared API business program A (
4
). The shared user interface A (
1
) is connected to the shared API business program A (
4
) through the shared communication protocol (
3
). When gaining access to the shared API business program A (
4
) through the shared communication protocol (
3
), the shared user interface A (
1
) uses the shared API.
As an example, it is assumed that data is requested to be written into the data base A (
5
). In that case, the shared API business program A (
4
) writes the data requested by the shared user interface A (
1
) into the data base A (
5
) based on SQL. Then, the written data may be read out from the data base A (
5
) in a later opportunity by a user who uses the shared user interface A (
1
). The readout data from the data base A (
5
) is outputted to the shared user interface A (
1
) through the shared communication protocol (
3
). Similarly, the above mentioned operation applies to the single use of the business application B (
7
). In other words, a user who intends to use the business application B (
7
) operates the shared user interface B (
6
) so as to connect with the shared API business program B (
9
) through the shared common protocol (
8
), thereby utilizing the function of the shared API business program B (
9
).
Next, a discussion will be made of the conventional operation in the case that the business application A (
2
) and the business application B (
7
) are used in a mutual manner by the users of the business applications A (
2
) and B (
7
) over the network.
It is assumed that the user operates the shared user interface A (
1
) in order to use the function of the business application A (
2
) and the function of the business application B (
7
) so as to write data in the data base A (
5
) and further write the data in the corresponding data area in the data base B (
10
), so that the data in the data base B (
10
) has the same meaning as that of the data in the data base A (
5
).
As aforementioned, in the case of writing data into the data base A (
5
), the shared user interface A (
1
) is operated to request the shared API business program A (
4
) to write the data into the data base A (
5
) through the shared communication protocol (
3
).
Now, a description will be made with the data requested to be written into the data base B (
10
).
Now, it is assumed that a data area or a name (which will be referred to hereinafter as the “data area”) corresponding to data written in the data base A (
5
) is previously known by the business application B (
7
).
The shared API business program A (
4
) instructs the shared API business program B (
9
), by using the shared communication protocol (
3
) and the shared communication protocol (
8
), to write the same data as that written into the data base A (
5
) into the corresponding data area of the data base B (
10
). In this case, the data is transmitted from the shared communication protocol (
8
) to the shared API business program B (
9
) by means of the shared API. In other words, the shared API business program A (
4
) and the shared API business program B (
9
) are provided with the same API function. For that reason, the shared API business program A (
4
) can transmit an instruction to write data into the data base B (
10
) to the shared API business program B (
9
) correctly by means of parameters, for example, representing storage position information and the like. The written data in the data base B (
10
) can be read out in a later opportunity by a user of the shared user interface B (
6
). The data, being read out from the data base B (
10
), is outputted to the shared user interface B (
6
) through the shared communication protocol (
8
). In other words, the data written into the data base A (
5
) by the user of the shared user interface A (
1
) is also written into the data base B (
10
) so that the user of the shared user interface B (
6
) can use the data.
As aforementioned, according to the conventional business application system, the following conditions have to be satisfied in order to achieve the mutual use of the functions and data of the two business applications of different types. The conditions include:
1. The business application A (
2
) and the business application B (
7
) are to share the communication protocol such as the shared communication protocol (
3
) and the shared communication protocol (
8
), thereby allowing the business application A (
2
) and the business application B (
7
) to communicate with each other.
2. The API of the

Affiliated with

Also associated with

Rating

Inter-application data transmitting system and method does not yet have a rating. At this time, there are no reviews or comments for this patent.

If you have personal experience with Inter-application data transmitting system and method, we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Inter-application data transmitting system and method will most certainly appreciate the feedback.

Rate now

Comments { 0 }

Profile ID: LFUS-PAI-O-3288916