JP2011138461A - Failure information management system, portable terminal device, server and method for managing failure information, program and recording medium - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a failure information management system which can collect when occurrence of a failure of a portable terminal device, information effective for analysis of the failure without a significant rise of load. <P>SOLUTION: When the failure occurs in the portable terminal device 2, failure information containing at least the model name of the portable terminal device 2, the content of the failure, and the state of the failure occurrence part is transmitted to the failure information management server 3 as a failure occurrence report. The failure information management server 3 periodically transmits, upon receipt of the failure occurrence report, a broadcast message for instructing a collection start condition of detailed data for analysis of the failure occurring in the portable terminal device 2 from a base station 6 covering the area where the portable terminal device 2 is present through a broadcast message center 4. The portable terminal device 2 starts collection of detailed data for failure analysis according to the collection start condition instructed by the received broadcast message, and transmits, when the next failure occurs, the collected detailed data to the failure information management server 3 as failure analysis information. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention relates to a failure information management system, a mobile terminal device, a failure information management server, a failure information management method, a failure information management program, and a program recording medium.

  The software of the mobile terminal device has become multifunctional and high performance year by year, and it is possible to provide the user with a convenient mobile terminal device, but the software is also very complicated. In addition, there is a high risk of occurrence of malfunctions, which may cause uncomfortable feelings to the user due to unintentional power interruptions, resets, and communication interruptions after sales.

  When such a failure occurs, the user of the mobile terminal device usually contacts the retailer of the mobile terminal device as a complaint, and the retailer that received the complaint replaces it with a new mobile terminal device. In addition to passing to the user, the mobile terminal device in which the failure has occurred is sent to the manufacturer of the mobile terminal device, and the manufacturer attempts to analyze the failure by analyzing the information inside the mobile terminal device. Yes.

  However, in particular, problems related to the wireless communication function of the mobile terminal device often occur only under conditions such as the cell parameter setting of the wireless base station and a specific communication state, and the failure analysis is often performed. There are many cases where it is extremely difficult.

  In order to solve this problem, it is described in Japanese Patent Application Laid-Open No. 8-237188 “Communication System and Communication Method” in Patent Document 1 and Japanese Patent Application Laid-Open Publication No. 2003-179541 “Mobile Phone Terminal Failure Notification System” in Patent Document 2. A failure analysis method has been proposed. According to these failure analysis methods, internal information for failure analysis (hereinafter referred to as failure analysis information) accumulated in advance in the mobile terminal device after the occurrence of a failure can be sent to the failure analysis server. The developer of the mobile terminal device can analyze a failure based on the collected internal information for failure analysis.

JP-A-8-237188 (page 5-6) JP 2003-179541 A (page 4)

  However, in the case of the failure analysis methods described in Patent Document 1 and Patent Document 2, in general, failure analysis based on predetermined collection conditions is possible even though it is not known in which part the failure occurs. There is a high possibility that detailed information effective for performing failure analysis cannot be collected for such troubles occurring in the portable terminal device only by storing the business information in the portable terminal device. In addition, since the failure analysis information is constantly accumulated, there is a problem that a load is applied to a processing unit (CPU: Central Processing Unit) of the mobile terminal device and battery consumption is accelerated.

  The present invention has been made in view of such circumstances, and when a failure of the mobile terminal device occurs, information effective for analysis of the failure occurring in the mobile terminal device is greatly increased in load on the mobile terminal device. An object of the present invention is to provide a failure information management system, a portable terminal device, a failure information management server, a failure information management method, a failure information management program, and a program recording medium that can be collected without being increased. .

  In order to solve the above-described problems, the fault information management system according to the present invention employs the following characteristic configuration.

  (1) A failure information management system comprising at least a mobile terminal device that performs wireless communication with a base station, and a failure information management server that collects and manages information for analyzing a failure of the mobile terminal device In the case where a failure occurs in the portable terminal device, the portable terminal device includes a model name indicating the model of the own portable terminal device, a failure content indicating the content of the failure that has occurred, a communication type at the time of the failure, and a location where the failure has occurred A failure information management system for transmitting failure information including at least a state of a failure occurrence site as a failure occurrence notification to the failure information management server.

  According to the fault information management system, portable terminal device, fault information management server, fault information management method, fault information management program, and program recording medium of the present invention, the following effects can be obtained.

  First, since failure information and failure analysis information related to the mobile terminal device can be collected only in a specific base station covering the area where the mobile terminal device in which the failure has occurred is present, for example, different base station areas Even under conditions where the possibility of failure is low, it is possible to avoid a situation in which the operating rate of the processing unit (CPU) of the mobile terminal device increases by trying to collect failure information, Thus, battery consumption of the mobile terminal device can be suppressed.

  Second, since the conditions for collecting the failure analysis information can be changed according to the failure that has occurred and can be set to an appropriately limited condition, as in the case of the first effect, Battery consumption can be suppressed.

  Thirdly, when a plurality of mobile terminal devices exist in the area of the fault information management system, the fault information is collected each time the fault information collection condition specified by the fault information management server is satisfied in each of the plurality of mobile terminal devices. Since detailed data is collected as failure analysis information, the number of samples of failure analysis information increases, and even for failures with low reproducibility at specific base stations, effective data can be collected as failure analysis information. The possibility increases.

  Fourth, when a mobile terminal device in which a failure occurs moves from an area (cell area) covered by the base station that has collected detailed failure information data as failure analysis information to a cell area of another base station ( In other words, when a handover between base stations occurs), the failure information collection conditions in the base station so far are discarded together with the collected failure analysis information. Accordingly, useless information for failure analysis is not collected, and thus the memory consumption in the mobile terminal device can be suppressed.

  Fifth, since the transmission destination address for sending failure information and failure analysis information can be changed for each area where the mobile terminal device exists and for each model of the mobile terminal device, for example, a plurality of failure information management servers are provided. Install a separate failure information management server that sends failure information and failure analysis information for each area where the mobile terminal device exists or for each model of the mobile terminal device, and load on the failure information management server Can be dispersed.

It is a system configuration figure showing an example of a system configuration of a failure information management system concerning the present invention. It is a block block diagram which shows an example of an internal structure of the portable terminal device applied to the failure information management system of FIG. It is a block block diagram which shows one form of an internal structure at the time of expressing paying attention to the function for failure information management in the portable terminal device shown in FIG. It is a block block diagram which shows an example of an internal structure of the failure information management server applied to the failure information management system of FIG. It is a sequence chart which shows an example of the flow of the signal in the initial state of the failure information management system which concerns on this invention. It is a sequence chart which shows an example of the flow of a signal when a failure generate | occur | produces in the portable terminal device of the failure information management system which concerns on this invention. It is a flowchart which shows an example of the flow of operation | movement of the said portable terminal device when the portable terminal device of the failure information management system which concerns on this invention changes to a data storage standby state. It is a sequence chart which shows an example of the flow of a signal when a failure generate | occur | produces in the said portable terminal device when the portable terminal device of the failure information management system which concerns on this invention exists in the data accumulation state. The sequence which shows an example of the signal flow when the portable terminal device of the failure information management system according to the present invention is in the data storage standby state or the data storage state and a handover across the base stations occurs in the mobile terminal device It is a chart. 3 is a table showing an example of a CBS message created at a broadcast message center in the failure information management system of FIG. It is a table which shows an example of the failure generation | occurrence | production notification produced with the portable terminal device in the failure information management system of FIG. 6 is a table showing another example of a CBS message created at a broadcast message center in the failure information management system of FIG. 3 is a table showing an example of failure analysis information notification transmitted from the mobile terminal device to the failure information management server in the failure information management system of FIG. 1.

  Preferred embodiments of a failure information management system, a mobile terminal device, a failure information management server, a failure information management method, a failure information management program, and a program recording medium according to the present invention will be described below with reference to the accompanying drawings. In the following description, a fault information management system, a mobile terminal device, a fault information management server, and a fault information management method according to the present invention will be described. The fault information management method is executed as a fault information management program that can be executed by a computer. Needless to say, the failure information management program may be recorded on a computer-readable recording medium.

(Features of the present invention)
Prior to the description of the embodiments of the present invention, an outline of the features of the present invention will be described first. The present invention relates to a W-CDMA (Wideband-Code Division Multiple Access) or GSM (Global System for Mobile Communications) mobile phone, a PHS (Personal Handy-phone System) terminal, a personal digital assistant (PDA). A mechanism capable of efficiently collecting information for analysis related to failures and malfunctions of mobile terminal devices such as the above is realized.

  More specifically, the fault information management system according to the present invention has a configuration as shown in FIG. FIG. 1 is a system configuration diagram showing an example of a system configuration of a failure information management system according to the present invention.

  A failure information management system 1 shown in FIG. 1 includes a mobile terminal device 2 such as a mobile phone having a wireless communication function, a PHS terminal, or a personal digital assistant (PDA), and each mobile terminal device 2 to a mobile terminal device 2. Failure information management server 3 that manages the received failure information, a broadcast message center (BMC) 4 that broadcasts a CBS (Cell Broadcast System) message, that is, a broadcast message, a base station 6, 7 and 8 are connected to the mobile phone network and the Internet network 9 to perform wireless communication with the mobile terminal device 2 and the exchange 5 that routes data such as failure information and failure analysis information to the failure information management server 3. It comprises at least base stations 6, 7, and 8 that are connected to the mobile phone network.

  Here, the mobile terminal device 2 has a CBS message receiving function, and can receive a CBS message distributed by the broadcast message center 4 through the exchange 5 and the base station 6.

  The failure information management server 3 is connected to the broadcast message center 4 and the switching center 5 through the Internet network 9 or a dedicated line (shown in FIG. 1 shows the case of the Internet network 9). It is possible to request the center 4 to transmit a CBS message, or to receive failure information, failure analysis information, and the like from the mobile terminal device 2 via the switching center 5. Possesses a mass storage device for retaining failure information, failure analysis information, etc., or is connected to a mass storage device installed outside.

  In the failure information management system 1 shown in FIG. 1, the mobile terminal device 2 in which a failure such as a power failure, reset, or communication failure has occurred indicates failure information such as the failure content, communication state at that time, model name, etc. 3 is notified. The failure information management server 3 stores the failure information received from the mobile terminal device 2 in a large-capacity storage device, and a specific base station (base station 6 in the case of FIG. 1) is sent via the broadcast message center 4. The failure information received from the mobile terminal device 2 is collected as failure information collection start conditions (that is, detailed data for analyzing the failure is collected as failure analysis information for all the mobile terminal devices existing in the covered area. As a condition for starting the operation, broadcast distribution is performed using a CBS message.

  The plurality of portable terminal devices including the portable terminal device 2 located in the area of the base station 6 that has received the CBS message from the broadcast message center 4 matches the failure information collection start condition described in the CBS message. Only when there is a match, detailed data such as communication history information and memory dump information starts to be accumulated as failure analysis information in the internal memory, and then when the same failure occurs, The portable terminal device sends the accumulated failure analysis information to the failure information management server 3.

  The failure information management server 3 that has received the failure analysis information from the mobile terminal device stores the failure information stored previously, such as the failure content, the communication status at that time, the model name, and the failure analysis received from the mobile terminal device. The information is stored in a large-capacity storage device as a pair, and after the storage is completed, the broadcast distribution of the CBS message including the failure information collection start condition regarding the failure information is stopped.

  As described above, in the present invention, among the mobile terminal devices existing in the area covered by the specific base station, the failure analysis information related to the mobile terminal device of a specific model is stored in a plurality of areas located in the area. Data can be efficiently collected from the mobile terminal device.

(Embodiment of portable terminal device of the present invention)
Next, as an example of the present invention, an example of the internal configuration of the mobile terminal device 2 applied to the failure information management system 1 shown in FIG. 1 will be described with reference to FIG. FIG. 2 is a block configuration diagram showing an example of the internal configuration of the mobile terminal device 2 applied to the failure information management system 1 of FIG. 1, and has a configuration substantially similar to that of a general mobile terminal device currently used. It has become.

  2 includes a CPU (Central Processing Unit) 201, a nonvolatile memory 202, a work memory 203, a screen display control unit 204, an input control unit 205, and a ROM (Read Only Memory). 206 and a wireless communication unit 207 are provided, and are connected to each other via a bus 200.

  The CPU 201 is a processing unit that operates according to a control program, and controls each component in the mobile terminal device 2 connected via the bus 200 according to the control program. The nonvolatile memory 202 is a storage device that holds stored information even after the power supplied to the mobile terminal device 2 is turned off. The work memory 203 is constituted by a RAM (Random Access Memory), and stores data temporarily necessary for the CPU 201 to execute the program.

  The screen display control unit 204 includes a control circuit that controls screen display and a display device such as a monochrome or color liquid crystal panel or an organic EL (Electro-Luminescence). The input control unit 205 is an input circuit that receives an input corresponding to an operation by the user, such as a key input as a result of operating various keys. The ROM 206 is a storage device that stores fixed data such as various control programs executed by the CPU 201, a dictionary, and built-in content.

  The wireless communication unit 207 includes a wireless device that transmits and receives data by wireless communication and measures radio waves in a frequency band used for the wireless communication. Here, the wireless communication unit 207 is, for example, a circuit for performing transmission / reception of data by a wireless method of a mobile phone network such as a W-CDMA (Wideband-Code Division Multiple Access) method or a GSM (Global System for Mobile Communications) method. A group.

  The mobile terminal device 2 is equipped with a plurality of wireless communication systems including a circuit group for transmitting and receiving data by a short-range wireless communication method such as a wireless local area network (LAN), Bluetooth, and infrared communication. May be.

  Next, with respect to the mobile terminal device 2 shown in FIG. 2, one form of the internal configuration when expressed by paying attention to the configuration requirements of the failure information management system 1 according to the present invention shown in FIG. It explains using. FIG. 3 is a block configuration diagram showing one form of an internal configuration when attention is paid to the failure information management function in the mobile terminal device 2 shown in FIG.

  As shown in FIG. 3, paying attention to the failure information management function, the mobile terminal device 2 includes a wireless communication unit 301 that performs wireless communication with the base station 6 in the failure information management system 1 of FIG. 1, and the failure information of FIG. The CBS message processing unit 302 that combines and analyzes the CBS messages distributed by the broadcast message center 4 in the management system 1 and the terminal failure status of the mobile terminal device 2 and the status of functional blocks in the mobile terminal device 2 are monitored. A failure / event monitoring unit 303, a function block 1 that implements each function of the mobile terminal device 2,..., A function block group 304 including a function block N, and an internal memory 305.

  Here, the functional block group 304 including the functional blocks 1,..., And the functional block N is not limited to software blocks such as application tasks and threads, and controls, for example, hardware that performs modulation / demodulation and hardware operations. A communication module group such as firmware is also included.

  The wireless communication unit 301 is responsible for a wireless interface with the base station 6 and connects to a mobile phone network to transmit and receive data. The CBS message processing unit 302 combines and analyzes CBS messages received from the wireless communication unit 301, and the received CBS message is a failure analysis message (that is, a failure analysis message related to failure analysis related to the failure information management system 1 according to the present invention). If it is a failure analysis message indicating a failure information collection start condition, which is a condition for starting collection of detailed data for analysis, the failure analysis message is transmitted to the failure / event monitoring unit 303.

  The failure / event monitoring unit 303 monitors the failure status of the mobile terminal device 2. If a failure occurs, the failure / event monitoring unit 303 collects the failure content and uses the wireless communication unit 301 to check the failure information management server 3. In response, a failure notification is sent. In addition, if a failure occurs while the detailed data for failure analysis is being stored in the internal memory 305 as failure analysis information after the condition specified by the received failure information collection start condition is satisfied, The failure analysis information is read from the internal memory 305 and transmitted to the failure information management server 3.

  In addition, the failure / event monitoring unit 303 stores the failure information collection start condition received from the CBS message processing unit 302 in the internal memory 305, the failure information collection start condition, the terminal state of the mobile terminal device 2, and various terminals Comparison with the internal event is made, and if they match, the function block group 304 is instructed to start collecting information for failure analysis.

  Here, the correspondence between the internal configuration of the mobile terminal device 2 shown in FIG. 2 and the internal configuration of the mobile terminal device 2 shown in FIG. 3 will be described. First, the wireless communication unit 301 illustrated in FIG. 3 is realized by the wireless communication unit 207 illustrated in FIG. Further, the CBS message processing unit 302, the failure / event monitoring unit 303, and the functional block group 304 shown in FIG. 3 execute various control programs stored in the ROM 206 shown in FIG. Realized. The internal memory 305 shown in FIG. 3 is realized by the nonvolatile memory 202 or the work memory 203 shown in FIG.

  Next, as an example of the present invention, an example of the internal configuration of the failure information management server 3 applied to the failure information management system 1 shown in FIG. 1 will be described with reference to FIG. FIG. 4 is a block diagram showing an example of the internal configuration of the failure information management server 3 applied to the failure information management system 1 of FIG. 1, and the server function is realized by an application operating on a PC (Personal Computer). Shows when to do.

  The failure information management server 3 shown in FIG. 4 is connected to a large-capacity storage device 404 such as a hard disk device, for example, and can store failure information and failure analysis information in each of a large number of mobile terminal devices 2. It is configured. In the present embodiment shown in FIG. 4, the failure information management server 3 is configured to connect an external large-capacity storage device 404, but the failure information management server 3 includes a large-capacity storage device. You may comprise as follows.

  Here, the failure information management server 3 shown in FIG. 4 is a communication unit that connects and communicates with the broadcast message center (BMC) 4 and the switching center 5 in the failure information management system 1 of FIG. 401, a failure information management unit 402 that manages failure information and failure analysis information received from the mobile terminal device 2, and failure information editing that connects to the mass storage device 404 to edit failure information and failure analysis information Unit 403 at least.

  The communication unit 401 receives a failure occurrence notification (failure information) and failure analysis information of each mobile terminal device 2 routed from the exchange 5 via the Internet network 9. The communication unit 401 shows an example in which communication is performed with the broadcast message center 4 and the exchange 5 via the Internet network 9, but the broadcast message center 4 and the exchange 5 each use a dedicated line or the like. Thus, the communication unit 401 may individually communicate with each other.

  The failure information management unit 402 stores the failure occurrence notification (failure information) and failure analysis information of each mobile terminal device 2 received from the communication unit 401 in the large-capacity storage device 404 using the failure information editing unit 403. To do. Further, when the failure information management unit 402 receives a failure occurrence notification (failure information) from the mobile terminal device 2, the failure information management unit 402 stores the failure occurrence notification (failure information) in the mass storage device 404 and the broadcast message center 4. The failure notification (failure information) is transmitted to the mobile station and broadcasted to all mobile terminal devices in the area of the base station 6 where the mobile terminal device 2 in which the failure has occurred is present in the CBS message. To request.

  When the failure information management unit 402 receives the failure analysis information from the mobile terminal device 2, the failure information management unit 402 stores the failure analysis information in the mass storage device 404 and periodically sends it to the broadcast message center 4. In addition, it is requested to delete information related to the failure corresponding to the failure analysis information from the broadcast CBS message.

(Description of operation of embodiment)
Next, an example of the operation of the failure information management system 1 shown in FIGS. 1 to 4 as an embodiment of the present invention is shown in the sequence charts of FIGS. 5, 6, 8, and 9 and the flowchart of FIG. 7. 10 and FIG. 13 (tables for explaining related information). Here, as described above, according to the present invention, the detailed information inside the mobile terminal device 2 that is effective for analyzing a failure related to wireless communication in the mobile terminal device 2, a fatal failure such as a power failure, and resetting can be efficiently obtained. Its purpose is to provide a means to collect.

  In the sequence charts illustrated in FIGS. 5, 6, 8, and 9, the switching center 5 of the failure information management system 1 only performs routing, so that description thereof is omitted and the mobile terminal device 2 The flow of signals transmitted and received between the base station 6, the broadcast message center 4 and the failure information management server 3 is shown.

  First, the signal flow in the initial state will be described with reference to the sequence chart of FIG. FIG. 5 is a sequence chart showing an example of a signal flow in the initial state of the failure information management system 1 according to the present invention. In the initial operation state of the failure information management system 1, the failure information management server 3 is in a state in which failure information of the mobile terminal device 2 is not stored.

  In the sequence chart of FIG. 5, the failure information management server 3 transmits a CBS message to the broadcast message center 4 in order to collect failure information in all mobile terminal devices 2 existing in the area covered by the base station 6. The request is transmitted, and the broadcast message center 4 is requested to transmit the CBS message to all the mobile terminal devices 2 existing in the area covered by the base station 6 (sequence S500).

  Upon receiving the CBS message transmission request, the broadcast message center 4 creates a CBS message for collecting failure information (sequence S501) and creates it for the base station 6 designated by the failure information management server 3. A CBS message is transmitted (sequence S502). The broadcast message center 4 determines the CBS message in advance in order to keep the CBS message broadcast to all the mobile terminal devices 2 existing in the area covered by the base station 6. Send periodically at regular intervals.

  The base station 6 that has received the CBS message from the broadcast message center 4 broadcasts the received CBS message to all the mobile terminal devices existing in the area covered by the base station 6 (sequence S503).

  An example of a CBS message created by the broadcast message center 4 and broadcast to all mobile terminal devices is shown in FIG. FIG. 10 is a table showing an example of the CBS message created by the broadcast message center 4 in the failure information management system 1 of FIG. 1, and the area management number indicating the area covered by the base station 6 is “0001”. For a certain case, an example of a CBS message that does not include a failure information collection start condition (condition for starting an operation of collecting detailed data for analyzing a failure) is shown.

  As shown in the table of FIG. 10, the CBS message includes an area management number 21, model names 22A, 22B,..., Failure information report addresses 23A, 23B,..., Failure numbers 24A, 24B,. ..., failure information collection start condition 1 (communication type) 26A, 26B, ..., failure information collection start condition 2 (failure occurrence part) 27A, 27B, ..., failure information collection start condition 3 (state of the relevant part) 28A, 28B ,... Are included.

  That is, the CBS message is created for each area covered by each base station as indicated by '0001' of the head area management number 21, and 'A01' of the model names 22A, 22B,. As shown in “B01”,..., As shown in “192.0.0.1”, “192.0.0.2”,... Of failure information report addresses 23A, 23B,. The addresses for reporting the failure information from the mobile terminal devices are different addresses.

  Further, as described above, since the failure information management server 3 in the initial state is in a state in which failure information of the mobile terminal device 2 is not stored, the failure numbers 24A, 24B,..., The failure contents 25A, 25B,. , Fault information collection start condition 1 (communication type) 26A, 26B,..., Fault information collection start condition 2 (failure occurrence part) 27A, 27B,..., Fault information collection start condition 3 (state of the relevant part) 28A, 28B, No information is stored in .... In FIG. 10, only information for two models A01 'and' B01 'is described, but information on a plurality of model names may be further described.

  The mobile terminal device 2 that has received the CBS message like this analyzes the area management number 21, model names 22A, 22B,..., Failure information report addresses 23A, 23B,. The destination address and the area management number of the failure information in its own model are stored in the internal memory 305 shown in FIG. 3 (sequence S504).

  The received CBS message includes fault numbers 24A, 24B,..., Fault contents 25A, 25B,..., Fault information collection start condition 1 (communication type) 26A, 26B,. .., 27A, 27B,..., Failure information collection start condition 3 (state of corresponding part) 28A, 28B,... The normal state in which normal communication is performed remains (sequence S505).

  In this embodiment shown in FIG. 5, the CBS message is transmitted from the broadcast message center 4 to only one base station 6. However, the failure information management server 3 has a plurality of base stations (in FIG. For the base station 7, base station 8, and other base stations in the fault information management system 1, a plurality of fault information is collected by transmitting a similar CBS message transmission request to the broadcast message center 4. A similar CBS message can be broadcast from the broadcast message center 4 to the mobile terminal devices existing in the respective base station areas. In order to individually identify a plurality of areas covered by each of a plurality of base stations when performing such an operation, an area management number 21 is provided in the CBS message as described in the table of FIG. ing.

  Next, the flow of signals when a failure occurs in the mobile terminal device 2 will be described using the sequence chart of FIG. FIG. 6 is a sequence chart showing an example of a signal flow when a failure occurs in the portable terminal device 2 of the failure information management system 1 according to the present invention. In the sequence chart of FIG. A signal flow at that time when a failure occurs in the mobile terminal device 2 storing the area management number in the internal memory 305 is shown.

  The mobile terminal device 2 in which the failure has occurred reads the destination address of the failure information stored in the internal memory 305 and notifies the failure information management server 3 indicated by the destination address of the failure information relating to the failure that has occurred. Thus, when the failure information management server 3 recognizes the failure of the mobile terminal device 2, all the mobile phones in the cover area of the base station 6 in which the mobile terminal device 2 exists are used using the broadcast message center 4. The flow of signals until a CBS message is transmitted in order to notify a terminal device of a failure information collection start condition (a condition for starting an operation of collecting detailed data for analyzing a failure) is shown.

  In the sequence chart of FIG. 6, when a failure occurs in the mobile terminal device 2 that is in a normal state (sequence S600), the mobile terminal device 2 describes the content of the failure related to the failure, the area management number when the failure occurs, A failure occurrence notification including information that can specify a failure occurrence operation condition inside the mobile terminal device 2 such as a model name, a communication type, and a part or a function, a state where the failure has occurred is created as failure information. (Step S601). Thereafter, the mobile terminal device 2 uses the created failure occurrence notification as failure information for the address of the failure information management server 3 indicated by the failure information transmission destination address stored in the internal memory 305 in the sequence chart of FIG. (Step S602).

  FIG. 11 shows an example of a failure occurrence notification created by the mobile terminal device 2 and transmitted to the failure information management server 3 as failure information. FIG. 11 is a table showing an example of a failure occurrence notification created by the mobile terminal device 2 in the failure information management system 1 of FIG. 1, and an area indicating the cover area of the base station 6 in which the mobile terminal device 2 exists An example of the case where the management number is “0001” is shown. As shown in the table of FIG. 11, the failure occurrence notification includes an area management number 31, a model name 32, a failure content 33, a communication type 34, a failure occurrence portion 35, a state 36 of the relevant portion, and the like. .

  In the failure occurrence notification shown in FIG. 11, the area management number of the cover area of the base station 6 in which the mobile terminal device 2 exists is “0001” as indicated by the area management number 31, and the mobile terminal device 2 Is “A01” as shown in the model name 32, and the content of the failure that has occurred indicates a case relating to “reset” as shown in the failure content 33.

  Further, the communication type at the time of failure of the mobile terminal device 2 is “W-CDMA voice communication” as shown in the communication type 34, and the site where the failure has occurred is shown in the failure occurrence site 35. , 'Task 1', the state of the fault occurrence part, as shown in the state 36 of the corresponding part, indicates that it is 'sending'.

  The failure information management server 3 that has received the failure occurrence notification like this generates a failure number uniquely determined for each occurrence area and model from the content of the failure occurrence notification received from the mobile terminal device 2 and received it. A CBS message transmission request for requesting transmission of the saved failure information as a CBS message is given to the content of the failure occurrence notification and saved as failure information in the mass storage device 404 (step S603). The message is transmitted to the broadcast message center 4 (step S604).

  The broadcast message center 4 that has received the CBS message transmission request creates a CBS message for transmitting the received failure information, or adds the received failure information to the existing CBS message (sequence S605). Thereafter, the created or added CBS message is transmitted to the base station 6 designated by the failure information management server 3 as a base station covering the area where the mobile terminal device 2 in which the failure has occurred (sequence S606). ). The broadcast message center 4 determines the CBS message in advance in order to keep the CBS message broadcast to all the mobile terminal devices 2 existing in the area covered by the base station 6. Send periodically at regular intervals.

  The base station 6 that has received the CBS message from the broadcast message center 4 broadcasts the received CBS message to all the mobile terminal devices existing in the area covered by the base station 6 (sequence S607).

  FIG. 12 shows an example of a CBS message created by the broadcast message center 4 and broadcast to all mobile terminal devices. FIG. 12 is a table showing another example of the CBS message created by the broadcast message center 4 in the failure information management system 1 of FIG. 1, and the area management number indicating the area covered by the base station 6 is' 0001. In the case of ', an example of a CBS message including a failure information collection start condition (condition for starting an operation of collecting detailed data for analyzing a failure) is shown.

  As shown in the table of FIG. 12, the CBS message including the failure information collection start condition is the same as the CBS message described in FIG. 10 as an example of the CBS message not including the failure information collection start condition, and the area management number 21. , Model names 22A, 22B,..., Failure information report addresses 23A, 23B,. Further, the failure name 24B,..., Failure content 25B,..., Failure information collection start condition 1 (communication type) on the side corresponding to the portable terminal device whose model name 22B,. ) 26B,..., Failure information collection start condition 2 (failure occurrence part) 27B,..., Failure information collection start condition 3 (state of the relevant part) 28B,... Are the same as the CBS message described in FIG. Information is not stored.

  However, the failure number 24A on the side corresponding to the mobile terminal device 2 whose model name 22A where the failure has occurred is “A01” has the failure number “001” assigned to uniquely identify the failure that has occurred. The stored “reset” notified by the failure content 33 of the failure occurrence notification from the mobile terminal device 2 is stored in the failure content 25A. The failure information collection start condition 1 (communication type) 26A stores “W-CDMA voice communication” notified in the communication type 34 of the failure occurrence notification, and the failure information collection start condition 2 (failure occurrence part) 27A stores “task 1” notified in the failure occurrence part 35 of the failure occurrence notification, and the failure information collection start condition 3 (state of the relevant part) 28A contains the failure occurrence part 35 in the failure occurrence notification. Stores “calling” notified.

  That is, the CBS message shown in the table of FIG. 12 is also created for each area covered by the base station, as indicated by '0001' in the head area management number 21, as in the CBS message shown in the table of FIG. As shown in the model name 22A, the fault that has occurred for the model of the mobile terminal device in which the fault has occurred for each model name of the mobile terminal device that is the collection target of the detailed data for analyzing the fault. Along with the failure number uniquely specified, information on the failure content, communication type, failure location, failure status, etc. notified from the occurred mobile terminal device 2 as failure occurrence notification (failure information) As the failure information collection start condition for the CBS message shown in the table of FIG.

  That is, the failure information collection start condition is not set in the CBS message shown in the table of FIG. 10, whereas in the present CBS message shown in the table of FIG. An information collection start condition is additionally provided along with the failure number.

  The mobile terminal device 2 that has received the CBS message like this has the information stored in the area management number 21, the failure number 24A, the failure content 25A, and the failure information collection start conditions 26A, 27A, 28A,. It is stored in the internal memory 305 as a detailed data collection start condition (failure information collection start condition) related to a failure (sequence S608), and transitions from a normal state to a data accumulation standby state (sequence S609).

  Here, the data storage standby state in which the mobile terminal device 2 has transitioned means that the occurrence event and terminal state of the mobile terminal device 2 are compared with the failure information collection start condition stored in the internal memory 305, and the occurrence event and terminal This means a state in which the accumulation of failure analysis information (detailed data for analyzing a failure) is awaited until the state matches a stored failure information collection start condition.

  Next, an example of the operation of the mobile terminal device 2 in the data storage standby state will be described using the flowchart of FIG. FIG. 7 is a flowchart showing an example of the operation flow of the mobile terminal device 2 when the mobile terminal device 2 of the failure information management system 1 according to the present invention transitions to the data storage standby state.

  In the flowchart shown in FIG. 7, when an event such as communication start / end or communication module start / end occurs in the mobile terminal device 2 that has transitioned to the data storage standby state (step S700), the generated event and the terminal state are displayed. Compared with one or more conditions included in the failure information collection start condition held in the internal memory 305 (step S701), if all conditions of the failure information collection start condition are matched (Yes in step S701), designated as the failure information collection start condition as a condition for starting the operation of collecting detailed data for failure analysis corresponding to the failure information collection condition stored in the internal memory 305 is satisfied The accumulation of the detailed data to be collected is started in the internal memory 305 (step S702), and the data accumulation status Transits to (step S703).

  On the other hand, if the event and the terminal state that have occurred do not match any one or more of the conditions included in the failure information collection start condition held in the internal memory 305 (step S701). No) returns to step S700 and returns to the state of monitoring the event that occurs.

  Next, a signal flow when a failure occurs in the mobile terminal device 2 in a state where data is being stored will be described with reference to the sequence chart of FIG. FIG. 8 is a sequence chart showing an example of a signal flow when a failure occurs in the mobile terminal device 2 when the mobile terminal device 2 of the failure information management system 1 according to the present invention is in a data storage state. In the sequence chart of FIG. 5, the failure address is generated in the portable terminal device 2 that stores the destination address and the area management number of the failure information in the internal memory 305 and has transitioned to the data accumulation state in the flowchart of FIG. 7. For the case, the signal flow at that time is shown.

  When a failure to accumulate detailed data for failure analysis occurs in the mobile terminal device 2 that has transitioned to the data accumulation state (sequence S800), the failure information stored in the internal memory 305 in the sequence chart of FIG. The address of the failure information management server 3 indicated by the destination address of the failure information, that is, the destination address of the failure analysis information, is read out by reading the destination address (which is also the destination address of the failure analysis information in this embodiment). In response to this, the collected detailed data for failure analysis is transmitted as a failure analysis information notification (sequence S801).

  An example of the notification content of the failure analysis information transmitted from the mobile terminal device 2 to the failure information management server 3 is shown in FIG. FIG. 13 is a table showing an example of a failure analysis information notification transmitted from the mobile terminal device 2 to the failure information management server 3 in the failure information management system 1 of FIG. 1. In the sequence chart of FIG. The portable terminal device 2 or the portable terminal device of the same model as the portable terminal device 2 that has been transmitted to the information management server 3 (in this embodiment, the case of the portable terminal device 2 is described) An example of transmitting a failure analysis information notification is shown. As shown in the table of FIG. 13, the failure analysis information notification includes area management number 41, model name 42, failure number 43, failure analysis information 1 (memory dump of task 1) 44, failure analysis information 2 (task 1 operation history) 45, failure analysis information 3 (transmission / reception history with the base station 6) 46, and the like.

  In the failure analysis information notification shown in FIG. 13, the area management number of the cover area of the base station 6 in which the mobile terminal device 2 exists is the case of the failure occurrence notification shown in FIG. As in the case of the failure occurrence notification shown in FIG. 11, the mobile terminal device 2 is “A01” as shown in the model name 42, and the failure number that identifies the failure that occurred is “0001”. Indicates the case where the failure number assigned to uniquely identify the failure information to be collected by the failure information management server 3 in the sequence chart of FIG. ing.

  Further, as the information that is effective for the failure information management server 3 to analyze the failure inside the mobile terminal device 2, the mobile terminal device 2 in the data storage state receives the failure information in the failure occurrence notification shown in FIG. Fault analysis information 1 (memory dump of task 1) 44 for storing various status information and history information in 'task 1', which is the fault occurrence site previously notified to the management server 3, and fault analysis information 2 ( Task 1 operation history) 45, failure analysis information 3 (transmission / reception history with the base station 6) 46, and the like are prepared.

  Here, in the failure analysis information 1 (task 1 memory dump) 44, the mobile terminal device 2 in the data accumulation state has previously notified the failure information management server 3 by the failure occurrence notification shown in FIG. Memory dump data at the time of failure occurrence in 'task 1' which is the failure occurrence site is stored, and in the failure analysis information 2 (operation history of task 1) 45, the mobile terminal device 2 in the data accumulation state is shown in FIG. 11 stores operation history data indicating a situation in which “task 1”, which is the failure occurrence part previously notified to the failure information management server 3 by the failure occurrence notification shown in FIG. Further, the failure analysis information 3 (transmission / reception history with the base station 6) 46 stores transmission / reception history data transmitted / received to / from the base station 6 by the mobile terminal device 2 in the data accumulation state.

  The failure information management server 3 that has received the failure analysis information notification as described above uses the failure analysis information received from the mobile terminal device 2 to analyze the failure relating to the failure number “001” that has occurred in the mobile terminal device 2 this time. Failure information requesting the mobile terminal device 2 to delete the failure information related to the failure number '001' that occurred at this time from the CBS message after the failure information detailed data is stored in the large-capacity storage device 404 (step S802). A transmission stop request is transmitted to the broadcast message center 4 (step S803). Here, the failure information transmission stop request includes at least an area management number “0001”, a model name “A01”, and a failure number “001”.

  The broadcast message center 4 that has received the failure information transmission stop request receives information on the failure specified by the received failure information transmission stop request from among the CBS messages that are regularly distributed at a predetermined cycle. Is deleted from the CBS message from the next time (step S804).

  Next, when the mobile terminal device 2 in the data storage standby state or the data storage state moves between areas covered by the base station or a change in the radio wave state occurs, The operation of switching between base stations that transmit and receive signals will be described with reference to the sequence chart of FIG. 9 when a so-called handover occurs. FIG. 9 shows a signal when a handover across base stations occurs in the mobile terminal device 2 when the mobile terminal device 2 of the failure information management system 1 according to the present invention is in a data storage standby state or a data storage state. 7 is a sequence chart illustrating an example of the flow of the mobile terminal device 2 that has transitioned to the data storage standby state in the sequence chart of FIG. 6 or the mobile terminal device 2 that has transitioned to the data storage state in the flowchart of FIG. However, when moving from the area covered by the base station 6 to the area covered by the base station 7 (that is, handed over from the base station 6 to the base station 7), the signal flow at that time is shown. Yes.

  The mobile terminal device 2 that exists in the area covered by the base station 6 and is in the data storage standby state or the data storage state is periodically transmitted from the broadcast message center 4 via the base station 6. Each time a CBS message is received (sequence S900), as described in the sequence chart of FIG. 6, among the failure information collection conditions included in the received CBS message, the model name “A01” of the mobile terminal device 2 is included. Failure information collection conditions (area management number 21, failure number 24A, failure content 25A, information stored in each failure information collection start condition 26A, 27A, 28A,...) Corresponding to 'are stored in the internal memory 305. (Sequence S901).

  The base station with which the mobile terminal device 2 performs wireless communication is switched from the base station 6 to the base station 7 due to the movement of the mobile terminal device 2 itself in such a state or the deterioration of radio quality from the base station 6. When a handover occurs (sequence S902), the mobile terminal device 2 starts the failure information collection start condition (the operation for collecting detailed data for analyzing the failure) that was received when the mobile terminal device was in the base station 6 Are deleted from the internal memory 305 (sequence S903), and the data storage standby state or the data storage state is changed to the normal state (sequence S904).

  As described above, after returning to the normal state by handing over to the base station 7, the mobile terminal device 2 sends a CBS message including a failure information collection condition in the area covered by the base station 7 from the broadcast message center 4. When received via the base station 7 (sequence S905), failure information collection conditions (area management number 21, failure number 24A, failure content 25A, failure information collection corresponding to the model name 'A01' of the mobile terminal device 2) (Information stored in the start conditions 26A, 27A, 28A,...) Are stored in the internal memory 305 (sequence S906), and then the normal state is changed to the data accumulation standby state (sequence S907). The broadcast message center 4 periodically transmits a CBS message via the base station 7 at a predetermined period.

  As described above in detail, in the failure information management system 1 according to the present embodiment shown as an example in FIG. 1, when a failure occurs in the mobile terminal device 2, an operation of collecting detailed data regarding the failure information Is started as a CBS message from the failure information management server 3 using the broadcast message center 4, so that the mobile terminal device 2 is included in the CBS message. Collection of detailed data for failure analysis of the collection target specified in the failure information collection start condition is started, and after that, the failure information collection start condition is started. When the error occurs, the collected detailed data is sent to the failure information management server 3 as failure analysis information.

  In the operation of the failure information management system 1 described above with reference to FIGS. 5 to 13, the mobile terminal device 2 designates from the failure information management server 3 after the failure first occurs in the mobile terminal device 2. When the failure information collection start condition is met, collection of detailed data for failure analysis is started, and thereafter, the operation of collecting detailed data is repeated, and when a failure occurs again in the mobile terminal device 2 In the above description, the detailed information for failure analysis that has been collected is sent from the portable terminal device 2 to the failure information management server 3 as failure analysis information. However, the present invention is not limited to this operation. Absent.

  For example, the failure specified by the failure information management server 3 by another mobile terminal device different from the mobile terminal device 2 in which the failure has occurred (for example, a mobile terminal device of the same model as the mobile terminal device 2 in which the failure has occurred) It goes without saying that failure information detailed data that matches the information collection conditions may be collected as failure analysis information and sent to the failure information management server 3.

(Description of the effect of this embodiment)
As described in detail above, the following effects are obtained in the present embodiment.

  First, it is possible to collect failure information and failure analysis information related to the mobile terminal device 2 only in a specific base station (base station 6 or the like) that covers the area where the mobile terminal device 2 where the failure has occurred. For this reason, for example, even in a case where a failure is unlikely to occur, such as in a different base station area, by collecting failure information, a situation in which the CPU operating rate of the mobile terminal device 2 increases is avoided. Thus, battery consumption of the mobile terminal device 2 can be suppressed.

  Second, since the condition for collecting the information for failure analysis can be changed according to the failure that has occurred and can be set to an appropriately limited condition, as in the case of the first effect, the mobile terminal device 2 battery consumption can be suppressed.

  Thirdly, when a plurality of mobile terminal devices exist in the area of the fault information management system 1, each time a fault information collection condition specified by the fault information management server 3 is satisfied in each of the plurality of mobile terminal devices, Because failure information detailed data is collected as failure analysis information, the number of samples of failure analysis information increases, and even for failures with low reproducibility at specific base stations, data that is effective as failure analysis information must be collected. The possibility of being able to be increased.

  Fourth, the mobile terminal device 2 in which the failure has occurred has moved from the area (cell area) covered by the base station 6 that has collected detailed failure information data as failure analysis information to the cell area of another base station. In this case (that is, when a handover between base stations occurs), the failure information collection conditions up to now in the base station 6 are discarded together with the collected failure analysis information. Collection of useless information for failure analysis based on the information collection condition is not performed, and thus the memory consumption in the mobile terminal device 2 can be suppressed.

  Fifth, since the transmission destination address to which the failure information and the failure analysis information are sent can be changed for each area where the mobile terminal device 2 exists and for each model of the mobile terminal device 2, for example, the failure information management server 3 Are prepared separately, and for each area where the mobile terminal device 2 exists or for each model of the mobile terminal device 2, a failure information management server 3 for sending failure information and failure analysis information is prepared separately, The load on the failure information management server 3 can be distributed.

(Other embodiments of the present invention)
In the above-described embodiment, the failure occurrence notification and the failure analysis information notification are transmitted to the same failure information management server 3, but the CBS message (no failure information collection start condition) shown in FIG. The failure notification destination address set in the failure information report address 23A, 23B,... And the failure analysis information notification set in the failure information report address 23A, 23B,. The failure information management servers 3 serving as transmission destinations may be distributed by designating different addresses for the transmission destination addresses.

  In addition, when there is another model with the same software and hardware as the mobile terminal device, the failure information management server 3 is information for determining a plurality of model names of the mobile terminal device with the same software and the same hardware. Are stored in advance, and when the CBS message transmission request is transmitted for the first time, or when the CBS message transmission request is transmitted when a failure information notification is received from a portable terminal device of a certain model name, Thus, a plurality of corresponding model names may be automatically stored and distributed as model names to be included in the CBS message.

  In the above-described embodiment, as shown in the table of FIG. 10 or FIG. 12, information on portable terminal devices having a plurality of model names is stored in one CBS message. For example, a plurality of CBS messages may be transmitted. By separating the CBS message for each model, manufacturer, etc., it is possible to avoid unnecessary CBS message analysis processing by using a function of rejecting reception of the same CBS message as the portable terminal device.

  In the above description, a case where a mobile phone is used as a mobile terminal device and a broadcasting method using a CBS message for the mobile phone is used has been described. However, other types of mobile terminal devices such as PHS and PDA are used. It is possible to use the same notification method as in the above-described embodiment by using a broadcasting method for other types of mobile terminal devices, and for the failure analysis as described above. It is of course possible to collect information.

The configuration of the preferred embodiment of the present invention has been described above. However, it should be noted that such examples are merely illustrative of the invention and do not limit the invention in any way. Those skilled in the art will readily understand that various modifications and changes can be made according to a specific application without departing from the gist of the present invention. For example, the embodiment of the present invention can be expressed as the following configuration in addition to the configuration (1) in the means for solving the problems.
(2) The failure information management server that has received the failure occurrence notification from the portable terminal device broadcasts a collection start condition for starting collection of failure detailed data for analyzing the failure that has occurred in the portable terminal device. The failure information management system according to (1), wherein a message is periodically transmitted at a predetermined cycle from the base station covering an area where the mobile terminal device exists via a broadcast message center.
(3) Among the mobile terminal devices that have received the broadcast message from the base station, the mobile terminal device in which the failure has occurred or a mobile terminal device of the same model as the mobile terminal device is instructed by the broadcast message. Depending on the collection start condition, the collection details of the failure detail data to be collected are changed and the collection of the failure detail data is started, and then collected when a failure occurs in the mobile terminal device The failure information management system according to (2), wherein the detailed failure data that has been stored is transmitted to the failure information management server as failure analysis information.
(4) The failure information management server that has received the failure analysis information from the mobile terminal device relates to the failure analysis information received from the broadcast message that is periodically transmitted at a predetermined cycle. The failure information management system according to (3), wherein the failure detailed data collection start condition is deleted.
(5) The failure information management server that receives the failure analysis information from the mobile terminal device separates the failure analysis information for each area covered by the base station and for each model of the mobile terminal device. The fault information management system according to (3) or (4), which can be stored.
(6) A mobile terminal device that performs wireless communication with a base station, and when a failure occurs in the mobile terminal device, a model name indicating the model of the mobile terminal device, and a failure indicating the content of the failure that has occurred Failure information management that collects and manages information for analyzing the failure of a mobile terminal device, using failure information that includes at least the content, the type of communication at the time of failure, the location of the failure, and the state of the failure as a failure notification A mobile terminal device that transmits to a server.
(7) A failure information management server that collects and manages information for analyzing a failure of the mobile terminal device, and the failure that has occurred in the mobile terminal device when the failure occurrence notification is received from the mobile terminal device A broadcast message for instructing a collection start condition for starting the collection of failure detailed data for analyzing the error is transmitted from the base station covering the area where the mobile terminal device exists via a broadcast message center to a predetermined cycle. The failure information management server that is sent out periodically.
(8) A failure information management system comprising at least a mobile terminal device that performs wireless communication with a base station, and a failure information management server that collects and manages information for analyzing a failure of the mobile terminal device In the failure information management method according to claim 1, when a failure occurs in the portable terminal device, the portable terminal device includes a model name indicating the model of the own portable terminal device, a failure content indicating the content of the failure that has occurred, Fault information management method for transmitting fault information including at least a communication type, a fault occurrence site, and a status of the fault occurrence site as a fault occurrence notification to the fault information management server.
(9) A failure information management program in which the failure information management method of (8) is implemented as a program executable by a computer.
(10) A program recording medium in which the failure information management program of (9) is recorded on a computer-readable recording medium.

1 Failure Information Management System 2 Mobile Terminal Device 3 Failure Information Management Server 4 Broadcast Message Center (BMC)
5 Switching station 6 Base station 7 Base station 8 Base station 9 Internet network 21 Area management number 22A Model name 22B Model name 23A Failure information report address 23B Failure information report address 24A Failure number 24B Failure number 25A Failure content 25B Failure content 26A Failure information Collection start condition 1 (communication type)
26B Failure information collection start condition 1 (communication type)
27A Failure information collection start condition 2 (failure occurrence location)
27B Failure information collection start condition 2 (failure occurrence location)
28A Fault information collection start condition 3 (status of relevant part)
28B Failure information collection start condition 3 (status of relevant part)
31 Area management number 32 Model name 33 Fault content 34 Communication type 35 Fault location 36 Status of relevant part 41 Area management number 42 Model name 43 Fault number 44 Fault analysis information 1 (memory dump of task 1)
45 Fault analysis information 2 (operation history of task 1)
46 Failure analysis information 3 (transmission / reception history with the base station 6)
200 Bus 201 CPU (Central Processing Unit)
202 Non-volatile memory 203 Work memory 204 Screen display control unit 205 Input control unit 206 ROM (Read Only Memory)
207 Wireless communication unit 200 Bus 301 Wireless communication unit 301
302 CBS Message Processing Unit 303 Fault / Event Monitoring Unit 304 Functional Block Group 305 Internal Memory 401 Communication Unit 402 Fault Information Management Unit 403 Fault Information Editing Unit 404 Mass Storage Device

Claims (10)

  In a failure information management system comprising at least a mobile terminal device that performs wireless communication with a base station, and a failure information management server that collects and manages information for analyzing a failure of the mobile terminal device, When a failure occurs in the mobile terminal device, the mobile terminal device displays the model name indicating the model of the mobile terminal device itself, the failure content indicating the content of the failure that has occurred, the communication type at the time of the failure, the location of the failure, and the occurrence of the failure A failure information management system, wherein failure information including at least a part state is transmitted to the failure information management server as a failure occurrence notification.   The failure information management server that has received the failure occurrence notification from the mobile terminal device transmits a broadcast message instructing a collection start condition for starting collection of failure detailed data for analyzing the failure that has occurred in the mobile terminal device, 2. The fault information management system according to claim 1, wherein the base station that covers an area where the mobile terminal device exists is periodically transmitted at a predetermined cycle via a broadcast message center. .   Among the mobile terminal devices that have received the broadcast message from the base station, the mobile terminal device in which the failure has occurred or a mobile terminal device of the same model as the mobile terminal device starts collection indicated by the broadcast message Depending on the conditions, the collection details of the failure detailed data to be collected are changed and the collection of the failure detailed data is started, and then collected when a failure occurs in the mobile terminal device. The failure information management system according to claim 2, wherein the failure detailed data that has been transmitted is transmitted to the failure information management server as failure analysis information.   The failure information management server that has received the failure analysis information from the mobile terminal device has received detailed failure data relating to the received failure analysis information from the broadcast message that is periodically transmitted at a predetermined cycle. The failure information management system according to claim 3, wherein the collection start condition is deleted.   The failure information management server that receives the failure analysis information from the mobile terminal device separates and stores the failure analysis information for each area covered by the base station and for each model of the mobile terminal device. The fault information management system according to claim 3 or 4, wherein the fault information management system can be used.   A mobile terminal device that performs wireless communication with a base station. When a failure occurs in the mobile terminal device, the model name indicating the model of the mobile terminal device, the failure content indicating the content of the failure, and the failure Failure information including at least the communication type at the time of occurrence, failure location, and failure status is sent as a failure notification to the failure information management server that collects and manages information for analyzing the failure of the mobile terminal device A portable terminal device.   A failure information management server that collects and manages information for analyzing a failure of a mobile terminal device, and analyzes a failure that has occurred in the mobile terminal device when a failure occurrence notification is received from the mobile terminal device Broadcast message for instructing the collection start condition for starting the collection of detailed failure data for the base station that covers the area where the mobile terminal device exists is periodically transmitted via the broadcast message center. A failure information management server characterized by causing the server to send out the information.   Fault information in a fault information management system comprising at least a mobile terminal device that performs wireless communication with a base station and a fault information management server that collects and manages information for analyzing faults of the mobile terminal device In the management method, when a failure occurs in the portable terminal device, the portable terminal device displays a model name indicating a model of the own portable terminal device, a failure content indicating the content of the generated failure, and a communication type at the time of occurrence of the failure A failure information management method, wherein failure information including at least a failure occurrence site and a failure occurrence state is transmitted as a failure occurrence notification to the failure information management server.   9. A failure information management program, wherein the failure information management method according to claim 8 is implemented as a program executable by a computer.   10. A program recording medium, wherein the failure information management program according to claim 9 is recorded on a computer-readable recording medium.

Images