MXPA99008383A - Information processing device, information processing method, and media de regis - Google Patents

Abstract

An information processing apparatus is connected to another information processing apparatus through a network and has at least one sub-unit to carry out a predetermined function. A reservation is made to cause a sub-unit to carry out a predetermined function. A reservation is made to cause a tuner sub-unit of an IRD to receive an emission on a predetermined channel at a predetermined time and record said broadcast on a DVCR sub-unit of the DVCR through an IEEE serial data transmitter. -1394: Then an IRD controller writes the reservation information of a Resource scheme board (rsb) integrated in a sub-unit of the bounce table (bbs) of the IRD and also writes reservation information of the sub-unit of the IRD. VCR is an RSB integrated in a BBS of the DVCR. With this arrangement, a double reservation is avoided

Description

INFORMATION PROCESSING DEVICE, INFORMATION PROCESSING METHOD, AND RECORDING MEDIA BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates generally to information processing apparatuses, information processing methods and recording means. More particularly, the present invention relates to an information processing apparatus connected to other information processing devices through a serial data bus according to IEEE-1394 and which reliably and individually controls integrated units. The invention also relates to an information processing method employed in the aforementioned type of information processing apparatuses and to a registration means implementing said method. 2. DESCRIPTION OF THE RELATED TECHNIQUE Audio / Visual (AV) machines are being developed that can transmit information between them through a network using a serial data bus according to IEEE-1394. In this network, it is possible to control AV machines connected to the network by using a predetermined command (set of AV / C command transactions). For example, a video image received by an Integrated Receiver Decoder (IRD) 71 for receiving digital satellite broadcasts can be recorded, as shown in Figure 1, on a digital video recorder (DVCR) 81 connected to the IRD 71 through a serial data bus according to IEEE-1394 2 (hereinafter referred to simply as "bus 2"). In addition, what is known as "registration reservations" can be done through the use of IRD 71 and DVCR 81. According to the registration reservation processing, a controller 72 of the IRD 61 controls the IRD 71 and the DVC 81. More specifically, the registration reservation features (channel, registration start time, etc.) are made in the IRD 71, and when the record start time is reached, the controller 72 of the IRD 71 controls a tuner subunit 73 to select the reserved channel (set) and to send a received video signal to the DVCR 81 over the bus 2. Simultaneously, the controller 72 transmits a registration start command to a VCR sub-unit 84 of the DVCR 81 via bus 2. In response to the registration start command transmitted from the controller 71 , the VCR subunit 84 of the DVCR 81 records the video signal supplied from the tuner subunit 73 on a magnetic tape (not shown). As mentioned above, it is possible to control the operation of DVCR 81 from another machine (in the example illustrated in figure 1, IRD 71) connected to DVCR 81 via bus 2. In this case, there may be the danger that what is known as a "double reservation" will occur.

For example, when a reservation of registration (reservation of registration A) of a digital satellite broadcast is entered in the IRD 71, the reservation information is stored in the controller 72 of the IRD 71. Then, if it is entered in the DVCR 81 a reservation of registration (booking of registration B) of a terrestrial analog broadcast, which must be broadcast at the same time as the reservation of registration A, a controller 82 of DVCR 81 receives and stores the reservation of registration B since the information As for the registration reservation A entered in the IRD 71 has not been reported to the DVCR 81. Thus, when the time arrives when both the A registration reservation and the B registration reservation start, video images are provided in a disadvantage from the tuner subunit 73 of the IRD 71 and from an analog tuner block 83 from the DVCR 81 to the VCR subunit 84 of the DVCR 81. The drawback above mentioned This originates from the fact that reservation information handled by an AV machine is not available to another AV machine connected via bus 2. In order to overcome the above-described inconvenience, a CF mode is conventionally provided for the DVCR 81. According to the CS mode, the DVCR 81 is controlled only by the controller 72 of the IRD 71 and enters the registration wait position. After the entry of the registration reservation A in the IRD 71, the DVCR 81 is established in the CS mode, thus avoiding the occurrence of a double reservation. However, since the DVCR 81 established in the CS mode goes to the reservation sphere position, it can not execute processing, such as the reproduction of video signals, thus decreasing the convenience of the operation. In addition, one information (registration start time, etc.) handled by an AV machine is not reported to the other AV machines. Because of this, when the AV machines simultaneously send information to bus 2, the amount of information can exceed the bandwidth of bus 2, causing transmission errors. SUMMARY OF THE INVENTION Accordingly, taking into account the abovementioned background, it is an object of the present invention to improve the convenience of reservation registration operation and to inhibit the occurrence of double reservation by mutually seeking information handled by the individual AV machines connected to a bus To achieve the aforementioned object, according to one aspect of the present invention there is provided an information processing apparatus that includes an input unit for entering a reservation information on a reservation of the subunit. A storage unit stores the reservation information regarding the reservation of the subunit. A supply unit reads the reservation information stored in the storage unit and supplies the reservation information to an external information processing apparatus in response to a request from the external information processing apparatus. The aforementioned information processing apparatus may further include a writing unit for writing the reservation information of the subunit of the information processing apparatus in the storage unit and for writing reservation information of a subunit of the external processing apparatus. information in a storage unit of the external information processing apparatus when a reservation is made to use the subunit of the information processing apparatus in cooperation with the subunit of the external information processing apparatus at the same time. The aforementioned information processing apparatus may further include a comparison unit for comparing the reservation information entered by the input unit with the reservation information stored in the storage unit of the information processing apparatus and the reservation information of the reservation unit. the storage unit of the external information processing apparatus that includes the subunit to be used at the same time as the subunit of the information processing apparatus. Accordingly, the writing device can write the reservation information in accordance with a comparison result obtained by the comparison unit. The writing unit may restrict the reservation information to be written to the storage unit of the information processing apparatus from the external information storage device when the writing device writes the reservation information to the storage unit of the device. of information processing. The writing unit may interrupt the reading by the external information processing apparatus of the reservation information of the storage unit of the information processing apparatus when the writing unit writes the reservation information in the storage unit of the apparatus of information processing. The storage unit may store limitation information as to a limitation of the reservation information to be stored, and the supply unit can supply the limitation information to the external information processing apparatus in response to a request from the external information processing apparatus. The storage unit may store the reservation information in a predetermined address position. Reservation information may include a subunit start time at which the use of the subunit starts and a period to use the subunit. The period to use the subunit can be established as an undefined value. The reservation information may include apparatus information on the information processing apparatus reserved by the subunit, and apparatus information may be stored in a address position subsequent to the address positions of the subunit start time and period. to use the subunit. The subunit start time may be represented by a decimal in binary code (VCD). The storage unit may further store an identification information to identify the reservation information stored. The identification information may include a unique value for the information processing apparatus that the subunit has reserved and a unique value for the reservation established in the information processing apparatus. The unique value for the information processing apparatus may be a global unique ID, and the unique value for the reservation may be a registration ID. The reservation information may include a weekly reservation information for the subunit that is reserved weekly by specifying a day of the week. The reservation information may include reservation information of intervals of the subunit that is repeatedly reserved at a predetermined interval. The storage unit can be one of the subunits. The network can be formed through the use of a serial data bus according to IEEE-1394. In accordance with another aspect of the present invention, there is provided an information processing method for use in an information processing apparatus. The information processing method includes an entry step for entering reservation information on a reservation of a sub-unit, a storage control step for controlling the storage of reservation information on the reservation of the sub-unit, and a supply step to read the reservation information stored with the processing of the storage control step and to supply the reservation information to an external information processing device in response to a request from the external information processing apparatus. In accordance with another aspect of the present invention there is provided a recording means for registering a program for controlling an information processing apparatus. The program includes an entry step for entering reservation information about a reservation of a sub-unit, a storage control step for controlling the storage of reservation information regarding the reservation of the sub-unit and a provisioning step for reading the reservation information stored by processing the storage control step and by supplying reservation information to an external information processing apparatus in response to a request from the external information processing apparatus. In accordance with the information processing apparatus, the information processing method, and the registration means, the reservation information on a reservation of a sub-unit is stored, and in response to a request from an external processing apparatus. information, the stored reservation information is supplied to the external information processing device. BRIEF DESCRIPTION OF THE DRAWINGS Figure 1 - is a block diagram that illustrates an example of the configuration of a related network system; Figure 2 is a block diagram illustrating the configuration of a network system incorporating an embodiment of the present invention; Figure 3 is a block diagram illustrating the configuration of a Bulletin Board Subunit (BBS) 14 illustrated in Figure 2; Figure 4 is a block diagram illustrating the configuration of a BBS 34 illustrated in Figure 2; Figure 5 illustrates an example of the operation of the network system illustrated in Figure 2; Figure 6 illustrates an example of the operation of the network system illustrated in Figure 2; Figure 7 is a flow chart illustrating the network system operation illustrated in Figure 5; Figure 8 is a flow chart illustrating the operation of the network system illustrated in Figure 5; Figure 9 is a flow diagram illustrating the operation of the network system illustrated in Figure 5; Figure 10 illustrates the format of the Write command Open; Figure 11 illustrates the format of a Read command; Figure 12 illustrates the format of a Create command; Figure 13 illustrates the subfunction_l illustrated in Figure 12; Figure 14 illustrates the details of the subfunction_l illustrated in Figure 13; Figure 15 illustrates the values of the fields illustrated in Figure 14; Figure 16 illustrates the format of a Write command Descriptor; Figure 17 illustrates the format of a Close command; Figure 18 illustrates another example of the operation of the network system illustrated in Figure 2; Fig. 19 is a flow diagram illustrating the processing for establishing the Object ID; Figure 20 illustrates the BBS format; Figure 21 illustrates the raster_list_list_id illustrated in Figure 20; Figure 22 illustrates the RSB format; Figure 23 illustrates the format of the allowed write_specific information illustrated in Figure 22; Figure 24 illustrates the format of the board_type illustrated in Figure 23; Figure 25 illustrates the format of the object_input illustrated in Figure 22; Figure 26 illustrates the format of the resource programming entry illustrated in Figure 25; Figure 27 illustrates the start time format illustrated in Figure 26; Figure 28 illustrates the format of the Duration illustrated in Figure 26; Fig. 29 illustrates the format of the repeat_type illustrated in Fig. 30; Figure 30 illustrates the format of the_repetition information illustrated in Figure 26; Figure 31 illustrates the format of the_repetition information illustrated in Figure 26; Figure 32 illustrates the format of the info blocks illustrated in Figure 26; Figure 33 illustrates the format of the information_specific_of__type_of_tablero_supported illustrated in Figure 20; and Figure 34 is a block diagram illustrating an example of the configuration of a computer. DESCRIPTION OF THE PREFERRED MODALITIES The configuration of a network system incorporating an embodiment of the present invention is described below with reference to Figure 2. In the specifion, the term "system" indes an entire apparatus consisting of several devices, means , etc. This network system is formed by an IRD 1 and a DVCR 3 connected to each other through a bus 2. In addition, IRD 1 and DVCR 3, electronic machines equipped with a terminal according to IEEE-1394, such as Personal computers, hard drives, compact disc players (CDs), monitors, digital camcorders, and mini-disc (MD) players (commercial name), can be connected to bus 2. Electronic machines, such as IRD 1 and the DVCR 3, connected to the bus 2 are known as "units". Between the units, it is possible to read information from the individual units and write information in the individual units by using a descriptor (Descriptor) defined in the general specifion of AV / C digital interface command setting of the transaction set AV / C command (hereinafter referred to as "general AV / C"). The general AV / C details can be found at http://cxn02.net.arch.sony.co.jp/Doc/. The functions provided by the units are known as "subunits". A controller 11 of the IRD 1 controls the entire IRD 1 by receiving a channel selection operation or a registration reservation operation carried out by a user. The controller 11 also controls the DVCR 3 by using a predetermined command (set of AV / C command transactions). A CS 13 antenna receives digital signals from a digital satellite broadcast transmitted through a communion satellite (not shown) and sends the digital signals to a tuner subunit 12. The tuner subunit 12 extracts a predetermined channel signal to from the digital signals input from the CS 13 antenna under the control of the controller 11, and sends the extracted signal to a VCR sub-unit 33 of the DVCR 3 via the bus 2. The controller 11 also searches for information stored in a bulletin board sub-unit (BBS) 34 of the DVCR 3. A BBS 14, which serves as a subunit of IRD 1, stores information regarding registration reservations received and determined by controller 11 (details are discussed below with reference to figure 20). A controller 21 of the DVCR 3 controls the entire DVCR3 receiving a playback instruction operation or a registration reservation operation performed by a user. An analog tuner block 32 extracts a predetermined channel signal from the analog signals input under the control of the controller 31 and sends the extracted signal to the VCR sub-unit 33. The VCR sub-unit 33 registers on a magnetic tape (not illustrated) ) a video signal input from the analog tuner block 32 or a video signal input from the tuner subunit 12 of the IRD 1 via the bus 2. The BBS 34 handles registration reservation information as to the DVCR 3. The tuner subunit 12 and the BBS 14 are subunits of the IRD 1 and the subunit of VCR 33 and the BBS 34 are subunits of the DVCR 3. The analog tuner block 32 is not a subunit because it is not controlled by another unit via bus 2 even when executing one of the functions of the DVCR 3. In this network system, when a registration reservation of a digital satellite emission is carried out, a user uario enters the characteristics of the registration reservation (channel, registration start time, etc.) in the IRD 1. If the reservation entered does not cause a double reservation, it is accepted, and the reservation information is written in the BBS 14 of the IRD 1. BBS 14 is formed, as shown in Figure 3, of a Resource Programming Board (RSB) 51 and a Programmed Action Board (SAB) 52. The SAB 52 stores all the information about the record reservations entered from controller 11 of IRD 1 and from a controller of another unit (for example, controller 31 of DVCR 3). That is, the SAB 52 stores all the information to control a series of operations to cause the tuner subunit 12 of the IRD 1 to receive information at a predetermined time and to register it on the VCR subunit 33 of the DVCR 3.

In contrast, the RSB 51 stores only reservation information for the tuner subunit 12 of the IRD 1 among all the information about the registration reservations (including reservations established by other units). Even if the operation of the VCR subunit 33 is related to the operation of the tuner subunit 12, the RSB 51 does not store reservation information of the VCR subunit 33. The RSB 51 makes the stored information public in response to a request not only of the controller 11 of the same unit, but also of the controller of another unit (for example, the controller 31 of the DVCR 3). Similarly, the BBS 34 of the DVCR 3 is formed, as shown in Figure 4, of an RSB 61 and a SAB 62. The SAB 62 stores all the information about registration reservations entered from the controller 31 of the DVCR 3 and from another controller of another unit (for example, controller 11 of IRD 1). In contrast, the RSB 61 stores only reservation information for the VCR subunit 33 of the DVCR 3 among all the information on registration reservations entered in the controller 31 of the DVCR 3 and in the controller 11 of the IRD 1. Even if the operation of the tuner subunit 12 is related to the operation of the VCR sub-unit 33, the RSB 61 does not store reservation information of the tuner subunit 12. The RSB 61 makes the stored information public in response to a request not only from the controller 31 of the same unit but also of the controller of another unit (for example controller 11 of IRD 1). Details of the information stored in the RSBs 51 and 61 and made public will be described in detail below with reference to Figure 22. The operation related to both the RSB 51 and the RSB 61 is discussed below with reference to Figure 5 For example, when a registration reservation (which causes the tuner subunit 12 to receive channel 48 from 8:00 pm to 9:00 pm on October 16 and record the video signal received in sub-unit 33 of the VCR of the DVCR 3) is input to controller 11 of IRD 1, as shown in figure 5, controller 11 establishes an ID (object ID BB) (in this mode, ID_X) unique to the reservation, and stores all the information on the registration reservation in the SAB 52. The controller 11 also stores in the RSB 51 the established ID (ID_X), the time and date (from 20:00 to 21:00 on October 16), as well as information ( ID information) to specify the related subunit (in e This mode, tuner subunit 12) of the IRD 1. The controller 11 additionally stores in the RSB 61 of the DVCR 3 the established ID (ID_X), the time and the date (from 20:00 to 21:00 on October 16 ), as well as information (ID information) to specify the related subunit (in this mode, the VCR sub-unit 33) of the DVCR 3. Then, when a registration reservation (which causes the analog tuner block 32 to receive the third channel from 8:00 p.m. to 9:00 p.m. on October 16 and record the video image received in the sub-unit of VCR 33) is input to controller 31 of DVCR 3, as shown in figure 3, the controller 31 it refers to the RSB 61 and determines if the information of the entered registration reservation links the reservation information that has been accepted and made public for the RSB 61. In this case, since the registration time, that is, 20 : 00 a.m. to 9:00 p.m. on October 16, the entered reservation is spliced With the registration time of the reservation accepted, the registration reservation entered is not accepted. If it is determined that the information of a reservation or coincides with the information of another reservation, the registration reservation entered is accepted. All information is stored in the SAB 62, and information on the VCR subunit 33 is stored in the RSB 61. Details of the reservation processing described above (containment unit search processing) are discussed below with reference to the flowcharts of Figures 7 to 9. In step Sil, a user establishes a reservation in controller 11 of IRD 1. That is, in the example illustrated in Figure 5, a reservation to cause the tuner subunit 12 to receive channel 48 from 20:00 to 21:00 on October 16 and transfer the received video signal to the VCR subunit 33 of the DVCR 3 and register it. Simultaneously, in step S12, the controller 11 controls the RSBs of the units including the white subunits so that they are in the Open Write state. In the example illustrated in Figure 5, the white subunits are the tuner subunit 12 of the IRD 1 and the VCR subunit 33 of the DVCR 3. Accordingly, the controller 11 first selects the tuner subunit 12 and sends a command of Write open such that the RSB 51 of the IRD 1 including the tuner subunit 12 reaches the Open Write state (the state that allows writing). In practice, however, the RSB 51 and the controller 11 are in the same unit, i.e., the IRD 1, and are not connected via the bus 2. Accordingly, the controller 11 controls the RSB 51 as if an Open Structure command will be supplied to RSB 51 via bus 2.

After the RSB 51 of the IRD 1, including the tuner subunit 12 has reached the open structure state, the controller 11 controls the RSB 61 of the DVCR 3 including the remaining white subunit, i.e. the sub-unit of VCR 33, for that is in the state of Open Writing. In this case, the controller 11 sends an Open Write command having the format illustrated in FIG. 10 to the RSB 61 (controller 31) of the DVCR 3 via the bus 2. The Open Write command mentioned above is a type of Open Descriptor commands to access a predetermined white address space. As shown in Figure 10, the value 08? 6, which represents the Open Descriptor, is established in the operation code. The value lOie, which indicates the Object List Descriptor defined by the list ID, is set in operand 0 as the type_of_descriptor that represents the type of the descriptor. In operand 1 and in operand 2, list IDs (in this mode, 00 and 01) of the RSBs to which they must have access (to be in the Open Write state) are described. The value 03? 6, which indicates that descriptors must be opened to gain access, such as reading or writing, is established in operand 3 as a subfunction. The value 00 is set in operand 4 as a preserved value. Referring again to FIG. 7, in step S13, the controller 11 reads the descriptor length and the list_specific information field (FIG. 22) of the RSB 51 within the BBS 14. The read operation is carried out using, for example , the Read command illustrated in FIG. 11. In this case, since the controller 11 and the RSB 51 are not connected via the bus 2, as indicated above, the above data is read directly from the controller 11 to the RSB 51. Without However, if the controller 11 reads data from the RSB 61 of the DVCR 3, the Read command illustrated in FIG. 11 is sent to the RSB 61 (the controller 31) via the bus 2. As illustrated in FIG. 11, the value 09? 6, which represents the reading descriptor, is set in the operation code, which is the Read header. In the subsequent operand 0, the descriptor identifier is described to identify the descriptor to be read. In the read operation in step S13, the descriptor identifier is set by the list ID. More specifically, 00? 6 to 0Di6 of the address_address of the information field_specific_of_list with allowed script of the postop RSB in FIG. 23 are established. When the Read command is transmitted, FF is set in the state_of_result_ofreading. When the Read command is returned from the blank in response, the read result is set. In the length_of_data, the number of bytes of data to be read from the blank is described. When the data length is set to zero, all lists are read. The direction in which the reading starts is established in the address. When 00 is set in the address, the reading starts from the header.

With reference again to Figure 7, in step S14, the controller 11 extracts for the RSB 51 the maximum length of the view (the maximum_size_of_list_of_objects illustrated in Figure 23), the maximum number of entries in the list (the maximum_number_of_entries_of_objects illustrated. in Figure 23), and the maximum byte length of each entry (the maximum_in_entry_of_object size illustrated in Figure 23). The controller 11 then determines in step S15 whether data (reservation information) to be recorded in the RSB 51 cause an excess of the maximum length of the list extracted in step S14. If the result of step S15 is no, the process proceeds to step S16 in which the controller 11 determines whether the value obtained by subtracting the current number of entries from the maximum number of entries from the list extracted in step S14 is greater. that 0, that is, if there is an available entry to write data. If the result of step S16 is yes, the process proceeds to step S17 in which the controller 11 determines whether the value obtained by subtracting the length of the input from the reservation information to write the maximum length of the extracted input in step S14 it is greater than 0, that is, if there is space available for the input in which the data is written. If any of the conditions raised in steps S15 to S17 are not met, the process proceeds to step S18 in which the controller 11 indicates a warning, such as "complete reservations" to the user. This allows the user to recognize that reservations can no longer be made. If all the conditions stated in steps S15 to S17 are met, reservation information may be written in RSB 51 and a determination is made further in steps S19 to S25 of figure 8 if the time of the reservation entered by the user connects with the time of the reservation that has already been accepted, that is, a double reservation occurred. More specifically, in step S19, a variable y is initialized to zero. It is then determined in step S20 whether the value obtained by subtracting the variable i from the number of entries, ie the number_of_entries, recorded in the RSB 51 is greater than 0, that is, if all the entries recorded in the RSB 51 have been searched. If the result of step S20 is yes, the process proceeds to step S21 in which the controller 11 reads the entry_of_obj eto (i) (125) in this case, the_object_in_ (0) illustrated in the RSB 51. Even though the Reading operation in step S21 is also carried out by using the Read command illustrated in Figure 11, the descriptor identifier is set by the object position. At the object_income (i), the time information of the registered reservation (the start_time and the duration illustrated in Figure 26) and the subunit ID information (the_e_unity_ID_type (0) illustrated in Figure 32) are stored as which will be described later. Then, the controller 11 determines in step S22 whether the time information (start_time and duration) entered by the user in step Sil is spliced with the time information (start_time and Duration) read in step S21. If the result of step S22 is yes, the process proceeds to step S23. In step S23, the controller 11 determines whether the subunit in which the reservation was established in step Sil (in this case, the tuner subunit 12) matches the subunit read in step S21 (the_e_unity_ID_type). If the results of step S23 is yes, the time and subunit read in step S21 correspond to those entered by the user. Accordingly, the process proceeds to step S25 where the controller 11 indicates, a warning, as for example "reservations are splicing". As a result, the occurrence of a double reservation can be avoided. If it is in step S22 that the time information entered by the user does not splice the time information read in step S21, or if it is found in step S23 that the subunits determined in steps Sil and S21 do not coincide with each other even if a time splice has occurred in step S22, there is no possibility of generating a double reservation. Accordingly, in step S24, the variable i is i is incremented by 1, and the process returns to step S20. A processing similar to the processing described above is repeated until it is determined in step S20 that the value obtained by subtracting the variable i from the number_of_inputs is not greater than 0, that is, all the entries_of_obj eto (i) stored in the RSB 51 are searched for the purpose of determining if there is no spliced reservation. If it is found in step S20 that the value obtained by subtracting the variable i from the number_of_inputs is not greater than 0, that is, that all the object_inputs (i) have been searched, the process proceeds to step S26. In step S26, the controller 11 sends a Create command to the RSB 51 and creates an object entry in the RSB 51. In this case, the Create command is not actually sent, and the processing is executed as if the Create command was sent, as stated above. When the object entry is created in RSB 61, the Create command is sent. The steps S15 to S28 described above can be executed after the determination in step S20 that not all entries have been fully searched. The Create command described above is described in detail below with reference to figures 12 to 15. Figure 12 illustrates the format of the Create AV / C command. Figure 13 illustrates the value that can be specified by the subfunction_l illustrated in Figure 12, and in this mode, 01 (create a new object and its consequent list) is used. Figure 14 illustrates the format of the subfunction_ specification_l for subfunction_l = 01 which is illustrated in Figure 12. Figure 15 illustrates the values of the individual fields presented in Figure 14. If the values, 20, 22 and 11 are respectively set, as shown in figure 15, in the fields, that is, identifier_descriptor_d where the identifier_of_descriptor_what_l and the identifier_of_descriptor_what_2, of figure 14, the meaning is to create a new object and its consequent view. Details of the Create AV / C command are indicated in IEEE-1394 (see Internet page http: //www.1394 TA.org), and the formats used in this mode are extracted from the specifications of the standards according to IEEE 1394 ( improvement of the general specification AV / C 3.0 version 1.0 FC2 and TA document 1999005 general specification of bulletin board subunit AV / C 1.0, version 0.99: 149). The information descriptors that form the dashboard (Information List Descriptor) include descriptors in which you can write and descriptors that can be read, and the type of list is used to differentiate the two types. To write new information in the AV / C descriptor (AV / C descriptor) from an external source, the following method can be used as a typical example. The controller sends the command Create above described to the target, and then the target forms a model to write information, the controller controls again a writing of specific information. More specifically, when writing information first, the controller designates a desired list and sends the Create AV / C Descriptor command. Upon receiving this command, the blank forms the object based on the model that has the data structure specified by the General AV / C. The model that has the data structure designated by the General AV / C has a field of the object ID. In the list using the AV / C descriptor, the object ID is handled by the target, namely, when the object is created, the target adds a unique ID to the object and has the function of handling the ID. The object ID is an ID number to uniquely specify the object in the list, and the target is required to prevent multiple storage of Ids. The BBS simply offers information, and the object IDs are handled by the controller. When the Create command is sent to a subunit, inconsistencies may arise. When an object is created, the object ID, which must be handled by the controller, is under the control of the target. After sending the Create command, the controller has to follow the write controller. In this way, the processing is divided into several steps. Therefore, if the controller is accidentally disconnected from the bus while information is being written to the BBS, an imperfect object may be created. To overcome the situation described above, there is a need for a system to specify the imperfect object and to eliminate it correctly. In this mode, the writing of information in the BBS is restricted in such a way that imperfect objects are specified. When creating an object, the target, in this mode, the (DVCR 3) first allocates management numbers temporarily (all 0 to a Global Unique ID (GUID) of the object ID. The object ID consists of the GUID and Registration ID The driver then writes information to the object, and if the write operation is carried out correctly, the controller overwrites the GUID, according to the procedure described above, if the write operation was carried out. As a result, such objects can be specified as imperfect objects that were created accidentally while the writing operation was being carried out. they are being written can be identified in a unique way It is also possible to distinguish correctly written objects from imperfect objects and easily eliminate imperfect objects (objet invalid). This may be additionally possible to effectively employ a finite memory provided for an electronic device. Accordingly, according to the aforementioned method, the objects that are being written can be specified simply by temporarily assigning 0 to the GUID. You can easily create, therefore, a programmatic to eliminate imperfect objects. In step S26 of Figure 9, the Insert command can be used instead of the Create command. Referring again to FIG. 9, the process proceeds to step S27 in which the controller 11 writes the reservation content in the input_specific information fields (FIGS. 26 to 32) of the RSB 51. That is, the start_time, the Duration , and the Repeat_Information, and the white subunit (type_e_Unit_of_subunity) are written. Figure 16 illustrates the command Write descriptor sent from controller 11 when step S27 is executed. As previously stated, since the controller 11 and the RSB 51 are not connected via the bus 2, the controller 11 directly writes the information in the RSB 51 without sending the Write descriptor command. Conversely, when the controller 11 writes information in the RSB 61, the Write Descriptor command is sent. In the operation code, which is the header of the Write Descriptor command, the value OA? 6 indicated by the Write Descriptor is established. In operand 0, the descriptor identifier to identify the descriptor of the information to be written is determined by the object position. Then, the subfunction is set to the value 50? D, which represents the partial_replacement, thus executing a partial insertion or a partial deletion. When an insert is made, a new descriptor is inserted immediately before the descriptor defined by the operand specified by the identifier_of_descriptor. When deleting, the descriptor defined by the identifier_of_describer is deleted. The group_marker is used to update the data that can not be divided when written in the descriptor. In this modality, the value 00? 6 (immediate) is established, which indicates that the data is written immediately in the descriptor. The length_of_data_of_replacement represents the number of bytes of the operand, that is, the length of data to be written. The address indicates the position in which the processing is carried out. If the replacement_data_length indicates 0, a partial deletion is carried out, in which case the operand of the replacement_data does not exist. In this case, the length_of_original_data is greater than 0, and it indicates the number of bytes to be erased. If the original_data_length is 0, a partial insertion is made, in which case the replacement_data_length is greater than 0, and indicates the number of bytes to insert. By reference again to FIG. 9, the process proceeds to step S28 in which the controller 11 closes the list, i.e., the RSB 51. Simultaneously, the controller 11 sends the Close command illustrated in FIG. 17 to the RSB 51 As stated above, the controller 11 directly closes the RSB 51 without sending the Close command since the controller 11 and the RSB 51 are not connected through the bus 2. If the controller 11 closes the RSB 61 of the DVCR 3, it is send the Close command. The format of the Close command illustrated in Figure 17 is practically similar to the Open Write command illustrated in Figure 10, except for the following. The Open Write command subfunction indicates 03? 6 which represents Open Script, while the Close command subfunction indicates 00? 6, which indicates Close. The process then continues until step S29 in which the controller 11 determines whether there are other resources related to the reservation. In this case, even though the processing for making a reservation in the tuner subunit 12 has been terminated, further processing is required to make a reservation in the VCR subunit 33 of the DVCR 3. Consequently, the process returns to step S12 in which a processing similar to the processing performed in the RSB 51 is carried out in the RSB 61 of the DVCR 3. If it is determined in step S29 that there are no other resources related to the reservation, the processing is terminated. As discussed above, a series of registration reservation operations have been performed to cause the tuner subunit 12 to receive a video signal and to register it on the VCR subunit 33. It is now considered that the reservations are made separately , as shown in Figure 18, that is, a reservation of reception is made in the IRD 1 and a reservation of registration in the DVCR 3. More specifically, a reservation is entered in the controller 11 of the IRD 1 to cause the tuner subunit 12 receives a predetermined channel (channel 48) for a predetermined period of 20:00 a.m. to 9:00 p.m. on October 16, and another reservation is entered in the controller to cause the sub-unit of VCR 33 to initiate registration during a predetermined period from 8:00 pm to 9:00 pm on October 16th. It seems to the user that the two reservations are the same reservation. However, it appears to the IRD and DVCR 3 that the two reservations have been made separately and, different IDs (ID Y of object BB, and ID Z of object BB) are respectively set in IRD 1 and in DVCR 3 and are stored in the corresponding RSB 51 and RSB 61. Even when reservations are made separately in the individual units, a reservation processing can be carried out in a manner similar to that indicated by the flow diagrams of Figures 7 to 9. However, if reservations are made separately even when the subunits of the different units are used in cooperation among them, it must be reviewed by the user the occurrence of double reservation. The processing to establish the Object ID is described below with reference to the flow chart of Figure 19. After having made a reservation of registration using the DVCR 3 in the IRD 1 by the user and after being detected by the user. controller 11, the above-mentioned reservation processing (containment unit search processing) illustrated in Figures 7 to 9 is carried out. When the registration reservation is accepted, the processing mentioned above begins to establish the object ID. In this embodiment, the object ID is used to identify the reservation (event) to begin at a predetermined time for a predetermined period. The object ID has 72 bits in which the most significant 64 bits are used for the unique ID for the unit that processes all the information related to the reservation, that is, for the GUID of the unit, and the 8 least significant bits they are used for the unique value established in the unit, that is, for the registration ID. In this way, the object ID to identify the Event is formed from the GUID and the registration ID. Thus, processing can be easily executed to set the Object ID. It is necessary to identify the object ID between the individual units connected via bus 2. The reason for this is as follows. The content of the RSB of a unit can be read by the other units, and the processing can be executed simultaneously by the subunits of the different units in cooperation (in relation) between them. Therefore, it is necessary that individual units review any processing to be done in cooperation between them. Among the units connected via bus 2, the object IDs can be set sequentially from the number 1 each time an Event is generated. However, if a predetermined unit establishes an Object ID for a predetermined Event, it must review the contention IDs to read all Object IDs that have already been established in the other units. In this mode, however, the GUID is included in the object ID, and the value of the GUID is reliably unique for each unit. Therefore it is essential only that each unit set the registration ID as a unique ID, which does not compete with the other registration IDs, within the same unit. Accordingly, the object ID obtained by combining the GUID with the record ID is reliably different from the Object IDs established by the other units. Thus, each unit establishes the Object ID for the Event to be recorded in the RSB in accordance with the processing indicated by the flow chart of Figure 19. In step S41, the controller 11 issues a provisional ID to uniquely identify the reservation information within IRD 1 as a registration ID of the object ID (consisting of GUID and registration ID). In step S42, the controller 11 extracts one of the Events recorded in the RSB51, and additionally extracts the record ID of the object ID corresponding to the Extracted Event. The controller 11 then determines in step S43 whether the provisional ID issued in step S41 matches the record ID extracted in step S42. If the result of step S43 is yes, the process returns to step S41 where the provisional ID changes. The processing of steps S41 to S43 is repeated until the provisional ID does not correspond to the registration ID. If it is found in step S43 that the provisional ID does not match the registration ID, the controller 11 determines in step S44 whether all the Events on the related Subunit that have been made public in the RSB 51 have been extracted. If the result of step S44 is no, the process returns to step S42, and the processing of steps S42 to S44 is repeated until it is determined in step S44 that all Events have been extracted. If the result of step S44 is yes, the process proceeds to step S45. In step S45, the controller 11 adds the provisional ID (record ID) generated in step S41 to the unit ID (GUID) of IRD 1, thus generating the object ID. The object ID is then established in RSB 51. As discussed above, the Object ID can be established by simply checking the RSB corresponding to the related subunit (without the need to review the RSBs of the units that include unrelated subunits). The reason for this situation is the following, as it was raised above. Since the object IDs of the RSBs of the other units include the unique GUIDs for the individual units, it is not possible for the object IDs set by the other units to correspond to the Object ID set by the corresponding unit. As a result, the Object ID can be easily established. -The BBS is discussed in more detail below. Figure 20 illustrates the format of the identifier descriptor sub-unit that forms the BBS. The length_of_descriptor represents the length of the descriptor. Generation_ID indicates which AB / C descriptor format of the BBS is used, and generally, it is set to 00? 6. The size_of_ID_of_list designates the number of bytes of the ID. The size_of_ID_of_object indicates the number of bytes of the object ID. The size_of_prosition_of_object represents the number of bytes of the position of the object in the list. The number_of_list_of_object_raiz indicates the number of root object lists to which the BBS directly relates. The ID_of_list_of_object_raix_x (x = 0, 1, 2, .... n-1) represents the ID of each of the lists of root objects to which the BBS is related. The subunit_dependent_information_length refers to the length of the subunit_dependent_info, and the format and content information in which the DBS is descending is set in the subunit_dependent_info. The información_dependiente_de_subunidad includes longitud_de_campos_de_bloques_de_no_info, the versión_de_subunidad_de_tablero_de_boletin, the número_de_tipo_de_tablero_soportado (n), the tipo_de_tablero_soportado_especifico_de_longitud (0), the tipo_de_tablero_soportado_especifico_de_info (0) tipo_de_tablero_soportado_especifico_de_infor (n-1), and the specific type of supported board length (0) to tipo_de_tablero_soportado_especifico_de__longitud (n -1), which represents the lengths of the type_of_table_support_specific_of_info (0) up to the type_of_table_supported_specific_of_info (n-1). The BBS also includes the manufacturer_dependent_length, which implies the length of the manufacturer_dependent_info and the manufacturer_dependent_info, which represents the information that depends on the manufacturer. If the value of the item_array_list_ID indicates the RSB, a default value of 1001? 6 is set, as shown in Figure 21. In this way, by setting the ID representing the RSB (described as a resource scheduling list in Fig. 21) in the predetermined value, processing for reading the RSB can be facilitated. Figure 22 illustrates the format of the RSB. The length_of_descriptor indicates the length of the RSB. The type_of_list indicates whether the RSB is read only or if writing is allowed. The read-only list indicates that only reading is allowed, and the allowed writing list indicates that both writing and reading are allowed. The information_specif_size_of_list indicates the length of the information_specifies_of_list, and the content of information_specifics_of_list varies according to the type_of_list. The information presented in figure 23 is established in the list_specific information with allowed structure. The length_of_fields_of_block_of_no_info represents the number of bytes of the non-information fields. If the type_of_table is the Resource Programming Board, as shown in Figure 24, then Oliß is set. The maximum_size_of_list_of_objects represents the maximum size of the list of objects. The maximum_number_of_object_input indicates the maximum number of object entries in the list. The maximum_size_of_object_input indicates the maximum size of each object entry. If there is no limit imposed on the maximum size of the object list, the maximum number of object entries, and the maximum size of the object entry, 0000? 6 is set in each of the fields. The three previous fields are significant for the controller to recognize the capability of the object list or object entry. The length_of_dependent_information_of_type_of_tablero designates the length of the information_dependent_of_type_of_table, and the unique information for the type of board is established in the information_dependent_of_type_of_table. The object_input is configured specifically as illustrated in Figure 25. The length_of_descriptor indicates the length of the descriptor. If the input_type is a dashboard entry descriptor, the value 80? 5 that the Dashboard represents is set. The object_ID is made up of the GUID_of_register_device and the_register_ID. The registration_device indicates the controller that has written (registered) information in the DBS, and therefore, the GUID_of_registration_device represents the GUID of the controller. The registration_ID designates an ID assigned to the Event within the unit. The input_spec_spec_size_size presents the size of the input_specific information. Figure 26 illustrates the format of the entry_specific information. The length_of_block_of_no_info indicates the number of bytes of the block fields of no_info before the_request_info. The start_time represents the day and year in which the event starts, as illustrated in figure 27. The year has 16 bits, the four numbers are each represented by an ordinarily coded decimal (BCD) of 4 bits. The month has 8 bits, the two numbers are each represented by a 4-bit BCD. The day has 8 bits, the two numbers are each indicated by a BCD of four bits. The time has 8 bits, the two numbers are each indicated by a BCD of four bits. The minute has 8 bits, the two numbers are each indicated by a 4-bit BCD. The second has 8 bits, the two numbers are each represented by a 4-bit BCD. The start_time is easily identified by its location as the BCD. Time is represented by local time. The Duration, which indicates the length of the event, is represented by the hour, minute, and second, as illustrated in Figure 28. The time has a total of 12 bits, the three numbers are represented each of them for a 4-bit BCD. The minute has a total of 8 bits, the two numbers are each indicated by a BCD of four bits. The second has a total of 8 bits, the two numbers are each represented by a BCD of 4 bits. By adding the duration to the start_time, you can indicate the final time of the event. The lapse of the event is therefore represented by the Duration without directly indicating the time of completion. This eliminates the need to modify the termination time even when the start_time of the event changes, thus simplifying the update processing. The length_of_repeat_information indicates the length of the_request_info. Repetition_info represents when and how the schedule is repeated. If the Programmed Action is not repeated, the repetition_formation_length indicates 00? 6. The content of the repeat_formation varies according to the type of repetition selected. The type of repetition includes the weekly scheme 00? 6 and the 101S interval scheme, as shown in figure 29. If the scheme is repeated every week, the Registration Device indicates the days of the week and the number of events to repeat, as illustrated in Figure 30. The value 0016 illustrated in Figure 29 is set to the type_of_repetition. The number of events is established in the number_of_event. The weekly bookmarks from Sunday to Saturday indicate the days of the week in which the repeated event begins. For example, if an event starting from 1:00 PM for 3 hours is held every Monday and Wednesday, one is set in the weekly markers on Monday and Wednesday, and zero in the other weekly markers. Repeated weekly events can be recorded, as described above. Therefore, only a lower storage capacity is required compared to the storage capacity required to store, for example, the absolute time and the date every Monday and Wednesday that correspond to the broadcast days.

When the Programmed Action is repeated at predetermined intervals, the Registration Device describes the event by using the format illustrated in FIG. 31. In this example, the value 10? 6 illustrated in FIG. 29 is set to the repeat_type. The number of events is established in the number_of_events. The interval represents the interval from the start_time of a current event to the start_time of the subsequent event. This interval is represented by the hour, minute and second. The time has a total of 12 bits, the three numbers are indicated by means of a 4-bit BCD. The minute has a total of 8 bits, the two numbers are each indicated by means of a 4-bit BCD. The second has a total of 8 bits, the four numbers are indicated by a 4-bit BCD. In this way, events repeated periodically can be stored. As a consequence, only a smaller capacity is required compared to the capacity required to store the absolute time (time and date) at which each event begins. The info blocks illustrated in Figure 26 are represented by the format illustrated in Figure 32. The composite_length indicates the byte length of the info block, except for the field length. The info block type is set to 8900i6. The length_of_primary_fields indicates the number_of_subunities and the number of bytes of the_type_field_and_subunity_ID. The number_of_subunits represents the number of subunits that are used by the Registration Device. The type_e_ID_de_subunidad specific subunits to be used by the Registration Device. As previously mentioned, the start_time and the duration are represented by the fixed lengths in the fixed direction. In contrast, the ID information to identify the subunit and the registry device that employs the subunit is stored as Info blocks at a predetermined address subsequent to the address of start_time and duration. With this arrangement, you can easily handle the addition of the Registration Devices. The data_specific_field_of_uploaded_field illustrated in Figure 20 is indicated by the format illustrated in Figure 33. The value 0116 that it indicates in RSB, illustrated in Figure 24, is set to the supported_table_type. The version_of_type_of_ supported_table represents the version number of the Bulletin Board Type Specification. The ID_of_implementation_profile designates the profile ID version for this type of board. The length of dependent information type of supported board indicates the number of bytes of the_dependent_type_of_type_file_upported. The information inherent in each dashboard type specification is described in the_dependent_type_info_upported information. The above-described series of operations can be executed by team. Alternatively, a programmatic one can be used, in this case, a program that implements the aforementioned operations can be installed in a computer integrated in a controller specifically used as a computer. Alternatively, the aforementioned programmatic can be installed on a general-purpose personal computer that can perform the various functions by installing several programs. As shown in Figure 34, a general purpose personal computer 101 has, for example, an integrated central processing unit (CPU) 111. An input / output interface 116 is connected to the CPU 111 via a bus 115. In response to an instruction provided by a user from an input unit 118, such as a keyboard, mouse, etc., through the input / output interface 116, the CPU 111 reads a program that implements the operations described above from a recording medium, such as a read-only memory (ROM) 112 or a hard disk 114or a recording medium loaded in a unit 120, such as for example a magnetic disk 131, an optical disk 132, or a magneto-optical disk 133. The CPU 111 then installs the read program in a random access memory (RAM) 113 and executes it. The program installed on the hard disk 114 can be a program stored in a recording medium and distributed to the user, or it can be a program transferred through a satellite or a network and received by a communication unit 119, and then installed on the hard disk 14. After processing the program, the CPU 111 sends an image signal to a display unit 117, such as a liquid crystal display (LCD) or a cathode ray tube (CRT). ) through the input / output interface 116. Co or can be seen from the above description, according to the information processing apparatus, the information processing method, and the registration means of the present invention, stores the reservation information of a subunit, and also, in response to a request from another information processing apparatus, the stored reservation information is read and supplied to the device. As a consequence, double reservation can be avoided.

Claims (12)

1. CLAIMS An information processing apparatus connected to an external information processing device through a network and having at least one subunit to execute a predetermined function, said information processing apparatus comprising: an input device for entering information Reservation regarding a reservation of the subunit; a storage device for storing the reservation information with reference to the reservation of the sub-unit; and a supply device for reading the reservation information stored in said storage device and supplying reservation information to said external information processing apparatus in response to a request from said external information processing device.
2. An information processing apparatus according to claim 1, further comprising a writing device for writing the reservation information of the subunit of said information processing apparatus in said storage device and for writing a reservation information of a subunit of said external information processing apparatus in a storage device of said external information processing apparatus when a reservation is made to use the subunit of said information processing apparatus in cooperation with the subunit of said external information processing apparatus. information at the same time.
3. An information processing apparatus according to claim 2, further comprising a comparing device for comparing the reservation information entered by said input device with the reservation information stored in said storage device of said information processing apparatus. and the reservation information of said storage device of said external information processing apparatus that includes the subunit to be used at the same time as the subunit of said information processing apparatus; wherein said writing device writes the reservation information in accordance with a comparison result obtained by said comparison device.
4. An information processing apparatus according to claim 2, wherein said writing device limits the reservation information to be written to said storage device of said information processing apparatus of said external information storage device when said writing device write the reservation information in said storage device of said information processing apparatus.
5. An information processing apparatus according to claim 4, wherein said writing device interrupts the reading by said external information processing apparatus of the reservation information of said storage device of said information processing apparatus when said The writing device writes the reservation information in said storage device of said information processing apparatus.
6. An information processing apparatus according to claim 1, wherein said storage device stores a limitation information regarding a limitation of the reservation information to be stored, and said delivery device supplies the limitation information to said external device. processing information in response to a request from said external information processing apparatus.
7. An information processing apparatus according to claim 1, wherein said storage device stores the reservation information in a predetermined address position.
8. 8. An information processing apparatus according to claim 1, where the reservation information includes a subunit start time in which the use of the subunit is initiated and a period to use the subunit.
9. 9. An information processing apparatus according to claim 8, wherein the period for using the subunit is set as an undefined value.
10. 10. An information processing apparatus according to claim 8, wherein the reservation information includes an apparatus information that refers to the information processing apparatus reserved by the subunit, and the apparatus information is stored in a position of address subsequent to the address positions of the subunit start time and the period to use the subunit.
11. 11. An information processing apparatus according to claim 8, wherein the subunit start time is represented by a binary coded decimal.
12. 12. An information processing apparatus according to claim 1, wherein said storage device further stores an identification information to identify the stored reservation information. An information processing apparatus according to claim 12, wherein the identification information includes a unique value for the information processing apparatus that has reserved the subunit and a unique value for the reservation established in said information processing apparatus. A compliance information processing apparatus of claim 13, wherein the unique value for the information processing apparatus is a global unique ID and the unique value for the reservation is a registration ID. An information processing apparatus according to claim 1, wherein the reservation information includes a weekly reservation information of the subunit reserved weekly by specifying a day of the week. An information processing apparatus according to claim 1, wherein the reservation information includes a reservation information of the subunit that is repeatedly reserved in a predetermined interval. An information processing apparatus according to claim 1, wherein said storage device is one of the subunits. An information processing apparatus according to claim 1, wherein said network is formed by the use of an IEEE-1394 serial data bus. An information processing method for use in an information processing apparatus connected to an external information processing apparatus through a network and having at least one subunit to execute a predetermined function, said method of information processing comprises : an entry step to enter reservation information about a subunit reservation; a storage control step for controlling the storage of reservation information concerning the reservation of the subunit; and a supply step for reading reservation information stored by processing said storage control step and by supplying reservation information to said external information processing apparatus in response to a request from said external device. information processing. a recording means for registering an executable program by a computer, said program for controlling an information processing apparatus connected to an external information processing device through a network and having at least one subunit to execute a predetermined function, said program comprises: an entry step to enter a reservation information regarding a reservation of the subunit; a storage control step to control the storage of reservation information regarding the reservation of the subunit; and a supply step for reading the reservation information stored by the processing of said storage control step and for supplying the reservation information to said external information processing apparatus in response to a request from said external processing apparatus. information.