JP2007080198A - Digital device using randomly accessible recording medium - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To record file data input via a camera storage of IEEE 1394 separately into an additional information area and a data area of a disk. <P>SOLUTION: A RECEIVE FILE PARTIAL command is provided with a file_type field and a file_type_dependent_parameter field and a controller notifies a target of a type of transmission data. The target executes recording in either the additional information area or the data area according to the type of data. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to an apparatus having a system for performing data communication between devices by connecting electronic devices (hereinafter referred to as devices) using a data communication bus capable of communicating by mixing control signals and data. Is.

  When recording information such as moving images, still images, audio, etc. on a recording medium such as an optical disk, magnetic disk, magneto-optical disk, etc., the file is stored on the disk through a file system such as UDF (Universal Disk Format) or FAT (File Allocation Table). Recording is done in units. When recording a file, the recording medium is divided into two areas, an additional information area and a data area, for efficient file information management and data reproduction. There is a system for recording a data portion such as a moving image, a still image, and audio compressed / uncompressed data in a data area as an additional information portion. FIG. 8 shows an example of a disk divided into the above two areas and file data recorded on the disk. The disk shown in FIG. 8 has an additional information area on the inner periphery of the disk and a data area on the outer periphery. For example, when a digital video camera using the disk as a recording medium records moving image data, The footer portion is recorded in the additional information area, and the compressed moving image data is recorded in the data area. The finally recorded data exists on the disc as one file, and the arrangement of the data is in the order of “header”, “compressed image data”, and “footer” in FIG.

  In the conventional system shown in FIG. 9A, when an application accesses each file directly using the file system, if the number of files or the number of groups increases, it becomes difficult to collectively manage them. The problem is that it takes time to search for necessary information, and when specifying a file through the file system, the file type must be determined by the extension, and the same type of extension is used for video and audio files. When attached, there is a problem that it is difficult to discriminate and the search efficiency is lowered. Further, when reproducing a plurality of recorded files in time series, it is necessary to access all the files and rearrange them in order of recording time. In order to solve such a problem, a method of providing a CMF (Contents Management File) has been proposed as a method for managing files recorded on a recording medium. In the CMF, the file name of the file recorded on the recording medium, additional information, group information to which the file belongs, etc. are recorded. As shown in FIG. By providing CMF, which is a file for managing groups in a batch, applications can handle a large number of files on the disk through CMF and perform general processing such as grouping without directly communicating with the file system. Is possible.

  In recent years, IEEE1394 has become widespread as a digital video camera using the disk medium and a digital interface for connecting the digital camera to a PC or the like. When transferring data by connecting the digital interface, the personal computer requests a list of files and directories existing on the recording medium to the digital video camera or digital camera, and sends / receives file data based on the received list. I do. As a protocol for making a transmission / reception request as described above, the Camera Storage subunit is defined by the 1394 Trade Association, which is a standardization body of the IEEE1394 interface standard (TA Document 1999036, AV / C Camera Storage Subunit 1.0). The sub-unit and a controller such as a personal computer can perform a transaction via IEEE1394, and the controller can control the sub-unit and acquire information held by the sub-unit.

  This transaction is defined as FCP (Function Control Protocol) in IEC-61883-1, Consumer audio / video equipment-Digital interface-Part 1: General, and the controller performs a write transaction for a specific address of the target device. The command data is written using the target, and the target receiving the data of the write transaction writes the response data to the specific address of the controller using the write transaction. In the AV / C protocol, CTS (Command Transaction Set) is defined for each AV / C subunit. FIG. 10 shows a command frame format used in CTS. The ctype field indicates the type of command, and specifies the command type shown in FIG. The subunit_type and subunit ID fields are fields indicating which unit in the specified node is the command. The opcode and operand fields are fields for specifying the actual command contents. FIG. 11 shows a response frame format used in CTS. The response field indicates the type of response, and specifies the response type shown in FIG. The subunit_type and subunit ID fields are fields indicating from which unit in the node the response is received. The opcode and operand fields are fields for specifying response data.

  FIG. 12 shows a basic transaction procedure performed between the controller and the Camera Storage subunit via IEEE1394. The example of FIG. 12 shows a procedure for writing file data to a recording medium on the Camera Storage subunit. The controller detects the Camera Storage subunit on the IEEE1394 bus and transmits a VERSION status command to the detected Camera Storage Subunit. This command is a command for inquiring version information of the standard implemented by the Camera Storage subunit. When this command is received, the Camera Storage subunit sets the version of the implemented standard and sends a response to the controller. The format of the VERSION status command and response is shown in FIG. When a function compliant with AV / C Camera Storage Subunit 1.0 is implemented, 0x10 is set in the subunit_version_information field in the response frame of FIG. Camera Storage subunits are categorized according to the functions they implement, and receive file data using Asynchronous sender and Asynchronous transactions, which have the function of sending file data on recording media using Asynchronous transactions. "Asynchronous receiver" with the function, "isochronous sender" with the function to send the file data on the recording medium using the isochronous transaction, and "isochronous receiver" with the function to receive the file data using the isochronous transaction A profile is defined. FIG. 33 shows the profile and the value assigned to each profile. When the Camera Storage subunit receives the VERSION status command, the value of the implemented profile is set in the subunit_version_information_dependent_field of the response frame.

  The controller that has received the VERSION starus response frame determines the function of the Camera Storage subunit based on each field value of the response frame.

  Next, the controller transmits a MEDIA INFO command and a VOLUME INFO command to acquire information on the recording medium possessed by the Camera Storage subunit.

  FIG. 14 shows the format of the MEDIA INFO Control command and response. In the Camera Storage subunit, a physical volume and a logical volume are defined, the physical volume indicates a physical recording medium itself, and the logical volume indicates a logically partitioned area existing in the physical volume. The subfunction field in the control command is a field indicating what operation is requested to the subunit. FIG. 34 shows the meaning and value of subfunction. The controller sets “execute” for executing the command in the subfunction field of the command frame, and sends the command to the Camera Storage subunit. When the MEDIA INFO control command is received, the Camera Storage subunit sets the number of physical volumes that the device has (for example, the number of slots in which recording media can be set) in the number_of_physical_volume field, and the logical volumes that exist on each physical volume. (Eg, the number of partitions existing on each recording medium) is set in the number_of_logical_volume field.

  FIG. 15 shows the format of the VOLUME INFO control command and response. This command is a command for acquiring information on each logical volume of the Camera Storage subunit. The controller sets “execute” in the subfunction field, sets the volume number for acquiring information in the physical_volume_number and logical_volume_number fields, and transmits a command frame to the Camera Storage Subunit. When the VOLUME INFO Control command is received, the Camera Storage subunit sets the specified volume information in each field of the response frame and sends it to the controller. Media_generation_count in the response frame is a counter value that is counted up when a recording medium is inserted, and is updated when a removable recording medium is inserted into the device. This count value is initialized to “0” when the power is turned on, for example, and is incremented by one when updated. The attribute field indicates the attribute of the recording medium. FIG. 16 shows the format of the attribute field. The Camera Storage subunit checks the attribute of the specified volume and sets the corresponding attribute bit to “1”. The byte size of the volume specified in the maximum_capacity field is set, and the remaining recordable byte size is set in the free_space field.

  After acquiring the volume information, the controller transmits a FILE LIST Control command to acquire a list of files recorded on the recording medium of the Camera Storage subunit. FIG. 17 shows the format of the FILE LIST Control command and response. The controller sets “execute” in the subfunction field of the control command frame, and sets the target volume number in physical_volume_number and logical_volume_number. A value acquired by the VOLUME INFO control response is set in the mediga_generation_count field. The file_type field and the attribute field are fields that specify the type of entry included in the file list to be acquired. FIG. 35 shows the value of the file_type field, and FIG. 18 shows the format of the attribute field. The start_number field indicates from which entry of the corresponding file list the list is to be acquired, and the number_of_entries field of the command frame specifies the maximum number of entries to be acquired. The request_path_length field indicates the byte size of the subsequent request_path, and the request_path field indicates to which path in the specified volume the file list is acquired. When receiving the FILE LIST Control command, the Camera Storage subunit sets the file list for the request_path specified in the response frame and sends it to the controller. The file list is composed of directory entries of files and directories. 19 and 20 show the format of the directory entry. Each directory entry is composed of 20-byte data, and has file name or directory name, attribute, creation date and time, and file size information. In the eol field of the response frame, whether or not the last directory entry in the list transmitted in the response frame is the last directory entry in the list specified in the command frame is set. When this field is “0”, it indicates that the last directory entry in the list transmitted in the response frame is not the last directory entry in the list specified in the command frame. That is, since there is a continuation in the list, in order to acquire the entire list, the controller needs to acquire a continuation list by sending a FILE LIST Control command again. The number of directory entries set in the file_list field is set in the number_of_entries field of the response frame. In the file_list field, file_list for request_path specified in the command frame is set.

  A procedure for acquiring a file list by a FILE LIST Control command will be described with reference to FIGS.

  FIG. 21 shows an example of data existing on the recording medium of the Camera Storage subunit. These data are assumed to exist on a volume with physical_volume_number = 0 and logical_volume_number = 0. In FIG. 21, a “DCIM” directory exists under the root directory, and “100ABCDE”, “101ABCDE”, and “102ABCD” subdirectories exist below it, and JPEG files exist in each subdirectory. 22 and 23 show field values set in the FILE LIST Control command shown in FIG. 17 and part of directory entries set in the response file_list.

  First, FIG. 22A shows data for acquiring a list of subdirectories existing in the “DCIM” directory. Set start_number to 0x00 to specify that data is acquired from the top of the list. Set file_type to 0x00 and attribute to 0x01 to specify that all directory records are to be acquired. In the request_path field, set "\ DCIM" in ASCII code (add 0x00 as a terminal symbol at the end) and set the length to request_path_length.

  FIG. 22B shows the contents extracted from a part of the directory entry included in the file list created in accordance with the control command of the list request shown in FIG. Since there are three subdirectories “100ABCDE”, “101ABCDE”, and “102ABCDE” on the “\ DCIM” directory, the list is composed of three directory entries. The Camera Storage subunit sets a directory entry in the file_list field of the response frame. The maximum size of the response frame is 512 bytes, and the record is 20 bytes. Therefore, a maximum of 24 directory entries can be set in the file_list field. In this example, there are only three directory entries, so all directory entries can be set in the response frame, and the last directory entry in the list is included, so set the eol field to "1".

  By sending the command with the data shown in FIG. 22 set in the command frame and receiving the response, the controller obtains information on the “\ DCIM” directory, and then “100ABCDE” on the “\ DCIM” directory. “Sends a Control command to the Camera Storage subunit to obtain a list of still image files in the directory. FIG. 23A shows an example of data for acquiring a file list in the “\ DCIM \ 100ABCDE” directory. Set start_number to 0x00 to specify that data is acquired from the top of the list. Set file_type to 0x01 and attribute to 0x10 to specify that still image file records are to be acquired. In the request_path field, set "\ DCIM \ 100ABCDE" in ASCII code (add 0x00 as a terminal symbol at the end) and set the length to request_path_length.

  FIG. 23B shows the contents extracted from a part of the directory entry included in the file list created in accordance with the control command of the list request shown in FIG. There are three still image files "ABCD0001.JPG", "ABCD0002.JPG", "WXYZ0003.JPG" and one text file "Readme.txt" in the "\ DCIM \ 100ABCDE" directory. For the image list request, the file list is composed of directory entries of three still image files. These three directory entries are set in the file_list field of the response frame, 1 is set in the eol field, and the Camera Storage subunit transmits a response frame to the controller.

  By using the FILE LIST Control command, the controller obtains the path of the file and directory existing on the recording medium of the Camera Storage subunit, and sets the path of each file in the RECEIVE FILE Control command shown in FIG. A file can be recorded on a target directory.

  The RECEIVE FILE Control command is a command for inputting file data to the Camera Storage subunit and recording on the recording medium. When requesting this file recording operation to the Camera Storage subunit, the controller needs to set up a connection for file transfer between the Camera Storage subunit and an external device in order to perform recording. In the Camera Storage subunit, this connection is AV / C Asynchronous Serial Bus Connections (TA Document 1998011, AV / C Commands for management of Asynchronous Serial Bus Connections, Ver.1.0 and TA Document 1998016, AV / C Compatible Asynchronous Serial Bus Connections 1.0 ) Is used.

  FIG. 24 shows a file transfer procedure using the connection setting and RECEIVE FILE Control commands. First, the controller transmits the ALLOCATE and ATTACH commands to the AV / C unit on which the Camera Storage subunit is mounted in accordance with the procedure defined by AV / C Asynchronous Serial Bus Connections, and the controller and the AV / C unit Set the connection between. Next, a RECEIVE FILE Control command in which the file path for recording data is set is transmitted to the Camera Storage subunit. After receiving the RECIEVE FILE Control command, the Camera Storage subunit sends an INTERIM response to the RECEIVE FILE command, and then receives it from the controller device that is the producer according to the AV / C Asynchronous Serial Bus Connections procedure. Record to a separate file. When all data recording of the file is completed, the Camera Storage subunit sends a final response of RECEIVE FILE to the controller. After receiving the final response, the controller transmits DETACH and RELEASE commands to the AV / C unit in which the Camera Storage subunit is mounted, and releases the connection between the controller and the AV / C unit.

  FIG. 25 shows the format of the RECEIVE FILE Control command and response. The controller sets “execute” in the subfunction field, and sets the volume number and the generation count value of the volume in the physical_volume_number, logical_volume_number, and media_generation_count fields. In the file_path field, the path name of the file to be recorded is set, and in the file_path_length field, the length is set. The receive_mode field specifies the operation when the specified file already exists on the specified volume. FIG. 36 shows the meaning and value of receive_mode. The file_type field indicates the type of data input to the Camera Storage subunit. FIG. 37 shows the meaning and value of file_type. The destination_plug field specifies from which destination plug of the Camera Storage subunit the data to be recorded is input.

  FIG. 26 shows an example of a logical connection path between the controller and the Camera Storage subunit when performing file transfer with the RECEIVE FILE Control command. The controller uses the ALLOCATE and ATTACH commands to connect the controller's Asynchronous Output Plug [0] and the AV / C unit's Asynchronous Input Plug [0], so that the controller's Asynchronous Output Plug [0] and the Camera Storage subunit's Subunit Establish a connection with Destination Plug [0]. In the case of the connection shown in FIG. 26, 0x00 (indicating Subunit Destination Plug [0]) is set in the destination_plug field in the command frame of FIG. 25, and the controller transmits a RECEIVE FILE Control command to the Camera Storage subunit. . The Camera Storage subunit that has received the Control command sends an INTERIM response to the controller, and then the AV / C unit receives data from the Asynchronous Output Plug [0] of the controller according to the procedure of Asynchronous Serial Bus Connections. Input the data to the specified Subunit Destination Plug. The Cmaera Storage subunit records the data entered from the specified Subunit Destination Plug in the specified file, and when all the data is recorded, the Camera Storage subunit sends the final response to the controller and the RECEIVE FILE Control command End the operation.

  FIG. 27 shows a configuration example of a conventional digital video camera having the above-described function. First, a case where an image input from a camera is recorded will be described. An image input through the lens 101 is photoelectrically converted by the CCD 102 and then converted from an analog signal to a digital signal by the A / D converter 103. The digitally converted data is converted into MPEG-compressed moving image data by MPEG Codec 104.

  Formatter 105 creates MPEG file header data at the start of recording, creates a file on Disc 107 through File System 106, and writes the header information to the additional information area. Also, the MPEG moving image data input from the MPEG Codec 104 is sequentially written in the data area of the Disc 107 through the File System 106. At the end of recording, footer data of the MPEG file is created, a file is created on the Disc 107 through the File System 106, and header information is written in the additional information area. Formatter 105 also adds information about the created MPEG file to the CMF file.

  Next, a case where data recorded on the disc is reproduced will be described. A system controller (not shown) reads the CMF and displays the recorded file information on the Monitor Panel 109. The user selects one of the displayed files using a user interface such as an operation button (not shown). To start playback. The designated files are sequentially read from the Disc 107 through the File System 106 and input to the Formatter 105. Formatter 105 analyzes additional data such as header data and footer data, and outputs only compressed moving image data to MPEG Codec 104 to MPEG Codec 104. The MPEG Codec 104 decodes the input data and then outputs the decoded data to the D / A converter 108. The D / A converter 108 converts the input digital data into an analog signal and outputs it to the Monitor Panel 109 and the analog video output terminal 110.

  Next, a case where an MPEG file is recorded via IEEE1394 will be described. A controller such as a PC connected to the IEEE1394 terminal 111 accesses the above-mentioned Camera Storage subunit, and a recording operation is started by a RECEIVE FILE command. In accordance with the RECEIVE FILE command received from the IEEE1394 terminal 111, the IEEE1394 block 112 creates a file on the Disc 107 through the File System 106 and sequentially writes the received file data to the data area on the Disc 107 to receive all the file data. When recording is completed, the file is closed and the process is terminated.

Moreover, as a prior art example, patent document 1 and patent document 2 can be mention | raise | lifted, for example.
JP 2000-299710 A JP 2001-167556 A

  A device for recording digital data such as a digital video camera or a digital camera using the disk medium, when image data input from the camera by a user operation by the user is filed and recorded by a system in the main body, Data generated during header information generation, compressed / uncompressed digital image / sound data generation, and footer information generation can be written separately into an additional information area and a data area on the disk medium. When the file data input via the external digital interface is recorded, the digital interface processing block records the file data input by accessing the file system. Cannot be determined, and the additional information area It was not possible to write divided into over data area.

  In order to solve the above-mentioned problems, in the present invention, route information for inputting data, information indicating the type of the input data, information for designating an area for recording the input data, and the input Receiving a control signal including information indicating a path name for designating a file for recording data to be recorded and information for designating a recording start position of the designated file, and sending an asynchronous transaction from the designated route Is used to input file data, and the input file data is recorded in a specific area on a recording medium divided into a plurality of areas based on information indicating the type of data in the control signal.

  According to the present invention, by using the RECEIVE FILE PARTIAL Control command to divide a file into three parts and write sequentially, the MPEG2 file can be written separately into an additional information area and a data area.

  FIG. 1 shows a format of a RECEIVE FILE PARTIAL Control command and response for dividing and recording file data of the present invention.

  Each field except the start_offset, receive_size, close_mode, file_type, and file_type_dependent_parameter fields in the command frame has the same meaning and use as the field of the same name in the above-mentioned RECEIVE FILE Control command frame.

  The start_offset field is a field for designating from which position of the designated file the data is recorded, and designates the offset from the top of the file by the number of bytes. If the value set in this field indicates a position that does not exist on the file, the Camera Storage subunit rejects the command by sending a REJECTED response to the command. For example, if the specified file size is 1024 bytes and start_offset is set to 2048, a REJECTED response is sent. If the start_offset field is set to zero and the specified file does not exist, the Camera Storage subunit may create the specified file on the specified volume and record the input data.

  The receive_size field specifies how many bytes of data are recorded from the specified offset position. When the camera storage subunit finishes recording the specified number of bytes, it sets the number of bytes of the actually recorded data in the received_size field of the response frame and sends an ACCEPTED response to the controller.

  The close_mode field is a field for instructing a method for closing a file when data recording by this command is completed. FIG. 28 shows an example of values set in the close_mode field. 2 and 3 are diagrams showing the relationship between the close_mode and the file configuration after execution of the RECEIVE FILE PARTIAL command. As shown in Fig. 2, when data from the middle of a file on the recording medium to the position before the end of the file is overwritten with the RECEIVE FILE PARTIAL command, recording was performed when close_mode was "preserve" The file is closed while retaining the data after the last offset. If "terminate", the data after the last offset is deleted and the file is closed. As shown in FIG. 3, when data is written beyond the end of a file existing on the recording medium, the file is closed with the last recorded offset as the end of the file regardless of the value of close_mode.

  The file_type and file_type_dependent_parameter fields in FIG. 1 are fields for designating the type of data recorded by the RECEIVE FILE PARTIAL command. FIG. 29 shows an example of values set in the file_type field. The file_type field indicates the format of data input using the RECEIVE FILE PARTIAL command. FIG. 30 shows an example of values set in the file_type_dependent_field when “Exif 2.1” or “MPEG2” is set in the file_type. For example, when only the header part of an MPEG2 file is written using the RECEIVE FILE PARTIAL command, “MPEG2” is set in the file_type field and “Header” is set in the file_type_dependent_field.

  Next, a procedure for recording an MPEG2 file on a disc on a digital video camera using the RECEIVE FILE PARTIAL command will be described. FIG. 4 shows an example of data to be recorded in this embodiment. The data is MPEG2 format compressed video data, from 10 Kbyte (1024 bytes) header data, 3 Mbyte (3145728 bytes) MPEG2 compressed video data, and 2 Kbyte (2048 bytes) footer data. Assume that recording is performed with the file name “movie01.mpg” in the root directory of a volume with physical_volume_number = 0 and logical_volume_number = 0 on the Camera Storage subunit. It is assumed that a file named “movie01.mpg” does not exist in the root directory of the volume on the Camera Storage subunit.

  First, the controller transmits the ALLOCATE and ATTACH commands to the digital video camera connected by IEEE1394 to set the connection shown in FIG. 26, and then the camera storage subunit in the digital video camera is shown in FIG. Send RECIEVE FILE PARTIAL Control command. Upon receipt of the command, the Camera Storage subunit checks whether the specified file exists. In this case, the specified file does not exist, so the specified file is newly created and writable, and an INTERIM response is sent to the controller. Send. At this time, from the file_type and file_type_dependent_parameter values of the received command, the Camera Storage subunit determines that the data to be transmitted is the header data of the MPEG2 file, and creates the specified file in the additional information area. . The controller that has received the INTERIM response sequentially transmits the data of the header portion in FIG. 4 to the digital video camera in accordance with the procedure of AV / C Asynchronous Serial Bus Connections. The camera storage subunit sequentially records the data transmitted from the controller in a file created in the additional information area. When the recording of the received data is completed, the Camera Storage subunit closes the file and sends a response shown in FIG. 5 to the controller.

  When the response is received, the controller transmits a RECIEVE FILE PARTIAL Control command shown in FIG. 6 to the Camera Storage subunit in the digital video camera. The command shown in FIG. 6 is a command for additionally recording data to the file created by the command of FIG. 5, and instructs to record 3 Mbyte data from the end position of the created file. To do. The Camera Storage subunit that has received the command shown in FIG. 6 checks whether or not the specified file exists. In this case, since the file already exists on the medium, the specified file is opened in a writable state, and the controller Send an INTERIM response to. At this time, the value of the start_offset field is the same as the file size, and from the values of the file_type and file_type_dependent_parameter of the received command, the Camera Storage subunit determines that the transmitted data is compressed image data of an MPEG2 file. Then, the data writing position is moved onto the data area on the disk. The controller that has received the INTERIM response sequentially transmits the data of the compressed moving image portion in FIG. 4 to the digital video camera in accordance with the procedure of AV / C Asynchronous Serial Bus Connections. The Camera Storage subunit sequentially records the data sent from the controller in the data area. When the received data is recorded, the Camera Storage subunit closes the file and sends the response shown in FIG. 6 to the controller. To do.

  When the response is received, the controller transmits a RECIEVE FILE PARTIAL Control command shown in FIG. 7 to the Camera Storage subunit in the digital video camera. The command shown in FIG. 7 is a command for additionally recording data to the file additionally recorded by the command of FIG. 6, and 2 Kbytes of data are recorded from the end position of the additionally recorded file. It is an instruction to record. Upon receipt of the command, the Camera Storage subunit checks whether the specified file exists. In this case, since the file already exists on the media, the specified file is opened in a writable state, and INTERIM is sent to the controller. Send a response. At this time, the value of the start_offset field is the same as the file size, and from the value of the file_type and file_type_dependent_parameter of the received command, the Camera Storage subunit determines that the transmitted data is footer data of an MPEG2 file. The data write position is moved onto the additional information area on the disc. The controller that has received the INTERIM response sequentially transmits the data of the footer portion in FIG. 4 to the digital video camera according to the procedure of AV / C Asynchronous Serial Bus Connections. The camera storage subunit sequentially records the data transmitted from the controller in a file created in the additional information area. When the recording of the received data is completed, the Camera Storage subunit closes the file and sends a response shown in FIG. 7 to the controller.

The figure which shows the format of the RECEIVE FILE PARTIAL Control command and response of this invention. The figure for demonstrating the relationship between RECEIVE FILE PARTIAL Control command close_mode and the file after command execution. The figure for demonstrating the relationship between RECEIVE FILE PARTIAL Control command close_mode and the file after command execution. The figure which shows the structural example of the file recorded using RECEIVE FILE PARTIAL Control command. The figure which shows the example of the RECEIVE FILE PARTIAL Control command and response for dividing and recording an MPEG2 file. The figure which shows the example of the RECEIVE FILE PARTIAL Control command and response for dividing and recording an MPEG2 file. The figure which shows the example of the RECEIVE FILE PARTIAL Control command and response for dividing and recording an MPEG2 file. The figure which shows the example of the disc divided | segmented into the additional information area | region and the data area. The figure which shows the example of the system which used the conventional system and CMF. The figure which shows the command frame format used by CTS. The figure which shows the response frame format used by CTS. The figure which shows the basic transaction procedure between a controller and a Camera Storage subunit. The figure which shows the format of a VERSION Status command and a response. The figure which shows the format of a MEDIA INFO Control command and a response. The figure which shows the format of a VOLUME INFO Control command and a response. The figure which shows the format of the attribute field of a VOLUME INFO Control response. The figure which shows the format of a FILE LIST Control command and a response. The figure which shows the format of the attribute field of a FILE LIST Control response. The figure which shows the format of the directory entry which comprises a file list. The figure which shows the format of attribute_byte of a directory entry. The figure which shows the structural example of the file data recorded on the recording medium of a Camera Storage subunit. The figure which shows the data example set to a FILE LIST Control command frame, and a part of directory entry contained in a file list. The figure which shows the data example set to a FILE LIST Control command frame, and a part of directory entry contained in a file list. The figure which shows the transaction procedure in the case of transmitting file data to a Camera Storage subunit. The figure which shows the format of a RECEIVE FILE Control command and a response. The figure which shows the logical connection example between a controller and Camera Storage subunit in the case of transmitting file data to a Camera Storage subunit. The block diagram which shows the structure of the conventional digital video camera. A table showing the values to be set in the close_mode field of the RECEIVE FILE PARTIAL command. A table showing the values to be set in the file_type field of the RECEIVE FILE PARTIAL command. A table showing the values to be set in the file_type_dependent_parameter field of the RECEIVE FILE PARTIAL command. The table | surface which shows the value of the ctype field set to the command frame of CTS. The table | surface which shows the value of the response field set to the response frame of CTS. A table showing profile values for the Camera Storage subunit. The table which shows the value of the subfunction field in the Control command of Camera Storage subunit. The figure which shows the file_type field value of a FILE LIST Control command. The figure which shows the value of receive_mode of RECEIVE FILE Control command. The figure which shows the value of file_type of RECEIVE FILE Control command.

Claims (4)

  A digital device comprising a digital interface for transmitting and receiving serial data, performing transmission and reception of control signals and digital data via the digital interface, and handling digital data on the recording medium using a randomly accessible recording medium The path information for inputting data, the information indicating the type of the input data, the information for specifying the area for recording the input data, and the file for recording the input data Received a control signal including information indicating a path name for designating a file and information for designating a recording start position of the designated file, and data input using the Asynchronous transaction from the designated route A digital device characterized by recording.   2. The digital apparatus according to claim 1, wherein information indicating a type of data in the control signal is determined, and data input using the Asynchronous transaction is processed according to the determination result.   Recording and playback of file data using a randomly accessible recording medium, the function of managing the recording medium by dividing it into a plurality of areas, and recording a single file divided into the divided areas The divided recording means for performing recording according to claim 1, wherein the input data is recorded in any one of the divided areas in accordance with information indicating a type of data in the received control signal. 1. A digital device according to 1.   4. The digital apparatus according to claim 3, wherein the plurality of areas are an additional information area for recording additional information of a file and a data area for recording file data excluding the additional information.

Images