JP6134406B1 - Device management system, device management method and program - Google Patents

Abstract

An object of the present invention is to provide a device management system, a device management method, and a program that improve the convenience of an administrator and improve the security of the system. A device management system 1 for managing devices used by a user is registered in such a manner that an application provider registers an application in a database, and an administrator of the device management system 1 introduces the device into a device used by the user. The application is selected from the database and purchased, and the purchased application is distributed to the device used by the user. [Selection] Figure 1

Description

  The present invention relates to a device management system, a device management method, and a program for managing devices used by a user.

  In recent years, such information terminals are used in various scenes as information terminals such as smartphones and tablet terminals become more sophisticated and popular. For example, a user uses an information terminal owned by the user or an information terminal provided for business use for his business.

  In such an information terminal, the user has to download a desired application from an application sales site, an application distribution site, or the like and install it on the information terminal owned by the user.

  As a configuration in which such a user actively suppresses the trouble of installing an application, a configuration in which the user actively receives an application installation or update program without accessing an application distribution site or the like is disclosed. (See Patent Document 1).

JP2015-109114A

  However, in the configuration of Patent Document 1, although it is possible to acquire a new application, an update program, or the like without the user actively executing access, the administrator of the device management system is installed by the user. The contents of the application, settings, etc. could not be confirmed. Therefore, when the administrator checks the contents and settings of the application installed by the user, the user needs to notify the administrator about the application, or the administrator must actually check the information about the application. Convenience was low. In addition, since the user can install an application that the administrator does not want, the security of the device management system may be reduced.

  An object of the present invention is to provide a device management system, a device management method, and a program that improve the convenience of the administrator and improve the security of the system.

  The present invention provides the following solutions.

The invention according to the first aspect is a device management system for managing a device used by a user,
A registration means for registering the application in a database by a provider of the application;
A purchase means for an administrator of the device management system to select and purchase an application to be installed in a device used by the user from the database;
Distribution means for distributing the purchased application to a device used by the user;
A device management system is provided.

  According to the first aspect of the invention, in the device management system for managing the device used by the user, the provider of the application registers the application in the database, and the administrator of the device management system An application to be installed in a device to be used is selected and purchased from the database, and the purchased application is distributed to the device used by the user.

  Here, the invention according to the first feature is a category of the device management system, but the same operation / effect according to the category is exhibited also in other categories such as a device management method or a program.

The invention which concerns on 2nd characteristic WHEREIN: The introduction means which introduces the said distributed application to the apparatus which the said user uses,
A device management system that is an invention according to a first feature is provided.

  According to the second aspect of the invention, the equipment management system according to the first aspect of the invention introduces the distributed application to the equipment used by the user.

The invention according to a third aspect is characterized in that, after the application is purchased, the provider of the application exchanges messages with the administrator of the device management system for sending and receiving messages,
A device management system that is an invention according to either the first or second feature is provided.

  According to the third aspect of the invention, the device management system according to the first or second aspect of the invention is characterized in that, after the application is purchased, the provider of the application makes the device management system Send and receive messages with other administrators.

An invention according to a fourth feature is a device management method for managing a device used by a user,
An application provider registers the application in a database;
An administrator of the device management system selects and purchases an application to be installed in a device used by the user from the database;
Delivering the purchased application to a device used by the user;
A device management method is provided.

The invention which concerns on the 5th characteristic in the apparatus management system which manages the apparatus which a user uses,
An application provider registers the application in a database;
The administrator of the device management system selects and purchases an application to be installed in the device used by the user from the database;
Delivering the purchased application to a device used by the user;
A program characterized in that is executed is provided.

  According to the present invention, it is possible to provide a device management system, a device management method, and a program that improve the convenience of the administrator and improve the security of the system.

FIG. 1 is a diagram showing an outline of the device management system 1. FIG. 2 is an overall configuration diagram of the device management system 1. FIG. 3 is a functional block diagram of the distribution server 10, the user terminal 100, the administrator terminal 200, and the provider terminal 300. FIG. 4 is a flowchart showing terminal management information registration processing executed by the administrator terminal 200. FIG. 5 is a flowchart showing an application introduction process executed by the distribution server 10, the user terminal 100, the administrator terminal 200, and the provider terminal 300. FIG. 6 is a flowchart showing message transmission / reception processing executed by the distribution server 10, the administrator terminal 200, and the provider terminal 300. FIG. 7 is a diagram showing a terminal information management table. FIG. 8 shows a terminal affiliation management table. FIG. 9 is a diagram showing an application database. FIG. 10 shows an application purchase screen. FIG. 11 is a diagram showing a support application screen. FIG. 12 is a diagram showing a message list screen.

  Hereinafter, the best mode for carrying out the present invention will be described with reference to the drawings. This is merely an example, and the technical scope of the present invention is not limited to this.

[Outline of Device Management System 1]
The outline of the present invention will be described with reference to FIG. FIG. 1 is a diagram for explaining an overview of a device management system 1 which is a preferred embodiment of the present invention. The device management system 1 includes a distribution server 10, a user terminal 100, an administrator terminal 200, and a provider terminal 300. Each device is not limited to one device, and may be a plurality of devices. Each process described below may be configured to be executed by any, a plurality, or all of each device. Each device may be either an actual device or a virtual device or both.

  The distribution server 10 is a server device capable of data communication with the user terminal 100, the administrator terminal 200, and the provider terminal 300.

  The user terminal 100 is a terminal device capable of data communication with the distribution server 10. The user terminal 100 is, for example, an electronic product such as a netbook terminal, a slate terminal, an electronic book terminal, and a portable music player in addition to a mobile phone, a portable information terminal, and a personal computer.

  The administrator terminal 200 is a terminal device capable of data communication with the distribution server 10. The administrator terminal 200 is an electrical appliance similar to the user terminal 100.

  The provider terminal 300 is a terminal device capable of data communication with the distribution server 10. The provider terminal 300 is an electrical appliance similar to the user terminal 100 and the administrator terminal 200.

  First, the provider terminal 300 transmits application data, which is information related to the application created by the application provider, to the distribution server 10, and the distribution server 10 registers it in the distribution application database based on the application data ( Step S01).

  The administrator terminal 200 receives a purchase instruction from the administrator of the device management system 1 to select and purchase an application to be installed in the user terminal 100 used by the user from the distribution application database, and purchases the purchase instruction to the distribution server 10. An instruction is transmitted (step S02).

  The distribution server 10 receives the purchase instruction, and distributes the application purchased by the administrator to the user terminal 100 used by the user based on the purchase instruction (step S03). The user terminal 100 receives the application and introduces the application to itself.

  In this way, the device management system 1 allows the system administrator to select an application and introduce the selected application into the user terminal 100. Therefore, the user needs to introduce the application individually. Disappears. Therefore, it is not necessary for the administrator to install and set an application in each user terminal 100, so that the convenience for the administrator is improved. In addition, by introducing the application selected by the administrator to the user terminal 100, the user can suppress introduction of an application that is not intended by the administrator, so that the security of the system can be improved.

  The above is the outline of the device management system 1.

[System configuration of device management system 1]
The system configuration of the device management system 1 will be described with reference to FIG. FIG. 2 is a diagram showing a system configuration of the device management system 1 which is a preferred embodiment of the present invention. The device management system 1 includes a distribution server 10, a user terminal 100, an administrator terminal 200, a provider terminal 300, and a public line network 5 (Internet network, third and fourth generation communication network, etc.) 5. A plurality of devices may exist on the system. Further, each device may be realized by either or both of an actual device and a virtual device.

  The distribution server 10 has the functions described below and is the server device described above.

  The user terminal 100 is the above-described terminal device having the functions described below.

  The administrator terminal 200 is a terminal device that has the functions described below and is described above.

  The provider terminal 300 has the functions described later and is the terminal device described above.

[Description of each function]
Based on FIG. 3, functions of the device management system 1 will be described. FIG. 3 is a functional block diagram of the distribution server 10, the user terminal 100, the administrator terminal 200, and the provider terminal 300 according to a preferred embodiment of the present invention.

  The distribution server 10 includes a CPU (Central Processing Unit), a RAM (Random Access Memory), a ROM (Read Only Memory), and the like as the control unit 11, and a device for enabling communication with other devices as the communication unit 12. For example, a device compatible with WiFi (Wireless Fidelity) compliant with IEEE 802.11 is provided. In addition, the distribution server 10 includes a data storage unit such as a hard disk, a semiconductor memory, a recording medium, a memory card, or the like as the storage unit 13.

  In the distribution server 10, when the control unit 11 reads a predetermined program, the application data receiving module 20, the application list distribution module 21, the payment module 22, the application distribution module 23, support application data in cooperation with the communication unit 12. A reception module 24, a new arrival notification transmission module 25, a message list acquisition request reception module 26, a message list transmission module 27, a message data reception module 28, and a message transmission module 29 are realized. Further, in the distribution server 10, the control unit 11 reads a predetermined program, thereby realizing the database storage module 30 and the message storage module 31 in cooperation with the storage unit 13.

  As with the distribution server 10, the user terminal 100 includes a CPU, RAM, ROM, and the like as the control unit 110, a device for enabling communication with other devices as the communication unit 120, and a storage unit 130 as the storage unit 130. A data storage unit is provided.

  In the user terminal 100, when the control unit 110 reads a predetermined program, the application acquisition module 150 is realized in cooperation with the communication unit 120. Further, in the user terminal 100, the application unit 160 is realized in cooperation with the storage unit 130 by the control unit 110 reading a predetermined program.

  As with the user terminal 100, the administrator terminal 200 includes a CPU, a RAM, a ROM, and the like as the control unit 210, a device for enabling communication with other devices as the communication unit 220, and a storage unit 230 A data storage unit is provided. Further, the administrator terminal 200 includes, as the input / output unit 240, a display unit that outputs and displays data and images controlled by the control unit 210, an input unit such as a touch panel, a keyboard, and a mouse that receives input from the user.

  In the administrator terminal 200, when the control unit 210 reads a predetermined program, the application list acquisition module 250, the payment data transmission module 251, the support application data transmission module 252, and the message reception module 253 cooperate with the communication unit 220. The message transmission module 254 is realized. In the administrator terminal 200, the control unit 210 reads a predetermined program, thereby realizing the table storage module 260 in cooperation with the storage unit 230. Further, in the administrator terminal 200, the control unit 210 reads a predetermined program, so that the terminal management information input reception module 270, the application list acquisition instruction reception module 271 and the application list display module cooperate with the input / output unit 240. 272, an application purchase screen display module 273, a support application input reception module 274, and a message input reception module 275 are realized.

  As with the user terminal 100, the provider terminal 300 includes a CPU, RAM, ROM, and the like as the control unit 310, a device for enabling communication with other devices as the communication unit 320, and an input / output unit 340. As such, a display unit, an input unit, and the like are provided.

  In the provider terminal 300, when the control unit 310 reads a predetermined program, the application data transmission module 350, the new arrival notification reception module 351, the message acquisition module 352, and the message data transmission module 353 are cooperated with the communication unit 320. Realize. Further, in the provider terminal 300, the message list display module 370 and the message creation module 371 are realized in cooperation with the input / output unit 340 by the control unit 310 reading a predetermined program.

[Terminal management information registration process]
A terminal management information registration process executed by the administrator terminal 200 will be described with reference to FIG. FIG. 4 is a flowchart of terminal management information registration processing executed by the administrator terminal 200. Processing executed by each module described above will be described together with this processing.

  First, the terminal management information input receiving module 270 determines whether or not input of terminal management information has been received from an administrator (step S10). The terminal management information includes, for example, the name of the user terminal 100, the OS name of the user terminal 100, the name of the user who owns the user terminal 100, and the name of the user group to which the user terminal 100 is distributed or used. In step S10, the administrator terminal 200 may be configured to acquire terminal management information from an external terminal, another database, or the like, instead of receiving input of terminal management information from the administrator. Moreover, you may acquire required information by another structure. Further, the information included in the terminal management information may be information other than the information described above.

  If the terminal management information input receiving module 270 determines in step S10 that terminal management information input has not been received (NO in step S10), the process ends.

  On the other hand, when the terminal management information input reception module 270 determines that the input of terminal management information has been received (YES in step S10), the table storage module 260 creates a terminal information management table based on the received terminal management information. Is stored (step S11).

[Terminal information management table]
FIG. 7 is a diagram showing a terminal information management table stored in the table storage module 260. In FIG. 7, the table storage module 260 stores a terminal name, an OS name, a user name, and a department name in association with each other based on the terminal management information. The terminal name is the name of the user terminal 100. The terminal name is not limited to the name set for each user terminal 100, but may be a number or a character string that can uniquely identify the terminal such as an ID, a serial number, or a MAC address. The OS name is the name of the OS installed in the user terminal 100. The user name is the name of the user who owns the user terminal 100. The user name is not limited to a part or all of the name of the user who owns each user terminal 100, but may be a number or character string such as an employee number, ID, or identifier. The department name is a name of a user group to be distributed or used by the user terminal 100. The user group is a classification to which one or a plurality of user terminals 100 belong, and includes a department name, a company name, a project name, a job title, and the like. Each item of the terminal information management table stored in the table storage module 260 can be changed as appropriate.

  The terminal information management table may be stored in the distribution server 10 instead of in the administrator terminal 200. In this case, the administrator terminal 200 transmits terminal management information to the distribution server 10, and the distribution server 10 may store the terminal management information in association with an identifier such as an ID of the administrator terminal 200. That is, the ID of the administrator terminal 200 may be further associated with the terminal information management table described above. The ID of the administrator terminal 200 in this case is, for example, a corporate ID issued for each corporation or a personal ID issued for each individual.

  The table storage module 260 creates and stores a terminal affiliation management table based on the terminal management information (step S12).

[Terminal belonging management table]
FIG. 8 is a diagram showing a terminal affiliation management table stored in the table storage module 260. In FIG. 8, the table storage module 260 stores a department name and a terminal name in association with each other as a terminal affiliation management table. The department name and terminal name are the same as those in the terminal information management table described above. Each item in the terminal affiliation management table stored in the table storage module 260 can be changed as appropriate.

  The terminal affiliation management table may be configured to be stored in the distribution server 10 in the same manner as the terminal information management table.

  The above is the terminal management information registration process.

[Application installation processing]
Based on FIG. 5, application introduction processing executed by the distribution server 10, the user terminal 100, the administrator terminal 200, and the provider terminal 300 will be described. FIG. 5 is a diagram illustrating a flowchart of an application introduction process executed by the distribution server 10, the user terminal 100, the administrator terminal 200, and the provider terminal 300. The processing executed by the modules of each device described above will be described together with this processing.

  First, the application data transmission module 350 transmits application data indicating an application created by the application provider and information related to the application to the distribution server 10 (step S20). In addition to the application, the application data includes provider information such as the provider's name, provider ID, application name, application ID, sales price, contact e-mail address, official site URL, and application description. .

  The application data receiving module 20 receives application data transmitted from the provider terminal 300. The database storage module 30 creates and stores an application database based on the received application data (step S21).

Application database
The application database stored in the database storage module 30 will be described with reference to FIG. FIG. 9 is a diagram showing an application database.

  In FIG. 9, the database storage module 30 creates and stores an application database in which an application name, a provider name, a price, an official site URL, and an email address are associated with each other based on application data. Although not shown on the database, the application name and the application description are further linked to the application name. The application name is the name of the application. The application name is not limited to the name of each application, but may be a number such as an ID or an identifier or a character string. The provider name is the name of the provider of the application. The provider name is not limited to the provider's company name or the provider's personal name, but may be a number or character string such as an ID or an identifier. The price is the selling price of the application. The price may be an amount related to the sale of application data, or an amount related to a license for granting an application license. The official site URL is a URL of a website owned by an application provider or a website that publishes application information such as updater information and notifications. An e-mail address is a destination for sending a message to an application provider.

  The database storage module 30 may store other information included in the application data in association with the database in addition to each item described above, or only one of the items described above, for example, an application name, A database in which only prices and email addresses are associated may be created and stored. Each item in the application database can be changed as appropriate. In addition, regarding the provider name, price, official site URL, and e-mail address, a plurality of pieces of information may be associated with one application. For example, a plurality of e-mail addresses may be associated with one application, or each of or one of a plurality of prices, a plurality of providers, and a plurality of official site URLs may be associated. .

  The application list acquisition instruction reception module 271 determines whether an application list acquisition instruction has been received (step S22). The application list acquisition instruction is an instruction to acquire a part or all of application data registered in the application database. This acquisition instruction is determined based on whether, for example, a dedicated application, an Internet browsing application, or the like is started and an input necessary for acquiring the application list is received. In step S22, when the application list acquisition instruction reception module 271 determines that an acquisition instruction has not been received (NO in step S22), this process is repeated until an acquisition instruction is received.

  On the other hand, when the application list acquisition instruction reception module 271 determines in step S22 that the acquisition instruction has been received (YES in step S22), the application list acquisition module 250 transmits an application list acquisition instruction to the distribution server 10 (step S22). S23).

  The application list distribution module 21 receives an application list acquisition instruction. Based on the application list acquisition instruction, the application list distribution module 21 transmits information related to the application stored in the application database to the administrator terminal 200 as application list data (step S24).

  The application list acquisition module 250 receives application list data. The application list display module 272 displays an application list based on the received application list data (step S25).

  The application list display module 272 determines whether or not an input for selecting one of the displayed applications has been received (step S26). If the application list display module 272 determines in step S26 that a selection input has not been accepted (NO in step S26), this process is repeated until it is accepted.

  On the other hand, when the application list display module 272 determines in step S26 that the selection input has been accepted (YES in step S26), the application purchase screen display module 273 displays an application purchase screen indicating the purchase screen of the selected application. (Step S27). In step S27, the application purchase screen display module 273 displays the application purchase screen shown in FIG.

  FIG. 10 is a diagram showing an application purchase screen displayed by the application purchase screen display module 273. 10, the application purchase screen display module 273 displays an application name display area 500, an application description display area 510, an introduction destination selection area 520, and an introduction information display area 530 as application purchase screens. The application name display area 500 displays the name and icon of the application received in step S26. The application explanation display area 510 displays the explanation, sales price, license amount, and the like related to this application. The installation destination selection area 520 displays a user group such as a department name to which the user terminal 100 to which the application is installed belongs, and accepts a selection input from the administrator. In this user group, the total number of the user group registered in the above-described terminal affiliation management table and the user terminal 100 associated with this user group is displayed. The introduction information display area 530 displays the total number of user terminals 100 in the user group selected in the introduction destination selection area 520, the total number of user terminals 100 for each OS, and when introducing an application to the user terminals 100 belonging to the selected user group. The total amount of money necessary for the operation, a cancel icon 540, and a determination icon 550 are displayed. The cancel icon 540 and the determination icon 550 are used for processing to be described later.

  In the present embodiment, the user group is not limited to the department name, but may be other configurations such as a company, a project, and a post, and can be changed as appropriate as long as one or a plurality of user terminals 100 belong to it. . The price of an application is the price of the application itself, a license fee that gives permission to use the application, or the like.

  In this embodiment, the user group is selected. However, not only the user group is specified, but also the identifier and ID of the user terminal 100 existing in the device management system 1 are displayed, and the user terminal that introduces the application 100 may be designated separately. Also, instead of the user terminal 100, the user name, identifier, etc. are displayed, and by designating this user, the application is introduced to the user terminal 100 associated with the user name stored in the terminal information management table It may be.

  The application purchase screen display module 273 determines whether an application purchase input has been accepted (step S28). The application purchase screen display module 273 determines whether or not a purchase input has been received based on whether an operation input of either the cancel icon 540 or the determination icon 550 has been received. If the application purchase screen display module 273 determines in step S28 that no purchase input has been received (NO in step S28), that is, if an operation input to the cancel icon 540 has been received, the application purchase screen display module 273 cancels the purchase of the application, A notice that the purchase of is canceled is displayed, and this processing is terminated. In step S28, the application purchase screen display module 273 may display the application list again after canceling the purchase of the application.

  On the other hand, when the application purchase screen display module 273 determines in step S28 that the purchase input has been received (YES in step S28), that is, when the operation input of the decision icon 550 is received, the payment data transmission module 251 receives the payment data. Is transmitted to the distribution server 10 (step S29). The payment data includes various information necessary for purchasing the application, terminal management information, setting information such as usage conditions and connection destinations.

  The payment module 22 receives the payment data transmitted by the administrator terminal 200. The payment module 22 executes a payment process such as a billing process necessary for purchasing the application based on the payment data (step S30). The settlement process is a process for collecting a charge from a settlement account of the administrator terminal 200, for example.

  The application distribution module 23 distributes the application for which the purchase process has been executed to the designated user terminal 100 based on the payment data (step S31).

  The application acquisition module 150 acquires the application distributed by the distribution server 10, and the application introduction module 160 introduces the acquired application to itself (step S32). In step S32, the application introduction module 160 may set an application based on the setting information included in the payment data.

  The above is the application introduction process.

[Message transmission / reception processing]
A message transmission / reception process executed by the distribution server 10, the administrator terminal 200, and the provider terminal 300 will be described with reference to FIG. FIG. 6 is a diagram illustrating a flowchart of message transmission / reception processing executed by the distribution server 10, the administrator terminal 200, and the provider terminal 300. The processing executed by the modules of each device described above will be described together with this processing.

  The support application input receiving module 274 determines whether or not the support application input has been received (step S40). In step S40, the support application input receiving module 274 has received the support application input based on whether a dedicated application is started, the support web site is accessed, and the support application input is executed. Judge whether or not. If the support application input receiving module 274 determines in step S40 that the support application input has not been received (NO in step S40), the process ends.

  On the other hand, when the support application input receiving module 274 determines in step S40 that the support application input has been received (step S40 YES), the support application input receiving module 274 displays a support application screen (step S41).

  FIG. 11 is a diagram showing a support application screen displayed by the support application input receiving module 274. 11, the support application input receiving module 274 includes a notification message display area 600, an application display area 610, a period display area 620, a terminal number display area 630, a support application display area 640, a contract display area 650, an application icon 660, and a cancel. An icon 670 is displayed.

  The notification message display area 600 displays a message indicating that it is a support application screen. The application name display area 610 displays the name of the application that is the target of the current support application. The period display area 620 displays a plurality of or one support period and accepts a selection input from the administrator. The support application display area 640 displays a message as to whether to receive support and accepts a selection input from the administrator. The rule display area 650 displays a support use rule and a message indicating whether or not to agree to the use rule, and accepts a selection input from the administrator. The application icon 660 receives input from the administrator and transmits the input information to the distribution server 10. The cancel icon 670 receives input from the administrator, deletes the input information, and displays a notification screen indicating that the support application has been canceled. The content displayed on the support application screen is not limited to the above-described configuration, and can be changed as appropriate.

  The support application input receiving module 274 receives input of each information necessary for application and determines whether or not a support application has been received (step S42). In step S42, the support application input receiving module 274 determines whether a support application has been received based on whether the application icon 660 or the cancel icon 670 has been input.

  In step S42, when the support application input receiving module 274 determines that the support application has not been received (NO in step S42), that is, when it is determined that the input to the cancel icon 670 has been received, the process is terminated. When receiving an input to the cancel icon 670, the support application input receiving module 274 deletes the input information, displays a notification screen indicating that the support application has been canceled, and ends this processing.

  On the other hand, when the support application input receiving module 274 determines that the support application has been received (step S42 YES), that is, when it is determined that the input to the application icon 660 has been received, the support application data transmission module 252 Support application data, which is information related to this, is transmitted to the distribution server 10 (step S43). The support application data includes personal information such as the administrator's name, ID, contact e-mail address, and information related to the support period. In step S42, if an input to the application icon 660 is accepted, but an input to the support application display area 640 or an input to the contract display area 650 is not performed, the support application is canceled and necessary A notification screen indicating that no information has been input is displayed, and it is determined whether or not a support application has been accepted again.

  The support application data receiving module 24 receives support application data. The message storage module 31 stores the message box for the provider of this application in association with the personal information of the manager based on the support application data received this time (step S44). If the message box does not exist, a new message box may be created.

  The new arrival notification transmission module 25 transmits a new arrival support notification for notifying that new personal information is associated to the provider terminal 300 (step S45). For example, the new arrival support notification transmits a message to the contact mail address of the provider associated with the message box for the provider. Note that the notification may be transmitted by other methods.

  The new arrival notification receiving module 351 receives a new arrival support notification. The message acquisition module 352 transmits a message list acquisition request to the distribution server 10 (step S46). The message list is a part or all of messages stored in the message storage module 31. The message list may be configured to exclude previously acquired messages and acquire only a message list that has not been acquired.

  The message list acquisition request receiving module 26 receives a message list acquisition request. Based on the received message list acquisition request, the message list transmission module 27 transmits message list data indicating a message list existing in the message box of the provider to the provider terminal 300 (step S47).

  The message acquisition module 352 receives message list data. The message list display module 370 displays a message list screen based on the received message list data (step S48).

  FIG. 12 is a diagram showing a message list screen displayed by the message list display module 370. In FIG. 12, the message list display module 370 displays an explanation display area 700, a user name display area 710, a company name display area 720, a remaining period display area 730, and an inquiry method display area 740 as message list screens.

  In the explanation display area 700, a message explaining the contents of the message list screen is displayed. The user name display area 710 displays the name of the administrator who owns the administrator terminal 200 and the name of the administrator terminal 200. The company name display area 720 displays the name of the company to which the administrator of the administrator terminal 200 belongs and the name of the organization. The remaining period display area 730 displays the remaining period of support. In the inquiry method display area 740, a mail icon 750 and a chat icon 760 are displayed. The mail icon 750 is an icon associated with each administrator's contact mail address, accepts an input operation of the provider, and activates an application necessary for sending and receiving messages. The chat icon 760 is an icon associated with each manager's ID and contact e-mail address. The chat icon 760 accepts a provider's input operation and activates an application necessary for sending and receiving a chat.

  The application provider registers in advance with the distribution server 10 whether support can be executed, and the distribution server 10 sets, for each application, whether or not matching is possible when the administrator applies for support. It is also possible. The contents displayed on the message list screen can be changed as appropriate.

  The message creation module 371 creates a message addressed to the administrator contact email address included in the new arrival support notification (step S49). The message creation module 371 sets a mail address as a contact mail address of an administrator, sets a text and a title as a preset sentence, or a sentence executed by a provider, and creates a message.

  The message data transmission module 353 transmits message data indicating the created message to the distribution server 10 (step S50). The message data includes the contact mail address of the provider, the contact mail address of the administrator, the text, and the title.

  The message data receiving module 28 receives message data. The message transmission module 29 transmits a message to the administrator terminal 200 based on the message data (step S51).

  The message receiving module 253 receives a message. The message input receiving module 275 determines whether or not a message input has been received (step S52). In step S52, the message input receiving module 275 makes a determination based on whether or not a reply input to the received message has been received. The reply input includes input of a message body and a title, and a message transmission instruction. In step S52, when the message input reception module 275 determines that the input is not received (NO in step S52), the process is repeated until the input is received.

  On the other hand, when the message input reception module 275 determines in step S52 that the input has been received (step S52 YES), the message transmission module 254 transmits message data indicating the received message to the distribution server 10 (step S53). .

  The message data receiving module 28 receives message data. The new arrival notification transmission module 25 transmits a new arrival message notification for notifying that a new message has been received to the provider terminal 300 (step S54). The new message notification is transmitted as e-mail, for example. Note that the notification may be transmitted by other methods.

  The new arrival notification receiving module 351 receives a new arrival message notification. The message acquisition module 352 transmits a message list acquisition request to the distribution server 10 (step S55). The process in step S55 is the same as the process in step S46 described above.

  The message list acquisition request receiving module 26 receives a message list acquisition request. The message list transmission module 27 transmits message list data to the provider terminal 300 based on the received message list acquisition request (step S56). The process of step S56 is the same as the process of step S47 described above.

The message acquisition module 352 receives a message list. The message list display module 370 displays the received message list (step S57). The process in step S57 is the same as the process in step S48 described above.

  In the above-described embodiment, the configuration using mail as a message has been described. However, the message is not limited to email, and may be configured to use chat or other methods. In this case, an input to the chat icon 760 described above may be accepted and each process may be executed.

  In each process described above, the administrator terminal 200 and the provider terminal 300 transmit and receive messages via the distribution server 10, but directly transmit and receive messages without passing through the distribution server 10. It may be configured to do so. In this case, for example, the administrator terminal 200 notifies the provider terminal 300 of its own email address when applying for support, and the provider terminal 300 is configured to transmit and receive messages to this email address. good.

  The above is message transmission / reception processing.

  The means and functions described above are realized by a computer (including a CPU, an information processing apparatus, and various terminals) reading and executing a predetermined program. The program is provided in a form recorded on a computer-readable recording medium such as a flexible disk, CD (CD-ROM, etc.), DVD (DVD-ROM, DVD-RAM, etc.), for example. In this case, the computer reads the program from the recording medium, transfers it to the internal storage device or the external storage device, stores it, and executes it. The program may be recorded in advance in a storage device (recording medium) such as a magnetic disk, an optical disk, or a magneto-optical disk, and provided from the storage device to a computer via a communication line.

  As mentioned above, although embodiment of this invention was described, this invention is not limited to these embodiment mentioned above. The effects described in the embodiments of the present invention are only the most preferable effects resulting from the present invention, and the effects of the present invention are limited to those described in the embodiments of the present invention. is not.

  1 device management system, 10 distribution server, 100 user terminal, 200 administrator terminal, 300 provider terminal

Claims (5)

A device management system for managing a plurality of user terminals used by users for their business ,
An application database including application name and application provider name information, and a plurality of registered application information provided by a plurality of providers;
Application for introduction to at least user terminals belonging to a predetermined department among user terminals stored in advance in a terminal affiliation management table in which a department name and a user terminal name are associated with each other by an administrator of the device management system Purchasing means for selecting and purchasing from the application database;
Distribution means for collectively distributing the purchased application to user terminals belonging to at least the predetermined department ;
A device management system comprising: Introducing means for introducing the distributed application into the user terminal ;
The device management system according to claim 1, further comprising: After the application is purchased, an address exchange means for the provider of the application to send and receive a message with an administrator of the device management system;
The device management system according to claim 1, further comprising: A device management method for managing a plurality of user terminals used by users for their own work ,
A plurality of providers providing an application , registering application information including application name and application provider name information in an application database;
Application for introduction to at least user terminals belonging to a predetermined department among user terminals stored in advance in a terminal affiliation management table in which a department name and a user terminal name are associated with each other by an administrator of the device management system Selecting and purchasing from the application database;
Delivering the purchased applications together to user terminals belonging to at least the predetermined department ;
A device management method comprising: In a device management system that manages multiple user terminals that users use for their work ,
A plurality of providers providing the application , each registering application information including application name and application provider name information in the application database;
Application for introduction to at least user terminals belonging to a predetermined department among user terminals stored in advance in a terminal affiliation management table in which a department name and a user terminal name are associated with each other by an administrator of the device management system Selecting from the application database and purchasing,
Delivering the purchased applications together to at least user terminals belonging to a predetermined department ;
A program characterized by having executed.