EP0461674A2 - Système de communication et dispositifs de communication avec verrouillage - Google Patents

Système de communication et dispositifs de communication avec verrouillage Download PDF

Info

Publication number
EP0461674A2
EP0461674A2 EP91109818A EP91109818A EP0461674A2 EP 0461674 A2 EP0461674 A2 EP 0461674A2 EP 91109818 A EP91109818 A EP 91109818A EP 91109818 A EP91109818 A EP 91109818A EP 0461674 A2 EP0461674 A2 EP 0461674A2
Authority
EP
European Patent Office
Prior art keywords
communication device
communication
data
slave
master
Prior art date
Legal status (The legal status 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 status listed.)
Granted
Application number
EP91109818A
Other languages
German (de)
English (en)
Other versions
EP0461674B1 (fr
EP0461674A3 (en
Inventor
Izumi Ohshima
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
NEC Electronics Corp
Original Assignee
NEC Corp
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 NEC Corp filed Critical NEC Corp
Publication of EP0461674A2 publication Critical patent/EP0461674A2/fr
Publication of EP0461674A3 publication Critical patent/EP0461674A3/en
Application granted granted Critical
Publication of EP0461674B1 publication Critical patent/EP0461674B1/fr
Anticipated expiration legal-status Critical
Expired - Lifetime legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/40—Bus networks
    • H04L12/40006—Architecture of a communication node
    • H04L12/40013—Details regarding a bus controller
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/40—Bus networks
    • H04L12/407—Bus networks with decentralised control
    • H04L12/413—Bus networks with decentralised control with random access, e.g. carrier-sense multiple-access with collision detection [CSMA-CD]
    • H04L12/4135—Bus networks with decentralised control with random access, e.g. carrier-sense multiple-access with collision detection [CSMA-CD] using bit-wise arbitration

Definitions

  • the present invention relates to a communication system for transmitting a message or data using a communication packet and, more particularly, to a communication device having a lock function of responding to only the communication packet sent from a specific communication device and a communication system using it.
  • a domestic digital bus which is a data bus between household audio/video devices
  • D2B domestic digital bus
  • an example of the patent which relates to such communication system is an European Patent Application No. EP 0333269.
  • FIG. 1 An arrangement of the D2B communication system including a plurality of communication devices is shown in Fig. 1.
  • the communication system is composed of a transmission or transfer path 70 and a plurality of communication devices 71a, 71b, 71c, ... connected with the transmission path 70.
  • each of the communication devices 71a, 71b, 71c, ... has a function serving as a master device capable of independently executing a communication (that is, "a multi-master function").
  • the communication device as a master will send out a communication packet described below to the transmission path 70.
  • Another device which has been designated as a communication partner by the communication packet will serve as a slave receiving this communication packet.
  • the format of the communication packet used in the D2B communication system is shown in Fig. 2. As shown in Fig. 2, the communication packet is composed of a header 80, a master address field 81, a slave address field 82, a control field 83 and a data field 84.
  • the header 80 is composed of start bits 85 indicative of sending a communication packet and mode bits 86 indicative of either one of three kinds of modes (modes 0, 1 and 2) with different transfer speeds.
  • the master address field 81 is composed of master address bits 87 indicative of the address of the communication device serving as a master and a parity bit 88.
  • the slave address field 82 is composed of slave address bits 89 indicative of the address of a slave communication device which is a communication partner of the master communication device, a parity bit 90 and an acknowledge bit 91 for acknowledging right reception of the communication packet by the slave communication device.
  • the control field 83 is composed of control bits 92 described below, a parity bit 93, and an acknowledge bit 94.
  • control bits 92 are a control code indicative of the transfer direction and contents of communication data, and lock setting or lock releasing.
  • the control bits of requesting data write in a slave communication device and setting lock is referred to as "Bh”
  • that of requesting data write and releasing lock is referred to as "Fh”
  • that of requesting reading the status from the slave communication device is referred to as "6h”.
  • the data field 84 is composed of repetition of basic unit data 99 which includes 1(one) byte data bits 95, an end-of-data bit 96 indicative of an end of the communication data, a parity bit 97 and an acknowledge bit 98.
  • a message will be transferred acknowledging that it has been received by a receiving communication device for each one byte data based on the basic unit data 99. If the one byte data have not been received and hence the acknowledge bit has not been sent back, the same one byte data will be transferred again.
  • the maximum number of times of repetition of the basic data unit 99 is determined in accordance with the communication mode (mode 0, 1, or 2) defined by the mode bits 86. For example, it is 32 in the case of mode 1. Therefore, in the case of mode 1, the data up to 32 bytes can be transferred using one communication packet.
  • unlocking releasing the locking (hereinafter referred to as "unlocking") of the slave communication device will be performed using the control bits 92 of requesting unlocking in the case where the communication packet the acknowledge bit of which has been sent back owing to successful transfer of at least one byte data within the data field 84 has been exchanged between the master communication device and the slave communication device concerned.
  • Fig. 3 shows a combination of communication packets in transferring a message of 40 bytes in communication mode 1 from the communication device 71a as a master in Fig. 1 to the communication device 71b as a slave. It should be noted that in the communication as shown in Fig. 3, three communication packets are transferred from the communication device 71a to the communication device 71b.
  • the first transferring method will be explained.
  • control bits 92 are set for "Bh" (data write and locking) to request locking and transfer 32 byte data which can be transferred in mode 1. Now, it is assumed that the 32 byte data have been transferred satisfactorily. Since this means that the data of one byte or more have been transferred satisfactorily, the slave communication device 71b will be locked by the master communication device 71a.
  • the control bits 92 are set for "Bh" (data write and locking) to request locking and transfer the remaining 8 byte data to be added to the 32 byte data which have already been transferred using the first communication packet 100.
  • the communication device 71b since the communication device 71b has already been locked, it remains locked regardless of the communication result, i.e., whether the remaining 8 byte data have been completely transferred or even one byte data has not been transferred.
  • the second communication packet 101 does not set the control bits 92 for "Fh" (data write and unlocking) which is a code requesting release of locking. This is because it is not guaranteed that the second communication packet can surely transfer the remaining 8 byte data.
  • the second communication packet 101 may be able to transfer only one byte corresponding to the size of the buffer. In this case, although 7 bytes to be transferred remain, the communication device 71b will be unlocked.
  • control bits 92 are set for "6h" (read of slave status and unlocking) to read one byte slave status from the slave communication device 71b.
  • the communication device 71b will be unlocked.
  • the control bits 92 are set for "Bh" to request locking and transfer 7 byte data which is lesser by one byte than the remainder (8 bytes) of the message to be added to the 32 byte data transferred using the first communication packet 100.
  • the control bits 92 are bet for "Fh" (data write and unlocking) to request unlocking and transfer the remaining one byte data. When this last one byte data has been successfully transferred, the communication device 71b will be unlocked.
  • the communication device serving as a master can transfer data to the slave communication device without being disturbed by other communication devices. Further, since the slave communication device does not accept or receive the communication packet from any communication device other than a specific communication device, communication data over a number of communication packets can be formed as one message.
  • the communication system has the following disadvantage.
  • one communication packet is required for the purpose of locking/unlocking so that one redundant communication packet must be transferred.
  • 40 byte data which can be transferred using two communication packets in the mode 1
  • at least three communication packets are required. This makes the transfer efficiency inferior.
  • the master communication device since the values of the control bits set for locking and unlocking are different, the master communication device must construct the communication packets by taking into account the locking of the slave communication device, thus making the processing required complicate.
  • a communication system comprising a transmission path, at least one master communication device capable of executing a communication, and at least one slave communication device to be a communication partner to the master communication device for performing data transfer therebetween using communication packets, wherein each of the communication packets includes control bits which are information relating to locking of the slave communication device and data length bits indicative of the size of a message to be transferred, and wherein in transmitting the communication packets from the master communication device to the slave communication device, the slave communication device is locked when locking is designated by the control bits and is unlocked when a message having a data length specified by the data length bits has been transferred successfully.
  • Fig. 4 shows the format of the communication packet for data transfer used in the communication system according to the present invention.
  • the communication packet is composed of a header 1, a master address field 2, a slave address field 3, a control field 4, a data length field 5 and a data field 6.
  • the header 1 is composed of start bits 10 indicative of transmission of a communication packet and a broadcasting bits 11 for selecting individual communication or broadcasting communication.
  • the master address field 2 is composed of master address bits 12 and a parity bit 13, the master address bits 12 being indicative of the address of a master communication device mainly executing a communication.
  • the slave address field 3 is composed of slave address bits 14 indicative of the address of a slave communication device which is a communication partner of the master communication device, a parity bit 15 and an acknowledge bit 16 for acknowledging right reception of the communication packet by the slave communication device.
  • the control field 4 is composed of control bits 17 indicative of control information for data to be transferred, a parity bit 18, and an acknowledge bit 19.
  • TABLE 1 shows the contents of the control bits 17.
  • control bits 17 are a 4-bit code consisting of the direction of transferring a message, the contents of the message and the information relating to locking.
  • the transfer direction of a message is defined by the most significant bit MSB (i.e., bit 3) of the control bits 17. If the MSB is "1”, the message will be transferred from a master communication device to a slave communication device ("WRITE"). If the MSB is "0", the message will be transferred from the slave communication device to the master communication device ("READ").
  • the contents of the message include reading of slave status, data and a lock address, and writing of a command and data.
  • the code relating to locking the slave communication device includes "3h", "Ah” and "Bh".
  • the acknowledge bit 17 is sent back from the slave communication device only when the control bits 17 transferred from the master communication device can be rightly processed. For example, in the case where the MSB (bit 3) of the control bits 17 is "1", the slave communication device will not send back the acknowledge bit 17 unless its buffer for data reception is vacant.
  • the data length field 5 is composed of the data length bits 20 indicative of the size of a message, a parity bit 21 and an acknowledge bit 22.
  • the data field is composed of repetition of basic unit data 26 which includes 1(one) byte data bits 23 indicative of a message, a parity bit 24 and an acknowledge bit 25.
  • the message will be transferred acknowledging that it has been received by a receiving communication device for each one byte data based on the basic unit data 26. If the one byte data have not been received and hence the acknowledge bit has not been sent back, the same one byte data will be transferred again.
  • the maximum number of times of repetition of the basic data unit 26 is 32 so that the data will be transferred within this number of times. Therefore, the data up to 32 bytes can be transferred using one communication packet.
  • Fig. 5 is a block diagram of an arrangement of the communication system according to the present invention. As shown in Fig. 5, the communication system is composed of a transmission path 30 and a plurality of communication devices 31a, 31b, 31c, ... .
  • the communication device 31a is composed of an input and output (I/O) terminal 32 for the transmission path 30, a receiving unit 33, a data link controller 34, a control unit 35, a receiving buffer 36, a transmission buffer 37, a lock status unit 38 and a transmission unit 39.
  • the I/O terminal 32 is connected with the input of the receiving unit 33 and the output of the transmission unit 39.
  • the output of the receiving unit 33 is connected with the input of the data link controller 34.
  • the first output terminal of the data link controller 34 is connected with the control unit 35 and the second output terminal thereof is connected with the input of the receiving buffer 36.
  • the input/output terminal of the data link controller 34 is connected with the input/output terminal of the lock status unit 38.
  • the first output terminal of the control unit 35 is connected with the input of the data link controller 34 and its second output is connected with the input of the transmission buffer 37.
  • the output of the receiving buffer 36 is connected with the input of the control unit 35.
  • the output of the transmission buffer 37 is connected with the input of the data link controller 34.
  • the output of the data link controller 34 is connected with the input of the transmission unit 39.
  • Each of the other communication devices 31b, 31c, ... has the same arrangement as that of the communication device 31a.
  • the communication system can lock the slave communication device for the purpose of surely transferring a message from the master communication device to the slave communication device.
  • locking of the slave device is executed, using the control bits 17 ("3h", "Ah” and "Bh") relating to locking of the slave communication device in a communication packet when the data length bits 20 are successfully transferred so that the acknowledge bit is sent back.
  • unlocking of the slave device is executed, using the same control bits when the message having the number of bytes designated by the data length bits 20 has been successfully transferred.
  • Fig. 6A shows a combination of communication packets in the case where a 40 byte message is transferred from the communication device 31a as a master to the communication device 31b specified as a slave (Fig. 5).
  • Fig. 6B shows a communication sequence between the communication device 31a and the communication device 31b.
  • the number of communication packets to be transferred in the present invention is 2 whereas it is 3 in the prior art.
  • the data is transferred.
  • the slave communication device 31b receives the data length bits 20 successfully and sends back the acknowledge bit 22, it is locked by the master communication device 31a (Fig. 6B 1).
  • one communication packet permits the data up to only 32 bytes to be transferred, so that the first communication packet 40 cannot complete reception of the 40 byte data specified by the data length bits 20 (although it completes reception of 32 byte data in this embodiment). Therefore, at the end of transferring the first communication packet 40 (Fig. 6B 2), the communication device 31b does not satisfy the condition for unlocking so it remains locked by the master communication device 31a. As a result, the communication device 31b will not receive a communication packet from any communication device other than from the communication device 31a.
  • the master communication device 31a transfers the second communication packet 41 to the slave communication device 31b.
  • the second communication packet 41 with the control bits set for "Bh" which is the same in the first communication packet 40, and the data length bits 20 set for 8 bytes which corresponds to the remaining message, the remaining data will be transferred.
  • the slave communication device 31b sends back the acknowledge bit 22 in the data length field 5 of the second communication packet 41 (Fig. 6B 3) it will be locked by the master communication device 31a again.
  • the 8 byte data specified by the data length bits 20 are transferred successfully (Fig. 6B 4)
  • the communication device 31b is unlocked by the communication device 31a and restored to its original state.
  • unlocking of the slave communication device is automatically executed in accordance with the communication result, so that it is not necessary for the communication device serving as a master to consider to attend to the unlocking and so its processing can be made easily.
  • the message can be transferred with less number of communication packets so that its transfer efficiency can be improved.
  • the control unit 35 of the master communication device 31a sets, through its second output, the data corresponding to the respective fields constituting the first communication packet 40 in the transmission buffer 37. Specifically, with the slave address bit 14 set for the address of the slave communication device 31b, the control bits 17 set for "Bh" (data write and locking) and the data length bits 20 set for 40 bytes, the message is set in the transmission buffer 37. Thereafter, the control unit 35 emits, through its first output, a command of requiring data transmission to the data link controller 34. Then, the data link controller 34 reads out the data from the transmission buffer 37 so as to constitute a communication packet. The data will be transferred to the transmission unit 39.
  • the transmission unit 39 modulates the input data and sends out the modulated data to the transmission path 30 as the first communication packet 40 through the I/O terminal 32.
  • the maximum length of a message which can be transferred within one communication frame (packet) is 32 bytes so that the message of 40 bytes specified by the data length bits 20 will not be transferred.
  • the communication device 31b serving as a slave its receiving unit 33 receives the data on the transfer path 30 through the I/O terminal 32 and demodulates it.
  • the receiving unit 33 supplies the demodulated data to the data link controller 34.
  • the data link controller 34 decomposes the data for each field and checks whether or not the data includes an error such as parity.
  • the data link controller 34 supplies the received data to the receiving buffer 36 through its second output.
  • the data link controller 34 supplies a signal indicative of reception of the communication packet to the control unit 35 through its first output. In response to this signal, the control unit 35 reads the received data from the receiving buffer 36 so that the first communication packet 40 can be received.
  • Fig. 7 is a flowchart of the processing flow relating to locking in the data link controller 34.
  • Fig. 7 first, whether or not the control field 4 has been received successfully is decided (routine 50). If it is “NO”, the processing will be ended. If “YES”, whether or not the control bits 17 are any one of "3h”, “Ah” and “Bh” which are codes relative to locking will be decided (routine 51). If it is “NO”, the processing will be ended. If “YES”, that is, the control bits 17 are the code relative to locking, whether or not the data length field 5 has been received successfully will be decided (routine 52). If it is “NO”, the processing will be ended. If it is "YES”, the code indicative of being locked and the address of the master communication device 31a will be stored in the lock status unit 38 (routine 53).
  • routine 54 determines whether or not message having a length specified by the data length bits 20 has been received. If it is "NO”, the processing will be ended. If "YES”, the code indicative of being not locked will be stored in the lock status unit 38 (routine 55), thus completing the entire processing.
  • the data link controller 34 reads the contents of the lock status unit 38. If the code indicative of being locked has been stored therein, the data link controller 34 will perform the data reception only when the address stored in the lock status unit 38 coincides with the master address 12 of a communication packet transferred.
  • the first communication packet 40 permits the message of only 32 bytes to be received although the length of 40 bytes is specified by the data length bits 20. Therefore, the data link controller 34 completes the processing after having executed the routines 50, 51, 52, 53 and 54. Thus, the code indicative of being locked and the address of the communication device 31a are stored in the lock status unit 38. As a result, the communication device 31b is locked and thereafter will receive only the communication packet transferred from the communication device 31a until it is unlocked.
  • the communication device 31a transmits the second communication packet 41 in the same manner as for the first communication packet 40.
  • the control unit 35 in the communication device 31a sets in advance the control bits 17 for "Bh" which is also set for the first communication packet 40 and the data length bits 20 for 8 bytes which correspond to the size of the remaining message.
  • the communication device 31b receives the second communication packet 41 transmitted from the first communication device 31a. Then, the second communication packet 41 permits the data link controller 34 in the second communication device 31b to receive the message having a length specified by the data length bits 20, so that the data link controller 34 will execute the routines 50, 51, 52, 53, 54 and 55. Thus, the code indicative of being unlocked will be stored in the lock status unit 38 to unlock the second communication device 31b.
  • the slave communication device can be locked and unlocked using the same control bits in accordance with the communication result so that the master communication device is not required to previously attend to locking and unlocking, whereby the operation of the communication device can be made simple. Further, the message can be transferred with the number of communication packets lesser by one than in the prior art, so that the transfer efficiency can be improved.
  • the communication device 31b specified as a slave by the communication device 31a receives the first communication packet 40 from the communication device 31a, it is locked. Then, when a predetermined communication has been completed, the master communication device 31a must unlock the slave communication device 31b. However, if in connection with the second communication packet 41, the control unit 35 in the communication device 31b is late to read out the data stored in the receiving buffer 36 so that the receiving buffer 36 does not become vacant readily, the second communication packet 41 cannot be received and thus the communication device 31b remains locked disadvantageously.
  • control bits 17 include the code of "6h” (read of slave status and unlocking: see TABLE 1) which are control bits dedicated to unlocking in addition to the control bits (codes: "3h", “Ah” and “Bh”) relating to locking.
  • Fig. 8 is a flowchart of the processing of the data link controller 34 for the control bits "6h" dedicated to unlocking.
  • the data controller 34 in the slave communication device 31b will store the code indicative of not being locked in the lock status unit 38 to unlock the slave communication device 31b.
  • the slave status will be transferred irrespectively of the condition of the receiving buffer 36 so that the communication device 31b can be unlocked unconditionally.
  • the slave communication device can be locked and unlocked using the same control bits in accordance with the communication result so that the control unit in the master communication device is not required to previously take into account locking and unlocking, whereby the operation of the communication device can be made simple.
  • the message can be transferred without using one communication packet dedicated to locking and unlocking, i.e., with the number of communication packets lesser by one than in the prior art so that the transfer efficiency of a message can be improved.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Selective Calling Equipment (AREA)
  • Small-Scale Networks (AREA)
EP91109818A 1990-06-14 1991-06-14 Système de communication et dispositifs de communication avec verrouillage Expired - Lifetime EP0461674B1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
JP15588490 1990-06-14
JP155884/90 1990-06-14
JP307694/90 1990-11-14
JP30769490 1990-11-14

Publications (3)

Publication Number Publication Date
EP0461674A2 true EP0461674A2 (fr) 1991-12-18
EP0461674A3 EP0461674A3 (en) 1992-12-02
EP0461674B1 EP0461674B1 (fr) 1996-09-25

Family

ID=26483784

Family Applications (1)

Application Number Title Priority Date Filing Date
EP91109818A Expired - Lifetime EP0461674B1 (fr) 1990-06-14 1991-06-14 Système de communication et dispositifs de communication avec verrouillage

Country Status (3)

Country Link
US (1) US5343469A (fr)
EP (1) EP0461674B1 (fr)
DE (1) DE69122308T2 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0604166A1 (fr) * 1992-12-21 1994-06-29 Sony Corporation Système de communication et dispositifs de communication avec verrouillage
WO1999060753A1 (fr) 1998-05-21 1999-11-25 Matsushita Electric Industrial Co., Ltd. Procede de transmission de donnees, systeme de transmission de donnees, dispositif de commande pour transmettre des donnees, et support d'enregistrement de programme
EP1037431A1 (fr) * 1998-10-05 2000-09-20 Matsushita Electric Industrial Co., Ltd. Procede de transfert de donnees et systeme de transfert de donnees

Families Citing this family (46)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2862160B2 (ja) * 1993-05-31 1999-02-24 ソニー株式会社 通信方式
EP0660956B1 (fr) * 1993-07-16 2001-12-19 D2B Systems Co. Ltd. Systeme de bus de communication a attenuation du probleme de verrouillage des stations asservies
GB9314860D0 (en) * 1993-07-16 1993-09-01 D2B Systems Co Ltd Communication bus system with mitigation of slave station locking problem and master station for use in such communication system
JP3596021B2 (ja) * 1994-03-04 2004-12-02 三菱電機株式会社 データリンク情報制御方式
JP2760280B2 (ja) * 1994-04-18 1998-05-28 日本電気株式会社 通信データ交換装置および該交換装置を用いた通信システム
JP2848784B2 (ja) * 1994-08-02 1999-01-20 沖電気工業株式会社 パケット交換方式
US6631435B1 (en) 1996-02-02 2003-10-07 Sony Corporation Application programming interface for data transfer and bus management over a bus structure
US7577782B2 (en) 1996-02-02 2009-08-18 Sony Corporation Application programming interface for data transfer and bus management over a bus structure
US6233637B1 (en) * 1996-03-07 2001-05-15 Sony Corporation Isochronous data pipe for managing and manipulating a high-speed stream of isochronous data flowing between an application and a bus structure
US6519268B1 (en) 1996-03-07 2003-02-11 Sony Corporation Asynchronous data pipe for automatically managing asynchronous data transfers between an application and a bus structure
US6504847B1 (en) * 1996-10-16 2003-01-07 Thomson Licensing Sa Device interoperability
US7035898B1 (en) 1997-09-10 2006-04-25 Schneider Automation Inc. System for programming a factory automation device using a web browser
US20020091784A1 (en) * 1997-09-10 2002-07-11 Baker Richard A. Web interface to a device and an electrical network control system
US20020152289A1 (en) * 1997-09-10 2002-10-17 Schneider Automation Inc. System and method for accessing devices in a factory automation network
US6732191B1 (en) 1997-09-10 2004-05-04 Schneider Automation Inc. Web interface to an input/output device
US7058693B1 (en) 1997-09-10 2006-06-06 Schneider Automation Inc. System for programming a programmable logic controller using a web browser
US6011801A (en) * 1997-10-09 2000-01-04 Timeplex, Inc. Rate control of channels on a time division multiplex bus
US7162510B2 (en) * 1998-03-16 2007-01-09 Schneider Automation Inc. Communication system for a control system over Ethernet and IP networks
US6233626B1 (en) 1998-10-06 2001-05-15 Schneider Automation Inc. System for a modular terminal input/output interface for communicating messaging application layer over encoded ethernet to transport layer
US6167471A (en) 1998-10-14 2000-12-26 Sony Corporation Method of and apparatus for dispatching a processing element to a program location based on channel number of received data
US6853867B1 (en) 1998-12-30 2005-02-08 Schneider Automation Inc. Interface to a programmable logic controller
US6523108B1 (en) 1999-11-23 2003-02-18 Sony Corporation Method of and apparatus for extracting a string of bits from a binary bit string and depositing a string of bits onto a binary bit string
US7519737B2 (en) * 2000-07-07 2009-04-14 Schneider Automation Inc. Input/output (I/O) scanner for a control system with peer determination
US7181487B1 (en) 2000-07-07 2007-02-20 Schneider Automation Inc. Method and system for transmitting and activating an application requesting human intervention in an automation network
US7032029B1 (en) 2000-07-07 2006-04-18 Schneider Automation Inc. Method and apparatus for an active standby control system on a network
US7028204B2 (en) * 2000-09-06 2006-04-11 Schneider Automation Inc. Method and apparatus for ethernet prioritized device clock synchronization
US20020167967A1 (en) * 2000-09-06 2002-11-14 Schneider Electric Method for managing bandwidth on an ethernet network
US6904475B1 (en) 2000-11-06 2005-06-07 Sony Corporation Programmable first-in first-out (FIFO) memory buffer for concurrent data stream handling
US7023795B1 (en) 2000-11-07 2006-04-04 Schneider Automation Inc. Method and apparatus for an active standby control system on a network
US20030231212A1 (en) * 2002-06-18 2003-12-18 Bellsouth Intellectual Property Corporation User interface to a device environment
US7016888B2 (en) 2002-06-18 2006-03-21 Bellsouth Intellectual Property Corporation Learning device interaction rules
US7039698B2 (en) 2002-06-18 2006-05-02 Bellsouth Intellectual Property Corporation Notification device interaction
US6889207B2 (en) 2002-06-18 2005-05-03 Bellsouth Intellectual Property Corporation Content control in a device environment
US20030233660A1 (en) * 2002-06-18 2003-12-18 Bellsouth Intellectual Property Corporation Device interaction
US6795404B2 (en) 2002-06-18 2004-09-21 Bellsouth Intellectual Property Corporation Device for aggregating, translating, and disseminating communications within a multiple device environment
US20040210664A1 (en) * 2003-04-17 2004-10-21 Schneider Automation Inc. System and method for transmitting data
US7729464B2 (en) * 2006-12-22 2010-06-01 Teranetics, Inc. Aiding synchronization between master and slave transceivers
US8411764B2 (en) * 2007-08-16 2013-04-02 Farpointe Data, Inc. System and method for multi-protocol radio-frequency identification
US8624710B2 (en) * 2007-08-16 2014-01-07 Farpointe Data, Inc. System and method for interrogation radio-frequency identification
US7904696B2 (en) * 2007-09-14 2011-03-08 Intel Corporation Communication paths for enabling inter-sequencer communication following lock competition and accelerator registration
US8055856B2 (en) * 2008-03-24 2011-11-08 Nvidia Corporation Lock mechanism to enable atomic updates to shared memory
EP2316180A4 (fr) 2008-08-11 2011-12-28 Assa Abloy Ab Communications par interface wiegand sécurisées
US8680966B2 (en) 2009-02-19 2014-03-25 FP Wireless, LLC Long range radio frequency identification system
US8310344B2 (en) * 2009-02-19 2012-11-13 FP Wireless, LLC Long range radio frequency identification system
US10452877B2 (en) 2016-12-16 2019-10-22 Assa Abloy Ab Methods to combine and auto-configure wiegand and RS485
TWI647570B (zh) * 2017-06-16 2019-01-11 緯穎科技服務股份有限公司 資料傳輸裝置及其方法

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0333269A1 (fr) * 1988-03-16 1989-09-20 Koninklijke Philips Electronics N.V. Système et procédé omnibus de communication à canal unique et station servant à être utilisée dans un tel système omnibus de communication
EP0350838A2 (fr) * 1988-07-11 1990-01-17 Matsushita Electric Industrial Co., Ltd. Système de communication

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4707828A (en) * 1984-09-11 1987-11-17 Ricoh Company, Ltd. Multiaccess communication system
JPS6276954A (ja) * 1985-09-30 1987-04-09 Toshiba Corp 通信制御装置
JPH0771088B2 (ja) * 1987-04-06 1995-07-31 古河電気工業株式会社 多重伝送方式
US4951281A (en) * 1987-11-30 1990-08-21 Furukawa Electric Co., Ltd. Multiplex transmission system
US4998245A (en) * 1987-12-17 1991-03-05 Matsushita Electric Industrial Co., Ltd. Information transmission system having collective data transmission and collection devices
US5031175A (en) * 1989-09-15 1991-07-09 Matsushita Electric Industrial Co., Ltd. Communication control method for releasing communication apparatus from occupied state

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0333269A1 (fr) * 1988-03-16 1989-09-20 Koninklijke Philips Electronics N.V. Système et procédé omnibus de communication à canal unique et station servant à être utilisée dans un tel système omnibus de communication
EP0350838A2 (fr) * 1988-07-11 1990-01-17 Matsushita Electric Industrial Co., Ltd. Système de communication

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ELEKTRONIK. vol. 38, no. 25, 8 December 1989, MUNCHEN DE pages 79 - 83; K. ETSCHBERGER ET AL.: 'Buscontrollerbaustein f}r echtzeitf{hige Netze' *

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0604166A1 (fr) * 1992-12-21 1994-06-29 Sony Corporation Système de communication et dispositifs de communication avec verrouillage
US5608730A (en) * 1992-12-21 1997-03-04 Sony Corporation Bi-directional communication system
CN1055587C (zh) * 1992-12-21 2000-08-16 索尼公司 用于双向总线系统的发送方法，接收方法和通信方法以及双向总线系统
WO1999060753A1 (fr) 1998-05-21 1999-11-25 Matsushita Electric Industrial Co., Ltd. Procede de transmission de donnees, systeme de transmission de donnees, dispositif de commande pour transmettre des donnees, et support d'enregistrement de programme
EP1005199A1 (fr) * 1998-05-21 2000-05-31 Matsushita Electric Industrial Co., Ltd. Procede de transmission de donnees, systeme de transmission de donnees, dispositif de commande pour transmettre des donnees, et support d'enregistrement de programme
EP1005199A4 (fr) * 1998-05-21 2008-01-16 Matsushita Electric Ind Co Ltd Procede de transmission de donnees, systeme de transmission de donnees, dispositif de commande pour transmettre des donnees, et support d'enregistrement de programme
EP1037431A1 (fr) * 1998-10-05 2000-09-20 Matsushita Electric Industrial Co., Ltd. Procede de transfert de donnees et systeme de transfert de donnees
US6744777B1 (en) 1998-10-05 2004-06-01 Matsushita Electric Industrial Co., Ltd. Data transfer method and data transfer system
EP1037431A4 (fr) * 1998-10-05 2005-06-15 Matsushita Electric Ind Co Ltd Procede de transfert de donnees et systeme de transfert de donnees

Also Published As

Publication number Publication date
EP0461674B1 (fr) 1996-09-25
DE69122308D1 (de) 1996-10-31
US5343469A (en) 1994-08-30
EP0461674A3 (en) 1992-12-02
DE69122308T2 (de) 1997-04-24

Similar Documents

Publication Publication Date Title
US5343469A (en) Communication system and communication devices having lock function
CA1155521A (fr) Methode et systeme pour retransmettre les blocs numerotes recus incorrectement dans un systeme de transmission de donnees
US7944952B2 (en) Asynchronous data pipe for automatically managing asynchronous data transfers between an application and a bus structure
EP0228078B1 (fr) Procédé et réseau de communication pour diffusion limitée
EP0525985B1 (fr) Interface de liaison bidirectionnelle de données à haute vitesse
US5572546A (en) Data communications system with multilink protocol
EP0324886B1 (fr) Réduction du flux de contrôle dans des protocoles à retransmission sélective
US6944173B1 (en) Method and system for transmitting data between a receiver and a transmitter
EP0130206B1 (fr) Procede et dispositif permettant de resoudre un conflit d'utilisation d'un bus
EP0390567A2 (fr) Dispositif électronique avec fonction de communication du type à commande exclusive et son système de communication
KR100297395B1 (ko) 통신방법
EP0350838B1 (fr) Système de communication
JPS5992651A (ja) ポ−リング方式
US6744777B1 (en) Data transfer method and data transfer system
FI112710B (fi) Tietoliikenneväyläjärjestelmä ja sellaisessa järjestelmässä käytettävä asema
JP3109534B2 (ja) 通信システム及び通信装置
EP1005199B1 (fr) Procede de transmission de donnees, systeme de transmission de donnees, dispositif de commande pour transmettre des donnees, et support d'enregistrement de programme
KR100226781B1 (ko) 노드(node)인식(recognition)방법
US6711179B1 (en) Signal processing apparatus with three layer processing sections, and signal processing system with said two signal processing apparatuses
US20220374376A1 (en) Memory mapping of legacy i/f protocols over tdd
JP3428098B2 (ja) ネットワークにおけるデータ転送方法
JP2650317B2 (ja) 無線通信システムにおける同報通信制御方法
JPH06284140A (ja) ローカル通信システム
JPH0521378B2 (fr)
JP2874983B2 (ja) 通信装置

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 19910712

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): DE FR GB NL

PUAL Search report despatched

Free format text: ORIGINAL CODE: 0009013

AK Designated contracting states

Kind code of ref document: A3

Designated state(s): DE FR GB NL

17Q First examination report despatched

Effective date: 19940930

GRAH Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOS IGRA

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

GRAH Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOS IGRA

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): DE FR GB NL

REF Corresponds to:

Ref document number: 69122308

Country of ref document: DE

Date of ref document: 19961031

ET Fr: translation filed
PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

26N No opposition filed
REG Reference to a national code

Ref country code: GB

Ref legal event code: IF02

REG Reference to a national code

Ref country code: GB

Ref legal event code: 732E

NLS Nl: assignments of ep-patents

Owner name: NEC ELECTRONICS CORPORATION

REG Reference to a national code

Ref country code: FR

Ref legal event code: TP

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20090615

Year of fee payment: 19

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20100709

Year of fee payment: 20

REG Reference to a national code

Ref country code: NL

Ref legal event code: TD

Effective date: 20100715

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: NL

Payment date: 20100616

Year of fee payment: 20

REG Reference to a national code

Ref country code: FR

Ref legal event code: CD

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20100609

Year of fee payment: 20

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: DE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20110101

REG Reference to a national code

Ref country code: NL

Ref legal event code: V4

Effective date: 20110614

REG Reference to a national code

Ref country code: GB

Ref legal event code: PE20

Expiry date: 20110613

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GB

Free format text: LAPSE BECAUSE OF EXPIRATION OF PROTECTION

Effective date: 20110613

Ref country code: NL

Free format text: LAPSE BECAUSE OF EXPIRATION OF PROTECTION

Effective date: 20110614