JP4792964B2 - 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 Application Laid-Open No. 11-96131 (Patent Document 1), as shown in FIG. 11, 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.

Further, in the invention disclosed in Japanese Patent Laid-Open No. 2003-339086 (Patent Document 2), as shown in FIG. 12, 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 adapters J1 to J3 (hereinafter referred to as power supply 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 position information system of the present invention includes a device that transmits a device ID that is a unique identifier that uniquely identifies the device, and a concentrator that includes a plurality of ports to which the device is connected. A device management apparatus for identifying and managing a position to which the device is connected based on a device ID transmitted from the device connected to the port and port number information for uniquely identifying the port to which the device is connected; The concentrator detects that the device is connected to the port, transmits a TRAP signal to the device management device via SNMP, and the device management device responds to the reception of the TRAP signal. Te, transmits a predetermined confirmation request to the device, the device transmits the device ID to the response time in response to the confirmation request to the device management apparatus, the device management apparatus, said port Equipment responds to the connection confirmation request transmitted at a predetermined timing after being connected, acquires the port number information from the connection acknowledgment from the concentrator.

In order to solve the above-described problem, the position information system of the present invention includes a device that transmits a device ID, which is a unique identifier that uniquely identifies itself, and a concentrator having a plurality of ports to which the device is connected. Device management that identifies and manages the location where the device is connected based on the device, 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 The concentrator detects that the device is connected to the port, transmits a TRAP signal to the device management device via SNMP, and the device management device receives the TRAP signal. depending on, transmits a predetermined confirmation request to the device, the device transmits the device ID to the response time in response to the confirmation request to the device management apparatus, the concentrator, the apparatus Along to Luo device ID is transmitted, transmits the port number information of the port where the device is connected to the device management apparatus.

  According to the present invention, when a device responds to a predetermined confirmation request transmitted from the device management device, the device ID is transmitted to the device management device, and the device is connected to the port of the concentrator by the device management device. The port number information is acquired from the connection confirmation response from the line concentrator that responds to the connection confirmation request transmitted at a predetermined timing after.

  In addition, when the device transmits a device ID to the device management device in response to a predetermined confirmation request transmitted from the device management device, the port management unit manages the port number information of the port to which the device is connected from the line concentrator. Send to device.

  Therefore, since the device ID and port number information required for location management can be reliably acquired by a simple method without performing a special operation for a device that does not spontaneously transmit a device ID, the communication burden of the device is reduced. It becomes possible to do.

  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. Note that a coaxial cable such as 10Base-2 or 5 may be used as necessary, 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 location information system, the device Hn transmits a device ID to the management device when responding to a predetermined confirmation request transmitted from the device management apparatus A1 in data communication using TCP / IP. In addition, the device management apparatus A1 directly acquires the port number of the port dn to which the device Hn is connected via the information outlet Fn by inquiring the port number of the port dn, or the device ID is transmitted from the device Hn. Accordingly, 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. In the following (1) to (4), an inquiry made from the device management apparatus A1 to the device Hn is a network inspection command using ICMP (Internet Control Message Protocol), which is used on IPv6 (Internet Protocol version 6) Multicast ping (packet inter network groper). Further, since the IPv6 IP address is composed of 128 bits, uniqueness can be drastically ensured as compared to IPv4. Therefore, an IPv6 address is used as the device ID transmitted from the device Hn.

(1) First method by sending device ID by multicast ping response and port number inquiry using SNMP (Simple Network Management Protocol) In IPv6, IP address is automatically assigned to realize plug and play. Automatic address configuration that can be set in the device 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.

  As shown in the timing chart of FIG. 3, the device management apparatus A1 always performs a multicast ping for inquiring a device ID before the device Hn is plugged in (connected) to the port dn of the line concentrator C0. Suppose you are sending to.

  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 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. 3, when any device Hn is plugged into any port dn of the concentrator C0 via the information outlet Fn, automatic address configuration is performed to start plug-and-play. Be started. Here, the device Hn first receives global information from the router by receiving an RA (Router Advertisement) message (step S1) that includes information on the prefix that constitutes the IP address of the IPv6 that is being transmitted at all times. Suppose you have configured an address.

  The device management apparatus A1 transmits a multicast ping addressed to the IPv6 host for which the device ID is inquired to the line concentrator C0 and inquires the connected device Hn to request transmission of the device ID (step S2). The device Hn that has received this multicast ping responds to this (step S3).

  Accordingly, the device management apparatus A1 that has received the response to the multicast ping can acquire a device ID that is a unique identifier that uniquely identifies the device Hn connected to the port dn of the line concentrator C0.

  Next, the device Hn tentatively configures the link local address and confirms that the temporarily configured link local address is not duplicated by sending an NS (Neighbor Solicitation) message to the router via the line concentrator C0. Transmit (step S4).

  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. The device Hn sets the provisionally configured link local address as the official link local address in response to the NA message not being transmitted within a certain time.

  Next, the device management apparatus A1 that has received the response to the multicast ping confirms to which port dn of the line concentrator C0 the device Hn that has acquired the device ID from this response, and acquires the port number. Therefore, a connection confirmation request is transmitted to the line concentrator C0 (step S5). In response, the line concentrator C0 returns a device connection confirmation response (step S6).

  For this connection confirmation, SNMP (Simple Network Management Protocol) Get Request and Get Response are used in this embodiment. SNMP is a protocol for managing network devices. The device management apparatus A1 functions as a manager having a management function, and the line concentrator C0 functions as an agent to be managed.

  SNMP is a protocol generally realized on UDP (User Datagram Protocol), and an SNMP message is composed of an SNMP version, a community used for a password between a manager and an agent, and a PDU (Protocol Data Unit). ing.

  As shown in FIG. 4, these SNMP messages are displayed when a PDU type, a request ID for associating a response of a manager (device management apparatus A1) and an agent (concentrator C0), an error status indicating an error code, and an error occur. It consists of an error index and object data indicating which data has an error.

  That is, the device management apparatus A1 transmits a Get Request that stores a PDU type of “0” indicating Get Request, a predetermined request ID, an OID (Object Identification) of each port dn, and the like. On the other hand, from the line concentrator C0, the response is “3” PDU type indicating Get Response, corresponding request ID, OID of each port dn, link UP or DOWN of each port dn, and link UP. Returns a Get Response in which the MAC address of the connected device Hn is stored.

  Next, the device management apparatus A1 that has received the connection confirmation response (Get Response) 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. 5, 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 when the device Hn is linked down (for example, index 4 in FIG. 5), and when the same MAC address is newly registered (index 1 in FIG. 5), the position information database Has been removed from.

  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. 5, 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 only the device ID and the MAC address are displayed, it is difficult for the user to understand. Therefore, the device management apparatus A1 refers to the device information database from the device ID and the MAC address of the device Hn connected to the port dn. As shown in FIG. 6, for example, information such as “Matsushita Electric, VTR, SN (serial number)”, “Matsushita Electric, hair dryer, SN” is acquired, and information excluding SN, together with location information, You may make it alert | report to a user (step S7).

As a result, the device management apparatus A1 can acquire the port number that identifies which port dn of the concentrator C0 the device Hn is connected to, and by using the previously acquired device ID, the device Hn It is possible to identify and manage the location where the is connected. 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) Second Method by Transmission of Device ID by Multicast Ping Response and Port Number Inquiry Using SNMP Here, as shown in the timing chart of FIG. 7, the device management apparatus A1 and the device Hn are the concentrator C0. It is assumed that a multicast ping for inquiring a device ID is not always transmitted to the line concentrator C0 before being plugged in (connected) to the port dn.

  In such a case, as shown in the timing chart of FIG. 7, when any device Hn is connected to any information outlet Fn (step S11), the line concentrator C0 has the device Hn at its own port dn. Detecting the connection, a device connection signal is transmitted to the device management apparatus A1 (step S12).

  For example, SNMP TRAP is used to transmit the device connection signal. As described above, SNMP is a protocol for managing network devices, the device management apparatus A1 functions as a manager having a management function, and the line concentrator C0 functions as an agent to be managed. It has become.

  TRAP is information transmitted from the agent side when there is a failure or a change in state in the network device. More specifically, as shown in the packet format of FIG. 8, SNMP is generally a protocol realized on UDP (User Datagram Protocol), and an SNMP message includes an SNMP version, a password between a manager and an agent, and the like. It is composed of a community and a PDU (Protocol Data Unit).

  The PDU is different from Get Request used for reading information, and is unique to TRAP. As shown in FIG. 8, the PDU type in which “4” indicating TRAP is stored, and the company defining the TRAP is used. OID (Object Identification), IP address of agent (concentrator C0), general trap number that stores “3” indicating link-up, unique trap number when sending a company-specific trap, concentrator C0 is activated last Then, object data indicating which port dn is connected to the device Hn is stored, which includes a time stamp indicating the time until the occurrence of the TRAP, an OID, and a value.

  The UDP header stores the SNMP port number, the IP header stores the IP address of the device management apparatus A1, and the MAC header stores the MAC address of the device management apparatus A1. Therefore, it is necessary for the line concentrator C0 to store the IP address of the device management apparatus A1 in advance by a user or a contractor.

  Steps S11 and S12 are communication preparation periods, which are silence periods during which the device Hn does not communicate spontaneously. In this silence period, the device Hn first receives the global address from the router by receiving the RA message (step S13) which is information including the prefix information constituting the IPv6 IP address that is always transmitted. Suppose you have configured.

  In response to being notified by SNMP TRAP that the device Hn is connected to the concentrator C0, the device management apparatus A1 transmits a multicast ping addressed to the IPv6 host that makes an inquiry about the device ID to the concentrator C0. Then, the connected device Hn is inquired to request transmission of the device ID (step S14). Multicast ping continues to be retransmitted periodically in consideration of the case where the address configuration is incomplete.

  The device Hn that has received this multicast ping responds to this (step S15). Accordingly, the device management apparatus A1 that has received the response to the multicast ping can acquire a device ID that is a unique identifier that uniquely identifies the device Hn connected to the port dn of the line concentrator C0.

  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 S0). S16).

  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 message notifying that is transmitted from this terminal. The device Hn sets the provisionally configured link local address as the official link local address in response to the NA message not being transmitted within a certain time.

  Next, the device management apparatus A1 that has received the response to the multicast ping confirms to which port dn of the line concentrator C0 the device Hn that has acquired the device ID from this response, and acquires the port number. Therefore, a connection confirmation request is transmitted to the line concentrator C0 (step S17). In response to this, the line concentrator C0 returns a device connection confirmation response (step S18). The device information acquisition processing in steps S17, S18, and further in step S19 is exactly the same as the processing in steps S5 to S7 shown in FIG.

  As a result, the device management apparatus A1 can acquire the port number that identifies which port dn of the concentrator C0 the device Hn is connected to, and by using the previously acquired device ID, the device Hn It is possible to identify and manage the location where the is connected. 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 transmission method by multicast ping response, port number acquisition method using SNMP TRAP As shown in the timing chart of FIG. 9, this method is a process until the device ID is acquired by multicast ping. Since the processing from step S11 to step S15 in the timing chart of FIG. As shown in FIG. 9, this method is different in that SNMP TRAP is used instead of SNMP Get Request and Get Response when acquiring a port number from the line concentrator C0.

  As shown in FIG. 9, the device Hn that has transmitted the response of the multicast ping temporarily configures the link local address, and collects the NS message to confirm that the temporarily configured link local address is not duplicated. The data is transmitted to the router via the device C0 (Step S21, Step S22). At this time, in response to receiving the NS message, the line concentrator C0 attaches the port number to the SNMP TRAP and transmits it to the device management apparatus A1 (step S23).

  As a result, the device management apparatus A1 can acquire the port number that identifies which port dn of the concentrator C0 the device Hn is connected to, and by using the previously acquired device ID, the device Hn It is possible to identify and manage the location where the is connected. 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 device information acquisition process in step S24 is exactly the same as the process in step S7 shown in FIG.

(4) Device ID Transmission and Port Number Transmission Method by Multicast Ping Response As shown in the timing chart of FIG. 10, this method is a step in the timing chart of FIG. 7 until the process of requesting the device ID by multicast ping. Since it is exactly the same as the processing from S11 to S14, the description is omitted. As shown in FIG. 10, the present method is different in that a multicast ping response is used when a port number is acquired from the line concentrator C0.

  As illustrated in FIG. 10, the device Hn that has received the multicast ping responds to the device management apparatus A1 with the multicast ping (step S31). At this time, the line concentrator C0 attaches the port number of the port dn to which the device Hn is connected to the response to the multicast ping transmitted to the device management apparatus A1 (step S32).

  As a result, the device management apparatus A1 can acquire the port number that identifies which port dn of the concentrator C0 the device Hn is connected to, and by using the previously acquired device ID, the device Hn It is possible to identify and manage the location where the is connected. 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. In particular, when a port number of the port dn to which the device Hn is connected is attached to the response of the multicast ping and transmitted, the port number is obtained by using SNMP Get Request and Get Response, or SNMP TRAP. Thus, the number of data communication can be further reduced.

  The device information acquisition process in step S33 is exactly the same as the process in step S7 shown in FIG.

  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 1st method by transmission of apparatus ID by a multicast ping (packet inter network groper) response, and the inquiry of the port number using SNMP (Simple Network Management Protocol). It is the figure which showed the packet format of SNMP. 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 2nd method by transmission of apparatus ID by a multicast ping response, and the inquiry of the port number using SNMP. It is the figure which showed the packet format of SNMP-TRAP. It is a timing chart for demonstrating the transmission method of apparatus ID by a multicast ping response, and the acquisition method of the port number using SNMP TRAP. It is a timing chart for demonstrating the transmission method of apparatus ID by a multicast ping response, and the transmission method of a port number. 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 (2)

A device that transmits a device ID that is a unique identifier for uniquely identifying 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,
The line concentrator detects that the device is connected to the port, transmits a TRAP signal to the device management device by SNMP,
In response to receiving the TRAP signal, the device management apparatus transmits a predetermined confirmation request to the device,
The device transmits a device ID to the device management apparatus in response to the confirmation request ,
The device management apparatus acquires the port number information from a connection confirmation response from the line concentrator in response to a connection confirmation request transmitted at a predetermined timing after a device is connected to the port. Location information system. A device that transmits a device ID that is a unique identifier for uniquely identifying 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,
The line concentrator detects that the device is connected to the port, transmits a TRAP signal to the device management device by SNMP,
In response to receiving the TRAP signal, the device management apparatus transmits a predetermined confirmation request to the device,
The device transmits a device ID to the device management apparatus in response to the confirmation request ,
The location information system, wherein the concentrator transmits port number information of a port to which the device is connected to the device management device as a device ID is transmitted from the device.

Images