JP7530865B2 - Terminal setup method, program, terminal management method, and terminal management system - Google Patents

Description

Article 30, paragraph 2 of the Patent Act applies 1. [Publisher] VAIO Corporation [Published address] https://news.vaio.com/sokowaku_201127/ [Press release name] Launch of "Sokowaku", which realizes safe and comfortable remote access anywhere [Published date] November 27, 2020 2. [Publisher] VAIO Corporation [Published address] https://news.vaio.com/sokowaku_210129/ [Press release name] Launch of "Sokowaku Secure RDP Connect", which allows you to build a safe telework environment from scratch in as little as five business days [Published date] January 29, 2021

The present invention relates to a terminal setup method, a program, a terminal management method, and a terminal management system.

Conventionally, when a terminal such as a personal computer (PC) was purchased, its setup was carried out by a terminal manager, such as an information equipment specialist, who would insert a USB memory stick containing setup data, software, etc. into the terminal, install it, and set up each terminal individually.
Some telecommunications companies issue license keys for connecting to the communication lines operated by the company, and allow terminals having the license keys to connect to the communication lines, thereby enhancing security. Such license keys are, for example, a combination of alphanumeric characters, and are different for each terminal. When using a company's communication lines, a terminal administrator who manages the terminals assigns (stores) different license keys to each terminal, and sets up each terminal so that it can connect to the communication lines.
In addition, a table software was used to input the serial number of each terminal, the license key for that terminal, etc., to create a management table for managing multiple terminals, and the terminals were managed based on this management table.
In addition, if a terminal administrator wishes to change the state of a terminal that is connected to a communication line that requires authentication to a state that does not allow connection for some reason, the terminal administrator can change the state to the state that does not allow connection by contacting the communication company.
Technological development regarding such setups has not progressed.

However, with the development of the information society and the spread of terminals, the number of terminals that terminal administrators manage is increasing dramatically. Also, license keys are becoming more and more complicated in order to improve security.
In this changing environment, if you set up a terminal using traditional methods, there is a risk that the terminal you are setting up will be assigned incorrect alphanumeric characters (license key), resulting in an unsafe setup.
Furthermore, there is a risk that incorrect alphanumeric characters or the like will be entered into the management table for managing the terminals, resulting in terminal management being based on the incorrect management table, making terminal management difficult.
In addition, if a terminal administrator wishes to stop communication involving authentication of a certain terminal (for example, to change the state from connected to unconnectable), it is necessary to contact the telecommunications company, making it difficult to make the change.

The present invention aims to achieve at least one of the following: reduce the risk of an insecure setup due to an incorrect alphanumeric character or the like (license key) being assigned to the terminal to be set up; facilitate the management of terminals; and make it possible to change the connection status of a terminal to a communication line without the need to contact a communication carrier.

[1] The terminal setup method of the present invention is a terminal setup method when a license key for authentication is required to connect a terminal belonging to a specified group to a specified communication line, and is characterized in that it includes the steps of: creating an account for the group on a cloud server; storing a specified number of license keys for the account on the cloud server; acquiring individual information of the terminal from the terminal by the cloud server and storing the individual information on the cloud server; applying an unused license key among the license keys to the terminal to which no license key has been applied, and making it an individual license key linked to the individual information by the cloud server; and installing, based on the individual information, connection software for authenticating the terminal, connecting to the communication line, and performing encrypted communication, from the cloud server to the terminal.

According to the terminal setup method of the present invention, individual information of the terminal is acquired by the cloud server in the individual information acquisition step, an unused license key is applied to the terminal in the individual information linking step to become an individual license key linked to the individual information, and the connection software is installed on the terminal based on the individual information in the installation step. This reduces the risk of a safe setup being performed due to an incorrect alphanumeric character (license key) being assigned to the terminal to be set up.

[5] The program of the present invention is a program for causing a computer to execute a terminal setup, and causes the computer to realize an individual information acquisition function in which the cloud server acquires individual information of the terminal from the terminal and stores the information in the cloud server, an individual information linking function in which the cloud server applies an unused license key among license keys to the terminal to which no license key has been applied, making it an individual license key linked to the individual information, and an installation function in which the cloud server installs connection software for connecting the terminal to the communication line for encrypted communication, into the terminal based on the individual information.

With this type of program, the cloud server obtains individual information from the terminal and applies an unused license key to a terminal to which a license key has not been applied, creating an individual license key linked to the individual information. Based on the individual information, the connection software is installed on the terminal from the cloud server. This reduces the risk of a safe setup being performed due to an incorrect alphanumeric character (license key) being assigned to the terminal to be set up.

[6] The terminal management method of the present invention is a method for managing terminals that belong to a specified group and to which a license key for connecting to a specified communication line can be applied, and is characterized in that it includes a setup step of setting up one or more of the terminals using any of the setup methods of claims 1 to 4, a management portal creation step of creating, on a management portal, management information indicating individual information of the terminal, the application status of the license key to the terminal, and, if the license key is applied to the terminal, the license key and an authentication connection status, and a management portal display step of displaying the management portal by accessing the management portal from the management terminal.

With this type of device management method, the device is set up and a management portal is created on the cloud server, so that the management portal can be displayed on the management device, making it easier to manage the device.

[9] The terminal management system of the present invention is a management system for terminals that belong to a specified group and to which an authentication license key for connecting to a specified communication line can be applied, and is characterized in that it comprises a cloud server that creates a management portal showing individual information of the terminal, the application status of the license key to the terminal, and, when the license key is set up and applied, the license key and the authentication connection status, and a management terminal that manages the terminals, wherein the management terminal is capable of specifying the terminal to which the license key is to be applied on the management portal, accessing the cloud server to display the management portal, and changing the authentication status of a specified terminal to an authentication suspended state on the management portal, and the cloud server is configured to prepare connection software that is installed on the terminal specified by the management terminal and enables the terminal to connect to the communication line and perform encrypted communication.
The present invention is characterized in that it is configured as follows.

In such a terminal management system, a management terminal that manages the terminals can access the cloud server and display a management portal, making it possible to easily manage the terminals.
In addition, the management terminal can change the authentication status of a specific terminal to an authentication suspended state on the management portal, making it possible to change the connection status of the terminal to the communication line without having to contact the communication carrier.

1 is a diagram for explaining an overview of a management system 1 according to a first embodiment. 2 is a diagram for explaining a management portal 20 of the management system 1 according to the first embodiment. FIG. 4 is a diagram for explaining a processing flow of registration of a license key 21 and the like in the management system 1 according to the first embodiment. 5 is a diagram for explaining a process flow for setting up a terminal 4 in the management system 1 according to the first embodiment. FIG. FIG. 1 is a diagram for explaining the hardware configuration of a management system 1 according to a first embodiment. 5 is a diagram for explaining a process flow for connecting or disconnecting a terminal 4 to a leased line 6 in the first embodiment. FIG. 6 is a diagram for explaining the processing flow of “temporarily suspend authentication” of the management portal 20 in the first embodiment. FIG. FIG. 11 is a diagram for explaining a second embodiment.

The terminal setup method, program, terminal management method, and terminal management system of the present invention will be described below with reference to Figures 1 to 8. Note that each figure described below is a schematic diagram that simplifies the actual configuration, processing, method, etc.

[Embodiment 1]
A method for setting up a terminal 4, a program, a method for managing the terminal 4, and a management system 1 for the terminal 4 according to the first embodiment will be described with reference to FIGS.

[Management system 1 for terminal 4]
FIG. 1 is a diagram for explaining an overview of a management system 1 for a terminal 4 according to the first embodiment.
The management system 1 for a terminal 4 shown in Fig. 1 is a management system 1 for a terminal 4 that belongs to a predetermined group (e.g., company A) and is applicable to a license key 21 for authentication to connect to a predetermined communication line (dedicated line 6, wired or wireless). The management system 1 includes a cloud server 2 and a management terminal 3 that manages the terminal 4. The management system 1 is configured as follows.
The cloud server 2 creates a management portal 20. The management portal 20 indicates individual information 22 of the terminal 4, the application status of the license key 21 to the terminal 4, and the authentication connection status of the terminal 4. In addition, when the terminal 4 is set up and the license key 21 is applied, the license key 21 is also displayed.
The management terminal 3 is capable of specifying the terminal 4 to which the license key 21 is to be applied on the management portal 20, accessing the cloud server 2 to display the management portal 20, and changing the authentication status of a specific terminal 4 to an authentication suspended state on the management portal 20.
Cloud server 2 is installed on four terminals designated by management terminal 3, and prepares connection software for terminal 4 to connect to a communication line (dedicated line 6) and perform encrypted communication.

The cloud server 2 may be configured as a three-tier architecture consisting of a web server, an application server, and a database server, in which the web server accepts requests from users (such as the management terminal 3), the application server processes the requests according to the users' requests, and the database server stores and manages data.
A more detailed explanation will be given with reference to FIG.

[Cloud Server 2]
In this specification, "cloud server 2" refers to a server that performs cloud computing. The cloud server 2 may be composed of a web server, an application server (also called a web application server), and a database server. In this case, the web server accepts requests from users (such as the management terminal 3), the application server processes the requests according to the users' requests, and the data server stores and manages the data.
As described above, the cloud server 2 creates the management portal 20. It also acquires individual information 22 from the terminal 4. It also manages the license key 21. It prepares software for setting up the terminal 4. It also prepares connection software for connecting the terminal 4 to the communication line (dedicated line 6).

[Management Portal 20]
The "management portal 20" is a tool (software, service) for managing terminals, and is displayed on the Internet, such as a website. It is created, updated, etc. by the cloud server 2. It can be accessed from the management terminal 3 to display it, and some operations can be performed. The data of the management portal 20 is stored in the cloud server 2.
As described above, the terminal 4 is managed using the management portal 20. In the management portal 20, the individual information 22 and license key 21 of the terminal 4 are managed, and authentication permission settings of the terminal 4 are performed.

Fig. 2 is a diagram for explaining the management portal 20 of the management system 1 according to the first embodiment. Fig. 2 shows an example of the configuration of the management portal 20. The management portal 20 is for managing terminals 4 of a specific group (company A) for which an account for that group has been created in the management system 1.
On the left side of the management portal 20, there is provided a "Terminal No." field for the numbers of terminals 4. "Group name" is the name of the group into which each terminal 4 is classified according to ownership, use, etc. "IP address" will be described later.

The individual information 22, license key 21, etc. of each terminal 4 are displayed in a row direction (horizontal direction), and each terminal 4 is displayed in a column direction (vertical direction).
The "individual information 22" is information that identifies the individual terminal. In addition to the terminal name, manufacturer, and model number, if a SIM (Subscriber Identity Module) card is inserted in the terminal 4, SIM card information is also included.
The "license key 21" is given as a connection license to the dedicated line 6, and is license information given to each terminal 4 one by one. The license key 21 (authentication license key) is, for example, license information (authentication key information) that combines alphanumeric characters, symbols, etc., and is different for each terminal 4. Company A purchases one or more license keys 21 from the operator of the dedicated line 6 according to the number of terminals 4. If the number of license keys 21 is the same as the number of terminals 4, the license keys 21 are assigned to all terminals 4 without excess or deficiency, but the number does not necessarily have to be the same and may be more than the number of terminals. The operator of the dedicated line is basically a different operator from the terminal management service operator, but may be the same operator.
The "individual license key 23" is an integration of the license key 21 and the individual information 22 (the two are linked together).

The "License key assigned" field indicates whether or not a license key for connecting to the dedicated line 6 has been assigned to the terminal 4. If a license key 21 has not been assigned to the terminal 4, the license key 21 field is blank. If a license key has not been assigned to the terminal 4, "Not assigned" is displayed.

The "Connection Setting Type" column indicates the type when connecting the terminal 4 to the leased line 6. For example, it indicates setting information such as individual settings due to the internal network of company A, whether to automatically connect to the leased line 6 when the terminal 4 is started, or whether to connect manually.
Authentication is information for the terminal 4 to be authenticated by the authentication permission device 7. The "authentication suspension setting" field is normally set to "do not suspend," but in the event that the terminal 4 is stolen, it can be set to "suspend authentication" by operating the management terminal 3. When the authentication suspension is set to "suspend authentication," the management portal 20 stops the authentication of the terminal 4 in question for the authentication permission device 7, and cuts off the connection to the dedicated line 6.

The "IP address" column shows the IP address assigned to each terminal 4. When the terminal 4 is connected to the dedicated line 6, communication etc. is performed using this IP address in the virtual network adapter.

[Relationship between cloud server 2, management terminal 3, and terminal 4 (overview)]
Returning to FIG. 1, the relationship between the cloud server 2, the management terminal 3, and the terminal 4 will be outlined.
When the management terminal 3 requests the cloud server 2 to provide management information of the terminal 4, the cloud server 2 provides the management information of the terminal 4 to the management terminal 3. Specifically, the management portal 20 is displayed on the management terminal 3.
Furthermore, when the management terminal 3 makes a setup request for the terminal 4 to the cloud server 2, the cloud server 2 provides the management terminal 3 with setup software for the terminal 4. The setup software includes connection software for connecting the terminal 4 to the dedicated line 6.
The administrator of the terminal 4 installs the setup software and connection software provided to the management terminal 3 from the cloud server 2 into a specific terminal 4 .
At this time, the cloud server 2 provides a license key 21 to the terminal 4 to be set up, while collecting individual information 22 of the terminal 4 .

An authentication permission device 7 is provided between a communication line 5 (wired or wireless) to which a terminal 4 is connected and a dedicated line 6. A master of a license key 21 is stored in the authentication permission device 7. The authentication permission device 7 cooperates with the cloud server 2 to determine whether or not to authenticate a specific terminal 4, and connects to the dedicated line 6 if the terminal 4 is authenticated.
The dedicated line 6 is connected to a base of a predetermined group. The dedicated line 6 is connected to a base connection device 61 at the base (head office) of company A, and is further connected to a server 62 within the base, such as a data server or a mail server, via a communication line 63 within the base. The terminal 4 is authenticated by the authentication permission device 7, and is then connected to the server 62 within the group base, such as a data server, via the dedicated line 6.

[Registration of license key 21, etc.]
The registration of the license key 21 will be described with reference to FIG.
FIG. 3 is a diagram for explaining a processing flow of registration of the license key 21 and the like in the management system 1 according to the first embodiment.
When a certain group (e.g., company A) wishes to manage multiple terminals 4 using the cloud server 2 (management portal 20), it applies for the service to a terminal management service provider. The terminals 4 to be managed are terminals 4 that obtain a connection license to the dedicated line 6 from the operator of the dedicated line 6 and communicate using the highly secure dedicated line 6.

An account for a specific group (company A) is created on the cloud server 2 (management portal 20) by the terminal management service company that has applied for the service (step 101).

Next, a predetermined number of license keys 21 (the number of license keys 21 purchased by company A) for company A's account are stored in the cloud server 2 (management portal 20) by the terminal management service provider (step 103).

Furthermore, the cloud server 2 (management portal 20) may store communication application (software) setting information (setting specifications, corresponding to the connection setting types in FIG. 2) for company A's account by a terminal management service provider.
The communication application setting information for the account of company A is a specification unique to company A. For example, it is setting information such as individual settings due to the internal network of company A, and whether to automatically connect to the dedicated line 6 or manually connect when the connection software (installed on the terminal 4) to the dedicated line 6 is executed on the terminal 4.
The setting information is not limited to one. A plurality of pieces of setting information may be used. For example, the plurality of pieces of setting information may be types T1, T2, and T3, where type T1 is a manual connection, type T2 is an automatic connection in which only communication to company A passes through the dedicated line 6, and type T3 is an automatic connection in which the enhanced security setting of the terminal 4 is enabled.

[set up]
"Setup" refers to putting the terminal 4 into a state in which it can be authenticated by the authentication permission device 7 (e.g., an authentication server). Specifically, it refers to applying the license key 21 to a specific terminal 4 and installing connection software (authentication software) on that terminal 4. The connection software is software that enables the terminal 4 to be authenticated by the authentication permission device 7 and to connect to the dedicated line 6.
When a specific terminal 4 is to be connected to the leased line 6, the connection software installed in the terminal 4 is launched and an authentication request is made to the authentication permission device 7. The authentication permission device 7 determines whether or not authentication is possible by referring to the license key 21 or individual license key 23 stored in the terminal 4. When the terminal 4 is authenticated by the authentication permission device 7, it becomes possible for the terminal 4 to connect to the leased line 6 (virtual closed communication network).

The setup of the terminal 4 will be described with reference to FIG.
FIG. 4 is a diagram for explaining a process flow for setting up the terminal 4 in the management system 1 according to the first embodiment.
In order to manage the terminal 4 using the management portal 20, it is necessary to set up the terminal 4. The terminal 4 is a terminal owned or used by company A, permitted to be used by employees of company A, and used by the employees under their accounts.
Therefore, the administrator of terminal 4 (for example, the information equipment administrator of company A) accesses the cloud server 2 (management portal 20) from the management terminal 3 (step 201). The administrator has an administrator account and is able to access the cloud server 2 (management portal 20). The management terminal 3 is a terminal used by the administrator with that account. The terminal 4 may be a dedicated terminal for use by the administrator, or may be any of the terminals 4. When the administrator uses the terminal 4 with that account, the terminal 4 becomes the management terminal 3.
The management terminal 3 and the terminal 4 do not necessarily have to be personal computers, but the first embodiment is an embodiment in which they are personal computers.

The administrator requests the download of setup software (e.g., software in file form, including necessary software such as connection software) on the management portal 20, and downloads the software from the management portal 20 to the management terminal 3 (step 203).
This download may be performed from the management portal 20 website to the management terminal 3, or the software may be sent by email from the management portal 20 (cloud server 2) to the management terminal 3.

Next, the administrator provides the setup software (file) to the terminal 4 to be set up by sending it by email or the like (step 205).
Next, the administrator runs the setup software on the terminal 4 (step 207).
Then, the terminal 4 accesses the management portal 20 (step 209). Access to the management portal 20 is restricted, and from a security standpoint, personal authentication is required to log in. When the administrator enters his/her ID/password on the login screen, it is authenticated and the website of the management portal 20 is displayed.
Note that the setup software may contain authentication information (for self-certification) with a token in place of the ID/password. In this case, the input of the ID/password is omitted, and the process automatically proceeds to the next step. This token imposes restrictions, such as the authentication information (information for terminal administrator self-certification) being valid for one day only, up to 10 times, etc., and login is possible within the restrictions, but login is not possible after the restrictions have been exceeded.

Then proceed to the next process. (The subsequent processes may be performed by installation software (installer) that is part of the setup software or that accompanies the software.)

When the setup (installation) of the terminal 4 is started, the cloud server 2 (management portal 20) first acquires the individual information 22 from the terminal 4 to be set up (step 211).

Next, an unused license key 21 is assigned to the terminal 4 (step 213).
This allocation may be done manually by an administrator, but the cloud server 2 (administration portal 20) may randomly extract unused license keys 21 and automatically allocate them.

Then, the cloud server 2 links the individual information 22 and the license key 21 for the terminal 4 and stores them as an individual license key 23 on the management portal 20 (step 215). Figure 2 shows how this is displayed on the management portal 20. Note that "linked" means associated.

Then, the license key 21 is encrypted and downloaded from the management portal 20 to the terminal 4 (step 217).

Next, the connection software is installed on terminal 4 (step 219).
After being set up, this connection software resides in the terminal 4. Then, the terminal 4 is authenticated by the authentication and authorization device 7 and is used to connect to the leased line 6.

Next, the license key 21 is stored (memorized) in the terminal 4 (step 221).
In addition, when the connection software is installed in the terminal 4, for example, the license key 21 assigned to the terminal 4 may be referenced, and (a) if the license key 21 is already linked to another terminal, the installation may be canceled, or (b) if the license key 21 is already linked to the terminal 4, the license key 21 may be installed, and the license key 21 may be stored in the terminal 4 during the installation of the connection software.

Furthermore, the process of step 223 may be performed.
In this step, the communication application setting information (specifications) linked to the account of company A is downloaded from the management portal 29 and applied to the terminal 4 (step 223).
If there is only one piece of setting information stored in the management portal 20 , that setting information is downloaded and applied to the terminal 4 .
When the setting information stored in the management portal 20 is of multiple types, such as types T1, T2, and T3, one of them is selected, downloaded, and applied to the terminal 4.

In this way, the setup method for terminal 4 in embodiment 1 is a setup method for terminal 4 when an authentication license key 21 is required to connect a terminal 4 belonging to a specified group (company A) to a specified communication line (dedicated line 6).
The process also includes a step of creating an account for company A on the cloud server 2 (FIG. 3, step 101); a step of storing a predetermined number of license keys for the account on the cloud server 2 (FIG. 3, step 103); an individual information acquisition step (FIG. 4, step 211) in which the cloud server 2 acquires individual information 22 from the terminal 4 and stores it in the cloud server 2; an individual information linking step (FIG. 4, steps 213, 215) in which the cloud server 2 applies an unused license key 21 out of the license keys 21 to a terminal 4 to which no license key 21 has been applied, to create an individual license key 23 linked to the individual information 22; and an installation step (FIG. 4, step 219) in which the cloud server 2 installs, based on the individual information 22, connection software for authenticating the terminal 4, connecting it to a communication line (dedicated line 6), and performing encrypted communication, on the terminal 4 from the cloud server 2.

In addition, in the process of installing the connection software (FIG. 4, steps 211 to 221 (223)), the terminal 4 downloads the license key 21 in an encrypted state from the cloud server 2 (management portal 20) (step 217), installs the connection software (step 219), and stores the license key 21 in the terminal 4 based on the connection software (step 221).

In addition, in this setup method, at least the individual information acquisition process (FIG. 2, step 211), the individual information linking process (step 215), and the installation process (step 219) can be automatically performed by executing the setup software (step 207).

This setup method can further include a step in which the cloud server 2 (management portal 20) stores communication application setting information associated with one or more accounts for company A's account (FIG. 3, step 105), and a communication application setting step in which the terminal 4 downloads the communication application setting information associated with a specific account from the cloud server 2 (management portal 20) and applies it (FIG. 4, step 223).

The method for managing terminals 4 in the first embodiment is a method for managing terminals 4 that belong to a specific group (company A) and are applicable to a license key 21 for connecting to a specific communication line (dedicated line 6), and includes a setup process (see FIG. 4) for setting up one or more terminals 4 using the setup method described above, a management portal creation process (see FIG. 2) for creating, on the management portal 20, management information indicating individual information 22 of the terminal 4, the application status of the license key 21 to the terminal 4, and, if the license key 21 is applied to the terminal 4, the license key 21 and the authentication connection status, and a management portal display output process for displaying the management portal 20 by accessing the management portal 20 from the management terminal.

[Hardware configuration of management system 1]
The hardware configuration of the management system 1 will be described with reference to FIG.
FIG. 5 is a diagram for explaining the hardware configuration of the management system 1 according to the first embodiment.
The cloud server 2 and management terminal 3 that constitute the management system 1 each have a CPU (Central Processing Unit), a ROM (Read Only Memory), a RAM (Random Access Memory), an internal bus connecting these, and an interface circuit provided between the internal bus and an external communication line 5.
The CPU executes various processes according to programs stored in the ROM or programs loaded from an external storage device (not shown) into the RAM. The RAM appropriately stores data and the like required for the CPU to execute various processes.
The terminal 4 and the authentication permission device 7 (authentication permission decision device 71) are configured in the same manner, and signals are exchanged between them via an interface circuit.

[program]
The cloud server 2 and the management terminal 3 are a kind of computer. In order to operate such a computer, a program for causing the computer to execute the setup of the terminal 4 may be installed and executed on the cloud server 2 or the management terminal 3, and may be configured to realize an individual information acquisition function in which the cloud server 2 acquires individual information 22 of the terminal 4 from the terminal 4 and stores the information in the cloud server 2, an individual information linking function in which the cloud server 2 applies an unused license key 21 among the license keys 21 to a terminal 4 to which the license key 21 has not been applied, and sets the individual license key 23 linked to the individual information 22, and an installation function in which the cloud server 2 installs, based on the individual information 22, connection software for connecting the terminal 4 to a communication line (dedicated line 6) and performing encrypted communication, in the terminal 4.

[Authentication permission device 7]
The authentication permission device 7 will now be described. As shown in Fig. 5, the authentication permission device 7 has an authentication permission judgment device 71 and a connection device 72. The authentication permission judgment device 71 is connected to the communication line 5 via an interface circuit. The authentication permission judgment device 71 has a CPU, ROM, RAM, and an interface circuit, similar to the terminal 4, etc. The connection device 72 is a kind of switch device that connects or disconnects the communication line 5 (terminal 4) and the dedicated line 6.
The authentication and permission device 7 cooperates with the management portal 20 to authenticate the terminal 4 , and sets the connection device 72 to connection on or off, thereby connecting or disconnecting the terminal 4 to the leased line 6 .
For example, in the case where there are multiple terminals 4 and the connection to the leased line 6 is assigned to each terminal 4 in a time-sharing manner, when a certain terminal 4 is authenticated, the connection device 72 connects to the leased line 6 with the connection on for the time period assigned to that terminal 4. On the other hand, when the terminal 4 is not authenticated, the connection device 72 cuts off the connection to the leased line 6 with the connection off for the time period assigned to that terminal 4.

[Connection or disconnection to the leased line 6 using the license key 21 or the individual license key 23]
The process of connecting or connecting the terminal 4 to the leased line 6 using the license key 21 or the individual license key 23 will be described with reference to FIG.
FIG. 6 is a diagram for explaining a process flow for connecting or disconnecting the terminal 4 to the leased line 6 in the first embodiment.
The process from the state where a certain terminal 4 is permitted to connect to the leased line 6 will be described.
First, the authentication suspension process is carried out for the license key 21 to be suspended (the terminal 4 to which the license key 21 is assigned) (step 300). When the "temporary authentication suspension" of the license key 21 (terminal 4) is set to "Yes" in the management portal 20, the authentication is suspended via the management portal 20 to the authentication permission device 7, and the connection of the terminal 4 to the dedicated line 6 is cut off.

In this state, the connection software is started on the terminal 4 (step 301).
Then, a request for connection to the dedicated line 6 of the terminal 4 is sent from the terminal 4 to the authentication/permission device 7 (step 303).
Next, the authentication permission device 7 (authentication permission judging device 71) collates the license key 21 of the terminal 4 with the license key 21 stored in the authentication permission device 7 (step 305).

Then, based on the result of the comparison, the authentication permission decision device 71 decides whether or not to permit connection (communication) to the leased line 6 (step 307).
If the license key 21 stored as the master in the authentication permission device 7 does not match the license key 21 of the individual license key 23 stored in the terminal 4 (NO), the connection is not permitted.
The authentication permission decision device 71 sets the connection device 72 to "connection off" and cuts off the leased line 6 (the cut-off state is maintained, step 311).
If the license key 21 matches (YES), the connection is permitted.
The authentication permission decision device 71 turns on the connection device 72 and connects it to the leased line 6 (step 309).

When the connection software is stopped by turning off the power of the terminal 4, for example, the authentication permission decision device 71 sets the connection device 72 to "connection off" and cuts off the leased line 6 (step 313).
For example, when the terminal 4 is shut down, step 313 may be performed by disconnecting the terminal 4 from the leased line 6 while leaving the connection device 72 in the on-state (when the terminal 4 is shut down, the connection software is stopped). In this case, when the terminal 4 is restarted, the process may proceed to step 301, for example. Then, in step 309, the terminal 4 is connected to the leased line 6 while keeping the connection device 72 in the on-state.

[Authentication Suspension Processing]
The authentication suspension process will now be described. Authentication suspension can be performed by operating the management portal 20.
In other words, the method for managing terminals 4 may further include a step in which the management terminal 3 changes the authentication status of a specific terminal 4 that has been authenticated and can be connected to the communication line (dedicated line 6) to an authentication suspended state on the management portal 20, thereby cutting off the connection of that terminal 4 to the communication line (dedicated line 6).
FIG. 7 is a diagram for explaining the processing flow of “temporarily suspend authentication” of the management portal 20 in the first embodiment.
In the management system 1, authentication is performed by the authentication permission device 7 based on the state of the "authentication suspension setting" field on the management portal 20. The management portal 20 can be accessed from the management terminal 3, and the "authentication suspension setting" field of the management portal 20 can be changed while being accessed.
Then, the process branches depending on whether or not "temporary authentication" in the "temporary authentication setting" field of the management portal 20 is set to "Yes" (step 401).
If "Yes" or "No", the process returns to step 401.
If "yes" is desired, the process proceeds to step 403.
In step 403, the "authentication suspension" in the "authentication suspension setting" field of the management portal 20 is set to "Yes" (step 403). Then, the authentication permission device 7 (authentication permission determination device 71) does not permit authentication of the terminal 4. Then, the connection state of the connection device 72 is switched to "connection off". Then, the connection to the leased line 6 is cut off.

[Effects of the First Embodiment]
According to the method for setting up the terminal 4 of the first embodiment, individual information of the terminal 4 is acquired by the cloud server 2 in an individual information acquisition step, an unused license key 21 is applied to the terminal 4 to become an individual license key 23 linked to the individual information 22 in an individual information linking step, and the connection software is installed in the terminal 4 based on the individual information 22 in an installation step. This reduces the risk that a secure setup will not be performed using the license key 21.

Furthermore, according to the method for setting up the terminal 4 of the first embodiment, the license key 21 is downloaded in an encrypted state to the terminal 4 in the installation process and is stored in the terminal 4 based on the connection software. This makes it possible to keep the license key 21 secret in the installation process. Furthermore, since the license key 21 is stored in the terminal 4 based on the connection software, it becomes possible, for example, to have the authentication permission device 7 transmit the license key 21 to the terminal 4 by starting the connection software.

In addition, according to the method for setting up the terminal 4 of the first embodiment, if at least the individual information acquisition process, the individual information linking process, and the installation process are automatically performed by executing the setup software, an even safer setup is possible. Also, the setup becomes easier.

In addition, according to the setup method for terminal 4 of embodiment 1, if it further includes a step of storing communication application setting information and a communication application setting step, it becomes easy to set up a communication application corresponding to an account.

In addition, according to the program of the first embodiment, the program is a program for causing a computer to execute the setup of the terminal 4, and is a program for causing the computer to realize an individual information acquisition function, an individual information linking function, and a connection software installation function. Therefore, by using the program,
Setup will be made even easier, with some parts of the setup being performed automatically.

In addition, the method for managing a terminal 4 according to the first embodiment includes a process for setting up the terminal 4, a process for creating a management portal, and a process for displaying the management portal, so that the use of the management portal can facilitate the management of the terminal 4.

In addition, according to the method for managing terminals 4 of embodiment 1, the method further includes a step of cutting off the connection of a specific terminal 4 that has been authenticated and can be connected to the communication line (dedicated line 6) to the communication line (dedicated line 6) by changing the authentication status of the terminal 4 to an authentication-suspended state on the management portal 20 by the management terminal 3, thereby making it possible to change (cut off) the connection status of the terminal 4 to the communication line (dedicated line 6) without the need to contact the operator (telecommunications carrier) of the dedicated line 6.

The management system for terminals 4 in the first embodiment includes a cloud server 2 that creates a management portal 20 and a management terminal 3 that manages terminals 4, and the management terminal 3 is capable of displaying and operating the management portal. The cloud server 2 is configured to prepare connection software for terminals 4 to connect to and communicate with a communication line (dedicated line 6). Therefore, using the management portal makes it easy to manage terminals 4. Also, it is possible to cut off access to the dedicated line 6 without the need to contact the dedicated line 6.

[Embodiment 2]
The method of managing the terminal 4 in the second embodiment (the method of cutting off the connection to the dedicated line 6) is basically the same as the method of managing the terminal 4 in the first embodiment. However, the difference is that whereas in the first embodiment, the method is performed by accessing the management portal 20 from the management terminal 3 and changing the authentication status of the terminal 4 to an authentication suspended state, in the second embodiment, it is further possible to access the management portal 20 from a smartphone at any time and change the authentication status of the terminal 4 to an authentication suspended state.

This will be described with reference to Fig. 8. Fig. 8 is a diagram for explaining the second embodiment.
The method for managing the terminal 4 according to the second embodiment further includes the following steps in addition to the method according to the first embodiment.

[Step 501: Specifying the terminal 4 for which authentication can be suspended by smartphone operation on the management portal 20 using the management terminal 3]
In this process, the user accesses the management portal 20 from the management terminal 3 by logging in. Then, the user specifies on the management portal 20 the terminal 4 for which the user wishes to be able to suspend authentication via smartphone operation.

[Step 503: A token corresponding to the terminal 4 is issued from the management portal 20 and received by the management terminal 3]
In this process, a token corresponding to the specified terminal 4 is issued from the management portal 20 (cloud server 2). The token is issued as a QR code (image) with a token, and is received by the management terminal 3 by email, downloading from a website, or the like.

[Step 505: Sending a token from management terminal 3 to the user of terminal 4]
In this process, a token (a QR code with a token (image, two-dimensional barcode, "QR code" is a registered trademark of DENSO WAVE INCORPORATED)) is sent from the management terminal 3 to the terminal 4 (user of the terminal 4) by attaching it to an email, for example.

[The token is attached to the software for accessing the management portal 20 on the smartphone (step 507)]
In this process, the QR code (image) is photographed with a smartphone, and the information stored in the QR code (image) is analyzed using a reading application (software).
Then, the token is attached to the software for accessing the management portal 20. By attaching the token to the access software in this way, access to the management portal 20 using the software is proved to be access linked to the terminal 4.
Such a reading application or access software can be easily obtained on the Internet, either free of charge or for a fee, but may be created specifically for the application of embodiment 2. These are installed in the smartphone in advance.

[A registration step (step 509) in which the smartphone is registered in the management portal 20 via the access software with the token attached, and the registration enables the smartphone to access the management portal 20 thereafter and change the authentication status of the terminal 4 to a suspended state]
In this process, when the software for accessing the management portal 20 is started, the management portal 20 containing management information for the terminal 4 (see FIG. 2 ; only some or all of the information related to the terminal 4 is displayed) is displayed on the smartphone. Then, a registration button is displayed for registering the smartphone as a smartphone that allows access to the management portal 20 for the terminal 4. By pressing the registration button, the smartphone is registered on the management portal 20 in association with the terminal 4.

The above steps then result in the following:
[After smartphone registration (step 511)]
Once a smartphone is registered in the management portal 20, it becomes possible thereafter to access the management portal 20 (the management portal 20 corresponding to the smartphone) from the smartphone at any time and change the authentication status of the terminal 4 corresponding to the smartphone to a stopped state (authentication temporarily suspended state).

[Effects of the Second Embodiment]
In the case of embodiment 2, once a smartphone is registered in the management portal 20, it becomes possible to access the management portal 20 from the smartphone and change the authentication status of the terminal 4 corresponding to the smartphone to a suspended state, thereby making it possible for a user of the terminal 4 to change the connection status of the terminal 4 to the communication line (dedicated line 6) without having to contact the telecommunications carrier of the dedicated line 6.
Even in this way, only information on the management portal 20 related to the terminal 4 corresponding to the smartphone can be accessed from the smartphone, and changes to the authentication status are limited to that terminal 4, so security of information on other terminals 4 and authentication can be ensured.

Note that the second embodiment is similar to the first embodiment except that the authentication status of the terminal 4 is changed to the authentication suspension status by accessing the management portal 20 from a smartphone, and has the corresponding effects among the effects of the first embodiment.

[Modification]
Although the present invention has been described based on the above embodiment, the present invention is not limited to the above embodiment. Changes can be made without departing from the spirit of the present invention, and for example, the following modifications are also possible.

(1) In the above-mentioned first and second embodiments, a personal computer is used as the management terminal 3 and the terminal 4, but the management terminal 3 and the terminal 4 are not limited to a personal computer. Either or both of them may be a tablet, a smartphone, etc.
(2) In the second embodiment, a smartphone is used as a device that enables access to the management portal 20 and change the authentication status of the terminal 4 to the authentication suspension state, but such a device is not limited to a smartphone. A tablet may be used instead of a smartphone.

1...Management system, 2...Cloud server, 3...Management terminal, 4...Terminal, 5...Communication line, 6...Leased line, 7...Authentication permission device, 20...Management portal, 21...License key, 22...Individual information, 23...Individual license key, 61...Base connection device, 62...Server within the base, 63...Communication line within the base, 71...Authentication permission judgment device, 72...Connection device

Claims (9)

A method for setting up a terminal when a license key for authentication is required to connect a terminal belonging to a predetermined group to a predetermined communication line, comprising the steps of:
creating an account for the group on a cloud server;
storing, on the cloud server, a predetermined number of license keys for the account;
an individual information acquisition step of the cloud server acquiring individual information of the terminal from the terminal and storing the information in the cloud server;
an individual information linking step in which the cloud server applies an unused license key among the license keys to the terminal to which no license key has been applied, and sets the unused license key as an individual license key linked to the individual information;
and an installation step of installing connection software for authenticating the terminal, connecting to the communication line, and performing encrypted communication from the cloud server to the terminal based on the individual information. 2. The terminal setup method according to claim 1,
A method for setting up a terminal, characterized in that, in the installation process, the terminal downloads the license key in an encrypted state from the cloud server, installs the connection software, and stores the license key in the terminal based on the connection software. 3. The terminal setup method according to claim 1, further comprising:
A terminal setup method, comprising: at least the individual information acquisition step, the individual information linking step, and the installation step being automatically performed by executing setup software. A terminal setup method according to any one of claims 1 to 3,
Furthermore,
storing, by the cloud server, one or more account-associated communication application setting information for the account;
a communication application setting step in which the terminal downloads the communication application setting information linked to a specific account from the cloud server and applies the communication application setting information. A program for causing a computer to execute a terminal setup, the program comprising:
an individual information acquisition function in which the cloud server acquires individual information of the terminal from the terminal and stores the information in the cloud server;
An individual information linking function in which the cloud server applies an unused license key among the license keys to the terminal to which no license key has been applied, and sets the unused license key as an individual license key linked to the individual information; and
an installation function for installing connection software for connecting the terminal to the communication line and performing encrypted communication from the cloud server to the terminal based on the individual information;
A program to achieve this. A method for managing a terminal that belongs to a predetermined group and to which a license key for connecting to a predetermined communication line can be applied, comprising the steps of:
A setup step of setting up one or more of the terminals using the setup method according to any one of claims 1 to 4;
a management portal creation step of creating, on a management portal, management information indicating individual information of the terminal, an application state of the license key to the terminal, and, if the license key is applied to the terminal, the license key and an authentication connection state;
a management portal display step of displaying the management portal by accessing the management portal from a management terminal. A method for managing a terminal according to claim 6, comprising the steps of:
Furthermore,
a step of cutting off connection of a specific terminal, which has been authenticated and can be connected to the communication line, to an authentication suspended state on the management portal by the management terminal, thereby cutting off connection of the specific terminal to the communication line. A method for managing a terminal according to claim 6 or 7, comprising the steps of:
Furthermore,
A step of designating, on the management portal, a terminal for which authentication suspension is to be performed by operating a smartphone, using the management terminal;
a step of issuing a token corresponding to the terminal from the management portal and receiving the token at the management terminal;
sending the token from the management terminal to a user of the terminal;
said token being attached to software on said smartphone for accessing said management portal;
a registration process in which the smartphone is registered in the management portal via the access software to which the token is attached, and said registration enables the smartphone to access the management portal thereafter and change the authentication status of the terminal to a suspended state. A management system for a terminal that belongs to a predetermined group and is applicable to a license key for authentication for connecting to a predetermined communication line, comprising:
a cloud server that creates a management portal that indicates individual information of the terminal, the application status of the license key to the terminal, the license key if the terminal is set up and the license key is applied, and an authentication connection status;
a management terminal for managing the terminals,
the management terminal is capable of specifying the terminal to which the license key is to be applied on the management portal, accessing the cloud server to display the management portal, and changing the authentication status of a specific terminal to an authentication suspension state on the management portal;
The cloud server prepares connection software that is installed on the terminal designated by the management terminal and enables the terminal to connect to the communication line and perform encrypted communication.
A terminal management system configured as follows.

Images