JP5421041B2 - Remote device connection establishment method and connection establishment device - Google Patents

Description

  The present invention relates to a remote apparatus connection establishment method and connection establishment apparatus, and more particularly to a remote apparatus connection establishment method and connection establishment apparatus using a hypertext transfer protocol.

  A method of controlling a remote device using the Internet (HTTP) (hyper text transfer protocol: hereinafter referred to as HTTP) is known. An Internet site controls how to control an audio-video device (AV device) such as an audio tuner or a television receiver that broadcasts various information that can be selected by switching to another channel via the Internet. Demonstration. An example of such a system is shown in FIG. Here, a system for controlling radio broadcasting by HTTP is shown.

  The radio transmitter 30 as a source device is a target device (here, a server 31) having a universal resource locator (hereinafter referred to as URL) such as http // www.chilton.com.sctipts / radio / R8-receiver. ) To supply analog signals for providing a plurality of services. The server 31 includes a microcontroller and an HTTP server 33. For this reason, one of various service contents available from the radio transmitter 30 via the Internet is selected and output to the Internet. Can do. In this example, HTTP is used as a transfer protocol.

  The microcontroller and HTTP server 33 has a graphical user interface for all Internet users who have selected the URL of the server 31. On the Internet user side, in order to perform asynchronous connection to the server 31, it is necessary to include a controller 32 that can display a web browser, for example. This asynchronous point-to-point connection is made for audio data and HTTP control protocol.

  It is also known that connection is made between two remote devices such as two HTTP servers on the Internet. An example of such a connection is shown in FIG. An Internet user connects to a target device 35 that is an HTTP server 33 having a search engine function. The connection to the target device 35 is an asynchronous connection for controlling the target device 35 and capturing data from the target device 35 to the controller 32 which is an Internet user, for example, a web browser. Further, the HTTP server 33, that is, the target device 35 may not be able to supply desired data by itself. In this case, the target device 35 performs a second asynchronous connection to another HTTP server 34 that functions as a search engine. In this way, the connection between two remote servers, such as the HTTP server 34 and the HTTP server 33 (target device 35), is not controlled by the Internet user, but is controlled by the target device 35 itself selected by the Internet user. Has been. In the example shown in FIG. 11, the Internet user uses the controller 32 functioning as a web browser to connect to Yahoo of the target device 35 having the URL “www.Yahoo.com”, and the Yahoo, which is the target device 35. Connects to Altavista, the source server, with the URL "www.Altavista.digital.com".

  In any of the examples shown in FIGS. 10 and 11, audio data and search data, as well as control data, are not subjected to bandwidth guarantee. A conventional transmission control protocol / Internet protocol (hereinafter referred to as TCP / IP). It is transmitted by connection. For this reason, for example, after the target device 35 is controlled using HTTP, further desired information is also transmitted to the web browser of the user using HTTP, that is, the controller 32 via the Internet. That is, long latency often occurs because the bandwidth of the HTTP connection is not guaranteed.

  On the other hand, in a network environment, interoperability between an audio / video source device and a target device is required. For example, a device having a guaranteed bandwidth and a communication mechanism defined by IEEE 1394 is used. It is also known that communication is possible. An example of such a network environment is shown in FIG. IEEE 1394 defines an isochronous channel that guarantees a communication bandwidth between a connected source device and a target device. In addition, there are asynchronous channels that provide point-to-point connections for system-specific control protocols. Here, for example, a digital VTR (video tape recorder: hereinafter referred to as VTR), a digital video broadcast (hereinafter referred to as DVD) tuner, a digital audio broadcast (hereinafter referred to as DAB) tuner, and the like. Various system-specific protocols have been defined so that various types of corresponding devices can be controlled.

  The remote device 21A shown in FIG. 9 functions as a tuner device, and the remote device 21B functions as a storage device. Both the remote device 21A and the remote device 21B have a logical interface 24 connected to an isochronous channel of the IEEE 1394 network. Each of the remote device 21A and the remote device 21B includes a microprocessor 29 that controls these devices. Still further, both remote device 21A and remote device 21B have a logical interface connected to controller 22 through an asynchronous channel of the IEEE 1394 network. The multi-function controller 22 that controls the remote device 21A and the remote device 21B needs to correspond to all system-specific protocols, and therefore has a relatively complicated structure. Furthermore, the different types of remote devices 21A and 21B each require a system-specific control protocol that is transmitted over the asynchronous channel, so when adding another type of device, the corresponding controller 22 is typically used. Must be upgraded.

Japanese translation of PCT publication No. 2002-510415

  As described above, various remote devices connected to the IEEE 1394 network system each require a unique control protocol. The controller 22 needs to support all control protocols, and therefore it is not easy to design the controller 22 so that all devices can be controlled on the user side. Further, since a so-called system-dedicated controller assuming one type of system is used, it is difficult for one controller to control all systems.

  In addition, since system-specific protocols are defined for the purpose of controlling the lower level functions of the device, such protocols are relatively inflexible. Therefore, when upgrading the remote device 21A and remote device 21B on the IEEE 1394 network, the existing protocol must be expanded, and the controller 22 related to the remote device 21A and remote device 21B must be upgraded. I must.

  Further, when a new remote device is added to the IEEE 1394 network, there is a restriction that the controller 22 needs to support a new system-specific protocol or a new remote device needs to support an existing protocol. Since the system-specific protocol is inflexible as described above, depending on the design of the controller 22, the functions and operability of the remote device may not be fully exhibited. For this reason, some manufacturers are reluctant to respond to the IEEE 1394 network, thus increasing the number of incompatible network protocols and creating problems with interoperability between devices connected to the network. There is also.

  The problems as described above can be solved by device control using HTTP currently performed on the Internet. However, in that case, the connection established between the two remote devices cannot be directly controlled, and the desired data, such as audio data or video data, can be transmitted via a connection that does not guarantee sufficient bandwidth. Therefore, when the network is congested, the data flow becomes discontinuous and audio / video playback tends to be interrupted.

  The present invention has been made in view of the above-described problems, and an object of the present invention is to provide a connection establishment method and a connection establishment device for easily establishing a connection between remote devices connected to a network and remotely controlled. And

  In order to solve the above-described problem, a connection establishment method for establishing a connection between a plurality of remote devices by the control device according to the present invention is a predetermined method assigned to each of the plurality of remote devices by the control device. And controlling each connected remote device using a hypertext transfer protocol based on the Universal Resource Locator. The predetermined universal resource locator is configured with prefix identification information identifying the remote device. Here, the remote device is controlled by a controller, and the controller controls the remote device using a hypertext transfer protocol. In addition, the controller is controlled remotely using a hypertext transfer protocol or via a user interface provided in the controller. Furthermore, bandwidth is preferably guaranteed for connections between remote devices.

  In the present invention, instead of a plurality of system specific protocols, a hypertext transfer protocol, ie HTTP, is used to establish a connection between a plurality of remote devices. Each remote device can act like an Internet server and provide menu choices that correspond to specific control functions. Since the controller only needs to support the hypertext transfer protocol, the controller design becomes very simple. When adding a remote device to the network, there is no need to add a new control protocol to the controller. To perform a network upgrade, the user can control the remote device by downloading a user interface from each remote device controlled by the controller into the controller and displaying the downloaded interface.

  A connection establishment device for establishing a connection between a plurality of remote devices according to the present invention is based on a predetermined universal resource locator assigned to each of the plurality of remote devices. Remote control means for controlling using a hypertext transfer protocol. The predetermined universal resource locator is configured with prefix identification information identifying the remote device. The control interface stores a user interface, which is preferably a graphical user interface. The remote device according to the present invention effectively functions as an HTTP server by such a user interface. In this case, when the user accesses the remote device via the controller, the user interface stored in the control interface is downloaded from the remote device to the controller. Thus, the user can access all the functions of the remote device through the control device operated by himself / herself.

  As described above, according to the connection establishment method and the connection establishment device according to the present invention, in communication between a plurality of remote devices, a hypertext transfer protocol, that is, a remote device using HTTP instead of a plurality of system-specific protocols. Establish a connection between.

It is a figure which shows the structure of the IEEE1394 network to which this invention is applied. It is a figure explaining allocation of the IP address of each apparatus of FIG. It is a figure which shows the initialization process of the DNS server of a home network. It is a figure explaining the external request by a DNS server. It is a figure explaining HTTP server initialization. It is a flowchart which shows the process of the network device based on a user command. It is a figure which shows the logical connection state of the extended network. It is a figure which shows the physical connection state of the network environment to which this invention is applied. It is a figure which shows the conventional IEEE1394 network structure. It is a figure explaining the conventional method of controlling radio broadcasting using the internet. It is a figure explaining the conventional type | formula automatic connection established between two remote devices on the internet.

  Hereinafter, a remote device connection establishment method and a connection establishment device according to the present invention will be described in detail with reference to the drawings.

  FIG. 1 is a diagram showing a configuration of an IEEE 1394 network to which the present invention is applied. The remote device 1A, the remote device 1B, and the remote device 1C shown in FIG. 1 (hereinafter collectively referred to as the remote device 1 unless otherwise described) communicate audio / video data with a guaranteed bandwidth. In addition, it is connected to an isochronous connection line 5 via a data interface 4 included in each remote device itself. Such isochronous connection can be realized using an IEEE bus system. Further, an asynchronous connection may be performed instead of a connection with a guaranteed bandwidth. Each of the remote devices 1A, 1B, and 1C has a control interface, that is, a hypertext transfer protocol server 3 (hereinafter also referred to as an HTTP server 3), and establishes an asynchronous connection with the controller 2 through them. To do.

  The hypertext transfer protocol server 3 has at least a microcontroller and a memory. Such an asynchronous connection is a point-to-point connection for a device control protocol. In the IEEE 1394 network shown in FIG. 1, a hypertext transfer protocol, that is, HTTP is used as a device control protocol. An HTTP server 3 having a microcontroller and a memory in each remote device 1A, 1B, 1C controls the remote devices 1A, 1B, 1C, for example, the respective logical interfaces 4 of the remote devices 1A, 1B, 1C and the like. Functions as a gateway to control the process.

  In this embodiment, the remote device 1A functions as a tuner device for selecting one of a plurality of broadcast services being broadcast simultaneously, and the remote device 1B is a data based on a signal such as a broadcast service. It functions as a storage device that records or stores data. The remote device 1C functions as a display device that displays a broadcast service or the like.

  The remote device 1A has a switch 6 that selects one of a plurality of input signals. The HTTP server 3 of the remote device 1A controls the processing in the remote device 1A and the data interface 4 of the remote device 1A based on a predetermined algorithm, and the switch 6 controls the controller 2 and the HTTP server 3 of the remote device 1A. To be controlled by the user. Further, in the remote device 1B, the recording medium 7 itself and the processing in the remote device 1B are controlled based on a predetermined algorithm, and recording or reproduction of data on a certain connected isochronous connection line 5 is started. The selection of termination is performed by the user via the controller 2 and the HTTP server 3 of the remote device 1B.

  In the example shown in FIG. 1, the remote device 1 </ b> C is also connected to the isochronous connection line 5 and the controller 2. The remote device 1C is connected to the controller 2 by an asynchronous connection. The remote device 1C is controlled by the same controller 2 by the same protocol as the remote device 1B, that is, HTTP, but the data of the selected isochronous connection is displayed without being recorded. As shown by a broken line in FIG. 1, the remote device 1C as such a display device does not necessarily need to be asynchronously connected, and does not necessarily need to be controlled using HTTP.

  The controller 2 can be accessed by the user in order to control the remote devices 1A, 1B, 1C connected thereto. The isochronous channel used by the remote devices 1A, 1B, 1C for data broadcasting over a bandwidth-guaranteed connection is chosen by the system itself, regardless of the capacity at that time, and is therefore subject to such choice. Instead, the user can fully control each of the remote devices 1A, 1B, 1C.

  In the embodiment shown in FIG. 1, the user controls the switch 6 to select any one of a plurality of broadcast services input to the remote device 1 </ b> A and supply it to the isochronous connection line 5. The remote device 1B is controlled by the user to select one of the connected isochronous connection lines 5, and the data supplied to the selected isochronous connection line 5 is processed to obtain a recording medium 7 To be recorded.

  In this embodiment, the remote devices 1A, 1B, 1C are independently controlled using the same protocol, ie, a hypertext transfer protocol such as HTTP, so that the remote devices 1A, 1A, There is no need for a controller 2 specially adapted to all of 1B, 1C or a different controller 2 for each remote device 1A, 1B, 1C. The controller 2 may be a relatively inexpensive device that supports only asynchronous connection. By using HTTP without using a control protocol specially designed for each remote device 1, the controller 2 can efficiently function as a web browser. In order to be able to use an existing web browser, the same protocols as those currently used on the Internet, that is, TCP / IP and HTTP may be used.

  In FIG. 1, asynchronous and isochronous connections are shown separately, but in an actual system, both types of connections are supported by the same cable, as in the IEEE 1394 system. IEEE 1394 defines a method for supporting the Internet protocol (internet protocol: hereinafter referred to as IP) of the uppermost layer of IEEE 1394 connection. Thereby, TCP connection and HTTP connection can also be supported. In addition, a domain system such as a domain name system (hereinafter referred to as DNS) can be used to assign a domain name to a remote device, and for automatic assignment of an IP address, netmask, or DNS name server. Other protocols may be introduced to improve the plug and play operation. In this case, a dynamic host configuration protocol (hereinafter referred to as DHCP) or a protocol similar to the DHCP protocol is used.

  FIG. 2 is a diagram illustrating the assignment of IP addresses to remote devices 1A, 1B, 1C and controller 2 (interfaces 2a, 2b) in accordance with the principles of the present invention.

  The IEEE 1394 bus system is currently used to connect consumer audio / video equipment. However, in the present invention, such a remote device is connected to an Internet server for software upgrade, for example, and the user controls the service according to the conventional IEEE1394 using the controller 2. At the same time of viewing, the same controller 2 is used to select and access Internet services, and for example, because a traveling user needs to access his home network device via the Internet. For the purpose of connection, the IEEE 1394 bus system can be used.

  A network initialization process for realizing such various purposes will be described. In a specific example described below, as shown in FIG. 8, the controller 2 is a personal computer or a similar device that functions as a gateway to the Internet. Connection to the Internet can be supported by a telephone modem or cable modem, for example, as is well known. Hereinafter, a conventional boot process procedure after network initialization will be described with reference to FIG.

  FIG. 9 shows the IEEE 1394 network being initialized. For example, two remote devices such as a remote device 21A functioning as a tuner device and a remote device 21B functioning as a storage device are connected to an isochronous connection line 25 of an IEEE 1394 network via respective logical interfaces 24. Further, these remote devices 21A and 21B are connected to the controller 22 via a logical interface 24 and an asynchronous connection of an IEEE 1394 network. Further, since the sets of control commands of the respective types of remote devices 21A and 21B are different, it is necessary to adapt the controller 22 to the remote devices 21A and 21B. The controller 22 can access a remote display input device 28, or the display input device 28 may be incorporated within the controller 22.

  The initialization of the conventional IEEE 1394 network is performed after the power is turned on or after re-initialization. Here, all devices connected to the network are booted to an optimum state. Here, in order to complete booting, for example, processing for identifying a master device such as an isochronous resource manager, and processing for setting up an IEEE1394 asynchronous connection by assigning node_ids are executed. This procedure is described in the IEEE 1394 specification. After establishing this transport layer, devices connected to the network connect to other devices to send and receive data, collect information about their functions, or investigate network connection status . Such information is stored as data in each remote device and supports basic communication. Furthermore, information for notifying the user of the function of each device at a later stage is also stored.

  According to the present invention, in the first stage of the boot procedure, conventional network initialization as described above for IEEE 1394 is performed. After such an IEEE 1394 transport layer is established, initialization of the Internet protocol (hereinafter referred to as IP) network is started. In order to fully support plug and play, it is necessary to automatically assign parameters such as an IP address and an IP netmask.

  In addition, it is necessary to know a default IP address in a device that must access a remote Internet site via a router. If it is necessary to automatically assign such parameters in addition to the basic IP family, a protocol such as DHCP is used. In a simple IEEE 1394 network, if there is something like a standardized IP address assignment rule, there is no need to use a protocol such as DHCP.

  The IP address is configured by a unique ID that is not duplicated in the world according to IEEE 1394, that is, unique. Therefore, the IP address guarantees a unique ID even in the local area. Also, in order to allow a fixed name server and default router to enter each of the IP devices, the name server and default router adopt a standardized IP address. A device having a plurality of roles can assign a plurality of IP addresses to the interface as needed.

In the example shown in FIG. 2, the remote device 1A that functions as a tuner device assigns the following addresses to the HTTP server 3 provided in the remote device 1A.
Default router: 192.168.0.1
DNS server: 192.168.0.1
Netmask: 255.255.255.0
IP address: 192.168.0.2
On the other hand, the remote device 1B functioning as a storage device assigns the following addresses to the HTTP server 3 provided in the remote device 1B.
Default router: 192.168.0.1
DNS server: 192.168.0.1
Netmask: 255.255.255.0
IP address: 192.168.0.3
The controller 2 that also serves as a gateway to the Internet and accesses the display input device 8 includes two interfaces 2a and 2b. The address of the internal interface 2a for the DNS server and the home network DHCP server is as follows.

IP address: 192.168.0.1
Netmask: 255.255.255.0
DNS server: 192.168.0.1
On the other hand, the address of the external interface 2b that communicates with the Internet is as follows.

IP address: 192.109.206.33
Netmask: 255.255.255.0
Default router: 192.109.206.1
To simplify the system, these addresses may be fixed addresses based on future standards, but they can also be assigned during IP network initialization, for example by DHCP.

  A lower layer externally connected to the Internet, such as a point-to-point protocol (hereinafter referred to as PPP) or a telephone line, is necessary to support IP traffic. Since this part of network initialization has already been standardized, a description thereof is omitted here.

  When using the DHCP protocol, the initialization of the network is determined by the condition of which device functions as a DHCP server. If only an IP stack is required to support HTTP control by the web browser, an IP stack is required if at least one HTTP server and at least one HTTP client are connected to the network. In a home network, the total number of source and target remote devices is typically greater than the total number of controllers.

  If the network comprises one controller 2 acting as an HTTP client and several source and target remote devices acting as HTTP servers, ie remote devices 1A, 1B, the controller 2 HTTP session with 1A, 1B. Therefore, in this embodiment, a DHCP server is provided in the controller 2 in order to limit the dependence on other remote devices.

  For example, when a new control software is downloaded from the Internet to a device other than the controller 2, that is, to the remote devices 1A and 1B, and when the controller 2 is not a gateway to the Internet, the device other than the controller 2 is preferably used. A DHCP server is provided.

  In a home network, proper routing and address values are needed to support IP traffic over the Internet. Considering that there are a large number of home networks and a larger number of devices included in them, the Internet addresses that can be registered are limited, so that they cannot be used in the home network. Therefore, for this purpose, a special “private” address (eg 192.168.0.0 to 192.168.255.255) assigned by the Internet engineering task force (hereinafter referred to as IETF) must be used. Since these addresses do not exist on the Internet, they can be used and reused in a private network.

  In FIG. 2, the DHCP server uses an address within this range, for example, 192.168.0.0. In addition to assigning a unique address locally, the DHCP server assigns a 3-byte netmask, the default router IP address, ie 192.168.0.1, and the name server, ie 192.168.0.1, on the home network. Assigned to each remote device, that is, the remote devices 1A and 1B.

  The controller 2 requires a special IP configuration in order to function as a gateway to the Internet. The controller 2 has a further IP interface with an address registered in the Internet, ie an external interface 2b, so that the controller 2 can communicate with an external Internet site.

  In the embodiment shown in FIG. 2, the IP address is 192.109.206.33. For this purpose, the controller 2 needs a different default router address representing a router on the Internet. The value of such a parameter depends on the ISP (Internet Service Provider) gateway used. At the same time that the DHCP server of the home network assigns such parameters to the remote devices 1A, 1B on the home network, the ISP also uses the DHCP server to assign appropriate IP parameters to the external interface 2b of the home network. Can do.

  In FIG. 2, the ISP DHCP server assigns an address 192.109.206.33 to the external interface 2 b of the controller 2. Further, the ISP instructs the gateway of the home network to use 192.109.206.1 as its default router.

  After IP configuration, the home network gateway converts any internal IP address to an external IP address to send IP packets to the outside, and vice versa to receive IP packets from the outside. I do.

  Instead of identifying the remote devices 1A, 1B and the controller 2 only by address, a name indicating the remote devices 1A, 1B or the controller 2 can be used. In the Internet, there are four reasons why address assignment by name is desirable in addition to address assignment using an IP address.

  First of all, in order to improve the convenience for the user, each device should have an appropriate name associated with it.

  Secondly, the assignment of IP addresses is dynamic, so it should not be known on the web browser.

  Even if such an IP address is fixed, if the portable controller attaches a bookmark to such an IP address, the Internet does not support such a private address. Controller cannot use the bookmark from the external network. In other words, the IP address of the local home network is valid only within this local home network environment. The portable controller in this case is a portable terminal device that can move from a home network to a remote Internet connection. In order to support the IP address of the local home network, the mobile terminal device must know the external IP address of the home network. Further, since this external IP address is dynamically assigned by the Internet service provider, it is difficult to use it as a bookmark. The above is the third reason.

  Fourth, in a system including a plurality of devices providing the same type of service, it may be preferable to use the same type of server name rather than mapping this name to a different IP address. That is why. The advantage of this method is that the burden caused by the concentration of a plurality of clients can be distributed to a plurality of servers.

  In order to cope with these situations, the home network uses a DNS, that is, a domain name system. In this domain name system, a name server that converts a name into an appropriate IP address is used. When the domain name system tries to access a device by its name, it must first contact its name server. The name server returns an appropriate IP address and uses it to enable subsequent communication.

  A home network using DNS according to the present invention is shown in FIG. In the configuration example shown in FIG. 3, the controller 2 also functions as a DNS server, and each of the microprocessors of the HTTP servers 3 of the remote devices 1A, 1B has a further entry, ie a tuner device, such as an IEEE 1394 device description name. , A device description name indicating the type of device such as a storage device or a controller.

  In addition to the address of the controller 2 shown in FIG. 2, the controller 2 shown in FIG. 3 further has a DNS server corresponding to the domain no29.bahnstrasse.bonn.de and the following DNS database.

Subdomain Response to internal device Response to external device Tuner 192.168.0.2 192.109.206.33
Storage 192.160.0.3 192.109.206.33
Controller 192.160.0.1 192.109.206.33
Here, the further device also has an entry with its name assigned to two addresses.

  When a device in the Internet needs to access a remote home network, the device needs to communicate with the Internet service provider to which the remote home network is connected. As shown in FIG. 3, if this home network is located in Bonn, for example, the Internet service provider assigns a name associated with the location of the home network, such as “no29.bahnstrasse.bonn.de”.

  Using the domain name (no29 ...) given by the Internet service provider, the DNS server of the home network in the controller 2 assigns a unique name to the remote device in the home network, that is, the remote devices 1A and 1B. These names are fully qualified domain names. If the device name is already defined in the IEEE 1394 specification, the DNS server of the home network uses such a device name defined by the IEEE 1394 standard and prefixes the name to the domain name of the home network. Can do. For example, if a device is called with the name “storage” in the IEEE 1394 network, the DNS server will indicate this as a subdomain identifier representing each device, for example “storage.no29.bahnstrasse.bonn.de”. Can be used as The predetermined domain name may be automatically assigned in this way, or may be arbitrarily assigned by an operator of the home network.

  Using these data, namely the device description name defined by the IEEE 1394 network, the IP address assigned by the DHCP server of the home network, and the IP address of the external interface of the gateway assigned by the Internet service provider, the controller The DNS server of the home network in 2 constructs a database as shown in FIG. During such an initialization procedure, the controller 2 displays a message “Please wait for a while” on the display input device 8 connected to or incorporated in the controller 2.

  The DNS server must prepare two usable addresses for each device connected to the home network. If the internal device requires name translation, the entry shown in the second column, ie the private IP address, is used. Since a private address cannot be used on the Internet, the value in the third column, that is, the Internet IP address is used when responding to a request from an external device. Internet service providers can also handle all name conversion requests for no29.bahnstrasse.bonn.de from external devices. In any case, as shown in FIG. 4, the external device can only reach the controller 2 that is the gateway of the home network, and reaches the remote devices in the home network, that is, the remote devices 1A and 1B. I can't do it.

  FIG. 4 shows the system shown in FIG. 3 and the procedure of the internet device for accessing the remote device 1B functioning as a storage device of the home network. In order to specify storage.no29.bahnstrasse.bonn.de, the Internet device first transmits a query “Who is storage.no29.bahnstrasse.bonn.de?” To the DNS server of the home network. Next, “192.109.206.33” is returned as a response from the DNS server. This is the IP address of the external interface of the controller 2. That is, the device requesting the IP address “storage.no29.bahnstrasse.bonn.de” is not supplied with the IP address of the remote device 1B functioning as a storage device, but only the IP address of the external interface of the controller 2 is provided. Supplied.

  In this embodiment, a warning that someone is accessing the home network from the Internet is displayed on the display input device 8. In addition, authentication / authorization processing is performed during session setup as necessary. As described above, a user who transmits a request via the Internet can access the remote device 1B functioning as a storage device via the controller 2, but cannot directly access the remote device 1B.

  As a countermeasure against this problem, in the present invention, a new unified resource that supports HTTP access from the Internet to a remote device in the home network, that is, the remote devices 1A and 1B, via the gateway of the home network, that is, the controller 2. Specifies an identifier (URI).

  In order to access the ISP subdomain of the remote device from the Internet site, a complete domain name is required. However, it is difficult to use such a long domain name for each device in a home network environment. In order to solve this problem, in this IP network, it is assumed that the client device in the home network is the default domain. In the above example, a suitable default domain name is “no29.bahnstrasse.bonn.de”.

  By mapping one name to a plurality of IP addresses, resources can be managed using DNS. When a home network has a wide variety of devices that can support one user or a task, the home network can have some of such devices. In this embodiment, the intelligent name server can map the generic name of the device, such as “dvbtuner.no29.bonn.de”, to the IP address of the desired device. When assigning an address to a specific device, a unique name may be assigned.

  Hereinafter, control of the remote devices of the home network shown in FIGS. 1 to 4, that is, the remote devices 1A and 1B will be described with reference to FIGS.

  A general HTTP application server is assigned a universal resource locator (URL) including a server name, that is, a predetermined domain name, followed by a path indicating an HTML document on the server. In this method, the URL of the main menu such as the DVB tuner is “http://dvbtuner.no29.bahnstrasse.bonn.de/index.html”. Using this URL, the browser inside the home network first refers to the IP address “dvbtuner.no29.bahnstrasse”. Then, the DNS server responds using the internal IP address, and as a result, the browser transmits an HTTP get command “GET / index.html” to this IP address. Internet browsers also reference this domain, but as described above, they can only obtain the gateway's external IP address.

  In order to enable access to the controller 2 from the Internet system via the gateway of the home network, the gateway can receive HTTP requests and send those requests to the remote devices 1A, 1B of the home network. And the domain name is copied to a path like "http://dvbtuner.no29.bahnstrasse.bonn.de/index/html" so that the gateway can access the target device in the home network Can do.

  Due to this new URL definition, in the present invention, as shown in FIG. 5, the audio / video device initializes their HTTP servers 3. In the case of the remote device 1A functioning as a tuner device, the main HTML document is stored in the memory in the HTTP server 3. The main HTML document is as follows, for example.

<A HREF = "http // tuner.no29.bahnstrasse.bonn.de /
tuner.no29.bahnstrasse.bonn.de/next.cgi "> next <\ A>
<A HREF = "http // tuner.no29.bahnstrasse.bonn.de /
tuner.no29.bahnstrasse.bonn.de/back.cgi "> back <\ A>
<A HREF = "http // storage.no29.bahnstrasse.bonn.de /
storage.no29.bahnstrasse.bonn.de "> storage <\ A>
<A HREF = "http // camera.no29.bahnstrasse.bonn.de /
camera.no29.bahnstrasse.bonn.de "> camera <\ A>
An example of the main HTML document in the memory of the HTTP server 3 included in the remote device 1B functioning as the storage device is shown below.

<A HREF = "http // storage.no29.bahnstrasse.bonn.de /
storage.no29.bahnstrasse.bonn.de/next.cgi "> next <\ A>
<A HREF = "http // storage.no29.bahnstrasse.bonn.de /
storage.no29.bahnstrasse.bonn.de/back.cgi "> back <\ A>
<A HREF = "http // tuner.no29.bahnstrasse.bonn.de /
tuner.no29.bahnstrasse.bonn.de "> tuner <\ A>
<A HREF = "http // camera.no29.bahnstrasse.bonn.de /
camera.no29.bahnstrasse.bonn.de "> camera <\ A>.
Each HTTP server 3 can detect a local domain name by performing reverse DNS lookup. That is, all HTTP servers 3 can query the local DNS server for their domain names to translate their IP addresses. In addition, when the home network is not connected to the Internet, a standardized local domain name such as “home net” can be used as the name server.

  All servers can compile HTML documents that describe:

  That is, the server compiles an HTML document indicating the current service. For example, in the case of a tuner device, this indicates a broadcast signal received as an input signal. To describe such a signal, the tuner converts MPEG data / related DVB SI (Digital Video Broadcast Signal Information) data to HTML data. In the case of a storage device in the recording mode, this indicates an input signal such as audio / video data on an isochronous channel. In addition to the text description of the service shown in FIG. 5, it is desirable that audio video data is also presented in the HTML menu. In order to support moving images, commands such as "server push" and "client pull" that regularly update pictures are used.

  If there is a service such as “next” or “back” that returns to the previous, such a service can be selected and operated. Each server associates an appropriate script or program with such an entry.

  In addition, each server can provide links to other devices on the home network. To determine the link, the server polls another device, for example at port 80, as it is the default IP port for HTTP communications, and if there is a response, the associated entry for that device. Establish. Alternatively, each server captures snoops, ie IP packets, to determine other devices that are active. With this polling or snoop process, the server generates hyperlinks for all remote devices.

  FIG. 6 is a flowchart showing processing performed by each device in the network based on the user command. After the initialization of the HTTP server, that is, the remote devices 1A and 1B and the controller 2, the display input device 8 connected to the controller 2 displays a message “Which device do you want to access?”. Here, in step S1, when the user types or voices a command such as “storage”, the controller 2 recognizes this command. When the recognition is completed without any problem, in step S2, the controller 2 performs DNS reference of the default domain input command “storage” which is “no29.bahnstrasse” in this example. In step S3, the DNS server returns 192.168.0.3, which is the internal IP address of the remote device 1B that functions as the storage device. In step S4, the browser of the controller 2 transmits the HTTP command “GET /” to the internal IP address of the desired apparatus, here 192.168.0.3.

  Steps S5 and S6 show the response of the HTTP server having the address 192.168.0.3, that is, here the remote device 1B functioning as a storage device, to the universal resource locator that is not transmitted by the new URL rule. In step S5, the server, that is, the remote device 1B functioning as a storage device identifies this conventional URL and returns a server redirect response as follows.

try "http://storage.no29.nahnstrasse.bonn.de/
storage.no29.bahnstrasse.bonn.de "instead!
In accordance with the redirect response, the browser transmits a new URL “GET storage.no29.nahnstrasse.bonn.de” in step S6. In this way, automatic conversion is performed, and the display input device 8 connected to the controller 2 displays a message “Fetching menu ...” during the waiting time caused by asynchronous connection.

  In step S7, the HTTP server 3 of the remote device 1B functioning as the storage device transmits “index.html” to the HTML page. The browser receives the HTML data and displays it on the display input device 8 as a graphical user interface (GUI). The display input device 8 includes, for example, the name “STORAGE” of the remote device 1B functioning as a storage device, next, back, tuner / camera, and the input device selected at that time of the remote device 1B (not shown here). And available commands such as pictures taken by a camera.

  When the first menu is supplied from the remote device 1B functioning as the selected storage device, in this embodiment, the user notifies that the device is currently connected to the camera. If the user wants to record from the tuner instead of the camera, the user issues a “next” command and requests the next service. In step S8, the controller 2 recognizes this command. In step S9, the browser finds the anchor “next” and sends the HTTP command “GET / storage.no29.bahnstrasse.bonn.de / next.cgi” to the IP address 192.168.0.3 of the remote device 1B functioning as the storage device. Send to. In step S10, the HTTP server 3 of the remote device 1B functioning as the storage device receives this command and executes the script “next.cgi”. Therefore, the remote device 1B functioning as a storage device selects a new isochronous channel and presents a new menu.

  In step S11, the controller 2 receives the updated menu from the remote device 1B and displays it on the connected display input device 8. At this stage, the menu includes new data received on the isochronous channel connecting the remote device 1A functioning as a tuner device to the remote device 1B functioning as a storage device. The data is, for example, a CNN video or the like.

  Since the user has already set the remote device 1B functioning as a storage device in a desired state, the user can switch to the remote device 1A functioning as a tuner device at this stage and select a desired channel. it can.

  To make these commands clearer, for example if the last line of the menu is to connect the browser to a different audio / video device, more elaboration and graphics are required and can be included on each HTML page. it can.

  Here again, the browser tries to find the anchor associated with the command "tuner". The command “tuner” follows the HREF field within the anchor. As a result, DNS is referred to “tuner.no29, bahnstrasse.bonn.de”, and an HTTP command “GET / tuner.no29.bahnstrasse.bonn.de” is transmitted to an appropriate IP address. The latter returns a menu related to the path, and the path includes information on the service currently selected. This menu also has entries of “next” and “back”, which perform different processing from the next and back processing of the remote device 1B functioning as a storage device. For example, a tuner “next” operation may change the frequency of the tuner, but the output signal from the tuner is transmitted using the same isochronous channel number.

  In another embodiment of the present invention, all or some menus of selected ones of the remote devices connected to the controller 2 are simultaneously displayed on the display input device 8 connected to the controller 2. .

  The extended network initialization to make it easier to set up an isochronous channel is described with reference to FIG. Here, an IEEE 1394 network system is used, and broadcasts of unrequested audio / video data described later are received and recorded.

  In a conventional IEEE 1394 application form such as a VTR, for example, the controller performs two-way communication with the user and controls both the source device and the target device almost simultaneously based on the user input. Thus, conventional controllers may hide part of the network configuration from the user. One disadvantage of this approach is that, in the worst case, the newly purchased source and target devices are only partially or not valid for the controller graphical interface. According to the present invention, a manufacturer of each device can develop a device using a user interface unique to each company so that a user can directly control each device. That is, as described above, the user can control the mutual relationship between the devices by continuously controlling both the source device and the target device.

  In order to improve convenience for the user, it is better to avoid fixing the order of the remote devices. That is, it is better to allow the user to freely select which source / remote device to control first. According to the present invention, for this purpose, each device capable of transmitting data on an isochronous channel can transmit such data in a desired data format immediately after setup. From a technical point of view, such broadcasts are called unsolicited broadcasts. Here, no direct or indirect user command is required to initiate isochronous data communication. These devices will continue to broadcast after the basic connection is established. If necessary, video data having high temporal and spatial redundancy is used in order to eliminate waste of bandwidth. For example, in the case of an MPEG2 transport stream, such video data is compressed to reduce the bit rate. If such a signal is not available at the input of the broadcasting device, that is, if there is no bit rate signal that can be transmitted to the IEEE 1394 isochronous channel and used at all, the hardware and software in the device are used. A simple signal can be generated. In addition, it is desirable that the initial isochronous data provides information for allowing the user to easily grasp the type and state of the device.

  Older devices such as existing IEEE 1394 devices do not support the ability to internally generate such low bit rate data streams. However, according to the present invention, new devices send instructions to these older devices immediately after start-up to start data broadcasting on the isochronous channel, even at conventional bit rates. In the case of a tuner, this makes it possible to efficiently transmit a bit stream by cable or satellite broadcasting to the home network. A storage apparatus equipped with a tuner such as a VTR can also transmit a broadcast service in order to save mechanical processing. For example, if there is a limitation on bandwidth, power consumption, etc. and it is not appropriate to do this with older devices, the system will notify the user that these devices need to be programmed. To do.

  As described above, according to the connection establishment method, the remote device, and the control device according to the present invention, in communication between a plurality of remote devices, a hypertext transfer protocol, that is, HTTP is used instead of a plurality of system-specific protocols. Establish a connection between remote devices.

  The remote device can act like an Internet server and provide menu choices that correspond to specific control functions. This simplifies controller design because the controller only needs to support one protocol. When upgrading a network system by adding remote devices, the controller need not include a new control protocol. To perform the upgrade, a user interface can be downloaded into the controller from each remote device controlled by the controller, and the downloaded interface provided to the user who wants to control the remote device.

  1A remote device, 1B remote device, 2 controller, 3 HTTP server, 4 data interface, 5 isochronous connection line, 8 display input device

Claims (12)

A connection establishment device for establishing a connection between a plurality of remote devices ,
Based on a predetermined universal resource locators assigned to each of the upper Symbol plurality of remote devices, each of the connected remote device, the remote control means for controlling by using a hypertext transfer protocol,
An interface provided in the remote control means for downloading a user interface from each of the remote devices to which the connection is established ,
The predetermined universal resource locator is configured by prefixing identification information for identifying the remote device,
The remote control means displays the downloaded user interface or a modified user interface;
By the remote control means, other interfaces different from the interface is connected to the Internet, connection establishment device the plurality of remote devices is remotely controlled by using the Hypertext Transfer Protocol.   The connection establishment apparatus according to claim 1, which is directly controlled via the user interface.   The connection establishment apparatus according to claim 2, wherein the user interface is a graphical user interface.   The connection establishment apparatus according to any one of claims 1 to 3, wherein a communication bandwidth is guaranteed for the connection established between the remote apparatuses.   The connection establishment apparatus according to any one of claims 1 to 4, wherein the remote apparatuses are connected via a bus conforming to IEEE 1394.   6. The connection establishment device according to claim 1, wherein the identification information for identifying the remote device is a name of the remote device. A connection establishment method for establishing a connection between a plurality of remote devices by a control device,
Downloading a user interface from each remote device with which the connection is established by the control device;
Controlling each of the connected remote devices using a hypertext transfer protocol based on a predetermined universal resource locator assigned to each of the plurality of remote devices by the control device. ,
The predetermined universal resource locator is configured by prefixing identification information for identifying the remote device,
The control device displays a user interface to modify the user interface or the user interface downloaded above,
By the control device, other interface different from the interface to download the user interface is connected to the Internet, connection establishment method in which the plurality of remote devices is remotely controlled by using the Hypertext Transfer Protocol.   The connection establishment method according to claim 7, wherein the control device is directly controlled via the user interface.   The connection establishment method according to claim 8, wherein the user interface is a graphical user interface.   The connection establishment method according to any one of claims 7 to 9, wherein a communication bandwidth is guaranteed for the connection established between the remote devices.   The connection establishment method according to any one of claims 7 to 10, wherein the remote devices are connected via a bus conforming to IEEE1394.   12. The connection establishment method according to claim 7, wherein the identification information for identifying the remote device is a name of the remote device.

Images