JP2016173628A - Terminal apparatus, operation diagnosis program, operation diagnosis method and computer - Google Patents

Abstract

PROBLEM TO BE SOLVED: To improve convenience for a user relevant to operation diagnosis considering a failure on a portable terminal.SOLUTION: A terminal apparatus 3 includes: a storage 130b which stores an execution history of plural application 1 to application N in an application execution frequency DB 63; and a self-diagnosis processing section 30 including an application operation diagnosis section 35 that executes operation diagnosis processing on an application the execution frequency of which exceeds a predetermined frequency in the plural applications based on the execution history at a predetermined timing.SELECTED DRAWING: Figure 3

Description

  The present invention relates to a terminal device, an operation diagnosis program, an operation diagnosis method, and a computer.

  A failure of an information processing terminal such as a smart device or a wearable terminal may be found when a user operates the information processing terminal by himself or when a self-diagnosis function of the information processing terminal is manually executed.

  A technique has been proposed in which a self-diagnosis is periodically performed so that the failure of the information processing terminal is not left until the user recognizes it, and if there is an abnormality, the diagnosis result is transmitted to an external server. ing.

  In order to perform self-diagnosis efficiently, the priority of self-diagnosis is set according to the operation frequency of each of the plurality of functional blocks, and each function is based on the set priority and the number of executable self-diagnosis. Techniques for performing self-diagnosis of blocks are known.

JP 2008-108111 A JP 2012-252373 A Japanese Patent No. 3880453 JP 2005-18199 A

  However, after the failure of the information processing terminal is discovered, the repair of the information processing terminal is started for the first time when the user brings it to the store or service base of the information processing terminal or sends it. Even if the user wants to use the terminal immediately, it may take a long time to complete the repair and use the information processing terminal.

  In particular, when a user detects a failure at a travel destination such as a business trip or a trip, it may take a while to complete the repair, and may hesitate to request a repair. In such a case, there is an inconvenience that the functions of the information processing terminal or the information processing terminal cannot be used at a business trip destination or a travel destination.

  Therefore, in one aspect, the present invention aims to improve the convenience of a user of a terminal device in consideration of a failure of the terminal device.

  According to one aspect, storage means for accumulating execution histories of a plurality of applications in the terminal device, and applications having an execution frequency equal to or higher than a predetermined frequency among the plurality of applications based on the execution history at a predetermined timing And a diagnostic processing means for executing an operation diagnostic process for the terminal device.

  Further, according to one aspect, receiving means for receiving an operation diagnosis result for an application selected from the plurality of applications based on an execution history of the plurality of applications in the terminal device accumulated in the terminal device; And determining means for determining whether or not the terminal device needs to be repaired or inspected based on the operation diagnosis result, and when it is determined that repair or inspection is necessary, the operation according to the operation diagnosis result Transmitting means for transmitting information relating to repair or inspection of the terminal device to the terminal device is provided.

  It is possible to improve the convenience of the user of the terminal device in consideration of the failure of the terminal device.

It is a figure which shows the network structural example of a repair system. It is a figure which shows the hardware constitutions of a portable terminal. It is a figure which shows the function structural example of a portable terminal. It is a figure which shows the data structural example of log DB. It is a figure which shows the example of a data structure of diagnostic time DB. It is a figure which shows the example of a data structure of application execution frequency DB. It is a figure which shows the data structural example of position information DB. It is a figure which shows the data structural example of operation | movement diagnostic result DB. It is a flowchart for demonstrating the operation | movement diagnostic process of a portable terminal. It is a flowchart for demonstrating the application operation | movement diagnostic process by the application operation | movement diagnosis part in FIG.9 S76. It is a figure which shows the hardware constitutions of a server. It is a figure which shows the function structural example of a server. It is a figure for demonstrating a server process.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. In this embodiment, the operation of an application with high execution frequency of an information processing terminal such as a smart device or a wearable terminal is diagnosed, and the information processing terminal is located around the position of the information processing terminal based on the position information when a failure is found. Enables efficient repair or inspection. As an information processing terminal, a mobile terminal will be described below as an example, but the information processing terminal is not limited to a mobile terminal.

  FIG. 1 is a diagram illustrating a network configuration example of a repair system. In a repair system 1000 shown in FIG. 1, a server 200, a parts center 300, a store 400, and one or more portable terminals 3 are connected via a network 2 (including the Internet). In the present embodiment, the store 400 may be a service base.

  The mobile terminal 3 includes a self-diagnosis processing unit 30 that diagnoses the operation of the mobile terminal 3 at a predetermined timing. In addition to sensor operation diagnosis, transmission / reception operation diagnosis, terminal operation diagnosis, and system state diagnosis, the self-diagnosis processing unit 30 preferentially performs application operation diagnosis on applications frequently used by the user.

  Diagnosis information 70 including a terminal management number 71, an operation diagnosis result 72 executed by the self-diagnosis processing unit 30, and position information 73 is transmitted to the server 200 of the integrated service center 100. The terminal management number 71 is identification information of the mobile terminal 3 that is managed by the server 200 in association with the model of the mobile terminal 3, information about the user of the mobile terminal 3, and the like. The operation diagnosis result 72 indicates the results of various operation diagnoses automatically performed by the mobile terminal 3, and details thereof will be described later with reference to FIG. The position information 73 is information indicating the current position of the mobile terminal 3.

  The integrated service center 100 includes a server 200, a parts center 300, a store 300, and the like. The server 200 may be installed at each site, or one server 200 may centrally manage the diagnostic information 70 collected from all the mobile terminals 3. Each of the parts center 300 and the store 300 has one or more information processing terminals and is connected to the Internet 2. In the present embodiment, each information processing terminal will be described as a parts center 300 and a store 300 without identifying each information processing terminal.

  The server 200 is a computer device, collects diagnostic information 70 from each portable terminal 3, selects the parts center 300 and the store 400 that are closest to the current position of the portable terminal 3, and arranges for repair or inspection. Process.

  That is, the server 200 discriminates parts necessary for repair or inspection from the operation diagnosis result 72 received from the mobile terminal 3, and the nearest parts center 300 storing the parts from the position information 73 of the mobile terminal 3. The store 400 is selected, and the date and time when the parts arrive is calculated.

  Thereafter, the server 200 notifies the user of the mobile terminal 3 of information regarding the repairable date and time and the information about the store 400 by e-mail, telephone, or the like. When the user desires to repair or check the portable terminal 3, a procedure for sending parts to the store 400 is performed, and the repair or inspection is performed.

  When the parts center 300 receives a parts sending instruction from the server 200, the parts center 300 performs a process related to sending the parts designated by the sending instruction to the store 400 designated by the sending instruction.

  The store 400 displays a repair request received in advance from the server 200 that matches the terminal management number 71 input in response to a visit for repairing or checking the user's mobile terminal 3 on the display unit. The portable terminal 3 is repaired using the parts sent from the parts center 300 based on the repair request.

  Since various processes performed by the server 200, the parts center 300, and the store 400 as described above can be realized by known techniques disclosed in Patent Literature 3 and Patent Literature 4, detailed description thereof is omitted.

  FIG. 2 is a diagram illustrating a hardware configuration of the mobile terminal. In FIG. 2, a mobile terminal 3 is an information processing terminal such as a tablet or a mobile phone controlled by a computer, and includes a CPU (Central Processing Unit) 11b, a main storage device 12b, and a user I / F (interface). 15b, positioning device 16b, communication I / F 17b, and drive device 18b, which are connected to bus B2.

  The CPU 11b is a processor that controls the portable terminal 3 according to a program stored in the main storage device 12b. A RAM (Random Access Memory), a ROM (Read Only Memory), or the like is used as the main storage device 12b. The program is executed by the CPU 11b, data necessary for processing by the CPU 11b, and obtained by processing by the CPU 11b. Store or temporarily store the data. Various processes are realized by the CPU 11b executing a program stored in the main storage device 12b.

  The user I / F 15b is a touch panel or the like that displays various types of information required under the control of the CPU 11b and that allows the user to input operations. The positioning device 16b receives signals from three or more GPS (Global Positioning System) satellites and measures the current location on the earth. Position information 73 indicating the current position of the mobile terminal 3 is stored in the position information DB (database) 32 (FIG. 3). Communication by the communication I / F 17b is not limited to wireless or wired.

  A program that realizes processing performed by the mobile terminal 3 is downloaded from an external device via the network 2. Or you may memorize | store in the main memory 12b of the portable terminal 3 previously.

  The drive device 18b performs an interface between a storage medium 19b (for example, an SD (Secure Digital) memory card) set in the drive device 18b and the portable terminal 3. The main storage device 12b and / or the storage medium 19b corresponds to the storage unit 130b.

  The portable terminal 3 may be an information processing terminal such as a desktop type, a notebook type, or a laptop type.

  FIG. 3 is a diagram illustrating a functional configuration example of the mobile terminal. 3, the mobile terminal 3 includes a self-diagnosis processing unit 30, and the storage unit 130 b includes an operation diagnosis result DB 61, a position information DB 62, an application execution frequency DB 63, a diagnosis time DB 64, a log DB 65, a plurality of applications 1, 2, ... N are stored. The plurality of applications 1, 2, etc. are applications already installed in the mobile terminal 3.

  The self-diagnosis processing unit 30 is a processing unit that performs an operation diagnosis of the mobile terminal 3, and is realized by the CPU 11b executing a corresponding program. The self-diagnosis processing unit 30 further includes a sensor operation diagnosis unit 31, a transmission / reception operation diagnosis unit 32, a terminal operation diagnosis unit 33, a system state diagnosis unit 34, an application operation diagnosis unit 35, and a diagnosis result notification unit 36. Have

  The sensor operation diagnosis unit 31 diagnoses the operation of the mobile terminal 3 such as GPS (Global Positioning System), network communication, Wi-Fi, Bluetooth (registered trademark). The transmission / reception operation diagnosis unit 32 diagnoses transmission / reception operations of Web data, e-mail, and the like. The terminal operation diagnosis unit 33 diagnoses the operation of the terminal such as screen display, sound, and vibrator. The system status diagnosis unit 34 diagnoses the system status such as the usage status of the CPU 11b and the main storage device 12b.

The application operation diagnosis unit 35 confirms logs of applications 1, 2,... N (hereinafter simply referred to as “application i” (i = 1, 2,... N)). The log is stored for each application i and stored in the corresponding log DB 65 _i (i = 1, 2,... N) for each application i.

Log confirmation of the application 1 is carried out using the log DB65 _1, log confirmation of the application 2 is performed using the log-DB65 _2, ···, log confirmation of the application N, using the log DB65 _N line Is called. The log DB 65 _i may be collectively referred to as “log DB 65”.

  Further, in the application operation diagnosis process for the application i by the application operation diagnosis unit 35, the past activation state is stored in the application execution frequency DB 63 to determine the execution frequency, and the application having an execution frequency higher than a predetermined threshold value. Let i be a diagnostic target. Alternatively, the application i to be diagnosed by the user may be selected.

The application operation diagnosing unit 35 totals the time from the start-up to shutdown of the previous month from the log DB 65 _i of each application i, and obtains the execution frequency of each application i by calculating the total value of the start-up time of the previous month. And stored in the application execution frequency DB 63. In the present embodiment, the application i that is always required by the user is determined by setting the frequency of execution, not the number of activations of each application i, that is, that is, the total of operating time.

  The diagnosis time DB 64 stores the date and / or time of diagnosis designated in advance or the date and / or time for regular diagnosis. Further, a predetermined threshold time may be stored.

In addition, application operation diagnosis unit 35 searches whether or not the record of error of system startup fail, such as the diagnosis date and time from the log DB65 _i of the installed application i exist, normal operation if there is no error in the record, the error If there is a record, the operation failure is stored in the operation diagnosis result DB 61. One or more pieces of information regarding normal operation or operation failure regarding error recording are managed in the operation diagnosis result DB 61 in association with the date on which automatic diagnosis is performed.

  When the execution frequency indicated by the total value of the activation times of the previous month stored in the application execution frequency DB 63 is longer than the threshold time at the diagnosis date and time specified in advance or the date and time for periodic diagnosis In addition, an application operation diagnosis process is performed on the application i. Further, the application operation diagnosis unit 35 performs the application operation diagnosis process for the application i designated in advance by the user regardless of whether the application operation diagnosis process based on the threshold time is necessary.

  The diagnosis result notifying unit 36 transmits the diagnosis results obtained by the sensor operation diagnosis unit 31, the transmission / reception operation diagnosis unit 32, the terminal operation diagnosis unit 33, the system state diagnosis unit 34, and the application operation diagnosis unit 35 to the server 200 of the integrated service center 100. And notify the user.

  The diagnosis result notifying unit 36 transmits the diagnosis information 70 indicating the terminal management number 71, the operation diagnosis result 72 of the operation diagnosis result DB 61, the position information 73 acquired by the positioning device 16b, and the like via the network 2 by the communication I / F 17b. It transmits to the server 200 of the integrated service center 100. The diagnosis result notifying unit 36 notifies the user by displaying the operation diagnosis result 72 on the user I / F 15b and sending it to the user by e-mail.

Next, a data configuration example of the databases 61 to 65 will be described with reference to FIGS. FIG. 4 is a diagram illustrating a data configuration example of the log DB. In FIG. 4, the log DB 65 _i is a database prepared for each application i and storing the operation state of the application i in time series in a predetermined log data format.

  The predetermined log data format is, for example, “month day hour: minute: second operation: result”. “Dec 16 11:15:45 init: system startup now.” Indicates that “the system of application i has been started by the initialization operation at 11:15:45 on December 16”. “Dec 16 11:24:30 init: system shutdown now.” Indicates that “the system of application i has been shut down due to the initialization operation at 11:24:30 on December 16”. . Furthermore, “Dec 17 13:05:15 init: system startup fail.” Indicates that “the system i application startup failed due to the initialization operation on December 17, 13:05:20”. ing.

  FIG. 5 is a diagram illustrating a data configuration example of the diagnosis time DB. In FIG. 5, the diagnosis time DB 64 is a database that stores the date and time of the operation diagnosis process performed by the self-diagnosis processing unit 30. The diagnosis time DB 64 stores designated diagnosis date and time, periodic diagnosis date and time, threshold time, and the like.

  In FIG. 5, it is indicated that the designated diagnosis date and time is 00:00:00 on December 25, 2014. Further, it is shown that the regular diagnosis date and time is 03:00:00 on every Sunday. Furthermore, the threshold time is 10:00:00.

  FIG. 6 is a diagram illustrating a data configuration example of the application execution frequency DB. In FIG. 6, the application execution frequency DB 63 is a database that manages the total time that each application i has been operating for a predetermined period (for example, the immediately preceding month), and includes items such as an application name and an execution frequency.

  The application name indicates information that can identify the already installed applications 1, 2,... N. The execution frequency indicates the total time (total operation time) that the application i has operated during a predetermined period, calculated by the application operation diagnosis unit 35. The predetermined period is, for example, the previous month.

The application operation diagnosing unit 35 refers to the log DB 65 _i corresponding to each application i having the data configuration shown in FIG. 4 and totals the time from the start-up to the shutdown of the previous month, thereby Calculate the total time. The calculated operation time total is stored in the application execution frequency DB 63.

  FIG. 6 shows an example of data for the past month. For example, during one month from November 1st to 30th, 2014, at least the application 1 is started at “2014/11/01 15:28:35” and “2014/11/02 10:13:56” Then, it can be seen that the application 2 is activated at “2014/11/30 23:42:10” and the application N is activated at “2014/11/02 08:11:24”.

  FIG. 7 is a diagram illustrating a data configuration example of the position information DB. In FIG. 7, the position information DB 62 is a database that stores position information indicating the current position of the mobile terminal 3 in time series, and includes items such as date and time, latitude and longitude. The date and time indicate the date and time when the current position is measured. The longitude and latitude indicate the result of positioning based on signals received by the positioning device 16b from a plurality of GPS satellites.

  In FIG. 7, for example, the current position at 10:12:41 on November 29, 2014 is longitude and latitude (35.658xx, 139.7454yy), and at 14:51:19 on December 01, 2014. The current position at is latitude and longitude (35.6813xx, 139.7660yy), and the current position at 08:31:27 on December 02, 2014 is longitude and latitude (35.5313xx, 139.6968yy).

  FIG. 8 is a diagram illustrating a data configuration example of the operation diagnosis result DB. In FIG. 8, the operation diagnosis result DB 61 is a database that stores various operation diagnoses performed by the self-diagnosis processing unit 30. As for the applications 1, 2,..., N already installed in the storage unit 130b, the result of the application i that has been subjected to the application operation diagnosis process for diagnosing the operation of the application i is stored.

  In FIG. 8, on December 01, 2014, the operation diagnosis is performed on the applications 2,... On December 01, 2014, the result of the application operation diagnosis process for the application 1 is not shown. This indicates that application operation diagnosis processing has not been performed for application 1.

  On December 02, 2014, an operation diagnosis is performed on the applications 1, 2,..., N, indicating that all operations were normal. On December 02, 2014, the result of the application operation diagnosis process for the application 1 is shown.

  On December 03, 2014, the operation diagnosis is performed on the applications 1, 2,..., N, and all the applications other than the application 2 are operating normally. The result of the application operation diagnosis process for the application 2 on December 03, 2014 indicates an operation failure.

  In addition, at least during the period from December 01, 2014 to December 03, 2014, the sensor operation, the transmission / reception operation, and the system state indicate normal operation.

  The operation diagnosis process by the self-diagnosis processing unit 30 of the portable terminal 3 will be described with reference to FIG. FIG. 9 is a flowchart for explaining the operation diagnosis process of the mobile terminal. In FIG. 9, the self-diagnosis processing unit 30 determines whether it is the activation of the portable terminal 3, the designated diagnosis date and time, or the regular diagnosis date and time (step S71). The activation of the portable terminal 3 corresponds to when the power is turned on. If the mobile terminal 3 is not activated, it is determined whether or not the current date and time has reached the designated diagnosis date or periodic diagnosis date and time stored in the diagnosis time DB 64. If none of these apply (No in Step S71), the self-diagnosis processing unit 30 repeats Step S71 at a predetermined interval.

  When one of them is satisfied (Yes in step S71), the sensor operation diagnosis unit 31 of the self-diagnosis processing unit 30 diagnoses the operation of various sensors, and stores normal operation or operation failure of the sensor operation in the operation diagnosis result DB 61. (Step S72).

  The transmission / reception operation diagnosis unit 32 of the self-diagnosis processing unit 30 diagnoses the transmission / reception operation, and stores normal operation or operation failure of the transmission / reception operation in the operation diagnosis result DB 61 (step S73). The terminal operation diagnosis unit 33 of the self-diagnosis processing unit 30 diagnoses the terminal operation, and stores normal operation or operation failure of the terminal operation in the operation diagnosis result DB 61 (step S74). The system state diagnosis unit 34 of the self-diagnosis processing unit 30 diagnoses the system state, and stores normal operation or operation failure of the terminal operation in the operation diagnosis result DB 61 (step S75).

  The application operation diagnosis unit 35 of the self-diagnosis processing unit 30 performs application operation diagnosis processing for diagnosing the operation of the application, and stores normal operation or operation failure of the application operation in the operation diagnosis result DB 61 (step S76). The application operation diagnosis process will be described with reference to FIG. The processing order of steps S72 to S76 is not limited to the order described above.

  Thereafter, in the self-diagnosis processing unit 30, the diagnosis result notifying unit 36 acquires the operation diagnosis result 72 from the operation diagnosis result DB 61 (step S77), acquires the current position information from the positioning device 16b (step S78), It is determined whether or not the current position information 73 has been acquired (step S79).

  When the current position information cannot be acquired (No in Step S79), the diagnosis result notifying unit 36 acquires the previous position information from the position information DB 62 and sets it as the current position information 73 (Step S80). On the other hand, when the current position information 73 can be acquired (Yes in step S79), the diagnosis result notifying unit 36 stores the acquired position information 73 in the position information DB 62 (step S81).

  After step S80 or S81, the diagnostic result notifying unit 36 creates diagnostic information 70 and transmits it to the server 200 of the integrated service center 100 (step S82). The diagnostic result notifying unit 36 creates diagnostic information 70 indicating the terminal management number 71 of the mobile terminal 3, the operation diagnostic result 72, and the position information 73, and transmits the diagnostic information 70 to the server 200.

  The diagnosis result notification unit 36 displays the operation diagnosis result 72 on the user I / F 15b and notifies the user (step S83). The processing order of steps S82 and S83 is not limited. The process of step S83 for notifying the user may be performed before step S82. After steps S82 and S83, the self-diagnosis processing unit 30 returns to step S71, and repeats the same process described above while the mobile terminal 3 is operating (the mobile terminal 3 is not turned off).

  FIG. 10 is a flowchart for explaining the application operation diagnosis process by the application operation diagnosis unit in step S76 of FIG. In FIG. 10, the application operation diagnosis unit 35 selects one of the applications 1 to N installed in the storage unit 130b in order, and sets it as the application i (step S761).

  The application operation diagnosis unit 35 acquires the execution frequency of the application i from the application execution frequency DB 63 (step S762), and acquires a threshold time (for example, “10:00:00” (FIG. 5)) from the diagnosis time DB 64 ( Step S763).

  The application operation diagnosis unit 35 determines whether or not the execution frequency of the application i indicates a time longer than the threshold time (step S764). If the execution frequency of the application i is equal to or less than the threshold time (No in step S764), it is determined whether or not the application i is a diagnosis target (step S765). Whether or not the application i is a diagnosis target is determined by referring to setting information set in advance by the user. If the application i is not a diagnosis target (No in step S765), the application operation diagnosis unit 35 proceeds to step S770.

  When the application i is a diagnosis target (Yes in step S765), the application operation diagnosis unit 35 proceeds to step S766. Even if the execution frequency of the application i is equal to or less than the threshold time, the setting by the user is prioritized and the operation diagnosis of the application i is performed.

In the case of Yes in step S764, the application operation diagnosis unit 35 searches the log DB 65 _{i of the} application i for a record of an error related to activation based on the current date (that is, the diagnosis date) (step S766). The error record is, for example, system startup fail.

  Then, the application operation diagnosis unit 35 determines whether or not an error record has been retrieved (step S767). If the error record cannot be retrieved, the application operation diagnosis unit 35 stores the operation failure regarding the application i in the operation diagnosis result DB 61 (step S768), and proceeds to step S770.

  On the other hand, if the error record can be retrieved, the application operation diagnosis unit 35 stores the normal operation for the application i in the operation diagnosis result DB 61 (step S768), and proceeds to step S770.

After step S765, S768, or S769, the application operation diagnosis unit 35 calculates the execution frequency of a predetermined period (for example, the previous month) using the log DB 65 _{i of the} application i and stores it in the application execution frequency DB 63 ( Step S770). Application operation diagnosis unit 35, counts the time from the log DB65 _i until the shutdown from the previous month of the start up, to get the execution frequency of application i by calculating the total value of the previous month of the start-up time, application execution frequency DB63 To store.

  Then, the application operation diagnosis unit 35 determines whether or not the applications 1 to N have been completed (step S771). If the above-described processing has not been completed for all the applications 1 to N (No in step S771), the application operation diagnosis unit 35 returns to step S761 and repeats the above-described processing. On the other hand, when the above-described processing is completed for all the applications 1 to N (Yes in step S771), the application operation diagnosis unit 35 ends this application operation diagnosis processing.

  Next, the server 200 will be described. The server 200 has a hardware configuration as shown in FIG. FIG. 11 is a diagram illustrating a hardware configuration of the server. In FIG. 11, a server 200 is an information processing device controlled by a computer, and includes a CPU 11a, a main storage device 12a, an auxiliary storage device 13a, an input device 14a, a display device 15a, a communication I / F ( Interface) 17a and drive device 18a, which are connected to bus B1.

  The CPU 11a controls the server 200 according to a program stored in the main storage device 12a. A RAM (Random Access Memory), a ROM (Read Only Memory), or the like is used as the main storage device 12a. The program is executed by the CPU 11a, the data necessary for processing by the CPU 11a, and is obtained by processing by the CPU 11a. Store or temporarily store the data.

  The auxiliary storage device 13a uses an HDD (Hard Disk Drive) or the like, and stores data such as programs for executing various processes. A part of the program stored in the auxiliary storage device 13a is loaded into the main storage device 12a and executed by the CPU 11a, thereby realizing various processes. The main storage device 12a and the auxiliary storage device 13a correspond to the storage unit 130a.

The input device 14 a includes a mouse, a keyboard, and the like, and is used by an operator to input various information necessary for processing by the server 200. The display device 15a displays various information necessary under the control of the CPU 11a. The input device 14a and the display device 15a may be a user interface such as an integrated touch panel. The communication I / F 17a performs communication through a wired or wireless network. Communication by the communication I / F 17a is not limited to wireless or wired communication.
A program for realizing the processing performed by the server 200 is provided to the server 200 by a storage medium 19a such as a CD-ROM (Compact Disc Read-Only Memory).

  The drive device 18a performs an interface between the storage medium 19a (for example, a CD-ROM) set in the drive device 18a and the server 200.

  Further, a program for realizing various processes according to the present embodiment to be described later is stored in the storage medium 19a, and the program stored in the storage medium 19a is installed in the server 200 via the drive device 18a. . The installed program can be executed by the server 200.

  The storage medium 19a for storing the program is not limited to a CD-ROM, and one or more non-transitory tangible media having a structure that can be read by a computer. If it is. As a computer-readable storage medium, in addition to a CD-ROM, a portable recording medium such as a DVD disk or a USB memory, or a semiconductor memory such as a flash memory may be used.

  FIG. 12 is a diagram illustrating a functional configuration example of the server. In FIG. 12, the server 200 includes a reception unit 241, a determination unit 242, a transmission unit 243, and an arrangement unit 244, and a registration list 271 is stored in the storage unit 130a.

  When receiving the diagnostic information 70 transmitted from the mobile terminal 3 via the communication I / F 17a, the receiving unit 241 notifies the determining unit 242 of the diagnostic information 70. The determination unit 242 determines the operating state of the mobile terminal 3 with reference to the operation diagnosis result 72 of the diagnosis information 70 notified from the reception unit 241. The determination unit 242 notifies the transmission unit 243 of the diagnostic information 70 when the operation diagnosis result 72 has an operation failure.

  The transmission unit 243 transmits a confirmation e-mail 8a for confirming whether or not the user desires repair or inspection via the communication I / F 17b, thereby confirming whether or not there is a request from the user transmitted from the mobile terminal 3. The reply e-mail 8b shown is received via the communication I / F 17b (step S243). When the reply e-mail 8b determines that the user desires repair or inspection, the transmission unit 243 notifies the diagnosis information 70 and the repair or inspection information related to the repair or inspection.

  In situations where the user is outside the daily life zone such as on a business trip or traveling, the user may want to repair or check after returning to daily life. In this case, the user may send a reply that does not require repair or inspection.

  Even in situations where the user is out of daily life such as on a business trip or traveling, if the application that has failed in operation is an application that he / she wishes to continue to use, the user may desire immediate repair or inspection. In this case, the user may send a reply requesting repair or inspection.

  As described above, in this embodiment, the user can repair or check a necessary application at an appropriate timing according to the convenience of the user.

  The arrangement unit 244 creates the parts delivery data 9a based on the diagnostic information 70 and the repair or inspection information, transmits the parts delivery data 9a to the parts center 300, and creates the repair request data 9b, so that the store 400 (or To the service location.

  Next, server processing performed by the server 200 will be described with reference to FIG. FIG. 13 is a diagram for explaining server processing. The server processing described below is realized by the CPU 11a of the server 100 executing a corresponding program.

  In FIG. 13, in the server 200, the receiving unit 241 determines whether or not the diagnostic information 70 has been received from the portable terminal 3 (step S201). When the diagnostic information 70 has not been received (No in step S201), the receiving unit 241 performs step S201 at a predetermined interval. On the other hand, when the diagnostic information 70 is received (Yes in step S201), the reception unit 241 notifies the determination unit 242 of the received diagnostic information 70.

  Upon receiving the notification of the diagnostic information 70, the determination unit 242 determines whether or not there is an operation failure in the operation diagnosis result 72 (step S202). When there is no operation failure in the operation diagnosis result 72 (No in Step S202), the determination unit 242 returns to Step S201 and repeats the same processing as described above. On the other hand, when there is an operation failure in the operation diagnosis result 72 (Yes in step S202), the determination unit 242 resets the state flag of the device indicating the operation failure (step S203). Then, the determination unit 242 notifies the transmission unit 243 of the diagnostic information 70.

  In response to the notification of the diagnosis information 70, the transmission unit 243 determines a part to be repaired or inspected based on the operation diagnosis result 72 (step S204). Further, the transmission unit 243 searches the registration list 271 for a parts center and a store (or service base) based on the position information 73 of the diagnostic information 70 (step S205). The registration list 271 stores the location, contact information, and the like of each parts center 300 and each store 400 (or service base).

  The transmission unit 243 determines whether or not the parts center 300 and the store 400 (or service base) close to the position information 73 can be searched from the registration list (step S206). When the search cannot be performed (No in Step S206), the transmission unit 243 displays and / or prints various information based on the diagnostic information 70 (Step S207). Thereafter, the server 200 ends this server process. In this case, based on the output of various information based on the diagnostic information 70, the operator contacts the user, etc., whether there is a request for repair, the dealer 400 (or service base) that can handle the repair, the repair date and time, etc. Confirmation and necessary procedures are performed.

  If the search is successful (Yes in step S206), the transmission unit 243 calculates the arrival date and time of the parts (step S208).

  Then, the transmission unit 243 transmits a confirmation e-mail confirming whether or not repair or inspection is desired to the user who has transmitted the diagnostic information 70, thereby requesting repair or inspection from the user's portable terminal 3. A reply e-mail indicating the presence or absence is received (step S209).

  The transmission unit 243 determines whether or not the user desires repair or inspection (step S210). When the user does not desire repair or inspection (No in step S210), the server 200 ends the server process. On the other hand, when the user desires repair or inspection (Yes in step S210), the transmission unit 243 notifies the arrangement unit 244 of the diagnosis information 70 and the repair or inspection information related to the repair or inspection.

The repair or inspection information includes information on parts to be repaired or inspected, information on the parts center 300, information on the dealer 400 (or service base), information on arrival date and time when the parts arrive at the dealer 400 (or service base), etc. Is included.
In response to the diagnosis information 70 and the notification of the repair or inspection information related to the repair or inspection, the arrangement unit 244 creates the part delivery data 9a related to the delivery of the part to be repaired or inspected determined in step S204, and searches in step S205. It transmits to the parts center 300 which has done (step S211).

  In addition, the arrangement unit 244 creates repair request data 9b relating to a part indicating an operation failure in the operation diagnosis result 72, and transmits the repair request data 9b to the store 400 (or service base) searched in step S205 (step S212). In the operation diagnosis result 72, if there is an application i that has failed in operation, the application i is specified in the repair request data. Then, the server 200 ends this server process.

  As described above, in the present embodiment, the operation of an application having a high execution frequency of a plurality of installed applications 1 to N is self-diagnosed. Therefore, even when the user of the mobile terminal 3 does not notice the failure, the user can easily recognize the failure by notifying the user of the operation diagnosis result 72.

  In addition, the server 200 is notified of the terminal management number 71, the operation diagnosis result 72, and the position information 73, and the server 200 indicates the baht center 300 and the store 400 (or service base) close to the current position of the user. select. Therefore, since the user can perform repairs during business trips and during travel, the user can avoid situations where the mobile terminal 3 cannot be used during business trips or travel.

  The present invention is not limited to the specifically disclosed embodiments, and can be principally modified and changed without departing from the scope of the claims.

The following additional notes are further disclosed with respect to the embodiment including the above examples.
(Appendix 1)
Storage means for accumulating execution histories of a plurality of applications in the terminal device;
Diagnostic processing means for executing an operation diagnostic process for an application having an execution frequency equal to or higher than a predetermined frequency among the plurality of applications based on the execution history at a predetermined timing;
The terminal device characterized by having.
(Appendix 2)
The diagnostic processing means includes
In the operation diagnosis process, it is determined whether or not there is an error record related to activation in the log of the application whose execution frequency is the predetermined frequency or more. If there is an error record, the application diagnoses that the operation has failed. The terminal device according to supplementary note 1, wherein:
(Appendix 3)
The diagnostic processing means includes
In the operation diagnosis process, when there is no error record, it is determined whether or not the application is set as a diagnosis target, and when the application is set as a diagnosis target, the operation diagnosis process The terminal device according to supplementary note 2, wherein the terminal device is executed.
(Appendix 4)
The diagnostic processing means includes
4. The execution frequency is calculated by referring to the execution history and totaling the time from the start to the end of the operation of the application in a predetermined period. 5. Terminal device.
(Appendix 5)
Accumulate execution history of multiple applications,
At a predetermined timing, based on the execution history, an operation diagnosis process is executed for an application whose execution frequency is equal to or higher than a predetermined frequency among the plurality of applications.
An operation diagnosis program for causing a computer to perform processing.
(Appendix 6)
Accumulate execution history of multiple applications,
At a predetermined timing, based on the execution history, an operation diagnosis process is executed for an application whose execution frequency is equal to or higher than a predetermined frequency among the plurality of applications.
An operation diagnosis method, characterized in that the processing is performed by a computer.
(Appendix 7)
Receiving means for receiving an operation diagnosis result for an application selected from the plurality of applications based on an execution history of the plurality of applications in the terminal device accumulated in the terminal device;
A determination means for determining whether the terminal device needs to be repaired or inspected based on the received operation diagnosis result;
When it is determined that repair or inspection is necessary, transmission means for transmitting information related to repair or inspection of the terminal device according to the operation diagnosis result to the terminal device;
A computer comprising:

2 Internet 3 Mobile terminal 8a Confirmation e-mail, 8b Reply e-mail 9a Parts delivery data, 9b Repair request data 11a CPU, 12a Main storage device 13a Auxiliary storage device, 14a Input device 15a Display device, 17a Communication I / F
18a drive device, 19a storage device 11b CPU, 12b main storage device 15b user I / F, 16b positioning device 17b communication I / F, 18b drive device 19b storage medium 30 self-diagnosis processing unit 31 sensor operation diagnosis unit, 32 transmission / reception operation diagnosis Unit 33 terminal operation diagnosis unit 34 system state diagnosis unit 35 application operation diagnosis unit 36 diagnosis result notification unit 61 operation diagnosis result DB 62 position information DB
63 App execution frequency DB, 64 Diagnosis time DB
65,65 _i log DB
70 diagnostic information,
71 Terminal management number, 72 Operation diagnosis result 73 Location information 100 Integrated service center 130a Storage unit, 130b Storage unit 200 Server 300 Parts center 400 Dealer

Claims (6)

Storage means for accumulating execution histories of a plurality of applications in the terminal device;
Diagnostic processing means for executing an operation diagnostic process for an application having an execution frequency equal to or higher than a predetermined frequency among the plurality of applications based on the execution history at a predetermined timing;
The terminal device characterized by having. The diagnostic processing means includes
In the operation diagnosis process, it is determined whether or not there is an error record related to activation in the log of the application whose execution frequency is the predetermined frequency or more. If there is an error record, the application diagnoses that the operation has failed. The terminal device according to claim 1. The diagnostic processing means includes
In the operation diagnosis process, when there is no error record, it is determined whether or not the application is set as a diagnosis target, and when the application is set as a diagnosis target, the operation diagnosis process The terminal device according to claim 2, wherein: Accumulate execution history of multiple applications,
At a predetermined timing, based on the execution history, an operation diagnosis process is executed for an application whose execution frequency is equal to or higher than a predetermined frequency among the plurality of applications.
An operation diagnosis program for causing a computer to perform processing. Accumulate the execution history of multiple applications,
At a predetermined timing, based on the execution history, an operation diagnosis process is executed for an application whose execution frequency is equal to or higher than a predetermined frequency among the plurality of applications.
An operation diagnosis method, characterized in that the processing is performed by a computer. Receiving means for receiving an operation diagnosis result for an application selected from the plurality of applications based on an execution history of the plurality of applications in the terminal device accumulated in the terminal device;
A determination means for determining whether the terminal device needs to be repaired or inspected based on the received operation diagnosis result;
When it is determined that repair or inspection is necessary, transmission means for transmitting information related to repair or inspection of the terminal device according to the operation diagnosis result to the terminal device;
A computer comprising:

Images