JPH11355303A - Computer identification system and method - Google Patents

Abstract

(57) [Summary] [PROBLEMS] In a computer network using DHCP, a device connected to the network is permanently and uniquely identified. In a computer network using DHCP, a pseudo-physical device ID management unit 17 generates a pseudo-physical device ID uniquely for a MAC address owned by each device, and associates the MAC address with the generated pseudo-physical device ID. The correspondence with the device ID is registered in the pseudo physical device ID table. And the business application unit 9
When identifying individual devices, instead of using an IP address, a pseudo physical device ID uniquely corresponding to a MAC address is obtained from the pseudo physical device ID management unit 17,
This pseudo physical device ID is used.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a computer identification system on a computer network, and more particularly to a technique suitable for permanently and uniquely identifying individual devices on a computer network using DHCP.

[0002]

2. Description of the Related Art Computer networks such as TCP /
In an IP network, a network layer identifier (that is, an IP address) is used to identify a computer connected to the network. In addition, devices operating on the network include identifiers at the physical layer in the OSI reference model (hardware addresses used to identify terminals connected to the network, that is, MAC addresses), and network layers. I at
DHCP (DynamicHost Co.) that dynamically associates P addresses
nfigurationProtocol) is used. When using DHCP, only a device in an active state is assigned a valid IP address in the network. Therefore, when a device changes state, such as when the device is disconnected from the network or shifts from the operating state to the non-operating state, the IP address assigned before the change is changed to another operating state. Is assigned its IP address, so the MAC address and I
The correspondence of the P address changes.

[0003]

FIG. 1 shows the relationship between an IP address and a logical host name that uniquely corresponds to each other.

[0004] FIG. 2 shows the correspondence between an IP address and a MAC address dynamically assigned to each device in an active state at a certain point in time.

FIG. 3 shows the correspondence between the MAC address to which the IP address is assigned and the logical host name in the state shown in FIG.

For example, as shown in FIG. 1, [172.17.0.6
8] corresponds to the logical host name HostD. Also, the IP address [172.17.0.68]
As shown in (1), it is assigned to a device in the operating state having the MAC address [FF: 00: 17: 94: 42: 0B]. Therefore, as shown in FIG. 3, a device to which an IP address [172.17.0.68] is assigned is assigned a logical host name of HostD.

FIG. 4 shows an IP address and MAC dynamically assigned to each active device when the status of a plurality of devices is changed from the status in FIG.
Indicates the correspondence with the address.

FIG. 5 shows the correspondence between a MAC address to which an IP address is assigned and a logical host name in the state shown in FIG.

When the device is no longer in the active state from the previous state, as shown in FIG. 4, the IP address [172.17.0.68] assigned before the state change is changed to another active device. (MAC address [FF: 00: 17: 93: 4E: 1
0]). Accordingly, as shown in FIG. 5, the logical host name HostD corresponding to the IP address [172.17.0.68] is also different from the device (MAC address [FF: 00: 17: 93: 4E] in the state shown in FIG. : 10]).

[0010] The MAC address [FF: 00: 17: 94: 42: 0]
2], the IP address [172.17.0.67] corresponding to Host C is assigned in the state of FIG. 2, but from this state, the state of the other device is changed to change the state of FIG. When the state is changed, an IP address [172.17.0.68] different from that before the state change is assigned, and accordingly, a logical host name HostD different from the state in FIG. 2 is allocated to the device.

As described above, if the state of the device connected to the network changes, the correspondence between the MAC address and the IP address by DHCP changes (if the IP address corresponds to the logical host name, the MAC address changes). And the correspondence between logical host names also change). Therefore, it is possible to identify each device in the operating state by a conventional identification method using an IP address.However, when a device whose state has changed, such as a power-off state, is restarted, the original device can be identified. Cannot be recognized as being the same as That is, there is a problem that it is not possible to permanently and uniquely identify each device whose state has changed.

In connection with the problem, there is also a problem that when a device is secretly connected to the network with malicious intent or the like, it cannot be identified at an application level.

Accordingly, a more general object of the present invention is to
In a computer network using DHCP, the purpose is to permanently and uniquely identify each device connected to the network.

[0014]

The system is connected to a computer network and has one or more devices having a fixed hardware address and a dynamically assigned logical address, and a computer network. And a pseudo physical device ID management unit that is provided in any one of the nodes on the computer network and uniquely assigns a pseudo physical device ID to each device. The business server receives a network stack having an ARP table in which the correspondence between hardware addresses and logical addresses of individual devices is registered, and a logical address included in a communication signal from the device, and converts the logical address to a pseudo physical device. ID
And a business application unit for receiving a pseudo physical device ID corresponding to the logical address sent from the management unit, and identifying the device based on the pseudo physical device ID. The pseudo physical device ID management unit stores the hardware address of each device and the pseudo physical device ID.
Have a pseudo-physical device ID table registered correspondingly.

The business application unit in the business server receives the logical address contained in the communication packet from the device and sends it to the pseudo physical device ID management unit. The pseudo physical device ID management unit acquires a hardware address corresponding to the transmitted logical address from the ARP table, and generates a pseudo physical device ID uniquely corresponding to the hardware address. Then, the correspondence between the hardware address and the pseudo physical device ID is registered in the pseudo physical device ID table, and the generated pseudo physical device ID is sent to the business application unit. The business application unit uses this pseudo physical device ID when identifying each device. Devices and pseudo-physical devices
Since the correspondence with the ID does not change, the business application unit can permanently and uniquely identify each device. This makes it possible to provide a service that depends on each device, for example, a service that requires authority to execute, such as an electronic approval process, to only certain terminals.

In this embodiment of the system, the pseudo physical device ID management unit is provided at a predetermined node outside the business server on the network, and is connected to the pseudo physical device ID management unit in the business server so as to be communicable with the pseudo physical device ID management unit. And a pseudo physical device ID management stub functioning as an interface of the pseudo physical device ID management unit.

The pseudo physical device ID management stub receives a logical address from the business application unit, acquires a hardware address corresponding to the logical address from the ARP table, and sends the hardware address to the pseudo physical device ID management unit. . Similarly, the pseudo physical management stub provided in another business server is sent to the same pseudo physical device ID management stub. The pseudo physical device ID management unit generates a pseudo physical device ID that uniquely corresponds to a hardware address sent from a plurality of pseudo physical device ID management stubs. As a result, if there are multiple business servers on the network, those business servers
The common pseudo-physical device ID generated by the common pseudo-physical device ID can be used, and individual devices can be uniformly managed.

[0018]

FIG. 6 shows how IP addresses are dynamically assigned by DHCP in a computer network using TCP / IP according to an embodiment of the present invention.

A computer network using DHCP generally includes a large number of devices 1a, 1b (in FIG. 6, two devices 1a,
1b only) and the IP from each active device
It includes a DHCP daemon 3 that receives an address assignment request and assigns an assignable IP address, and a business server 5 connected to the network. The DHCP daemon 3 has an IP lease table 7 for registering the correspondence between the assigned IP address and the assigned MAC address. Inside the business server 5, a business application unit 9 for recognizing an IP address included in a communication signal from each device is provided at the uppermost layer, and an active state is provided below the business application unit 9. ARP (Address ResolutionPr) that registers the MAC address and IP address of the device
otocol) Network stack 1 with table 11
3 are provided. Network study 13
This layer is lower than DHCP.

The devices 1a and 1b and the device not shown in FIG. 6 include, for example, those shown in the left column of FIG.
MAC addresses are permanently assigned. For example, device 1a has a MAC address [FF: 00: 17: 93: 4E: 1
0], and the device 1b has a MAC address [FF: 00: 17: 92: E0: 2
A] is assigned.

Next, among many devices, device 1
The operation when the device 1a enters the operating state will be described with reference to a (MAC address [FF: 00: 17: 93: 4E: 10]) as an example.

When the device 1a enters the operating state, the device 1a sends a request for assigning an IP address to the DHCP daemon 3 together with its own MAC address [FF: 00: 17: 93: 4E: 10].
The DHCP daemon 3 returns the assignable IP address [172.17.0.67] at the time of receiving the grant request to the device 1a. At that time, the DHCP daemon 3 registers the returned IP address and the MAC address of the return destination in the IP lease table 7 inside the DHCP daemon 3 in association with each other. on the other hand,
In the business server 5, the network stack 13 uses the IP address and the MAC address of the device 1a included in the communication packet sent from the device 1a to the business server 5 to determine the correspondence between the IP address and the MAC address of the device 1a. , Detected by the ARP, and registered in the ARP table 11.
By performing such an operation for all the active devices on the network, the correspondence between the IP address and the MAC address of each of the active devices becomes, for example, the correspondence shown in FIG. (The operating state of a plurality of devices at a certain point in time as shown in FIG. 2 is referred to as state 1, and hereinafter referred to as state 1.)

When the operating state of one or more devices changes from this state 1, as described above, for example,
Device 1a assigned address [172.17.0.67]
(MAC address [FF: 00: 17: 93: 4E: 10]) is given a different IP address [172.17.0.68] as shown in FIG. 4 (a plurality of devices as shown in FIG. 4). Is referred to as state 2 and hereinafter referred to as state 2). Thus, when the operating state of the device changes, the correspondence between the MAC address and the IP address of the device changes. Therefore, in a conventional computer identification system that identifies a computer using an IP address, since the IP address is dynamically assigned, there is a problem that individual devices cannot be permanently and uniquely identified. Therefore, as a means for solving this problem, in the present embodiment, a pseudo physical device ID that permanently and uniquely corresponds to a MAC address is used to identify a computer.

The configuration of this embodiment using the pseudo physical device ID will be described with reference to FIG.

The business server 5 includes a pseudo physical device ID management stub 15 between the business application unit 9 and the network stack 13. On the other hand, a pseudo physical device ID management stub 15 is communicably connected, and has a pseudo physical device ID table 19 in which a unique correspondence between a MAC address and a pseudo physical device ID is registered. And a pseudo-physical device ID management unit 17 provided in the server. The pseudo physical device ID management stub 15 functions as an interface between the business application unit 9 and the network stack 13 of the pseudo physical device ID management unit 17. That is, it receives the IP address from the business application unit 9, accesses the ARP table 11 of the network stack 13, obtains the MAC address corresponding to the received IP address, and stores the MAC address in the pseudo physical device ID management unit 17 Send to Then, the pseudo physical device ID management unit 17 returns a pseudo physical device ID uniquely corresponding to the transmitted MAC address, and sends the returned ID to the business application unit 9. The pseudo physical device ID management unit 17 generates a pseudo physical device ID that can be uniquely assigned to the MAC address sent from the pseudo physical device ID management stub 15, and returns the ID to the pseudo physical device ID management stub 15. I do.
At this time, the generated pseudo physical device ID and the MAC address before generation are uniquely associated and registered in the pseudo physical device ID table 19.

The operation of the present system will be described by taking as an example a case where a request is issued from the active device 1a to the business server 5 in the state 1.

Device 1a (MAC address [FF: 00: 17: 93:
4E: 10]), the business application unit 9 first receives the request and recognizes the IP address [172.17.0.67] included in the communication signal from the device 1a. . next,
The business application unit 9 stores the IP address [172.17.0.6] of the device 1a in the pseudo physical device ID management stub 15.
7], and the pseudo physical device ID corresponding to device 1a
Make a request to get Requested pseudo physical device ID
The management stub 15 obtains the MAC address corresponding to the transmitted IP address of the device 1a by using the ARP table 1
Access 1 Among the plurality of IP addresses registered in the ARP table 11, the IP address [172.17.0.67] of the device 1a is detected, and the corresponding MAC address [FF: 00: 17: 93: 4E: 10] is obtained. And the pseudo physical device ID
Access the management unit 13. The pseudo-physical device ID management unit 13 generates a pseudo-physical device ID [July] that can be uniquely assigned to the MAC address of the device 1a (to confirm the description, an English word of a month name, for example, January, February, etc.).
y, etc. are used as pseudo physical device IDs). At that time, as described above, the MAC address before generation [FF: 00: 17:
93: 4E: 10] and the pseudo physical device ID [July] after generation
Pseudo-pseudo physical device ID table 19 uniquely associated
Registered in. The pseudo physical device ID management stub 11
The ID [July] is sent to the business application unit 9. The business application unit 9 identifies the device 1a based on the transmitted ID [July], and provides a service or the like depending on the ID to the device 1a that has issued the request.

FIG. 8 shows the correspondence between the MAC address of each active device and the pseudo physical device ID.

The above-described operation is performed on other active devices, so that the correspondence between the MAC address of each active device and the pseudo physical device ID is as follows.
For example, the correspondence is as shown in FIG. in this way,
A system using a pseudo-physical device ID that permanently and uniquely corresponds to a MAC address allows a computer to be permanently and uniquely identified. The advantages of the present system will be specifically described using the following two cases as examples.

Case 1: Device 1a in state 1 (FIG. 2)
Is assigned to another device 1b in state 2 (FIG. 4),
A case where a request is issued from another device 1b to the business server (that is, a request from a different device has the same IP address) Case 2:
IP address [172.17.0.6 assigned in state 1 (FIG. 2)
7] is assigned to the same device 1a in state 2 (FIG. 4), and a request is issued from the same device 1a to the business server (that is, from a different IP address). First, referring to FIG. 9, in case 1, the IP address [172.17.0.67]
Will be described below.

The operation of giving an IP address is as described with reference to FIG. That is, in the state 2, the device 1b which is in the operating state requests the DHCP daemon 3 to assign an IP address and at the same time, the MAC address [FF: 00: 17: 92: E0:
2A]. The DHCP daemon 3 returns the IP address [172.17.0.67] that can be assigned in the state 2 to the device 1b. This returned IP address [172.17.0.67]
Is assigned to the device 1a in the state 1, but since the device 1a is in the non-operational state, it can be assigned and is assigned to the device 1b.
The new correspondence between the MAC address and the IP address of the device 1b is registered in the ARP table 11. Such an operation is performed for all the active devices in the state 2, and as described above, the MAC of each device is
The correspondence between addresses and IP addresses is, for example, as shown in FIG.

Next, referring to FIG. 10, in this state 2,
An operation will be described in which when a request is issued from the device 1b to the business server 5, it is identified that the request is from a device 1b different from that in the state 1.

When a request is issued from the device 1b to the business server 5, the business application unit 9 cannot recognize at the time of receiving the request that the request is from a device different from the device 1a. Therefore, the pseudo physical device ID management stub 11 obtains the IP address [172.17.0.67] from the ARP table in which the correspondence between the MAC address and the IP address is registered as described above.
Address of device 1b corresponding to [FF: 00: 17: 92: E
0: 2A], and accesses the pseudo physical device ID management unit 13. The pseudo physical device ID management unit 13 sends the
Pseudo-physical device I that can be uniquely assigned to MAC address
Generate D [May]. Generated ID [May] and M before generation
The AC address [FF: 00: 17: 92: E0: 2A] is uniquely associated with the pseudo physical device ID table 1 as in the description of FIG.
9 is registered. The generated ID is sent to the business application unit 9 and identified as the device 1b based on the ID.

FIG. 11 shows the correspondence between the MAC address and the pseudo physical device ID.

The above-described operation is performed for each operating device in this state 2, so that the correspondence between the MAC address and the pseudo physical device ID becomes, for example, the correspondence shown in FIG. Become. FIG.
Comparing (State 1) with FIG. 11 (State 2), it is understood that the unique correspondence between the MAC address and the pseudo physical device ID has not changed as described above.

By such an operation, in various states, different devices are given the same IP address,
Even if the request is made from that different device, the MAC
By using a pseudo physical device ID whose correspondence with an address does not change permanently, it is possible to accurately and uniquely identify a device. Thereby, the user can receive the service as requested. Of course, this effect can be similarly obtained even in the case of a request from the same device to which a different IP address is assigned before and after the change of the operation state. Hereinafter, this will be described using Case 2 as an example.

FIG. 12 shows a case 2 in which device 1
This shows how an IP address is assigned to a.

In the state 2, the device 1a is in the operating state as in the state 1. However, since the IP address given by the DHCP daemon 3 is assigned by an appropriate algorithm according to the operation status of another device, an IP address [172.17.0.68] different from that in the state 1 is returned in this state. . Then, as in the case of FIG. 6, the MAC address and the IP address of the device 1a in the state 2
The new correspondence of the address is registered in the ARP table.

Next, referring to FIG. 13, in this state, a request is issued from the device 1a to the business server 5,
An operation will be described in which, even when an IP address [172.17.0.68] different from the state 1 is recognized, the request is identified as a request from the device 1a.

When a request is issued from the device 1a to the business server 5, the business application unit 9 cannot recognize at this point that the request is from the device 1a. Therefore, the pseudo physical device ID management stub 11 obtains the IP address [172.1] from the correspondence between the MAC address and the IP address registered in the ARP table in FIG.
7.0.68] MAC address of device 1a [FF: 00:
17: 93: 4E: 10] and accesses the pseudo physical device ID management unit 13. Pseudo physical device ID management unit 13
Returns the pseudo physical device ID [July] corresponding to the MAC address of the already registered device 1a from the pseudo physical device ID table 19 to the pseudo physical device ID stub 11. The returned ID is sent to the business application unit 9, and the device 1a is identified based on the ID.

By such an operation, in various states,
Even if a request is issued from the same device to which a different IP address is assigned, it is possible to accurately and uniquely identify the request.

As described above, in the above system configuration, individual devices can be used not only in a network to which an IP address is statically assigned, but also in a network to which an IP address is dynamically assigned using DHCP. , Can be uniquely identified permanently. Thus, for example, in a store or the like, if it is desired to separate services that can be used mainly by terminals handled by employees and services that can be mainly used by terminals handled by customers, the same IP address can be set under the same DHCP management. Resources can be used effectively. Further, a specific service limited to only a specific terminal group can be provided. For example, providing services that require authority to execute, such as electronic settlement processing, only to certain terminals, or providing services that use them only to devices with card readers Can be realized. On the other hand, pseudo physical device ID
If there is a service request from a device with a MAC address that is not registered in the table, it is considered that the device has been newly connected to the network, and the MAC address and the generated pseudo-device are added to the pseudo-physical device ID table. The physical device ID is registered. Thereby, it is possible to prevent the connection to the network secretly.

Although some preferred embodiments of the present invention have been described above, these are merely examples for describing the present invention, and are not intended to limit the scope of the present invention to only these examples. . The present invention can be implemented in other various forms. For example, in this embodiment, DHCP is used.
Although described in a TCP / IP network, it can be used in other computer networks.

[Brief description of the drawings]

FIG. 1 is a diagram illustrating a relationship between an IP address and a logical host name that uniquely corresponds to each other;

FIG. 2 shows an IP address dynamically assigned to each device in an active state at a certain point in time.
The figure which shows the correspondence of a MAC address.

FIG. 3 is a diagram showing a correspondence relationship between a MAC address to which an IP address is assigned and a logical host name in the state shown in FIG. 2;

FIG. 4 is a diagram showing a correspondence relationship between an IP address and a MAC address dynamically assigned to each device in an active state when the state of a plurality of devices is changed from the state in FIG. 2; .

FIG. 5 is a diagram showing a correspondence relationship between a MAC address to which an IP address is assigned and a logical host name in the state in FIG. 4;

FIG. 6 is a diagram showing a state where an IP address is dynamically assigned by DHCP in one embodiment of the present invention.

FIG. 7 is an exemplary view showing how a pseudo physical device ID is obtained from an IP address in the embodiment.

FIG. 8 is a diagram showing the correspondence between the MAC address of each active device and the pseudo physical device ID.

FIG. 9 is a diagram showing a state in which an IP address is dynamically assigned by DHCP in case 1;

FIG. 10 is a diagram showing a state in which a pseudo physical device ID is obtained from an IP address in case 1.

FIG. 11 is a diagram showing a correspondence relationship between a MAC address and a pseudo physical device ID.

FIG. 12 is a diagram showing a state in which an IP address is dynamically assigned by DHCP in case 2;

FIG. 13 is a diagram showing a state in which a pseudo physical device ID is obtained from an IP address in case 2.

[Explanation of symbols]

 DESCRIPTION OF SYMBOLS 1 Device 3 DHCP daemon 5 Business server 7 IP lease table 9 Business application part 11 ARP table 13 Network stack 15 Pseudo physical device ID management stub 17 Pseudo physical device ID management part 19 Pseudo physical device ID table

Claims (11)

[Claims] 1. connected to a computer network,
One or more devices having a permanently determined hardware address and a dynamically assigned logical address; a business server connected to the computer network; and a node provided on any node on the computer network. A pseudo physical device ID management unit that uniquely assigns a pseudo physical device ID to the device, wherein the business server has an ARP table in which a correspondence relationship between the hardware address and the logical address is registered. A network stack, receiving a logical address included in a communication signal from the device, transmitting the logical address to the pseudo physical device ID management unit, and transmitting the pseudo address corresponding to the transmitted logical address from the pseudo physical device ID management unit; Receives the physical device ID and, based on the received pseudo physical device ID, And a business application unit for identifying the device, wherein the pseudo physical device ID management unit is a pseudo physical device ID table in which the hardware address of the device and the pseudo physical device ID are registered in correspondence with each other. Having the logical address of the device from the business application unit, obtain the hardware address corresponding to the logical address from the ARP table,
A pseudo-physical device ID that can be uniquely assigned to the hardware address is generated, and a correspondence between the hardware address and the pseudo-physical device ID is registered in the pseudo-physical device ID table. A computer identification system for sending the pseudo physical device ID corresponding to the hardware address to the business application unit. 2. A hardware address of the device in an operating state is received, an assignable logical address is assigned to the device, and a correspondence relationship between the received hardware address and the assigned logical address is registered. 2. The computer identification system according to claim 1, further comprising a DHCP daemon having a logical address lease table. 3. The pseudo physical device ID management unit is provided at a predetermined node of the network outside the business server, and the business server is provided between the business application unit and the network stack. device
A pseudo physical device ID management stub communicably connected to an ID management unit, wherein the pseudo physical device ID management stub receives the logical address from the business application unit and receives the ARP
From the table, obtain the hardware address corresponding to the logical address and send it to the pseudo physical device ID management unit, and receive the pseudo physical device ID from the pseudo physical device ID management unit, and The computer identification system according to claim 1, which is sent to: 4. Connected to a computer network,
Receives the logical address included in a communication signal from one or more devices having a permanently determined hardware address and a dynamically assigned logical address, and generates a pseudo-physical device ID corresponding to the logical address. On the basis of,
A business application unit for identifying the device, a network stack having an ARP table in which a correspondence relationship between the hardware address and the logical address of the device is registered, and the hardware address and the pseudo physical device ID. Having a pseudo physical device ID table correspondingly registered, receiving the logical address from the business application unit, acquiring a hardware address corresponding to the logical address from the ARP table, and acquiring the acquired hardware address A pseudo-physical device ID that can be uniquely assigned to the device, registers the correspondence between the hardware address and the pseudo-physical device ID in the pseudo-physical device ID table, and stores the pseudo-physical device ID in the business application unit. Pseudo device ID to send to A business server including a management unit. 5. The pseudo physical device ID management unit is provided in a predetermined node of the network outside the business server, and the pseudo physical device ID management unit is provided between the business application unit and the network stack. A pseudo physical device ID management stub communicably connected, the pseudo physical device ID management stub receives the logical address from the business application unit, and receives the ARP
From the table, obtain the hardware address corresponding to the logical address and send it to the pseudo physical device ID management unit, and receive the pseudo physical device ID from the pseudo physical device ID management unit, and 5. The business server according to claim 4, which is sent to: 6. A pseudo physical device ID that is registered in correspondence with one or more hardware addresses permanently assigned to one or more devices connected to a computer network and a pseudo physical device ID assigned to the hardware address. Having an ARP table that receives the logical address of the device to be identified and registers the correspondence between the hardware address and the logical address dynamically assigned to the device, Obtain a hardware address corresponding to a logical address, generate a pseudo-physical device ID that can be uniquely assigned to the hardware address, and calculate the correspondence between the hardware address and the pseudo-physical device ID using the pseudo-physical device. Before registering in the ID table and assigning it to the device to be identified Pseudo physical device ID management unit for outputting a pseudo physical device ID. 7. Connected to a computer network,
A DH connected to the network is connected to one or more devices having a fixed hardware address.
A process in which a CP daemon dynamically assigns a logical address, and a correspondence between a hardware address of the device and the logical address assigned to the device is stored in a network stack in a business server connected to the network. Registering the ARP table of the business server, a business application unit in the business server receives the logical address included in the communication signal sent from the device to the business server, and a pseudo physical device ID existing on the network Sending the received logical address to a management unit, the pseudo physical device ID management unit receives the logical address, acquires a hardware address corresponding to the logical address from the ARP table, and stores the hardware address in the hardware address. Generate a pseudo-physical device ID that can be uniquely assigned, and Registering the correspondence between the hardware address and the pseudo physical device ID in a pseudo physical device ID table, and returning the pseudo physical device ID corresponding to the obtained hardware address to the business application unit; and The part is the pseudo-physical device
Acquiring an ID and identifying the device based on the acquired pseudo physical device ID. 8. Connected to a computer network,
Receiving the logical address corresponding to one or more devices having a permanently determined hardware address and a dynamically assigned logical address; receiving the logical address, and receiving the logical address of the device; A step of acquiring the hardware address corresponding to the logical address from the ARP table in which the correspondence relationship with the hardware address is registered; anda pseudo physical device ID that can be uniquely assigned to the acquired hardware address. A program for causing a computer to execute a step of generating, a step of registering a correspondence between the hardware address and the pseudo physical device ID in a pseudo physical device ID table, and a step of outputting the pseudo physical device ID. A recorded computer-readable recording medium. 9. Connected to a computer network,
Registering a correspondence between the hardware address and the logical address of one or more devices having a permanently determined hardware address and a dynamically assigned logical address; and communication from the device. Receiving the logical address included in the signal, acquiring the hardware address corresponding to the received logical address, generating a pseudo physical device ID that can be uniquely assigned to the acquired hardware address,
A program for causing a computer to execute a step of registering a correspondence relationship between the hardware address and the pseudo physical device ID and a step of identifying the device based on the generated pseudo physical device ID are recorded. Computer readable recording medium. 10. A process for receiving the logical address included in a communication signal from one or more devices having a permanently determined hardware address and a dynamically assigned logical address, connected to a computer network. Sending the received logical address to a pseudo physical device ID management unit provided at any node on the computer network and uniquely assigning a pseudo physical device ID to the device; A computer-readable recording medium recording a program for causing a computer to execute the step of receiving the pseudo physical device ID from an ID management unit and the step of identifying the device based on the received pseudo physical device ID. 11. A correspondence relationship between the hardware address and the logical address of one or a plurality of devices connected to a computer network and having a permanently determined hardware address and a dynamically assigned logical address. Registering, and receiving the logical address from a business application unit that receives the logical address included in the communication signal from the device; and obtaining the hardware address corresponding to the received logical address. Sending the acquired hardware address to the pseudo-physical device ID management unit, which is provided at any node on the computer network and uniquely assigns a pseudo-physical device ID to the device; Receives the pseudo physical device ID from the device ID management unit And the pseudo physical device ID received
And a computer-readable recording medium for recording a program for causing a computer to execute the process of sending the program to the business application unit.