Data communication system, data communication equipment, data communication method and storage medium thereof
Abstract
[Task] A data communication bus capable of mixing and communicating control signals and data is used to connect a plurality of electronic devices so that data communication can be performed between the devices.
Solution.The first ID information indicating a virtual communication relationship composed of N devices included in a plurality of devices and the second ID information for determining information data communicated between the N devices are provided. By using the information data to communicate, the inconvenience of the conventional communication method can be solved, and even in data transfer that does not require real-time performance, multicast transfer can be easily and quickly realized.
Term
Term ended
Projected expiry passed 9 March 2018, 8.5 years ago.
- Priority and filed
- Published
- Projected expiry
- Today
32 claims: 12 independent, 20 dependent
- 1【特許請求の範囲】 【請求項1】 複数の機器により構成されたデータ通信システムにおいて、 前記複数の機器に含まれるN個の機器により構成される仮想的な通信関係を示す第1の情報と、該N個の機器間において通信される情報データを判別する第2の情報とを用いて前記情報データの通信を行うことを特徴とするデータ通信システム。
- 2【請求項2】 請求項1に記載のデータ通信システムにおいて、 前記データ通信システムは、前記第1及び第2の情報を管理する機能を具備する管理機器を含み、該管理機器を用いて前記N個の機器間の通信を制御することを特徴とするデータ通信システム。
- 3【請求項3】 請求項2に記載のデータ通信システムにおいて、 前記管理機器は、前記N個の機器のそれぞれに、前記第1及び第2の情報を送信することを特徴とするデータ通信システム。
- 4【請求項4】 請求項3に記載のデータ通信システムにおいて、 前記管理機器は、前記第1及び第2の情報とともに、該管理機器に固有のユニークID情報を前記N個の機器のそれぞれに送信することを特徴とするデータ通信システム。
- 5【請求項5】 請求項4に記載のデータ通信システムにおいて、 前記N個の機器は、前記ユニークID情報を用いて前記第1及び第2の情報を設定した管理機器を識別することを特徴とするデータ通信システム。
- 6【請求項6】 請求項2~5の何れか1項に記載のデータ通信システムにおいて、 前記管理機器は、IEEE1394規格に準拠したAsynchronous転送方式を用いて、前記N個の機器のそれぞれとの通信を行うことを特徴とするデータ通信システム。
- 7【請求項7】 請求項2~6の何れか1項に記載のデータ通信システムにおいて、 前記管理機器は、前記第1及び第2の情報に関する付加情報をテーブルを用いて管理することを特徴とするデータ通信システム。
- 8【請求項8】 請求項2~7の何れか1項に記載のデータ通信システムにおいて、 前記N個の機器は、前記第1及び第2の情報により構成される通信パケットを用いて前記情報データを送信することを特徴とするデータ通信システム。
- 9【請求項9】 請求項8に記載のデータ通信システムにおいて、 前記第1の情報は、前記通信パケットのヘッダ部に格納され、前記第2の情報は、該通信パケットのデータ部に格納されていることを特徴とするデータ通信システム。
- 10【請求項10】 請求項2~9の何れか1項に記載のデータ通信システムにおいて、 前記情報データは、第2の情報に対応するメモリ空間に格納されていることを特徴とするデータ通信システム。
- 11【請求項11】 請求項1~10の何れか1項に記載のデータ通信システムにおいて、 前記第1の情報は、一つの送信機器と複数の受信機器とにより構成される論理的な接続関係を示すことを特徴とするデータ通信システム。
- 12【請求項12】 請求項1~11の何れか1項に記載のデータ通信システムにおいて、 前記第2の情報は、前記N個の機器間において通信される複数の異なる情報データのそれぞれを判別する情報であることを特徴とするデータ通信システム。
- 13【請求項13】 請求項1~12の何れか1項に記載のデータ通信システムにおいて、 前記N個の機器のそれぞれから出力される情報データは、前記データ通信システムを構成する全ての機器に転送されることを特徴とするデータ通信システム。
- 14【請求項14】 請求項1~13の何れか1項に記載のデータ通信システムにおいて、 前記N個の機器のそれぞれから出力される情報データは、IEEE1394規格に準拠したAsynchronous転送方式を用いて転送されることを特徴とするデータ通信システム。
- 15【請求項15】 請求項2~14の何れか1項に記載のデータ通信システムにおいて、 前記管理機器は、前記情報データを送信する機器から送信された終了フラグにより、該情報データの通信が終了したことを特徴とするデータ通信システム。
- 16【請求項16】 請求項2~15の何れか1項に記載のデータ通信システムにおいて、 前記仮想的な通信関係の開放は、前記管理機器或いは前記情報データを受信する機器により行われることを特徴とするデータ通信システム。
- 17【請求項17】 請求項1~16の何れか1項に記載のデータ通信システムにおいて、 前記情報データを受信する機器は、前記仮想的な通信関係を構成する要求に対して、受信バッファのサイズ、メモリ空間内の所定の領域を示すアドレス情報、データ開始のポインタを示すシーケンシャル番号、準備完了を示す情報のうち、少なくとも一つの情報を含むパケットを送信することを特徴とするデータ通信システム。
- 18【請求項18】 請求項1~17の何れか1項に記載のデータ通信システムにおいて、 前記情報データを送信する機器は、該情報データを受信する機器からのレスポンスを所定期間計時し、該期間により通信異常を検出することを特徴とするデータ通信システム。
- 19【請求項19】 請求項18に記載のデータ通信システムにおいて、 前記情報データを送信する機器は、前記通信異常を検出した場合に、前記情報データの再送動作を自動的に開始することを特徴とするデータ通信システム。
- 20【請求項20】 複数の機器により構成されたデータ通信システムにおいて、 前記複数の機器に含まれるN個の機器により構成される仮想的な通信関係を示す情報と、該N個の機器間で通信される情報データを格納する仮想的なメモリ空間を指定する情報とを用いて前記情報データの通信を行うことを特徴とするデータ通信システム。
- 21【請求項21】 複数の機器により構成されたデータ通信システムにおいて、 複数のID情報を用いて仮想的な通信環境を設定することを特徴とするデータ通信システム。
- 22【請求項22】 複数の機器により構成されたデータ通信システムに接続可能なデータ通信装置において、 前記複数の機器に含まれるN個の機器により構成される仮想的な通信関係を示す第1の情報と、該N個の機器間において通信される情報データを判別する第2の情報とを設定する設定手段と、 前記設定手段により設定された前記第1及び第2の情報を用いて前記情報データの通信を行う通信手段とを具備することを特徴とするデータ通信装置。
- 23【請求項23】 複数の機器により構成されたデータ通信システムに接続可能なデータ通信装置において、 前記複数の機器に含まれるN個の機器により構成される仮想的な通信関係を示す第1の情報と、該N個の機器間において通信される情報データを判別する第2の情報とを含む前記情報データを受信する受信手段と、 前記第1及び第2の情報の情報を用いて前記受信手段により受信された情報データが自己に送信されたデータであるか否かを判別する判別手段とを具備することを特徴とするデータ通信装置。
- 24【請求項24】 複数の機器により構成されたデータ通信システムに接続可能なデータ通信装置において、 前記複数の機器に含まれるN個の機器により構成される仮想的な通信関係を示す情報と、該N個の機器間で通信される情報データを格納する仮想的なメモリ空間を指定する情報とを設定する設定手段と、 前記設定手段により設定された前記第1及び第2の情報を用いて前記情報データの通信を行う通信手段とを具備することを特徴とするデータ通信装置。
- 25【請求項25】 複数の機器により構成されたデータ通信システムに接続可能なデータ通信装置において、 前記複数の機器に含まれるN個の機器により構成される仮想的な通信関係を示す情報と、該N個の機器間で通信される情報データを格納する仮想的なメモリ空間を指定する情報とを含む情報データを受信する受信手段と、 前記第1及び第2の情報を用いて前記受信手段により受信された情報データが自己に送信されたデータであるか否かを判別する判別手段とを具備することを特徴とするデータ通信装置。
- 26【請求項26】 複数の機器により構成されたデータ通信システムに適用可能なデータ通信方法において、 前記複数の機器に含まれるN個の機器により構成される仮想的な通信関係を示す第1の情報と、該N個の機器間において通信される情報データを判別する第2の情報とを用いて前記情報データの通信を行うことを特徴とするデータ通信方法。
- 27【請求項27】 複数の機器により構成されたデータ通信システムに適用可能なデータ通信方法において、 前記複数の機器に含まれるN個の機器により構成される仮想的な通信関係を示す情報と、該N個の機器間で通信される情報データを格納する仮想的なメモリ空間を指定する情報とを含む通信パケットを用いて前記情報データの通信を行うことを特徴とするデータ通信方法。
- 28【請求項28】 複数の機器により構成されたデータ通信システムに適用可能なデータ通信方法において、 複数のID情報を用いて仮想的な通信環境を設定することを特徴とするデータ通信方法。
- 29【請求項29】 複数の機器により構成されたデータ通信システムに適用可能なデータ通信方法において、 前記複数の機器に含まれるN個の機器により構成される仮想的な通信関係を示す第1の情報と、該N個の機器間において通信される情報データを判別する第2の情報とを用いて、前記情報データが自己に送信されたデータであるか否かを判別することを特徴とするデータ通信方法。
- 30【請求項30】 複数の機器により構成されたデータ通信システムに適用可能なデータ通信方法において、 前記複数の機器に含まれるN個の機器により構成される仮想的な通信関係を示す情報と、該N個の機器間で通信される情報データを格納する仮想的なメモリ空間を指定する情報とを用いて、前記情報データが自己に送信されたデータであるか否かを判別することを特徴とするデータ通信方法。
- 31【請求項31】 請求項22~25の何れか1項に記載の各手段としてコンピュータを機能させるためのプログラムを格納したことを特徴とする記憶媒体。
- 32【請求項32】 請求項26~29の何れか1項に記載のデータ通信方法の手順をコンピュータに実行させるためのプログラムを格納したことを特徴とする記憶媒体。
Independent claims32
418 paragraphs in 1 section, as filed
Description: TECHNICAL FIELD [Detailed description of the invention]
【0001】
[Technical field to which the invention belongs]
The present invention relates to a data communication system, a data communication device, a data communication method and a storage medium, and in particular, a plurality of electronic devices (hereinafter referred to as devices) using a data communication bus capable of mixing and communicating control signals and data. It relates to a data communication system in which data communication is performed between devices by connecting the devices, and devices and methods constituting the data communication system.
【0002】
[Conventional technology]
Hard disks and printers are the most frequently used computer peripherals, and these peripherals are general-purpose interfaces for small computers, such as SCSI, which is a typical digital interface (hereinafter referred to as digital I / F). The computer is connected to the computer and data communication is performed.
【0003】
In addition, recording / playback devices such as digital cameras and digital video cameras are also one of the peripheral devices as an input means to a personal computer (hereinafter referred to as a PC), and in recent years, images such as still images and moving images taken by a digital camera or a video camera can be displayed. Technology in the field of importing to a PC, storing it on a hard disk, editing it on a PC, and then printing it in color with a printer is advancing, and the number of users is increasing.
【0004】
Then, when the captured image data is output from a PC to a printer or a hard disk, data communication is performed via the above-mentioned SCSI or the like, and in such a case, information having a large amount of data such as image data. These digital I / Fs need to have a high transfer data rate and are versatile in order to send data.
【0005】
FIG. 8 shows a block diagram when a digital camera, a PC, and a printer are connected as a conventional example. In Figure 8, 101 is a digital camera, 102 is a personal computer (PC), and 103 is a printer. Is found, the memory is a recording unit of the digital camera 104, the image data decoding circuit 105, 106 is an image processing unit, 107 a D / A converter, 108 is a display unit EVF, 109 is a digital camera Digital The I / O section, 110 is the digital I / O section with the digital camera of the PC, 111 is the operation section such as the keyboard and mouse, and 112 is the image data decoding circuit.
【0006】
113 Is the display, 114 is the hard disk device, 115 is the memory such as RAM, 116 is the MPU of the arithmetic processing unit, 117 is the PCI bus, 118 is the SCSI interface (board) of the digital I / F, and 119 is connected to the PC with a SCSI cable. The SCSI interface of the printer, 120 is the memory, 121 is the printer head, 122 is the printer controller of the printer control unit, and 123 is the driver.
【0007】
The procedure for importing an image captured by a digital camera to a PC and outputting it from the PC to a printer will be explained. When the image data stored in the memory 104 of the digital camera 101 is read out, one of the read image data is decoded by the decoding circuit 105 and image processing for display by the image processing circuit 106. Is displayed, and it is displayed on EVF108 via D / A converter 107. On the other hand, it goes from the digital I / O section 109 to the digital I / O section 110 of the PC 102 along the cable for external output.
【0008】
In the PC102, the image data input from the digital I / O section 110 using the PCI bus 117 as a mutual transmission bus is stored on the hard disk 114 when stored, and decoded by the decoding circuit 112 when displayed. After that, it is stored in the memory 115 as a display image, converted into an analog signal on the display 113, and then displayed. Operation input such as when editing on PC102 is performed from the operation unit 111, and processing of the entire PC102 is performed by MPU116.
【0009】
When printing out an image, the image data is transmitted from the SCSI interface board 118 in the PC102 on the SCSI cable, received by the SCS I interface 119 on the printer 103 side, and formed as a print image by the memory 120. The printer head 121 and the driver 123 operate under the control of the printer controller 122 to print the print image data read from the memory 120. The above is the procedure for importing or printing conventional image data on a PC.
【0010】
In this way, conventionally, each device is connected to the host PC, and the image data captured by the recording / playback device is printed after passing through the PC. In addition, AV devices such as digital VTRs, TVs, and tuners, personal computers (hereinafter referred to as PCs), etc. are connected to each other using the IEEE 1394 serial bus (hereinafter referred to as 1394), and digital between them. Communication systems for transmitting and receiving video signals, digital audio signals, etc. have been proposed.
【0011】
In these systems, it is important to transfer data in real time, so data communication is performed by so-called synchronous communication (hereinafter referred to as Isochronous communication). In this case, the real-time performance of the data transfer is guaranteed, but the reliable communication is not guaranteed.
【0012】
[Problems to be Solved by the Invention]
However, as the problems of the digital interface mentioned in the above-mentioned conventional example, SCSI has a low transfer data rate, a thick cable for parallel communication, the type and number of peripheral devices to be connected, a connection method, and the like. There are restrictions, and inconveniences in many respects have also been pointed out.
【0013】
Further, in the case of the conventional IEEE 1394 communication, since the synchronous communication is performed, it is not guaranteed that the communication is surely performed. Therefore, if you want to transfer data reliably, you cannot use the conventional 1394 Isochronous communication.
【0014】
Further, in the conventional 1394 Isochronous communication, the total number of communications is limited to 64 even when there is a free communication band. Therefore, there is a problem that the conventional 1394 Isochronous communication cannot be used when it is desired to perform a large number of communications that do not require much communication band. Further, in the conventional 1394 communication method, it is conceivable that the data transfer is interrupted due to a bus reset or an error during the data transfer.
【0015】
In this case, with the conventional 1394 communication method, it is not possible to know what kind of data content has been lost. Therefore, the conventional 1394 communication method has a problem that it is required to take a very complicated communication procedure in order to recover from the data transfer interruption.
【0016】
The present invention has been made to solve the above-mentioned problems, and the first object is to solve the inconvenience of the conventional communication method, transfer data easily and at high speed, and enable reliable data transfer. The purpose of 1. A second object of the present invention is to enable a large number of communications at the same time when the communication band is not used so much. Another object of the present invention is that the data lost due to the interruption of data transfer can be easily detected, and the recovery from the interruption of data transfer can be surely and easily made possible. .. Further, in the present invention, when a plurality of control nodes exist on the network, there is no means for identifying the logical connection set by each control node. The fourth purpose is to be able to provide a means of sending data from one source node to multiple destination nodes. A fifth object of the present invention is to prevent multicast packets from being received by a conventional 1394 standard device in order to realize multicast forwarding.
【0017】
[Means for solving problems]
In order to solve the conventional problems, the present invention solves the problems of the conventional digital I / F as much as possible, and is a general-purpose digital I / F (for example, IEEE1394) that is unified and installed in each digital device. -1995 High-performance serial bus) is used to realize data communication between devices when PCs, printers, other peripheral devices, digital cameras, digital VTR recording / playback devices, etc. are connected in a network configuration, and from the recording / playback device. It realizes importing video data to a PC, and transferring video data directly to a printer for printing. In such a network, a protocol for transmitting various types of data by dividing each data into a plurality of pieces by an asynchronous transaction is provided.
【0018】
An ID, which is unique node information possessed by the control node, is added to the payload, which does not change even when the bus is reset. The control node announces the number of logically connected destinations to the source.
【0019】
The source node waits for the reception confirmation response packet from the destination for each buffer size from the destination, and then transmits the next segment packet. For the packet indicating the end of transmission data from the source node, each destination returns a reception confirmation response packet.
【0020】
Send from the source node in multicast transmission Destination Bus ID Set an address of 0 to 3 FE or less, not the local bus 3 FF (h).
【0021】
The data communication system of the present invention is a data communication system composed of a plurality of devices, the first information indicating a virtual communication relationship composed of N devices included in the plurality of devices, and the N. It is characterized in that the information data is communicated by using the second information for discriminating the information data to be communicated between the devices. Here, the first information corresponds to the multicast ID described in the embodiment. Further, the second information corresponds to the connection ID described in the present embodiment. Another feature of the data communication system of the present invention is that the data communication system includes a management device having a function of managing the first and second information, and the management device is used to describe the data communication system. It is characterized by controlling communication between N devices. Another feature of the data communication system of the present invention is that the management device transmits the first and second information to each of the N devices. Another feature of the data communication system of the present invention is that the management device, together with the first and second information, provides unique ID information unique to the management device to each of the N devices. It is characterized by transmitting. Another feature of the data communication system of the present invention is that the N devices identify the management device in which the first and second information is set by using the unique ID information. It is supposed to be. Another feature of the data communication system of the present invention is that the management device communicates with each of the N devices by using an asynchronous transfer method compliant with the IEEE1394 standard. There is. Another feature of the data communication system of the present invention is that the N devices manage additional information related to the first and second information by using a table. Another feature of the data communication system of the present invention is that the N devices use communication packets composed of the first and second information. It is characterized by transmitting information data. Another feature of the data communication system of the present invention is that the first information is stored in the header part of the communication packet and the second information is stored in the data part of the communication packet. It is characterized by being. Another feature of the data communication system of the present invention is that the information data is stored in a memory space corresponding to the second information. Another feature of the data communication system of the present invention is that the first information indicates a logical connection relationship composed of one transmitting device and a plurality of receiving devices. .. Another feature of the data communication system of the present invention is that the second information is information for discriminating each of a plurality of different information data communicated between the N devices. It is supposed to be. Another feature of the data communication system of the present invention is that the information data output from each of the N devices is transferred to all the devices constituting the data communication system. There is. Another feature of the data communication system of the present invention is that the information data output from each of the N devices is transferred using an asynchronous transfer method compliant with the IEEE1394 standard. There is. Another feature of the data communication system of the present invention is that the management device ends the communication of the information data by the end flag transmitted from the device that transmits the information data. .. Another feature of the data communication system of the present invention is that the virtual communication relationship is opened by the management device or the device that receives the information data. Further, another feature of the data communication system of the present invention is that the device that receives the information data determines the size of the reception buffer and the predetermined size in the memory space in response to the request constituting the virtual communication relationship. Address information indicating the area of It is characterized by transmitting a packet containing at least one piece of information indicating a sequential number indicating a data start pointer and information indicating readyness. Another feature of the data communication system of the present invention is that the device that transmits the information data clocks the response from the device that receives the information data for a predetermined period and detects a communication abnormality according to the period. It is characterized by that. Another feature of the data communication system of the present invention is that the device that transmits the information data automatically starts the retransmission operation of the information data when the communication abnormality is detected. It is supposed to be. Another feature of the data communication system of the present invention is information indicating a virtual communication relationship composed of N devices included in the plurality of devices and communication between the N devices. It is characterized in that the information data is communicated using information that specifies a virtual memory space for storing the information data to be stored. Here, the information indicating the virtual communication relationship corresponds to the multicast ID described in the present embodiment. Further, the information that specifies the virtual memory space corresponds to the destination offset described in the present embodiment. Another feature of the data communication system of the present invention is that a virtual communication environment is set using a plurality of ID information. Here, the plurality of ID information includes any one of the multicast ID, the connection ID, and the destination offset described in the present embodiment.
【0022】
The data communication device of the present invention is a data communication device that can be connected to a data communication system composed of a plurality of devices, and exhibits a virtual communication relationship composed of N devices included in the plurality of devices. Using the setting means for setting the information 1 and the second information for discriminating the information data communicated between the N devices, and the first and second information set by the setting means. It is characterized by including a communication means for communicating the information data. Here, the first information corresponds to the multicast ID described in the embodiment. The second information corresponds to the connection ID described in the present embodiment. Another feature of the data communication device of the present invention is a data communication device that can be connected to a data communication system composed of a plurality of devices, and is composed of N devices included in the plurality of devices. A receiving means for receiving the information data including the first information indicating the virtual communication relationship and the second information for determining the information data communicated between the N devices, the first and the first. It is characterized in that it includes a discriminating means for determining whether or not the information data received by the receiving means is the data transmitted to itself by using the information of the second information. Another feature of the data communication device of the present invention is that the data communication device that can be connected to a data communication system composed of a plurality of devices is composed of N devices included in the plurality of devices. The setting means for setting the information indicating the virtual communication relationship and the information for specifying the virtual memory space for storing the information data communicated between the N devices, and the setting means set by the setting means. It is characterized by including a communication means for communicating the information data using the first and second information. Here, the information indicating the virtual communication relationship corresponds to the multicast ID described in the present embodiment. The information that specifies the virtual memory space is the destination described in the present embodiment. Corresponds to offset. Another feature of the data communication device of the present invention is a data communication device that can be connected to a data communication system composed of a plurality of devices, and is composed of N devices included in the plurality of devices. A receiving means for receiving information data including information indicating a virtual communication relationship and information specifying a virtual memory space for storing information data communicated between the N devices, and the first method. It is characterized in that it includes a discriminating means for determining whether or not the information data received by the receiving means is the data transmitted to itself by using the second information. Here, the information indicating the virtual communication relationship corresponds to the multicast ID described in the present embodiment. Further, the information that specifies the virtual memory space corresponds to the destination offset described in the present embodiment.
【0023】
The data communication method of the present invention is a data communication method applicable to a data communication system composed of a plurality of devices, and shows a virtual communication relationship composed of N devices included in the plurality of devices. It is characterized in that the information data is communicated by using the information of 1 and the second information for discriminating the information data to be communicated between the N devices. Here, the first information corresponds to the multicast ID described in the embodiment. Further, the second information corresponds to the connection ID described in the present embodiment. Another feature of the data communication method of the present invention is that the data communication method applicable to a data communication system composed of a plurality of devices is composed of N devices included in the plurality of devices. The information data is communicated using a communication packet containing information indicating a virtual communication relationship and information specifying a virtual memory space for storing information data communicated between the N devices. It is characterized by that. Here, the information indicating the virtual communication relationship corresponds to the multicast ID described in the present embodiment. The information that specifies the virtual memory space is the destination described in the present embodiment. Corresponds to offset. Another feature of the data communication method of the present invention is that a virtual communication environment is set using a plurality of ID information in a data communication method applicable to a data communication system composed of a plurality of devices. It is characterized by doing. Further, another feature of the data communication method of the present invention is that the data communication method applicable to a data communication system composed of a plurality of devices is composed of N devices included in the plurality of devices. The information data is the data transmitted to itself by using the first information indicating the virtual communication relationship and the second information for discriminating the information data communicated between the N devices. It is characterized by determining whether or not it is. Here, the plurality of ID information includes any one of the multicast ID, the connection ID, and the destination offset described in the present embodiment. Further, another feature of the data communication method of the present invention is that the data communication method applicable to a data communication system composed of a plurality of devices is composed of N devices included in the plurality of devices. Data in which the information data is transmitted to itself by using information indicating a virtual communication relationship and information specifying a virtual memory space for storing information data communicated between the N devices. It is characterized in that it is determined whether or not it is. Here, the information indicating the virtual communication relationship corresponds to the multicast ID described in the present embodiment. Further, the information that specifies the virtual memory space corresponds to the destination offset described in the present embodiment. Any of offset is included. Further, another feature of the data communication method of the present invention is that the data communication method applicable to a data communication system composed of a plurality of devices is composed of N devices included in the plurality of devices. Data in which the information data is transmitted to itself by using information indicating a virtual communication relationship and information specifying a virtual memory space for storing information data communicated between the N devices. It is characterized in that it is determined whether or not it is. Here, the information indicating the virtual communication relationship corresponds to the multicast ID described in the present embodiment. Further, the information that specifies the virtual memory space corresponds to the destination offset described in the present embodiment. Any of offset is included. Further, another feature of the data communication method of the present invention is that the data communication method applicable to a data communication system composed of a plurality of devices is composed of N devices included in the plurality of devices. Data in which the information data is transmitted to itself by using information indicating a virtual communication relationship and information specifying a virtual memory space for storing information data communicated between the N devices. It is characterized in that it is determined whether or not it is. Here, the information indicating the virtual communication relationship corresponds to the multicast ID described in the present embodiment. Further, the information that specifies the virtual memory space corresponds to the destination offset described in the present embodiment.
【0024】
The storage medium of the present invention is characterized in that it stores a program for operating a computer as each of the above means. Here, the first information corresponds to the multicast ID described in the embodiment. Another feature of the storage medium of the present invention is that the storage medium stores a program for causing a computer to execute the procedure of the data communication method.
【0025】
[Action]
Since the present invention has the above-mentioned technical means, an independent connection ID uniquely determined in the network is set by the controller node, a logical connection is established between the source and destination nodes, and each logical connection is established. Assign the connection ID. After that, in the handshake communication between the source and the destination node, communication is performed using a so-called broadcast asynchronous transaction in which the connection ID number set by the controller is included in the field in the payload.
【0026】
Each node determines the connection ID in the payload, determines whether or not it is a connection set between its own nodes, and excludes everything other than the set connection ID by itself.
【0027】
The source node sends a broadcast packet with a connection request flag to the destination node, and the destination node starts the data packet and the buffer size information that can be received as soon as the node is ready to receive data. It contains a data sequence number indicating the order, sets the Ack bit, and communicates using so-called broadcast Asynchronous packets.
【0028】
The source node receives the packet sent by broadcast, determines the connection ID, and confirms that it is an Ack response from the destination node. With the above, data transfer is started.
【0029】
In addition, the source and destination nodes identify the logical connections individually set between the source destinations by the worldwide unique ID which is the unique information of the control node in the payload and the connection ID set by the control node. ..
【0030】
In addition, data is transmitted to multiple connected destinations with a single connection ID. Traditional 1394 devices are not 3 FF (h), which indicates that the destination bus ID is local, so even if the destination physical ID is 3 F (h), packets forwarded by multicast can be easily transmitted. Can be deleted.
【0031】
BEST MODE FOR CARRYING OUT THE INVENTION
Hereinafter, embodiments of the present invention will be described with reference to the drawings. In Figure 1, 10 is a computer, 12 is an arithmetic processing device (MPU), 14 is a first 1394 interface, 16 is a first operation unit such as a keyboard, 18 is a first decoder, 20 is a CRT display, etc. The display device, 22 is a hard disk, 24 is the first memory, which is the internal memory of the computer 10 according to the present invention, and 26 is the internal computer bus such as the PCI bus.
【0032】
In addition, 28 is VCR, 30 is an imaging optical system, 32 is an analog-to-digital (A / D) converter, 34 is a video processing unit, 36 is a compression / expansion circuit, 38 is the first memory, and 40 is the second. Memory, 42 is the first data selector, 44 is the second 1394 interface, 46 is the first memory control circuit, 48 is the second memory control circuit, 50 is the system controller, 52 is the second operation unit, 54 is a finder, 56 is a D / A converter, and 58 is a recording unit.
【0033】
In addition, 60 is the printer, 62 is the third 1394 interface, 64 is the second data selector, 66 is the third controls, 68 is the printer controller, 70 is the second decoder, 72 is the third memory. , 74 is an image processing unit, 76 is a driver, and 78 is a printer head.
【0034】
The computer10, the VCR28, and the printer 60 form a 1394 serial bus node with the first to third 1394 interfaces 14,44,62, and the first to third 1394 interfaces 14,44,62. It is connected to each other via 1394, and it is possible to send and receive data and control by command.
【0035】
In this embodiment, for example, computer10 operates as a controller for transmitting and receiving image signals on a 1394 serial bus. In the computer 10 according to the present embodiment, for example, by the computer internal bus 26 such as the PCI bus, 12 is the arithmetic processing unit (MPU), the 1394 interface 14, the keyboard 16, the decoder 18, the CRT display 20, the hard disk 22, and the internal. Each internal device, such as memory 24, is interconnected.
【0036】
12 is an arithmetic processing unit (MPU) that executes the software recorded on the hard disk 22 and moves various data to the internal memory 24. In addition, the arithmetic processing unit (MPU) in 12 also performs arbitration operation of each device connected by the PCI bus 26. The 1394 interface 14 receives the image signal transferred on the 1394 serial bus, and also transmits the image signal recorded on the hard disk 22 and the image signal stored in the internal memory 24.
【0037】
The 1394 interface 14 also transmits command data to other devices connected on the 1394 serial bus. In addition, the 1394 interface 14 transfers the signal transferred on the 1394 serial bus to another 1394 node.
【0038】
The operator causes the MPU 12 to execute the software recorded on the hard disk 22 through an operation unit such as the keyboard 16. Information such as the software is presented to the operator by a display device 20 such as a CRT display.
【0039】
The decoder 18 decodes the image signal received from the 1394 serial bus through the above software. The decoded image signal is also presented to the operator by a display device 20 such as a CRT display.
【0040】
In this embodiment, for example, the VCR28 operates as an image signal input device. The luminance signal (Y) and color difference signal (C) of the image input from the imaging optical system 30 are each converted into digital data by the A / D converter 32.
【0041】
The digital data is multiplexed by the video processing unit 34. After that, the data amount of the image information is compressed by the compression / expansion circuit 36. Generally, the compression processing circuit is provided independently of YC, but here, for simplification of the explanation, an example of compression processing in YC time division is shown.
【0042】
Next, a shuffling process is performed for the purpose of making the image data resistant to transmission path errors. The purpose of this process is to convert a burst error, which is a continuous code error, into a random error, which is a discrete error that is easy to correct or interpolate. In addition, if the purpose of equalizing the bias of the amount of information generated due to the density in the screen of the image is emphasized, if this processing step is brought before the compression processing, a variable length code such as run length can be obtained. It is convenient when used.
【0043】
In response to this, data identification (ID) information for data shuffling restoration is added. The ID added by this ID addition operation is used as auxiliary information at the time of decompression processing (information amount expansion processing) at the time of reproduction together with the mode information of the system recorded at the same time. Error correction (ECC) information is added to reduce errors during playback of these data. Up to the addition of such a redundant signal is processed for each independent recording area corresponding to each information such as video and audio.
【0044】
As described above, the image signal to which the ID information and the ECC information are added is recorded by the recording unit 58 on a recording medium such as a magnetic tape, and is temporarily stored in the first memory 38 described later.
【0045】
On the other hand, the image data multiplexed by the video processing unit 34 is digital-to-analog converted by the D / A converter 56 and observed by the operator with the electronic viewfinder 54.
【0046】
Further, the operator transmits various operation information to the system controller 50 via the second operation unit 52, and the system controller 50 controls the entire VCR by the operation information.
【0047】
Further, the image data multiplexed by the video processing unit 34 is output to the second memory 40 and temporarily stored. The operation of the first memory 38 and the second memory 40 described above is controlled by the system controller 50 via the first memory control circuit 46 and the second memory control circuit 48, respectively.
【0048】
The first data selector 42 selects data from the first memory 38 and the second memory 40 described above and passes the data to the second 1394 interface 44, or the data from the second 1394 interface 44. Select to pass to either the first memory 38 or the second memory 40.
【0049】
By the above operation, the compressed image data and the uncompressed image data can be selected and output by the operator from the second 1394 interface 44 in the VCR28.
【0050】
The second 1394 interface 44 receives command data for controlling the VCR28 through the 1394 serial bus. The received command data is input to the system controller 50 through the first data selector 42.
【0051】
The system controller 50 creates response data for the command data and sends the data to the 1394 serial bus through the first data selector 42 and the second 1394 interface 44.
【0052】
In this embodiment, for example, the printer 60 operates as an image print output device. The third 1394 interface 62 receives an image signal transferred on the 1394 serial bus and command data for controlling the printer 60 through the 1394 serial bus. The third 1394 interface 62 also transmits response data to the command.
【0053】
The received image data is input to the second decoder 70 through the second data selector 64. The second decoder 70 decodes the image data and outputs it to the image processing unit 74. The image processing unit 74 temporarily stores the decoded image data in the third memory 72.
【0054】
On the other hand, the received command data is input to the printer controller 68 through the second data selector 64. The printer controller 68 performs various printing-related controls such as paper feed control by the driver 76 and position control of the printer head 78 based on the command data.
【0055】
Further, the printer controller 68 transmits the image data temporarily stored in the third memory 72 as print data to the printer head 78 to perform the printing operation. As described above, the first to third 1394 interfaces 14, 44, 62 according to the present embodiment each constitute a node of the 1394 serial bus.
【0056】
The first 1394 interface 14 operates as a control node or a controller, the second 1394 interface 44 operates as a source node for image data, and the third 1394 interface 44 operates as a destination node.
【0057】
The operation of each node according to the present embodiment is shown below with reference to FIG. In Figure 2, 200 is the controller, 202 is the source node, 204 is the destination node, 206 is the subsystem inside the source node, 208 is the object such as image data, 210 is the first memory space inside the destination node, 212. Is the first connection, 214 is the nth memory space of the destination, and 216 is the nth connection.
【0058】
The controller 200 is a node that manages the connection ID for establishing the connection between the source node 202 that performs data transfer and the destination node 204.
【0059】
The controller 200 may be a node independent of the source node 202 and the destination node 204, or the source node or the destination node and the controller may be the same. In the latter case, no transaction is required between the controller and the source node or destination node, which is the same node as the controller.
【0060】
In this embodiment, an example is shown in which the controller 200 exists on a node other than the source node 202 and the destination node 204. In the communication device of the present embodiment, it is possible to establish a plurality of connections.
【0061】
The source node 202 writes object208 such as image data from the internal subunit 206 to the first memory space 210 inside the destination node, for example, through the first connection 212. Further, data transfer by the above-mentioned connection is performed by using, for example, an asynchronous packet.
【0062】
Next, the operation of each node of the controller 200, the source node 202, and the destination node 204 described above will be described with reference to FIG. 3 (a). The controller sends a data packet to make a connection to the source node and destination node selected by the user.
【0063】
This packet is an Asynchronous packet, and the connection ID for identifying this connection is written in the payload. Following this packet, the controller sends a send command packet to the source node. Upon receiving the send command packet, the source node and destination node perform a broadcast transaction using the assigned connection ID and start data transfer.
【0064】
When the data transfer is completed, the source sends a broadcast packet indicating segment end, and the controller that receives this packet releases the connection ID and the data transfer ends.
【0065】
Here, the connection ID has a meaning of indicating a logical connection between the source node and the destination node and discriminating a plurality of objects transmitted from the subunits included in the source node. Therefore, when multiple different objects are sent from the same source node to the same destination node, the destination node can determine each object by detecting the connection ID contained in the Asynchronous packet. ..
【0066】
Further, when the same object is transmitted from the same source node to a plurality of different destination nodes, each destination node can determine an asynchronous packet to be received based on this connection ID.
【0067】
The source node that receives the connection ID notification packet and the transmission command packet from the controller sends an Asynchronous broadcast packet of the inquiry to the destination node.
【0068】
The connection ID specified in the controller is written in this packet. The destination node receives this packet and sends out a broadcast packet of the response. The same connection ID is also written in this packet, and the source node collates this ID to identify whether the packet is destined for this source node.
【0069】
The buffer size and offset address of the destination node are written in the response packet, and subsequent data transfer is performed by a write transaction to that address.
【0070】
The source node writes to the offset address received from the destination node using Asynchronous broadcast packets. The connection ID and data sequence number are written in this packet.
【0071】
After sending the broadcast packet, the source node waits for a response from the destination node. A response packet with the connection ID and sequence number is sent from the destination node as an asynchronous broadcast packet, and when this packet is received, the source node increments the sequence number and sends the next data in the same way.
【0072】
By repeating this procedure, the source node transfers data. The maximum time to wait for a response from the destination node is predetermined, and if no response is returned after that time, the same data is retransmitted using the same sequence number. When the response packet of the retransmission request is transmitted from the destination node, the data of the specified sequence number is retransmitted by broadcasting. When all the data transfer is completed, the source node sends a broadcast packet indicating segment end to end the data transfer.
【0073】
The destination node that receives the connection ID notification packet from the controller waits for the asynchronous broadcast packet of the inquiry from the source node. The destination node that receives the broadcast packet compares the connection ID written in the packet with the connection ID notified by the controller to determine whether or not this packet is from the source node.
【0074】
When the inquiry packet from the source node is received, the destination node broadcasts a response packet in which the connection ID, the buffer size for data reception, and the offset address are written. Data from the source node is written to this address.
【0075】
When data is written from the source node, the destination node matches the connection ID in the payload. If this ID matches the ID notified from the controller, data is received and a response packet in which the connection ID and the sequence number in the received data are written is broadcast. When an inconsistency is detected in the sequence number of the received data, a response indicating a retransmission request can be sent and the data can be requested again from the source node. When all data transfer is completed, a broadcast packet indicating segment end is sent from the source node, and when this packet is received, the data transfer process is terminated.
【0076】
In order to reliably transfer data, it is desirable that the data transfer be resumed promptly even if the data transfer is interrupted due to the occurrence of a bus reset or some error. In the present embodiment, the problem is solved by providing a procedure for requesting retransmission.
【0077】
Next, the procedure of the retransmission request will be described with reference to FIG. 3 (b). If a bus reset occurs during data transfer, each node will follow the procedure specified by the standard. For example, if the data transfer is interrupted when the sequence number is i, each node will first follow the procedure specified by the standard. Rebuild the bus at.
【0078】
After the bus rebuild is complete, the destination node sends a retransmission request packet with the connection ID and sequence number i written in it as a broadcast packet. If the data transfer can be resumed, the source node returns an ack response. After that, the source node collates the connection ID of the received packet, and sequentially transmits the data of the data string after the requested sequence number, that is, the data string starting from the sequence number (i + 1), in a broadcast packet.
【0079】
According to the above procedure, the source node, the destination node, and the controller node can easily and surely restart the subsequent data transfer even if the data transfer is interrupted without considering the node ID. Further, as described above, in the present embodiment, there is an effect that the control procedure of the controller can be simplified even when the data transfer is interrupted.
【0080】
Next, the above-mentioned Asynchronous packet will be described with reference to FIG. The Asynchronous packet according to the present embodiment is, for example, a data packet having 4 bytes, (32 bits, hereinafter referred to as a quadlet) as a unit. In Asynchronous packets, the first 16 bits are the destination ID field, which indicates the node ID of the recipient.
【0081】
In the 1394-1995 standard, the first 16 bits indicate the destinationBus ID, and the lower 6 bits indicate the destination Physical ID, the so-called node ID. The upper 10 bits indicate transmission to the local bus when it is 3FFh, and indicate transmission to other buses from 0h to 3Fe h.
【0082】
The lower 6 bits indicate that it is a broadcast packet when it is 3Fh, and 0 h to 3Eh indicate transmission to a specific node ID. When broadcasting to the local bus as in this embodiment, the value of this field is FFFF 16.
【0083】
The next 6 bits field is the transaction label (tl) field, which is a tag unique to each transaction. The next 2 bits field is the retry (rt) code, which specifies whether the packet will attempt to retry.
【0084】
The next 4 bits field is the transaction code (tcode). tcode specifies the format of the packet and the type of transaction it must execute.
【0085】
In this embodiment, for example, a transaction of a data block write request having this value of 0001 2 is used. The next 4-bit field is the priority (pri) field, which specifies the priority. In this embodiment, since Asynchronous packets are used, the value of this field is 00002.
【0086】
The next 16 bits are the source ID field, which indicates the sending node ID. The next 48 bits are the destination offset field, which specifies the lower 48 bits of the packet's destination node address.
【0087】
The next 16 bits are the data length field, which indicates the length of the data field, which will be described later, in bytes. The next 16 bits are the extended tcode field, which is $ 0000 16 $ in the write request transaction of the data block used in this embodiment.
【0088】
The next 32 bits are the header CRC field, and the area from the destination ID field to the extended tcode field described above is called a packet header and is used for error detection of the header packet. The next field is a variable length data field, which is referred to as the packet payload. In this embodiment, if the data field is not a multiple of the quadlet, the bits less than the quadlet are padded with zeros.
【0089】
The next 32-bit field is the data CRC field, which, like the header CRC field above, is used to detect errors in the data field. FIG. 5 is a diagram in which fixed data is added to the Asynchronous packet header according to the present embodiment in the above-mentioned field. Further, FIG. 6 is a diagram showing the structure of the data field of the Asynchronous packet used in the present embodiment.
【0090】
In FIG. 6, data having the same function as that in FIG. 4 will not be described. The first 6 quadlets are header information, in which the connection ID for identifying the connection described above is written.
【0091】
The sixth and subsequent quadlets are variable-length data blocks. In this embodiment, if the data block is not a multiple of the quadlet, the bits less than the quadlet are padded with zeros.
【0092】
FIG. 7 is a diagram showing the structure of the header information. The first two quadlets are the worldwide unique IDs of the control nodes, from which the source and destination identify the control node for which the connection was set. This Worldwide Unique ID complies with the 1394-1995 standard.
【0093】
Here, a worldwide unique ID compliant with 1394-1995 was used to identify individual control nodes, but if it is unique information that can identify individual nodes that do not change even if a bus reset occurs. Anything is fine. The next 16 bits are the connection ID field described above, which identifies the connection by the data.
【0094】
Even when a plurality of controllers set the same connection ID, each node identifies an absolute logical connection by the unique ID of the control node and the connection ID.
【0095】
Further, each controller allows duplication of the connection ID number set by another controller, and the controller may use the ID set by the other controller.
【0096】
The next 8 bits are protocol type fields, which indicate the procedure for data transfer using the header information. In the figure, it is shown as Reserved.
【0097】
For the transfer procedure of this embodiment, for example, a value of 01 16 is used. The next 8 bits are the control flags field, where control data is written. The most significant bit of the control flag field is, for example, the resume request flag, and when the value of this bit is 1, it indicates that a data retransmission request has occurred.
【0098】
The next 16 bits are the sequence number field. As described above, a continuous value is used for the sequence number field for data packets sent and received with a specific connection ID. The destination node monitors the continuity of significant data by the sequence number field, and if a discrepancy occurs, makes a retransmission request to the source node.
【0099】
The next 16 bits are the confirmation number fields. This field is meaningful only when the value of the retransmission request flag described above is 1.
【0100】
When the value of the retransmission request flag described above is 1, this field indicates the sequence number of the start packet in which the retransmission request is occurring. The next 16 bits indicate the buffer size of the destination node. The next 48 bits indicate the offset address of the virtual address space (CRS space) conforming to the IEEE1212 standard of the destination node.
【0101】
(Explanation of terms) In the above-described embodiment, the following segments are divided into units of the data of the source node obtained by subtracting the header size value provided in the payload from the data value of the payload. Good, segment data is called segment data. The segment data size is called the segment data size.
【0102】
FIG. 9 shows a configuration in which two controllers have the same connection ID set on the network. It is shown that the controller node 1 in FIG. 9 has a unique node identification ID that does not change even if a bus reset or the like occurs. Here, it is assumed that the worldwide unique ID = 1 of the IEEE1394-1995 standard.
【0103】
Similarly, the controller node 2 in the figure shows that it has a node-unique identification ID that does not change even if a bus reset or the like occurs, like the controller node 1. Here, it is assumed that the IEEE1394-1995 standard worldwide unique ID = 4. Each controller sets a logical connection between the source destinations, where each logical connection ID is 0.
【0104】
In this way, even if the same connection ID is set by each controller, there is no need to negotiate between the control nodes so that the connection IDs do not overlap.
【0105】
When setting the connection, the controller announces the connection ID and the node-unique identification ID of the controller between the source destinations in advance. For each of the source and the destination, the controller for which the connection is set is identified here by the above procedure.
【0106】
FIG. 10 shows a rough flow between the entire controller, source, and destination of the present embodiment that supplements the flow described in FIG. 3 (a). (1) The controller first queries each destination for the maximum _rec size conforming to the IEEE1394-1995 standard, which represents the maximum Asynchronous Write transaction payload size that each destination can tolerate, and at the same time, the unique connection ID set by the controller. To announce. Each destination notifies the command from the controller of the max rec size, and returns as a response that the connection ID has been set.
【0107】
(2) Next, the controller has a unique connection ID set by the controller for the source, the total number N of destinations that the controller logically connects between the source and the destination, and the broadcast Asynchronous transmitted by the source. Write Announces the size of the transaction payload. As for the payload size notified from this controller to the source node, the smallest max rec size among the max rec sizes from each destination is set as the payload size from the source node.
【0108】
For the source node, the data size obtained by subtracting only the size of the fixed data size header provided in the payload of each Asynchronous Write transaction from the payload size from the controller is set as the data size of one segment, and this data size is selected. Split the created object.
【0109】
Here, the controller notifies the source of the data size of the payload and the source node calculates the data size of the segments, but even if the controller notifies the source node of the result of calculating the size of these segments in advance. Good. The source returns as a response that each is set in response to the command from the controller.
【0110】
(3) The controller selects one object from the object data of the source that the source wants to send to the source. The source returns to the controller that the object has been selected as a response. The selected object may be a still image or a moving object. It may also be text data or binary data.
【0111】
(4) When the controller knows that the source can send an object in response to the response from the source, the controller sends a command to the source to instruct the destination to start sending the selected object.
【0112】
(5) When the source receives the transmission start command from the controller, the source starts transmission of the selected object.
【0113】
(6) When the transmission of the object from the source is completed, the controller releases the selected object to the source.
【0114】
(7) At this point, the controller repeats steps (3) to (6) above if it wants to send another object.
【0115】
(8) After sending all the objects, the controller may release the unique connection ID set earlier.
【0116】
Figure 11 shows a configuration in which one controller sets the same connection ID on the network between one source and N destinations. Here, the unique connection ID is FFFF (h), but other numbers may be used. The controller performs the entire flow procedure (1) shown in FIG. 10 for each destination, and repeats it N times for convenience.
【0117】
FIG. 12 shows a case where each destination has the same receive buffer size and the object data size is equal to the receive buffer in the network configuration as shown in FIG. Here, the number of destinations is set to N = 3 for the sake of simplicity. The source has already been notified by the controller that the number of destinations connected by the controller with the same connection ID = 3.
【0118】
(B) When the transmission start command from the controller is transmitted to the source, the source sends a connection request according to the procedure described in Fig. 3 (a). (B) Each of the three destinations returns an Ack response with its own receive buffer size added when the reception preparation is completed. (C) After confirming that three Acks have returned, the source divides the object into the specified payload size from the receive buffer size in the Ack response until it reaches the buffer size of the destination. Send.
【0119】
(D) Send by setting the segment end flag indicating the end of the segment to the last segment where all the data has been transmitted. (E) When each destination receives a packet at the segment end, it returns a segment end receive response indicating that all the data has been received. (F) The controller and the source recognize that the segment end receive response has returned from all destinations and recognize the individual data transfer has been completed.
【0120】
FIG. 13 shows a model of object data transfer described with reference to FIG. In this figure, the object data is a still image with a data size of 128 Kbytes, and the segment size is divided into 500 with 256 bytes and transferred to the destination.
【0121】
FIG. 14 shows the flow of data transfer in a network in which each of the three destinations has a different receive buffer size in FIG. Here, the number of destinations is set to N = 3 for the sake of simplicity. The source has already been notified by the controller that the number of destinations connected by the controller with the same connection ID = 3.
【0122】
(G) When the transmission start command from the controller is transmitted to the source, the source sends a connection request according to the procedure described in Fig. 3 (a). (H) Each of the three destinations returns an Ack response with its own receive buffer size added when the reception preparation is completed.
【0123】
(I) After confirming that three Acks have been returned, the source divides the object into the specified payload size from the field indicating the receive buffer size in each Ack response and determines the destination. Send until the smallest buffer size is reached, and wait for the receive response from the destination with the smallest buffer size to be sent. (N) When receiving a receive response from a destination with the minimum receive buffer, the source continues to send up to the buffer size of the destination node with the next largest receive buffer, and the receive response from that destination is sent. Wait for
【0124】
(L) When receiving the receive response from the destination, the source continues to send up to the buffer size of the destination node with the next largest receive buffer and waits for the receive response from the destination to be sent. .. (W) When the source finishes sending all the data, it sends the final segment with the segment end flag and waits until it receives the segment end receive response from each destination.
【0125】
(W) When all the segment end receive responses have been received, the controller and the source recognize that the data transmission has been completed. FIG. 15 shows the case of the different receive buffers shown in FIG. 14, and here, for the sake of simplicity, the number of destinations is N = 2.
【0126】
The source object here is a still image with a data size of 128 Kbytes, but the data size is variable and is not specified. Moreover, the object may be not only a still image but also a moving image, text, binary data, or the like.
【0127】
The source divides the object into 500 with a segment size of 256 bytes and sends it up to the buffer size of destination # 1, which returns a receive response until the source continues to be the receive buffer for destination # 2. Continue to send. Here, the buffer size of the destination of # 2 is twice the buffer size of # 1, but the buffer size between the destinations is not specified by each other.
【0128】
The # 1 destination will return 3 send / receive responses, and the # 2 destination will return 1 send / receive response.
【0129】
(Second Embodiment) This embodiment relates to broadcasting in multicast. In the first embodiment shown in FIG. 5, in the Asynchronous Write packet, the first 16 bits are the destination ID field, which indicates the node ID of the recipient. When broadcasting to the local bus as in the first embodiment, the value of this field is FFFF 16.
【0130】
FIG. 16 shows the destination ID field. As explained earlier, in the IEEE1394-1995 standard, the first 16 bits of this first field indicate the destination Bus ID, and the lower 6 bits indicate the destination Physical ID, so-called node ID.
【0131】
When the upper 10 bits are 3FFh, it indicates transmission to the local bus, and from 0h to 3Feh, it indicates transmission to other buses. The lower 6 bits indicate that it is a broadcast packet when it is 3Fh, and 0h to 3Eh indicate transmission to a specific node ID.
【0132】
Here, a total of 16 bits of the upper 10-bit destination Bus ID and lower destination Physical ID defined using one specific value from 0h to 3FEh used to indicate transmission to other buses is used. Defined as a multicast ID. In the second embodiment, 3Fh is used in which the lower 6 bits indicate a broadcast. If the lower 6 bits are 3Fh, it is defined as a broadcast ID.
【0133】
In the second embodiment, of the first 16-bit fields described above, the above 10-bit destination Bus ID is used in 0h to 3FEh, which was conventionally used to indicate transmission to another bus. , A specific value is dedicated to multicast data transfer, and the lower 6 bits use destination Physical ID, so-called node ID, 3Fh, which indicates that it is a broadcast packet. An example of this is shown in FIG.
【0134】
(Third Embodiment) Here, in the second embodiment, the definition is made using one specific value from 0h to 3FEh used to indicate transmission to another bus. It is the same as the second embodiment that the multicast ID is defined as the one indicated by the field of a total of 16 bits, which is a combination of the upper 10-bit destination Bus ID and the lower destination Physical ID.
【0135】
In the third embodiment, of the first 16-bit fields described above, the lower 6-bit destination Physical ID, so-called node ID shown in the second embodiment uses a value indicating an ID addressed to a specific node. .. This indicates the node ID determined after the bus reset in 1394. It takes a value from 0h to 3Eh, and 63 node IDs can be specified for convenience.
【0136】
Here, since the upper 10 bits are designated as the destination Bus ID dedicated to multicast data transfer as shown in the second embodiment, the ID indicated by the lower 6 bits is a specific ID for multicast data transfer. The node ID shall be indicated. This is shown in FIG.
【0137】
Similar to the first embodiment, as shown in FIG. 10, the controller notifies the source and the destination in advance of the multicast ID indicated by 16 bits described in the present embodiment in advance when setting the connection. .. Also, since the upper 10 bits specify multicast, the value is fixed, so it is possible to notify only the lower 6 bits.
【0138】
At the same time, the controller notifies each of the source and destination of the 48 bits destination offset field of any CSR space of the destination. The controller can specify a 48-bit destination offset field in any number of CSR spaces for each multicast ID.
【0139】
The controller may have a 48-bit destination offset field in the CSR space of these destinations as a table. The controller sets a connection between the source and the destination for each 48-bit destination offset field in the CSR space of these multiple destinations.
【0140】
As a result, the lower 48 bits of the destination node address of the packet are specified by this field. By setting in this way, each destination recognizes the 6-bit ID set by the controller and the 48-bit destination offset field in the CSR space, and fetches the data.
【0141】
The controller manages the combination of the multicast ID and the offset address as the connection ID for each of the multicast ID and the destination offset address. Figure 19 shows an example of the table format. In addition, Fig. 20 shows the connection table that the controller has when the controller sets five independent connections between the source and the destination.
【0142】
Here, it can be seen that the controller reserves three multicast IDs for convenience, and different destination Offset addresses are set for multicast ID = 3FE00 (h).
【0143】
One destination Offset address is set for multicast ID = 3FE01 (h). Multicast ID = 3fE04 (h) also has one destination Offset address set in the same way.
【0144】
In this way, it provides a mechanism for setting multiple destination Offset addresses for one multicast ID. Therefore, even if the multicast ID is only 63, multiple connections can be set.
【0145】
The response packet to be returned to the source from the destination is written to the destination ID of Asynch's Write shown in Fig. 4 by setting the 16-bit multicast ID and destination Offset address set by the controller, and sent by the Asynchronous Write transaction. To do.
【0146】
The controller has set the destination offset field of 48 bits in the CSR space of the source node for each connection in advance, and notifying the destination of the destination offset of 48 bits in the above CSR space of the source node at the time of connection setting means that I have already explained.
【0147】
The controller also notifies each source and destination of the WWUID of the controller, which is the same as in the first embodiment and the second embodiment. In addition, the total number of destinations set with the same connection ID for each connection ID is 6 bits in word length, and the total number of destination fields shows the total number of destinations for which connection settings have been completed.
【0148】
By writing the connection ID managed by the controller in the field indicating the WWUID shown in FIG. 21 and using the multicast ID, even if a bus reset occurs, the source and destination are as shown in the first embodiment. , The connection can be automatically restored as shown in Fig. 3 (b).
【0149】
(Fourth Embodiment) In the present embodiment, the node having the multicast ID table is the Isochronous resource manager. The controller that sets the connection once reads the multicast ID held at a specific offset address in the Asynchronous Read transaction to the Isochronous resouce manager, and writes the desired multicast ID in the compare / swap lock transaction. To get the desired multicast ID.
【0150】
These procedures are the same as the procedure for acquiring Isochrnous Ch in the IEEE1394-1995 standard. Similarly, when the node having the multicast ID is the ROOT node, the procedure for the controller to acquire the multicast ID is the same.
【0151】
Since the number of nodes that manage the multicast ID is limited to one on the bus and the controller that wants to connect secures the ID to the node that manages the multicast ID, the multicast IDs are duplicated. There will be no such thing.
【0152】
Since the multicast ID and the destination offset of 48 bits in the CSR space of each source and destination are specified for each connection, the connection ID and the connection ID in the header provided in the payload in the packet as shown in Fig. 7 are specified. , WWUID is added and the source and destination need not be added. The header in the case of the fourth embodiment is shown in FIG.
【0153】
The example of the header shown in FIG. 23 shows a case where the controller queries the destination and notifies the source of the buffer size of the destination in the general flow described in FIG. In this case, it is not necessary to provide a field indicating the buffer size of the destination in the header in each payload.
【0154】
The example shown in FIG. 24 shows the connection configuration of the controller and the source destination. The controller sets a connection between the source and the destination, and is managed by the connection ID. It is the same as the first embodiment that the source and the destination determine the connection based on the connection ID notified in advance.
【0155】
Each destination has a set connection ID, multicast ID, and offset address as a table as shown in the figure. Although not shown in FIG. 24, it goes without saying that the source also has a similar table.
【0156】
FIG. 24 shows the connection configuration between the controller and the source destination. It is the same as the first embodiment that the source and the destination determine the connection based on the connection ID notified in advance.
【0157】
The controller indicates that it has set up a connection between one source and N destinations. The controller has all the connections currently set by the controller as a table.
【0158】
The controller sets the source node and the connection for a total of three destination nodes 0, 1, and 2 with the connection ID = 0 (h). Record the total number of destinations connected with the same connection ID = 3 (h) in the Total number of destination field of the table. Also, a connection is set to the destination node #n with another connection ID = 4 (h). Similarly, record the total number of connected destinations = 1 (h) in the Total nuber of destination field of the table.
【0159】
Destination nodes 0, 1, and 2 shown in FIG. 24 indicate that each destination has a table of connections set by the controller for each destination.
【0160】
As shown in FIG. 24, since the same connection ID is set for each of the destination nodes 0, 1 and 2, the connection tables of the destination nodes 0, 1 and 2 are all the same. ..
【0161】
When the source sends the same data to destination nodes 0, 1 and 2 at the same time, the connection ID = 0 (h) in the connection table of the source is changed to the destination ID in the header of the Asynchronous Write packet. In the payload defined in this embodiment, 0 (h) multicast ID = 3FE00 (h) is added, and the same table destination offset address field = FFFF E000 0000 (h) is added to the destination offset address. Send the same Asynchoronous White packet with the connection ID = 0 (h) added to the header of.
【0162】
At the time of reception, destination nodes 0, 1, and 2 compare the multicast ID = 3FE00 (h) and the destination ID = 3FE00 (h) of the captured Asynchronous Write packet from their own connection table and are the same. Therefore, the data is fetched as a packet addressed to itself.
【0163】
Next, the destination offset address of the same packet is compared with the destination offset address field = FFFF E000 0000 (h) of its own table, and since it is the same, the data is taken in as a packet addressed to itself and the connection is set. And the data is taken into the internal buffer for connection ID = 0 (h).
【0164】
The destination node #n compares the multicast ID = 3FE04 (h) and the destination ID = 3FE00 (h) of the captured Asynchronous Write packet from its own connection table, and since they are not the same, capture the data as a packet. Absent.
【0165】
When sending data from the source to the destination node #n, the connection ID = 4 (h) from the connection ID = 4 (h) in the connection table of the source to the destination ID in the header of the Asynchronous Write packet. ) Multicast ID = 3FE04 (h) is added, and the destination offset address field = FFFF E000 0000 (h) of the table is also added to the destination offset address to connect to the header in the payload defined in this proposal. Send an Asynchronous Write packet with ID = 4 (h) added.
【0166】
The receiving destination node #n compares the multicast ID = 3FE04 (h) with the destination ID = 3FE04 (h) of the captured Asynchronous Write packet from its own connection table. Next, the destination offset address of the same packet is compared with the destination offset address field = FFFF E000 0000 (h) of its own table, and since it is the same, the data is taken in as a packet addressed to itself, and the connection ID = 4 ( Load the data for h) into the buffer.
【0167】
At this time, the destination nodes 0, 1, and 2 compare the multicast ID = 3FE00 (h) and the destination ID = 3FE04 (h) of the captured Asynchronous Write packet from their own connection table, and are not the same. , Do not capture data as packets. Although not shown in FIG. 24, it goes without saying that the source also has a similar table.
【0168】
Figure 25 shows the connection configuration between the controller and the source destination. It is the same as the first embodiment that the source and the destination determine the connection based on the connection ID notified in advance.
【0169】
The controller indicates that one source and one destination have several different connections. The controller has all the connections currently set by the controller as a table.
【0170】
The controller sets the connection with the source node for the destination node with a total of three connection IDs = 0 (h), 1 (h), and 2 (h). Record the total number of destination fields connected by each connection ID = 1 (h) for each total number of destination field in the table.
【0171】
The destination node shown in FIG. 25 shows that the controller has the connection set as the destination as a table. As shown in FIG. 25, since the connection ID = 0 (h), 1 (h), and 2 (h) are set for the destination node, the connection table of the destination node is multicast for each connection ID. The IDs are the same, but the destination offset addresses are different.
【0172】
The source may send different data to the destination node for each connection. Hereinafter, such a case will be described. First, when sending data using the connection ID = 0 (h) of the connection table of the source, the multicast ID = 3FE00 (connection ID = 0 (h)) is added to the destination ID in the header of the Asynchronous Write packet. Add h) and add the destination offset address field = FFFF E000 0000 (h) of the same table to the destination offset address, and connect ID = 0 (h) to the header in the payload defined in this embodiment. ) Is added to send the same Asynchronous Write packet.
【0173】
At the time of reception, the destination node compares the multicast ID = 3FE00 (h) with the destination ID = 3FE00 (h) of the captured Asynchronous Write packet from its own connection table, and since it is the same, it is addressed to itself. Capture data as a packet. Next, the destination offset address of the same packet is compared with the destination offset address field = FFFF E000 0000 (h) in its own table, and since it is the same as connection ID = 0, it is determined that the connection is set. Then, import the data into the buffer for connection ID = 0 (h). Hereinafter, connection IDs = 1 (h) and 2 (h) are processed in the same manner.
【0174】
(Other Embodiments of the present invention) The present invention may be applied to a system composed of a plurality of devices (for example, a host computer, an interface device, a reader, a printer, etc.) or a device composed of one device. good.
【0175】
Further, in order to operate various devices so as to realize the functions of the above-described embodiment, software for realizing the functions of the above-described embodiment is provided to a device connected to the various devices or a computer in the system. The present invention also includes those carried out by supplying a program code and operating the various devices according to a program stored in a computer (CPU or MPU) of the system or device.
【0176】
Further, in this case, the program code itself of the software realizes the function of the above-described embodiment, and stores the program code itself and means for supplying the program code to the computer, for example, such a program code. The storage medium constitutes the present invention. As a storage medium for storing such a program code, for example, a floppy disk, a hard disk, an optical disk, a magneto-optical disk, a CD-ROM, a magnetic tape, a non-volatile memory card, a ROM, or the like can be used.
【0177】
Further, by executing the program code supplied by the computer, not only the functions of the above-described embodiments are realized, but also the OS (operating system) or other application software in which the program code is running on the computer, etc. Needless to say, such a program code is included in the embodiment of the present invention even when the functions of the above-described embodiment are jointly realized.
【0178】
Furthermore, after the supplied program code is stored in the memory provided in the function expansion board of the computer or the function expansion unit connected to the computer, the CPU provided in the function expansion board or function expansion unit is based on the instruction of the program code. It goes without saying that the present invention also includes a case where a part or all of the actual processing is performed by the processing, and the function of the above-described embodiment is realized by the processing.
【0179】
[Effect of the invention]
As described above, in the present invention, the effect of solving the inconvenience of the conventional communication method can be obtained. Further, even in data transfer that does not require real-time performance, it is possible to obtain an effect that data can be transferred easily and at high speed. Further, according to the present invention, it is possible to obtain an effect that a large number of communications can be performed at the same time when the communication band is not used so much. Further, according to the present invention, it is possible to easily detect the data lost due to the interruption of the data transfer, and it is possible to reliably and easily recover from the interruption of the data transfer. Is obtained. Further, according to the present invention, it is not necessary to adjust the connection IDs so that they do not overlap between the plurality of controls, so that the controller can easily and surely set the connection. Further, according to the present invention, even when a plurality of control nodes individually set a plurality of logical connections between a source and a destination, each node is information unique to the node in which the connection is set. Since it is possible to discriminate by a unique node ID such as a worldwide unique ID, it is possible to obtain an effect that each node can reliably identify a logical connection. Further, according to the present invention, data can be easily transmitted as a single segment packet to a plurality of destinations by using one logical connection ID, so that the effect of reducing the traffic on the bus can be obtained. Be done. In addition, since it is not necessary to set a plurality of connection IDs, the effect of facilitating the initial setting of the connection IDs of the controller can be obtained. Further, according to the present invention, even if the receive buffers of the respective destinations are different, the source only needs to manage and transmit only the receive buffer size of each destination, so that the sources have the same data. The flow is good, and the effect of facilitating implementation can be obtained. Further, according to the present invention, when the same object is transferred from one source node to N plurality of destinations. However, since it is not necessary to send N segments to each destination and the single segment can be efficiently forwarded, the effect of not increasing the traffic on the 1394 bus can be obtained. Further, according to the present invention, since a Bus ID other than the local bus is used for multicast, there is no unnecessary processing that a conventional 1394 standard device recognizes and receives as a local broadcast. The effect that there is no effect on the equipment can be obtained. Further, according to the present invention, since individual multicast IDs are used, a device conforming to the present invention has a multicast ID written on the destination ID of the Asynchronous Write packet as compared with the case of using the broadcast Asynchronous Write transaction. Since it is possible to determine whether or not to capture a packet simply by comparing the multicast ID notified from the controller, the effect of reducing processing can be obtained. Further, according to the present invention, it is possible to obtain an effect that 63 or more logical connections can be set by associating the destination offset address with the connection ID. Since it is possible to determine whether or not to capture the packet simply by comparing the multicast ID written in the destination ID of the packet with the multicast ID notified from the controller, the effect of reducing the processing can be obtained. Further, according to the present invention, it is possible to obtain an effect that 63 or more logical connections can be set by associating the destination offset address with the connection ID. Since it is possible to determine whether or not to capture the packet simply by comparing the multicast ID written in the destination ID of the packet with the multicast ID notified from the controller, the effect of reducing the processing can be obtained. Further, according to the present invention, it is possible to obtain an effect that 63 or more logical connections can be set by associating the destination offset address with the connection ID.
[Simple explanation of drawings]
[Figure 1]
It is a block diagram which shows the embodiment of this invention.
[Figure 2]
It is a block diagram which shows the operation of each node which concerns on this invention.
[Fig. 3]
It is a figure which shows the diagram which shows the transfer of the command and data between each node which concerns on this invention.
[Fig. 4]
It is a figure which shows the Asynchronous packet which concerns on this invention.
[Fig. 5]
It is a figure which shows the Asynchronous packet used in embodiment of this invention.
[Fig. 6]
It is a figure which shows the structure of the data field of the Asynchronous packet used in embodiment of this invention.
[Fig. 7]
It is a figure which shows the structure of the header in the data field used in embodiment of this invention.
[Fig. 8]
It is a figure which shows the conventional example.
[Fig. 9]
It is a figure which shows the peculiar identification information which a control node used in embodiment of this invention has.
[Fig. 10]
It is a figure which shows the whole flow which supplements the flow explained in FIG. 3A used in embodiment of this invention.
[Fig. 11]
It is a figure which shows the structure which one controller used in embodiment of this invention set the same connection ID on a network between one source and N destinations.
[Fig. 12]
It is a figure which shows the case where each destination used in embodiment of this invention has the same receive buffer size, and the object data size is equal to the receive buffer.
[Fig. 13]
It is a figure which shows the model of the transfer of the object data used in the embodiment of this invention.
[Fig. 14]
It is a figure which shows the flow of the data transfer in the network where each of the three destinations used in the embodiment of this invention has a different receive buffer size.
[Fig. 15]
The case of different receive buffers used in the embodiment of the present invention is shown, and here, it is a figure which shows that the number of destinations N = 2 for the sake of simplicity.
[Fig. 16]
It is a figure which shows the destination ID of Asnchronous shown by IEEE1394-1995.
[Fig. 17]
It is a figure which shows the example of the broadcast ID in the multicast used in the 2nd Embodiment of this invention.
[Fig. 18]
It is a figure which shows the multicast ID used in embodiment of this invention.
[Fig. 19]
It is a figure which shows the connection ID table which a controller, a source, and a target have used in 2nd to 4th Embodiment of this invention.
[Fig. 20]
It is a figure which shows the connection ID table which the controller used in 2nd to 4th Embodiment of this invention has.
[Fig. 21]
It is a figure which shows the header structure in the payload used in 1st to 3rd Embodiment of this invention.
[Fig. 22]
It is a figure which shows the header structure in the payload used in the 4th Embodiment of this invention.
[Fig. 23]
It is a figure which shows the header in the payload used in the 4th Embodiment of this invention.
[Fig. 24]
It is a figure which shows the table of the connection ID, the multicast ID, and the destination offset address which the controller and the destination have used in the 2nd to 4th Embodiment of this invention.
[Fig. 25]
It is a figure which shows the connection structure of a controller and a source destination.
[Explanation of symbols]
10 computer 12 Arithmetic processing unit (MPU) 14 First 1394 interface 16 First operation unit such as keyboard 18 First decoder 20 Display devices such as CRT displays 22 hard disk 24 First memory 26 Computer internal bus such as PCI bus 28 VCR 30 Imaging optics 32 A / D converter 34 Video processing unit 36 Compression / decompression circuit 38 First memory 40 Second memory 42 First data selector 44 Second 1394 interface 46 First memory control circuit 48 Second memory control circuit 50 system controller 52 Second operation unit 54 Electronic viewfinder 56 D / A converter 58 Recording section 60 printer 62 Third 1394 interface 64 Second data selector 66 Third operation unit 68 Printer controller 70 Second decoder 72 Third memory 74 Image processing unit 76 driver 78 Printer Head 200 Control Node 202 202 Source node 204 Destination node 206 Subunit inside the source node 208 object such as image data 210 First memory space inside the destination node 212 First connection 214 Nth memory space inside the destination node 216th nth connection
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US6977901B2 | Cited by | United States of America | Applicant |
| JP2012155749A | Cited by | Japan | Examiner |
| JP2012155749A | Cited by | Japan | Search report |
76 members in 7 offices
Priority claims2
| Document | Office | Kind | Date |
|---|---|---|---|
| 5726898 | Japan | A | |
| JP19980057268 | – | – | – |
Members76
| Document | Office | Kind | |
|---|---|---|---|
| EP0938218A2 | European Patent Office (EPO) | A2 | |
| EP0939529A2 | European Patent Office (EPO) | A2 | |
| EP0939530A2 | European Patent Office (EPO) | A2 | |
| JPH11252153A | Japan | A | |
| JPH11261608A | Japan | A | |
| JPH11261621AThis record | Japan | A | |
| KR19990072861A | Republic of Korea | A | |
| KR19990072864A | Republic of Korea | A | |
| KR19990072911A | Republic of Korea | A | |
| KR19990072916A | Republic of Korea | A | |
| KR19990072917A | Republic of Korea | A | |
| KR19990072918A | Republic of Korea | A | |
| CN1233023A | China | A | |
| JPH11298509A | Japan | A | |
| JPH11308255A | Japan | A | |
| JPH11308256A | Japan | A | |
| JPH11313091A | Japan | A | |
| JPH11313124A | Japan | A | |
| CN1234671A | China | A | |
| CN1234672A | China | A | |
| JPH11317755A | Japan | A | |
| CN1235303A | China | A | |
| CN1235460A | China | A | |
| CN1235462A | China | A | |
| JPH11355319A | Japan | A | |
| JPH11355320A | Japan | A | |
| JP2000032005A | Japan | A | |
| JP2000032010A | Japan | A | |
| EP0984600A2 | European Patent Office (EPO) | A2 | |
| EP0984601A2 | European Patent Office (EPO) | A2 | |
| EP0984602A2 | European Patent Office (EPO) | A2 | |
| EP0938218A3 | European Patent Office (EPO) | A3 | |
| EP0939529A3 | European Patent Office (EPO) | A3 | |
| KR100294960B1 | Republic of Korea | B1 | |
| KR100311706B1 | Republic of Korea | B1 | |
| KR100311707B1 | Republic of Korea | B1 | |
| KR100312276B1 | Republic of Korea | B1 | |
| CN1119001C | China | C | |
| US2003156093A1 | United States of America | A1 | |
| US2003172201A1 | United States of America | A1 | |
| US2003193948A1 | United States of America | A1 | |
| KR100407095B1 | Republic of Korea | B1 | |
| US6678769B1 | United States of America | B1 | |
| US6690648B2 | United States of America | B2 | |
| CN1161940C | China | C | |
| US6804250B2 | United States of America | B2 | |
| CN1179280C | China | C | |
| CN1184786C | China | C | |
| CN1184787C | China | C | |
| US6895003B1 | United States of America | B1 | |
| US7002964B1 | United States of America | B1 | |
| MY123326A | Malaysia | A | |
| MY125043A | Malaysia | A | |
| JP3814407B2 | Japan | B2 | |
| JP3862403B2 | Japan | B2 | |
| KR100664634B1 | Republic of Korea | B1 | |
| CN1301471C | China | C | |
| MY128864A | Malaysia | A | |
| EP0939529B1 | European Patent Office (EPO) | B1 | |
| DE69935940D1 | Germany | D1 | |
| JP4026979B2 | Japan | B2 | |
| MY134779A | Malaysia | A | |
| DE69935940T2 | Germany | T2 | |
| JP4046846B2 | Japan | B2 | |
| JP4065466B2 | Japan | B2 | |
| MY135481A | Malaysia | A | |
| JP4143205B2 | Japan | B2 | |
| MY138138A | Malaysia | A | |
| EP0984601A3 | European Patent Office (EPO) | A3 | |
| EP0938218B1 | European Patent Office (EPO) | B1 | |
| US7590133B2 | United States of America | B2 | |
| DE69941313D1 | Germany | D1 | |
| EP0939530A3 | European Patent Office (EPO) | A3 | |
| EP0984600A3 | European Patent Office (EPO) | A3 | |
| EP0984602A3 | European Patent Office (EPO) | A3 | |
| JP4428750B2 | Japan | B2 |
16 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Cancellation because of no payment of annual feesLAPS | LAPS | |
| Renewal fee payment (event date is renewal date of database)FPAY | FPAY | |
| Renewal fee payment (event date is renewal date of database)FPAY | FPAY | |
| Renewal fee payment (event date is renewal date of database)FPAY | FPAY | |
| Renewal fee payment (event date is renewal date of database)FPAY | FPAY | |
| Renewal fee payment (event date is renewal date of database)FPAY | FPAY | |
| Renewal fee payment (event date is renewal date of database)FPAY | FPAY | |
| Renewal fee payment (event date is renewal date of database)FPAY | FPAY | |
| Certificate of patent or registration of utility modelJAPANESE INTERMEDIATE CODE: R150R150 | R150 | |
| First payment of annual fees (during grant procedure)JAPANESE INTERMEDIATE CODE: A61A61 | A61 | |
| Written decision to grant a patent or to grant a registration (utility model)JAPANESE INTERMEDIATE CODE: A01A01 | A01 | |
| Decision of grant or rejection writtenTRDD | TRDD | |
| Written amendmentJAPANESE INTERMEDIATE CODE: A523A521 | A521 | |
| Notification of reasons for refusalJAPANESE INTERMEDIATE CODE: A131A131 | A131 | |
| Written amendmentJAPANESE INTERMEDIATE CODE: A523A521 | A521 | |
| Written request for application examinationJAPANESE INTERMEDIATE CODE: A621A621 | A621 |
Numbers
- Publication
- 11-261621
- Publication, DOCDB
- H11261621
- Publication, EPODOC
- JPH11261621
- Application
- 10057268
- Application, DOCDB
- 5726898
- Application, EPODOC
- JP19980057268
Titles2
- Japanese
- 【発明の名称】データ通信システム、データ通信装置、データ通信方法及び記憶媒体
- English
- Description: Data communication system, data communication device, data communication method and storage medium.
Classification
- IPC, 8
- G06F13 38
- G06F13 00
- G11B20 10
- H04L12 28
- H04L12 40
- H04L12 46
- H04L12 70
- H04N1 00