JP2005086556A - Controller connected to ieee 1394 serial bus - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To reduce a time required for acquiring device information of all of target devices which become control objects in a controller connected to IEEE 1394 serial bus. <P>SOLUTION: In a case where a record cannot be added in a list Y (YES at S31), a priority of device information of a concerned target is set (at S32) from a viewpoint of whether or not there is a high possibility that the concerned target is controlled by a controller on the basis of the kind of the controller and the device information of the target included in the record which becomes an addition object. Also, a record whose priority is lower than the priority of the device information of the concerned target is deleted (at S36) from the records stored in the list Y. Thus, since device information of a target whose possibility of being controlled by the concerned controller is high can be left in the list Y, a frequency of directly acquiring the device information from each target can be reduced. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

  The present invention relates to a controller device connected to an IEEE1394 serial bus, and more particularly to a technique for reducing traffic on the bus.

  Conventionally, a controller device connected to an IEEE1394 serial bus (hereinafter abbreviated as a bus) is a command for inquiring device information of each target device to each target device connected to the bus after a bus reset occurs. And each target device is controlled based on the inquiry result information returned from the inquiry target device.

  Also, in the field of connected devices connected to the bus, when there is a competition for channel acquisition of the bus interface, it is known that the channel is switched to the plug with the highest priority among the competing plugs. (For example, refer to Patent Document 1). Furthermore, in the field of this type of connected equipment, the priority of the equipment associated with the detected event is increased, and the bandwidth is preferentially allocated to the equipment with the higher priority. It is known (see, for example, Patent Document 2).

However, in the conventional controller device as described above, every time a bus reset occurs, device information necessary for control of each target device is obtained directly from each target device, so all the targets to be controlled are obtained. There was a problem that it took time to obtain device information of the device. This problem increases in proportion to the number of target devices controlled by the corresponding controller device. In addition, in the invention shown by the said patent document 1 and the patent document 2, said problem cannot be eliminated.
JP 2002-16620 A (page 1-10, FIG. 1-19) Japanese Patent Laying-Open No. 2003-18161 (page 2-6, FIG. 1-11)

  The present invention has been made to solve the above-described problem, and is connected to an IEEE1394 serial bus that can shorten the time required to acquire device information of all target devices to be controlled. An object is to provide a controller machine.

  In order to achieve the above object, the invention of claim 1 is connected to a network via an IEEE1394 serial bus, and includes a GUID (Global Unique Identification) unique to each target device from each target device on the network after a bus reset occurs. GUID receiving means for receiving information, transmitting means for sending a command for inquiring device information of the target device to a target device that is a transmission source of information including the GUID received by the GUID receiving means, and transmitting means In response to the inquiry command sent by the inquiry result receiving means for receiving the inquiry result returned from the target device of the inquiry destination, and the device information of each target device included in the inquiry result received by the inquiry result receiving means Based on the IEEE1394 system including control means for controlling each target device. In the controller device connected to the Albus, the current device information list, which is a list of device information of each target device currently connected to the bus, created based on the device information of each target device included in the inquiry result, and the bus Storage means for storing an old device information list that is a list of device information of target devices connected in the past, and when a GUID is received from each target device by the GUID receiving means after a bus reset, A first search means for searching for a record of the corresponding target device from the records in the current device information list; and a GUID receiving means when the record of the target device cannot be searched by the first search means. Records the target device corresponding to the GUID received by the old device information list. A second search means for searching from the records in the storage device and a determination means for determining whether or not a record can be added to the old device information list, and stored in the current device information list before the bus reset When a record having a GUID other than the GUID received by the GUID receiving means is included in the recorded record, the record corresponding to the deleted record is deleted from the current device information list. When adding to the old device information list and adding a record to the old device information list, if it is determined by the determining means that the record cannot be added, the device of the target device included in the record to be added The target device is likely to be controlled by the controller device based on the information and the type of controller device From the viewpoint of whether or not, the priority of the corresponding device information is set, and from the records stored in the old device information list, the record with the priority lower than the priority of the corresponding device information is the first record If the search is successful, the first record found is deleted. If the search is not successful, the device information priority is the same as the records stored in the old device information list. Search for the priority records in order from the top record, delete the first searched record, pack the records in the old device information list in order from the top, and add the records to be added to the old device information list. It was added to the end of

  In the above configuration, when adding a record to the old device information list, if the determination unit determines that the record cannot be added, the device information and controller of the target device included in the record to be added Based on the device type, the priority of the corresponding device information is set and stored in the old device information list from the viewpoint of whether the target device is likely to be controlled by the controller device. A record having a lower priority than the priority of the corresponding device information is searched from the records, and if the search is successful, the first searched record is deleted. As a result, the device information of the target device that is highly likely to be controlled by the corresponding controller device can be left in the old device information list. Therefore, based on the current device information list and the device information stored in the old device information list. It is possible to increase the probability that each target device can be controlled by the control means. Accordingly, since the frequency of directly acquiring the device information from each target device can be reduced, the time required to acquire the device information of all target devices to be controlled can be shortened.

  Also, search from the records stored in the old device information list for records with a priority lower than the priority of the device information included in the record to be added, starting with the first record. If the search is successful, the first searched record is deleted. If the search is not successful, the device information contained in the record to be added is prioritized from the records stored in the old device information list. The records with the same priority as the search were searched in order from the first record, and the first searched record was deleted. As a result, among the records with the same priority stored in the old device information list, the record with the oldest storage time can be deleted, so that the target device that has been recently controlled by the corresponding controller device can be deleted. Device information can be left in the old device information list.

  The invention of claim 2 is connected to the network via the IEEE1394 serial bus, and transmits a command for inquiring device information of the target device to each target device on the network after the bus reset occurs. Each of the query results received by the query result receiving means and the query result receiving means for receiving the query result returned from the target device of the query destination with respect to the command for inquiry sent by the sending means. Based on the device information of the target device, in the controller device connected to the IEEE1394 serial bus provided with the control means for controlling each target device, the bus created based on the device information of each target device included in the inquiry result Old device information that is a list of device information of target devices that have been connected to A storage unit that stores the list; and a determination unit that determines whether or not the record can be added to the old device information list. When the record is added to the old device information list, If it is determined that the target device cannot be added, the controller device may be controlled by the controller device based on the device information of the target device and the type of controller device included in the record to be added. Set the priority of the corresponding device information from the viewpoint of whether it is high or not, and from the records stored in the old device information list, start the record with a priority lower than the priority of the corresponding device information. If you are able to search in order from the first record, delete the first searched record. If you cannot find the record, search the old device information list. From among the records stored in the same priority record with the priority of the corresponding device information from the first record by searching sequentially, at first one so as to remove the retrieved record.

  In this configuration, the same effect as in the first aspect can be obtained.

  Further, in the invention of claim 3, in the invention of claim 2, when adding a record to the old device information list, if the record stored in the old device information list is deleted, The records are packed in order from the top, and the record to be added is added at the end in the old device information list.

  In this configuration, the records in the old device information list can be arranged in order from the oldest storage time.

  Further, in the invention of claim 4, in the invention of claim 2, when adding a record to the old device information list, if it is determined by the determining means that the record cannot be added, the record to be added is added. The priority of the corresponding device information is set in consideration of the distance between the target device and the controller device in addition to the included device information and the type of the controller device.

  In this configuration, the function described in claim 2 can be obtained accurately.

  According to the first aspect of the present invention, when it is determined that the record cannot be added to the old device information list, the device information of the target device and the type of the controller device included in the record to be added are included. Based on whether or not the target device is likely to be controlled by the controller device, set the priority of the corresponding device information, from among the records stored in the old device information list, A record with a priority lower than the priority of the corresponding device information was deleted. Also, if a record with a priority lower than the priority of the corresponding device information could not be searched, the record with the oldest storage time among the records with the same priority stored in the old device information list The record was deleted. As a result, the device information of the target device that is highly likely to be controlled by the corresponding controller device can be left in the old device information list. Therefore, based on the current device information list and the device information stored in the old device information list. The establishment of being able to control each target device can be enhanced. Accordingly, since the frequency of directly acquiring the device information from each target device can be reduced, the time required to acquire the device information of all target devices to be controlled can be shortened.

  According to the invention of claim 2, the same effect as that of claim 1 can be obtained.

  According to the invention of claim 3, when the record stored in the old device information list is deleted, the records in the old device information list are sequentially packed from the top, and the record to be added is changed to the old device information. By adding to the end in the list, the records in the old device information list can be arranged in order of oldest storage time.

  Further, according to the invention of claim 4, in addition to the device information of the target device and the type of the controller device included in the record to be added, the distance between the target device and the controller device is considered, By setting the priority of the corresponding device information, the effect described in claim 2 can be accurately obtained.

  The best mode for carrying out the present invention will be described with reference to the drawings. The embodiments described below do not cover the present invention, and the present invention is not limited to the following modes. FIG. 1 shows an electrical block configuration of a controller device according to the first embodiment and each target device controlled by the controller device. A controller device 10 (hereinafter abbreviated as a controller) is connected to each target device 20a, 20b (hereinafter collectively referred to as a target 20) to be controlled via an IEEE1394 serial bus 9 (hereinafter abbreviated as a bus). Yes.

  The controller 10 includes a CPU 11 that controls the entire apparatus, and a memory 12 (storage means) that stores various data. The CPU 11 also provides an application layer function on the IEEE1394 protocol, and also functions as a control unit in the claims. The memory 12 also includes a program (device information list creation program) 13 for creating a list storing the GUID and device information of each target device necessary for controlling each target device, the controller 10 itself, and the bus 9. A register space 14 that stores various information related to other connected devices, and various lists 16 created by the device information list creation program 13 are stored. The register space 14 stores a configuration ROM 15 that stores information such as its own GUID. The device information list creation program 13 and the CPU 11 correspond to a first search unit, a second search unit, and a determination unit in claims.

  The controller 10 also has a LINK 17 that provides a link layer level service on the IEEE1394 protocol, a PHY 18 that provides a physical layer level service, and an IEEE1394 port 19 for connecting a cable of the bus 9. Yes. These LINK 17, PHY 18 and IEEE1394 port 19 correspond to the GUID receiving means, transmitting means and inquiry result receiving means in claim 1.

  Each target 20 has a CPU 21, a memory 22, a LINK 27, a PHY 28, and an IEEE1394 port 29 as well as the controller 10, and includes a register space 24 in the memory 22. However, unlike the controller 10, the device information list creation program 13 and various lists 16 are not stored in the memory 22.

  Next, the various lists 16 stored in the memory 12 of the controller 10 will be described with reference to FIGS. The various lists 16 include a current pointer list 31 and a current list X32 (current device information list) that are lists of device information of each target 20 currently connected to the bus 9 and each of the devices connected to the bus 9 in the past. A list Y33 (old device information list) that is a list of device information of the target 20 is included. As shown in FIG. 4, the current list X <b> 32 is a list including records A to G that actually store the device information data of each target 20 currently connected to the bus 9. On the other hand, as shown in FIGS. 2 and 3, the current pointer list 31 is a circular list composed of records storing pointers * A to * G for the records A to G of the current list X32. The list Y33 shown in FIG. 5 stores the priority of device information in addition to the GUID and device information. This priority is based on the information regarding the type of the own device stored in the configuration ROM 15 in the controller 10 and the device information of the target 20, and whether or not the target 20 is likely to be controlled by the controller 10. It is set from the point of view, and the higher the number, the higher.

  In the case where the lists 31 and 32 have never been created in the past, the controller 10 inquires all the targets 20 about the functions of each device, and based on the inquiry result, the lists 31 and 32 are obtained. create. The controller 10 keeps the records in the lists 31 and 32 even when the power is turned off. When detecting the occurrence of the bus reset, the controller 10 receives the GUID from each target 20 after the bus configuration is completed, creates the GUID list 34 as shown in FIG. When the GUID of each record stored in the list X32 is not included in the GUID list 34, the record corresponding to the corresponding record in the current list X32 is stored in the list Y33. The controller 10 retains the records in the list Y33 even when the power is turned off, but does not retain the records in the GUID list 34.

  Next, the processing of the controller 10 when a new target 20 is additionally connected to the bus 9 or when the target 20 connected to the bus 9 is removed will be described with reference to FIGS. . As shown in the flowchart of FIG. 7, when a bus reset occurs (S1) and a GUID is received from each target 20 after the bus configuration is completed, the controller 10 creates a GUID list 34 as shown in FIG. (S2). Then, a new pointer list 40 (see FIG. 9) having the same format as the current pointer list 31 before the occurrence of the bus reset shown in FIG. 3 and a new list having the same format as the current list X32 before the occurrence of the bus reset shown in FIG. X42 (see FIG. 10) is created. FIGS. 9 and 10 show the new pointer list 40 and the new list X42 after the storage of the records is completed. In the stage immediately after the occurrence of the bus reset, these lists 40 and 42 contain records. Is not stored.

  Next, the controller 10 extracts one GUID from the GUID list 34 (S3), and checks whether or not a record storing this GUID exists in the current list X32 before the bus reset occurs (S4). ). For example, if a GUID as shown in FIG. 6 is stored in the GUID list 34, the first GUID a is extracted, and the record storing this GUID (a) is shown in FIG. It is checked whether or not the records A to G in the current list X32 exist. Then, as in this case, when the record storing the corresponding GUID (a) exists in the record in the current list X32 (YES in S4), the controller 10 displays the current record indicated by 30 in FIG. The corresponding record A in the list X32 is copied and stored in the new list X42 as indicated by 47 in FIG. 10, and in the new pointer list 40 as indicated by 48 in FIG. A record (data0) storing a pointer (* A) to the record A of the new list X42 is added (S5). Thereafter, the controller 10 deletes the corresponding record A indicated by 30 in FIG. 4 from the current list X32 (S6). On the other hand, when the record storing the GUID extracted from the GUID list 34 does not exist in the current list X32 before the bus reset occurs, device information acquisition processing is performed (S7).

  Next, the device information acquisition process will be described with reference to FIG. For example, a record storing the GUID (h) indicated by 37 in FIG. 6 and the GUID (o) indicated by 38 in FIG. 6 is stored in the current list X32 before the bus reset shown in FIG. not exist. If the GUID extracted in the process of S3 is such a GUID, the controller 10 checks whether or not a record storing the GUID exists in the list Y33 shown in FIG. (S21). For example, when the GUID extracted in the process of S3 is “h” indicated by 37 in FIG. 6, a record 51 with GUID = “h” exists in the list Y33 shown in FIG. 10 stores the record H (see 43 in FIG. 10) created based on the corresponding record 51 in the list Y33 in the new list X42 and, as indicated by 49 in FIG. 9, the new pointer list A record (data5) storing a pointer (* H) to the record H of the new list X42 is added to 40 (S22). Thereafter, the controller 10 deletes the corresponding record 51 from the list Y33 shown in FIG. 5 (S23). Thereby, the data in the list Y33 has the contents shown in FIG.

  If the record storing the corresponding GUID does not exist in the list Y33 in the determination process of S21 (NO in S21), the controller 10 has a device that each device has for the target 20 having the corresponding GUID. An information inquiry command is transmitted, and a record created based on the inquiry result information acquired from the inquiry target 20 is added to the new list X42 and the new pointer list 40 (S24, S25). For example, when the GUID extracted in the process of S3 is “o” indicated by 38 in FIG. 6, the record of GUID = “o” does not exist in the list Y33 shown in FIG. Transmits a device information inquiry command of the target 20 to the target 20 having the corresponding GUID (o). Based on the query result information acquired from the target 20 to be queried, the record O shown at 44 in FIG. 10 is stored in the new list X42, and the new pointer is shown at 50 in FIG. A record (data6) storing a pointer (* O) to the record O of the new list X42 is added to the list 40.

  When the above processing is repeated and the processing for all the GUIDs stored in the GUID list 34 is completed (YES in S8), the controller 10 stores the current list X32 before occurrence of the bus reset shown in FIG. Check if there are any records that have not been deleted. As a result, if a record remains in the current list X32 (YES in S9), the remaining record is added to the list Y33. For example, when the current list X32 before the occurrence of the bus reset has the contents shown in FIG. 4 and the GUID list 34 acquired after the occurrence of the bus reset has the contents shown in FIG. 6, the processing of S1 to S8 is completed. Later, in the current list X32, a record C (see 35 in FIG. 4) and a record F (see 36 in FIG. 4) that were not processed remain. Therefore, as shown in FIGS. 12 and 13, the controller 10 adds records 53 and 55 having the same contents as those records C and F to the list Y33 (S10). The process of adding records to the list Y33 will be described later. When this record addition processing is completed, the controller 10 deletes the current list X32 and the current pointer list 31 before the bus reset occurs, and creates a new list X42 shown in FIG. 10 and a new pointer list 40 shown in FIG. The current list X32 and the current pointer list 31 are held (S11).

  Next, with reference to the flowchart of FIG. 14 in addition to FIG. 4 to FIG. 13 and FIG. 15, the record addition processing to the list Y33 shown in S10 in FIG. 7 will be described in detail. When performing the process of adding a record to the list Y33, the controller 10 checks whether or not the number of records in the list Y33 is maximized (S31). When the number of records in the list Y33 has not reached the maximum (NO in S31) and the record can be additionally stored in the list Y33, it is not necessary to delete the existing record in the list Y33. 10 adds the record created based on the record remaining in the current list X32 to the end of the list Y33 as it is (S38). For example, when the maximum number of records that can be stored in the list Y33 is 6, and the records stored in the list Y33 have the contents shown in FIG. 11, the contents in the current list X32 as shown in FIG. The record 53 created based on the remaining record C is added to the end of the list Y33 as it is.

  On the other hand, when the number of records in the list Y33 is maximum (YES in S31) and no more records can be stored in the list Y33, it is necessary to delete existing records in the list Y33. . In this case, the controller 10 firstly includes the information about the type of the own device stored in the configuration ROM 15 in the controller 10 and the target 20 included in the remaining record in the current list X32 that is the basis of the record to be added. The priority of the device information of the record to be added is set based on the device information (S32). Then, the controller 10 compares the priority of the device information with the priority of each record in the list Y33 in order from the first record in the list Y33 (S33), and the device information of the record to be added is added. If a record having a priority lower than the priority is detected and detected (YES in S34), the first detected record is deleted from the list Y33 (S36), and the records in the list Y33 are sequentially ordered from the top. Stuff (S37). Thereafter, the controller 10 adds a record created based on the records remaining in the current list X32 to the end of the list Y33 (S38). For example, when the record stored in the list Y33 has the contents shown in FIG. 12, the priority of the record created based on the record F remaining in the current list X32 (see 36 in FIG. 4). Is equal to 2, the priority (2) is compared with the priority of each record in the list Y33 in order from the first record in the list Y33. Then, the record 52 (see FIG. 12) first detected among the records having the lower priority than the priority (2) of the record 55 created based on the record F is deleted from the list Y33 and shown in FIG. As shown, the records in the list Y33 are packed in order from the top, and the record 55 created based on the record F is added to the end of the list Y33.

  On the other hand, when a record having a priority lower than the priority of the device information of the record to be added cannot be detected (NO in S34), the controller 10 stores the device information of the record to be added. Records with the same priority as the priority are detected in order from the first record in the list Y33 (S35). If records having the same priority can be detected (YES in S35), the first detected record is deleted from the list Y33 (S36), and the records in the list Y33 are sequentially packed from the top (S37). Thereafter, the controller 10 adds a record created based on the records remaining in the current list X32 to the end of the list Y33 (S38). For example, when the record stored in the list Y33 has the contents shown in FIG. 13, and the target 20 with GUID = “g” connected to the bus 9 is removed, it is shown in FIG. 4, since the priority of the record 56 created based on the record G in FIG. 4 is 2, the controller 10 assigns a record having a lower priority than the priority (2) of the record 56 in the list Y33. It cannot be detected. In this case, the controller 10 detects the records having the same priority as the priority (2) of the record 56 in order from the first record in the list Y33, and deletes the first record 54 (see FIG. 13) from the list Y33. Then, as shown in FIG. 15, the records in the list Y33 are packed in order from the top, and the record 56 created based on the record G is added to the end of the list Y33.

  However, if a record with the same priority cannot be detected (NO in S35), the record is not added to the list Y33.

  As described above, according to the controller 10 according to the first embodiment, when a record cannot be added to the list Y33, the device information of the target 20 included in the record to be added, and the controller 10 From the viewpoint of whether or not the target 20 is likely to be controlled by the controller 10 based on the type information of the controller 10 stored in the configuration ROM 15, the device information of the target 20 A priority is set, and records having a lower priority than the priority of the device information of the target 20 are deleted from the records stored in the list Y33. Further, when a record having a priority lower than the priority of the device information of the target 20 cannot be retrieved, the storage time is the longest among the records having the same priority stored in the list Y33. Deleted old records. As a result, the device information of the target 20 that is likely to be controlled by the corresponding controller 10 can be left in the list Y33, so that each target 20 can be changed based on the device information stored in the current list X32 and the list Y33. Establishing that can be controlled can be enhanced. Accordingly, since the frequency of directly acquiring the device information from each target 20 can be reduced, the time required to acquire the device information of all the targets 20 to be controlled can be shortened.

  Next, the controller 1 according to the second embodiment will be described with reference to FIG. A digital tuner 60 shown in the figure corresponds to the controller 1 according to the second embodiment. In the first embodiment, the priority of the device information of the record to be added is set based on the information related to the type of the controller 10 and the device information included in the record that is the source of the record to be added. In the second embodiment, in addition to the information about the type of the controller 10 and the device information of the target 20 included in the record that is the source of the record to be added, the distance between the target 20 and the controller 10 is considered, The priority of the device information of the record to be added was set. As shown in the figure, a digital tuner 60 is connected to a digital television 61, a Hard Disc Recorder (HD-REC) 62, and a Digital Versatile Disc Recorder (DVD-REC) via an IEEE1394 cable 67 (hereinafter abbreviated as a cable). 63, a digital video home system (D-VHS) 64, and a digital video camera 65 are connected. These digital devices 61 to 65 are the target 20 as viewed from the digital tuner 60 that is the controller 1. The priority of these digital devices 61 to 65 is 3 for the digital television 61, 2 for the HD-REC 62, 2 for the DVD-REC 63, and D-VHS 64 as shown in parentheses in the figure. Is 2 and 1 for the digital video camera 65. Among these digital devices, for HD-REC 62, DVD-REC 63, and D-VHS 64, priority determined based on information on the type of controller 10 and device information included in the record that is the source of the record to be added. Although the degrees are both 2, the distance between each digital device 62 to 64 and the digital tuner 60 that is the controller 10 is different, so that the closer the distance to the digital tuner 60 is, the higher the priority is set. . This is because the closer the distance to the digital tuner 60 is, the higher the probability of being controlled by the digital tuner 60 is.

  In addition, this invention is not restricted to the said embodiment, Various deformation | transformation are possible. For example, in the first embodiment, when adding a record to the list Y, the record is added to the end of the list Y. However, the record may be added to the top of the list Y. Further, a record may be added at a position where the deleted record exists in the list Y. In addition, the “distance” as a reference when setting the priority in the second embodiment may be the total length of the cable or the number of relays from the controller to the target. Also good.

The figure which shows the electrical block structure of the controller apparatus and each target apparatus by the 1st Embodiment of this invention. The figure which shows the image of the present pointer list | wrist stored in the said controller apparatus. The figure which shows the content of the said current pointer list. The figure which shows the content of the present list X stored in the said controller apparatus. The figure which shows the content before the bus reset of the list | wrist Y stored in the said controller apparatus. The figure which shows the content of the GUID list | wrist stored in the said controller apparatus. The flowchart of the process of a controller when a new target is additionally connected to the bus or when a target connected to the bus is removed. The flowchart of the apparatus information acquisition process in FIG. The figure which shows the content of the new pointer list | wrist stored in the said controller apparatus. The figure which shows the content of the new list X stored in the said controller apparatus. The figure which shows a mode that the record of GUID = "h" is deleted from the list Y shown by FIG. The figure which shows a mode that the record of GUID = "c" was added to the list Y shown by FIG. The figure which shows a mode that the record of GUID = "j" was deleted from the list Y shown in FIG. 12, and the record of GUID = "f" was added. The flowchart of the record addition process to the list Y in FIG. The figure which shows a mode that the record of GUID = "i" was deleted from the list Y shown in FIG. 12, and the record of GUID = "g" was added. The figure which shows the distance and priority of the controller apparatus and each target apparatus by the 2nd Embodiment of this invention.

Explanation of symbols

9 IEEE1394 serial bus 10 Controller (controller device connected to IEEE1394 serial bus)
11 CPU (first search means, second search means, control means, determination means)
12 Memory (memory means)
13 Device information list creation program (first search means, second search means, determination means)
17 LINK (GUID receiving means, sending means, inquiry result receiving means)
18 PHY (GUID receiving means, sending means, inquiry result receiving means)
19 IEEE1394 port (GUID receiving means, sending means, inquiry result receiving means)
20 Target 31 Current pointer list (current equipment information list)
32 Current list X (Current device information list)
33 List Y (old device information list)

Claims (4)

Connected to the network via the IEEE1394 serial bus,
GUID receiving means for receiving information including GUID (Global Unique Identification) unique to each target device from each target device on the network after the occurrence of a bus reset;
Transmitting means for transmitting a command for querying device information of the target device to a target device that is a transmission source of information including the GUID received by the GUID receiving unit;
Inquiry result receiving means for receiving an inquiry result returned from the target device of the inquiry destination for the inquiry command transmitted by the transmission means;
In the controller device connected to the IEEE 1394 serial bus comprising the control means for controlling each target device based on the device information of each target device included in the inquiry result received by the inquiry result receiving means,
A current device information list, which is a list of device information of each target device currently connected to the bus, created based on device information of each target device included in the inquiry result, and has been connected to the bus in the past. Storage means for storing an old device information list which is a list of device information of the target device,
After a bus reset, when a GUID is received from each target device by the GUID receiving unit, a first search unit that searches a record of the target device corresponding to the GUID from the record in the current device information list;
When the record of the target device cannot be searched by the first search means, the record of the target device corresponding to the GUID received by the GUID reception means is searched from the records in the old device information list. A second search means for:
Determination means for determining whether or not a record can be added to the old device information list,
When a record having a GUID other than the GUID received by the GUID receiving unit is included in the record stored in the current device information list before the bus reset, the corresponding record is included in the current device information. Delete from the list, add a record corresponding to the deleted record to the old device information list,
When adding a record to the old device information list, if it is determined by the determination means that a record cannot be added,
From the viewpoint of whether the target device is likely to be controlled by the controller device based on the device information of the target device included in the record to be added and the type of the controller device, Set the priority of the corresponding device information,
When the records with the priority lower than the priority of the device information are searched sequentially from the first record among the records stored in the old device information list, the search is performed first. When the record is deleted and cannot be searched, the records having the same priority as the priority of the device information are searched from the records stored in the old device information list in order from the first record, Delete the first found record,
The controller device connected to the IEEE1394 serial bus, wherein the records in the old device information list are packed in order from the top and the record to be added is added at the end in the old device information list . Connected to the network via the IEEE1394 serial bus,
After the bus reset occurs, to each target device on the network, a transmission means for transmitting a command for querying the device information of the target device,
Inquiry result receiving means for receiving an inquiry result returned from the target device of the inquiry destination for the inquiry command transmitted by the transmission means;
In the controller device connected to the IEEE 1394 serial bus comprising the control means for controlling each target device based on the device information of each target device included in the inquiry result received by the inquiry result receiving means,
Storage means for storing an old device information list that is a list of device information of target devices that have been connected to the bus in the past;
Determination means for determining whether or not a record can be added to the old device information list,
When adding a record to the old device information list, if it is determined by the determination means that a record cannot be added,
From the viewpoint of whether the target device is likely to be controlled by the controller device based on the device information of the target device included in the record to be added and the type of the controller device, Set the priority of the corresponding device information,
When the records with the priority lower than the priority of the device information are searched sequentially from the first record among the records stored in the old device information list, the search is performed first. When the record is deleted and cannot be searched, the records having the same priority as the priority of the device information are searched from the records stored in the old device information list in order from the first record, A controller device connected to the IEEE1394 serial bus, wherein the first retrieved record is deleted.   When adding a record to the old device information list, if the record stored in the old device information list is deleted, the records in the old device information list are packed in order from the top and become the addition target. The controller device connected to the IEEE1394 serial bus according to claim 2, wherein a record is added to the end of the old device information list. When adding a record to the old device information list, if it is determined by the determination means that a record cannot be added,
In addition to the device information of the target device and the type of the controller device included in the record to be added, the priority of the device information is determined in consideration of the distance between the target device and the controller device. 3. The controller device connected to the IEEE1394 serial bus according to claim 2, wherein the controller device is set.

Images