JP2000358048A - Device and method for information processing, and recording medium - Google Patents

Abstract

PROBLEM TO BE SOLVED: To accurately control a target even when UTC(universal time code) is reference time. SOLUTION: When reservation information using a VCR subunit 33 of DVCR 3 is inputted, a controller 11 for IRD operating with UTC as reference time reads out the offset time of the DVCR 3 for the UTC stored in BBS 34 of the DVCR 3 and uses this to convert the use time of an inputted VCR subunit 33 into the use time of the local time of the DVCR 3. The converted use time is written to the BBS 34 of the DVCR 3.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an information processing apparatus and method, and a recording medium, and more particularly, to an information processing apparatus and method for accurately controlling reservation of a subunit connected via an IEEE1394 serial data bus, and recording. Regarding the medium.

[0002]

2. Description of the Related Art AV equipment capable of mutually transmitting information via a network using an IEEE1394 serial data bus has been developed. In this network, it is possible to control AV devices connected to the network by using a predetermined command (AV / C Command Transaction Set). For example, as shown in FIG. 1, an IRD (Integrated Rec.
eiver Decoder) 171 converts the video signal received by IEEE (In
Institute of Electrical and Electronic Engineer
s) DVCR (Digital Video) connected via 1394 serial data bus 2 (hereinafter simply referred to as bus 2)
A cassette recorder 181 can be used for recording. Further, it is possible to make a so-called recording reservation using the IRD 171 and the DVCR 181.

In the recording reservation processing, the IRD 17
One controller 172 includes the IRD 171 and the DVCR 18
Control 1 That is, the setting of the recording reservation (setting of the channel and the recording start time, etc.) is performed for the IRD 171, and when the set recording start time comes, the IRD 17
1 controller 172 includes the tuner subunit 17
3, select a reserved (set) channel and transmit the received video signal to the DVCR 1 via the bus 2.
81. At the same time, the controller 172
Is connected via the bus 2 to the VCR subunit 18 of the DVCR 181.
4, a command to start recording is transmitted. VCR of DVCR181
The subunit 184 records the video signal from the tuner subunit 173 on a magnetic tape (not shown) in response to the recording start command transmitted from the controller 172.

[0004]

The reservation start time is usually set in local time. This is because if the target device controlled by the controller is set in local time when considering an application that displays the scheduled use set in the device,
This is because the display may be performed as it is.

However, in the future, there is a possibility that a device for specifying the time not by the local time but by the UTC (Universal Time Code) will appear. UTC is Earth time, expressed in seconds. As described above, when UTC is used, the user cannot intuitively understand what time the local time corresponds to, and the operability deteriorates.

The present invention has been made in view of such a situation, and is intended to suppress deterioration in operability even when an AV device operates based on UTC. .

[0007]

According to a first aspect of the present invention, an information processing apparatus operates based on a second reference time using a target operating based on a first reference time via a network. In the information processing apparatus, a first acquisition unit that acquires a use time represented by a second reference time using a target, and a second acquisition unit that acquires information about the first reference time from the target. , First
The use time of the target represented by the second reference time acquired by the acquisition means is used as the first reference based on the information on the first reference time acquired by the second acquisition means. Conversion means for converting to use time represented by time.

[0008] Registering means for registering the use time of the target converted by the converting means in the target may be further provided.

[0009] The second acquisition means may include, as information relating to the first reference time, information relating to a difference between the first reference time and a third reference time common between the information processing apparatus and the target. Can be obtained.

[0010] The second obtaining means may further obtain information on the polarity of the third reference time as information on the first reference time.

[0011] The second acquisition means may acquire a code representing a country where the target is located as information on the first reference time.

[0012] The use time of the target may include a start time at which the use of the target is started.

An information processing method according to claim 7, wherein a target operating based on the first reference time is used via a network, and the information processing apparatus operates based on the second reference time. A first obtaining step of obtaining a use time represented by a second reference time using the target; a second obtaining step of obtaining information about the first reference time from the target; The use time of the target represented by the second reference time acquired by the processing of the acquisition step 1 is
And a conversion step of converting the information into a use time represented by a first reference time based on the target based on the information on the first reference time acquired by the processing of the acquisition step.

[0014] According to another aspect of the present invention, a program for a recording medium includes a target operating based on a first reference time,
In a program for information processing of an information processing apparatus that operates based on a second reference time and is used via a network, a first method of using a target and obtaining a use time represented by a second reference time An acquisition step, a second acquisition step of acquiring information about the first reference time from the target, and a use time of the target represented by the second reference time acquired by the processing of the first acquisition step. A conversion step of converting to a use time represented by a first reference time based on the target based on the information on the first reference time acquired by the processing of the second acquisition step. .

According to a ninth aspect of the present invention, the information processing apparatus operates based on a second reference time and is used via a network from another information processing apparatus operating based on the first reference time. In the processing device, a first storage unit that stores an event started at a predetermined time, a second storage unit that stores an event start time, and a third storage that stores information related to a second reference time. Means, and output means for outputting information on the second reference time stored in the third storage means to another information processing apparatus in response to a request from another information processing apparatus. Features.

[0016] The third storage means stores, as the information relating to the second reference time, information relating to the difference between the second reference time and the third reference time common to other information processing devices. It can be made to memorize.

[0017] The third storage means may further store information on the polarity of the third reference time as information on the second reference time.

[0018] The third storage means may further store a code representing the country in which it is located as information on the second reference time.

According to a thirteenth aspect of the present invention, the information processing method according to
From another information processing device that operates based on the reference time of
An information processing method for an information processing apparatus that operates based on a second reference time and is used via a network,
First to control storage of an event started at a predetermined time
A storage control step of controlling the storage of the start time of the event, a third storage control step of controlling the storage of information related to the second reference time,
Outputting the information on the second reference time stored by the processing of the third storage step to another information processing apparatus in response to a request from another information processing apparatus. I do.

The program of the recording medium according to the present invention operates based on a second reference time used via a network from another information processing apparatus which operates based on the first reference time. A first storage control step of controlling storage of an event started at a predetermined time in a program for information processing of the information processing apparatus; a second storage control step of controlling storage of an event start time;
A third storage control step for controlling storage of information relating to the second reference time, and a second reference time stored by the processing of the third storage control step in response to a request from another information processing apparatus. And outputting the related information to another information processing apparatus.

According to a fifteenth aspect of the present invention, in the information processing apparatus for exchanging data via a network, a storage means for storing an event to be processed, and an execution means for executing the event stored in the storage means And a time designating means for designating a time at which the event is executed, and a validity designating means for designating the validity of the event stored in the storage means.

The validity specifying means can specify the validity of the entire event stored in the storage means.

[0023] The validity specifying means may specify the validity of each event stored in the storage means.

An information processing method according to claim 18 is an information processing method for an information processing apparatus for exchanging data via a network, wherein a storage control step for controlling storage of an event to be processed and a storage control step. An execution step of executing the stored event; a time specification step of specifying the time of execution of the event; and a validity specification step of specifying the validity of the event stored in the processing of the storage control step. And

A storage medium program according to claim 19 is a program for information processing when data is transmitted and received via a network, wherein a storage control step for controlling storage of an event to be processed, and a processing of the storage control step. An execution step of executing the event stored in the step, a time specification step of specifying a time of execution of the event,
And a validity specifying step of specifying validity of the event stored in the processing of the storage control step.

According to a twentieth aspect of the present invention, in the information processing apparatus for exchanging data via a network, storage means for storing an event to be processed and execution means for executing the event stored in the storage means And a time specifying means for specifying the end time or the preparation time of the event by a relative time.

[0027] The time specification means may further specify an expiration date of the event stored in the storage means.

[0028] The time designation means may designate the end time or the preparation time of the event as a relative time from the start time of the event.

According to a twenty-third aspect of the present invention, in the information processing method of an information processing apparatus for exchanging data via a network, a storage control step for controlling storage of an event to be processed and a storage control step The method is characterized by including an execution step of executing the stored event, and a time specifying step of specifying an end time or a preparation time of the event by a relative time.

According to a twenty-fourth aspect of the present invention, there is provided a program for a recording medium, wherein a storage control step for controlling storage of an event to be processed and a storage control step are provided in an information processing program for exchanging data via a network. And a time specifying step of specifying an end time or a preparation time of the event by a relative time.

According to a twenty-fifth aspect of the present invention, in the information processing apparatus for exchanging data via a network, an event storage means for storing an event to be processed;
Executing means for executing an event stored in the event storage means, time specifying means for specifying a time at which the event is executed, and connection information necessary for exchanging data via a network are stored for each event. Connection information storage means.

According to a twenty-sixth aspect of the present invention, in the information processing method of the information processing apparatus for exchanging data via a network, an event storage control step for controlling storage of an event to be processed; An execution step of executing an event stored in the processing, a time specifying step of specifying a time of executing the event, and a connection information storage for storing connection information necessary for exchanging data via a network for each event And a step.

An information storage program for transmitting and receiving data via a network is an event storage control step for controlling storage of an event to be processed, and an event storage control step. An execution step of executing the event stored in the processing of the above, a time specifying step of specifying a time of executing the event, and connection information for storing connection information necessary for exchanging data via the network for each event. And a storage step.

An information processing apparatus according to claim 28 is an information processing apparatus for exchanging data via a network, wherein: an event storage means for storing an event to be processed;
Time specifying means for specifying a time to execute the event, and executing means for executing the event stored in the event storage means at each stage of preparation, start, end, stop, or restart It is characterized by.

A stage validity designating means for designating the validity of each stage may be further provided.

An information processing method according to claim 30 is an information processing method for an information processing apparatus for exchanging data via a network, wherein an event storage control step for controlling storage of an event to be processed, and a time for executing the event. , The event stored in the process of the event storage control step, the preparation, start,
An execution step to be executed for each stage of termination, suspension, or resumption.

According to a thirty-first aspect of the present invention, in the recording medium program according to the first aspect, an event storage control step of controlling storage of an event to be processed and an event are executed in an information processing program for exchanging data via a network. A time specification step of specifying a time; and an execution step of executing the event stored in the process of the event storage control step at every stage of preparation, start, end, stop, or restart. And

An information processing apparatus according to a thirty-second aspect is an information processing apparatus for exchanging data via a network, wherein: an event storage means for storing an event to be processed;
A time specifying unit that specifies a time at which an event is to be executed; an executing unit that executes an event stored in an event storing unit; and a user information storing unit that stores user information for each event. I do.

An information processing method according to a thirty-fourth aspect of the present invention provides an information processing method for an information processing apparatus for exchanging data via a network, wherein an event storage control step for controlling storage of an event to be processed, , An execution step of executing the event stored in the process of the event storage control step, and a user information storage step of storing user information for each event.

A program for recording on a recording medium according to the present invention is an information processing program for transmitting and receiving data via a network, and executes an event storage control step for controlling storage of an event to be processed and an event. The method includes a time specifying step of specifying a time, an executing step of executing an event stored in the processing of the event storing control step, and a user information storing step of storing user information for each event.

The information processing apparatus according to claim 1,
In the information processing method described in the item (1) and the recording medium described in the item (8), the use time of the target is converted into a first reference time based on the target based on information on the first reference time. .

[0042] The information processing apparatus according to claim 9, wherein
In the information processing method according to the third aspect and the recording medium according to the fourteenth aspect, information on the second reference time is output to another information processing apparatus in response to a request from another information processing apparatus. .

In the information processing apparatus according to the fifteenth aspect, the information processing method according to the eighteenth aspect, and the recording medium according to the nineteenth aspect, the validity of the stored event is specified.

[0044] The information processing apparatus according to claim 20, claim 2.
In the information processing method according to the third aspect and the recording medium according to the twenty-fourth aspect, the end time or the preparation time of the event is designated by a relative time.

In the information processing apparatus according to the twenty-fifth aspect, the information processing method according to the twenty-sixth aspect, and the recording medium according to the twenty-seventh aspect, connection information necessary for exchanging data via a network is provided. Is stored for each event.

In the information processing apparatus according to claim 28, the information processing method according to claim 30, and the recording medium according to claim 31, the stored events are prepared, started, ended, stopped, Alternatively, it is executed at each stage of restart.

In the information processing apparatus according to claim 32, the information processing method according to claim 33, and the recording medium according to claim 34, user information is stored for each event.

[0048]

DESCRIPTION OF THE PREFERRED EMBODIMENTS A configuration example of a network system to which the present invention is applied will be described with reference to FIG. In addition, in this specification, the term of the system refers to a plurality of devices,
It means an overall device constituted by means and the like.

This network system comprises an IRD 1 and a DVCR 3 connected via a bus 2. Of course, besides the IRD 1 and the DVCR 3, it is possible to connect an electronic device having an IEEE1394 terminal such as a personal computer, a hard disk drive, a CD player, a monitor, a digital video camera, or an MD (trademark) player to the bus 2. It is.

Electronic devices such as the IRD 1 and the DVCR 3 connected to the bus 2 are called units, and AV / C Command Transactions are performed between the units.
Set AV / C Digital Interface Command Set General S
Descriptor (Descripto) specified by pecification (hereinafter referred to as AV / C General Specification)
Using r), the information stored in each unit can be read and written to each other. The details of AV / C General are published at http://cxn02.net.arch.sony.co.jp/Doc/. The function of the unit is called a sub unit.

The controller 11 of the IRD 1 receives a channel selection operation, a recording reservation operation, and the like from the user, and controls the entire IRD 1. Further, the controller 11 controls the DVCR 3 using a predetermined command (AV / C Command Transaction Set). The CS antenna 13 receives a digital satellite broadcast digital signal transmitted via a communication satellite (not shown) and outputs the digital signal to the tuner subunit 12. The tuner subunit 12 extracts a signal of a predetermined channel from the digital signal input from the CS antenna 13 based on the control of the controller 11, and
3 to the VCR subunit 33. Further, the controller 11 controls the BBS (Bulletin Board Subuni
t) Retrieve the information stored in 34.

The BBS 14, which is a sub-unit of the IRD 1, stores information on the recording reservation that has been accepted and determined by the controller 11.

The controller 31 of the DVCR 3 receives a reproduction instruction operation, a recording reservation operation, and the like from the user, and performs the DVCR 3 operation.
3 is controlled in its entirety. The tuner subunit 32 extracts a signal of a predetermined channel from the input digital signal under the control of the controller 31 and outputs the signal to the VCR subunit 33.

The VCR subunit 33 records the video signal input from the tuner subunit 32 or the video signal from the tuner subunit 12 of the IRD 1 input via the bus 2 on a magnetic tape (not shown).

The BBS 34 manages information on recording reservations related to the DVCR 3.

The tuner subunit 12 and the BBS 1
Reference numeral 4 denotes a subunit of the IRD 1, and a tuner subunit 32, a VCR subunit 33, and a BBS 34
It is a subunit of CR3.

In this network system, when a digital satellite broadcast recording reservation is made, the user inputs the recording reservation setting (setting of the channel, recording start time, etc.) to the IRD 1. If the recording reservation is not double booking, the input recording reservation is recognized, and the information is written to the BBS 14 of the IRD 1.

The BBS 14, as shown in FIG.
urce Schedule Board) 51 and SAB (Schedule Ac)
Option Board) 52. SAB52 is IRD1
All the information related to the recording reservation input from the controller 11 of another unit or the controller of another unit (for example, the controller 31 of the DVCR 3) is stored. That is, SA
B52 stores all information for controlling a series of operations of causing the tuner subunit 12 of the IRD 1 to receive at a predetermined time and recording the received information in the VCR subunit 33 of the DVCR 3.

On the other hand, the RSB 51 transmits only the information relating to the reservation of the tuner sub-unit 12 which is a sub-unit of the IRD 1 among all the information relating to the recording reservation (including the recording reservation set by other units). The information is stored (even if the operation is related, the reservation information of the VCR subunit 33 is not stored), and the stored information is stored not only in the controller 11 in the same unit but also in a controller in another unit (for example, the DVCR 3). Controller 31)
Publish in response to requests from.

Similarly, the BBS 34 of the DVCR 3 is composed of the RSB 61 and the SAB 62 as shown in FIG. SAB6
Reference numeral 2 stores all information relating to the recording reservation input from the controller 31 of the DVCR 3 or the controller of another unit (for example, the controller 11 of the IRD 1).
On the other hand, the RSB 61 is the controller 31 of the DVCR 3.
Reservation input to the IRD1 and IRD1 controller 1
Of all the information related to the recording reservation input in 1,
Stores information related to the reservation of the VCR subunit 33 (or the tuner subunit 32), which is a subunit of the DVCR3 (does not store the reservation information of the tuner subunit 12 of the IRD1, even if it operates in association). The stored information is disclosed in response to a request from a controller of another unit (for example, the controller 11 of the IRD 1) as well as the controller 31 in the same unit.

FIG. 5 shows an RSB model. The target device 72 corresponds to the DVCR3 in FIG.
It is. The subunit A in FIG. 5 is, for example, the DVCR in FIG.
3 corresponds to the VCR subunit 33. The owner device 71 in FIG. 5 corresponds to the IRD 1 in FIG. Program f
or Scheduled Action is the internal controller 11 of FIG.
It corresponds to the reservation program registered in.

The RSB 82 (corresponding to the RSB 61 in FIG. 4)
It is located in the BBS 81 (corresponding to the BBS 34 in FIG. 4) and is composed of one route list. The root list is an original list specified by the subunit Identifier Descriptor. The subunit Identifier Descriptor is a list showing the outline of the subunits of all the subunits. For more information on the structure of these lists, see AV
Specified in / C General Specification.

The route list of the Resource Schedule Board 82 includes one or more Resource Schedule Objects. The Resource Schedule Object is information to be used for writing to the device.

FIG. 6 shows the format of the RSB. descriptor_length indicates the length of the RSB. list_type
Is RSB Read Only or Write Enab
Whether it is led or not is described. The Read Only list allows only reading, and the WriteEnabled list allows writing. attributes is a bit flag indicating an attribute for all list structures.

Size_of_list_specific_information is l
ist_specific_information (described later with reference to FIG. 7)
Represents the length of number_of_entries (n) is object_entry [i] (i = 0, 1, 2,...) registered in this RSB.
..N-1). In this example, n objects
ct_entry is registered.

FIG. 7 shows the format of list_specific_information.

Non_info_block_fileds_length is non i
Indicates the number of bytes of nfo block fields (until Next_time_offset). board_type is Resource Schedule Board
In this case, "01 ₁₆ " is set.

Object_list_maximum_size is the object li
Indicates the maximum size of st. object_entries_maximum_num
ber represents the maximum number of object entries in the list. object_entry_maximum_size represents the maximum size of the object entry. The above object_list_maximum_size,
object_entries_maximum_number, object_entry_maximu
m_size is set to “0000 ₁₆ ” when no limit is set.

These three fields are significant when the controller knows the capacity of the object list or object entry.

Board_type_dependent_information_lengt
h represents the length of board_type_dependent_information, and board_type_dependent_information is the board typ
e indicates information specific to e, and since this board is an RSB,
try_Code, Contry_region_id, localtime_offset_polar
ity, Local_time_offset, Time_of_change, Next_time_
offset is described.

"Contry_Code" is a 24-bit code specified by ISO 3166, and represents a country. This code is composed of three characters, and each character is a code composed of 8 bits specified by ISO8859-1.

[0072] Contry_region_id is represented by 6 bits,
Represents the identification number of a given zone in the country represented by country_code. If this value is set to "000000", it means that there are no different local time zones in that country. localtime_offset_polar
ity is composed of one bit, and the “0” of this bit is
Represents a positive UTC (local time advanced from UTC (usually,
East of Greenwich)), "
1 "represents a negative UTC (local time delayed from UTC (time westward from Greenwich)).

Local_time_offset indicates the difference (offset) of how much the local time deviates from UTC. This time is shown in the range from -12 hours to +12 hours. This value is 1 of the hour
The four digits of the 0's and 1's, the tens's and the 1's are respectively represented by BCD, and have a total of 16 bits.

Time_of_change is a 40-bit field representing the date and time when the time is changed, such as daylight saving time, and is represented by a date and time in MJD (modified Julian date) and UTC.

Next_time_offset is a predetermined country (country_
predetermined area (country_region) of country specified by code
_id) in the area specified by _id)
Within 12 hours, after changed (after time change)
Indicates the time offset from UTC. This value is the tens place and ones place of the hour, and the tens place and the ones place of four.
Each number is represented by a 4-bit BCD, for a total of 16 bits.

After Next_time_offset, an area for future expansion optional info blocks for future expanse
sion.

FIG. 8 is a diagram showing object_entry [i] (i = 0,
1,2, ... n-1) (Resource Schedule Objec
t) format. non_info_block_leng
th is non-i up to repeat_type_dependent_information
Indicates the number of bytes in nfo block fields. start_time is
Indicates the year, month, day, hour, minute, and second when the event starts. The year is 16 bits and each of the four numbers is represented by a 4 bit BCD. The month is 8 bits and the two numbers are each represented by a 4 bit BCD. The day is 8 bits and the two numbers are each represented by a 4 bit BCD. The time is 8 bits and the two numbers are each represented by a 4 bit BCD. The minute is 8 bits and the two numbers are each represented by a 4 bit BCD. The second is 8 bits and the two numbers are
Each is represented by a 4-bit BCD.

The representation by the BCD facilitates the identification. This time is expressed in local time.

The duration representing the length of the event is expressed in hours, minutes, and seconds. Time is BC with 3 numbers each being 4 bits
D and a total of 12 bits. The minute is represented by a total of 8 bits, with each of the two numbers being a 4-bit BCD. In the second, two numbers are each represented by a 4-bit BCD, for a total of 8 bits.

By adding duration to start_time,
Indicates the end time of the event. By not expressing the end time directly, but expressing the length of the event as duration, even if the start_time of the event is changed, the end time does not need to be changed, and the change processing Becomes easier.

Repeat_type_dependent_information_leng
th represents the length of repeat_type_dependent_information. repeat_type_dependent_information is
Indicates how and when the schedule is repeated.
Repeat_type if Scheduled Action is not repeated
_dependent_infomation_length is set to “00 ₁₆ ”.

[Repeat_type_dependent_information]
The content differs depending on the selected repeat type. repeat
In type, Weekly schedule “00 ₁₆ ” and Interval
schedule “10 ₁₆ ”.

As described above, an event that is repeated every week (Weekly schedule) or at a predetermined interval (Intervalschedule) can be recorded, so that, for example, absolute dates and times on Monday and Wednesday are stored for the broadcast date. In this case, the storage capacity can be reduced as compared with the case where it is not necessary.

The info blocks include compound_length, inf
o_block_type, primary_fields_length, number_of_sub
Units, subunit_type_and_ID, etc. are described. conpou
nd_length represents the byte length of the info block. Where le
The ngth field itself is not included in this length. in
The fo_block_type is set to “8900 ₁₆ ”. prima
ry_fields_length is number_of_subunits and subunit_ty
pe_and_ID Indicates the number of bytes in the field.

Number_of_subunits is a posting Device
Subunits used by (device with controller)
Represents the number of subunit_type_and_ID is posting Devi
Specify the subunits used by ce.

As described above, start_time and duration are represented by a fixed length at a fixed address. On the other hand, the identification information for identifying the subunit and the posting device that uses the subunit is start_time, du as Info blocks.
It is stored at a predetermined address after the ration. As a result, even if the number of posting devices increases, it is easy to respond.

Next, the reservation processing (competition unit search processing) performed in the system of FIG. 2 will be described with reference to the flowcharts of FIGS.

First, in step S11, the user performs a reservation setting process for the controller 11 of the IRD1. For example, from 20:00 on October 16 to 21
Until 0:00, the 48th channel is received by the tuner subunit 12, and this is received by the VCR subunit 3 of the DVCR 3.
3 to be recorded. At this time, in step S12, the controller 11 executes a process of writing open the RSB in the device where the subunit to be used exists. In the case of the present example, the subunits to be used are the tuner subunit 12 of the IRD1 and the VCR of the DVCR3.
Since the sub-unit 33 is selected, one of them, for example, the tuner sub-unit 12 is selected first, and the controller 11 WRITE OPENs the RSB 51 of the IRD 1 as a device having the tuner sub-unit 12 (to be in a writable state). Output a WRITEOPEN command.

However, actually, the RSB 51 and the controller 1
1 is held in the IRD 1, and the bus 2 does not exist between them. So, controller 1
1 controls the RSB 51 so that the RSB 51 is in the same state as when a WRITE OPEN command is supplied via the bus 2.

For example, after the processing of WRITE OPEN to the RSB 51 in the IRD 1 as the device in which the tuner sub-unit 12 is present among the sub-units used in relation to the VCR as the remaining related sub-units, DVCR3 as a device with subunit 33
Is performed in the same manner as above, but in this case, the controller 11 transmits the WRIT of the format shown in FIG.
E Open command from RSB61 of DVCR3 (controller 3
Output to 1).

The WRITE OPEN command is a type of OPEN DESCRIPTOR command used to access a predetermined address space of a target, and has a format as shown in FIG. The opcode contains the OP
A value (08 ₁₆ ) representing EN DESCRIPTOR is described. operand0 has a value indicating that it is an Object List Descriptor specified by the list ID as a descriptor_type indicating the type of the descriptor to be WRITE OPEN "
10 ₁₆ ”is described. In operand 1 and operand 2, a list ID (in this example,“ 00 ”and“ 01 ”) of the RSB to be accessed (WRITE OPEN) is described.

Further, in operand3, as a subfunction, a value indicating that "descriptor" is WRITE OPEN for opening for read or write access "
03 ₁₆ "is described. Operand 4 is set to a value" 00 "for reserve.

Next, proceeding to step S13, the controller 11 sets the descrptior_length of the RSB 51 in the BBS 14 and l
Read the ist_specific_information field (FIG. 7). This reading is performed using, for example, a READ command shown in FIG. However, also in this case, since the controller 11 and the RSB 51 are not connected via the bus 2, the reading from the controller 11 to the RSB 51 is directly performed. However, when the controller 11 reads data from the RSB 61 of the DVCR 3, a READ command as shown in FIG. 13 is output to the RSB 61 (controller 31) via the bus 2.

As shown in FIG. 13, the value “09 ₁₆ ” representing the read descriptor is described as the first opcode of the READ command. The following operand0 is a descriptor for identifying the descriptor to be read.
identifier is described. In the case of the reading process in step S13, the descriptor ID is used as the list ID.
entifier is described. Specifically, RSB write enable
Address_offse of d list_specific_information field
“00 ₁₆ ” to “0D ₁₆ ” of t are described.

In the read_result_status, FF is described when a READ command is sent, and the read result is described when the response is returned from the target as a response. In data_length, the number of bytes of data to be read from the target is described. When this value is set to "0", all lists are read. In the address, an address from which reading is to be started is described. When the value is “00”, reading is started from the beginning.

In step S14, the controller 1
1 is a limit on the maximum length of the list for the RSB 51 as a target (object_list_maximum_size in FIG. 7);
Limit on the number of entries in the list (object_entri
es_maximum_number) and the maximum byte length of each entry (object_entry_maximum_size in FIG. 7)
Is extracted.

In step S15, the controller 11 determines whether or not the data (reservation information) to be recorded in the RSB 51 does not exceed the maximum length (object_list_maximum_size) of the list extracted in step S14. If this restriction is observed, step S16
The controller 11 proceeds to step S14 to limit the number of entries in the list extracted in step S14 (the maximum number of entries) (ob
ject_entries_maximum_number), it is determined whether or not a value obtained by subtracting the current number of entries is greater than “0”, that is, whether or not recordable entries still remain.
If this condition is satisfied, step S17 is further performed.
The controller 11 determines whether the value obtained by subtracting the entry length to be written from the maximum entry length (object_entry_maximum_size) extracted in step S14 is larger than "0", that is, the entry length to be written, It is determined whether there is still room.

If any one of the conditions in steps S15 to S17 is not satisfied, the process proceeds to step S18, and the controller 11 displays a warning message such as "reservation is full" to the user.
This allows the user to know that the reservation is full and that no more reservations can be made.

If all of the conditions of steps S15 to S17 are satisfied, there is room to write the reservation information in the RSB 51. Therefore, in steps S19 to S25, it is determined whether or not the reservation of the overlapping time has already been made. Is determined.

That is, in step S19, the variable i
Is initially set to “0”, and in step S20, RS
Number of entries recorded in B51 number_of_entries
It is determined whether or not the value obtained by subtracting the variable i from “0” is greater than “0”, in other words, whether or not all the entries recorded in the RSB 51 have been searched. number_of_
If the value obtained by subtracting the variable i from the entries is greater than "0", there are entries that have not been searched yet.
Proceeding to step S21, the controller 11
Is read (in this case, object_entry [0] is read).

The reading in step S21 is also performed by the READ command shown in FIG. 13. In this case, the descriptor identifier is described in the object posi.
It is performed in tion. In this object entry [i], the time information of the already registered reservation (start_ti in FIG. 8)
me, duration) and the identification information of the subunit used in the reservation (subunit in the info blocks in FIG. 8).
t_type_and_ID [0]) are stored.

In step S22, the controller 11 determines whether the time information (start_time, duration) input by the user in step S11 overlaps with the time information (start_time, duration) read in step S21. Is determined. If the times are duplicated, the process proceeds to step S23, where the controller 11 sets the sub-unit reserved in step S11 (in this case,
It is determined whether or not the tuner subunit 12) matches the subunit (subunit_type_and_ID) read in step S21. If the sub-units match, both the time and the sub-unit match in the end, so the process proceeds to step S25, and the controller 11 issues a warning such as "Reservation overlaps". Display. Thereby, double booking is prevented.

If it is determined in step S22 that the times do not overlap, or if it is determined in step S23 that the subunits do not match even if the times match, double booking is not performed. There is no danger. Therefore, in step S24, only the variable i is incremented by 1 and the process returns to step S20, where the value obtained by subtracting the variable i from number_of_entries is 0.
The same processing is repeatedly executed until it is determined that the value is not larger. That is, a search is made for all object entry [i] stored in the RSB 51 as to whether or not an overlapping time is reserved.

At step S20, number_of_entr
If it is determined that the value obtained by subtracting the variable i from ies is not greater than “0” (if the search for all object entry [i] has been completed), the process proceeds to step S26, and the controller 11 issues a CREATE command to the RSB 51. Output and object e
ntry is created in the RSB 51. However, even in this case, the CREATE command is not actually output (RS
If an objectentry is created for B61, it is output), but only the same processing as when it is output is performed.

The processing in steps S15 to S18 is the same as the processing in step S20 except for NO.
It is also possible to execute it when the determination is made.

Here, the CREATE command will be described.
FIG. 14 shows the format of the AV / C CREATE command.
FIG. 15 shows values that can be specified by subfunction_1 in FIG. 14, and in this embodiment, “01” (create a new
object and its childlist) are used. FIG. 16 shows the subfunction_1_specification in FIG.
The format of for subfunction_1 = 1 is shown. FIG. 17 is a diagram showing each field value in FIG. Descriptor_identifier_where, descrip in FIG.
In each field of tor_identifier_what_1 and _2,
As shown in FIG. 7, when “20”, “22”, and “11” are set, respectively, “create a newobject and its
child list ”.

For details of these AV / C CREATE commands, see IEEE 1394 (Internet home page ht)
tp: //www.1394TA.org), and each figure in the present embodiment is described in the literature (Enhanceme
nt to the AV / C GeneralSpecification 3.0 Ver
sion 1.0 FC2 and TA Document 1999005
AV / C Bulletion Board Subunit General Specif
ication 1.0 Draft 0.99: 149). In addition, the information list descriptor (Information List Des
Criptors are also writable and readable, and a list type is used to distinguish between them.

By the way, one of the methods for newly writing information to the AV / C Descriptor from outside is described below.
For example, a common method is that, for example, the controller issues the above-described CREATE command to the target, creates a template in which the target writes information, and again controls the controller to write specific contents. Conceived as a method. For example, when writing information for the first time, the controller specifies a desired list and executes an AV / C descriptor create command (AV / C Descriptor CR).
EATE command). The target receiving this command creates an object inside the target based on the template of the data structure specified by the AV / C General Specification. Also, AV / C General S
The data structure template determined by pecification has a field indicating an object ID. In a list using an AV / C descriptor, an object ID is managed by a target. In other words, when an object is created (CREATE), the target assigns an ID that uniquely specifies the object,
The target will have the ability to manage that ID.

Here, the object ID is an identification number for uniquely designating the object in the list. Therefore, a function for preventing the object ID from being duplicated is required on the managing side. The BBS itself is a place for providing information, and the controller has control of the object ID.

However, when a CREATE command is issued to a subunit, there is a possibility that inconsistency may occur. That is, when you create an object, the object ID that the controller should manage is
This is because the target will be allocated. Further, after issuing the CREATE command, it is necessary to continue the write control. As described above, since the processing is divided into a plurality of steps, an incomplete object may be created if the controller is disconnected from the bus during writing, for example.

Therefore, in such a situation, there is a need for a system capable of specifying the incomplete object and deleting the object when such an object is created.

Therefore, in the embodiment of the present invention, means for writing to the BBS is specified by the standard, and a mechanism for specifying an incomplete object is prepared.

That is, first, the target (DVCR3 in the present embodiment) creates an object (CRE).
ATE), object ID (global unique ID)
(Grobal Unique ID: GUID) and record ID) are assigned a number to be temporarily managed (for example, all “0”). The controller writes information in the object first, and when the writing is completed normally, finally rewrites the GUID.

By deciding the above procedure, when the writing operation is completed normally, an object whose GUID is all "0" cannot be performed. Therefore, an object whose GUID is all "0" cannot be written. An object that has become incomplete on the way can be identified.

As a result, the object being written can be uniquely specified, and the normally written object and the incomplete object can be distinguished.
Further, an incomplete object (invalid object) can be easily deleted. Thus, the finite memory provided in the electronic device can be effectively used. In addition, since the method of specifying an object in the middle of writing is a simple method of setting all GUID portions of the object ID to “0”, it is easy to create software for deleting an incomplete object.

In step S26 of FIG. 11,
Instead of using the CREATE command, you can also use the INSERT command.

Next, in step S27, the controller 11 sets the list of the RSB 61 of the DVCR 3 as the target.
Read the specific information field (Fig. 7),
Obtain the Local_time_offset of DVCR3. Step S2
In step 8, the controller 11 stores the reservation time information of the VCR subunit 33 input by the user in step S11 in the Local_time of the DVCR 3 obtained in step S27.
Calculate according to _offset. That is, the controller 1
1 operates based on UTC (although the UCT can be obtained), but in step S11, the user uses the VCR subunit 33 of the DVCR3 based on the local time of the IRD1 instead of the DVCR3. Enter the usage time. The controller 11 determines the time of use (IRD
1 based on the local time) is converted to UTC, the time corresponding to the Local_time_offset of the DVCR 3 is corrected from the UTC, and the use time based on the reference time of the local time of the DVCR 3 is calculated.

Next, proceeding to step S29, the controller 11 makes the entry_specific_information file of the RSB 51.
The reserved contents are written in the lds part (FIG. 8). That is,
With this, start_time, duration, repeat_informati
on, subunit to be used (subunit_type_and_ID), etc. are written. At this time, for example, start_time is recorded as a time based on the local time of the DVCR 3 calculated in step S28.

FIG. 18 shows the format of the WRITE DESCRIPTOR command output by the controller 11 in such a case. However, the controller 11 and RSB5
Since 1 is not connected via the bus 2,
Writing the reservation information of the tuner subunit 12 to the RSB 51 is performed directly, but the controller 11
When writing the reservation information of the VCR subunit 33 to the RSB 61 of No. 3, the controller 11
Issue the ESCRIPTOR command.

In the first opcode, a value “0A ₁₆ ” representing a WRITE DESCRIPTOR is described. operand0
Describes a descriptor indentifier for identifying a descriptor to be written. This description is made at the object position.

Hereinafter, partial_repla is used as a subfunction.
“50 ₁₆ ”, which is a value representing ce, is described. Thereby, partial insert or partial delate is executed. In insert, the new descriptor before one specified by operand specified by descriptor_identifier
or is inserted. In delete, the descriptor specified by descriptor_identifier is deleted.

The group_tag is used for performing update processing that cannot be divided on a descriptor where a WRITE DESCRIPTOR command needs to be issued. In this example, a value “00 ₁₆ ” (immediate) indicating that data is quickly written to the descriptor is described. rep
lacement_data_length is the operand of replacement_data
, Ie, the length of data to be written. The address indicates the position where the processing should be performed. "0" of replacement_data_length is p
means artial delete, in which case replacement_data
The operand does not exist. In this case, original_data_len
gth is a value greater than "0", which indicates the number of bytes to be deleted. If original_data_length is “0”, a partial insert process is performed. In this case, replacement_data_length is set to a value larger than "0" and represents the number of bytes to be inserted.

Next, in step S30, the controller 1
1 closes the list, ie, the RSB 51. At this time, the controller 11 outputs a CLOSE command shown in FIG. However, also in this case, since the controller 11 and the RSB 51 are not connected via the bus 2, the closing process is performed directly. However, when the controller 11 closes the RSB 61 of the DVCR 3, the closing process is performed. A CLOSE command is output.

The format of the CLOSE command shown in FIG. 19 is basically the same as the format of the WRITE OPEN command shown in FIG.
In, whereas there is a representative of the WRITE OPEN "03 _16", the CLOSE command shown in FIG. 19, CLOs
The difference is that the value indicating SE is “00 ₁₆ ”. Other configurations are the same as those in FIG.

Next, proceeding to step S31, the controller 11 determines whether or not there is another resource related to the reservation. In this case, since the processing for reserving the tuner subunit 12 has been completed by the processing so far, the processing for reserving the VCR subunit 33 of the DVCR 3 is still necessary. Therefore, in this case, the process returns to step S12, and the same processing as that performed on the RSB 51 described above is also performed on the RSD 61 of the DVCR 3.

If it is determined in step S31 that there is no other resource related to the reservation, the processing is terminated.

An example of the configuration of another network system to which the present invention is applied will be described with reference to FIG.

This network system comprises an IRD 1 and a DVCR 3 connected via a bus 2.

The controller 11 of the IRD 1 receives a channel selection operation, a recording reservation operation, and the like from the user, and controls the entire IRD 1. Further, the controller 11 executes a predetermined command (AV / C Command Transaction Se
The DVCR 3 is controlled using t). The CS antenna 13 receives a digital satellite broadcast digital signal transmitted via a communication satellite (not shown) and outputs the digital signal to the tuner subunit 12. Tuner subunit 1
2 extracts a signal of a predetermined channel from the digital signal input from the CS antenna 13 under the control of the controller 11, and outputs the signal to the VCR subunit 33 of the DVCR 3 via the bus 2. In addition, the controller 11
Schedule action for CR3 (hereinafter referred to as SA)
The information stored in the descriptor 221 is searched.

[0130] The SA descriptor 211, which is a subunit of the IRD1, is configured to store information on a recording reservation that has been accepted and determined by the controller 11.

The controller 31 of the DVCR 3 receives a reproduction instruction operation, a recording reservation operation and the like from the user,
3 is controlled as a whole. The analog tuner block 35 extracts a signal of a predetermined channel from the input analog signal under the control of the controller 31, and outputs the signal to the VCR subunit 33.

The VCR subunit 33 receives the video signal input from the analog tuner block 35 or the bus 2
The video signal input from the tuner subunit 12 of the IRD 1 via the IRD 1 is recorded on a magnetic tape (not shown).

[0133] The SA descriptor 221 which is a subunit of the DVCR 3 stores and manages information on recording reservations related to the DVCR 3.

In this network system, when making a recording reservation, the user inputs the recording reservation settings (channel, recording start time, etc.) to the IRD 1.
If the recording reservation is not double booking, the input recording reservation is accepted and the information is
It is written to one SA descriptor 211.

FIG. 21 shows the SA descriptor 21 of the IRD1.
1 shows a directory structure (the SA descriptor 221 has a similar structure, though not shown). The SA descriptor 211 includes a plurality of pieces of reservation information (S
A Root SA Event list consisting of A Event #i) and a Root macro command list which is a table for managing the macro command #i registered in the unit.

FIG. 22 shows a more detailed structure of the Root SA Event list. As shown in the figure, a Valid / Invalid_of_SA Root list is arranged at the top of the list, which indicates whether the SA descriptor 211 is valid or invalid (all the events described in the SA descriptor 211). Indicates whether there is. For example, controlling each electronic device of the entire system by a super timer 271 which will be described later with reference to FIG. 38 means that the Valid / Invad.
By turning off the flag of the lid_of_SA Root list, this can be easily done.

The SA list specific information is shown in FIG.
3 is included. The details are basically the same as the case shown in FIG. 7, and the description thereof is omitted. Number_of_SA_Event_object is followed by SA_
Indicates the number of events, followed by each SA_Ev
Pointer pointer_for_SA_Event #i to ent is placed.

The reservation information (SA Event #i) is the
D, time information, related unit information, connection information,
It consists of trigger information, command information for each stage, and user information. The SA Event ID describes an ID that can uniquely identify the reservation information in a network or a related unit. The time information describes a preparation time, a recording start time, a recording end time, and the like. The related unit information includes the Node (Global) Unique ID (unit unique ID) of the unit (in this case, DVCR3) related to the reservation, and the Node that changes every bus reset.
ID), Subunit Type, and Subunit ID. The connection information describes information such as the band used by the bus 2 and plugs. The trigger information describes the type of trigger (time, message, etc.). The command information for each stage describes macro commands to be executed in each stage (preparation stage, start stage, end stage, stop stage, and restart stage). Labels and the like are described in the user information.

FIG. 24 shows a more detailed configuration of the SA Event list. Valid / Invalid_of_Event_object is
A flag indicating whether this event is valid or invalid. For example, in a case where a recording of a serial drama being broadcast every week is scheduled, when the broadcast of the program is temporarily canceled for baseball broadcasting, the detailed reservation setting contents of the program are retained. The recording reservation processing is temporarily performed as is in this Valid / Invalid_of_Event_obj
It can be released by turning off the ect flag. Object_ID is the ID of the event, and this ID is a unique value within the unit.

[0140] Start_time_of_SA represents the start time of an event in absolute time. Period_for_standby represents the time required for preparation, and a specific value differs for each device. Preparation process starts from Start_time_of_SA to Period_for_standby
Only start from the previous time. Period_for_action is
Indicates the execution time of the event. Start_time_of_SA, Peri
The value obtained by adding od_for_action is the end time of the event. That is, Period_for_standby and Period_for
_action is represented by relative time from Start_time_of_SA represented by absolute time. As a result, the preparation time of each device can be input as a fixed value, which facilitates creation of an application. Also, by expressing the end time as a relative time, it is easy to change the end time when it is postponed or advanced (the end time need not be changed because only the start time needs to be changed).

[0141] Valid_time_of_SA indicates the valid period of the event. This is used when the reservation information is rearranged when the reservation is not executed for some reason or when the reservation information of the subunit is not used. In the case where the same recording reservation is made for a predetermined period, such as three months, six months, or one year, such as a serial drama, if this expiration date is set, when a certain period elapses (the When the broadcast of the drama series ends), the recording reservation is automatically ended.

The output unit (node ID) & oPCR No. represents the ID (node ID) of the unit that outputs the event and the number of the output plug control register.
(node ID) & iPCR No. represents the node ID of the electronic device to which the corresponding event is input and the number of the input plug control register. These are necessary as connection information when exchanging data with each electronic device via the bus 2. The bandwidth indicates the occupied bandwidth required for data transfer on the bus 2. These pieces of information are used when checking the contention situation of network resources (the details will be described later with reference to the flowchart of FIG. 29). Without this information, it would be necessary to scan the actual command to check for this conflict, which would take a long time to check for conflicts.

Pointer_for_SA is a pointer to SA_command_list in which an execution command is described. That is, this specifies the command of FIG. 25 described later.

Since the size of the execution command group changes due to the reservation operation, in this embodiment, FIG.
It is a separate list as shown in the figure.

Size_of_user_Information represents the size of user information (the details will be described later with reference to FIG. 27). Pointer_for_user_Information is described in FIG.
7 represents a pointer to a User_Information_list. User_Information_list is also a separate list because the size of user information changes.

FIG. 25 shows the detailed configuration of the SA command list. As shown in FIG.
It is divided into five stages of preparation (standby), start (action), end (stop), suspension (suspend), and restart (restart). First, a flag indicating whether the trigger for each of these five stages is valid or invalid is described. For example, Valid / Invalid_of_trigger_for_stand
"by_command" indicates the validity of the preparation trigger. Specifically, this flag is configured as shown in FIG. As shown in the drawing, each flag is set to be valid ("1") or invalid ("0") for each item such as time and command. This indicates whether the trigger is based on the internal time or the external time.

Next, the command size for each stage is described. For example, size_of_action_commands starts (a
ction) command size. Thereby, the head address of the command group at each stage is calculated.
That is, in this case, Number_of_action_command [0]
Is calculated.

After that, a command is described for each stage. In each command, the number of commands at that stage is described first, followed by specific commands. For example, in the case of a suspend command, the number of suspend commands is described in Number_of_suspend_command, followed by n Suspend commands.
spend_command [0] to Suspend_command [n-1] are described.

As described above, at each stage, a plurality of execution commands can be written.

[0150] The Standby_command is started from a time earlier than Start_time_of_SA by Period_for_standby. By this preparation process, for example, the tuner subunit 12 is set to the tuning state, or the bus 2 is transferred from the IRD 1 to the DVCR 3.
A connection necessary for transmitting data via the network is established, and processing such as securing necessary channels and bands is performed. Action_command is started at the time of Start_time_of_SA. As a result, for example, a scheduled recording operation is performed by the tuner subunit 12 from a predetermined time.

Stop_command is from Start_time_of_SA to Pe.
Executed when riod_for_action time has elapsed. Thus, at a predetermined time, for example, the scheduled recording operation by the tuner subunit 12 is ended.

The Suspend_command is a command transmitted when, for example, a broadcast program scheduled for some reason is interrupted on the broadcast station side, and by executing this command, event processing is temporarily interrupted. .

[0153] Restart_command is a command for canceling Suspend, whereby the processing of the event once suspended is restarted again.

As described above, by describing a command for each stage, it is possible to divide the command for each execution time, and it becomes easy to access a target command group.

Further, by enabling or disabling a command for each stage, it is possible to specify whether a command trigger is based on an internal time or an external time at each stage. Becomes

FIG. 27 shows a more detailed structure of the user information. As shown in the figure, first, user_informati
The number of on is described in Number_of_user_information. The user_information is an area in which the user can write data for each event, in which a nickname can be added (accordingly, for each event) or a memo can be written. Also, each user_infor
An info type is added to the mation, and for example, a tag can be described therein in order to facilitate the search.

As described above, by adding the nickname, the user can easily identify each event (reservation). Also, the user can use this area as a memo.

Returning to FIG. 21, macro command #i is a pointer to macro command list #i, macro command #i
It consists of an identifier and a user label. In the macro command list #i indicated by the pointer to the macro command list #i, the AV / C command to be executed and the Node Unique ID are described in pairs. The Subfunction describes information that defines the operation of the command group (for example, when an error occurs, the command is stopped, or the command is forcibly executed to the end).

FIG. 28 shows the SA descriptor 21 of FIG.
1 shows the descriptor information about the macro command stored in No. 1.

[0160] Since the descriptor information includes various information in addition to the information about the macro command, a data ID (data_id) is assigned to each piece of information to identify the information. In the present embodiment, the information on the macro command includes a data ID as shown in FIG.
, MACRO COMMAND is assigned.

Here, in the embodiment of FIG.
In MACRO COMMAND, 50h (h is the number before it is 1
(Representing a hexadecimal number). It should be noted that, for example, the information (SUBUNIT IDENTIFIER) about the specifications of the AV system and the function of the subunit includes 40h and the like, and a selectable object (the object avatar).
In the information (OBJECT LIST) about ilable to select, data such as 41h has already been assigned as a data ID, and data to be assigned to information about macro commands
The ID may be basically any value as long as it is not a value already assigned in this way.

The data ID is a handle for the information. Therefore, by referring to the data ID, the address in the descriptor where the information to which the data ID is assigned is stored is recognized. be able to.

Here, for example, as shown in FIG. 28B, information on a macro command (hereinafter, appropriately referred to as macro command descriptor information) is stored from an address 0000h.

In this embodiment, for example, the descriptor has a 16-bit address space, and each address can store 8-bit (1 byte) data.

In the macro command descriptor information, the start address and the second address (FIG. 28)
In (B), the length (size) descri of the macro command descriptor information is 0000h and 0001h).
ptor_length is described by 2 bytes. That is, FIG.
In the embodiment of (B), addresses 0000h to xxh
xxh stores macro command descriptor information, and the length of the xxxh is xxxh + 1h.
It is described as ptor_length.

The third address (in FIG. 28B, 0
002h) includes the number of macro commands included in the macro command descriptor information.
d_count is described by 1 byte. That is, not only one macro command but also a plurality of macro commands can be described in the macro command descriptor information, and the number is described in the entried macro_command_count. In FIG. 28B, n + 1 macro commands are described.

Then, the fourth address (FIG. 28B)
After 0003h), a set of commands constituting a macro command is divided into macro command units (hereinafter, appropriately,
Entry).

The entry macro_command_entry [i] is configured, for example, as shown in FIG. 28C (i = 0,
1, ..., n). Here, the entry has a variable length. In FIG. 28C, the left column describes an offset address from the head of the entry.

First address of entry (FIG. 28C)
In 00h), a Node UniqueID for command is described. For example, as described below with reference to FIG.
In the case where the personal computer (PC) 261 controls the DVCR 3 having no SA descriptor via the IRD 1, a command transfer destination (destination)
Becomes IRD1, but the destination of the command is IRD
DVCR3 instead of RD1. Therefore, in order to specify the destination where this command operates, Node UniqueID for co
mmand is described.

The next address (0 in FIG. 28C)
1h) includes an entry number macro_command_entry_number (hereinafter referred to as “entry_
abbreviated as number). Therefore, the entry macro_
For command_entry [i], for example, i is entry_nu
Described as mber. The third address of the entry (02h in FIG. 28C) describes the execution procedure subfunction of the command described thereafter. That is, the fourth address of the entry (in FIG. 28C,
03h) and thereafter, commands # 0, # 1,..., #K constituting the macro command are described. The order and conditions for executing these commands are described as subfunctions. Specifically, for example, first, the command #
0 is executed, and if it ends normally, the command # 1 is executed. If it ends abnormally, the command # 2 is executed.

Then, after the fourth address of the entry (03h in FIG. 28C), as described above,
Commands # 0, # 1,... Constituting the macro command
, #K are described. These commands are described according to the format of the AV / C command. For example, assuming the command # 0 in FIG. 28C as an example, the head address has the length of the command # 0 data_length
of command [0] is described, followed by an AV / C command.

That is, first, CTS (command transaction set) and CT / RC (command type / response code) are described. Following CT / RC, HA
(Header address) and OPC (operation code) are described sequentially, and thereafter, OPRs (operands) are described as many as necessary.

Here, 0h of the CTS indicates that it is an AV / C command set. CT / RC indicates the type of request (command) or reply (response). further,
The HA indicates the destination to send the command or the source to send the response. OPC indicates the content of a process to be executed, and OPR indicates parameters necessary for the process.

Next, the conflicting unit search processing of the network system will be described with reference to the flowcharts of FIGS. This process is performed by the user
For 1, input the operation of recording reservation using DVCR3,
The operation is started when the operation is detected by the controller 11. In step S51, the controller 11
One of all the units connected to the bus 2 is selected.

At the step S52, the controller 1
1 is reservation information (SA Event) from the Root SA Event list of the SA descriptor of the unit selected in step S51.
Is selected and read out. In step S53, the controller 11 reads out in step S52.
Refer to the related unit information of SA Event, and describe the Node Unique ID, SubunitType, and Subunit I described there.
It is determined whether or not D corresponds to DVCR3. If it is determined that D corresponds, the process proceeds to step S54. In step S54, the controller 11 refers to the time information of the SA Event read out in step S52, and determines whether or not the recording time described there overlaps the recording reservation time input by the user. If it is determined that they do not overlap, the process proceeds to step S55.

In step S54, step S52
If it is determined that the recording time described in the time information of the SA Event read out in the step overlaps with the recording reservation time input by the user, the process proceeds to step S58.

In step S58, the controller 1
1 judges that the input recording reservations conflict (becomes double booking), and notifies the user of the information by a predetermined method.

For example, a duplicate recording reservation may be presented to the user to request selection. Further, at the overlapping time, another DVCR for which recording reservation has not been made may be searched for and presented to the user.

If it is determined in step S53 that the Node Unique ID, SubunitType, and Subunit ID described in the related unit information do not correspond to the DVCR 3, the processing in step S54 is skipped.

At the step S55, the controller 1
1 indicates all the S described in the Root SA Event list of the SA descriptor of the unit selected in step S51.
It is determined whether or not A Event is selected in step S52,
Until it is determined that all SA Events have been selected, step S
The processing of 52 to S55 is repeated.

If it is determined in step S55 that all SA Events have been selected, in step S56, the controller 11 determines whether all units connected to the bus 2 have been selected in step S51. Step S51 until it is determined that all the units have been selected.
To S56 are repeated.

If it is determined in step S56 that all units have been selected, in step S57, the controller 11 determines that the input recording reservation does not conflict (does not result in double booking), and the input is made. The recording reservation information is stored in the SA descriptor 211.

Next, the controller 11 proceeds to step S59.
WRITE OPEN the SAB of the device for which you want to embed the reservation
Execute the processing to be performed. For example, if the device in which the reservation is to be embedded is the tuner subunit 12 of the IRD1, the controller 11 WRITE OPENs (sets to the writable state) the SAB 52 of the IRD1 as the device having the tuner subunit 12. Output WRITE OPEN command.

However, actually, the SAB 52 and the controller 1
1 is held in the IRD 1, and the bus 2 does not exist between them. So, controller 1
1 controls the SAB 52 so that the SAB 52 is in the same state as when a WRITE OPEN command is supplied via the bus 2.

Next, proceeding to step S60, the controller 11 sets the descrptior_length of the SAB 52 in the BBS 14 and S
Read A list_specific_information (FIG. 23).
This reading is performed using a READ command. However, also in this case, the controller 11 and the SAB 52
Are not connected via the bus 2, so that the reading from the controller 11 to the SAB 52 is performed directly.

At the step S61, the controller 1
1 is a limit on the maximum length of the list for the target SAB 52 (object_list_maximum_siz in FIG. 23).
e), limit on the number of entries in the list (objec in FIG. 23)
t_entries_maximum_number) and the limit on the maximum byte length of each entry (object_entry_maximum in FIG. 23)
_size).

In step S62, the controller 11 determines whether or not the data (reservation information) to be recorded in the SAB 52 does not exceed the maximum length (object_list_maximum_size) of the list extracted in step S61. If this restriction is observed, step S63
The controller 11 proceeds to step S61 to limit the number of entries in the list extracted in step S61 (the maximum number of entries) (ob
ject_entries_maximum_number), it is determined whether or not a value obtained by subtracting the current number of entries is greater than “0”, that is, whether or not recordable entries still remain.
If this condition is satisfied, step S64 is further performed.
The controller 11 determines whether the value obtained by subtracting the entry length to be written from the maximum entry length (object_entry_maximum_size) extracted in step S61 is larger than “0”, that is, the entry length to be written, It is determined whether there is still room.

If any one of the conditions in steps S62 to S64 is not satisfied, the process proceeds to step S65, where the controller 11 displays a warning message such as "reservation is full" to the user.
This allows the user to know that the reservation is full and that no more reservations can be made.

If all of the conditions in steps S62 to S64 are satisfied, there is room to write the reservation information in the SAB 52. Therefore, in steps S66 to S72, it is determined whether or not the reservation of the overlapping time has already been made. Is determined.

That is, in step S66, the variable i
Is initially set to "0", and in step S67, SA
Number of entries recorded in B52 number_of_entries
It is determined whether or not the value obtained by subtracting the variable i from “0” is greater than “0”, in other words, whether or not all the entries recorded in the SAB 52 have been searched. number_of_
If the value obtained by subtracting the variable i from the entries is greater than "0", there are entries that have not been searched yet.
Proceeding to step S68, the controller 11
Is read (in this case, object_entry [0] is read).

The reading in step S68 is also performed by the READ command.
The description of the riptor identifier is made at the object position. In this object entry [i], the time information of the already registered reservation (start_time, duration in FIG. 8)
n) and identification information of a subunit to be used in the reservation (subunit_type_and
_ID [0]) are stored.

Therefore, in step S69, the controller 11 outputs the time information (start_ti
It is determined whether or not (me, duration) overlaps with the time information (start_time, duration) read in step S68. If the times overlap, step S7
In step S68, the controller 11 determines that the reserved subunit (the tuner subunit 12 in this case) has read the subunit (subunit_type
_and_ID). If the sub-units match, both the time and the sub-unit match, so step S7
Proceeding to 2, the controller 11 performs a warning display such as "Reservation overlapped". Thereby, double booking is prevented.

If it is determined in step S69 that the times do not overlap, or if it is determined in step S70 that the subunits do not match even if the times match, double booking is not performed. There is no danger. Therefore, in step S71, only 1 is incremented for the variable i, and the process returns to step S67, where the value obtained by subtracting the variable i from number_of_entries is 0.
The same processing is repeatedly executed until it is determined that the value is not larger. That is, a search is made for all object entry [i] stored in the SAB 52 as to whether or not a reservation for an overlapping time has been made.

In step S67, number_of_entr
When it is determined that the value obtained by subtracting the variable i from ies is not greater than “0” (when the search for all object entry [i] is completed), the process proceeds to step S73, and the controller 11 issues a CREATE command to the SAB 52. Output and object e
ntry is created in SAB52. However, even in this case, the CREATE command is not actually output, and only the same processing as when it is output is performed.

The processing in steps S62 to S65 is the same as that in step S67 except that
It is also possible to execute it when the determination is made.

In step S73 of FIG.
Instead of using the CREATE command, you can also use the INSERT command.

Next, in step S74, the controller 11 sets the list of the SAB 62 of the DVCR 3 as a target.
The specific information field (FIG. 23) is read, and the Local_time_offset of the DVCR 3 is obtained. In step S75, the controller 11 calculates the reservation time information of the VCR subunit 33 input by the user according to the Local_time_offset of the DVCR 3 acquired in step S74. That is, although the controller 11 operates based on UTC (although UCT can be obtained), the user uses the VCR subunit 33 of the DVCR 3 based on the local time of the IRD 1 instead of the DVCR 3. Enter the usage time. The controller 11 converts the use time (time based on the local time of IRD1) into UTC, and further converts the UTC to Local_time of DVCR3.
The time corresponding to _offset is corrected, and the use time based on the reference time of the local time of the DVCR 3 is calculated.

Next, proceeding to step S76, the controller 11 makes the entry_specific_information file of the SAB 52.
Write the reservation contents to the lds part. That is, thereby, start_time, duration, repeat_information, reservation contents, and the like are written. At this time, for example, start_time
Is recorded as the time based on the local time of the DVCR 3 calculated in step S75.

Next, the process proceeds to a step S77, wherein the controller 1
1 closes the list, SAB52. At this time, the controller 11 outputs a CLOSE command to the SAB 52. However, also in this case, since the controller 11 and the RSB 51 are not connected via the bus 2, the closing process is performed directly.

Next, proceeding to step S78, the controller 11 determines whether or not there is another resource related to the reservation. In this case, since the processing for reserving the tuner subunit 12 has been completed by the processing so far, the processing for reserving the VCR subunit 33 of the DVCR 3 is still necessary. Therefore, in this case, the process returns to step S59, and the same processing as that performed on the SAB 52 described above is also performed on the SAB 62 of the DVCR 3.

If it is determined in step S78 that there are no other resources related to the reservation, the processing is terminated.

The information of the confirmed recording reservation is stored in IRD1
SA descriptor 211, and related units
If writing is performed to the SA descriptor 221 of the DVCR 3, the unit selected in step S51 may be only the DVCR 3 which is a related unit.

Also, in step S53 or step S53,
By reading the connection information of the SA Event at the same time as the processing of 54, it is possible to grasp the use reservation status of the bandwidth of the bus 2.

As described above, the execution command of each unit is verified one by one without confirming the status of the recording reservation.
By simply reading a part of the SA event of the SA descriptor of each unit, it is possible to obtain information on the already-set recording reservation.

Next, SA Eve of this network system
The nt ID setting process will be described with reference to the flowchart in FIG. This processing is performed after the user inputs an operation for recording reservation using the DVCR 3 to the IRD 1, the operation is detected by the controller 11, and the above-described conflicting unit search processing is executed, and the recording reservation is recognized. ,
Be started. In step S91, the controller 1
1 generates a temporary ID that can uniquely identify the reservation information in the network (or in a related unit).

At step S92, the controller 1
2 reads out the SA Event of the unit (or related unit) in the network and reads the SA Event ID in it
Is extracted. In step S93, the controller 1
1 is the temporary ID generated in step S91 and step S9
Determine whether the SA Event ID extracted in step 2 matches,
Steps S91 to S93 until it is determined that they do not match.
Is repeated.

The temporary ID and the SA Event extracted in step S92
If it is determined that the IDs do not match, in step S94, the controller 11 determines whether all the SA Events of the units (or related units) in the network have been read, and determines that all the SA Events have been read. Until the process, the processes of steps S92 to S94 are repeated. If it is determined that all SA Events have been read,
In step S95, the controller 11 records the temporary ID generated in step S91 as the SA Event ID in the SA descriptor 211.

FIG. 34 shows an example in which IRD1 is a subunit SA
A configuration without the descriptor 211 and with the SA controller 231 instead is shown. This SA controller 231 does not have an SA descriptor itself, but refers to the SA descriptor of another unit.
For example, it has a function corresponding to an AV / C Read Descriptor or Write Descriptor.

As described above, by assigning an ID that can be uniquely identified in the network (or related unit) to the recording reservation, an arbitrary recording reservation can be designated in the network (or related unit). Thus, processing such as change or deletion can be easily performed.

Next, another configuration example in the case of performing the recording reservation operation will be described. In the example of FIG. 35, the timer 241 is configured by the controller 11 of the IRD 1 and the SA descriptor 211, and the controller 31 of the DVCR 3
And the SA descriptor 221 constitute a timer 251. The user transfers data received at a predetermined time to the IRD 1 to the DVCR 3 and performs a recording reservation operation for recording the data on both the IRD 1 and the DVCR 3. That is, SA
The descriptor 211 stores that a broadcast of a predetermined channel is received at a predetermined time and transferred to the DVCR 3 via the bus 2. The controller 11 performs a timing operation, and when a predetermined time is reached, a channel and a band necessary for transferring data via the bus 2 are secured in the DVCR 3, and a channel designated by the tuner subunit 12 is allocated. Make the program receive. Then, the controller 11 transfers the received data to the DVCR 3 via the bus 2.

[0211] On the other hand, the SA descriptor 221 of the DVCR 3 also stores recording reservation information for receiving the data transferred from the IRD 1 and recording it on the recorder 3 at a predetermined time. The controller 31 performs a timing operation, and when a predetermined time is reached, the IRD
The data transferred from 1 is recorded in the VCR subunit 33.

FIG. 36 shows still another configuration example. In this configuration example, the DVCR 3 does not have the SA descriptor 221. Then, the personal computer (PC) 261 causes the SA descriptor 211 of the IRD 1 to store the recording reservation information. At this time, as described above, the PC 261 sets the transfer destination (de
IRD1 is designated as the “stination”, and at a predetermined time, the DVCR3 is designated as the destination to which the IRD1 sends the command.

When the predetermined time stored in the SA descriptor 211 has been reached, the controller 11 of the IRD 1 secures a channel and a band necessary for transferring data via the bus 2, and A predetermined channel is received. Then, the controller 11 transfers the received data to the DVCR 3 via the bus 2.

Further, prior to transferring data, the controller 11 sends a command to the DVCR 3 to
Requests the VCR subunit 33 to record the transferred data. When receiving this command, the controller 31 of the DVCR 3 receives the data transferred from the IRD 1 and causes the VCR subunit 33 to record the data. FIG. 37 shows still another configuration example. FIG.
6, the controller 11 of the IRD 1 and the DVC
Although the time of the clocking operation performed by the controller 31 of R3 needs to match, in the configuration example of FIG. 37, the recording reservation operation can be executed even if the two times do not match. That is, in this configuration example, when the predetermined time stored in the SA descriptor 211 has been reached, the controller 11 secures a channel and a band necessary for transferring data via the bus 2, and Trigger signal is output to the controller 31 of FIG. Further, the controller 11 controls the tuner subunit 12 to receive a signal of a predetermined channel and transfer the signal to the DVCR 3 via the bus 2. When a trigger signal is input from the controller 11 of the IRD 1, the controller 31 of the DVCR 3 responds to the input of the trigger signal.
3 starts a recording operation of the data transferred from the IRD 1.

Thereafter, when the time reaches the end of the scheduled recording operation, the controller 11 sets the tuner sub-unit 12
Stop the operation of DVCR3 controller 3
1 outputs a trigger signal for ending the recording operation. The controller 31 ends the recording operation of the VCR subunit 33 in response to the trigger signal.

FIG. 38 shows still another configuration example. In this configuration example, the timer operation of all the electronic devices connected to the bus 2 is performed by the super timer 2 of the PC 261.
71. That is,
The user stores the scheduled recording information in the SA descriptor 282 constituting the super timer 271. When a predetermined time stored in the SA descriptor 282 has been reached, the controller 281 performs a process of securing a channel and a band necessary for transferring data via the bus 2, and transmits the predetermined channel to the IRD 1. Requests that the signal be received and transferred to DVCR 3 via bus 2. In response to this request, the controller 11 causes the tuner subunit 12 to receive the designated channel, and transfers the data to the DVCR 3 via the bus 2.

The controller 281 also sends the data transmitted from the IRD 1 to the controller 31 of the DVCR 3
Require subunit 33 to record. In response to the request from the PC 261, the controller 31 of the DVCR 3 controls the VCR subunit 33 to record the data transferred from the IRD 1.

When the recording operation is completed, the PC 261 transmits the IRD1 and the DVC
This is executed by outputting a command to R3.

The AV / C Resource Schedule Board is the AV / CB
It is one board of ulletin Board Subunit. This board is for preventing double booking when performing a reservation operation between devices connected to the network. For devices that make reservations for devices in the network, their use schedules are indicated by the AV / C Bulletin Board in the device that they want to use.
Write the usage schedule of Resource Schedule Board in Subunit. If another device later wants to use the same device for reservation operation, etc., the Resource Schedule Boar of that device
By reading d, the use schedule of another device can be known before executing the reservation, and the double booking can be identified in advance.

FIG. 39 shows another configuration example. Object
The ID can be stored in the RSB and also in the SAB. Thus, when double booking occurs, it can be easily confirmed. For example, as shown in FIG.
It is assumed that R3 is connected and IRD 321 is connected. IRD1 has RSB51 and SAB52 in BBS14.
SID (Subunit Identifier Descriptor)
341. This SID 341 has this SID 34
Information for recognizing what board type (in this example, RSB 51 and SAB 52) is supported is stored in the BBS 14 to which 1 belongs.

[0221] In addition to the RSB 61, the BBS 34 of the DVCR 3
D311 is provided. The IRD 321 has a controller 322 and a display unit 323.

Next, an example of processing in the system of FIG. 39 will be described. The user operates the controller 11 of the IRD 1
Enter the reservation information in. In the example of FIG.
From 20:00 to 21:00 on the 2nd, the reservation content of selecting the X channel and recording the data of the selected program in the DVCR 3 is input. The controller 11 writes the reservation contents in the built-in memory, writes the reservation information in the RSB 51 and SAB 52 of its own BBS 14, and writes the reservation information of the BBS 34 of the DVCR 3 as a target.
The usage schedule is also written in SB61. At this time, the controller 11 sets the Object ID stored in each entry of the RSB 51, SAB 52, and RSB 61 to the same value.

In such a case, IRD 321
A processing example in the case where an attempt is made to reserve the DVCR 3 at a time overlapping with the time reserved by the RD 1 will be described with reference to the flowchart in FIG.

[0224] In step S111, the controller 322 of the IRD 321 controls the RS of the DVCR 3 as a target.
By checking B61, it is determined whether or not the schedule of another controller overlaps with the time zone to be used. When the schedule is not written in the overlapping time zone, the process proceeds to step S115, and the controller 322
The reservation process is executed in the same manner as in the case described above. That is, the controller 322 writes the use time zone in the RSB 61 of the DVCR 3.

In step S111, the VCR of DVCR3
If it is determined that the subunit 33 has already been reserved by another controller in the overlapping time zone, the process proceeds to step S112, where the controller 322 reads the Object ID of the entry used for the reservation, and reads the upper 8 bytes. From the (64-bit) GUID, the node ID of the device that wrote the entry is determined. Ie GUID
Is unique to each device and, unlike the node ID, does not change every bus reset. Therefore, the controller 322 is connected to each device connected to the bus 2.
The GUID and the node ID are checked, and a correspondence table is created in advance. The node ID can be determined from the GUID by referring to the correspondence table.

Next, proceeding to step S113, the controller 322 specifies the same Object ID as the multiple reservation entry from the SAB of the device determined in the processing of step S112 (in this case, from the SAB 52 of IRD1), and Is read out. Then, in step S114,
The controller 322 outputs the content of the overlapping reservation read out in the process of step S113 to the display unit 323 and displays it. As a result, the user of the IRD 321 can check the content that has been reserved earlier.

The series of processes described above can be executed by hardware, but can also be executed by software. When a series of processing is executed by software, a program constituting the software is installed in a controller built into a controller as dedicated hardware, or various functions are installed by installing various programs. Is installed in, for example, a general-purpose personal computer or the like that can execute the program.

A general-purpose personal computer 101 is
For example, as shown in FIG. 41, a CPU (Central Process
ng Unit) 111. The CPU 111 is connected to an input / output interface 116 via a bus 115.
When a user inputs a command from the input unit 118 including a keyboard, a mouse, and the like via the storage unit 16, the recording medium such as the ROM (Read Only Memory) 112 or the hard disk 114 or the drive 120 is correspondingly input. Mounted magnetic disk 131, optical disk 1
32, a program for executing the above-described series of processes, which is recorded on the recording medium such as the magneto-optical disk 133, is read out.
13 and run. The programs stored in the hard disk 114 include not only programs stored in advance and distributed to users, but also programs transferred from a satellite or a network, received by the communication unit 119, and installed.

[0229] The CPU 111 outputs the image signal among the processing results of the program to the input / output interface 116.
LCD (Liquid Crystal Display), CRT (Ca
output to a display unit 117 such as a Thode Ray Tube.

[0230]

As described above, the information processing apparatus according to the first aspect, the information processing method according to the seventh aspect, and the eighth aspect.
According to the recording medium described in the above, the use time of the target,
Since the target is converted into the first reference time based on the information on the first reference time, the target can be accurately controlled even when the reference time is different. Become.

[0231] The information processing apparatus according to the ninth aspect, the first aspect.
According to the information processing method described in Item 3 and the recording medium described in Item 14, information on the second reference time is stored, and when a request is received from another information processing device, the stored second information is stored. Since the information about the reference time is output to another information processing apparatus, it is possible to cause another information processing apparatus to manage an event at an accurate time.

According to the information processing apparatus described in claim 15, the information processing method described in claim 18, and the recording medium described in claim 19, the validity of the stored event is specified. In a case where a plurality of information processing apparatuses connected to a network are collectively controlled by one information processing apparatus, control is performed while retaining information of each event individually stored in each information processing apparatus. Becomes possible. Further, even in the case where the process for an event is temporarily changed, it is possible to execute the temporary process while keeping detailed information of each event in each information processing apparatus.

According to the information processing apparatus described in claim 20, the information processing method described in claim 23, and the recording medium described in claim 24, the end time or preparation time of an event is designated by a relative time. Therefore, in each information processing apparatus, the preparation time and the end time can be input as fixed values, and the creation of the application is facilitated. Further, even when the end time or the preparation time is postponed or advanced, the change is easy (unnecessary).

According to the information processing apparatus described in claim 25, the information processing method described in claim 26, and the recording medium described in claim 27, connection information necessary for exchanging data via a network. Is stored for each event, so that network conflict determination processing can be performed quickly.

According to the information processing apparatus of claim 28, the information processing method of claim 30, and the recording medium of claim 31, preparation, start, end, stop, or restart of an event is performed. , The event can be managed for each execution time, and the access to the execution of the event becomes easy.

According to the information processing apparatus described in claim 32, the information processing method described in claim 33, and the recording medium described in claim 34, user information is stored for each event. It is easy to manage and search for a plurality of events.

[Brief description of the drawings]

FIG. 1 is a block diagram showing a configuration of a conventional IEEE1394 serial data bus network.

FIG. 2 is a block diagram illustrating a configuration example of a network system to which the present invention has been applied.

FIG. 3 is a diagram showing a configuration of a Bulletin Board Subunit 14 of FIG.

FIG. 4 is a diagram showing a configuration of a Bulletin Board Subunit 34 of FIG.

FIG. 5 is a diagram illustrating a model of a Resource Schedule Board.

FIG. 6 is a diagram illustrating a format of a Resource Schedule Board.

FIG. 7 is a diagram illustrating a format of a List Specific Information field.

FIG. 8 is a diagram illustrating a format of a Resource Schedule Object.

FIG. 9 is a flowchart illustrating an operation of the controller 11 of FIG. 2;

FIG. 10 is a flowchart illustrating an operation of the controller 11 of FIG. 2;

FIG. 11 is a flowchart illustrating an operation of the controller 11 of FIG. 2;

FIG. 12 is a diagram illustrating a format of a WRITE OPEN command.

FIG. 13 is a diagram illustrating a format of a READ command.

FIG. 14 is a diagram illustrating a format of a CREATE command.

FIG. 15 is a diagram illustrating subfunction_1 in FIG. 14;

16 is a diagram illustrating details of subfunction_1 in FIG.

17 is a diagram illustrating an example of a field value in FIG. 16;

FIG. 18 is a diagram illustrating a format of a WRITE DESCRITOR command.

FIG. 19 is a diagram illustrating the format of a CLOSE command.

FIG. 20 is a block diagram illustrating a configuration example of a network system to which the present invention has been applied.

FIG. 21 is a diagram illustrating a directory structure of an SA descriptor.

FIG. 22 is a diagram illustrating a route schedule action event list.

FIG. 23 is a diagram illustrating the format of SA list specific information.

FIG. 24 is a diagram illustrating a schedule action event list.

FIG. 25 is a diagram illustrating a schedule action command list.

FIG. 26 is a diagram illustrating a valid / invalid trigger flag.

FIG. 27 is a diagram illustrating a user information list.

FIG. 28 is a diagram illustrating a macro command.

FIG. 29 is a flowchart illustrating a conflicting unit search process of the controller 11 of FIG. 20;

FIG. 30 is a flowchart illustrating a conflicting unit search process of the controller 11 of FIG. 20;

FIG. 31 is a flowchart illustrating a conflicting unit search process of the controller 11 of FIG. 20;

FIG. 32 is a flowchart illustrating a conflicting unit search process of the controller 11 of FIG. 20;

FIG. 33 is a flowchart illustrating SA Event ID setting processing of controller 11 in FIG. 20;

FIG. 34 is a block diagram illustrating another configuration example of a network system to which the present invention has been applied.

FIG. 35 is a block diagram showing another configuration example of the network system to which the present invention is applied.

FIG. 36 is a block diagram showing another configuration example of the network system to which the present invention is applied.

FIG. 37 is a block diagram illustrating another configuration example of a network system to which the present invention has been applied.

FIG. 38 is a block diagram illustrating another configuration example of a network system to which the present invention has been applied.

FIG. 39 is a block diagram illustrating another configuration example of a network system to which the present invention has been applied.

FIG. 40 is a flowchart illustrating an operation of the network system in FIG. 39;

FIG. 41 is a block diagram illustrating a configuration example of a computer.

[Explanation of symbols]

1 IRD, 2 IEEE1394 serial data bus, 3D
VCR, 11 controllers, 12 tuner subunits, 14 BBS, 31 controllers, 32
Tuner subunit, 33 VCR subunit,
34 BBS, 51, 61 RSB

 ──────────────────────────────────────────────────続 き Continuing on the front page (72) Kazuo Yamamoto, 6-7-35 Kita-Shinagawa, Shinagawa-ku, Tokyo Inside Sony Corporation (72) Harumi Kawamura 6-35, Kita-Shinagawa, Shinagawa-ku, Tokyo Sony Corporation F term (reference) 5K032 BA08 CC13 DB18 DB19 DB22

Claims (34)

[Claims] An information processing apparatus operating based on a second reference time, wherein the information processing apparatus operates based on a second reference time using a target operating based on a first reference time, wherein the second operation uses the target. A first acquisition unit that acquires a use time represented by a reference time, a second acquisition unit that acquires information about the first reference time from the target, and an acquisition unit that acquires the use time. The first reference used as a reference by the target based on the information about the first reference time acquired by the second acquisition unit, based on the use time of the target represented by the second reference time. An information processing apparatus comprising: a conversion unit configured to convert a use time represented by a time. 2. The information processing apparatus according to claim 1, further comprising a registration unit that registers the use time of the target converted by the conversion unit in the target. 3. The information processing apparatus according to claim 2, wherein the second acquisition unit includes, as the information regarding the first reference time, a third reference time common to the information processing apparatus and the target, the first reference time being used as the information. The information processing apparatus according to claim 1, wherein information on a difference between the information is acquired. 4. The information processing apparatus according to claim 3, wherein the second obtaining unit further obtains information on a polarity of the third reference time as information on the first reference time.
An information processing apparatus according to claim 1. 5. The information processing apparatus according to claim 1, wherein the second acquisition unit acquires, as the information on the first reference time, a code representing a country where the target is located. 6. The information processing apparatus according to claim 1, wherein the use time of the target includes a start time at which use of the target is started. 7. An information processing method for an information processing apparatus operating based on a second reference time, wherein the target operates based on a first reference time is used via a network, wherein the target is used. A first acquisition step of acquiring a use time represented by the second reference time; a second acquisition step of acquiring information on the first reference time from the target; and the first acquisition step The use time of the target represented by the second reference time acquired by the process of the above, based on the information about the first reference time acquired by the process of the second acquisition step, the target Converting to a use time represented by the first reference time as a reference. 8. A program for information processing of an information processing device operating based on a second reference time, wherein the target uses the target operating based on a first reference time via a network. A first acquisition step of acquiring a use time represented by the second reference time; a second acquisition step of acquiring information on the first reference time from the target; The use time of the target represented by the second reference time acquired by the processing of the acquisition step, based on the information about the first reference time acquired by the processing of the second acquisition step, Converting to a use time represented by the first reference time as a reference of the target. A recording medium on which an executable program is recorded. 9. A method in which another information processing apparatus operating based on a first reference time is used via a network.
An information processing apparatus that operates based on a second reference time; a first storage unit that stores an event started at a predetermined time; a second storage unit that stores a start time of the event; A third storage unit for storing information relating to a second reference time;
Output means for outputting information on the second reference time stored in the storage means to the other information processing apparatus. 10. The information processing apparatus according to claim 5, wherein the third storage unit stores, as the information regarding the second reference time, the second reference time with a third reference time common to the another information processing apparatus. The information processing apparatus according to claim 9, wherein information on a difference is stored. 11. The information processing apparatus according to claim 10, wherein the third storage unit further stores, as information relating to the second reference time, information relating to the polarity of the third reference time. apparatus. 12. The information processing apparatus according to claim 9, wherein the third storage unit further stores, as information on the second reference time, a code representing a country where the third device is located. . 13. An information processing method for an information processing apparatus that operates based on a second reference time and that is used via a network from another information processing apparatus that operates based on a first reference time. To control the storage of events that start at time
A second storage control step for controlling storage of the start time of the event, and a third storage control step for controlling storage of information relating to the second reference time.
In response to a request from the other information processing apparatus,
Outputting the information about the second reference time stored by the processing of the storage control step to the another information processing apparatus. 14. A program for information processing of an information processing apparatus operating based on a second reference time, which is used via a network, from another information processing apparatus operating based on a first reference time. A first for controlling storage of an event started at a predetermined time;
A second storage control step for controlling storage of the start time of the event, and a third storage control step for controlling storage of information relating to the second reference time.
In response to a request from the other information processing apparatus,
Outputting the information on the second reference time stored by the processing of the storage control step to the other information processing apparatus. The computer-executable program is recorded recoding media. 15. An information processing apparatus for exchanging data via a network, a storage unit for storing an event to be processed, an execution unit for executing the event stored in the storage unit, and a time for executing the event. An information processing apparatus, comprising: a time designating unit that designates the event; and a validity designating unit that designates the validity of the event stored in the storage unit. 16. The information processing apparatus according to claim 15, wherein the validity specifying unit specifies validity of the entire event stored in the storage unit. 17. The information processing apparatus according to claim 15, wherein said validity specifying means specifies the validity of each event stored in said storage means. 18. An information processing method for an information processing apparatus for exchanging data via a network, comprising: a storage control step of controlling storage of an event to be processed; and an execution step of executing the event stored in the processing of the storage control step. An information processing method, comprising: a step of specifying a time at which the event is to be executed; and a validity specifying step of specifying the validity of the event stored in the processing of the storage control step. . 19. An information processing program for exchanging data via a network, comprising: a storage control step for controlling storage of an event to be processed; and an execution for executing the event stored in the storage control step. And a time specifying step for specifying a time at which the event is executed; and a validity specifying step for specifying validity of the event stored in the processing of the storage control step. A recording medium on which a possible program is recorded. 20. An information processing apparatus for exchanging data via a network, wherein: storage means for storing an event to be processed; execution means for executing the event stored in the storage means; An information processing apparatus comprising: a time designation unit that designates a preparation time by a relative time. 21. The information processing apparatus according to claim 20, wherein the time designation unit further designates an expiration date of the event stored in the storage unit. 22. The time specification unit according to claim 20, wherein the end time or the preparation time of the event is specified by a relative time from the start time of the event.
An information processing apparatus according to claim 1. 23. An information processing method of an information processing apparatus for exchanging data via a network, comprising: a storage control step of controlling storage of an event to be processed; and an execution step of executing the event stored in the processing of the storage control step. An information processing method, comprising: a step of specifying an end time or a preparation time of the event as a relative time. 24. An information processing program for exchanging data via a network, comprising: a storage control step for controlling storage of an event to be processed; and an execution for executing the event stored in the processing of the storage control step. A recording medium in which a computer-executable program is recorded, comprising: a step; and a time designation step of designating an end time or a preparation time of the event by a relative time. 25. An information processing apparatus for exchanging data via a network, wherein: an event storage means for storing an event to be processed; an execution means for executing the event stored in the event storage means; An information processing apparatus, comprising: a time designating means for designating a time to be performed; and connection information storage means for storing connection information necessary for exchanging data via the network for each of the events. 26. An information processing method for an information processing apparatus for exchanging data via a network, comprising: an event storage control step of controlling storage of an event to be processed; and executing the event stored in the processing of the event storage control step. An execution step of specifying the time at which the event is to be executed, and a connection information storage step of storing connection information necessary for exchanging data via the network for each event. An information processing method characterized by the following. 27. An information processing program for exchanging data via a network, comprising: an event storage control step of controlling storage of an event to be processed; and executing the event stored in the event storage control step. An execution step of specifying the time at which the event is to be executed, and a connection information storage step of storing connection information necessary for exchanging data via the network for each event. A recording medium on which a computer-executable program is recorded. 28. An information processing apparatus for exchanging data via a network, wherein: an event storage means for storing an event to be processed; a time designation means for designating a time at which the event is to be executed; And an execution unit for executing the event at every stage of preparation, start, end, stop, or restart. 29. The information processing apparatus according to claim 28, further comprising a stage validity designating unit for designating the validity of each stage. 30. An information processing method of an information processing apparatus for exchanging data via a network, comprising: an event storage control step of controlling storage of an event to be processed; a time specification step of specifying a time of executing the event; An execution step of executing the event stored in the process of the event storage control step at each stage of preparation, start, end, stop, or restart. 31. An information processing program for exchanging data via a network, comprising: an event storage control step for controlling storage of an event to be processed; a time designation step for designating a time at which the event is executed; A computer-executable program comprising: an execution step of executing the event stored in the process of the event storage control step at each stage of preparation, start, end, stop, or restart. Recording medium on which is recorded. 32. An information processing apparatus for exchanging data via a network, wherein: an event storage means for storing an event to be processed; a time designation means for designating a time at which the event is to be executed; An information processing apparatus comprising: an execution unit that executes a given event; and a user information storage unit that stores user information for each event. 33. An information processing method for an information processing apparatus for exchanging data via a network, comprising: an event storage control step of controlling storage of an event to be processed; a time specification step of specifying a time of executing the event; An information processing method comprising: an execution step of executing an event stored in the processing of the event storage control step; and a user information storage step of storing user information for each event. 34. An information processing program for exchanging data via a network, comprising: an event storage control step of controlling storage of an event to be processed; a time designation step of designating a time at which the event is executed; A computer-executable program comprising: an execution step of executing an event stored in the processing of the event storage control step; and a user information storage step of storing user information for each event. Recording media.