WO2000069122A1 - Procede de reconnaissance a la connexion reseau, systeme de reseau et terminal a connexion reseau - Google Patents
Procede de reconnaissance a la connexion reseau, systeme de reseau et terminal a connexion reseau Download PDFInfo
- Publication number
- WO2000069122A1 WO2000069122A1 PCT/JP2000/002934 JP0002934W WO0069122A1 WO 2000069122 A1 WO2000069122 A1 WO 2000069122A1 JP 0002934 W JP0002934 W JP 0002934W WO 0069122 A1 WO0069122 A1 WO 0069122A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- command
- network
- response
- terminal device
- data
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims description 70
- 230000004044 response Effects 0.000 claims abstract description 102
- 238000012545 processing Methods 0.000 claims abstract description 20
- 230000005540 biological transmission Effects 0.000 claims description 46
- 230000008569 process Effects 0.000 claims description 44
- 238000010586 diagram Methods 0.000 description 44
- 230000006870 function Effects 0.000 description 18
- 230000015654 memory Effects 0.000 description 11
- 230000005236 sound signal Effects 0.000 description 9
- 230000001419 dependent effect Effects 0.000 description 8
- 230000001276 controlling effect Effects 0.000 description 6
- 238000004891 communication Methods 0.000 description 4
- 230000003287 optical effect Effects 0.000 description 4
- 230000007704 transition Effects 0.000 description 4
- 230000006835 compression Effects 0.000 description 3
- 238000007906 compression Methods 0.000 description 3
- 235000002597 Solanum melongena Nutrition 0.000 description 2
- 244000061458 Solanum melongena Species 0.000 description 2
- 230000003044 adaptive effect Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 2
- 239000000284 extract Substances 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 230000003321 amplification Effects 0.000 description 1
- 230000003466 anti-cipated effect Effects 0.000 description 1
- 238000001193 catalytic steam reforming Methods 0.000 description 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 238000012790 confirmation Methods 0.000 description 1
- 125000004122 cyclic group Chemical group 0.000 description 1
- 230000007423 decrease Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000003199 nucleic acid amplification method Methods 0.000 description 1
- 238000003752 polymerase chain reaction Methods 0.000 description 1
- 230000001105 regulatory effect Effects 0.000 description 1
- 239000011347 resin Substances 0.000 description 1
- 229920005989 resin Polymers 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/40—Bus networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client
- H04N21/63—Control signaling related to video distribution between client, server and network components; Network processes for video distribution between server and clients or between remote clients, e.g. transmitting basic layer and enhancement layers over different transmission paths, setting up a peer-to-peer communication via Internet between remote STB's; Communication protocols; Addressing
- H04N21/643—Communication protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
- H04N21/43—Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
- H04N21/436—Interfacing a local distribution network, e.g. communicating with another STB or one or more peripheral devices inside the home
- H04N21/4363—Adapting the video stream to a specific local network, e.g. a Bluetooth® network
- H04N21/43632—Adapting the video stream to a specific local network, e.g. a Bluetooth® network involving a wired protocol, e.g. IEEE 1394
Definitions
- Network connection recognition method for network system, and network connection terminal device
- the present invention relates to a network connection recognizing method suitable for recognizing devices connected by, for example, an IEEE 1394 bus line, a network system to which the connection recognizing method is applied, and a network system. It relates to a connection terminal device.
- Audio equipment and video equipment that can transmit information to each other via a network using the IEEE (The Institute of Electrical and Electronics Engineers) 13 9 4 serial serial bus. (Hereinafter, these devices are referred to as AV devices).
- AV devices In this network, certain commands (AV / C
- AV / C command By using the Command Transaction Set (hereinafter referred to as AV / C command), it is possible to control AV devices connected to the network.
- AV / C command By using the Command Transaction Set (hereinafter referred to as AV / C command), it is possible to control AV devices connected to the network.
- AV / C command For details of the IEEE1394 system and the AV command, see the AV / C Digital Interface Command Set General Specification published by the 1394 Trade Association.o
- an AV device connected by the IEEE1394 bus line for example, there has been a digital video camera device or a digital video tape recording / reproducing device of a standard called DV system. That is, two recording / reproducing devices are prepared, the two devices are connected by a bus line conforming to the IEEE1394 standard, and digital video data reproduced from one device is transmitted to the bus line. It was transmitted by the other device and recorded. In this way, by connecting an AV device using an IEEE1394-type bus line, large-volume data such as digital video data can be transmitted in real time, and video data can be edited efficiently.
- the data is not limited to the digital video data described above, but can transmit other various digital data, and can transmit various data handled by AV equipment.
- many devices for example, 64 devices
- video data, audio data, and control data can be transmitted among the many devices. possible transmission of such data dice 0
- an IRD Integrated Receiver Decoder
- DVC Digital Video Cassette Recorder
- a recording / reproducing device using a magnetic tape as a recording medium, and video data received by IRD can be recorded by DVCR.
- the same bus line is connected to a digital audio disc recording / reproducing device that uses a magneto-optical disc called MD (Mini Disc) as a recording medium, and the audio data received by the IRD is transmitted to the same bus line. It is possible to record with this audio recording / reproducing device (MD device).
- MD magneto-optical disc
- node IDs can only identify individual devices, and the functions of the devices to which the node IDs are assigned are determined by the network. It is difficult to recognize just by connecting, for example, by connecting the above-mentioned IRD, DVCR, and MD device to one network, and recording the video data of the video channel received by the IRD on the DVCR.
- the IRD determines which node ID device is a DVCR and which node ID device is an MD device. It cannot be determined just by being connected to the network.
- An object of the present invention is to make it possible to easily recognize the type of a device connected via a network such as the IEEE1394 system.
- a first invention is a network connection recognition method for recognizing a device connected to a predetermined network,
- a third process for specifying the type of device is executed. In this way, after determining the type of connected device in the response to the command inquired in the first process, the command corresponding to that type is sent, and the command corresponding to each device is sent. Can be used to accurately identify the type of connected device.
- the second process is a process of sending a command to open the other party's disc, and a process of sending a command to read the opened disc.
- the media type of the device is specified by the read. It is something to do. By doing so, it becomes possible to perform a process of determining details of a device that uses a disc in which media type data is described in the disc.
- the third invention is a network connection recognition method according to the first invention, wherein
- the second process is a process of sending a command for inquiring the format of the media.
- the device is identified as a device of a predetermined media format. It was done. By doing this, if the device uses tape or other media as media, the type of device can be determined. Processing can be performed.
- a fourth invention is a network connection recognition method according to the first invention, wherein:
- the process of recognizing the above devices is executed after the node ID of each device connected to the above network is obtained when the bus line that constitutes the above network is reset. is there. This makes it possible to reliably determine the type of each connected device when resetting the bus, for example, when the network configuration changes.
- a fifth aspect of the present invention in a network system configured by connecting a plurality of terminal devices via a predetermined network,
- a command storage unit for storing the second command, and the first command and the second command stored in the command storage unit are sequentially transmitted to the network, and the response is sent.
- a first response to which unit-type or subunit-type data provided in the second terminal device is added is sent, and the first response is sent.
- a data transmission unit is provided for sending the second response by adding the data specified by the command.
- the response to the first command causes the first terminal connected to the first terminal device to respond to the first command.
- the second terminal device includes a descriptor storage unit that stores, as a descriptor, data relating to the configuration of the device.
- the second command stored in the command storage unit provided in the first terminal device is a command for opening the descriptor stored in the disk storage unit of the second terminal device. Command to read the file and its opened descriptor.
- the network control unit specifies a media type handled by the second terminal device in response to a command for reading the descriptor. In this way, when the second terminal device is a device whose media type is described in a descriptor in a descriptor, the details of the second terminal device are described in the first terminal device. To be able to judge.
- the second terminal device includes a storage unit that stores data relating to a format handled by the device,
- the second command stored in the command storage unit provided in the first terminal device is a command for inquiring about the format of the media
- the network control unit identifies the second terminal device as a device of a predetermined media format when there is a correct response to a command inquiring about the format of the media. Things. By doing so, when the second terminal device is a device that uses tape or the like as a medium, it is possible for the first terminal device to determine the type of the second terminal device. Nana You.
- An eighth invention is directed to the network system according to the fifth invention, wherein the network control unit is configured to, when a bus line constituting the network is reset, reset each of the bus lines connected to the network. After the node ID of the terminal device is obtained, the processing of transmitting the first and second commands is performed. By doing so, it becomes possible to reliably determine the type of the second terminal device to which the first terminal device is connected at the time of a bus reset such as when the network configuration is changed. .
- the type of device connected to this terminal device can be specified using commands corresponding to each device, and the device connected to this terminal device via a network can be identified. The type can be specified accurately.
- the tenth invention is the network connection terminal device according to the ninth invention.
- the second command stored in the command storage unit is a command for opening the other party's disk descriptor and a command for reading out the opened disk descriptor.
- the network controller reads the descriptor.
- the media type of the device is specified.
- the eleventh invention is a network connection terminal device according to the ninth invention, wherein:
- the second command stored in the command storage unit is a command for inquiring about the format of the media.
- the network control unit identifies a device of a predetermined media format when there is a correct response to a command inquiring about the format of the media. is there . By doing so, when a device that uses a tape or the like as a medium is connected, a process of determining the type of the device becomes possible.
- the network control unit obtains the node ID of each device connected to the network when the bus line constituting the network is reset and obtains the first and the second after the node ID of each device connected to the network.
- the processing for sending the second command is performed. By doing so, it becomes possible to reliably determine the type of each connected device at the time of a bus reset such as when the configuration of the network to which this terminal device is connected is changed.
- a thirteenth invention is directed to a network connection terminal device connected to a predetermined network
- a data transmission unit that communicates with another terminal device in the network
- the command determining section determines the first command, it generates a first response to which a unit type or subunit type data included in the device is added, and transmits the first response after transmitting the first response.
- the command determining unit determines the second command, it generates a response to which the data specified by the command is added, and transmits the generated response from the data transmission unit. And a generation unit.
- a fourteenth invention is a network connection terminal device according to the thirteenth invention, wherein:
- a descriptor storage unit that stores data related to the configuration of the device as a descriptor is provided.
- a storage unit for storing data related to the format handled by the device is provided.
- FIG. 1 is a block diagram showing a configuration example of an entire system according to an embodiment of the present invention.
- Figure 2 is a block diagram showing an example of the configuration of a digital satellite broadcast receiver.
- FIG. 3 is a block diagram showing a configuration example of a video recording / reproducing apparatus.
- FIG. 4 is a block diagram showing a configuration example of an audio recording / reproducing apparatus.
- FIG. 5 is an explanatory diagram showing an example of a frame structure defined by the IEEE1394 system.
- FIG. 6 is an explanatory diagram showing an example of the structure of the address space of the CRS architecture.
- Figure 7 is an explanatory diagram showing an example of the location, name, and function of the main CRS.
- Fig. 8 is an explanatory diagram showing an example of the configuration of the plug control register.
- FIG. 9 is an explanatory diagram showing a configuration example of oMPR, oPCR, iMPR, and iPCR.
- FIG. 10 is an explanatory diagram showing an example of the relationship between a plug, a plug control register, and a transmission channel.
- FIG. 11 is an explanatory diagram showing an example of the data structure based on the hierarchical structure of the descriptor.
- FIG. 12 is an explanatory diagram showing an example of the data structure of the descriptor.
- FIG. 13 is an explanatory diagram showing an example of the generation ID of FIG.
- FIG. 14 is an explanatory diagram showing an example of the list ID in FIG.
- FIG. 15 is an explanatory diagram showing an example of a stack model of the AVZC command.
- FIG. 16 is an explanatory diagram showing an example of the relationship between the AV / C command and the response.
- FIG. 17 is an explanatory diagram showing an example of the relationship between the AV / C command command and the response in more detail.
- FIG. 18 is an explanatory diagram showing an example of the data structure of the AV / C command.
- FIG. 19 is an explanatory diagram showing a specific example of the AV / C command.
- FIG. 20 is an explanatory diagram showing a specific example of the command and response of the AVZC command.
- FIG. 21 is a flowchart showing an example of device identification processing according to an embodiment of the present invention.
- FIG. 22 is an explanatory diagram showing an example of the format of a sub-toinform command according to an embodiment of the present invention.
- FIG. 23 is an explanatory diagram showing an example of a response format for a submit-in-command according to an embodiment of the present invention.
- FIG. 24 is an explanatory diagram showing a format example of the unit info command according to the embodiment of the present invention.
- FIG. 25 is an explanatory diagram showing an example of the response format to the unity info command according to the embodiment of the present invention.
- FIG. 26 is an explanatory diagram illustrating an example of a submit type according to an embodiment of the present invention.
- FIG. 27 is an explanatory diagram showing an example of the format of an open disk drive evening command according to an embodiment of the present invention.
- FIG. 28 is an explanatory diagram showing an example of the format of a lead descriptor command according to an embodiment of the present invention.
- FIG. 29 is an explanatory diagram showing an example of a disk script of a disk subsystem according to an embodiment of the present invention.
- FIG. 30 is an explanatory diagram showing an example of the data configuration of the media type of the disk drive of the disk subsystem according to the embodiment of the present invention. .
- FIG. 31 is an explanatory diagram showing a format example of a tape playback command according to an embodiment of the present invention.
- FIG. 32 is an explanatory diagram showing an example of a format of a response to a tape playback command according to one embodiment of the present invention.
- FIG. 33 is a unit directory according to another embodiment of the present invention. It is explanatory drawing which shows the example of a tree.
- FIG. 34 is an explanatory diagram showing an example of correspondence between a protocol and a command set according to another embodiment of the present invention.
- FIG. 35 is an explanatory diagram showing an example of a CTS code according to another embodiment of the present invention.
- FIG. 36 is an explanatory diagram showing an example of key data according to still another embodiment of the present invention.
- FIG. 1 shows an example in which three AV devices 100, 200, and 300 are connected.
- the devices connected to the bus 1 are IRD (Integrated Receiver Decoder) 100, which is a digital satellite broadcast receiver, each of which is a device having an IEEE 1394 terminal.
- IRD Integrated Receiver Decoder
- DVCR digital video cassette recorder
- MD Mini Disc
- IRD100 connected to bus 1 and DVCR2
- An electronic device such as an MD / MD device 300 is called a unit.
- an AV / C Digital Interface Command Set General Specification (hereinafter referred to as an AVZC command) of an AV / C Command Transaction Set is used.
- the information stored in each unit can be read and written to each other by using a descriptor specified in the following.
- the descriptor is data relating to details of the unit written in a predetermined description format in a memory connected to a control unit of each unit (equipment).
- the details of the AV / C command are described in the AV / C Digital Interface Command Set General Specification published by the 1394 Trade Association.
- each function of the unit is called a subunit.
- the IRD 100 which receives and decodes digital satellite broadcasts and the like, is connected to a parabolic antenna 11 and a digital tuner 12 connected to the parabolic antenna 11 transmits a signal of a predetermined channel. Is received and decoded.
- the controller 13 built in the IRD 100 controls the reception operation such as reception and decoding.
- a channel that can receive the IRD 100 is a video channel (a so-called ordinary television broadcasting channel) that can obtain video data and audio data attached to the video data.
- an audio channel where only audio data such as music can be obtained
- a data channel where various data such as data for browsing the Internet of the Internet can be obtained.
- the audio data transmitted on the audio channel may be a channel that can obtain audio data compressed by the MPEG method or the like, or may be an audio signal that is compressed and encoded by a high-efficiency compression coding method such as an ATRAC Adaptive Transform Acoustic Coding (ATRAC) method.
- ATRAC ATRAC Adaptive Transform Acoustic Coding
- the channel can obtain data.
- the controller 13 also controls the data transmission with the IRD 100 via the bus 1. In this case, the controller 13 transmits the data via the bus 1 overnight, and the other devices 200, 30 connected via the bus 1 using the AVZC command described above.
- the operation of 0 can be controlled.
- the video data and the audio data of the video channel received by the IRD 100 are transmitted to the DVCR 200, and the recording operation in the DVCR 200 is controlled to control the mounted video cassette.
- Video recording can be performed on a video tape inside the unit. Also,
- the audio data of the audio channel received by the IRD 100 is transmitted to the MD device 300, and the recording operation of the MD device 300 is controlled, so that the attached magneto-optical disk is mounted. Recording can be performed to record audio data.
- recording can be performed to record audio data.
- the DVCR 200 is a tape recording / reproducing apparatus capable of recording and reproducing video data and audio data and data accompanying these data as digital data on a video tape.
- the recording / reproducing apparatus uses a format media called DVHS.
- the controller 210 of the DVCR 200 receives a recording or playback instruction operation, a recording reservation operation, or the like from the user, and controls the entire DVCR 200.
- the analog tuner 22 extracts a signal of a predetermined channel from the input analog signal under the control of the controller 21, converts the signal into digital data, and supplies the digital data to the tape recording / reproducing unit 23.
- the video data and audio data supplied from the analog tuner 22 or the video data and audio data supplied from the IRD 100 or the like via the bus 1 are transferred to a magnetic tape. Record in.
- the MD device 300 is capable of recording and reproducing audio data and data accompanying audio data as digital data on a format magneto-optical disc called a mini disc (MD) ⁇ It is a possible disc recording and playback device.
- the controller 31 of the MD device 300 receives a recording or playback instruction operation, a recording reservation operation, or the like from the user, and controls the entire MD device 300.
- the disc recording / reproducing section 32 records audio data or the like input from the bus 1 or another input section on a magneto-optical disc. In this case, the recording on the disc is recorded as data compressed and encoded by the ATRAC method. Therefore, if the audio data is transmitted via the bus 1 and the data is of the ATRAC type, the transmitted audio data is recorded on the disk as it is.
- the AVZC descriptor for each device is set and stored in the controllers 13, 21, and 31 of the devices 100, 200, and 300, respectively. It has a storage unit, and data such as commands necessary to read and write the descriptor is also stored in this storage unit.
- FIG. 2 is a diagram showing a specific configuration example of the IRD 100.
- Broadcast radio waves from the satellite are received by the antenna 8, input to the terminal 100a, and supplied to the tuner 101 as program selection means provided in the IRD 100.
- Each circuit of the IRD 100 operates under the control of the central control unit (CPU) 111, and a signal of a predetermined channel is obtained by the tuner 101.
- the received signal obtained by the tuner 101 is supplied to a descramble circuit 102.
- the descrambling circuit 102 is based on the encryption key information of the contract channel stored in the IC card (not shown) inserted into the IRD 100 main unit. Only the multiplexed data of the (or unencrypted channel) is extracted and supplied to the demultiplexer 103.
- the demultiplexer 103 sorts the supplied multiplexed data for each channel, extracts only the channel specified by the user, and converts the video stream composed of the bucket of the video portion into M.
- an overlap stream comprising a packet of an audio portion is also transmitted to the MPEG audio decoder 109.
- the MPEG video decoder 104 decodes the video stream to restore the video data before compression encoding, and sends this to the NTSC encoder 106 via the adder 105. .
- the NTSC encoder 106 converts the video data into NTSC-format luminance signals and color-difference signals, and converts them into NTSC-format video data. And sends it to the digital Z-analog converter 107.
- the digital Z analog converter 107 converts the NTSC data into an analog video signal and supplies it to a connected receiver (not shown).
- the IRD 100 in this example is a GUI data generation unit 100 that generates video data for various displays for a graphical “user” interface (GUI) based on the control of the CPU 111. 8 is provided.
- the GUI video data (display data) generated by the GUI data generation unit 108 is supplied to an adder 105, and is superimposed on the video data output from the MPEG video decoder 104.
- the GUI video is superimposed on the received broadcast video.
- the MPEG audio decoder 109 restores the PCM audio data before compression encoding by decoding the audio stream, and sends it to the digital-Z analog converter 110.
- the digital Z-analog converter 110 converts the PCM audio data into analog signals to generate LCh audio signals and RCh audio signals, which are connected to the speakers of the audio playback system. (Not shown) and output as audio.
- the IRD 100 of this example supplies the video stream and audio stream extracted by the demultiplexer 103 to the IEEE 1394 interface unit 112, Interface section 1
- the received video stream and audio stream are transmitted in the isochronous transfer mode.
- the GUI data generation unit 108 generates the video data for the GUI
- the video data is supplied to the interface unit 112 via the CPU 111 and the In the evening phase
- the video data for GUI can be sent to the bus line 1.
- a work RAM 113 and a RAM 114 are connected to the CPU 111, and control processing is performed using these memories.
- an operation command from the operation panel 115 and a remote control port signal from the infrared ray receiving unit 116 are supplied to the CPU 111 so that operations based on various operations can be executed. It is like that.
- the CPU 111 can also determine the command and response transmitted from the bus line 1 to the interface unit 112 so that the CPU 111 can determine it.
- FIG. 3 is a block diagram showing a configuration example of the DVCR 200.
- the recording system consists of a tuner built in the DVCR200.
- Digital broadcast data obtained by receiving a predetermined channel at 201 is supplied to an MPEG (Moving Picture Expers Group) encoder 202, and a video signal suitable for recording, for example, MPEG-2 video data and Assume audio data. If the received broadcast data is in the MPEG2 format, the processing by the encoder 202 is not performed.
- MPEG Motion Picture Expers Group
- the data encoded by the MPEG encoder 202 is supplied to a recording / reproducing unit 203 to perform a recording process, and the processed recorded data is recorded to a recording head in a rotary head drum 204. To the magnetic tape in the tape cassette 205.
- the MPEG encoder 202 After being converted into digital data by the analog-to-digital converter 206, the MPEG encoder 202 converts the data into, for example, MPEG-2 video data and audio data, and supplies the data to the recording / playback unit 203 for recording And supplies the processed recording data to the recording head in the rotating head drum 204 to be recorded on the magnetic tape in the tape cassette 205.
- the playback system consists of a magnetic tape in the tape cassette 205 played back by the rotating head drum 204 and a signal obtained by the recording and playback unit 2
- the reproduction process is performed in 03 to obtain video data and audio data.
- the video data and audio data are supplied to an MPEG decoder 207, for example, to perform decoding from the MPEG 2 system.
- the decoded data is supplied to the digital-to-analog converter 208 to be converted into analog video signals and audio signals and output to the outside.
- the DVCR 200 also has an interface section 209 for connecting to an IEEE 1394 bus, and the interface section 209 is provided from the IEEE 1394 bus side.
- the video data and audio data obtained in FIG. 9 are supplied to a recording / reproducing unit 203 so that they can be recorded on a magnetic tape in a tape cassette 205.
- video data and audio data reproduced from the magnetic tape in the tape cassette 205 are supplied from the recording / reproducing unit 203 to the interface unit 209, and are supplied to the IEEE 1394 bus side. It can be sent out.
- this DV During transmission via this interface section 209, this DV
- DVCR200 When the method of recording on a medium (magnetic tape) with CR200 (for example, the MPEG2 method described above) is different from the method of data transmitted on the IEEE1394 bus, DVCR200 is used. Alternatively, the method conversion may be performed by the internal circuit.
- the recording process and the reproduction process in the DVCR 200 and the transmission process via the interface unit 209 are executed under the control of the central control unit (CPU) 210.
- a memory 211 which is a peak RAM, is connected to the CPU 210.
- the operation information from the operation panel 2 12 and the control information from the remote control device received by the infrared receiver 2 13 are supplied to the CPU 210, and the operation information and the control information corresponding to the operation information and the control information are provided. Operation control is performed.
- the interface section 209 transmits control data such as AVZC commands to be described later via an IEEE1394-type bus. When the data is received, the data is supplied to the CPU 210 so that the CPU 210 can perform the corresponding operation control.
- FIG. 4 is a block diagram showing a configuration example of the audio recording / reproducing apparatus 300.
- the audio recording / reproducing apparatus 300 of this example uses a magneto-optical disc or an optical disc housed in a resin package called MD (mini disc) as a recording medium, and outputs an audio signal. It is a device that records and plays back digital data.
- MD mini disc
- the configuration of the recording system is as follows. Two-channel analog audio signals input externally are converted to digital audio data by the analog-to-digital converter 301.
- the converted digital audio data is ATR A
- a C (Adaptive Transform Acoustic Coding) encoder 302 which encodes the audio data compressed by the ATRAC method.
- the input audio data is directly supplied to the ATR AC encoder 302 without passing through the analog / digital converter 301.
- the data encoded by the encoder 302 is supplied to a recording / reproducing unit 303 for processing for recording, and an optical pickup 304 is driven based on the processed data. Then, data is recorded on a disc (magneto-optical disc) 305. At the time of recording, the magnetic field is modulated by a magnetic head (not shown).
- the configuration of the playback system is as follows: data recorded on a disc (a magneto-optical disc or an optical disc) 305 is read out by an optical pickup 304, and the recording / reproducing unit 303 performs a playback process.
- the reproduced audio data is supplied to an ATRAC decoder 306 to be decoded into digital audio data of a predetermined format, and the decoded audio data is converted to a digital Z analog converter 3. 0 7 to convert to 2-channel analog audio signal and output. Also, digital audio data is output directly to the outside.
- the audio data decoded by the ATRAC decoder 306 is directly output without passing through the digital-to-Z analog converter 307.
- the output audio signal converted into an analog signal is supplied to an amplifier device 391 to perform audio output processing such as amplification, and the two speakers 392 and 393 connected to two channels. It is designed to output audio (audio).
- the audio recording / reproducing apparatus 300 includes an interface section 308 for connecting to an IEEE 1394 system bus, and this interface is provided from the IEEE 1394 bus side.
- the audio data obtained in the interface section 308 is supplied to the recording / reproducing section 302 via the ATRAC encoder 302, and can be recorded on the disk 305.
- the audio data reproduced from the disc 305 is supplied from the recording / reproducing unit 302 to the interface unit 308 via the ATRAC decoder 306, and the IEEE 1394 system is used. It can be transmitted to the bus side.
- the recording process and the reproducing process in the audio recording / reproducing device 300 and the transmission process via the interface unit 308 are executed under the control of the central control unit (CPU) 310.
- CPU central control unit
- a memory 311 which is a work RAM is connected.
- operation information from the operation panel 312 is supplied to the CPU 310, and operation control corresponding to the operation information is performed.
- the interface unit 308 receives control data such as an AVZC command described later via the IEEE 1394 bus, the data is transmitted to the CPU 31. 0 so that the CPU 310 can perform the corresponding operation control.
- FIG. 3 is a diagram showing a cycle structure.
- data is divided into packets and transmitted in a time-division manner on the basis of a cycle having a length of 125 ⁇ S.
- This cycle is generated by a cycle start signal supplied from a node having a cycle mass function (any device connected to the bus).
- the isochronous bucket secures a band (a time unit but called a band) necessary for transmission from the beginning of every cycle. For this reason, the transmission within a certain period of time is guaranteed in the iso-mouth transmission.
- the node In order for a given node to perform isochronous eggplant transmission, the node must support the isochronous function. In addition, at least one of the nodes corresponding to the asynchronous function must have a cycle master function. Further, at least one of the nodes connected to the IEEE 1394 serial bus must have the function of an isochronous resource manager.
- IEEE 13944 conforms to the CSR (Control & Status Register) architecture with a 64 bit address space specified in ISO IEC13213.
- Fig. 6 is a diagram for explaining the structure of the address space of the CSR architecture.
- the upper 16 bits are a node ID indicating a node on each IEEE 1394, and the remaining 48 bits specify an address space given to each node. Used for The upper 16 bits are further divided into 10 bits of bus ID and 6 bits of physical ID (node ID in a narrow sense). A value where all bits are 1 is used for special purposes, so you can specify 1023 buses and 63 nodes.
- the node ID is reassigned when there is a bus reset.
- the bus reset is
- the space specified by the upper 20 bits is the 248-byte CSR-specific register or IEEE 13 9 4 Initialization register space used for unique registers, etc. (Initial Register Space), Private Space (Private Space), Initialization Memory Space (Initial Memory Space), etc. If the space specified by the upper 20 bits is the initialization register space, the space defined by the 28 bits is a configuration ROM (Configuration read only memory), a node, etc. Initial unit space and Plug Control Register (PC) used for specific applications
- Figure 7 illustrates the offset addresses, names, and functions of key CSRs.
- the offset in Fig. 7 indicates the offset address from address FFFFFOOOOOOOh where the initialization register space starts (the number ending with h indicates hexadecimal notation).
- the Bandwidth Available Register having an offset of 22 Oh indicates the bandwidth that can be allocated to the EAS communication. Valid only by the value of the node operating as the Ronus resource manager. In other words, each node has the CSR shown in Fig. 6, but only the ISO Resource Manager for the Bandwidth Available Registry is valid. In other words, the bandwidth-available register is substantially only owned by the Isochronous Resource Manager. In the bandwidth-available register, the maximum value is stored when no band is allocated to the isochronous communication, and the value decreases each time a band is allocated.
- the Channels Available Register at offsets 224 h to 228 h correspond to each of the 0 to 63 channel numbers, and have 0 bits. If it is, it indicates that the channel is already assigned. Only the channel available registry of the node that is operating as the resource manager is valid o
- a configuration ROM based on the general-purpose R0M (read only memory) format is placed at address 200h to 400h in the initialization register space. Is done.
- a bus info block, a knowledge directory, and a unit directory are arranged in the configuration section R0M.
- the company ID (Company ID) in the bus-in-a-block stores the ID number indicating the device manufacturer.
- the chip ID (Chip ID) stores the only ID unique to the device and unique in the world without duplication with other devices.
- FIG. 8 is a diagram illustrating the configuration of a PCR.
- the PCR has 0 PCR (output Plug Control Register) indicating an output plug and iPCR (input Plug Control Register) indicating an input plug.
- the PCR has a register o MPR (output Master Plug Register) and an i MPR (input Master Plug Register) indicating information of an output plug or an input plug unique to each device.
- Each device does not have multiple oMPRs and multiple iMPRs, but can have multiple 0PCRs and iPCRs corresponding to individual plugs depending on the capabilities of the device.
- the PCR shown in FIG. 8 has 31 oPCRs and iPCRs each. The flow of isochronous data is controlled by manipulating registers corresponding to these plugs.
- FIG. 9 is a diagram showing the configuration of oMPR, oPCR, iMPR, and iPCR.
- 9A shows the configuration of the oMPR
- FIG. 9B shows the configuration of the oPCR
- FIG. 9C shows the configuration of the iMPR
- FIG. 9D shows the configuration of the iPCR.
- the data rate capability of the two bits on the MSB side of the MPR and i MPR is a code indicating the maximum transmission rate of the isochronous eggplant data that the device can transmit or receive. Is stored.
- the broadcast channel base of the MPR specifies the number of the channel used for broadcast output (broadcast output).
- the 5-bit number of output plugs on the LSB side of the MPR is the number of output plugs that the device has, that is, 0
- a value indicating the number of PCRs is stored.
- the 5-bit number of input plugs on the LSB side of the iMPR stores the number of input plugs of the device, that is, a value indicating the number of iPCRs. You.
- the primary and secondary extension fields are areas defined for future extensions.
- the MSB of PCR and iPCR online indicates the usage status of the plug. That is, a value of 1 indicates that the plug is online, and a value of 0 indicates that it is offline.
- the value of the broadcast connection counter of PCR and iPCR indicates whether the broadcast connection is active (1) or not (0).
- the point-to-point connection counter that has a 6-bit width of PCR and iPCR is the point-to-point connection counter, It represents the number of point-to-point connections, a point-to-point connection (a so-called p-p connection), where one particular node and another feature are connected. This is a connection for transmitting data only between certain nodes.
- the value of the channel number having a 6-bit width of PCR and iPCR indicates the number of the isochronous channel to which the plug is connected.
- the PCR 2-bit data rate value indicates the actual transmission rate of the bucket of isochronous data output from the plug. 0
- the code stored in () indicates the over-bandwidth of isochronous communication. o
- the value of the payload of the PCR having a width of 10 bits represents the maximum value of the data contained in the isochronous bucket that the plug can handle.
- FIG. 10 is a diagram showing the relationship between a plug, a plug control register, and an isochronous channel.
- the devices connected to the IEEE1394 bus are shown as AV devices (AV devices) 71 to 73.
- AV device 7 3 o MPR Of the oPCR [0] to oPCR [2], where the transmission rate and the number of oPCRs are specified by 4 Transmitted to serial bus channel # 1.
- IPCR [0] and iPC whose transmission speed and number of iPCRs are specified by iMPR of AV device 71
- the input channel # 1 is based on the transmission speed and iPCR [0], and the AV device 71 receives the isochronous data transmitted to the channel # 1 of the IEEE1394 serial bus. Read. Similarly, the AV device 72 sends out isochronous data to the channel # 2 specified by oPCR [0], and outputs the AV device 72.
- data is transmitted between devices connected by the IEEE 1394 serial bus.
- data is transmitted via the IEEE 1394 serial bus.
- the AVZC command set which is specified as a command for controlling a device, it is possible to determine the control and status of each device. Next, the AVZC command set will be described.
- FIG. Figure 11 shows the data structure of a sub-identity fire disk. As shown in Fig. 11, it is formed by a list of the hierarchical structure of the subnet identity descriptor script.
- the list represents, for example, a receivable channel in the case of a tuner, and a song recorded therein in the case of a disc.
- Lists in lower layers are called list lists, for example, list 0 is the list for the list below it.
- Other lists are also root lists.
- the object is, for example, each channel in digital broadcasting when the AV device connected to the bus is a tuner.
- all lists in one hierarchy share common information.
- Figure 12 does not show the format of the General Subunit Identifier Descriptor.
- attribute information on functions is described as contents.
- the descriptor length field does not include the value of the field itself.
- the generation ID indicates the version of the AV command set, and its value is, for example, "00h" (h represents hexadecimal).
- "00h” means that the data structure and the command are version 3.0 of the AV / C General Specification as shown in Fig. 13, for example. .
- all values except “00h” are reserved and reserved for conventional specifications.
- the list ID size indicates the number of notes of the list ID.
- the object ID size indicates the number of bytes of the object ID.
- the object position size indicates the position (the number of bytes) in the list used for reference during control.
- the number of root object lists indicates the number of root object lists.
- the root object list ID (root obj ect l ist id) is Indicates the ID used to identify the root object list at the top of the independent hierarchy.
- the data belonging to the subunit indicates the number of items in the data field (subunit pendent information) field belonging to the following subunit.
- a data field belonging to a subunit is a field indicating information specific to a function.
- the manufacturer-specific data length indicates the number of subsequent manufacture-specific data (manufacturer dependent information) records.
- the data is a field that indicates the specification information of the vendor (manufacturer) .If there is no manufacturer-specific data in the descriptor, this field is present. do not do.
- FIG. 14 shows the list ID allocation range shown in FIG. As shown in FIG. 14, “OOOOh to OFFFh” and “400OOh to FFFFh” are reserved and reserved as allocation ranges for future specifications. “100000h to 3FFFFh” and “100000h to maximum value of list ID” are provided to identify the dependent information of the functional type.
- FIGS. Figure 15 shows the stack model of the AVZC command set.
- the physical layer 81, the link layer 82, the transaction layer 83, and the serial bus management 84 conform to IEEE1394.
- FCP (Function Control Protocol) 85 conforms to IEC 61883.
- the AV / C command set 86 complies with the 1394 TA specification.
- FIG. 16 illustrates the commands and responses of FCP 85 in Figure 15
- FIG. FCP is a protocol for controlling devices (nodes) on the IEEE1394 bus. As shown in Fig. 16, the controlling side is the controller and the controlled side is the target. The transmission or response of the FCP command is performed between the nodes by using the IEEE 1394 asynchronous communication light transaction. The target that has received the data returns an acknowledge to the controller to confirm receipt.
- FIG. 17 is a diagram for explaining the relationship between the FCP command and the response shown in FIG. 16 in more detail.
- Node A and Node B are connected via IEEE1394 bus.
- Node A is the controller and Node B is the target. Command registers and response registers are prepared for each of Node A and Node B, each with 512 bytes.
- the controller transmits a command by writing a command message to the command register 93 of the target.
- the response is transmitted by writing a response message to the response register 92 of the controller with high power.
- the control information is exchanged for the above two messages.
- the type of command set sent by FCP is described in the CTS in the data field of FIG. 18 described later.
- FIG. 18 shows the data structure of a bucket transmitted in the asynchronous transfer mode of the AVZC command.
- CTS (command set ID) "0000”.
- a VZC command frame and response frame are exchanged between nodes using the above FCP. Responses to commands are to be made within 100 ms in order not to burden the bus and AV equipment.
- the destination (destination ID) indicates the destination.
- the C-type Z-response (ctype / response) field indicates the function classification of the command in the case of a no- or zero- kt force command, and the command function in the case of a bucket response. This shows the processing result.
- Commands are broadly divided into (1) commands for controlling functions externally (CONTROL), (2) commands for inquiring the status from outside (STATUS), and (3) support for control commands. (GENERALINQUIRY (with or without opcode support) and SPECIFICINQUIRY (with or without support for opcode and operands)), (4) Command to request external notification of status changes (NOTIFY) are defined.
- Responses to the (CONTROL) command include “not implemented” (NOTIMPLEDEMEDED), “accept” (ACCEPTED), “rejection” (REJECTED), and “provisional” (INTELIM). “Not implemented” for the response to the status (STAtus) command
- the subunit type is provided to specify the function in the device. For example, a tape recorder Z player (tape reccorder / player), a tuner (tuner) and the like are harmfully applied.
- this subnet type has an assignment for a BBS (Pre-Template Subunit), which is a sub-unit that discloses information to other devices.
- BBS Pre-Template Subunit
- An operation code, opcode represents a command
- an operand represents a parameter of the command.
- Fields (dditinal operands) that are added as needed are also provided. After the operand, 0 data and the like are added as needed.
- Data CRC Cyclic Redundancy Check
- Figure 19 shows a specific example of the AV / C command.
- the left side of Fig. 19 shows a specific example of a c-type Z response.
- the upper part of the figure represents the command, and the lower part of the figure represents the response.
- Fig. 19 shows a specific example of the subnet type.
- "0 0 0 0 0” is a video monitor
- "0 0 0 1 1” is a disc recorder Z player
- "0 0 1 0 0” is a tape recorder / player
- "0 0 0 1 1” Is a tuner
- "0 1 1 1 1” is a video camera
- "0 1 0 1 0” is a subunit used as a bulletin board called BBS (Bulletin Board Subunit)
- "1 1 1 "0 0” is assigned to a manufacturer-specific sub-unit type (Vender unique)
- "111” is assigned to a specific sub-unit type (Subunit type extended to next byte).
- a unit is assigned to "1 1 1 1 1”. This unit is used when data is sent to the device itself, for example, power on / off.
- FIG. 19 shows a specific example of an operation code (operation code: opcode).
- operation code operation code: opcode
- Figure 20 shows a specific example of the AVZC command and response.
- each device has its own network as described above. -Have a unique ID. Aside from this node unique ID, a node ID is set within the network. This node ID is set individually for each device with a unique node ID when there is a bus reset.
- the controller in D100 is powerful, and the process of identifying the type of other device (here, DVCR200 and MD device300) connected to bus 1 is performed by the A VZC command. This is done using the commands and descriptors specified in the code.
- the process of identifying the type of the connected device will be described with reference to the flowchart of FIG. 21 and the data configuration of FIG. 22 and thereafter.
- the controller 13 in the IRD 100 determines whether or not a bus reset process for resetting the node ID of the node 1 and the like has been performed. Judgment is made (step S11). If it is determined that the bus reset has been performed,
- step S1 2 sends the subunit info command (SUBUNIT INFO) specified by the A VZC command to each device connected via bus 1 in order (step S1 2) Details of the subunit info command As described later, this sub-command is a command that must be implemented for AV / C command compatible devices, and when there is a correct response to this command, the other device It turns out that the device is compatible with the / C command. Note that the command transmitted here does not need to be a subunit command, but may be any command that is always implemented by the AVZC command compatible device.
- Step S13 the controller 13 determines whether or not the response data specified by AV / C has been returned to the IRD 100. Do (Step S13). Here, if there is no transmission of the response data, it is determined that it is impossible to identify the corresponding device by this AV / C command (step S27).
- the controller 13 If the response data is transmitted in step S13, the controller 13 semi-IJ-cuts the subnet type indicated by the response data (step S14). For details of the subunit type that can be judged, see the Power AVZC command described later. At least, a unit (equipment) that handles disks as media, and a tape (magnetic tape) as media. ) Can be judged as a unit (equipment) of the type that handles) and other types of units (equipment).
- step S14 of controller 13 If it is determined in step S14 of controller 13 that the subunit of the communicating unit is of a type that handles a disk as media, the partner Performs the process of reading the disk drive provided by.
- the command of the open descriptor control (OPEN descriptor control), which is a command for opening the descriptor of the corresponding unit, is transmitted (step S1). Five ) .
- the controller 13 determines whether or not there is a return from the corresponding device in response to the transmission of this command (step S16). When the return is made, the controller 13 reads the opened descriptor. The command of the read descriptor control (READ descriptor control 1) is transmitted (step S17).
- the controller 13 determines whether or not there is a return from the corresponding device in response to the transmission of this command (step S18). When the return is made, the returned disk is returned.
- the contents of the data of the media type in the data of the client are determined, and it is determined whether or not the media type is MD code (step S19). If it is determined that the code is MD, the IRD100 contact —La 13 identifies the relevant device as an MD device (step S20). If there is no reply command in steps S16 and S18, and if it is determined in step S19 that the media type is not MD, discs in other formats are discarded.
- the disk device to be handled is identified (step S21).
- step S14 when the controller 13 determines in step S14 that the subunit of the unit of the communicating party is of a type that treats the tape as media. In this case, the other party inquires about the format in which the tape is played. That is, the controller 13 transmits a command of the tape playback format (TAPE PLAYBACK FORMAT) for inquiring the tape playback format on the bus 1 (step S22).
- TPE PLAYBACK FORMAT a command of the tape playback format
- the controller 13 determines whether or not there is a return from the corresponding device in response to the transmission of this command (step S23).
- an inquiry about the tape reproduction format is made. Determine if it is valid. Specifically, it is determined whether or not the response is a response other than “N0T IMPLEMENTED”, which is a command that cannot respond to the transmission of the status command in step S22 (step S24).
- the corresponding unit is identified as a D-VHS standard DVCR (step S25). Then, if the reply command is absent in step S23 and if it is determined in step S24 that the response is a [N0T IMPLEMENTED] response, the tape device is identified as a tape device that handles tapes in other formats. (Step S26).
- step S14 when it is determined in step S14 that the subunit type is other than a disk and a tape, The device is identified as another type of device (step S28).
- the IRD 100 executes the above processing for each device connected to the bus 1 in order, and identifies the types of all the devices connected to the bus 1.
- the subunit information status command in the AVZC command is defined by the format shown in Fig.22. Here, 8 bits are shown as one unit (horizontal row in the figure) (the same applies to the format figures after Figure 23).
- the subunit response in the AV / C command is defined by the format shown in Fig. 23. Opcodes shown in Figs. 22 and 23
- the data of the operand is placed in the opcode and operand fields in the FCP frame in the packet shown in Fig. 18.
- the subnet info data is placed as an opcode, and the page and extension code are placed in the area of the operand [0].
- Data is placed, and a specific value (here, FF) is placed in the error after operand [1].
- page data is placed in the area after operand [1].
- the area of the response opcode and operand [0] ⁇ is the same as the command.
- the type of the device is determined by inquiring about the type of the unit.
- the unit info status command for inquiring the unit type is defined by the format shown in Fig. 24, and the unit information response as the response is the format shown in Fig. 25. It is defined by a tree.
- the unit info status command shown in Fig. 24 the unit information is stored as an operation code, and the operand A specific value (here, FF) is placed in the area after [0].
- the unit type and the data of the unit are arranged in the area of the operand [1].
- a Campaign ID which is a code assigned to each company that manufactures each device (unit), is placed.
- Figure 26 shows some of the codes related to the subsystem type specified by the A V Z C command.
- Fig. 26 shows a part of the subnet type shown in Fig. 19 again.
- video monitors, disc recorders and Z or players, tape recorders and Z or players, tuners, video cameras, etc. are specified as the subunit types.
- what is defined as a vendor type is a special type of submit type specified for each company.
- the command to open the descriptor (open descriptor command) is AV /
- the C command is specified in the format shown in Fig. 27.
- data indicating an open descriptor is arranged as an operation code, and data for discriminator identification and data of a subfunction are arranged as an operand.
- the command to read the descriptor is the AV / C command, as shown in Figure 28. It is regulated by the Matsu.
- This read descriptor command The data is arranged as an opcode in a data format indicating a lead descriptor, and the operands are data for discriminator identification, read status data, and data. The length and the data of the address to be read are arranged.
- FIG. 29 is a diagram showing a configuration example of a disk drive of an AV / C command disk type subunit read by such a command.
- the descriptor has a hierarchical structure of data.
- Figure 29 shows an example of a disk identity identifier descriptor.
- the descriptor length, the energy generation ID, the size of the list ID, the size of the object ID, and the object ID Size, size of object position, number of root object list, note object list ID, data length of disc specific data, disc specific information of disc type The location of the data, the length of the data unique to the manufacturer and the manufacturer, and the information specific to the manufacturer.
- the root object list ID the number indicated by the data of the number of the current object list is arranged.
- Disc Subunit Identity Discrimination dependent information is a key feature of disc subunits that are included in the disc discrimination, and are part of the disc subunit dependent information format.
- the structure of the evening is shown in Figure 30.
- the address offset here is the offset value of the address from the operand where the first part of the disk subunit dependent information is placed.
- This information includes the information fields specific to the disc submission, the length of the information fields, the attributes, and the version of the disc description.
- the number of supported media types is the number indicated by the data of the number of supported media types.
- the data of this saboted media type gives details about the format of the media. In the case of this example, this data indicates that the disc device uses a disc in the MD format as a medium.
- the tape playback format (TAPE PLAYBACK FORMAT) is used to query the tape playback format.
- Figure 32 shows the format of the response to this status command.
- the media type and format parameter data are placed in the operand area.
- the response at this time is indicated by one of the response types already shown in FIG.
- the response to the status command of the AVZC command is: [N0T IMPLEMENTED], rejection [REJECTED], transitioning [INTT]
- the D-VHS format DVCR is used. It turns out there is.
- the status of the tape play format can be obtained with the AVZC command. Since the command is not implemented, the response cannot be answered [N0T IMPLEMENTED].
- the network is connected to the network. Without knowing in advance what protocol the connected device supports, it is possible to know the details of the device type and media format, etc. without knowing in advance the network.
- a function that can be executed only for a device of a specific connected media format can be executed without the user having to perform an operation of setting a device type and the like.
- a sub-unit information command is first used to check whether or not the device is compatible with the AV / C command. Inquired about the subnet type, but the protocol and command set used by the device connected to the network may be checked in another process.
- configuration ROM configuration ROM
- a node unit
- the data related to the unit attribute of the configuration ROM specified in IEEE 122 is shown in FIG.
- the data structure of the format shown in Fig. 33 is shown in Fig. 34 by combining the data of the unit ID [unit spec id] and the data of the unit SW version [unit sw vesion].
- the corresponding protocol and command set are determined. Specifically, for example, the AVZC command standard standardized by 139 TA, the common application language (CAL) standard standardized by 139 TA, and the 4 From these data, it is possible to determine which protocol and command set, the standard of the E-mail Home System (EHS) standardized by TA and the standard of ANSI, are used. I have. If the correspondence between the unit ID data and the unit SW version data indicates that the unit is compatible with the AVZC command, the unit details may be queried. .
- EHS E-mail Home System
- step S12 in the flowchart of FIG. 21, that is, the status command of the subunit is executed.
- the process after sending may be performed.
- the code value of the CTS command is determined, and based on the code value of the CTS command, whether the connected device supports the AVZC command is determined. May be determined.
- the code value of this CTS command is placed in the first 4-bit section (the part shown as "0000") of the FCP frame shown in Fig. 18. In this case, when the code value of the CTS command is "0000", it is understood that the command corresponds to the AVZC command.
- the configuration ROM data specified by IEEE 1212 has a powerful key ID (key ID).
- Model ID data in this The details such as the type of the device may be directly determined by reading the information.
- the present invention is not limited to the above-described example as long as the data structure can be applied to the judgment and the network configuration can be similarly processed.
Landscapes
- Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Multimedia (AREA)
- Computer Networks & Wireless Communication (AREA)
- Computer And Data Communications (AREA)
- Small-Scale Networks (AREA)
- Signal Processing For Digital Recording And Reproducing (AREA)
Description
Claims
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
AU43187/00A AU4318700A (en) | 1999-05-11 | 2000-05-08 | Network connection recognition method, network system and network connection terminal device |
KR1020017000388A KR20010071821A (ko) | 1999-05-11 | 2000-05-08 | 네트워크접속인식방법, 네트워크시스템 및네트워크접속단말장치 |
EP00922986A EP1098475A4 (en) | 1999-05-11 | 2000-05-08 | NETWORK CONNECTION RECOGNITION METHOD, NETWORK SYSTEM AND NETWORK CONNECTION TERMINAL |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP11/130326 | 1999-05-11 | ||
JP13032699 | 1999-05-11 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2000069122A1 true WO2000069122A1 (fr) | 2000-11-16 |
Family
ID=15031686
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2000/002934 WO2000069122A1 (fr) | 1999-05-11 | 2000-05-08 | Procede de reconnaissance a la connexion reseau, systeme de reseau et terminal a connexion reseau |
Country Status (4)
Country | Link |
---|---|
EP (1) | EP1098475A4 (ja) |
KR (1) | KR20010071821A (ja) |
AU (1) | AU4318700A (ja) |
WO (1) | WO2000069122A1 (ja) |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR100434270B1 (ko) | 2001-05-30 | 2004-06-04 | 엘지전자 주식회사 | 가전기기 네트워크 제어시스템 |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH10124454A (ja) * | 1996-10-22 | 1998-05-15 | Sony Corp | 電子機器及びその内部の信号接続制御方法 |
CN1211127A (zh) * | 1997-07-03 | 1999-03-17 | 索尼公司 | 电子设备及其协议切换方法 |
Family Cites Families (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5883621A (en) * | 1996-06-21 | 1999-03-16 | Sony Corporation | Device control with topology map in a digital network |
JP4054451B2 (ja) * | 1997-08-26 | 2008-02-27 | キヤノン株式会社 | 通信装置 |
-
2000
- 2000-05-08 AU AU43187/00A patent/AU4318700A/en not_active Abandoned
- 2000-05-08 KR KR1020017000388A patent/KR20010071821A/ko not_active Application Discontinuation
- 2000-05-08 EP EP00922986A patent/EP1098475A4/en not_active Withdrawn
- 2000-05-08 WO PCT/JP2000/002934 patent/WO2000069122A1/ja not_active Application Discontinuation
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH10124454A (ja) * | 1996-10-22 | 1998-05-15 | Sony Corp | 電子機器及びその内部の信号接続制御方法 |
CN1211127A (zh) * | 1997-07-03 | 1999-03-17 | 索尼公司 | 电子设备及其协议切换方法 |
Non-Patent Citations (1)
Title |
---|
See also references of EP1098475A4 * |
Also Published As
Publication number | Publication date |
---|---|
KR20010071821A (ko) | 2001-07-31 |
AU4318700A (en) | 2000-11-21 |
EP1098475A4 (en) | 2002-08-07 |
EP1098475A1 (en) | 2001-05-09 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
KR100649340B1 (ko) | 통신 방법, 통신 장치, 통신 시스템 및 제공 매체 | |
US7130523B2 (en) | Information processing method, information processing system and information processing apparatus | |
US20020046311A1 (en) | Communications controlling method, communications system, and communications device | |
KR100715881B1 (ko) | 전자 장치 및 그 보수 방법 | |
EP1098476A1 (en) | Network connection recognizing method and network-connected terminal device | |
AU773294B2 (en) | Method of controlling device, transmission device, and medium | |
WO2000069122A1 (fr) | Procede de reconnaissance a la connexion reseau, systeme de reseau et terminal a connexion reseau | |
US20020041602A1 (en) | Communication control method, communication system, and communication apparatus | |
WO2000072519A1 (fr) | Procede, dispositif et systeme de communications | |
JP2002281038A (ja) | データ伝送方法およびデータ伝送装置 | |
JP2002051056A (ja) | 通信制御方法、通信システム及び通信装置 | |
WO2000072551A1 (fr) | Procede de communication, systeme de communication et dispositif electronique | |
JP2002051054A (ja) | 通信制御方法、通信システム及び通信装置 | |
JP2001024654A (ja) | 通信方法及び通信装置並びに提供媒体 | |
MXPA01000270A (en) | Network connection recognizing method and network-connected terminal device |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): AE AL AM AT AU AZ BA BB BG BR BY CA CH CN CR CU CZ DE DK DM EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG US UZ VN YU ZA ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): GH GM KE LS MW SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG |
|
ENP | Entry into the national phase |
Ref country code: JP Ref document number: 2000 617603 Kind code of ref document: A Format of ref document f/p: F |
|
WWE | Wipo information: entry into national phase |
Ref document number: 1020017000388 Country of ref document: KR |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
WWE | Wipo information: entry into national phase |
Ref document number: 2000922986 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 09743489 Country of ref document: US |
|
WWP | Wipo information: published in national office |
Ref document number: 2000922986 Country of ref document: EP |
|
WWP | Wipo information: published in national office |
Ref document number: 1020017000388 Country of ref document: KR |
|
REG | Reference to national code |
Ref country code: DE Ref legal event code: 8642 |
|
WWW | Wipo information: withdrawn in national office |
Ref document number: 2000922986 Country of ref document: EP |
|
WWW | Wipo information: withdrawn in national office |
Ref document number: 1020017000388 Country of ref document: KR |