JP7392399B2 - Information processing device, system, information processing method, and program - Google Patents

Description

The present invention relates to an information processing device, a system, an information processing method, and a program.

In a system in which a predetermined device and an information processing device are communicably connected, the information processing device uses the functions of the predetermined device via the middleware of the predetermined device in response to a request received by the information processing device from a user. Sometimes.

Patent Document 1 discloses that in a mobile terminal device, user operation logs received in an application are accumulated as log data, and when a self-diagnosis request is received from the user in the application, the log data and scenario data are compared and operation errors are detected. It is described that the diagnosis is carried out. As a result, according to Patent Document 1, the user himself/herself can diagnose an operational error using the application that the user normally uses.

Patent Document 2 discloses that in an image processing cooperation system in which a mobile information device and an MFP are communicably connected, the mobile information device acquires a log about a file from the MFP and combines it with a log about the file in its own device. It is stated that it should be managed by According to Patent Document 2, this makes it easier to track files handled across the portable information device and the MFP.

In the technique described in Patent Document 1, the log data that is accumulated is only related to the user's operation of the mobile terminal device, and there is a possibility that the information is insufficient for a developer to analyze a problem.

In the technology described in Patent Document 2, the logs that are managed together for the mobile information device and the MFP are only logs about files, and there is a possibility that there is insufficient information for a developer to analyze a problem. be.

The present invention has been made in view of the above, and aims to provide an information processing device, a system, an information processing method, and a program that can collectively manage information for defect analysis by a developer. .

In order to solve the above-mentioned problems and achieve the purpose, an information processing device according to one aspect of the present invention includes a utilization means for utilizing functions of a predetermined device having middleware via the middleware, and development of the middleware. a changing means for changing the operation using a menu for developers when the function for developers is enabled; and a generating means for generating information that integrates multiple types of logs recorded when the functions for developers are enabled. , acquiring information on the screen of the information processing device as a screen log at the timing when a transmitting means that transmits the information to the predetermined device and a relay application that relays transmission of a request from the application to the predetermined device are used; It is characterized by having a log acquisition means .

According to the present invention, it is possible to collectively manage information for failure analysis by a developer.

FIG. 1 is a diagram showing a schematic configuration of a system according to an embodiment. FIG. 2 is a diagram showing a schematic hardware configuration of each device in the embodiment. FIG. 3 is a diagram showing the functional configuration of the information processing device in the embodiment. FIG. 4 is a sequence diagram showing the operation of the system according to the embodiment. FIG. 5 is a diagram showing an example of a job log in the embodiment. FIG. 6 is a diagram illustrating an example of an API (Application Programming Interface) log in the embodiment. FIG. 7 is a diagram showing an example of a screen log in the embodiment. FIG. 8 is a diagram showing an example of a packet log in the embodiment. FIG. 9 is a diagram showing an example of an error log in the embodiment. FIG. 10 is a sequence diagram showing the operation of the system according to the first modification of the embodiment. FIG. 11 is a sequence diagram showing the operation of the system according to the second modification of the embodiment. FIG. 12 is a diagram showing the operation of the system according to the third modification of the embodiment. FIG. 13 is a diagram illustrating an example of the hardware configuration of an information processing apparatus in the embodiment and first to third variations thereof. FIG. 14 is a diagram illustrating an example of the hardware configuration of a predetermined device in the embodiment and first to third variations thereof.

(Embodiment)
A system 100 according to an embodiment of the present invention is a system in which a predetermined device and an information processing device are communicably connected. The predetermined device 1 is an image forming device that has middleware and forms an image in response to a request received via the middleware, and is a multifunction device (multifunction device) that has multiple functions such as a scanner function, a printer function, and a facsimile function. It may also be an MFP (Multifunction Peripheral). The information processing device is, for example, a mobile terminal such as a tablet or a smartphone. In this system, the information processing device may utilize the functions of a predetermined device via the middleware of the predetermined device in response to a request received by the information processing device from a user.

For example, in an information processing device, user operation logs received by an application are accumulated as log data, and when the application receives a request for self-diagnosis from the user, the log data and scenario data are compared to diagnose operational errors. Consider the case. In this case, the accumulated log data only relates to the user's operation of the information processing device, and tends to lack information for a developer to analyze a problem.

Further, consider a case in which an information processing apparatus acquires a log regarding a file from a predetermined apparatus in a system and manages it together with a log regarding the file within the own apparatus. In this case, the logs that are managed together for the information processing device and the predetermined device are only logs for files, and there is a tendency for the information to be insufficient for a developer to analyze a problem.

Therefore, in this embodiment, the system generates information that integrates multiple types of logs recorded when the developer function is enabled in the information processing device and sends it to a predetermined device. This makes it possible to consolidate the integrated log of the system and the log of a predetermined device, and enables developers to collectively manage information for trouble analysis.

Specifically, the system 100 may be configured as shown in FIG. 1, for example. FIG. 1 is a diagram showing a schematic configuration of a system 100 according to an embodiment.

The system 100 includes a predetermined device 1, an information processing device 2, a network 3, and a log server 30. The predetermined device 1, the information processing device 2, and the log server 30 are connected to each other via the network 3 so as to be able to communicate with each other. Network 3 includes wireless communication lines and/or wired communication lines. The wireless communication line includes a wireless LAN (Local Area Network), a mobile phone line, and the like. The wired communication line includes a wired LAN, WAN (Wide Area Network), and the like.

The predetermined device 1 is, for example, an image forming device that forms an image in response to a request. The predetermined device 1 has middleware and a plurality of functions, and can transmit a received request to the plurality of functions via the middleware. The plurality of functions include a copy function, a scanner function, a printer function, a facsimile function, and the like. The predetermined device 1 may be a multifunction peripheral (MFP) having these multiple functions. In addition, in FIG. 1, for the sake of simplicity of illustration and explanation, a configuration in which one predetermined device 1 (MFP) is connected to the network 3 is illustrated, but the network 3 may include a plurality of predetermined devices 1. (MFP) may be connected.

The information processing device 2 is a device that can receive a request from a user and transmit it to a predetermined device 1, and may be, for example, a tablet, a portable personal computer, or a mobile terminal such as a smartphone. , an installed personal computer, a workstation, or other information terminal. Further, the information processing device 2 may be a device that can autonomously generate a request and transmit it to a predetermined device 1. The information processing device 2 has an application and a relay application. When an application receives a request from a user or autonomously generates a request, the application supplies the request to the relay application. The relay application transmits the received request to the middleware of a predetermined device 1 via the network 3. Thereby, the information processing device 2 can transmit requests to a plurality of functions via the middleware of the predetermined device 1, and can utilize the functions of the predetermined device 1 via the middleware of the predetermined device 1.

The log server 30 is a server that stores logs of predetermined devices 1 and information processing devices 2, respectively. When the log server 30 receives a log from a predetermined device 1, the log server 30 stores the received log in association with the predetermined device 1. When the log server 30 receives a log from the information processing device 2, the log server 30 stores the received log in association with the information processing device 2.

Next, a schematic hardware configuration of each device in the system 100 will be described using FIG. 2. FIG. 2 is a diagram showing a schematic hardware configuration of each device in the embodiment.

The predetermined device 1 is, for example, a multifunction peripheral (MFP), and includes a control device 11, a display device 12, a main storage device 13, an operation input device 14, an external storage device 15, a printing device 16, an image reading device 17, and a communication device 18. , and bus 19. The control device 11 , display device 12 , main storage device 13 , operation input device 14 , external storage device 15 , printing device 16 , image reading device 17 , and communication device 18 are connected to each other via a bus 19 . The main storage device 13 includes a RAM and the like that functions as a work area for programs executed by the control device 11. The external storage device 15 is, for example, a hard disk drive, and stores various control programs, application programs, image data, and the like. The control device 11 loads necessary programs and the like from the external storage device 15 to the main storage device 13 and executes them, and controls the entire predetermined device 1 via the bus 19.

The information processing device 2 is, for example, a smartphone, and includes a control device 23, a display device 24, a main storage device 25, an operation input device 26, an external storage device 27, a communication device 28, and a bus 29. The control device 23, display device 24, main storage device 25, operation input device 26, external storage device 27, and communication device 28 are connected to each other via a bus 29. The main storage device 25 includes a RAM and the like that functions as a work area for programs executed by the control device 23. The external storage device 27 is, for example, a hard disk drive, and stores various control programs, application programs, image data, and the like. The control device 23 loads necessary programs and the like from the external storage device 27 to the main storage device 25 and executes them, and controls the entire information processing device 2 via the bus 29.

The log server 30 has a communication device 31, a storage device 32, and a bus 33. The communication device 31 and the storage device 32 are connected via a bus 33. The storage device 32 stores logs of the predetermined device 1 and the information processing device 2, respectively.

The communication device 18 of the predetermined device 1, the communication device 28 of the information processing device 2, and the communication device 31 of the log server 30 are connected to each other via the network 3 so that they can communicate with each other.

Next, the functional configuration of the information processing device 2 will be explained using FIG. 3. FIG. 3 is a diagram showing the functional configuration of the information processing device 2. As shown in FIG. When the program stored in the external storage device 27 shown in FIG. 2 is executed by the control device 23, the functional configuration shown in FIG. It can be expanded sequentially accordingly.

The information processing device 2 has an application and a relay application as software, and has an application 21 and a relay application 22 as configurations corresponding to the application and the relay application, respectively. The application 21 includes an input section 211, a usage section 212, a change section 213, a transmission section 214, and a display control section 215. The relay application 22 includes a request management section (generation means) 221 and a log management section 222. The log management section 222 includes an API (Application Programming Interface) log management section 222a, a job log management section 222b, a screen log management section (log acquisition means) 222c, a packet log management section 222d, and an error log management section 222e.

Upon receiving a request from a user, the input unit 211 supplies the request to the utilization unit 212 . The utilization unit 212 utilizes the functions of a predetermined device 1 via middleware in response to a user's request or in response to a request autonomously generated within the information processing device 2 . The utilization unit 212 transmits the request to middleware of a predetermined device 1 via the request management unit 221. In a predetermined device 1, middleware transmits a request to a function corresponding to the request, and the function receiving the request performs an operation corresponding to the request.

At this time, the request management section 221 supplies a log recording request to the log management section 222 according to the operation. If the operation is related to an API, the request management unit 221 supplies a log recording request to the API log management unit 222a, and the API log management unit 222a generates and maintains an API log. If the operation is related to a job, the request management unit 221 supplies a log recording request to the job log management unit 222b, and the job log management unit 222b generates and holds a job log. If the operation is related to the screen, the request management unit 221 supplies a log recording request to the screen log management unit 222c, and the screen log management unit 222c generates and holds a screen log. If the operation is related to packets, the request management unit 221 supplies a log recording request to the packet log management unit 222d, and the packet log management unit 222d generates and maintains a packet log. If the operation is related to an error, the request management unit 221 supplies a log recording request to the error log management unit 222e, and the error log management unit 222e generates and maintains an error log.

The changing unit 213 changes the operation according to a request selected from a developer menu of the predetermined device 1 or itself when the developer function of the middleware is enabled in the predetermined device 1 . For example, when log acquisition processing is selected in the developer menu while the information processing device 2 is operating in the job execution processing mode, the changing unit 213 changes the operation mode of the information processing device 2 from the job execution processing mode. The request management unit 221 is instructed to change to the log acquisition processing mode and operate in the log acquisition processing mode. In response to the instructions, the request management unit 221 sends the log acquisition request to the API log management unit 222a, job log management unit 222b, screen log management unit 222c, packet log management unit 222d, and error log management unit 222e in the log management unit 222. supply to each. The API log management unit 222a, the job log management unit 222b, the screen log management unit 222c, the packet log management unit 222d, and the error log management unit 222e each manage logs (for example, API log, job log) in response to log acquisition requests. , screen log, packet log, error log) to the request management unit 221.

The request management unit 221 generates information that integrates multiple types of logs that are recorded when the developer function is enabled. When the request management unit 221 receives each log from the log management unit 222, it generates information that integrates each log. The request management unit 221 transmits the information to a predetermined device 1 via the network 3. In response, the predetermined device 1 obtains its own log (for example, an MFP log), generates information by further integrating the log with the received information, and outputs it in a predetermined method. This allows developers to collectively manage information for defect analysis by allowing developers to view information that combines the integrated log of information processing device 2 and the log of a predetermined device 1. It can be done.

Next, the operation of the system 100 will be explained using FIG. 4. FIG. 4 is a sequence diagram showing the operation of the system 100.

A user selects a predetermined device (MFP) 1 to be connected using an application 21 of an information processing device (portable terminal) 2. The application 21 acquires information for identifying the predetermined device (MFP) 1, such as an IP address, from the user or from the predetermined device (MFP) 1, for example. The application 21 can display a touch panel screen that accepts input of an IP address from the user. Further, the application 21 uses an imaging device (for example, a camera) included in the information processing device (mobile terminal) 2 to display images on the operation screen of the predetermined device (MFP) 1 (or You can obtain the IP address by photographing a QR code (registered trademark) pasted on the housing and analyzing the QR code, or you can acquire the IP address by using a short-range wireless communication means such as an NFC (Near Field Communication) interface. The IP address may be acquired from the device (MFP) 1.

As shown in FIG. 4, in the job execution processing mode of the information processing device (mobile terminal) 2, the application 21 utilizes the functions (scan function, etc.) of a predetermined device (MFP) 1. By cooperating with the predetermined device (MFP) 1, the application 21 can utilize the functions of the predetermined device (MFP) 1, such as a print function, a copy function, and a scan function. The application 21 displays buttons for various functions on the display device 24 and sends a job request to a predetermined device (MFP) 1 to execute the function corresponding to the button selected by the user on the operation input device 26. do.

Logs of jobs executed by the application 21 are stored in the log management unit 222 within the relay application 22. When a predetermined device (MFP) 1 executes a job in response to a request from the application 21, the relay application 22 stores a job log for the job.

For example, the job log acquired and managed by the log management unit 222 of the relay application 22 may be information as shown in FIG. FIG. 5 is a diagram showing an example of a job log. The job log may include a log ID, log type, start time, end time, job status, operation source, user name, and device ID. The log ID is an ID that uniquely indicates a job log, and is, for example, "1". The log type is an attribute for distinguishing jobs, and is, for example, "scanner". The start time is the start time of the job, and is, for example, “2019/01/01 12:00”. The end time is the end time of the job, and is, for example, "2019/01/01 12:03". The job status indicates any one of in progress, normal end, and abnormal end, and is, for example, "normal end." The operation source indicates the operation from which the job was submitted, and is, for example, the "operation panel" of the operation input device 26. The user name is the name of the user who submitted the job, and is, for example, "department A." The device ID is identification information of the device number to which the job was submitted, and is, for example, "10012345."

The log of the API executed by the application 21 is stored in the log management unit 222 within the relay application 22. Here, the relay application 22 is software that needs to be installed separately from the application 21, and is software that is independent from the application 21. The application 21 communicates via the relay application 22 when communicating with the predetermined device (MFP) 1, including sending a job request. Further, the relay application 22 may transmit a response to the application 21 via the relay application 22 when the predetermined device (MFP) 1 responds to the application 21 via the API.

For example, the API log is a log as shown in FIG. FIG. 6 is a diagram showing an example of an API log. For example, when a program as shown in FIG. 6(a) is used with an API, an API log as shown in FIG. 6(b) is generated. As shown in FIG. 6(b), the API log includes the time when the API was used, the input parameters to the API, and the results output from the API. In Figure 6(b), the time when the API was used is "10-30 21:37:09.217", the input parameter to the API is "This is job setting", and the result output from the API is An example is shown in which is "ip/rest/config/user/1: panel, user 1, 10012345".

Information on the screen of the information processing device (mobile terminal) 2 is stored in the log management unit 222 within the relay application 22. The relay application 22 can acquire a captured image of the screen displayed on the information processing device (mobile terminal) 2 and store it in the log server 30 as a screen log.

For example, the screen log is a log as shown in FIG. FIG. 7 is a diagram showing an example of a screen log. The relay application 22 may save a snapshot of the screen of the display device 24 of the information processing device (mobile terminal) 2 at the time when the user operated the information processing device (mobile terminal) 2, and/or may display A predetermined device (MFP) 1 may be requested to save a snapshot of the screen of the device 12. 7(a) shows an example of a screen log of the display device 24 of the information processing device (mobile terminal) 2, and FIG. 7(b) shows an example of the screen log of the display device 12 of the predetermined device (MFP) 1. shows. The relay application 22 may acquire screen information by communicating with software that controls the display of the information processing device (mobile terminal) 2 or with the application 21 to be operated. Screen logs make it possible to understand situations that could not be understood from text logs alone. For example, since the screen of the information processing device (mobile terminal) 2 is recorded, it is possible to compare the operating procedure with other logs. Alternatively, since the screen of the predetermined device (MFP) 1 is recorded, it becomes possible to compare the status of the predetermined device (MFP) with other logs. In FIG. 4, a case is illustrated in which a snapshot of the screen of the display device 24 of the information processing device (mobile terminal) 2 is saved (recorded) as a screen log.

Further, the relay application 22 stores a packet log in the log management unit 222 when the information processing device (mobile terminal) 2 communicates with an external server (e.g., email).

For example, the packet log is a log as shown in FIG. FIG. 8 is a diagram showing an example of a packet log. When the information processing device (mobile terminal) 2 communicates with the outside of the device, it becomes possible to grasp the detailed operating status from the packet. The packets to be stored are assumed to be the packets of the relay application 22 since the relay application 22 of the information processing device (mobile terminal) 2 performs the process, but a method of acquiring communication packets from the predetermined device (MFP) 1 side is also conceivable. . The packet log includes information such as the source and destination of the packet, the sites visited, and the servers, routers, and switches that the packet passed through.

If an error occurs during processing in a predetermined device (MFP) 1 and/or information processing device (portable terminal) 2, an error log is stored in the log management unit 222.

For example, the error log is a log as shown in FIG. FIG. 9 is a diagram showing an example of an error log. If an error occurs during processing, the error log stores the time of error occurrence and error code. In FIG. 9, the case where the error occurrence time is "2019/01/01 10:00" and the error code is "SC999" is illustrated. In addition, by setting the error code to be different between the predetermined device (MFP) 1 and the information processing device (mobile terminal) 2, the location where the error occurred can be identified between the predetermined device (MFP) 1 and the information processing device (mobile terminal). ) 2 may be determined from the error code.

Returning to FIG. 4, for example, upon receiving a connection setting request from a user (S1), the application 21 supplies a connection setting request to the request management unit 221 (S2). In response to the connection setting request, the request management unit 221 requests the API log management unit 222a to record an API log (S3), and requests the screen log management unit 222c to record a screen (S4). In response, the API log management unit 222a generates and holds an API log, and the screen log management unit 222c generates and holds a screen log according to information on the screen of the display device 24.

When the application 21 receives a job setting request from the user (S5), it supplies the job setting request to the request management unit 221 (S6). In response to the job setting request, the request management unit 221 requests the API log management unit 222a to record an API log (S7), and transmits the job setting request to a predetermined device 1 (S8). In response, the API log management unit 222a generates and holds an API log. The predetermined device 1 performs function settings according to the job setting request, and returns a job setting OK response to the request management unit 221. Having communicated with the predetermined device 1, the request management unit 221 requests the packet log management unit 222d to record a packet log (S9). In response, the packet log management unit 222d generates and maintains a packet log.

When the request management unit 221 receives a response indicating that the job setting is OK from the predetermined device 1 (S10), it requests the screen log management unit 222c to record the screen (S11). In response to this, the screen log management unit 222c generates and holds a screen log according to the information on the screen of the display device 24.

When the application receives a job start request from the user (S12), the application supplies the job start request to the request management unit 221 (S13). In response to the job start request, the request management unit 221 requests the API log management unit 222a to record the API log (S14), requests the job log management unit 222b to record the job log (S15), and requests the API log management unit 222a to record the job log (S15). The request is sent to a predetermined device 1 (S16). In response, the API log management unit 222a generates and holds an API log, the job log management unit 222b generates and holds a job log, and the predetermined device 1 performs functions according to the job start request. Try to start the operation. At this time, if the predetermined device 1 is unable to start its operation due to some problem, it returns a job start NG response to the request management unit 221 (S17). Having communicated with the predetermined device 1, the request management unit 221 requests the packet log management unit 222d to record a packet log (S18). In response, the packet log management unit 222d generates and maintains a packet log.

Further, since the request management unit 221 receives a response indicating that the job is not started from the predetermined device 1, it requests the error log management unit 222e to record an error log (S19). In response, the error log management unit 222e generates and maintains an error log. The request management unit 221 notifies the application 21 that the job start has resulted in an error (S20). In response, the application 21 notifies the user that the job start has resulted in an error by displaying a message on the screen of the display device 24 (S21).

These logs can be obtained upon request from the user. Note that FIG. 4 shows an example in which logs are acquired via a predetermined device (MFP) 1. The predetermined device (MFP) 1 receives an instruction (log acquisition request) from the user to acquire log information via the operation input device 14 (S22). The predetermined device (MFP) 1 transmits a log acquisition request to the connected information processing device (portable terminal) 2 in accordance with the instruction from the user (S23). When the relay application 22 receives a log acquisition request from a predetermined device (MFP) 1, the relay application 22 collects a plurality of types of logs stored in the information processing device (mobile terminal) 2, respectively. That is, upon receiving a log acquisition request from a predetermined device (MFP) 1, the request management unit 221 sends the API log management unit 222a, job log management unit 222b, screen log management unit 222c, and packet log management unit of the log management unit 222. 222d and the error log management unit 222e respectively (S24 to S28). The request management unit 221 receives logs from the API log management unit 222a, job log management unit 222b, screen log management unit 222c, packet log management unit 222d, and error log management unit 222e of the log management unit 222, respectively. The request management unit 221 generates information in which multiple types of logs received are integrated. Information obtained by integrating multiple types of logs collected by the relay application is transmitted and output to the predetermined device (MFP) 1 that sent the log acquisition request (S29). The predetermined device (MFP) 1 obtains a log (for example, an MFP log) in the predetermined device (MFP) 1 (S30), and combines the obtained log with multiple types obtained from the information processing device (mobile terminal) 2. The information obtained by integrating the logs is further integrated and generated as information for failure analysis and output (S31). The output of information for failure analysis includes display output on the screen of the display device 12 of the predetermined device (MFP) 1, print output from the predetermined device (MFP) 1, and output from the predetermined device (MFP) 1 connected to the predetermined device (MFP) 1. It includes a transmission output to an external device (for example, the display control unit 215 of the information processing device 2). For example, by printing out information in which the log of a predetermined device (MFP) 1 and the log of the information processing device (portable terminal) 2 are integrated, the analysis time can be shortened. Alternatively, if the predetermined device (MFP) 1 further includes a memory card as the external storage device 15, the predetermined device (MFP) 1 may output the information for failure analysis by writing it to the memory card.

Note that the log acquisition request can be made by requesting the information processing device (mobile terminal) 2 from a predetermined device (MFP) 1 to acquire the log at the requested timing, or by sequentially requesting the information processing device (mobile terminal) 2 to obtain the log from the information processing device (mobile terminal) 2. One possible method is to send the log to the device (MFP) 1. FIG. 4 exemplifies a method in which a predetermined device (MFP) 1 makes an acquisition request to an information processing device (portable terminal) 2 at a requested timing. Furthermore, it may be possible to specify whether or not to record a log on a setting screen displayed on the display device 24 of the information processing device (mobile terminal) 2.

As described above, in the system 100, information is generated by integrating a plurality of types of logs recorded when the developer function is enabled in the information processing device 2, and is transmitted to a predetermined device 1. Thereby, a predetermined device can obtain its own log, generate information by further integrating the log with received information, and output it in a predetermined method. As a result, by allowing developers to view information that combines the integrated log of information processing device 2 and the log of predetermined device 1, it is possible for developers to collectively manage information for trouble analysis. It can be done. This eliminates the need for developers to replace middleware for defect analysis, reducing interaction with vendors and shortening the development period.

Note that, as shown in FIG. 10, the log acquisition request is made even if the information processing device (mobile terminal) 2 is configured to acquire logs (for example, MFP log, screen log) from a predetermined device (MFP) 1. good. At this time, the predetermined device (MFP) 1 may save information on the screen of the display device 12 as a screen log in response to a request from the request management unit 221. FIG. 10 is a sequence diagram showing the operation of the system 100 according to the first modification of the embodiment.

As shown in FIG. 10, for example, upon receiving a job setting request from a user (S41), the application supplies the job setting request to the request management unit 221 (S42). In response to the job setting request, the request management unit 221 requests the API log management unit 222a to record an API log (S43), and transmits the job setting to a predetermined device 1 (S44). In response, the API log management unit 222a generates and holds an API log. The predetermined device 1 performs function settings according to the job setting request. Since the functions have been set, the predetermined device 1 generates and holds a screen log according to the information on the screen of the display device 12 (S45). Having communicated with the predetermined device 1, the request management unit 221 requests the packet log management unit 222d to record a packet log (S46). When the request management unit 221 receives a response indicating that the job setting is OK from the predetermined device 1 (S47), it requests the screen log management unit 222c to record the screen (S48).

When the application 21 receives a job start request from the user (S49), it supplies the job start request to the request management unit 221 (S50). In response to the job start request, the request management unit 221 requests the API log management unit 222a to record the API log (S51), requests the job log management unit 222b to record the job log (S52), and requests the API log management unit 222a to record the job log (S52). The request is sent to a predetermined device 1 (S53). In response, the API log management unit 222a generates and holds an API log. The predetermined device 1 attempts to start operating with a function corresponding to the job start request. At this time, if the predetermined device 1 cannot start operation due to some kind of malfunction, it generates and holds a screen log according to the information on the screen of the display device 12 (S54), and sends a response of job start NG to the request management section. 221 (S55). Having communicated with the predetermined device 1, the request management unit 221 requests the packet log management unit 222d to record a packet log (S56). In response, the packet log management unit 222d generates and maintains a packet log.

Further, since the request management unit 221 receives a response indicating that the job is not started from the predetermined device 1, it requests the error log management unit 222e to record an error log (S57). In response, the error log management unit 222e generates and maintains an error log. The request management unit 221 notifies the application 21 that the job start has resulted in an error (S58). In response, the application 21 notifies the user that the job start has resulted in an error by displaying a message on the screen of the display device 24 (S59).

Further, the application 21 of the information processing device (mobile terminal) 2 receives an instruction (log acquisition request) from the user to acquire log information via the operation input device 26 (S60). The application supplies a log acquisition request to the request management unit 221 (S61). Upon receiving the log acquisition request, the request management unit 221 sends logs to the API log management unit 222a, job log management unit 222b, screen log management unit 222c, packet log management unit 222d, and error log management unit 222e of the log management unit 222, respectively. The log acquisition request is supplied (S62 to S66) and the log acquisition request is sent to a predetermined device (MFP) 1 (S67). The request management unit 221 receives logs from the API log management unit 222a, job log management unit 222b, screen log management unit 222c, packet log management unit 222d, and error log management unit 222e of the log management unit 222, and also receives logs from the API log management unit 222a, job log management unit 222b, screen log management unit 222c, packet log management unit 222d, and error log management unit 222e. Receive logs from device (MFP) 1. The request management unit 221 generates information that integrates multiple types of logs received from the log management unit 222, and also generates information that integrates the logs in a predetermined device (MFP) 1 (e.g., MFP log) and the information processing device (mobile terminal). ) The information obtained by integrating the plurality of types of logs obtained from step 2 is further integrated to generate information for trouble analysis. The request management unit 221 outputs information for failure analysis to the display control unit 215 of the application 21 as a log acquisition result (S68). As a result, information for failure analysis is displayed on the screen of the display device 24 of the information processing device (portable terminal) 2 and notified to the user (S69).

Alternatively, as shown in FIG. 11, in response to log printing being selected from the middleware developer menu of the predetermined device (MFP) 1, the operation mode of the information processing device (mobile terminal) 2 is set to log printing mode. may be changed to FIG. 11 is a sequence diagram showing the operation of the system 100 according to the second modification of the embodiment. The predetermined device (MFP) 1 receives an instruction to print a log (log print request) from the user via the operation input device 14 (S71). A predetermined device (MFP) 1 transmits a log acquisition request to a connected information processing device (portable terminal) 2 in accordance with an instruction from a user. When the relay application 22 receives a log acquisition request from the predetermined device (MFP) 1, the operation mode of the information processing device (mobile terminal) 2 is changed to log printing mode, and the relay application changes the operation mode of the information processing device (mobile terminal) 2 to the log printing mode. Collect multiple types of logs stored in the system. That is, when the request management unit 221 receives a log acquisition request from the predetermined device (MFP) 1 (S72), the request management unit 221 sends the API log management unit 222a, the job log management unit 222b, the screen log management unit 222c, and the packet A log acquisition request is supplied to the log management unit 222d and the error log management unit 222e, respectively (S73 to S77). The request management unit 221 receives logs from the API log management unit 222a, job log management unit 222b, screen log management unit 222c, packet log management unit 222d, and error log management unit 222e of the log management unit 222, respectively. The request management unit 221 generates information in which multiple types of logs received are integrated. Information obtained by integrating multiple types of logs collected by the relay application 22 is transmitted and output to the predetermined device (MFP) 1 that has transmitted the log acquisition request (S78). The predetermined device (MFP) 1 obtains a log (for example, an MFP log) in the predetermined device (MFP) 1 (S79), and combines the obtained log with multiple types obtained from the information processing device (mobile terminal) 2. The information obtained by integrating the logs of and the information obtained by further integrating the logs are generated as information for trouble analysis and output by printing (S80). This also allows developers to collectively manage information for defect analysis by allowing the developer to view information in which the integrated log of the information processing device 2 and the log of a predetermined device 1 are combined. can be made possible.

Alternatively, as shown in FIG. 12, error locations and countermeasures may be presented to the user. FIG. 12 is a diagram showing the operation of the system 100 according to the third modification of the embodiment. For example, if the API log shows the error location as shown in FIG. 12(a), analysis can be done by showing the user an example of the countermeasure as shown in FIG. 12(b) by displaying it on the display device 12, etc. , countermeasures can be taken efficiently. That is, if there is a mistake in the usage of the middleware, the display control unit (countermeasure presentation means) 215 of the application may present the error and an example of the countermeasure to the user. This allows you to identify middleware errors, such as the wrong order of middleware calls, and suggest countermeasures, thereby shortening the time it takes to resolve the problem.

Further, the information processing device 2 is not limited to a mobile terminal as long as it is a device equipped with a communication function. The information processing device 2 is, for example, an output device such as a PJ (Projector), an IWB (Interactive White Board: a whiteboard having an electronic blackboard function that allows mutual communication), a digital signage, or a HUD (Head Up Display) device. , industrial machinery, imaging devices, sound collection devices, medical equipment, network home appliances, automobiles (Connected Cars), notebook PCs (Personal Computers), mobile phones, smartphones, tablet terminals, game consoles, PDAs (Personal Digital Assistants), digital cameras. , a wearable PC, a desktop PC, or the like.

The information processing device 2 may be, for example, a smartphone 4 as shown in FIG. 13. FIG. 13 is a diagram showing the hardware configuration of the smartphone 4 as an example of the hardware configuration of the information processing device 2 in the embodiment and the first to third modifications thereof. As shown in FIG. 13, the smartphone 4 includes a CPU 401, a ROM 402, a RAM 403, an EEPROM 404, a CMOS sensor 405, an image sensor I/F 406, an acceleration/direction sensor 407, a media I/F 409, and a GPS receiving section 411. There is.

Among these, the CPU 401 controls the operation of the smartphone 4 as a whole. The ROM 402 stores the CPU 401 and programs used to drive the CPU 401 such as IPL. RAM 403 is used as a work area for CPU 401. The EEPROM 404 reads or writes various data such as smartphone programs under the control of the CPU 401. A CMOS (Complementary Metal Oxide Semiconductor) sensor 405 is a type of built-in imaging means that images a subject (mainly a self-portrait) and obtains image data under the control of the CPU 401. Note that an imaging means such as a CCD (Charge Coupled Device) sensor may be used instead of the CMOS sensor. The image sensor I/F 406 is a circuit that controls driving of the CMOS sensor 405. The acceleration/direction sensor 407 is a variety of sensors such as an electronic magnetic compass, a gyro compass, and an acceleration sensor that detect geomagnetism. A media I/F 409 controls reading or writing (storage) of data to a recording medium 408 such as a flash memory. GPS receiving section 411 receives GPS signals from GPS satellites.

The smartphone 4 also includes a long-distance communication circuit 412, a CMOS sensor 413, an image sensor I/F 414, a microphone 415, a speaker 416, a sound input/output I/F 417, a display 418, an external device connection I/F (Interface) 419, and a nearby It includes a distance communication circuit 420, an antenna 420a of a short distance communication circuit 420, and a touch panel 421.

Among these, the long distance communication circuit 412 is a circuit that communicates with other devices via the network 3. The CMOS sensor 413 is a type of built-in imaging means that images a subject and obtains image data under the control of the CPU 401. The image sensor I/F 414 is a circuit that controls driving of the CMOS sensor 413. Microphone 415 is a built-in circuit that converts sound into electrical signals. The speaker 416 is a built-in circuit that converts electrical signals into physical vibrations to produce sounds such as music and voice. The sound input/output I/F 417 is a circuit that processes input/output of sound signals between the microphone 415 and the speaker 416 under the control of the CPU 401 . The display 418 is a type of display means such as a liquid crystal or organic EL (Electro Luminescence) that displays an image of a subject, various icons, and the like. The external device connection I/F 419 is an interface for connecting various external devices. The near field communication circuit 420 is a communication circuit such as NFC (Near Field Communication) or Bluetooth (registered trademark). The touch panel 421 is a type of input means by which the user operates the smartphone 4 by pressing the display 418.

The smartphone 4 also includes a bus line 410. The bus line 410 is an address bus, a data bus, etc. for electrically connecting each component such as the CPU 401 shown in FIG. 13.

Furthermore, the predetermined device 1 may be an MFP 9 as shown in FIG. FIG. 14 is a diagram showing the hardware configuration of the MFP 9 as an example of the hardware configuration of the predetermined device 1 in the embodiment and the first to third variations thereof. As shown in FIG. 14, the MFP (Multifunction Peripheral/Product/Printer) 9 includes a controller 910, a short-range communication circuit 920, an engine control section 930, an operation panel 940, and a network I/F 950.

Among these, the controller 910 includes a CPU 901, a system memory (MEM-P) 902, a north bridge (NB) 903, a south bridge (SB) 904, an ASIC (Application Specific Integrated Circuit) 906, and a storage unit, which are the main parts of the computer. It has a local memory (MEM-C) 907, an HDD controller 908, and an HD 909 as a storage unit, and has a configuration in which the NB 903 and the ASIC 906 are connected by an AGP (Accelerated Graphics Port) bus 921.

Among these, the CPU 901 is a control unit that performs overall control of the MFP 9. NB903 is a bridge for connecting CPU901, MEM-P902, SB904, and AGP bus 921, and is a memory controller that controls reading and writing to MEM-P902, and a PCI (Peripheral Component Interconnect) master and AGP target. has.

The MEM-P 902 consists of a ROM 902a that is a memory for storing programs and data that realize each function of the controller 910, and a RAM 902b that is used as a memory for developing programs and data, and for drawing when printing the memory. Note that the program stored in the RAM 902b is configured to be provided as an installable or executable file recorded on a computer-readable recording medium such as a CD-ROM, CD-R, or DVD. You may.

SB904 is a bridge for connecting NB903, PCI devices, and peripheral devices. The ASIC 906 is an IC (Integrated Circuit) for image processing that includes hardware elements for image processing, and has the role of a bridge that connects the AGP bus 921, the PCI bus 922, the HDD controller 908, and the MEM-C 907, respectively. This ASIC906 includes a PCI target and an AGP master, an arbiter (ARB) that is the core of the ASIC906, a memory controller that controls the MEM-C907, and multiple DMACs (Direct Memory Access Controllers) that rotate image data using hardware logic, etc. , and a PCI unit that transfers data between the scanner section 931 and the printer section 932 via the PCI bus 922. Note that the ASIC 906 may be connected to a USB (Universal Serial Bus) interface or an IEEE 1394 (Institute of Electrical and Electronics Engineers 1394) interface.

MEM-C907 is a local memory used as a copy image buffer and code buffer. The HD 909 is a storage for storing image data, font data used during printing, and forms. The HD 909 controls data reading or writing to the HD 909 under the control of the CPU 901 . AGP bus 921 is a bus interface for graphics accelerator cards proposed to speed up graphics processing, and can speed up graphics accelerator cards by directly accessing MEM-P902 with high throughput. .

Further, the short-range communication circuit 920 includes a short-range communication circuit 920a. The short-range communication circuit 920 is a communication circuit such as NFC or Bluetooth.

Further, the engine control section 930 includes a scanner section 931 and a printer section 932. The operation panel 940 also includes a panel display section 940a such as a touch panel that displays current setting values, a selection screen, etc., and accepts input from the operator, as well as displaying setting values for image forming conditions such as density setting conditions. An operation panel 940b is provided, which includes a numeric keypad for accepting instructions, a start key for accepting copy start instructions, and the like. The controller 910 controls the entire MFP 9, and controls, for example, drawing, communication, input from the operation panel 940, and the like. The scanner section 931 or the printer section 932 includes image processing sections such as error diffusion and gamma conversion.

Note that the MFP 9 can sequentially switch and select the document box function, copy function, printer function, and facsimile function using the application switching key on the operation panel 940. When the document box function is selected, the mode becomes document box mode, when the copy function is selected, the mode becomes copy mode, when the printer function is selected, the mode becomes printer mode, and when the facsimile mode is selected, the mode becomes facsimile mode.

Further, the network I/F 950 is an interface for data communication using the network 3. Near field communication circuit 920 and network I/F 950 are electrically connected to ASIC 906 via PCI bus 922.

Moreover, each function of the embodiment described above can be realized by one or more processing circuits. Here, the term "processing circuit" as used herein refers to a processor programmed to execute each function by software, such as a processor implemented by an electronic circuit, or a processor designed to execute each function explained above. devices such as ASICs (Application Specific Integrated Circuits), DSPs (Digital Signal Processors), FPGAs (Field Programmable Gate Arrays), and conventional circuit modules. shall be included.

Furthermore, the programs executed by each device of this embodiment are files in an installable or executable format and can be stored on a computer such as a CD-ROM, a flexible disk (FD), a CD-R, or a DVD (Digital Versatile Disk). Provided recorded on a readable recording medium.

Further, the program executed by each device of this embodiment may be stored on a computer connected to a network such as the Internet, and may be provided by being downloaded via the network. Furthermore, the program executed by the apparatus of this embodiment may be provided or distributed via a network such as the Internet.

Further, the program of this embodiment may be configured to be provided by being incorporated in a ROM or the like in advance.

The program executed by each device of this embodiment has a module configuration including the above-mentioned parts, and in actual hardware, a CPU (processor) reads the program from the storage medium and executes it. Each part is loaded onto the main memory, and each part is created on the main memory.

Further, in the above embodiment, an example will be described in which the image forming apparatus of the present invention is applied to a multifunction device having at least two functions among a copy function, a printer function, a scanner function, and a facsimile function. The present invention can be applied to any image forming apparatus such as a printer, a scanner device, a facsimile device, or the like.

1 Predetermined device 2 Information processing device 3 Network 100 System

JP2012-216982A Japanese Patent Application Publication No. 2014-21874

Claims (6)

Utilization means for utilizing functions of a predetermined device having middleware via the middleware;
a changing means for changing the operation according to a request selected from a developer menu when the developer function of the middleware is enabled;
generating means for generating information that integrates multiple types of logs recorded when the developer function is enabled;
transmitting means for transmitting the information to the predetermined device;
a log acquisition unit that acquires information on the screen of the information processing device as a screen log at the timing when a relay application that relays transmission of a request from an application to the predetermined device is used;
An information processing device comprising: The functions of the predetermined device include a printing function,
2. The information processing apparatus according to claim 1 , wherein the utilization means causes the predetermined apparatus to print a log of the predetermined apparatus and a log of the information processing apparatus. 3. The information processing apparatus according to claim 1, further comprising countermeasure presenting means for displaying countermeasures against errors in the usage of the middleware. a predetermined device;
an information processing device capable of communicating with the predetermined device;
Equipped with
The information processing device includes:
Utilization means for utilizing functions of a predetermined device having middleware via the middleware;
a changing means for changing the operation according to a request selected from a developer menu when the developer function of the middleware is enabled;
generating means for generating information that integrates multiple types of logs recorded when the developer function is enabled;
transmitting means for transmitting the information to the predetermined device;
a log acquisition unit that acquires information on the screen of the information processing device as a screen log at a timing when a relay application that relays transmission of a request from an application to the predetermined device is used;
A system characterized by having. a step of utilizing the functions of a predetermined device having middleware via the middleware;
changing the operation according to a request selected by a developer menu when the developer function of the middleware is enabled;
a step of generating information that integrates multiple types of logs recorded when the developer function is enabled;
transmitting the information to the predetermined device;
acquiring information on the screen of the information processing device as a screen log at the timing when a relay application that relays transmission of a request from the application to the predetermined device is used;
An information processing method characterized by comprising: In the information processing device,
a step of using functions of a predetermined device via middleware;
changing the operation according to a request selected by a developer menu when the developer function of the middleware is enabled;
a step of generating information that integrates multiple types of logs recorded when the developer function is enabled;
transmitting the information to the predetermined device;
acquiring information on the screen of the information processing device as a screen log at the timing when a relay application that relays transmission of a request from an application to the predetermined device is used;
A program characterized by executing.

Images