# US 2004/0062255 A1 · Multiplexing unit, system and method for communication in a computer network

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

- Number: US 2004/0062255 A1
- Document ID: US20040062255A1
- Status: Published application
- Kind: A1
- Application number: 10/381,981
- Filed: 2003-09-12
- Published: 2004-04-01
- Earliest claimed: 2000-10-02
- Assignees: Amadeus S.A.S.
- Inventors: Alexis Grandemange; Veronique Marquion; Pierre Dor; Vincent Lextrait; Francois Weissert
- Web page: https://patentgrep.com/patent/US20040062255A1

## CPC

- H04L 67/1008: based on parameters of servers, e.g. available memory or workload (monitoring of computer activity G06F11/30)
- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L 67/1001: for accessing one among a plurality of replicated servers
- H04L 67/565: Conversion or adaptation of application format or content (adding application control or application functional data H04L67/561)
- H04L 67/63: Routing a service request depending on the request content or context
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

The invention concerns a multiplexing unit, a system and a method for communication in a computer network between a plurality of client machines supporting client programmes and one or several servers supporting application programmes, although said client and application programmes may be incompatible. The invention uses input and output management modules assigned to the client machines and to the servers. It performs conversion operations and routing operations, which are carried out so as to optimise the operation of the servers. It ensures communication between applications having incompatible formats or transfer protocols and this by means of a flexible technique with characteristics of modularity and upgradability. The invention is applicable in particular to computerised reservation systems for example in the field of travels and transport.

## Claims

### Claim 1

Multiplexing unit for communication in a computer network among a number of client machines (16) that support client programs and one or more servers (17) that support application programs, whereby the client programs and the application programs may be incompatible, characterized by the fact that it comprises:
For each type of client machine (16), an input management module (18) that receives requests (20) from client programs and transmits responses (21) to them;
For a server (17) or a group of servers, an output management module (19) that transmits to the server client messages (22) that are addressed to it and that transmits responses (21) to input management modules (18) of client machines (16);
Routing means that are connected to input management modules (18) and output management modules (19) that are able to define the identity of at least one output management module (19) for the processing of a request (20) and to determine the identity of client machine (16) to which message (23) that is obtained from target server (17) is to be addressed;
and conversion means that are able to convert, if necessary, the contents of request (20) into a client message (22) that is compatible with the application program of target server (17) and the contents of message (23) that is obtained from target server (17) into a response (21) that is compatible with the client program.

### Claim 2 (depends on 1)

Unit, according to claim 1, wherein the routing means comprise load distribution means (27) that can define the identity of a target server (17) for the processing of a request (20) according to load conditions.

### Claim 3 (depends on 1, 2)

Unit, according to claim 1 or 2, wherein the routing means comprise at least one routing application module (24, 30) that can be attached to the remainder of the routing means and that can carry out routing functions according to predetermined rules.

### Claim 4 (depends on 1, 2, 3)

Unit, according to any of claims 1 to 3, wherein the conversion means comprise at least one conversion application module (25, 31) that can be attached to the remainder of the conversion means and can carry out predetermined conversion functions.

### Claim 5 (depends on 1, 2, 3, 4)

Unit, according to any of claims 1 to 4, wherein the output management modules comprise a queue file device (26) that can concentrate the input to servers (17).

### Claim 6 (depends on 1, 2, 3, 4, 5)

Unit, according to any of claims 1 to 5, wherein it comprises an administration module (36) that can administer the creation, the suppression, the modification and the state of operation of the input management modules (18) and output management modules (19).

### Claim 7 (depends on 1, 2, 3, 4, 5, 6)

System for communication in a computer network among a number of client machines (16) that support client programs and one or more servers (17) that support application programs, whereby the client programs and the application programs may be incompatible, wherein it integrates at least one multiplexing unit according to any of claims 1 to 6.

### Claim 8 (depends on 6)

System for communication in a computer network among a number of client machines (16) that support client programs and one or more servers (17) that support application programs, whereby the client programs and the application programs may be incompatible, wherein
It integrates at least one multiplexing unit according to claim 6
It comprises a monitoring agent that can control the administration module of the multiplexing unit or units.

### Claim 9 (depends on 3, 4)

System for communication in a computer network among a number of client machines (16) that support client programs and one or more servers (17) that support application programs, whereby the client programs and the application programs may be incompatible, wherein
It integrates at least one multiplexing unit according to claim 3 or claim 4,
It comprises extensions in dynamic link library form that can be loaded by a multiplexing unit to hold application modules (24, 30; 25, 31).

### Claim 10 (depends on 7, 8, 9)

Process for communication in a computer network among a number of client machines (16) that support client programs and one or more servers (17) that support application programs, whereby the client programs and the application programs may be incompatible, able to be used by the system according to claims 7, 8 or 9, wherein
Each client machine (16) of a type under consideration is connected to an input management module (18) that receives requests (20) from the client program and transmits to it responses (21);
An output management module (19) that transmits to server (17) client messages (22) that are addressed to it and that transmits responses (21) to input management modules (18) of client machines (16) is connected to a server (17);
Request (20) is routed by recognition of the data of request (20) including the address of input management module (18) and the network address of client machine (16) from which it is obtained, then at least one target server (17) is determined according to these data;
Request (20) is converted into a client message (22) of a format that is compatible with target server or servers (17);
Client message (22) is routed to output management module (19) of target server (17) for transmission;
Message (23) that is obtained from target server (17) is routed and transmitted by output management module (19) by recognition of message (23) that is obtained from target server (17), then corresponding client machine (16) is determined according to the result of this recognition;
If necessary, before or after its routing, message (23) that is obtained from target server (17) is converted into a response (21) of a format that is compatible with client machine or machines (16);
Response (21) is routed to input management module (18) of client machine (16) for transmission.

### Claim 11 (depends on 10)

Process of communication, according to claim 10, wherein the data of request (20), recognized for its routing, comprise the nature of its contents.

### Claim 12 (depends on 10, 11)

Process of communication, according to claim 10 or 11, wherein at least one routing application module (24, 30) that can be attached to carry out predetermined routing functions is invoked for the routing of request (20) and message (23) that is obtained from target server (17).

### Claim 13 (depends on 10, 11, 12)

Process of communication according to any of claims 10 to 12, wherein at least one conversion application module (25, 31) that can be attached to carry out predetermined conversion functions is invoked for the conversion of request (20) and message (23) that is obtained from target server (17).

### Claim 14 (depends on 10, 11, 12, 13)

Process of communication according to any one of claims 10 to 13, wherein if a single output management module 19 was found during routing and receives throttling messages, the throttling is then administered by:
Definition, at the level of output management module 19, of a maximum number of messages that can be processed by server 17 up to a new definition;
Counting the number of messages received by output management module 19;
Subtraction of the number of messages from the maximum number to obtain a number of acceptable messages so as to determine a throttling level.

### Claim 15 (depends on 10, 11, 12, 13)

Process of communication, according to any one of claims 10 to 13, wherein if all of output management modules 19 that are found during the routing receive throttling messages, the following operations are carried out for each one:
Definition, at the level of output management module 19, of a maximum number of messages that can be processed by server 17 up to a new definition;
Counting of the number of client messages 22 received by output management module 19;
Subtraction of the number of client messages 22 received from the maximum number to obtain a number of acceptable messages so as to determine a throttling level,
and output management module 19 that has the best throttling level is selected.

### Claim 16 (depends on 10, 11, 12, 13)

Process of communication, according to any one of claims 10 to 13, wherein if only a portion of output management modules 19 found during the routing receive throttling messages and the other portion is not subject to the throttling:
1. The following operations are carried out for each output management module 19 that receives throttling messages:
Definition, at the level of output management module 19, of a maximum number of messages that can be processed by server 17 up to a new definition;
Counting of the number of client messages 22 received by output management module 19;
Subtraction of the number of client messages 22 received from the maximum number to obtain a number of acceptable messages so as to determine a throttling level;
The number of acceptable messages is divided by the time remaining up to a new definition of the maximum number of acceptable messages to obtain a request submission frequency;
The request submission frequency is added to the current time to determine from when output management module 19 can accept a new client message 22.
2. Client message 22 is directed to first output management module 19 that receives throttling messages that can accept it
3. Client message 22 is directed to another output management module 19 if no output management module 19 that receives throttling messages can accept it.

### Claim 17 (depends on 16)

Process of communication, according to claim 16, wherein the load is distributed among output management modules 19 that do not receive throttling messages by the following operations:
1. Construction of a table of output management modules 19 that do not receive throttling messages
2. Incrementing a counter with each client message 22 received
3. Integer division of the counter number by the number of output management modules 19 that do not receive throttling messages
4. Use of the remainder of the division as an index in the table to find output management module 19 that does not receive throttling messages to be used.
