JP4792963B2 - Location information system - Google Patents

Description

  The present invention relates to a position information system that provides an installation position of an electric device in a facility, a name of the electric device, and the like, and more particularly to a position information system that reduces a communication burden related to acquisition of position information.

  Conventionally, it has been attempted to connect home appliances to each other via a wired or wireless network and control them indoors and outdoors. Such a home network is called a home network, and various middleware such as HAVi (Home AV interoperability (registered trademark)) and EchoNet (Energy Conservation and Homecare Network (registered trademark)) that define the rules of the network are used. Proposed. Many home appliances incorporating these middleware, so-called network home appliances, have been developed, and refrigerators, microwave ovens, home laundry home networks, etc. have been put into practical use. When a large number of network home appliances are connected in this way, it is assumed that there are many similar home appliances, and it is necessary to introduce an easy-to-understand mechanism so that the user can operate the target network home appliance.

  For example, if there is a VTR installed in the living room and a VTR installed in the bedroom, simply displaying “Video 1”, “Video 2”, etc. on the screen of the home server or the like that gives instructions to the VTR It is not possible to know where the VTR is, and it may happen that another VTR is operated unexpectedly. However, if a GUI (Graphical User Interface) that displays network home appliance icons on the home server screen is displayed on the screen of the home server, or if the location where the network home appliance is located is displayed by text information, the user Can intuitively understand the installation location of each network home appliance, and the probability of erroneous operation is expected to be much lower.

  In view of such problems, various techniques have been proposed for “where the network home appliances are located”. For example, in the invention disclosed in Japanese Patent Laid-Open No. 11-96131 (Patent Document 1), as shown in FIG. 13, information outlets F0 to F4 (hereinafter referred to as information outlet Fn) connected to the IEEE1394 bus are provided. In the configuration memory of the information outlet Fn, room information indicating which room is installed is stored in advance. Each device H0 to H9 (hereinafter referred to as device Hn) is connected to the IEEE1394 bus via the information outlet Fn, and when the bus manager A2 creates a topology map, the device Hn is connected to which information outlet Fn. By determining whether the device Hn is in the room, it is intended to recognize where the device Hn is located.

In the invention disclosed in Japanese Patent Laid-Open No. 2003-339086 (Patent Document 2), as shown in FIG. 14, a power source connected to power outlets I1 to I4 (hereinafter referred to as power outlet In) and having a built-in power line modem. Room information in which the self is installed is stored in advance in the adapters J1 to J3 (hereinafter referred to as the power adapter Jn). When each of the devices H10 to H13 (hereinafter referred to as device Hn) is connected to the power adapter Jn, the device Hn transmits a room information request, and the power adapter Jn that has received the room information request transmits the request. The room information is returned to the transmitted device Hn, and the device Hn stores the room information. Next, the in-home server A3 requests room information and information about the device from the device Hn, thereby recognizing where the device Hn is located.
JP-A-11-96131 JP 2003-339086 A

  As described above, according to the invention disclosed in each of the above patent documents, it is possible to recognize where the device Hn (network home appliance) is located. However, in order to recognize this, the device Hn has to communicate with other devices Hn, the power adapter Jn, etc. multiple times, and there is a problem that the communication interface of the device Hn is burdened. It was. More specifically, since the invention disclosed in Patent Document 1 employs IEEE1394, when the device Hn is connected to the information outlet Fn, a large amount of communication is performed by the configuration process. That is, after the reset signal is transmitted on the IEEE1394 bus, the parent-child relationship is determined between the nodes and the communication of the self ID packet is performed, so that the communication amount increases in proportion to the number of nodes. .

  In the invention disclosed in Patent Document 2, when the device Hn is connected to the power adapter Jn, the room information is acquired with the adapter Hn, and then the device information and the room information are transmitted to the in-home server A3. Therefore, similarly, the communication amount of the device Hn is large. This problem of traffic is not so much a problem in AV home appliances that perform image transmission and the like. This is because a high-speed communication interface is adopted so that a large amount of data can be transmitted. However, white goods that occupy more than half of the homes do not require a large amount of data transmission except when the control software is updated. Therefore, it is not always necessary to adopt an expensive and high-speed communication interface. Therefore, especially considering white goods, it is desired to reduce the communication burden of the device Hn as much as possible.

  Further, in each of the above patent documents, it is necessary to mount a microcomputer on the information outlet Fn or the power adapter Jn connected to the device Hn, which causes a problem that the system cost increases. More specifically, in the invention disclosed in Patent Document 1, the information outlet Fn itself is an IEEE1394 node, and the information outlet Fn must include a multi-bit microcomputer for processing the configuration process and the like. I must. However, if an attempt is made to incorporate such a microcomputer, the power outlet would be about several hundred yen, but it would be several thousand yen, and it would be impractical to use a plurality of such outlets in a house. However, this document also describes that the information outlet Fn is configured as one node. According to this configuration, the number of microcomputers used for the information outlet Fn can be reduced.

  However, in such a configuration, each information outlet Fn corresponds to a port, and therefore, the apparatus Hn must normally be installed within the maximum cable connection length of 4.5 m from the information outlet group. I must. However, since a device Hn may be installed at a position exceeding the length in a house, a bus bridge is used in order not to be restricted by the length. However, since a microcomputer is used for the bus bridge, the number of microcomputers cannot be reduced after all. Therefore, the invention disclosed in Patent Document 1 requires a plurality of microcomputers, resulting in an expensive system. In addition, the power adapter Jn of Patent Document 2 needs to receive a room information request from the device Hn and perform a reply process of the information. Therefore, it is necessary to incorporate a multi-bit microcomputer, and similarly, it is expensive. System.

  The present invention has been proposed in view of the above-described circumstances, and it is possible to reduce the communication burden of a device by acquiring information necessary for position management by a simple method without performing a special operation. An object of the present invention is to provide a position information system that can be used.

In order to solve the above-described problem, the location information system of the present invention transmits an IPv6 address included in an NS message in IPv6 as a device ID that is a unique identifier for uniquely identifying the device, and the device A device is connected based on a concentrator having a plurality of connected ports, a device ID transmitted from the device connected to the port, and port number information that uniquely identifies the port to which the device is connected. A device management device that identifies and manages a position, and the device transmits an NS message including the device ID to the device management device in response to being connected to a port of the concentrator, As the device ID is transmitted from the device, the device changes the port number information of the port to which the device is connected to the NS message including the device ID. And transmitted to the device management apparatus.

  According to the present invention, the device ID is transmitted to the device management device by the predetermined communication that starts when the device connected to the concentrator is connected to the port of the concentrator, and the device ID is transmitted from the device. As a result, the port number information of the port to which the device is connected by the line concentrator is transmitted to the device management device.

  Therefore, the device ID and port number information necessary for location management can be obtained with a simple method without performing any special operation, and the communication burden on the device can be reduced.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings.

  First, the configuration of a position information system shown as an embodiment of the present invention will be described with reference to FIG. As shown in FIG. 1, the position information system includes information outlets in which a plurality of devices Hn (n = 0, 1, 2,...) And a plurality of devices Hn are connected to each other and are located at different locations (positions). Fn, a line concentrator (switch device) C0 having a plurality of ports dn, a device management device A1 that manages the installation position of the device Hn, and a management database A0.

  In the position information system having such a configuration, the device management device A1 and the device Hn perform data communication via the concentrator C0, so that the device Hn connected to the port dn of the concentrator C0 via the information outlet Fn. The installation position can be detected and centrally managed by the device management apparatus A1.

  As shown in FIG. 1, the information outlet Fn is connected to the device Hn via a communication line gn derived (or connected) from the device Hn. The line concentrator C0 is connected to the information outlet Fn via the communication line en (n = 0, 1, 2, 3...) Connected to the port dn (n = 1, 2, 3, 4...). The line concentrator C0 is connected to the device management apparatus A1 via the communication line b2 connected to the port dn (n = 0). The device management apparatus A1 and the management database A0 are connected via a communication line b1. The device Hn and the information outlet Fn correspond to the information outlet Fn and the port dn on a one-to-one basis.

  The communication line b1 connecting the device management apparatus A1 and the management database A0 is not particularly limited as long as information communication is possible between the management database A0 and the device management apparatus A1, and for example, a USB A serial bus such as a (Universal Serial Bus) cable or SCSI (Small Computer System Interface) can be used.

  The communication line b2 that connects the line concentrator C0 and the device management apparatus A1, the communication line en that connects the line concentrator C0 and the information outlet Fn, and the communication line gn that connects the information outlet F0 and the apparatus Hn are between the devices. There is no particular limitation as long as communication is possible. For example, twisted pair cables such as 10BaseT and 100BaseTX are used, and the information outlet Fn employs an RJ45 modular jack. If necessary, a coaxial cable such as 10Base-2 or 5 may be used, or a USB cable may be used.

  The device Hn can perform data communication by TCP / IP with the device management apparatus A1 via the line concentrator C0. The device Hn is a detection target of the installation position in the position information system, and is, for example, a home appliance.

  In the position information system, the device Hn stores, in a memory (not shown), a device ID serving as a device-specific identifier that uniquely identifies itself, for example, an OID (Object ID). In addition to the device ID, the device Hn stores, in a memory (not shown), variables (variables), events (events), functions (functions), and the like used in control in the position information system. It can be presented voluntarily or in response to some request to the device management apparatus A1. Further, as the device ID, a MAC address or an IPv6 address may be used when it corresponds to IPv6 (Internet Protocol version 6).

  The line concentrator C0 is a layer 2 switch, that is, a switching hub, and holds the link state of the port dn as a MIB (Management Information Base). Further, if necessary, power can be supplied by PoE ((Power over Ethernet (registered trademark)) or the like.

  The device management apparatus A1 is a central control device in the position information system, and is linked to application programs such as a management tool of the line concentrator C0 held by itself, various data, and management data stored in the management database in the form of the device Hn. It is possible to smoothly manage the location of the. The device management apparatus A1 can be configured by, for example, a PC (Personal Computer).

  The management database A0 is a relatively large-capacity data storage unit such as a hard disk. The management database A0 holds a position information database in which information on the port dn (port number) of the line concentrator C0 is associated with position information indicating where each port dn is installed. Further, the management database A0 may hold a device information database describing various information such as specifications related to the device Hn corresponding to the position information system.

  The location information database held by the management database A0 is, for example, as shown in the data table of FIG. 2, for each management identification index, the IP address of the concentrator C0, each port number, location information corresponding to the port dn, Device information, device ID, port link state, MAC address (Media Access Control Address) that is an identifier of the device Hn, and the like are associated with the connected device Hn.

  If the concentrator C0 has a function capable of storing the IP address of the device Hn connected to the port dn, the IP address (Internet Protocol Address) may be stored without being limited to the MAC address.

  The IP address of the line concentrator C0 and the location information corresponding to the port dn are input in advance by a user or a contractor by an input unit (not shown).

  On the other hand, the device information database stores a device-specific identifier and information specific to the device in association with each other. The device-specific information includes a manufacturer name (for example, Matsushita) and a product system (for example, a product name). ), Serial number, etc. This database is not always necessary, and can usually be acquired as needed from a server (not shown) or the like remotely connected to the device management apparatus A1 via a network.

  In the position information system having such a configuration, in order for the device management apparatus A1 to grasp and manage the position of the device Hn connected to the port dn of the line concentrator C0 via the information outlet Fn, what kind of device Hn It is necessary to detect which port dn is connected to. Specifically, the device management apparatus A1 identifies and manages the position of the device Hn based on the device ID of the device Hn and the port number that uniquely identifies the port dn of the line concentrator to which the device ID is connected. I do. Therefore, the device management apparatus A1 needs to acquire the device ID and the port number when the device Hn is connected to the port dn of the line concentrator C0.

  Therefore, in this position information system, the device management apparatus A1 self-assigns the device ID by data communication based on TCP / IP that starts in response to the connection of the device Hn to the port dn of the concentrator C0 via the information outlet Fn. As the device ID is transmitted from the device Hn, the line concentrator C0 transmits the port number of the port to which the device Hn is connected to the device management apparatus A1. Thereby, apparatus management apparatus A1 can acquire apparatus ID and a port number. A specific method of acquiring the device ID and the port number by the device management apparatus A1 will be described in (1) to (4) below.

(1) Transmission method of device ID and port number using Gratuitous ARP (Address Resolution Protocol) ARP is a protocol used to acquire a MAC address of a communication partner prior to data communication based on TCP / IP. The device Hn can transmit the device ID to the device management apparatus A1 by using this ARP. ARP is a standard protocol provided in IPv4 (Internet Protocol version 4).

  Gratuitous ARP is a function of ARP used to forcibly update the contents of the ARP table held by the computer itself. With this Gratuitous ARP function, it is possible to check whether there is a duplicate IP address having a problem on the network at the time of activation.

  When connected to the port dn of the line concentrator C0, the device Hn broadcasts a Gratuitous ARP request packet as shown in the timing chart of FIG. 3 to check for duplicate IP addresses (step S1). FIG. 4 shows the packet format of Gratuitous ARP. As shown in FIG. 4, the device Hn attaches the device ID to the ARP request packet transmitted in step S1.

  The line concentrator C0 that has received the Gratuitous ARP request packet attaches the port number of the port dn to which the device Hn is connected via the information outlet Fn to the Gratuitous ARP request packet as shown in FIG. 5 (Step S2). .

  As a result, the device management apparatus A1 that has received the Gratuitous ARP request packet, the device ID that is a unique identifier that uniquely identifies the device Hn connected to the port dn of the line concentrator C0, and the concentrator to which this device ID is connected. The port number of the port dn of the device C0 can be acquired at a time.

  Then, the device management apparatus A1 that has received the Gratuitous ARP request packet stores the acquired link state of each port dn and the device ID of the device Hn in the position information database, as shown in FIG. In the example shown in FIG. 6, UP indicating that the device Hn is connected is stored in the ports D1 and D2, and DOWN indicating that the device Hn is not connected is stored in the other ports D3 and D4. In addition, H0 and H1 are stored in the ports D1 and D2 of the link UP as device IDs of the devices H0 and H1, respectively.

  Note that the MAC address information remains as it is even if the device Hn is DOWN (for example, index 4 in FIG. 6), and is deleted from the position information database when the same MAC address is newly registered (same index 1). It has come to be.

  In this way, the device management apparatus A1 recognizes which device Hn is installed in which port by identifying which device Hn is connected to which port dn from the device ID. it can.

  For example, in the example shown in FIG. 6, it can be seen that the device H0 is installed in the “1st floor living room” and the device H1 is installed in the “1st floor kitchen”. By the way, even if the device ID and MAC address are displayed, it is difficult for the user to understand, so the device management apparatus A1 refers to the device information database from the device ID and MAC address of the device Hn connected to the port dn. As shown in FIG. 7, for example, information such as “Matsushita Electric, VTR, SN (serial number)”, “Matsushita Electric, dryer, SN” is acquired, and the information excluding SN is added to the user along with the location information. May be notified (step S3).

  The device management apparatus A1 can specify and manage the position where the device Hn is connected by using the device ID and the port number acquired in this way. In addition, since the number of communications until the device ID and port number are acquired is very small, the communication burden on the device Hn can be greatly reduced.

(2) Device ID and port number transmission method using IPv6 (Internet Protocol version 6) address automatic configuration In IPv6, in order to realize plug and play, an IP address may be automatically set in a device. Address automatic configuration is provided as a standard function. A device compatible with IPv6 generates an IP address using information flowing on the network and sets the IP address. Utilizing this timing, the device ID is transmitted from the device Hn, and the port number of the port dn to which the device Hn is connected is transmitted from the line concentrator C0 along with the transmission of the device ID.

  An example of a method for transmitting a device ID and a port number according to this method is shown below. When a unique IP address of 128 bits is used as a device ID, it is given to the device Hn as a device ID. The case where OID is used can be assumed.

(When using IPv6 as device ID)
When IPv6 is used as the device ID, the device ID and the port number can be transmitted as shown in the timing charts shown in FIGS.

  First, the case where IPv6 is used as the device ID will be described using the timing chart shown in FIG. As shown in FIG. 8, when the device Hn is connected to the port dn of the concentrator C0 via the information outlet Fn, automatic address configuration is started in order to realize plug and play. In IPv6, normally, two IP addresses, a link local address and a global address, are assigned to the communication interface of the device Hn. The link local address is an IP address used for control in a link which is one network partitioned by routers, and the global address is an IP address used for normal data communication.

  As shown in FIG. 8, when any device Hn is connected (plugged in) to any port dn of the line concentrator C0 via the information outlet Fn, an address is set to start plug and play. Automatic configuration starts. In FIG. 8, the device Hn first tentatively configures a link local address, and in order to confirm that the tentatively configured link local address is not duplicated, an NS (Neighbor Solicitation) message is sent to the router via the concentrator C0. (Step S11).

  The link local address is configured by fixing the IPv6 IP address prefix and generating the interface ID by itself. If there is another terminal using this link local address, an NA (Neighbor Advertisement) message notifying that is transmitted from this terminal.

  At this time, the device Hn sends an RS (Router Solicitation) message requesting an RA (Router Advertisement) message, which is information including prefix information, to the router on the network in the temporarily configured link local and the concentrator C0. Via the network. Moreover, since this RA message is periodically transmitted, the device Hn does not necessarily need to send an RS message.

  The line concentrator C0 that has received the NS message adds the port number of the port dn to which the device Hn is connected and transmits it to the router (step S12). At this time, since the device management apparatus A1 monitors the NS message transmitted to the router, the device management apparatus A1 acquires the IPv6 address of the NS message as the device ID and acquires the port number added to the NS message. When the RS message is transmitted from the device ID, the device management apparatus A1 may acquire the IPv6 address of the RS message as the device ID and acquire the port number added to the RS message.

  Accordingly, the device management apparatus A1 from the NS message or the RS message, the device ID that is a unique identifier for uniquely identifying the device Hn connected to the port dn of the line concentrator C0, and the line concentrator to which the device ID is connected. The port number of the port dn of C0 can be acquired at once.

  As a result, the device management apparatus A1 can acquire device information in the same manner as step S3 of the timing chart shown in FIG. 3 (step S13).

  In the timing chart shown in FIG. 8, since the NA (Neighbor Advertisement) message is not transmitted from the terminal that received the NS message and there is no duplication in the temporarily configured link local address, the temporarily configured link local address is used. In addition, the device Hn composes a global address by combining the prefix included in the RA message and the interface ID generated by itself in response to receiving the RA message transmitted periodically or in response to the RS message. Will do.

  The device management apparatus A1 can specify and manage the position where the device Hn is connected by using the device ID and the port number acquired in this way. In addition, since the number of communications until the device ID and port number are acquired is very small, the communication burden on the device Hn can be greatly reduced.

  Next, the case where IPv6 is used as the device ID will be described using the timing chart shown in FIG. As shown in FIG. 9, when the device Hn is connected to the port dn of the concentrator C0 via the information outlet Fn, automatic address configuration is started in order to realize plug and play.

  In the timing chart shown in FIG. 9, the global address is first configured by the device Hn receiving the RA message (step S <b> 21) periodically transmitted. Next, the device Hn temporarily configures the link local address and transmits an NS message to the router via the line concentrator C0 in order to confirm that the temporarily configured link local address is not duplicated (step S22). ). At this time, the device Hn may transmit an RS message.

  The line concentrator C0 that has received the NS message adds the port number of the port dn to which the device Hn is connected and transmits it to the router (step S23). At this time, since the device management apparatus A1 monitors the NS message transmitted to the router, the device management apparatus A1 acquires the IPv6 address of the NS message as the device ID and acquires the port number added to the NS message. When the RS message is transmitted from the device ID, the device management apparatus A1 may acquire the IPv6 address of the RS message as the device ID and acquire the port number added to the RS message.

  Accordingly, the device management apparatus A1 from the NS message or the RS message, the device ID that is a unique identifier for uniquely identifying the device Hn connected to the port dn of the line concentrator C0, and the line concentrator to which the device ID is connected. The port number of the port dn of C0 can be acquired at once.

  Therefore, the device management apparatus A1 can acquire device information in the same manner as Step S3 of the timing chart shown in FIG. 3 (Step S24).

  In the timing chart shown in FIG. 9, since the NA message is not transmitted within a predetermined time from the terminal that received the NS message and there is no duplication in the temporarily configured link local address, the temporarily configured link local address is used.

  The device management apparatus A1 can specify and manage the position where the device Hn is connected by using the device ID and the port number acquired in this way. In addition, since the number of communications until the device ID and port number are acquired is very small, the communication burden on the device Hn can be greatly reduced.

(When using OID as device ID)
When an OID is used as the device ID, the device ID and the port number can be transmitted as shown in the timing chart shown in FIG. As shown in FIG. 10, when the device Hn is connected to the port dn of the line concentrator C0 via the information outlet Fn, automatic address configuration is started to realize plug and play.

  In the timing chart shown in FIG. 10, the global address is first configured by receiving the RA message (step S31) that is periodically transmitted by the device Hn. Next, the device Hn temporarily configures the link local address and transmits an NS message to the router via the line concentrator C0 in order to confirm that the temporarily configured link local address is not duplicated (step S32). ). The device Hn attaches the device ID to the NS message transmitted in step S32. At this time, the device Hn may transmit an RS message with the device ID attached.

  The line concentrator C0 that has received the NS message adds the port number of the port dn to which the device Hn is connected and transmits it to the router (step S33). At this time, since the device management apparatus A1 monitors the NS message transmitted to the router, the device management apparatus A1 acquires the device ID and the port number added to the NS message. When the RS message is transmitted from the device ID, the device management apparatus A1 may acquire the device ID and the port number added to the RS message.

  Accordingly, the device management apparatus A1 from the NS message or the RS message, the device ID that is a unique identifier for uniquely identifying the device Hn connected to the port dn of the line concentrator C0, and the line concentrator to which the device ID is connected. The port number of the port dn of C0 can be acquired at once.

  Therefore, the device management apparatus A1 can acquire device information in the same manner as Step S3 of the timing chart shown in FIG. 3 (Step S34).

  The timing chart shown in FIG. 10 shows a case where the NA message is transmitted from the terminal that has received the NS message within a predetermined time (step S35). As shown in FIG. 10, when the device Hn receives the NA message, the provisionally configured link local address is duplicated, and the link local address is temporarily configured again, and the NS message is routed through the line concentrator C0. (Step S36, step S37). When the device Hn does not receive the NA message within a certain time, the device Hn uses the provisionally configured link local address.

  The device management apparatus A1 can specify and manage the position where the device Hn is connected by using the device ID and the port number acquired in this way. In addition, since the number of communications until the device ID and port number are acquired is very small, the communication burden on the device Hn can be greatly reduced.

(When using IPv6 or OID as device ID)
When IPv6 or OID is used as the device ID, the device ID and the port number can be transmitted as shown in the timing chart shown in FIG. As shown in FIG. 11, when the device Hn is connected to the port dn of the concentrator C0 via the information outlet Fn, automatic address configuration is started in order to realize plug and play.

  In the timing chart shown in FIG. 11, the global address is first configured by the device Hn receiving the RA message (step S41) periodically transmitted. Next, the device Hn temporarily configures the link local address and transmits an NS message to the router via the line concentrator C0 in order to confirm that the temporarily configured link local address is not duplicated (step S42). ). At this time, the device Hn may transmit an RS message.

  The line concentrator C0 that has received the NS message adds the port number of the port dn to which the device Hn is connected and transmits it to the router (step S43). At this time, since the device management apparatus A1 monitors the NS message transmitted to the router, the device management apparatus A1 acquires the IPv6 address of the NS message as the device ID and acquires the port number added to the NS message. When the RS message is transmitted from the device ID, the device management apparatus A1 may acquire the IPv6 address of the RS message as the device ID and acquire the port number added to the RS message.

  As a result, the device management apparatus A1 connects the device ID (IPV6 address), which is a unique identifier that uniquely identifies the device Hn connected to the port dn of the line concentrator C0, and the device ID from the NS message or the RS message. The port number of the port dn of the collected line concentrator C0 can be acquired at a time.

  Here, it is assumed that the NA message is transmitted from the terminal that has received the NS message within a predetermined time (step S44). When the device Hn receives this NA message, it is assumed that there is an overlap in the temporarily configured link local address, and the link local address is temporarily configured again, and the NS message attached with the device ID (OID) is sent to the concentrator C0. To the router (step S45, step S46). The line concentrator C0 that has received the NS message adds the port number of the port dn to which the device Hn is connected and transmits it to the router. At this time, since the device management apparatus A1 monitors the NS message transmitted to the router, the device management apparatus A1 acquires the OID of the NS message as the device ID and acquires the port number added to the NS message.

  As a result, the device management apparatus A1 is connected to the apparatus ID (OID), which is a unique identifier for uniquely identifying the apparatus Hn connected to the port dn of the line concentrator C0, from the NS message or RS message. In addition, the port number of the port dn of the concentrator C0 can be acquired at a time.

  Therefore, the device management apparatus A1 can acquire device information in the same manner as Step S3 of the timing chart shown in FIG. 3 (Step S47).

  The OID is an identifier set in advance so as to be unique with respect to the device Hn. Therefore, the device Hn is uniquely identified rather than using IPv6 which is extended to 128 bits but cannot be determined unless it is necessarily duplicated. It is effective in some cases. However, when the OID is transmitted as the device ID, there is a problem that the transmission data amount increases.

  Therefore, in the method shown in the timing chart shown in FIG. 11, in the NS message transmitted for confirming the duplication of the link local address in the temporary configuration, the data amount is first reduced by using IPv6 as the device ID, When an NA message is returned, the uniqueness of the device ID is ensured by using the OID as the device ID.

  When the device Hn does not receive the NA message within a predetermined time, the device Hn uses the provisionally configured link local address as the link local address.

  The device management apparatus A1 can specify and manage the position where the device Hn is connected by using the device ID and the port number acquired in this way. In addition, since the number of communications until the device ID and port number are acquired is very small, the communication burden on the device Hn can be greatly reduced.

(3) Device ID and port number transmission method using DHCP (Dynamic Host Configuration Protocol) DHCP is a protocol for automatically setting network information such as IP address and subnet mask for devices in the network. In IPv4, plug and play can be realized.

  In order to use DHCP, it is assumed that a DHCP server in which an IP address to be distributed in the network is set is constructed. In this DHCP server, a subnet mask, route control information, a DNS (Domain Name System) server address, and the like are set as necessary. When the IP address is automatically set by DHCP, the DHCP client transmits a DHCP request packet for requesting permission to use the IP address provided from the DHCP server on the network where the DHCP server is running.

  Therefore, if the device Hn is a DHCP client and the device management device A1 is a DHCP server, the device management device is attached with the device ID and the port number in the DHCP request packet transmitted when connected to the port dn of the concentrator C0. Can be sent to A1. When the device management apparatus A1 is not directly a DHCP server, the device management apparatus A1 can monitor the DHCP communication between the device Hn as a DHCP client and a DHCP server provided on a separate network. Thereby, the device management apparatus A1 can acquire the device ID and the port number attached to the DHCP request packet.

  FIG. 12 is a timing chart when a DHCP server exists on the network connected to the device management apparatus A1 and the device management apparatus A1 monitors the DHCP communication between the device Hn, which is a DHCP client, and the DHCP server. .

  First, when the device Hn is connected to the port dn of the concentrator C0, it broadcasts a DHCP request packet as shown in the timing chart of FIG. 12 (step S51). The device Hn attaches the device ID to the DHCP request packet transmitted in step S51.

  The line concentrator C0 that has received the DHCP request packet attaches the port number of the port dn to which the device Hn is connected via the information outlet Fn to the DHCP request packet (step S52).

  As a result, the device management apparatus A1 that has received the DHCP request packet receives the device ID that is a unique identifier for uniquely identifying the device Hn connected to the port dn of the line concentrator C0, and the line concentrator to which the device Hn is connected. The port number of the port dn of C0 can be acquired at once.

  Therefore, the device management apparatus A1 can acquire device information in the same manner as Step S3 of the timing chart shown in FIG. 3 (Step S53). Also, the DHCP server that has received the DHCP request packet transmits a DHCP reply packet to the device Hn (step S54).

  The device management apparatus A1 can specify and manage the position where the device Hn is connected by using the device ID and the port number acquired in this way. In addition, since the number of communications until the device ID and port number are acquired is very small, the communication burden on the device Hn can be greatly reduced.

  The characteristic functions of the above-described embodiment can be applied to a home network in which home appliance groups are connected to a network, an equipment network in which equipment groups are connected to a network, and the like.

  Here, as a technology for constructing a home network, in addition to the ECHO network, an embedded network technology called EMIT (Embedded Micro Internetworking Technology) can be used. This embedded network technology has a function of incorporating EMIT middleware into a network device and connecting it to a network, and is called EMIT technology.

  More specifically, a network device such as a terminal, a relay device, or a server is equipped with EMIT software that realizes EMIT technology, and a terminal or relay device that includes the EMIT software, and a user device that is remotely controlled or monitored Are connected for communication via a server provided on the Internet.

  The above-described embodiment is an example of the present invention. For this reason, the present invention is not limited to the above-described embodiment, and according to the design or the like, as long as the technical idea according to the present invention is not deviated from other embodiments. Of course, various modifications are possible.

It is a figure for demonstrating the structure of the positional information system shown as embodiment of this invention. It is a figure which shows the initial state of a positional infomation database. It is a timing chart for demonstrating the transmission method of apparatus ID and a port number using Gratuitous ARP (Address Resolution Protocol). It is the figure which showed the packet format of Gratuitous ARP to which apparatus ID was attached. It is the figure which showed the packet format of Gratuitous ARP with which the port number was attached. It is the figure which showed an example of the position information database structure after apparatus ID and port number acquisition. It is the figure which showed an example of the structure of the positional infomation database after apparatus information acquisition. It is a timing chart for demonstrating the transmission method of apparatus ID and a port number using the address automatic structure of IPv6 (Internet Protocol version 6). It is a timing chart for demonstrating the transmission method of apparatus ID and a port number using the address automatic configuration of the IPv6. It is a timing chart for demonstrating the transmission method of apparatus ID and a port number using the address automatic configuration of the IPv6. It is a timing chart for demonstrating the transmission method of apparatus ID and a port number using the address automatic configuration of the IPv6. It is a figure for demonstrating the transmission method of apparatus ID and a port number using DHCP (Dynamic Host Configuration Protocol). It is a figure for demonstrating the positional information system of the node using IEEE1394 shown as a prior art. It is a figure for demonstrating the positional information system by the power line conveyance shown as a prior art.

Explanation of symbols

A0 Management Database A1 Device Management Device C0 Concentrator Fn Information Outlet Hn Device dn Port en Communication Line gn Communication Line

Claims (1)

A device that transmits an IPv6 address included in an NS message in IPv6 as a device ID that is a unique identifier that uniquely identifies the device;
A line concentrator having a plurality of ports to which the device is connected;
A device management device that identifies and manages the position where the device is connected based on the device ID transmitted from the device connected to the port and the port number information that uniquely identifies the port to which the device is connected; Prepared,
In response to being connected to the port of the line concentrator, the device transmits an NS message including the device ID to the device management apparatus.
As the device ID is transmitted from the device, the line concentrator includes port number information of the port to which the device is connected in an NS message including the device ID and transmits the information to the device management apparatus. Feature location information system.

Images