CN113940046B

CN113940046B - Portable terminal system for managing portable terminal having docking station and main unit

Info

Publication number: CN113940046B
Application number: CN201980097335.0A
Authority: CN
Inventors: 长德典宏
Original assignee: Mitsubishi Electric Building Solutions Corp
Current assignee: Mitsubishi Electric Building Solutions Corp
Priority date: 2019-08-23
Filing date: 2019-08-23
Publication date: 2023-06-27
Anticipated expiration: 2039-08-23
Also published as: JP6693608B1; CN113940046A; JPWO2021038618A1; WO2021038618A1

Abstract

Provided is a portable terminal system capable of properly managing a main unit even when a docking unit and the main unit are erroneously connected. A portable terminal system is provided with: a plurality of portable terminals each having a pair of a docking station section and a main section in a detachable manner; a DHCP server that allocates IP addresses to the plurality of main units based on MAC addresses of the plurality of docking units, respectively, in a state where the docking units and the main units, which are paired, of the plurality of portable terminals are connected, respectively; and a management server that determines that the master is a master to be managed when the IP address of the master is an IP address assigned to any master of the plurality of masters by the DHCP server in a state where the docking station and the master are connected.

Description

Portable terminal system for managing portable terminal having docking station and main unit

Technical Field

The present invention relates to a portable terminal system for managing a portable terminal having a docking station section and a main section.

Background

Patent document 1 discloses a portable terminal system. According to this portable terminal system, the location of the portable terminal can be managed.

Prior art literature

Patent literature

Patent document 1: japanese patent laid-open publication No. 2011-18168

Disclosure of Invention

Problems to be solved by the invention

However, a plurality of portable terminals of the same type, in which the docking station section and the main section are detachably provided, may be used in the same area. Even if the portable terminal system described in patent document 1 is applied to this area, the erroneous connection between the docking station portion and the main portion cannot be suppressed. As a result, the master cannot be properly managed.

The present invention has been made to solve the above-described problems. The present invention aims to provide a portable terminal system, which can properly manage a main part even if a docking part and the main part are connected by mistake.

Means for solving the problems

The portable terminal system of the present invention comprises: a plurality of portable terminals each having a pair of a docking station section and a main section in a detachable manner; a DHCP server that allocates IP addresses to the plurality of main units based on MAC addresses of the plurality of docking units, respectively, in a state where the docking units and the main units, which are paired, of the plurality of portable terminals are connected, respectively; and a management server that determines that the master is a master to be managed when the IP address of the master is an IP address assigned to any master of the plurality of masters by the DHCP server in a state where the docking station and the master are connected.

Effects of the invention

According to the present invention, when the IP address of the master is assigned to any master of the plurality of masters by the DHCP server in a state where the docking station and the master are connected, the management server determines that the master is the master to be managed. Therefore, even when the docking station and the main unit are erroneously connected, the main unit can be properly managed.

Drawings

Fig. 1 is a block diagram of a mobile terminal system according to embodiment 1.

Fig. 2 is a flowchart for explaining an outline of an operation of a main unit of a mobile terminal to which the mobile terminal system according to embodiment 1 is applied.

Fig. 3 is a flowchart for explaining an outline of an operation of a management server of the mobile terminal system according to embodiment 1.

Fig. 4 is a flowchart for explaining an outline of an operation of the management server of the mobile terminal system in embodiment 1.

Fig. 5 is a hardware configuration diagram of a main part of a mobile terminal to which the mobile terminal system of embodiment 1 is applied.

Fig. 6 is a flowchart for explaining an outline of the operation of the management server of the mobile terminal system in embodiment 2.

Fig. 7 is a flowchart for explaining an outline of the operation of the management server of the mobile terminal system in embodiment 2.

Fig. 8 is a flowchart for explaining an outline of the operation of the management server of the mobile terminal system in embodiment 2.

Detailed Description

The manner in which the invention can be practiced is illustrated in the accompanying drawings. In the drawings, the same or corresponding portions are denoted by the same reference numerals. The repeated explanation of this portion is appropriately simplified or omitted.

Embodiment 1

In the mobile terminal system of fig. 1, a plurality of mobile terminals 1 are carried by users, respectively. The portable terminal 1 is carried by a maintainer of an elevator, for example. The maintainer performs maintenance work of an elevator, not shown, using the mobile terminal 1.

The plurality of portable terminals 1 have a pair of docking portions 1a and a main portion 1b, respectively. The docking station portion 1a and the main portion 1b are detachably provided to each other.

For example, the docking station portion 1a has a keyboard, a NIC (Network Interface Card: network interface card), and a preliminary battery. The docking station portion 1a stores own identification information. For example, the docking station section 1a stores information of the MAC address of the NIC as identification information of itself.

For example, the main section 1b has a CPU, a memory, a battery, and a liquid crystal panel. The main portion 1b reads the identification information stored in the docking portion 1a at the time of initial startup in a state of being connected to the paired docking portions 1a, and then stores the identification information.

For example, the DHCP server 2 is provided in a maintenance company of an elevator. The DCHP server allocates IP addresses to the plurality of main units 1b based on the MAC addresses of the plurality of docking units 1a in a state where the docking units 1a and the main units 1b, which are paired, are connected to each other in the plurality of portable terminals 1, and then stores information of the IP addresses in the plurality of main units 1b, respectively.

For example, the management server 3 is provided in a maintenance company of an elevator. The management server 3 recognizes the mobile terminals 1 connected to the network, and thereby manages the locations of the plurality of mobile terminals 1. For example, the management server 3 searches the network in the company for the mobile terminal 1 as the management target based on the information of the IP address stored in the main unit 1b in the state where the docking unit 1a and the main unit 1b are connected, and manages the main unit 1b according to a predetermined schedule.

In order to prevent the maintenance person using the master unit 1b from failing to manage the network in the company without returning to the network in the predetermined schedule, the management server 3 may perform management other than the predetermined schedule in response to a request from the master unit 1b.

Next, an outline of the operation of the main unit 1b of the mobile terminal 1 will be described with reference to fig. 2.

In step S1, the main unit 1b determines whether or not the docking unit 1a is connected. When the docking station 1a is not connected in step S1, the main unit 1b performs the operation of step S1. When the docking station 1a is connected in step S1, the main unit 1b performs the operation of step S2.

In step S2, the main unit 1b acquires information of the MAC address from the docking unit 1a. Then, the main unit 1b performs the operation of step S3. In step S3, the main unit 1b determines whether or not the information of the MAC address of the docking unit 1a matches the information of the MAC address stored in itself.

In step S3, when the information of the MAC address of the docking station 1a matches the information of the MAC address stored in the docking station, the main unit 1b ends the operation.

In step S3, when the information of the MAC address of the docking station 1a does not match the information of the MAC address stored in the docking station, the main unit 1b performs the operation of step S4. In step S4, the main unit 1b outputs a warning message to the outside. For example, the main unit 1b causes the liquid crystal panel to display a warning message. For example, the main section 1b generates Beep sound. Then, the main unit 1b ends the operation.

Next, an outline of the operation of the management server 3 when management is performed according to a predetermined schedule will be described with reference to fig. 3.

In step S11, the management server 3 determines whether or not the IP address of the main unit 1b is an IP address allocated by the DHCP server 2 based on the MAC address of the docking unit 1a.

In step S11, when the IP address of the main unit 1b is an IP address assigned by the DHCP server 2 based on the MAC address of the docking unit 1a, the management server 3 performs the operation of step S12. In step S12, the management server 3 determines that the docking station 1a and the main unit 1b are paired. Then, the management server 3 ends the operation.

In step S11, when the IP address of the main unit 1b is not the IP address allocated by the DHCP server 2 based on the MAC address of the docking unit 1a, the management server 3 performs the operation of step S13. In step S13, the management server 3 determines whether or not the IP address of the main unit 1b is an IP address assigned by the DHCP server 2 based on the MAC address of the docking unit 1a different from the docking unit 1a.

In step S13, when the IP address of the main unit 1b is an IP address assigned by the DHCP server 2 based on the MAC address of the docking unit 1a different from the docking unit 1a, the management server 3 performs the operation of step S14. In step S14, the management server 3 determines that the docking station 1a and the main unit 1b are not paired. Then, the management server 3 ends the operation.

In step S13, when the IP address of the main unit 1b is not an IP address assigned by the DHCP server 2 based on the MAC address of the docking unit 1a different from the docking unit 1a, the management server 3 performs the operation of step S15. In step S15, the management server 3 determines that the master 1b is not the master 1b to be managed. Then, the management server 3 ends the operation.

Next, an outline of the operation of the management server 3 when management is performed outside a predetermined schedule in response to a request from the main unit 1b will be described with reference to fig. 4.

In step S21, the management server 3 determines whether the docking station portion 1a is connected. When the docking station 1a is not connected in step S21, the management server 3 performs the operation of step S21. When the docking station 1a is connected in step S21, the management server 3 performs the operation of step S22.

In step S22, the management server 3 determines whether or not the main unit 1b is connected to the docking unit 1a. When the main unit 1b is not connected to the docking unit 1a in step S22, the operation of step S22 is performed. When the main unit 1b is connected to the docking unit 1a in step S22, the operation of step S23 is performed.

The operations of step S23 to step S27 are the same as those of step S11 to step S15 in fig. 3.

According to embodiment 1 described above, the portable terminal 1 has the docking station portion 1a and the main portion 1b. The docking station portion 1a stores own identification information. The main portion 1b is detachably provided to the docking portion 1a. The main portion 1b stores identification information of the paired docking portions 1a. When connected to the docking units 1a, the main unit 1b determines whether or not the docking units 1a are connected to each other based on the result of comparing the identification information of the connected docking units 1a with the identification information stored in the main unit. Therefore, the erroneous connection of the docking portion 1a and the main portion 1b can be suppressed.

When the main unit 1b is connected to a different docking unit 1a from the pair of docking units, a warning message is output to the outside. Therefore, it is possible to notify the user of the portable terminal 1 that the docking station portion 1a and the main portion 1b are erroneously connected.

In the main unit 1b, the stored identification information may be rewritten by an external operation. In this case, erroneous connection determination can be suppressed when the paired docking portions 1a are changed. For example, it is possible to suppress the erroneous connection determination when the paired docking portions 1a are failed or repaired and the identification information of the paired docking portions 1a is changed.

In addition, when the IP address of the master 1b is an IP address assigned by the DHCP server 2 based on the MAC address of the docking unit 1a in a state where the docking unit 1a and the master 1b are connected, the management server 3 determines that the docking unit 1a and the master 1b are paired. Therefore, the state of the portable terminal 1 can be accurately managed.

In a state where the docking station 1a and the main station 1b are connected, the management server 3 determines that the docking station 1a and the main station 1b are not paired when the IP address of the main station 1b is an IP address assigned by the DHCP server 2 based on the MAC address of the docking station 1a different from the docking station 1a. Therefore, the state of the portable terminal 1 can be accurately managed.

In addition, when the IP address of the master 1b is not assigned to any master 1b among the plurality of masters 1b by the DHCP server 2 in the state where the docking station 1a and the master 1b are connected, the management server 3 determines that the master 1b is not the master 1b to be managed. Therefore, the presence of the main portion 1b outside the management object can be grasped.

Next, an example of the main part 1b will be described with reference to fig. 5.

The functions of the main part 1b can be realized by a processing circuit. For example, the processing circuitry has at least one processor 100a and at least one memory 100b. For example, the processing circuit has at least one dedicated hardware 200.

In the case of a processing circuit having at least one processor 100a and at least one memory 100b, the functions of the main part 1b are implemented by software, firmware or a combination of software and firmware. At least one of the software and the firmware is referred to as a program. At least one of the software and firmware is stored in at least one memory 100b. The at least one processor 100a reads out and executes the program stored in the at least one memory 100b, thereby realizing the functions of the main part 1b. The at least one processor 100a is also referred to as a central processing unit, a processing unit, an arithmetic unit, a microprocessor, a microcomputer, a DSP. For example, the at least one memory 100b is a nonvolatile or volatile semiconductor memory such as RAM, ROM, flash memory, EPROM, EEPROM, etc., magnetic disk, floppy disk, optical disk, compact disk, mini disk, DVD, etc.

In the case of processing circuitry having at least one dedicated hardware 200, the processing circuitry is implemented, for example, by a single circuit, a composite circuit, a programmed processor, a parallel programmed processor, an ASIC, an FPGA, or a combination thereof. For example, the functions of the main part 1b are realized by processing circuits, respectively. For example, the functions of the main part 1b are unified by a processing circuit.

Regarding the functions of the main part 1b, one part may be realized by dedicated hardware 200 and the other part may be realized by software or firmware. For example, the function of determining whether or not the pair of docking units 1a is connected is realized by a processing circuit as the dedicated hardware 200, and the function other than the function of determining whether or not the pair of docking units 1a is connected is realized by at least one processor 100a reading and executing a program stored in at least one memory 100b.

Thus, the processing circuit realizes the functions of the main part 1b by hardware 200, software, firmware, or a combination thereof.

Although not shown, each function of the DHCP server 2 may be realized by a processing circuit similar to that of the main portion 1b. The functions of the management server 3 may be realized by the same processing circuit as that for realizing the functions of the main part 1b.

Embodiment 2

Fig. 6 is a flowchart for explaining an outline of the operation of the management server of the mobile terminal system in embodiment 2. The same or corresponding parts as those of embodiment 1 are denoted by the same reference numerals. The description of this part is omitted.

In embodiment 2, the management server 3 manages whether or not the master 1b is the master 1b to be managed based on the information of the IP address stored in the master 1b in a state where the docking station 1a and the master 1b are connected.

In step S31, the management server 3 determines whether or not the IP address of the main unit 1b is an IP address allocated by the DHCP server 2 based on the MAC address of the docking unit 1a.

In step S31, when the IP address of the main unit 1b is an IP address assigned by the DHCP server 2 based on the MAC address of the docking unit 1a, the management server 3 performs the operation of step S32. In step S32, the management server 3 determines that the master 1b is the master 1b to be managed. Then, the management server 3 performs the operation of step S33. In step S33, the management server 3 performs the inspection of the main unit 1b by a function such as intel AMT (intel active management technology), and retains a log indicating that the management is appropriate. Then, the management server 3 ends the operation.

In step S31, when the IP address of the main unit 1b is not the IP address allocated by the DHCP server 2 based on the MAC address of the docking unit 1a, the management server 3 performs the operation of step S34. In step S34, the management server 3 determines whether or not the IP address of the main unit 1b is an IP address assigned by the DHCP server 2 based on the MAC address of the docking unit 1a different from the docking unit 1a.

In step S34, when the IP address of the main unit 1b is an IP address assigned by the DHCP server 2 based on the MAC address of the docking unit 1a different from the docking unit 1a, the management server 3 performs the operation of step S35. In step S35, the management server 3 determines that the master 1b is the master 1b to be managed. Then, the management server 3 performs the operation of step S36. In step S36, the management server 3 performs a check of the main unit 1b by a function such as intel AMT, and retains a log indicating that management is inadequate. Then, the management server 3 ends the operation.

In step S34, when the IP address of the main unit 1b is not an IP address assigned by the DHCP server 2 based on the MAC address of the docking unit 1a different from the docking unit 1a, the management server 3 performs the operation of step S37. In step S37, the management server 3 determines that the master 1b is not the master 1b to be managed. Then, the management server 3 ends the operation without checking the main unit 1b.

Next, an outline of the operation of the management server 3 when management is performed outside a predetermined schedule in response to a request from the main unit 1b will be described with reference to fig. 7 and 8.

Fig. 7 and 8 are flowcharts for explaining an outline of the operation of the management server of the mobile terminal system according to embodiment 2.

In step S41, the management server 3 determines whether the docking station portion 1a is connected. When the docking station 1a is not connected in step S41, the management server 3 performs the operation of step S41. When the docking station 1a is connected in step S41, the management server 3 performs the operation of step S42.

In step S42, the management server 3 determines whether or not the main unit 1b is connected to the docking unit 1a. When the main unit 1b is not connected to the docking unit 1a in step S42, the operation of step S42 is performed. When the main unit 1b is connected to the docking unit 1a in step S42, the operation of step S43 is performed.

The operations of step S43 to step S49 are the same as those of step S31 to step S37 of fig. 6.

According to embodiment 2 described above, when the IP address of the master 1b is an IP address assigned to any master 1b among the plurality of masters 1b by the DHCP server 2 in a state where the docking station 1a and the master 1b are connected, the management server 3 determines that the master 1b is the master 1b to be managed. Therefore, even when the docking station portion 1a and the main portion 1b are erroneously connected, the main portion 1b can be properly managed.

For example, when the IP address of the master 1b is an IP address assigned by the DHCP server 2 based on the MAC address of the docking station 1a in a state where the docking station 1a and the master 1b are connected, the management server 3 determines that the master 1b is the master 1b to be managed. When the paired docking station sections 1a and main sections 1b are connected, the main sections 1b can be appropriately managed.

For example, when the IP address of the master 1b is an IP address assigned by the DHCP server 2 based on the MAC address of the docking station 1a different from the docking station 1a in a state where the docking station 1a and the master 1b are connected, the management server 3 determines that the master 1b is the master 1b to be managed. When the unpaired docking station 1a and the main unit 1b are connected, the main unit 1b can be properly managed.

For example, when the IP address of the master 1b is not assigned to any master 1b among the plurality of masters 1b by the DHCP server 2 in a state where the docking station 1a and the master 1b are connected, the management server 3 determines that the master 1b is not the master 1b to be managed. Therefore, the presence of the main portion 1b outside the management object can be grasped.

Industrial applicability

As described above, the portable terminal system of the present invention can be used for a system for managing a portable terminal.

Description of the reference numerals

1: a portable terminal; 1a: a docking station section; 1b: a main part; 2: a DHCP server; 3: a management server; 100a: a processor; 100b: a memory; 200: hardware.

Claims

1. A portable terminal system is provided with:

a plurality of portable terminals each having a docking station section and a main section storing identification information stored in the docking station section, the portable terminals being detachably attached to the main section;

a DHCP server that allocates IP addresses to the plurality of main units based on MAC addresses of the plurality of docking units, respectively, in a state in which the docking units and the main units storing the identification information stored in the docking units are connected to each of the plurality of portable terminals; and

and a management server that determines that the master is a master to be managed when the IP address of the master is an IP address allocated by the DHCP server based on the MAC address of the docking station in a state where the docking station and the master are connected according to a predetermined schedule, and determines that the master is a master to be managed when the IP address of the master is an IP address allocated by the DHCP server based on the MAC address of the docking station when the master is connected to the docking station other than the predetermined schedule.

2. The portable terminal system according to claim 1, wherein,

the management server determines that the master is the master to be managed when the IP address of the master is an IP address assigned by the DHCP server based on the MAC address of the docking different from the docking in a state where the docking and the master are connected.

3. The portable terminal system according to claim 1 or 2, wherein,

the management server determines that the master is not a master to be managed when the IP address of the master is not an IP address assigned to any master of the plurality of masters by the DHCP server in a state where the docking station and the master are connected.