Patent US5699523A successfully refreshed from Google Patents.
← Back to Patent Explorer
US5699523A Expired / Lapsed US ⏱️ 0.0 years remaining

Method and apparatus for communication between at least one client and at least one server

Assignee: Bull SAS
•
Filing: 1996-06-05
•
Granted: 1997-12-16
•
Expires: 2016-06-05
📄 Original PDF 🌐 Google Patents 🔄 Sync Now

Abstract

Abstract A device for communication between at least one client and at least one server who are exchanging messages, characterized in that it includes a router which routes the messages between at least one client and at least one server with the aid of three message queues, including a first queue assigned to the router assuring the storage of the messages from clients or servers; a second queue assigned to the server enabling the reading of messages of requests formulated to the server; a third queue assigned to the client enabling the reading of response messages.

Inventors

  • 👤 Jianzhong Li
  • 👤 Jean-Philippe Brunon

Bibliographic Details

Application Number —
Jurisdiction US
Data Source google_patents
Last Synchronized 2026-11-01 11:52
CPC Classifications
H; H04; H04L; H04L9/00; H04L9/40

Claims Analysis

Total Claims: 30
Claim 1
Independent Claim 235 words
A device for communication between at least one client and at least one server which are exchanging messages, comprising a router (360), means connecting the router to said at least one client and said at least one server for routing messages between said at least one client (361, 2) and said at least one server (381, 382, 35) with the aid of three message queues, said three message queues including: a first queue (3601) stored in the router (360) for enabling storage of messages received from said at least one client or said at least one server; a second queue (381) stored in said at least one server for enabling reading of messages including requests directed to said at least one server (38, 35); a third queue (392) stored in said at least one client (39) for enabling reading response messages from said at least one server, each of said messages including a field indicating whether a query or response is involved, the router (360) including means for generating a message identifier for said at least one server (38, 35) and said at least one client (39), and means for writing at the connection with the router a field in the message (Session Id) identifying the client session, and means for writing in other fields of the message (SRV Session Id) information identifying the server session at the connection of a server with the router.
Claim 2
Independent Claim 235 words
A device for communication between at least one client and at least one server which are exchanging messages, comprising a router (360), means connecting the router to said at least one client and said at least one server for routing messages between said at least one client (361, 2) and said at least one server (381, 382, 35) with the aid of three message queues, said three message queues including: a first queue (3601) stored in the router (360) for enabling storage of messages received from said at least one client or said at least one server; a second queue (381) stored in said at least one server for enabling reading of messages including requests directed to said at least one server (38, 35); a third queue (392) stored in said at least one client (39) for enabling reading response messages from said at least one server, each of said messages including a field indicating whether a query or response is involved, the router (360) including means for generating a message identifier for said at least one server (38, 35) and said at least one client (39), and means for writing at the connection with the router a field in the message (Session Id) identifying the client session, and means for writing in other fields of the message (SRV Session Id) information identifying the server session at the connection of a server with the router.
Claim 3
Dependent Claim 18 words
The device of claim 1, wherein the client includes means for generating a message identifier for the router.
Claim 4
Dependent Claim 24 words
The device of claim 1, wherein said at least one server (38, 35) includes means for generating a message identifier for the router (360).
Claim 5
Dependent Claim 22 words
The device of claim 1, wherein each of said messages includes a priority field indicating a degree of priority of said query.
Claim 6
Dependent Claim 22 words
The device of claim 1, wherein each of said messages includes a priority field indicating a degree of priority of said query.
Claim 7
Dependent Claim 24 words
The device of claim 5, wherein each of said messages includes a status field indicating a status of said message via a return code.
Claim 8
Dependent Claim 24 words
The device of claim 1, wherein each of said messages includes a status field indicating a status of said message via a return code.
Claim 9
Independent Claim 188 words
A device for communication between at least one client and at least one server which are exchanging messages, comprising a router (360), means connecting the router to said at least one client and said at leash one server for routing message between said at least one client (361, 2) and said at least one server (381, 382, 35) with the aid of three message queues, said three message queues including: a first queue (3601) stored in the router (360) for enabling storage of messages received from said at least one client or said at least one server; a second queue (381) stored in said at least one server for enabling reading of messages including requests directed to said at least one server (38, 35); a third queue (392) stored in said at least one client (39) for enabling reading response messages from said at least one server, each of said messages including a field indicating whether a query or response is involved and the router (360) including means for generating a message identifier for said at least one server (38, 35) and said at least one client (30-39).
Claim 10
Independent Claim 188 words
A device for communication between at least one client and at least one server which are exchanging messages, comprising a router (360), means connecting the router to said at least one client and said at leash one server for routing message between said at least one client (361, 2) and said at least one server (381, 382, 35) with the aid of three message queues, said three message queues including: a first queue (3601) stored in the router (360) for enabling storage of messages received from said at least one client or said at least one server; a second queue (381) stored in said at least one server for enabling reading of messages including requests directed to said at least one server (38, 35); a third queue (392) stored in said at least one client (39) for enabling reading response messages from said at least one server, each of said messages including a field indicating whether a query or response is involved and the router (360) including means for generating a message identifier for said at least one server (38, 35) and said at least one client (30-39).
Claim 11
Independent Claim 24 words
The device of claims 8, wherein said at least one server (38, 35) includes means for generating a message identifier for the router (360).
Claim 12
Independent Claim 24 words
The device of claims 8, wherein said at least one server (38, 35) includes means for generating a message identifier for the router (360).
Claim 13
Dependent Claim 57 words
The device of claim 8, wherein the message includes a first field of two eight-bit bytes indicating whether communication is synchronous or asynchronous and a second field of two eight-bit bytes to indicate whether the message is a response or a request, by assigning said second field a value 0 or a value other than 0, respectively.
Claim 14
Dependent Claim 23 words
The device of claim 11, wherein the message includes a third field of four eight-bit bytes identifying a user who sent the message.
Claim 15
Dependent Claim 21 words
The device of claim 11, wherein the message includes a field of four eight-bit bytes identifying an addressee of the message.
Claim 16
Independent Claim 106 words
A method for processing synchronous requests between a client and a server in communication through a router, said method including the steps of: sending a message by the client to a first queue (3601) of the router; determining by the router whether the message is a request or a reply; sending a message by the router with an identifier to a second queue (351, 381) assigned to the server; sending an acknowledgement message to the client with an identifier after receiving a response in the first queue of the router and enabling the client to retrieve a response from the first queue (3601) of the router.
Claim 17
Independent Claim 106 words
A method for processing synchronous requests between a client and a server in communication through a router, said method including the steps of: sending a message by the client to a first queue (3601) of the router; determining by the router whether the message is a request or a reply; sending a message by the router with an identifier to a second queue (351, 381) assigned to the server; sending an acknowledgement message to the client with an identifier after receiving a response in the first queue of the router and enabling the client to retrieve a response from the first queue (3601) of the router.
Claim 18
Dependent Claim 12 words
The method of claim 14, wherein the client is itself a server.
Claim 19
Dependent Claim 21 words
The method of claim 14, wherein the server is a client of a different server in a synchronous or asynchronous mode.
Claim 20
Dependent Claim 39 words
The method of claim 14, wherein each message includes a field of two eight-bit bytes indicating whether the communication is synchronous and a field of two eight-bit bytes to indicate whether the message is a response or a request.
Claim 21
Dependent Claim 21 words
The method of claim 14, wherein each message includes a field of four eight-bit bytes identifying a sender of the message.
Claim 22
Dependent Claim 21 words
The method of claim 14, wherein each message includes a field of four eight-bit bytes identifying an addressee of the message.
Claim 23
Independent Claim 141 words
A method for processing asynchronous requests between a client and a server in communication through a router, said method including the following steps: sending a request message by the client to a first queue (3601) of the router with a first identifier; sending a request message by the router with a second identifier to a second queue (351, 381) of the server (35, 38), acknowledging by the router to the client reception of the request message, and acknowledging by the server reception to the router by sending the second identifier to the first queue (3601) of the router (360); and sending a message by the server with the second identifier to the first queue (3601) of the router once the server has prepared a response, the message including a field to indicate whether the message is a response or a request.
Claim 24
Independent Claim 141 words
A method for processing asynchronous requests between a client and a server in communication through a router, said method including the following steps: sending a request message by the client to a first queue (3601) of the router with a first identifier; sending a request message by the router with a second identifier to a second queue (351, 381) of the server (35, 38), acknowledging by the router to the client reception of the request message, and acknowledging by the server reception to the router by sending the second identifier to the first queue (3601) of the router (360); and sending a message by the server with the second identifier to the first queue (3601) of the router once the server has prepared a response, the message including a field to indicate whether the message is a response or a request.
Claim 25
Dependent Claim 48 words
The method of claim 20, further including the steps of sending a message by the router to the second queue (351) of the server (35), sending a first acknowledgement from the server to the router (360) and sending a second acknowledgement from the router to the server (381).
Claim 26
Dependent Claim 67 words
The method of claim 20, further including the steps of retrieving a response by the client by sending a request message (fetch-message) to the first queue (3601) of the router, transmitting by the router said message to the second queue of the server (35), sending a response by the server to the first queue of the router and retransmitting by the router the response to the client.
Claim 27
Dependent Claim 71 words
The method of claim 20, further including the steps of sending by the client a message to the first queue (3601) of the router (360), and comparing by the router a value of the message identifier with the value "-1", in order to either calculate a new message identifier if the value is "-1", or to retransmit the message identifier received to the client if the value is other than "-1".
Claim 28
Dependent Claim 41 words
The method of claim 20, wherein the message includes a field of two eight-bit bytes indicating whether the communication is synchronous or asynchronous and a field of two eight-bit bytes to indicate whether the message is a response or a request.
Claim 29
Dependent Claim 23 words
The method of claim 24, wherein the message includes a field of four eight-bit bytes for identification of a sender of the message.
Claim 30
Dependent Claim 23 words
The method of claim 24, wherein the message includes a field of four eight-bit bytes for identification of an addressee of the message.

References Cited (Backward Citations)

US5265250A Cited
US5230051A Cited
US5355506A Cited
US5390328A Cited
US5329619A Cited

USPTO Annuity & Maintenance Windows

Annuity Stage Window Opens Payment Deadline Surcharge Period Until Estimated Fee Status
3.5 Years (Year 4) 2000-12-15 2001-06-16 2001-12-16 $2000.00 Window Closed / Lapsed
7.5 Years (Year 8) 2004-12-15 2005-06-16 2005-12-16 $3760.00 Window Closed / Lapsed
11.5 Years (Year 12) 2008-12-15 2009-06-16 2009-12-16 $7700.00 Window Closed / Lapsed

Assigned Categories & Tags

No categories assigned to this patent yet.

Assign Category Tag