WO2004077781A1 - 通信制御プログラムおよび通信制御方法 - Google Patents
通信制御プログラムおよび通信制御方法 Download PDFInfo
- Publication number
- WO2004077781A1 WO2004077781A1 PCT/JP2003/002277 JP0302277W WO2004077781A1 WO 2004077781 A1 WO2004077781 A1 WO 2004077781A1 JP 0302277 W JP0302277 W JP 0302277W WO 2004077781 A1 WO2004077781 A1 WO 2004077781A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- communication
- connection
- physical
- computer
- request
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
- H04L41/0668—Management of faults, events, alarms or notifications using network fault recovery by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
- H04L43/0811—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking connectivity
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/22—Alternate routing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/28—Routing or path finding of packets in data switching networks using route fault recovery
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/40—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection
Definitions
- the present invention relates to a communication control program and a communication control method for controlling communication between computers, and more particularly to a communication control program and a communication control method for performing communication using a multiplexed transmission path.
- LAN adapter For example, provide two LAN adapters in the system. One LAN adapter is used as the active host, and the other LAN adapter is used as the standby host. When a failure occurs in the active host, the LAN adapter of the active host is disabled, and the LAN adapter of the standby host is enabled (for example, see Patent Document 1). Thus, when a failure occurs in the LAN adapter, communication can be restored via another LAN adapter.
- Patent Document 1
- connection switching method it took a long time for a process such as an application to recognize the disconnection after a failure actually occurred in the transmission path. That is, a transmission line failure is not detected until packet transmission retries fail multiple times. Therefore, communication between processes on different computers stops while retrying packet transmission. As a result, the processing capacity of the entire network is reduced.
- the paths are often multiplexed only in the middle of the paths.
- the LAN adapter communication adapter
- the reliability may not be sufficient if only part of the transmission path is duplicated.
- a route is selected by a device such as a router, the flexibility of using multiple routes at the same time is lost. Disclosure of the invention
- the present invention has been made in view of such a point, and an object of the present invention is to provide a communication management program that prevents inter-process communication on different computers from being interrupted by a failure on one transmission path.
- a communication control program for realizing the functions as shown in FIG. 1 is provided.
- a communication control program according to the present invention is for communicating with another device via a plurality of communication devices connected to a plurality of transmission paths, respectively.
- the computer 1 executes the following processing according to the communication control program.
- the computer 1 selects at least one of the communication devices lc and 1d in response to a connection request from an arbitrary process, and establishes a physical connection via the selected communication device.
- the computer 1 defines a logical connection that combines one or more established physical connections into one.
- the computer 1 when a failure occurs in the physical connection included in the logical connection, the computer 1 reestablishes a physical connection via a communication device different from the physical connection in which the failure occurred, and includes the physical connection in the logical connection. Then, when receiving the communication request conforming to the logical connection from the process 1a, the computer 1 performs communication according to the communication request via the physical connection included in the logical connection at that time.
- one or more physical connections are established, and a logical connection that unifies the physical connections into one is defined. If a physical connection fails, reconnection is performed via another communication device. The establishment of the physical connection included in the logical connection is maintained. When a communication request conforming to the logical connection is issued from the process 1a, communication is performed via the physical connection included in the logical connection.
- a communication control method for communicating with another device via a plurality of communication devices connected to a plurality of transmission paths includes a method for receiving a connection request from an arbitrary process. Accordingly, at least one of the communication devices is selected, a physical connection via the selected communication device is established, and a logical connection that integrates the established one or more physical connections into one is defined. When a failure occurs in the physical connection included in the logical connection, a physical connection via the communication device different from the failed physical connection is reestablished, and the physical connection is included in the logical connection. When a communication request conforming to the logical connection is received from the server, the communication request is responded via the physical connection included in the logical connection. Communicating with the communication control method, characterized in that there is provided.
- one or more physical connections are established in response to a connection request from a process, and a logical connection that unifies those physical connections into one is defined. If a failure occurs in the physical connection, reconnection is performed via another communication device. The establishment of the physical connection included in the logical connection is maintained. Be held. When a communication request conforming to the logical connection is issued from the process, communication is performed via the physical connection included in the logical connection.
- FIG. 1 is a conceptual diagram of the invention applied to the embodiment.
- FIG. 2 is a diagram illustrating an example of a system configuration according to the present embodiment.
- FIG. 3 is a diagram illustrating an example of a hardware configuration of a computer.
- Figure 4 is a functional block diagram of a computer.
- FIG. 5 is a conceptual diagram of a connection mode according to the present embodiment.
- FIG. 6 is a diagram illustrating an example of a data structure of the communication management information table.
- FIG. 7 is a diagram illustrating an example of a data structure of the route management information table.
- FIG. 8 is a diagram illustrating an example of a data structure of a physical management information table.
- FIG. 9 is a diagram illustrating an example of the state management tree.
- FIG. 10 is a diagram illustrating an example of the communication management tree.
- FIG. 11 is a sequence diagram showing a connection establishment procedure.
- FIG. 12 is a diagram showing the first half of the state transition of the information table.
- FIG. 13 is a diagram illustrating the latter half of the state transition of the information table.
- FIG. 14 is a flowchart showing a processing procedure on the server side when a connection is established.
- FIG. 15 is a flowchart showing a processing procedure on the client side when a connection is established.
- FIG. 16 is a sequence diagram showing a procedure when a client computer detects a connection error. .
- FIG. 17 is a diagram showing the first half of the state transition of the information table.
- FIG. 18 is a diagram illustrating the latter half of the state transition of the information table.
- FIG. 19 is a sequence diagram illustrating a procedure when a server computer detects a connection error.
- FIG. 20 is a diagram showing the first half of the state transition of the information table.
- FIG. 21 is a diagram illustrating the latter half of the state transition of the information table.
- FIG. 22 is a flowchart showing a processing procedure when a connection error occurs in the server computer.
- FIG. 23 is a flowchart showing a processing procedure when a connection error occurs in the client computer.
- FIG. 24 is a flowchart showing a procedure for selecting a connection path.
- FIG. 25 is a diagram illustrating an example of a communication management information table on the server side when communication is performed through a plurality of routes.
- FIG. 26 is a diagram illustrating an example of a communication management information table on the client side when communication is performed through a plurality of routes.
- FIG. 27 is a diagram illustrating an example of a physical management information table on the server side when communication is performed through a plurality of routes.
- FIG. 28 is a diagram illustrating an example of a physical management information table on the client side when performing communication through a plurality of routes.
- FIG. 29 is a diagram illustrating an example of transfer when division is unnecessary.
- FIG. 30 is a diagram illustrating a first example in the case where the split transfer is performed.
- FIG. 31 is a diagram illustrating a second example in the case where the split transfer is performed.
- FIG. 32 is a diagram illustrating a third example in the case where the split transfer is performed.
- FIG. 33 is a sequence diagram showing a process of the division transfer.
- FIG. 1 is a conceptual diagram of the invention applied to the embodiment.
- the present invention is applied to a transmission system having a plurality of transmission paths 3 and 4 between a plurality of computers 1 and 2.
- Computer 1 has a plurality of communication devices lc and Id.
- the communication request from the process 1a in the computer 1 is received by the communication control unit 1b.
- This communication control unit 1 b The communication devices lc and Id are controlled to communicate with the computer 2.
- the computer 2 has a plurality of communication devices 2c and 2d.
- the communication request from the process 2a in the computer 2 is received by the communication control unit 2b.
- the communication control unit 2b controls the communication devices 2c and 2d to communicate with the computer 1.
- the communication control units lb and 2b of each of the computers 1 and 2 manage the physical connections established on the multiple transmission paths 3 and 4 collectively, and can be used virtually as a single transmission system (logical connection). Like that. Then, a data communication environment via a virtual transmission path (logical connection) is provided to the processes 1a and 2a to be executed by the user.
- the communication control unit lb selects at least one of the communication devices lc and Id in response to a connection request from an arbitrary process, and establishes a physical connection via the selected communication device. I do.
- the communication control unit lb defines a logical connection that combines one or more established physical connections into one.
- the communication control unit lb reestablishes the physical connection via a communication device different from the physical connection in which the failure occurred, and includes the physical connection in the logical connection.
- the communication control unit lb performs communication according to the communication request via the physical connection included in the logical connection at that time.
- connection relationship in the present invention includes a connection identifier (for example, an IP address) between the different computers 1 and 2, a device name on the computer 1 to be used, route information for specifying an intermediate route, and communication. It can be managed using communication identifiers (eg, TCP port numbers) between applications and communication serial numbers for identifying physical connections.
- connection identifier for example, an IP address
- communication identifiers eg, TCP port numbers
- a logical connection can be identified by a pair of a connection identifier and a communication identifier of both computers 1 and 2.
- Physical communication is recognized in addition to the communication serial number.
- logical communication is a set of multiple physical communication Things.
- the physical communication need only be recognized by the communication control units lb and 2b, and the processes la and 2a need not be recognized.
- the logical connection form is a physical connection in which a plurality of transmission lines 3 and 4 can be used arbitrarily.
- An external logical connection means a connection form recognized by processes 1a and 2a located outside the communication management function.
- the physical connection form is an arbitrary communication device and a physical connection using a transmission line connected to the communication device.
- An internal physical connection means that its existence is hidden from processes 1a and 2a located outside the communication management function.
- the processes 1a and 2a requesting communication on such a system start communication by designating the other party's connection identifier and the communication identifier of itself and the other party.
- the communication control units lb and 2b automatically select an appropriate communication device or transmission path in consideration of the operation state of the communication device and establish a physical connection. Therefore, it is possible to automatically improve the reliability and performance without changing the usage method from the user, and to replace or add equipment without interrupting the usage from the user. It can be carried out.
- the available device or route is automatically determined, and communication is resumed using the same communication sequence number for a reconnection request.
- the processes la and 2a recognize that they are communicating with each other by the logical connection, they can communicate continuously without being aware of the occurrence of a failure on the transmission path. Therefore, the reliability of a communication service for a process generated by a user application or the like is improved.
- the communication speed between processes la and 2a can be improved by performing communication on multiple paths at the same time.
- communication between processes 1a and 2a will not be interrupted and reliability will be improved if a physical connection is established via another transmission line.
- reconnection may be performed each time one physical connection is disconnected, or reconnection may be performed when all connected physical connections are disconnected.
- FIG. 2 is a diagram illustrating an example of a system configuration according to the present embodiment.
- a plurality of computers 100, 200, and 300 are connected via two switch devices 410 and 420.
- two transmission paths that is, a transmission path via the switch device 410 and a transmission path via the switch device 420 are provided between the computers.
- FIG. 3 is a diagram illustrating an example of a hardware configuration of a computer.
- the entire computer 100 is controlled by a CPU (Central Processing Unit) 101.
- the CPU 101 has a RAM (Random Access Memory) 102 via a bus 108, a hard disk drive (HDD) 103, a graphics processing unit 104, and an input interface. 105 and the communication devices 106 and 107 are connected.
- RAM Random Access Memory
- RAM 102 temporarily stores at least a part of an OS (Operating System) program or an application program to be executed by CPU 101. Further, the RAM 102 stores various data required for processing by the CPU 101.
- the HDD 103 stores OS and application programs.
- a monitor 11 is connected to the graphic processing device 104.
- the graphics processing device 104 displays an image on the screen of the monitor 11 in accordance with a command from the CPU 101.
- a keypad 12 and a mouse 13 are connected to the input interface 105.
- the input interface 105 transmits a signal transmitted from the keyboard 12 or the mouse 13 to the CPU 101 via the bus 108.
- the communication device 106 is connected to the switch device 410.
- the communication device 106 transmits and receives data to and from another computer via the switch device 410.
- the communication device 107 is connected to the switch device 420.
- the communication device 107 transmits and receives data to and from another computer via the switch device 420.
- FIG. 4 is a functional block diagram of a computer.
- the computer 100 has a communication management information table 1 1 1, a route management information table 1 1 2, a physical management information table 1 1 3, a user process 1 2 1, a logical communication management unit 1 2 2, and a connection.
- An identification information management unit 123, a used device selection unit 124, and a physical communication management unit 125 are provided.
- the communication management information table 111 manages information on logical communication paths (logical connections) provided to the user process 121.
- the path management information table 112 manages transmission paths (communication devices and transmission paths) to the communication partner.
- the physical management information table 113 manages the connection status of a connection (physical connection) constructed on a physical transmission path.
- the user process 122 is a process that executes processing based on an application program or the like.
- the user process 1221 functions as a server or functions as a client.
- the user process 1 212 that functions as a client outputs a communication start request in response to an operation input or the like instructing a process involving communication with the server.
- This communication start request includes the other party connection identifier / self communication identifier Z the other party communication identifier.
- the logical communication management unit 122 Upon receiving the communication start request output from the user process 122, the logical communication management unit 122 creates the communication management information table 111. The logical communication management unit 122 recognizes the state of the logical connection in a tree structure (communication management tree) based on the communication management information table 111. When the logical communication management unit 122 creates the communication management information table 111, the communication management tree is updated. Thereafter, the content of the communication start request is sent to the connection identification information management unit 123.
- a tree structure communication management tree
- connection identification information management unit 123 recognizes the state of the physical connection in a tree structure (state management tree) based on the route management information table 112, and determines which device is a valid identifier. It is determined whether the device is used. The connection identification information management unit 123 passes the determination result to the used device selection unit 124.
- the use device selection unit 124 determines which device route to use based on the load situation while using a round robin method or the like. When selecting the route to be used, the use device selection unit 124 requests the physical communication management unit 125 connected to the selected route to establish communication.
- the physical communication management unit 125 creates the route management information table 112 in response to the communication start request from the use device selection unit 124 and tries to establish a connection. If the connection cannot be established, the physical communication management unit 125 returns the processing to the use device selection unit 124 and causes the use device to be selected again. Then, the physical communication management unit 125 attempts a reconnection using the re-selected utilization device.
- the communication management information table 211 In the same way as the convenience store 200, the communication management information table 211, the route management information table 212, the physical management information table 21-3, the user process 221, A logical communication management unit 222, a connection identification information management unit 222, a used device selection unit 222, and a physical communication management unit 222 are provided.
- the function of each component is the same as the component of the same name in the computer 100.
- FIG. 5 is a conceptual diagram of a connection mode according to the present embodiment.
- the computer 100 selects the communication devices 106 and 107 to be used for communication using the connection identification information 131.
- the computer 200 selects the communication devices 206 and 207 to be used for communication using the connection identification information 231.
- connection identifier of the computer 100 is “1”, and the connection identifier of the computer 200 is “2”. Also, the identifier of the communication device 106 of the computer 100 is “A”, and the identifier of the communication device 107 is “B”. Further, the identifier of the communication device 206 of the computer 200 is “C”, and the identifier of the communication device 207 is “D”.
- the communication device 106 and the communication device 206 are connected by a transmission line 31, and the identifier of this transmission line is “X”. Further, the communication device 107 and the communication device 207 are connected via a transmission line 32, and the identifier of this transmission line is “Y”. Such a connection relationship is recognized by both computers 100 and 200 and registered in various information tables.
- FIG. 6 is a diagram illustrating an example of a data structure of the communication management information table.
- the communication management information table 111 is generated for each logical connection, and a communication identifier is assigned to each generated communication management information table.
- the communication management information table 111 has columns for own process status, logical communication management identifier, own connection identifier, counterpart connection identifier, physical communication, own communication identifier, counterpart communication identifier, reconnection availability, and establishment. Has been. Information arranged in the horizontal direction in each column is associated with each other.
- an identifier indicating whether the user process performing communication on the own computer is a server or a client is set.
- identification information for uniquely identifying a logical connection recognized from a process is set.
- the identification information of the self computer on the network for example, IP address
- the identification information of the remote computer on the network is set in the remote connection identifier column.
- the identification information of the transmission path when used for communication is set.
- identification information for identifying a user process performing communication is set. Identification information for identifying the user process of the communication partner is set in the column of the communication partner identifier.
- FIG. 7 is a diagram illustrating an example of a data structure of the route management information table.
- the route management information table 112 includes columns for a route identifier, a partner connection identifier, a device used, a route, the number of lines used, and availability. Information arranged in the horizontal direction in each column is associated with each other.
- Communication path identification information (a set of communication apparatus identification information and transmission path identification information) is set in the path identifier column.
- the connection identifier for example, IP address
- the identification information of the communication device is set in the column of the use device.
- the route column the identification information of the transmission route is set. You.
- the number of lines (physical connections) communicating on the communication path is set.
- the availability column sets whether or not a physical route is available. In the example of FIG. 7, the availability is “ ⁇ ” if available, and the availability is “X” if unavailable.
- FIG. 8 is a diagram illustrating an example of a data structure of a physical management information table.
- the physical management information table 113 has columns for a physical communication management identifier, a logical communication management identifier, a communication serial number, path information, and a communication state.
- the information arranged in the horizontal direction in each column is associated with each other.
- identification information for uniquely identifying a physical connection is set.
- identification information for uniquely identifying the logical connection to which the physical connection belongs is set.
- the serial number of the physical communication belonging to the same logical connection is set in the communication serial number (1).
- identification information of a transmission route used for communication is set.
- Information indicating “communication status:” is set in the communication status column. In the example of FIG. 8, the communication state is “ ⁇ ” if communication is possible, and the communication state is “X” if communication is not possible.
- the state management library and the communication management library are configured based on the data having such a structure.
- FIG. 9 is a diagram illustrating an example of the state management tree.
- the connection identifier “1” own connection identifier
- the connection identifier “2” the other-party connection identifier
- the identifiers “A” and “B” of the used devices are set as the lower-level structure of the partner connection identifier.
- Identifiers “X” and “Y” of the paths (transmission paths 31 and 32) connected to the use device are set as the lower-level structure of the use device.
- FIG. 10 is a diagram illustrating an example of the communication management tree.
- the connection identifier “1” own connection identifier
- the connection identifier “2” the other party connection identifier
- Logical communication management identifiers “C 1” and “C 2”, which are identification information of a logical connection, are set as lower structures of the other party connection identifier.
- Communication sequence numbers “P11”, “P12”, and “P2”, which are identification information of physical communication, are set as the lower-level structure of the logical connection.
- the communication management information table 111 is made by the logical communication manager 122. Created. By creating the communication management information table 111 corresponding to the communication start request, the communication management tree recognized by the logical communication management unit 122 is updated. Thereafter, a communication start request is sent to the connection identification information management unit 123 to establish a connection.
- connection identification information management unit 123 refers to the route management information table 112 and recognizes the state management information. Then, the connection identification information management unit 123 determines whether there is a transmission path to the computer corresponding to the partner connection identifier, and which communication apparatus is used for communication via the transmission path. . The connection identification information management unit 123 sends the determination result to the use device selection unit 124.
- the use device selection unit 124 determines the load status (for example, the number of lines used) of the communication devices that can communicate with the computer indicated by the other party connection identifier, and performs communication using a round robin method or the like. Determine the device. Information on the communication device to be used is sent to the physical communication management unit 125.
- the physical communication management unit 125 creates a management information table and tries to establish a connection. That is, the physical communication management unit 125 sends a connection request to the computer 200, and establishes a connection when receiving a reply indicating that connection is possible. If unsuccessful, control is returned to the device selection unit 124. Then, another communication device is selected by the use device selection unit 124 and the physical communication management unit 125 is notified. The physical communication management unit 125 attempts reconnection using the notified communication information, and if successful, updates the route management information table 212 and the physical management information table 213. Then, the establishment of the physical connection is notified to the logical communication management unit 122, and the communication management information table 111 is updated.
- the physical communication management unit 222 receives the connection request from the physical communication management unit 125 and transmits the connection request to the logical communication management unit 222.
- Communication management unit 2 2 2, connection identification information management unit 2 2 3, and use device selection unit 2 2 4 cooperate to use the same communication device as when the connection start request is output from user process 2 2 1 And updates the communication management information table 2 11, route management information table 2 1 2, and physical management information table 2 13.
- the physical communication management unit 225 returns a response indicating that the connection is possible.
- the establishment declaration is sent from the computer 100, the physical connection is established. Then, the establishment of the physical connection is notified to the logical communication management unit 222, and the communication management information table 211 is updated.
- the physical communication management unit 125 can also establish a physical connection via a plurality of transmission paths for one logical connection. In this case, the physical communication management unit 125 sets the communication serial number in order from 1 for each physical connection. For reconnection in the event of an error, a reconnection request is issued via another transmission path using the same communication sequence number. When reconnection of the physical connection is established, communication can be performed using the same communication sequence number as before the failure occurred.
- connection requests for the own communication identifier at both ends must be accepted until the logical connection is disconnected.
- the process can accept connection requests from clients. If the process is functioning as a client, activate the server function (at least the function to accept connection requests) in advance.
- a request is issued directly from the logical communication manager 122 to the physical communication manager 125.
- Data is passed from the physical communication manager 125 to the physical communication manager 222 of the computer 200.
- the physical communication management unit 225 transfers the received data to the logical communication management unit 222. Then, the logical communication management unit 222 sends the data to the user process 222.
- an error occurs after the start of communication, an error is detected in both or one of the physical communication management unit 125 and the physical communication management unit 225.
- the communication device uses the InfiniBand architecture, it detects a failure on the transmission path and Section (physical communication management section 125, 225).
- the physical communication management unit 125 when the physical communication management unit 125 detects a failure, the physical communication management unit 125 requests the use device selection unit 124 to reselect a communication device to be used. Then, the physical communication management unit 125 reconnects the communication via the communication device selected by the use device selection unit 124. At this time, the same communication sequence number is used for the failed physical connection and the reconnected physical connection.
- the physical communication management unit 225 that has received the connection request at the time of reconnection passes the connection request to the logical communication management unit 222.
- the logical communication management unit 222 determines whether the received connection request is a reconnection request based on whether the same connection identifier Z communication identifier Z communication serial number exists in the communication management information table 211. . The judgment result is transmitted to the connection identification information management unit 223. If it is a reconnection request, the connection identification information management unit 223 discards the connection identification information of the existing physical connection from the physical management information table 213 and accepts the reconnection request.
- a failure may be detected on both computers 100 and 200.
- the reconnection request takes precedence over the one that received the request first.
- the request from either the client or the server has priority. For example, if priority is given to the server-side reconnection request, the server-side computer discards the reconnection request sent from the client-side computer.
- connections are made using multiple communication serial numbers.
- a plurality of physical communications are bundled under the logical connection, the load is distributed by taking over the division rules of the logical communication managers 122, 222, and communications are performed in parallel.
- FIG. 11 is a sequence diagram showing a connection establishment procedure.
- the processing on the server side is shown on the left, and the processing on the client side is shown on the right.
- the user process 1221 in the computer 100 is a server and the user process 222 in the computer 200 is a client is described as an example. Will be described.
- the computer 200 selects a connection partner (step S11).
- the communication start request includes the other party's connection identifier, its own communication identifier, and the other party's communication identifier in order to identify the communication partner.
- the server-side computer 100 waits for a connection request (step S12).
- a connection request is issued from the computer 200 to the computer 100 (step S13). Thereafter, the computer 200 enters a state of waiting for a reply (step S14).
- the computer 100 Upon receiving the connection request, the computer 100 returns the connection request (step S15). Thereafter, the computer 100 is in a state of waiting for the establishment declaration (step S16).
- the computer 200 receiving the reply to the connection request issues an establishment declaration (step S17). Thereafter, the computer 200 enters a connection established state (step S18). The computer 100 that has received the establishment declaration is also in a connection established state (step S19).
- a connection is established in such a procedure.
- the following describes the transition status of the contents of the communication management information table and the physical management information table when establishing a connection.
- FIGS. 12 and 13 information on the server side is shown in the upper part and information on the client side is shown in the lower part of the communication management information table. Similarly, regarding the physical management information table, the information on the server side is shown in the upper row, The information on the client side is shown at the bottom.
- FIG. 12 is a diagram showing the first half of the state transition of the information table.
- the first state (ST1) is a state before the start of connection establishment.
- the communication management information table 111 on the server side includes the own server's process “server”, logical communication management identifier “C 1”, self connection identifier “1”, and partner connection identification.
- Child “1”, physical communication “11”, own communication identifier “10”, partner communication identifier “1-J, reconnection availability” "-”, establishment “X” are set.
- "one” indicates that the information is not registered.
- An established “X” indicates that the connection has not been established.
- the communication management information table 211 on the client side includes the status “client” of the own process, the logical communication management identifier “C2”, the own connection identifier “2”, the partner connection identifier “1”, and the physical communication “—1”. ”, Own communication identifier“ 99 ”, partner communication identifier
- the communication management information table 211 on the client side registers the partner identifier and the partner communication identifier indicated by the communication start request. At this time, no information is registered in the physical management information tables 113 and 213.
- the second state (ST2) is a state after selection of a connection partner on the client side (step S11).
- a connection partner is selected from the computer 200 on the client side
- physical communication “ ⁇ 2” is set in the communication management information table 211 on the client side.
- a physical communication management identifier “ ⁇ 2”, a logical communication management identifier “C2”, a communication sequence number “1”, route information “CX”, and a communication state “X” are set in the physical management information table 213 on the client side.
- the third state (ST3) is a state after the connection request is returned from the server (step S15).
- the other party's connection identifier “2”, the other party's communication identifier “99”, and the possibility of reconnection “Y” are set in the communication management information table 111 on the server side.
- the physical management information table 113 on the server side includes the physical communication management identifier “P 1”, the logical communication management identifier “C 1”, the communication sequence number “1”, the route information “AXJ, the communication status“ X "is set.
- FIG. 13 is a diagram illustrating the latter half of the state transition of the information table.
- the fourth state (ST 4) shows the state after the client issues the establishment declaration (step S 17).
- the establishment “ ⁇ ” is set in the communication management information table 211 on the client side.
- Established “ ⁇ ” is a flag indicating that the connection is established.
- the communication state of the physical management information table 2 13 on the client side is changed to “ ⁇ ” (indicating that communication is possible).
- the fifth state (ST5) indicates the state after the connection has been established (step S19).
- the computer 100 on the server side sets the establishment “ ⁇ ” in the communication management information table 111.
- the communication status of the physical management information table 113 on the server side is changed to “ ⁇ ”.
- the physical connection is established, and information on the logical connection and the physical connection is registered in the communication management information table and the physical management information table of both the server and the client.
- FIG. 14 is a flowchart showing a processing procedure on the server side when a connection is established. Hereinafter, the processing illustrated in FIG. 14 will be described along the step numbers.
- Step S21 The computer 100 on the server side determines whether a connection request has been received. If a connection request has been received, the process proceeds to step S22. If a connection request has not been received, the process of step S21 is repeated, and a connection request is received.
- Step S222 The computer 100 determines whether or not the received connection request is a connection request from a connectable partner. If it is a connection request from a connectable partner, the process proceeds to step S23. If it is a connection request from an unreachable partner, the process proceeds to step S29.
- Step S2 3 The computer 100 provides the reconnection means with the connection partner. Information indicating whether or not the information is stored is stored. Whether or not the reconnection means is provided is determined, for example, based on information included in the connection request. In this case, the client computer 200 sends a connection request with information indicating whether the client computer 200 provides reconnection means.
- Step S224 The computer 100 sends a reply to the client computer 200 that the connection is possible.
- Step S25 The computer 100 determines whether or not a predetermined time has elapsed after the reply in step S224. If the certain time has elapsed, the process proceeds to step S29. If not, the process proceeds to Step S26.
- Step S226 The computer 100 determines whether a reply has been received from the client computer 200. If a reply is received, the process proceeds to step S27. If no reply is received, the process proceeds to step S25, and the elapse of time is determined.
- Step S27 The computer 100 determines whether or not the received reply is a declaration of establishment. If so, the process proceeds to Step S28. If it is not an establishment declaration (for example, notification of connection refusal), the process proceeds to step S30.
- an establishment declaration for example, notification of connection refusal
- Step S28 The computer 100 completes the establishment and ends the process.
- Step S229 If the connection request is sent from the unreachable partner, or if there is no reply from the client computer 200 for a certain period of time after the connection is returned, A connection refusal is returned to computer 200.
- Step S300 After returning the connection refusal or when receiving a reply other than the establishment declaration in step S27, the computer 100 determines that the establishment has failed, and ends the processing.
- FIG. 15 is a flowchart showing a processing procedure on the client side when a connection is established. Hereinafter, the processing illustrated in FIG. 14 will be described along the step numbers.
- Step S41 Client computer 200 selects a connection partner.
- Step S42 Computer 200 transmits a connection request to computer 1 ⁇ 0 of the connection partner.
- Step S43 The convenience store 200 determines whether or not a fixed time has elapsed after transmitting the connection request. If the predetermined time has elapsed, the process proceeds to step S51. If not, the process proceeds to Step S44.
- Step S444 Computer 200 determines whether a reply has been received from computer 100 on the server side. If a reply has been received, the process proceeds to step S45. If no reply is received, the process proceeds to step S43.
- Step S45 The computer 200 determines whether or not the received reply is a connectable reply. If the reply indicates that connection is possible, the process proceeds to step S46. If the connection is not possible, the process proceeds to step S52.
- Step S46 The computer 200 determines whether connection can be established. If the connection can be established, the process proceeds to step S47. If the connection cannot be established, the process proceeds to step S51.
- Step S47 The computer 200 determines whether or not the other computer 100 has reconnection means. If the partner computer 100 has reconnection means, the process proceeds to step S48. If not, the process proceeds to step S49.
- Step S48 The computer 200 sets up a server with its own communication identifier.
- Step S500 The computer 200 completes the establishment and ends the process.
- Step S510 The computer 200 returns a connection refusal to the computer 100 if there is no reply for a certain period of time after the transmission of the connection request or if it is determined that the connection cannot be established in step S46. .
- Step S52 After returning the connection refusal or receiving the connection not possible reply in step S45, the computer 200 determines that the establishment has failed, and ends the process. Next, processing when a connection error is detected on the client side will be described in detail.
- FIG. 16 is a sequence diagram showing a procedure when a client computer detects a connection error.
- the processing on the server side is shown on the left, and the processing on the client side is shown on the right.
- the user process 1221 in the computer 100 is a server and the user process 222 in the computer 200 is a client as an example, it is assumed that the reestablishment of the connection has been completed normally. The flow will be described.
- the client computer 200 detects a physical connection abnormality and selects a reconnection route (step S61). As a result, the computer 100 is selected as the reconnection partner. At this time, the server computer 100 waits for a reconnection request (step S62).
- the computer 200 issues a reconnection request to the computer 100 (step S63). After that, the computer 200 enters a state of waiting for a reply (step S64).
- the computer 100 Upon receiving the reconnection request, the computer 100 replies to the reconnection request (step S65). Thereafter, the computer 100 is in a state of waiting for the establishment declaration (step S66).
- the computer 200 that has received the reply of the reconnection request issues an establishment declaration (step S67). Thereafter, the computer 200 enters a connection established state (step S68). The computer 100 that has received the establishment declaration is also in a connection established state (step S69).
- FIGS. 17 and 18 describe the transition of the contents of the communication management information table and the physical management information table when the client detects an error and issues a reconnection request, with reference to FIGS. 17 and 18. .
- the communication management information table the information on the server side is shown in the upper part, and the information on the client side is shown in the lower part.
- the physical management information table information on the server side is shown in the upper part, and information on the client side is shown in the lower part.
- FIG. 17 is a diagram illustrating the first half of the state transition of the information table.
- the first state (ST11) is a state after failure detection on the client side.
- the communication management information table 111 on the server side includes the position of the own process “server”, the logical communication management identifier “C 1”, the own connection identifier “1”, the partner connection identifier “2”, Physical communication “P 1”, own communication identifier “10”, partner communication identifier “99”, reconnection availability “Y”, establishment “ ⁇ ” are set.
- the position of the own process “client”, the logical communication management identifier “C2”, the own connection identifier “2”, the partner connection identifier “1”, and the physical communication “11” Its own communication identifier “99”, the other party communication identifier “10”, reconnection availability “Y”, and establishment “X”.
- the communication management information table 211 on the client side registers the partner identifier and the partner communication identifier indicated by the communication start request.
- the physical management information table 113 on the server side stores the physical communication management identifier “ ⁇ 1”, the logical communication management identifier “C1”, the communication sequence number “1”, the route information “AX”, and the communication state “ ⁇ ”. Is set. No information is registered in the physical management information table 213 on the client side.
- the second state (ST12) is a state after the reconnection route on the client side is selected (step S61) and the reconnection request is issued (step S63).
- the physical communication “P4” is set in the communication management information table 211 on the client side.
- the physical communication management identifier “P4”, the logical communication management identifier “C2”, the communication sequence number “1”, the route information “DX”, and the communication state “X” are set. You.
- the third state (ST13) is a state after the server returns a reconnection request (step S65).
- the server-side computer 100 knows that a failure has occurred due to the reconnection request, and changes the establishment of the communication management information table 111 to “X”. At this time, the communication state of the physical management information table 113 on the server side is changed to “X”.
- FIG. 18 is a diagram illustrating the latter half of the state transition of the information table.
- the client issues a declaration of establishment (step S6). 7) Shows the state after.
- the establishment declaration is issued from the computer 200 on the client side
- the establishment of the communication management information table 211 on the client side is changed to “ ⁇ ”.
- the communication state of the client-side physical management information table 2 13 is changed to “ ⁇ ”.
- the fifth state (ST15) shows the state after the connection is established (step S69).
- the server computer 100 receives the establishment declaration, the establishment of the communication management information table 111 is changed to “ ⁇ ”.
- the communication state of the server-side physical management information table 113 is changed to “ ⁇ ”.
- FIG. 19 is a sequence diagram illustrating a procedure when a server computer detects a connection error.
- the processing on the server side is shown on the left, and the processing on the client side is shown on the right.
- the user process 122 in the computer 100 is a server and the user process 222 in the computer 200 is a client, the re-establishment of the connection is completed normally. The following describes the flow when this is done.
- the computer 100 on the server side detects a physical connection abnormality and selects a reconnection route (step S71). As a result, the combination 200 is selected as the reconnection partner. At this time, the client computer 200 waits for a reconnection request (step S72).
- the computer 100 issues a reconnection request to the computer 200 (step S73). Thereafter, the computer 100 is in a state of waiting for a reply (step S74).
- the computer 200 Upon receiving the reconnection request, the computer 200 replies to the reconnection request (step S75). Thereafter, the computer 200 enters a state of waiting for the establishment declaration (step S76).
- the computer 100 that has received the reconnection request reply issues an establishment declaration. (Step S77). Thereafter, the computer 100 enters a connection established state (step S78). Also, the computer 200 that has received the establishment declaration enters the connection established state (step S79).
- connection is re-established in such a procedure.
- the transition of the contents of the communication management information table and the physical management information table when an error is detected and a reconnection request is issued on the server side will be described below with reference to FIGS.
- the communication management information container the information on the server side is shown in the upper part, and the information on the client side is shown in the lower part.
- the physical management information table information on the server side is shown in the upper row, and information on the client side is shown in the lower row.
- FIG. 20 is a diagram showing the first half of the state transition of the information table.
- the first state (ST21) is a state after failure detection on the server side.
- the communication management information table 111 on the server side includes the position of the own process “server”, the logical communication management identifier “C1”, the own connection identifier “1”, the other party connection identifier “2”, Physical communication “—one”, own communication identifier “10”, partner communication identifier “99”, reconnection possibility “Y”, establishment “X” are set.
- the position of the own process “client”, the logical communication management identifier “C2”, the own connection identifier “2”, the partner connection identifier “1”, and the physical communication “P 2” Its own communication identifier “99”, the other party communication identifier “10”, and reconnection availability “Yj”, establishment “ ⁇ ” are set.
- the physical management information table 213 on the client side the physical communication management identifier “P2”, the logical communication management identifier “C2”, the communication sequence number “1”, the route information “CX”, and the communication state “ ⁇ ” are set. ing. No information is registered in the physical management information table 113 on the server side.
- the second state (ST22) is a state after a reconnection path on the server side is selected (step S71) and a reconnection request is issued (step S73).
- a connection request is issued from the computer 100 on the server side
- physical communication “P 3” is set in the communication management information table 111 on the server side.
- the physical management information table 113 on the server side stores the physical communication management identifier “P 3”, the logical communication management identifier “C 1”, the communication serial number “1”, the route information “: BY”, Communication status "X" is set.
- the third state (ST 23) is a state after a reconnection request reply from the client side (step S 75). Klein and the computer 200 at the side know that a failure has occurred due to the reconnection request, and change the establishment of the communication management information table 211 to "X”. At this time, the communication state of the client-side physical management information table 2 13 is changed to “X”.
- FIG. 21 is a diagram illustrating the latter half of the state transition of the information table.
- the fourth state (ST 24) shows the state after the server issues the establishment declaration (step S 77).
- the establishment declaration is issued from the computer 100 on the server side
- the establishment of the communication management information table 111 on the server side is changed to “ ⁇ ”.
- the communication status of the physical management information table 113 on the server side is changed to “ ⁇ ”.
- the fifth state (ST25) indicates the state after the connection is established (step S79).
- the client computer 200 receives the establishment declaration, the establishment of the communication management information table 211 is changed to “ ⁇ ”. At this time, the communication status in the client-side physical management information table 2 13 is changed to “ ⁇ ”.
- FIG. 22 is a flowchart showing a processing procedure when a connection error occurs in the server computer. Hereinafter, the processing illustrated in FIG. 22 will be described along the step numbers.
- Step S81 The server computer 100 that has detected a physical connection failure determines whether it can reconnect to the client computer 200. If so, the process proceeds to Step S82. If reconnection is not possible, the process proceeds to step S89.
- Step S82 The computer 100 selects a reconnection route.
- Step S83 The computer 100 transmits a reconnection request by using the same communication identifier as that used in the disconnected physical connection.
- Step S84 Computer 100 is the computer (client computer) It is determined whether or not a reconnection request has been received since 2000). If a reconnection request has been received, the process proceeds to step S85. If a reconnection request has not been received, the process proceeds to step S86.
- Step S85 The computer 100 rejects the reconnection request sent from the client computer 200.
- Step S863 The computer 100 determines whether a reply to the reconnection request has been received. If a reply to the reconnection request has been received, the process proceeds to step S87. If no reply has been received, the process proceeds to step S84.
- Step S87 The computer 100 determines whether or not the content of the reply to the reconnection request is a reconnection rejection notification. If so, the process proceeds to step S89. If not, the process proceeds to Step S88.
- Step S88 The computer 100 re-establishes a connection (physical connection) using the communication path selected in step S82, and ends the process.
- Step S89 The computer 100 determines that the connection has been disconnected, and ends the processing.
- FIG. 23 is a flowchart showing a processing procedure when a connection error occurs in the client computer. Hereinafter, the processing illustrated in FIG. 23 will be described along the step numbers.
- Step S91 The computer 200 on the client side that has detected the failure of the physical connection determines whether it can reconnect to the computer 100 on the server side. If so, the process proceeds to Step S92. If reconnection is not possible, the process proceeds to step S99.
- Step S92 The computer 200 selects a reconnection route.
- Step S93 The computer 200 transmits a reconnection request using the same communication identifier as that used in the disconnected physical connection.
- Step S94 The computer 200 determines whether a reconnection request has been received from the partner (computer 100 on the server side). If a reconnection request has been received, the process proceeds to step S95. If the reconnection request has not been received, the process proceeds to step S96. [Step S95] The computer 200 acknowledges the reconnection request sent from the server computer 100. Thereafter, the process proceeds to step S98.
- Step S966 The computer 100 determines whether a reply to the reconnection request has been received. If a reply to the reconnection request has been received, the process proceeds to step S97. If no reply has been received, the process proceeds to step S94.
- Step S97 The computer 100 determines whether or not the content of the reply to the reconnection request is a reconnection rejection notification. If so, the process proceeds to Step S94. If not, the process proceeds to Step S98.
- Step S98 The computer 100 re-establishes a connection (physical connection) using the communication path selected in step S92, and ends the process.
- Step S99 The computer 100 determines that the connection has been disconnected, and ends the processing.
- the route management information table When selecting a connection route, the route management information table is referred to and a connection route with a small number of used lines is selected. For example, in the case of the route management information table 112 having contents as shown in FIG. 7, the route with the route identifier “AX” is selected.
- FIG. 24 is a flowchart showing a procedure for selecting a connection path. In the following description, it is assumed that the computer 100 selects a connection path. Hereinafter, the processing illustrated in FIG. 24 will be described along the step numbers.
- Step S1001 The computer 100 selects a route having the smallest number of available lines among the available routes. At this time, a plurality of routes may be selected.
- Step S1002 The computer 100 determines whether or not there is one selected route. If there is one, the process proceeds to step S104. If a plurality is selected, the process proceeds to step S103.
- Step S103 The computer 100 selects a route having a small route identifier (comes first as a character array). For example, if the path identifier is indicated by an alphabet, A will be the smallest value and Z will be the largest value.
- Step S104 The computer 100 determines one of the selected routes as a connection route.
- the above explanation is an example in which one physical connection is established between computers, but a plurality of physical connections may be established in one logical connection.
- a plurality of physical communication management identifiers are registered in the column of physical communication in the communication management information table.
- FIG. 25 is a diagram illustrating an example of a communication management information table on the server side when communication is performed through a plurality of routes.
- the communication management information table 111 shown in FIG. 25 two physical connections of physical communication management identifiers “P 1” and “P 2” are established for the logical connection of logical communication management identifier “C 1”. are doing.
- FIG. 26 is a diagram illustrating an example of a communication management information table on the client side when communication is performed through a plurality of routes.
- the communication management information table 211 shown in FIG. 26 two physical connections with physical communication management identifiers “P 3” and “P 4” are established for the logical connection with logical communication management identifier “C 2”. ing.
- FIG. 27 is a diagram illustrating an example of a physical management information table on the server side when communication is performed through a plurality of routes.
- the physical management information table 113 shown in FIG. 27 two pieces of physical management information on the physical connection with the common logical communication management identifier “C 1” are registered. Each connection has a different connection path.
- FIG. 28 is a diagram illustrating an example of a physical management information table on the client side when performing communication through a plurality of routes.
- the physical management information table 2 13 shown in FIG. 28 two pieces of physical management information regarding the physical connection with the common logical communication management identifier “C 2” are registered. Each connection has a different connection path.
- a negotiation bucket is transmitted at the time of transfer in order to perform division.
- the negotiation packet is sent from the sender on the physical connection with the smallest communication serial number, and a reply is required.
- a reply is required only if data transfer over multiple paths is required.
- a request packet is transmitted from the transmitting side to the receiving side.
- the request packet contains information on the transfer size and the division size.
- the transfer size is the total size of the transfer data. Division
- Division The size is the maximum amount of data that can be transmitted over one physical connection.
- the receiving side that has received the request packet returns a reply packet to the transmitting side.
- the reply packet includes the reception size.
- the receiving size is the data size that can be received by the receiving side.
- FIG. 29 is a diagram illustrating a transfer example when division is unnecessary.
- the number of physical connections is 2
- the transfer size is 1KB
- the split size is 1MB
- the receive size is 1KB.
- the division size is larger than the transfer size
- data transmission is performed after transmitting a request packet from the transmission side to the reception side.
- the transfer size is smaller than the split size, even if two physical connections are established, no split transfer is performed overnight, and one physical connection (the transmission side “P 1” and the reception side “ P 3 ”).
- FIG. 30 is a diagram illustrating a first example in the case where the split transfer is performed.
- the number of physical connections is 2, the transfer size is 8MB, the split size is 1MB, and the receive size is 8MB.
- the transfer size is larger than the split size, split transfer using two physical connections is performed.
- a request packet is transmitted from the transmitting side, a reply packet is returned from the receiving side.
- the transmitting side recognizes that the data of the transfer size can be received by the receiving side based on the reception size included in the reply packet, and starts data division transfer.
- the transfer of 1 MB from the sender “P 1” to the receiver “P 3” and the transfer of 1 MB from the sender “P 2” to the receiver “P 4” are performed alternately. Then, 8 MB of data is transferred by eight transfers.
- FIG. 31 is a diagram illustrating a second example in the case where the split transfer is performed.
- the number of physical connections is 2, the transfer size is 7 MB, the split size is 2 MB, and the receive size is 7 MB.
- 2MB transfer from the sender "P1" to the receiver "P3" and 2MB transfer from the sender "P2" to the receiver "P4" are performed alternately. . Then, after the transfer of 2 MB is performed three times, in the fourth transfer, the remaining 1 MB of data is transferred.
- FIG. 32 is a diagram illustrating a third example in the case where the split transfer is performed.
- the number of physical connections is 2, the transfer size is 8MB, the split size is 2MB, and the receive size is 5MB.
- the transfer size is larger than the reception size, only the data of the reception size is transferred.
- a 2 MB transfer from the sender “P 1” to the receiver “P 3” and a 2 MB transfer from the sender “P 2” to the receiver “P 4” alternately occur.
- the remaining 1 MB of data is transferred. That is, a total of 5 MB data transfer is performed.
- FIG. 33 is a sequence diagram showing the process of the division transfer. Hereinafter, the processing illustrated in FIG. 33 will be described along the step numbers. In the following description, it is assumed that data is transferred from the computer 100 to the computer 200.
- Step S111 The receiving-side computer 200 is waiting for reception of the request packet.
- Step S112 In response to a request from a user process or the like, the transmitting computer 100 transmits a request packet to the receiving computer 200.
- Step S113 The computer 200 that has received the request bucket compares information on the transfer size and the division size included in the request packet. Then, the computer 200 determines whether or not the transfer size is larger than the division size. If the transfer size is larger, the process proceeds to step S114. If not, the process proceeds to Step S118.
- Step S117 The computer 100 waits for reception of a reply packet from the computer 200.
- Step S118 The computer 200 transmits a reply bucket including the information of the reception size to the computer 100.
- Step S119 The computer 100 that has received the reply bucket sets the transfer size equal to the reception size.
- Step S120 The computer 100 sets PN as the number of physical connections, PS as a division size, TS as a transfer size (equal to the reception size), and obtains values of LOOP and AN.
- LOOP is the quotient of TS ⁇ (PSXPN). The remainder at this time is LS.
- AN is the quotient of LS + PS. The remainder at this time is referred to as AS.
- Step S121 The computer 200 obtains values of LOOP and AN using PN as the number of physical connections, PS as a division size, and TS as a reception size.
- LO ⁇ P is the quotient of TS ⁇ (PSXPN). The remainder at this time is LS.
- AN is the quotient of LS ⁇ PS. The remainder at this time is referred to as AS.
- Step S122 The computer 100 executes the data transfer of the division size by the number of times indicated by the LOOP via each established physical connection.
- Step S123 The computer 200 receives the data of the division size by the number of times indicated by the LOOP via each established physical connection.
- Step S124 The computer 100 executes data transfer for the division size via the physical connection whose communication serial number is AN or less.
- Step S125 The computer 200 receives data of the division size via the physical connection whose communication serial number is AN or less.
- Step S126 The computer 100 executes data transfer for the AS via the physical connection whose communication serial number is AN or less.
- the computer 200 receives the data for the AS via the physical connection whose communication serial number is AN or less.
- a program is provided that describes the processing of the functions that the computer should have.
- the program describing the processing contents can be recorded on a computer-readable recording medium.
- Computer-readable recording media include magnetic recording devices, optical disks, magneto-optical recording media, and semiconductor memory. Magnetic recording devices include hard disk drives (HDD), flexible disks (FD), and magnetic tapes.
- Optical discs include DVD (Digital Versatile Disc), DVD-EAM (Eandom Access Memory), CD-R ⁇ M (Compact Disc Read Only Memory), CD-R (Recordable) and ZRW (Rewritable).
- Magneto-optical recording media include MO (Magneto-Optical disc).
- portable recording media such as DVD, CD-ROM, on which the program is recorded are sold.
- the program can be stored in the storage device of the server computer, and the program can be transferred from the server computer to another computer via a network.
- the computer that executes the program stores, for example, the program recorded on the portable recording medium or the program transferred from the server computer in its own storage device. Then, the computer reads the program from its own storage device and executes processing according to the program. It should be noted that the computer can read the program directly from the portable recording medium and execute processing according to the program. Further, the computer can execute the processing according to the received program each time the program is transferred from the server computer.
- one or more physical connections are defined as one logical connection, and if a failure occurs in the physical connection, reconnection is performed via another communication device, and logical connection is performed. Physical communication included in logical connection according to communication requirements Added communication via connection. Therefore, the process that issues a communication request recognizes that one logical connection is continuously connected. As a result, retry processing in the event of a communication failure becomes unnecessary, communication continuity is maintained, and highly reliable inter-computer communication is realized.
Abstract
Description
Claims
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2004568758A JP4040628B2 (ja) | 2003-02-27 | 2003-02-27 | 通信制御プログラム |
PCT/JP2003/002277 WO2004077781A1 (ja) | 2003-02-27 | 2003-02-27 | 通信制御プログラムおよび通信制御方法 |
EP03707157A EP1599004A4 (en) | 2003-02-27 | 2003-02-27 | COMMUNICATION CONTROL PROGRAM AND COMMUNICATION CONTROL METHOD |
US11/087,273 US7768905B2 (en) | 2003-02-27 | 2005-03-23 | Program and method for controlling communication |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/JP2003/002277 WO2004077781A1 (ja) | 2003-02-27 | 2003-02-27 | 通信制御プログラムおよび通信制御方法 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/087,273 Continuation US7768905B2 (en) | 2003-02-27 | 2005-03-23 | Program and method for controlling communication |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2004077781A1 true WO2004077781A1 (ja) | 2004-09-10 |
Family
ID=32923112
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2003/002277 WO2004077781A1 (ja) | 2003-02-27 | 2003-02-27 | 通信制御プログラムおよび通信制御方法 |
Country Status (4)
Country | Link |
---|---|
US (1) | US7768905B2 (ja) |
EP (1) | EP1599004A4 (ja) |
JP (1) | JP4040628B2 (ja) |
WO (1) | WO2004077781A1 (ja) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2008244849A (ja) * | 2007-03-27 | 2008-10-09 | Ntt Docomo Inc | 通信接続サーバ及び通信接続方法 |
JP2010157225A (ja) * | 2008-12-31 | 2010-07-15 | Nhn Corp | メッセージングネットワークシステムのメッセージ送受信方法 |
JP2014022835A (ja) * | 2012-07-13 | 2014-02-03 | Fujitsu Ltd | 電子装置および送信制御方法 |
Families Citing this family (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7904563B2 (en) * | 2006-03-31 | 2011-03-08 | Microsoft Corporation | Establishing and utilizing terminal server dynamic virtual channels |
US7911830B2 (en) * | 2007-05-17 | 2011-03-22 | Integrated Magnetoelectronics | Scalable nonvolatile memory |
US8429674B2 (en) * | 2010-07-20 | 2013-04-23 | Apple Inc. | Maintaining data states upon forced exit |
CN103092701B (zh) * | 2011-10-31 | 2017-02-08 | 联想(北京)有限公司 | 一种通信方法、装置及电子设备 |
US9172600B1 (en) * | 2013-12-31 | 2015-10-27 | Symantec Corporation | Efficient I/O error analysis and proactive I/O failover to alternate paths for InfiniBand channel |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH10173773A (ja) * | 1996-09-30 | 1998-06-26 | Lucent Technol Inc | 故障した通信リンクからチャネルを回復するためのフレキシブルレートインタフェース(fri)リンクの設定 |
WO2000028715A1 (en) | 1998-11-10 | 2000-05-18 | Honeywell Inc. | Fault-tolerant networking |
JP2002026909A (ja) * | 2000-07-11 | 2002-01-25 | Hitachi Ltd | 回線多重化方法及び情報中継装置 |
JP2002232427A (ja) * | 2001-02-06 | 2002-08-16 | Fujitsu Ltd | 帯域制御装置 |
CA2459027A1 (en) | 2001-06-15 | 2002-12-15 | Tropic Networks Inc. | Extension of link aggregation protocols over the network and a switching node therefor |
Family Cites Families (22)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5182751A (en) * | 1990-12-31 | 1993-01-26 | At&T Bell Laboratories | Switching system using identical switching nodes |
US5862335A (en) * | 1993-04-01 | 1999-01-19 | Intel Corp. | Method and apparatus for monitoring file transfers and logical connections in a computer network |
DE4416719C2 (de) * | 1994-05-11 | 1998-08-20 | Siemens Ag | Schaltungsanordnung zum störungsfreien Umleiten eines Nachrichtenzellenstromes auf einen Ersatzweg |
US6069894A (en) * | 1995-06-12 | 2000-05-30 | Telefonaktiebolaget Lm Ericsson | Enhancement of network operation and performance |
US6246665B1 (en) * | 1995-12-27 | 2001-06-12 | Fujitsu Limited | Method for attending occurrence of failure in an exchange system that exchanges cells having fixed-length, and interface unit and concentrator equipped in the exchange system using the method |
JPH09270793A (ja) * | 1996-04-03 | 1997-10-14 | Sony Corp | 通信制御方法 |
JPH09326810A (ja) | 1996-06-06 | 1997-12-16 | Nippon Denki Ido Tsushin Kk | 障害時のコネクション切り替え方法 |
US5841780A (en) * | 1996-08-29 | 1998-11-24 | Lucent Technologies Inc. | ISDN BRI link restoration without loss of calls |
JPH10320327A (ja) | 1997-03-19 | 1998-12-04 | Fujitsu Ltd | 二重化された通信アダプタの切替方法、切替方式、および切替用プログラムを格納した記録媒体 |
US6314525B1 (en) * | 1997-05-13 | 2001-11-06 | 3Com Corporation | Means for allowing two or more network interface controller cards to appear as one card to an operating system |
US6308281B1 (en) * | 1998-09-02 | 2001-10-23 | International Business Machines Corporation | Virtual client to gateway connection over multiple physical connections |
US6473396B1 (en) * | 1999-01-04 | 2002-10-29 | Cisco Technology, Inc. | Use of logical addresses to implement module redundancy |
US6301254B1 (en) * | 1999-03-15 | 2001-10-09 | Tellabs Operations, Inc. | Virtual path ring protection method and apparatus |
US6763479B1 (en) * | 2000-06-02 | 2004-07-13 | Sun Microsystems, Inc. | High availability networking with alternate pathing failover |
EP1182903A1 (en) * | 2000-08-21 | 2002-02-27 | Lucent Technologies Inc. | Point-to-point protection in point-to-multipoint networks |
US7046619B2 (en) * | 2000-11-07 | 2006-05-16 | Ciena Corporation | Method and system for bi-directional path switched network |
GB2371706B (en) * | 2001-01-30 | 2003-04-23 | 3Com Corp | Link aggregation control for network devices |
US6956824B2 (en) * | 2001-06-14 | 2005-10-18 | Tropic Networks Inc. | Extension of link aggregation protocols over the network |
WO2003021858A1 (en) * | 2001-09-04 | 2003-03-13 | Rumi Sheryar Gonda | Method for supporting sdh/sonet aps on ethernet |
US20030063723A1 (en) * | 2001-09-28 | 2003-04-03 | Derek Booth | Interactive system for managing and remotely connecting customer utility loads |
US7134040B2 (en) * | 2002-04-17 | 2006-11-07 | International Business Machines Corporation | Method, system, and program for selecting a path to a device to use when sending data requests to the device |
US7145865B1 (en) * | 2002-06-26 | 2006-12-05 | Bellsouth Intellectual Property Corp. | Method for moving network elements with minimal network outages in an active ATM network |
-
2003
- 2003-02-27 WO PCT/JP2003/002277 patent/WO2004077781A1/ja active Application Filing
- 2003-02-27 EP EP03707157A patent/EP1599004A4/en not_active Withdrawn
- 2003-02-27 JP JP2004568758A patent/JP4040628B2/ja not_active Expired - Fee Related
-
2005
- 2005-03-23 US US11/087,273 patent/US7768905B2/en not_active Expired - Fee Related
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH10173773A (ja) * | 1996-09-30 | 1998-06-26 | Lucent Technol Inc | 故障した通信リンクからチャネルを回復するためのフレキシブルレートインタフェース(fri)リンクの設定 |
WO2000028715A1 (en) | 1998-11-10 | 2000-05-18 | Honeywell Inc. | Fault-tolerant networking |
JP2002026909A (ja) * | 2000-07-11 | 2002-01-25 | Hitachi Ltd | 回線多重化方法及び情報中継装置 |
JP2002232427A (ja) * | 2001-02-06 | 2002-08-16 | Fujitsu Ltd | 帯域制御装置 |
CA2459027A1 (en) | 2001-06-15 | 2002-12-15 | Tropic Networks Inc. | Extension of link aggregation protocols over the network and a switching node therefor |
Non-Patent Citations (1)
Title |
---|
See also references of EP1599004A4 |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2008244849A (ja) * | 2007-03-27 | 2008-10-09 | Ntt Docomo Inc | 通信接続サーバ及び通信接続方法 |
JP4499757B2 (ja) * | 2007-03-27 | 2010-07-07 | 株式会社エヌ・ティ・ティ・ドコモ | 通信接続サーバ及び通信接続方法 |
JP2010157225A (ja) * | 2008-12-31 | 2010-07-15 | Nhn Corp | メッセージングネットワークシステムのメッセージ送受信方法 |
JP2014022835A (ja) * | 2012-07-13 | 2014-02-03 | Fujitsu Ltd | 電子装置および送信制御方法 |
Also Published As
Publication number | Publication date |
---|---|
JP4040628B2 (ja) | 2008-01-30 |
EP1599004A4 (en) | 2010-04-28 |
US20050180432A1 (en) | 2005-08-18 |
JPWO2004077781A1 (ja) | 2006-06-08 |
EP1599004A1 (en) | 2005-11-23 |
US7768905B2 (en) | 2010-08-03 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN110912780B (zh) | 一种高可用集群检测方法、系统及受控终端 | |
US9749415B2 (en) | Service management roles of processor nodes in distributed node service management | |
US6055568A (en) | Method and apparatus for dynamically configuring a decentralized network of computers | |
US5835481A (en) | Fault tolerant lane system | |
US7792148B2 (en) | Virtual fibre channel over Ethernet switch | |
US9678802B2 (en) | Service management modes of operation in distributed node service management | |
KR20050012130A (ko) | 클러스터형 컴퓨터 시스템의 클러스터 데이터 포트 서비스 | |
US7768905B2 (en) | Program and method for controlling communication | |
KR100279812B1 (ko) | 제1 패킷 라우터에서 제2 패킷 라우터로의 전환을 순조롭게처리하기 위한 장치 및 방법 | |
JP2003099337A (ja) | データ共有装置 | |
JP2008228150A (ja) | スイッチ装置及びフレーム交換方法とそのプログラム | |
EP1535182A1 (en) | Method and structure for autoconfiguration of overlay networks by automatic selection of a network designated router | |
US20140095754A1 (en) | Back-Off Retry with Priority Routing | |
JPH1185644A (ja) | 冗長構成システムの系切替制御方法 | |
US6535991B1 (en) | Method and apparatus for providing reliable communications in an intelligent network | |
CN104660550A (zh) | 一种在多服务器之间进行会话迁移的方法 | |
TW200417261A (en) | An apparatus and method for coupling a network data device to a digital network | |
JP4579850B2 (ja) | ブレード型システムおよびコネクション管理方法 | |
JP4595469B2 (ja) | 接続態様制御装置及び接続態様制御方法並びに接続態様制御用プログラム | |
WO2000033189A1 (en) | Method and apparatus in a data communication system for establishing a reliable internet protocol session | |
EP1547321B1 (en) | Method for determining a parent portal in a wireless network and corresponding portal device | |
WO2006057349A1 (ja) | 管理システム及びそれに用いられる装置と、そのプログラムと、管理方法 | |
JP3102353B2 (ja) | 通信ルート切り戻し制御方式 | |
KR19990053166A (ko) | 멀티포인트 통신 시스템 및 멀티캐스트 경로 오류 제어 및경로 재배정 방법 | |
WO2020177471A1 (zh) | 报文传输方法、装置及存储介质 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): JP US |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PT SE SI SK TR |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
WWE | Wipo information: entry into national phase |
Ref document number: 2004568758 Country of ref document: JP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2003707157 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 11087273 Country of ref document: US |
|
WWP | Wipo information: published in national office |
Ref document number: 2003707157 Country of ref document: EP |