WO2013111285A1 - Appareil de communication, procédé de communication et programme - Google Patents

Appareil de communication, procédé de communication et programme Download PDF

Info

Publication number
WO2013111285A1
WO2013111285A1 PCT/JP2012/051540 JP2012051540W WO2013111285A1 WO 2013111285 A1 WO2013111285 A1 WO 2013111285A1 JP 2012051540 W JP2012051540 W JP 2012051540W WO 2013111285 A1 WO2013111285 A1 WO 2013111285A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
unit
transmission
frame
transmitted
Prior art date
Application number
PCT/JP2012/051540
Other languages
English (en)
Japanese (ja)
Inventor
大介 長川
Original Assignee
三菱電機株式会社
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 三菱電機株式会社 filed Critical 三菱電機株式会社
Priority to PCT/JP2012/051540 priority Critical patent/WO2013111285A1/fr
Publication of WO2013111285A1 publication Critical patent/WO2013111285A1/fr

Links

Images

Classifications

    • 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 data transmission technique.
  • the slave device when the slave device detects the occurrence of a failure in the network, the slave device notifies the master device of the occurrence of the failure.
  • the slave device In the conventional failure notification method, the slave device notifies the master device of the failure by broadcasting a failure notification frame to the entire network (for example, Patent Document 1).
  • the transmission of the failure notification frame is waited until the other communication is completed. Notification is delayed.
  • important data such as a failure notification frame is newly generated during transmission of certain data, until the transmission of the data being transmitted is completed in the conventional method, even if it is important data Since transmission is awaited, there is a problem that transmission of important data is delayed.
  • This invention is mainly intended to solve the above-described problems, and it is a main object to realize a configuration in which new data can be preferentially transmitted even during data transmission.
  • the communication device is A data transmission unit for transmitting data; When new data to be transmitted occurs while the data transmission unit is transmitting data, the data transmission unit determines which of the data being transmitted and the new data has priority, A data arbitration unit that outputs a data switching instruction to instruct data switching to the data transmission unit when giving priority to the new data;
  • the data transmitter is When a data switching instruction is input from the data arbitration unit during data transmission, transmission of the data being transmitted is interrupted and transmission of the new data is started.
  • the data arbitration unit determines which of the data being transmitted and the new data is prioritized by the data transmitting unit, and when giving priority to the new data, the data transmitting unit Is interrupted and transmission of new data is started. For this reason, important data can be transmitted first, and a situation in which transmission of important data is delayed can be avoided.
  • FIG. 1 is a diagram illustrating a configuration example of a communication system according to Embodiment 1.
  • FIG. 3 illustrates a configuration example of a slave device according to the first embodiment.
  • FIG. 3 shows an example of a communication frame according to the first embodiment.
  • FIG. 3 is a flowchart showing an operation example of the slave device according to the first embodiment.
  • FIG. 3 is a flowchart showing an operation example of the slave device according to the first embodiment.
  • FIG. 3 is a flowchart showing an operation example of the slave device according to the first embodiment.
  • FIG. 3 is a diagram illustrating a hardware configuration example of a slave device according to the first embodiment.
  • Embodiment 1 FIG. In the present embodiment, description will be given by taking a tree topology network in which token passing is performed as an example.
  • FIG. 1 illustrates an example of a tree topology network according to the first embodiment.
  • one master device 200 and a plurality of slave devices 100 are connected via a switch 300.
  • the master device 200 and the slave device 100 are collectively referred to as a station or a node.
  • the slave device 100, the master device 200, and the switch 300 relay the received frame to all ports that are not reception ports. Thereby, it is possible to communicate even between nodes that are not adjacent to each other.
  • the slave device 100 corresponds to an example of a communication device.
  • the order in which the tokens are circulated is determined in advance, and the tokens circulate between the master device 200 and the plurality of slave devices 100 according to the circulation order.
  • the node acquires the transmission right by acquiring the token.
  • the master device 200 that has acquired the token makes a request for information collection, data distribution, and the like to the slave device 100 as a master of the tree topology of FIG.
  • the slave device 100 that has acquired the token responds to the master device 200 with the requested data in response to the information collection request from the master device 200. Further, the slave device 100 performs an operation based on the data distributed from the master device 200.
  • each slave device 100 notifies the master device 200 of the failure regardless of the presence or absence of a token.
  • FIG. 2 shows a configuration example of the slave device 100 according to the present embodiment. Note that the plurality of slave devices 100 shown in FIG. 1 each have the configuration shown in FIG.
  • the failure detection unit 101 includes, for example, the own station, the master device 200 and the slave device 100 adjacent to the own station, and the communication line between the master device 200 and the slave device 100 adjacent to the own station and the own station.
  • a failure notification frame for notifying the occurrence of a failure is generated when a failure detection target is detected and a failure has occurred in the failure detection target.
  • the normal frame generation unit 102 generates a normal frame related to normal operation other than the failure notification frame transmitted from the own station.
  • the normal frame is a frame for making a response to an information collection request from the master device 200, for example.
  • the failure detection unit 101 and the normal frame generation unit 102 correspond to an example of a data generation unit.
  • the transmission arbitration unit 103 includes a data reception unit 104, a data transmission unit 105, and a data arbitration unit 106.
  • the data receiving unit 104 inputs a reception frame from an adjacent other station (which may be either the master device 200 or the slave device 100).
  • the data receiving unit 104 may receive a normal frame or a failure notification frame.
  • the data transmission unit 105 transmits a frame to another station (which may be either the master device 200 or the slave device 100) adjacent to the side opposite to the input side.
  • the data transmission unit 105 may transmit a normal frame or a failure notification frame. Further, when transmitting a normal frame, the data transmission unit 105 stores the normal frame to be transmitted in a retransmission frame buffer 107 described later in parallel with the transmission.
  • the data arbitration unit 106 receives the reception frame (normal frame, failure notification frame) received by the data reception unit 104, receives the failure notification frame generated by the failure detection unit 101, and the normal frame generated by the normal frame generation unit 102 The frame is input, and the input normal frame and failure notification frame are output to the data transmission unit 105. Then, when a new failure notification frame occurs while the data transmission unit 105 is transmitting a normal frame (when a new failure notification frame is input from the data reception unit 104, the data arbitration unit 106 The data transmission unit 105 is instructed to transmit the failure notification frame to another station in preference to the normal frame in both cases when a failure notification frame is newly input from 101. More specifically, the data arbitration unit 106 outputs, to the data transmission unit 105, a data switching instruction that instructs to switch from a normal frame to a failure notification frame for transmission.
  • the retransmission frame buffer 107 buffers the normal frame transmitted by the data transmission unit 105.
  • the retransmission frame buffer 107 corresponds to an example of a buffer unit.
  • FIG. 3 shows an example of the data structure of a communication frame 500 used as a normal frame or a failure notification frame communicated in the tree topology according to the present embodiment.
  • a header 501 is provided in the communication frame 500.
  • the header 501 is a data area in the communication frame 500 for identifying a failure notification frame and a normal frame.
  • the data transmission unit 105 and the data arbitration unit 106 can identify the failure notification frame and the normal frame by confirming the contents of the header 501.
  • the communication frame 500 is also simply referred to as a frame.
  • the failure detection unit 101 detects that a failure has occurred in the failure detection object.
  • the detected failure includes, for example, a failure in the own station (such as a data error in the memory), a network failure between the adjacent master device 200 and the slave device 100 (cable disconnection, unreachable frame to be reached) Etc.).
  • the failure detection unit 101 generates a failure notification frame and outputs it to the transmission arbitration unit 103.
  • the normal frame generation unit 102 generates a normal frame to be transmitted from the own station and outputs the normal frame to the transmission arbitration unit 103.
  • the data arbitration unit 106 receives the failure notification frame from the failure detection unit 101 and the normal frame from the normal frame generation unit 102.
  • the data reception unit 104 in the transmission arbitration unit 103 receives a frame (a failure notification frame and a normal frame are mixed) from another station, and outputs the received frame to the data arbitration unit 106.
  • the data arbitration unit 106 and the data transmission unit 105 can classify the input frame into a failure notification frame and a normal frame based on the difference in the header 501. Then, the data arbitration unit 106 and the data transmission unit 105 transmit the failure notification frame with priority. Further, when transmitting a normal frame, the data transmission unit 105 stores the normal frame to be transmitted in the retransmission frame buffer 107 in parallel with the transmission.
  • the data arbitration unit 106 receives a failure notification frame from the failure detection unit 101 or the data reception unit 104 while the data transmission unit 105 is transmitting a normal frame to another station, the data arbitration unit 106 The unit 105 causes the transmission of the normal frame to be interrupted and starts the transmission of the failure notification frame. Then, when the transmission of the failure notification frame is completed, the data transmission unit 105 reads the normal frame whose transmission is interrupted from the retransmission frame buffer 107, and resumes the transmission of the normal frame.
  • the data arbitration unit 106 confirms whether or not the data transmission unit 105 is transmitting a frame. For example, a flag indicating whether or not the data transmission unit 105 is transmitting a frame (hereinafter referred to as a transmission flag) is provided in a predetermined memory in the slave device 100, and the data transmission unit 105 transmits a frame. The transmission flag is set to ON when it starts, and the transmission flag is set to OFF when frame transmission is completed. Then, the data arbitration unit 106 refers to the transmission flag and determines whether the data transmission unit 105 is transmitting a frame.
  • a transmission flag indicating whether or not the data transmission unit 105 is transmitting a frame
  • the data arbitration unit 106 checks whether the frame being transmitted by the data transmission unit 105 is a received frame (a failure notification frame from another station or a normal frame from another station). .
  • a flag hereinafter referred to as a reception frame flag
  • the data arbitration unit 106 refers to the reception frame flag to determine whether or not the frame being transmitted by the data transmission unit 105 is a reception frame.
  • the data transmission unit 105 can determine whether the transmission source of the frame is another station or the own station by referring to the transmission source address in the header 501 of the frame.
  • the failure detection unit 101 confirms whether or not to generate a failure notification frame.
  • the failure detection unit 101 In the case of YES in S ⁇ b> 103, in S ⁇ b> 104, the failure detection unit 101 generates a failure notification frame and outputs it to the transmission arbitration unit 103. In the transmission arbitration unit 103, the data arbitration unit 106 inputs a failure notification frame.
  • the data arbitration unit 106 confirms whether the frame being transmitted is a received frame and is a normal frame. For example, in addition to the above-described frame transmission flag and reception frame flag, a flag (hereinafter referred to as a frame type flag) indicating whether the frame being transmitted by the data transmission unit 105 is a normal frame is provided, and the data transmission unit 105, the frame type flag is turned on when the frame being transmitted is a normal frame, and the frame type flag is turned off when the frame being transmitted is a failure notification frame. Then, the data arbitration unit 106 refers to the frame type flag to determine whether or not the received frame being transmitted by the data transmission unit 105 is a normal frame. As described above, the data transmission unit 105 can determine whether the frame is a normal frame or a failure notification frame by referring to the frame header 501.
  • a flag hereinafter referred to as a frame type flag
  • the data arbitration unit 106 determines to prioritize transmission of the failure notification frame, and the data arbitration unit 106 outputs a data switching instruction and a failure notification frame to the data transmission unit 105. . That is, the data arbitration unit 106 interrupts transmission of a normal frame that is a received frame, and transmits the failure notification frame generated by the failure detection unit 101 of the local station to the master device 200 via another station. To instruct. Then, the data transmission unit 105 interrupts transmission of the normal frame being transmitted, and starts transmitting the failure notification frame generated by the failure detection unit 101 of the local station (S106).
  • the data transmission unit 105 interrupts transmission of the normal frame being transmitted, but continues to store the normal frame in the retransmission frame buffer 107, and stores the normal frame in the retransmission frame buffer 107 and the failure notification frame. Send in parallel. Thereafter, after the transmission of the failure notification frame is completed, the data transmission unit 105 reads the normal frame whose transmission is interrupted from the retransmission frame buffer 107 and transmits the read normal frame to another adjacent station (S106).
  • the failure notification frame generated by the failure detection unit 101 of the local station is referred to as a failure notification frame (transmission), and the normal frame generated by the normal frame generation unit 102 of the local station is represented.
  • the normal frame (transmission) is denoted
  • the failure notification frame received from another station is denoted as a failure notification frame (reception)
  • the normal frame received from another station is denoted as a normal frame (reception).
  • the data arbitration unit 106 sends the failure detection frame input from the failure detection unit 101 to the data transmission unit 105.
  • the data transmission unit 105 outputs the failure notification frame received from the other station, and then transmits the failure notification frame generated by the failure detection unit 101 of the local station to the master device 200 via the adjacent other station.
  • the normal frame generation unit 102 confirms whether or not to generate a normal frame in S108. If YES, the normal frame generation unit 102 transmits the generated normal frame in S109. Output to the arbitration unit 103.
  • the data arbitration unit 106 inputs the normal frame from the normal frame generation unit 102 and outputs the input normal frame to the data transmission unit 105.
  • the data transmission unit 105 transmits the normal frame generated by the normal frame generation unit 102 of the local station after completing the transmission of the received frame (failure notification frame from the other station or normal frame from the other station) (S110). .
  • the transmission arbitration unit 103 confirms whether or not a received frame has been detected. That is, the data arbitration unit 106 confirms whether or not a reception frame is input from the data reception unit 104.
  • the data arbitration unit 106 checks whether or not the frame being transmitted by the data transmission unit 105 is a normal frame. For example, the data arbitration unit 106 refers to the above-described frame type flag to determine whether or not the frame being transmitted by the data transmission unit 105 is a normal frame.
  • the data arbitration unit 106 checks whether the received frame input from the data receiving unit 104 is a failure notification frame. Specifically, the data arbitration unit 106 confirms the header 501 of the received frame and confirms whether or not the received frame is a failure notification frame.
  • the data arbitration unit 106 determines to give priority to the transmission of the failure notification frame.
  • the data arbitration unit 106 instructs the data transmission unit 105 to perform a data switching instruction and a failure notification from another station. Frame and output. That is, the data arbitration unit 106 interrupts transmission of the normal frame generated by the normal frame generation unit 102 of the local station, and transmits the failure notification frame from the other station to the master device 200 via the other station. To instruct. Then, the data transmission unit 105 interrupts transmission of the normal frame being transmitted and starts transmission of a failure notification frame from another station (S114).
  • the data transmission unit 105 interrupts transmission of the normal frame being transmitted, but continues to store the normal frame in the retransmission frame buffer 107, and stores the normal frame in the retransmission frame buffer 107 and the failure notification frame. Send in parallel. Thereafter, after the transmission of the failure notification frame is completed, the data transmission unit 105 reads the normal frame whose transmission is interrupted from the retransmission frame buffer 107 and transmits the read normal frame to another adjacent station (S106).
  • the data arbitration unit 106 outputs the normal frame from the other station to the data transmission unit 105, and the data transmission unit 105 generates the normal frame generated by the normal frame generation unit 102 of its own station. After the frame is transmitted, a received frame (a normal frame from another station) is transmitted. At this time, the data transmission unit 105 stores the normal frame to be transmitted in the retransmission frame buffer 107 in parallel with the transmission.
  • the data arbitration unit 106 checks whether the received frame input from the data receiving unit 104 is a failure notification frame. Specifically, the data arbitration unit 106 confirms the header 501 of the received frame and confirms whether or not the received frame is a failure notification frame.
  • the data arbitration unit 106 outputs the failure notification frame from the other station to the data transmission unit 105, and the data transmission unit 105 transmits the failure notification frame of the local station to the other station. A failure notification frame from is transmitted.
  • the data arbitration unit 106 outputs the normal frame from the other station to the data transmission unit 105, and the data transmission unit 105 receives the failure notification frame of the local station from the other station.
  • the normal frame is transmitted.
  • the data transmission unit 105 stores the normal frame to be transmitted in the retransmission frame buffer 107 in parallel with the transmission.
  • the transmission arbitration unit 103 confirms whether or not a received frame has been detected. That is, the data arbitration unit 106 confirms whether or not a reception frame is input from the data reception unit 104.
  • the data arbitration unit 106 confirms whether or not the received frame input from the data receiving unit 104 is a failure notification frame. Specifically, the data arbitration unit 106 confirms the header 501 of the received frame and confirms whether or not the received frame is a failure notification frame.
  • the data arbitration unit 106 outputs the failure notification frame from the other station to the data transmission unit 105, and the data transmission unit 105 receives the failure notification frame from the other station as an adjacent station. To the master device 200.
  • the data arbitration unit 106 outputs the normal frame from the other station to the data transmission unit 105, and the data transmission unit 105 sends the normal frame from the other station to the adjacent other station. Send. Further, the data transmission unit 105 stores normal frames from other stations in the retransmission frame buffer 107 in parallel with the transmission.
  • the failure detection unit 101 confirms whether or not to generate a failure notification frame.
  • the failure detection unit 101 If YES in S123, the failure detection unit 101 generates a failure notification frame and outputs it to the transmission arbitration unit 103 in S124.
  • the data arbitration unit 106 receives the failure detection frame from the failure detection unit 101 and outputs the input failure detection frame to the data transmission unit 105.
  • the data transmission unit 105 transmits the failure notification frame generated by the failure detection unit 101 of the local station to the master device 200 via the adjacent station.
  • the normal frame generation unit 102 confirms whether or not to generate a normal frame in S126. If YES, the normal frame generation unit 102 transmits the generated normal frame in S127. Output to the arbitration unit 103.
  • the data arbitration unit 106 inputs the normal frame from the normal frame generation unit 102 and outputs the input normal frame to the data transmission unit 105.
  • the data transmission unit 105 transmits the normal frame generated by the normal frame generation unit 102 of the local station to another station. At this time, the data transmission unit 105 stores the normal frame to be transmitted in the retransmission frame buffer 107 in parallel with the transmission.
  • the failure notification frame is transmitted by overtaking the normal frame. Therefore, the failure notification is not delayed due to the transmission of the normal frame.
  • the master device that has received the failure notification can quickly stop the operation of each station, thereby preventing the influence (malfunction of the device, physical harm to the human body, etc.) due to the malfunction of the device.
  • the data handled by the data transmission unit 105 and the data arbitration unit 106 is not limited to the combination of the normal frame and the failure notification frame, and may be any data. That is, when new data to be transmitted occurs while the data transmission unit 105 is transmitting any data, the data arbitration unit 106 determines whether the data transmission unit 105 transmits the data being transmitted to the new data. When it is determined which is prioritized and new data is prioritized, a data switching instruction for instructing data switching is output to the data transmission unit 105. When the data transmission unit 105 receives a data switching instruction from the data arbitration unit 106 during data transmission, the data transmission unit 105 interrupts transmission of the data being transmitted and starts transmission of new data.
  • CSMA / CD Carrier Sense Multiple Access Collision Detection
  • the communication device including the following means has been described.
  • A means for identifying the type of frame;
  • B means for buffering the frame being transmitted;
  • C Means for interrupting frame transmission and starting transmission of another frame.
  • FIG. 7 is a diagram illustrating an example of hardware resources of the slave device 100 illustrated in the present embodiment.
  • the configuration in FIG. 7 is merely an example of the hardware configuration of the slave device 100, and the hardware configuration of the slave device 100 is not limited to the configuration illustrated in FIG. .
  • the slave device 100 includes a CPU 911 (also referred to as a central processing unit, a central processing unit, a processing unit, an arithmetic unit, a microprocessor, a microcomputer, and a processor) that executes a program.
  • the CPU 911 is connected to, for example, a ROM (Read Only Memory) 913, a RAM (Random Access Memory) 914, a communication board 915, a display device 901, a keyboard 902, a mouse 903, and a magnetic disk device 920 via a bus 912. Control hardware devices.
  • the CPU 911 may be connected to an FDD 904 (Flexible Disk Drive), a compact disk device 905 (CDD), a printer device 906, and a scanner device 907.
  • FDD 904 Flexible Disk Drive
  • CDD compact disk device
  • printer device 906 printer device 907
  • a storage device such as an SSD (Solid State Drive), an optical disk device, or a memory card (registered trademark) read / write device may be used.
  • the RAM 914 is an example of a volatile memory.
  • the storage media of the ROM 913, the FDD 904, the CDD 905, and the magnetic disk device 920 are an example of a nonvolatile memory. These are examples of the storage device.
  • the “retransmission frame buffer 107” described in the present embodiment is realized by the RAM 914, the magnetic disk device 920, and the like.
  • a communication board 915, a keyboard 902, a mouse 903, a scanner device 907, and the like are examples of input devices.
  • the communication board 915, the display device 901, the printer device 906, and the like are examples of output devices.
  • the communication board 915 is connected to a network.
  • the communication board 915 is connected to a LAN (local area network), the Internet, a WAN (wide area network), a SAN (storage area network), and the like.
  • the magnetic disk device 920 stores an operating system 921 (OS), a window system 922, a program group 923, and a file group 924.
  • the programs in the program group 923 are executed by the CPU 911 using the operating system 921 and the window system 922.
  • the RAM 914 temporarily stores at least part of the operating system 921 program and application programs to be executed by the CPU 911.
  • the RAM 914 stores various data necessary for processing by the CPU 911.
  • the ROM 913 stores a BIOS (Basic Input Output System) program
  • the magnetic disk device 920 stores a boot program.
  • BIOS Basic Input Output System
  • the BIOS program in the ROM 913 and the boot program in the magnetic disk device 920 are executed, and the operating system 921 is activated by the BIOS program and the boot program.
  • the program group 923 stores programs that execute the functions described as “ ⁇ units” in the description of the present embodiment.
  • the program is read and executed by the CPU 911.
  • the file group 924 includes “determination of”, “detection of”, “determination of”, “evaluation of”, “determination of”, “selection of”, Information, data, signal values, variable values, encryption keys / decryption keys, random values and parameters indicating the results of the processing described as “input of”, “output of”, etc. It is stored as each item of “Database”.
  • the “ ⁇ file” and “ ⁇ database” are stored in a storage medium such as a disk or memory.
  • Information, data, signal values, variable values, and parameters stored in a storage medium such as a disk or memory are read out to the main memory or cache memory by the CPU 911 via a read / write circuit.
  • the read information, data, signal value, variable value, and parameter are used for CPU operations such as extraction, search, reference, comparison, calculation, calculation, processing, editing, output, printing, and display.
  • Information, data, signal values, variable values, and parameters are stored in the main memory, registers, cache memory, and buffers during the CPU operations of extraction, search, reference, comparison, calculation, processing, editing, output, printing, and display. It is temporarily stored in a memory or the like.
  • the arrows in the flowchart described in this embodiment mainly indicate input / output of data and signals.
  • Data and signal values are recorded in a storage medium such as a memory of the RAM 914, a flexible disk of the FDD 904, a compact disk of the CDD 905, a magnetic disk of the magnetic disk device 920, other optical disks, mini disks, and DVDs.
  • Data and signals are transmitted online via a bus 912, signal lines, cables, or other transmission media.
  • Firmware and software are stored as programs in a storage medium such as a magnetic disk, a flexible disk, an optical disk, a compact disk, a mini disk, and a DVD.
  • the program is read by the CPU 911 and executed by the CPU 911.
  • the program causes the computer to function as “to part” and “to means” in the present embodiment.
  • the procedures and methods of “ ⁇ unit” and “ ⁇ means” of the present embodiment are executed by a computer.
  • the slave device 100 described in this embodiment includes a CPU that is a processing device, a memory that is a storage device, a magnetic disk, a keyboard that is an input device, a mouse, a communication board, and a display device that is an output device, a communication board, and the like.
  • a CPU that is a processing device
  • a memory that is a storage device
  • a magnetic disk that is a storage device
  • a keyboard that is an input device
  • a mouse a communication board
  • a display device that is an output device, a communication board, and the like.
  • Computer As described above, the functions indicated as “ ⁇ unit” and “ ⁇ means” are realized by using these processing devices, storage devices, input devices, and output devices.
  • 100 slave device 101 failure detection unit, 102 normal frame generation unit, 103 transmission arbitration unit, 104 data reception unit, 105 data transmission unit, 106 data arbitration unit, 107 retransmission frame buffer, 200 master device, 300 switch.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Small-Scale Networks (AREA)

Abstract

Si la transmission de nouvelles données survient pendant qu'une unité de transmission de données (105) est en cours de transmission de données, une unité d'arbitrage de données (106) détermine si la priorité est donnée aux données en cours de transmission par l'unité de transmission de données (105) ou aux nouvelles données. Si la priorité est donnée aux nouvelles données, l'unité d'arbitrage de données (106) fournit, à l'unité de transmission de données, une instruction de changement de données qui ordonne un changement de données. Lorsqu'elle a reçu l'instruction de changement de données de la part de l'unité d'arbitrage de données (106) pendant la transmission de données, l'unité de transmission de données (105) suspend la transmission des données en cours de transmission et commence la transmission des nouvelles données.
PCT/JP2012/051540 2012-01-25 2012-01-25 Appareil de communication, procédé de communication et programme WO2013111285A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/JP2012/051540 WO2013111285A1 (fr) 2012-01-25 2012-01-25 Appareil de communication, procédé de communication et programme

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2012/051540 WO2013111285A1 (fr) 2012-01-25 2012-01-25 Appareil de communication, procédé de communication et programme

Publications (1)

Publication Number Publication Date
WO2013111285A1 true WO2013111285A1 (fr) 2013-08-01

Family

ID=48873056

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2012/051540 WO2013111285A1 (fr) 2012-01-25 2012-01-25 Appareil de communication, procédé de communication et programme

Country Status (1)

Country Link
WO (1) WO2013111285A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015163094A1 (fr) * 2014-04-23 2015-10-29 三菱電機株式会社 Dispositif de relais et procédé de transfert de données
TWI561042B (fr) * 2015-02-20 2016-12-01 Mitsubishi Electric Corp
CN109496408A (zh) * 2016-07-28 2019-03-19 三菱电机株式会社 传送装置和帧传送方法

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2006279188A (ja) * 2005-03-28 2006-10-12 Nec Corp 優先制御を行う送信制御装置、通信制御装置、通信システム、通信ネットワーク、及び送信方法
JP2008236266A (ja) * 2007-03-19 2008-10-02 Fujitsu Ltd 伝送装置、保守用フレーム処理方法および伝送プログラム
JP2009267822A (ja) * 2008-04-25 2009-11-12 Mitsubishi Electric Corp 通信装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2006279188A (ja) * 2005-03-28 2006-10-12 Nec Corp 優先制御を行う送信制御装置、通信制御装置、通信システム、通信ネットワーク、及び送信方法
JP2008236266A (ja) * 2007-03-19 2008-10-02 Fujitsu Ltd 伝送装置、保守用フレーム処理方法および伝送プログラム
JP2009267822A (ja) * 2008-04-25 2009-11-12 Mitsubishi Electric Corp 通信装置

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015163094A1 (fr) * 2014-04-23 2015-10-29 三菱電機株式会社 Dispositif de relais et procédé de transfert de données
KR20160135329A (ko) * 2014-04-23 2016-11-25 미쓰비시덴키 가부시키가이샤 중계 장치 및 데이터 전송 방법
CN106233670A (zh) * 2014-04-23 2016-12-14 三菱电机株式会社 中继装置以及数据传送方法
JPWO2015163094A1 (ja) * 2014-04-23 2017-04-13 三菱電機株式会社 中継装置およびデータ転送方法
KR101960147B1 (ko) * 2014-04-23 2019-03-19 미쓰비시덴키 가부시키가이샤 중계 장치 및 데이터 전송 방법
US10523579B2 (en) 2014-04-23 2019-12-31 Mitsubishi Electric Corporation Relay device and data transfer method
CN106233670B (zh) * 2014-04-23 2020-01-03 三菱电机株式会社 中继装置以及数据传送方法
TWI561042B (fr) * 2015-02-20 2016-12-01 Mitsubishi Electric Corp
CN107251516A (zh) * 2015-02-20 2017-10-13 三菱电机株式会社 通信装置、通信方法及程序
CN109496408A (zh) * 2016-07-28 2019-03-19 三菱电机株式会社 传送装置和帧传送方法
CN109496408B (zh) * 2016-07-28 2021-03-12 三菱电机株式会社 传送装置和帧传送方法

Similar Documents

Publication Publication Date Title
US11599349B2 (en) Gateway device, in-vehicle network system, and firmware update method
US20110125949A1 (en) Routing packet from first virtual machine to second virtual machine of a computing device
US11842185B2 (en) Gateway device, in-vehicle network system, and firmware update method
US10810036B1 (en) Traffic management on an interconnect
US10116506B2 (en) Method for upgrading version of network device and network device
EP2704009B1 (fr) Appareil de traitement d' informations, procédé et programme de traitement d' informations
JP2011070655A (ja) 情報処理装置、メモリダンプシステムおよびメモリダンプ方法
JP6183931B2 (ja) クラスタシステム、サーバ装置、クラスタシステムの管理方法、及びプログラム。
WO2013111285A1 (fr) Appareil de communication, procédé de communication et programme
US9304955B2 (en) Techniques for identifying and handling processor interrupts
US10909270B2 (en) Information processing device, mobile object, information processing method, and computer program product
US9081614B2 (en) Managing shared resources in a multi-computer system with failover support
JP6365280B2 (ja) 情報処理装置、情報処理システム、及びプログラム
US8806082B2 (en) Direct memory access device for multi-core system and operating method of the same
US11711380B2 (en) Systems and methods for parallel virus and malware scan between agents in a cloud environment
US9798601B2 (en) Connection method
CN112052200A (zh) 信息处理装置、信息处理系统以及存储介质
US8380938B2 (en) Providing shared access to data storage resources across cluster computing environment boundaries
US20160020984A1 (en) Information processing apparatus, method, and system, and non-transitory computer readable medium
US10339076B2 (en) System and method for adaptable fabric consistency validation and issue mitigation in an information handling system
US8930586B2 (en) Identification of electronic devices operating within a computing system
JP5763030B2 (ja) 二重化ネットワーク制御システムおよび二重化ネットワーク制御方法
JP2019164621A (ja) 起動制御ユニット、制御システムおよび起動制御方法
EP4092969A1 (fr) Surveillance des noeuds xl d'un réseau de zone de contrôleur (can)
US20180145875A1 (en) Information processing device

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 12866778

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 12866778

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: JP