An image forming drive compliance detection method, device and storage medium

Abstract

Embodiments of the present application provide an image forming drive compliance detection method and device and a storage medium. The method comprises: obtaining a configuration file of a drive to be detected, the configuration file being used to describe functional feature information of an image forming device; and performing matching verification on the configuration file and a configuration standard to obtain a compliance detection result of the drive to be detected, the compliance detection result being used to represent whether the configuration file meets requirements. In the embodiments of the present application, the configuration file of the drive program is verified based on the formulated configuration standard, so that the drive program can be executed according to the recommended configuration standard, and the compatibility between the application software and the drive program is improved.

Description

Technical Field

[0001] This application relates to the field of image forming technology, and more specifically to an image forming-driven compliance detection method, apparatus, and storage medium. Background Technology

[0002] An image forming apparatus is a device that forms an image on a recording medium using imaging principles, such as a printer, copier, fax machine, multifunction image production and copying apparatus, electrostatic printing apparatus, and any other similar apparatus. During the image forming process, the user can send image forming commands to the driver program (image forming driver) via application software (image forming application). The driver program then converts the image forming commands into image forming data that the image forming apparatus can recognize and performs the image forming operation based on this data.

[0003] However, in practical applications, due to the different function options set in the drivers by different image forming apparatus manufacturers or the inconsistent descriptions of the specific functions of the function options, the compatibility between the application software and the driver is poor. This may cause the driver to be unable to recognize certain function options issued by the application software, making the function options ineffective and thus affecting the user's normal use of the image forming apparatus.

[0004] It should be noted that the information disclosed in the background section of this application is intended only to enhance the understanding of the general background of this application, and should not be construed as an admission or in any way implying that the information constitutes prior art known to those skilled in the art. Summary of the Invention

[0005] In view of this, this application provides an image forming driver compliance detection method, apparatus and storage medium to help solve the problem of poor compatibility between application software and driver in the prior art.

[0006] In a first aspect, embodiments of this application provide an image formation-driven compliance detection method, including:

[0007] Obtain the configuration file of the driver to be detected, which describes the functional characteristics of the image forming apparatus;

[0008] The configuration file is matched and verified against the configuration standard to obtain the compliance test result of the driver to be tested. The compliance test result is used to characterize whether the configuration file meets the requirements.

[0009] In one possible implementation, the step of matching and verifying the configuration file against the configuration standard to obtain the compliance detection result of the driver to be detected includes:

[0010] Determine whether the configuration file conforms to the configuration specifications in the configuration standard;

[0011] If the configuration file is determined to conform to the configuration specifications in the configuration standard, a detection result indicating conformity with the configuration specifications is obtained.

[0012] If it is determined that the configuration file does not conform to the configuration specifications in the configuration standard, a detection result indicating that it does not meet the configuration specification requirements is obtained.

[0013] In one possible implementation, after determining that the configuration file conforms to the configuration specifications in the configuration standard, the method further includes:

[0014] Iterate through the function options in the configuration file, and determine in turn whether each function option in the configuration file is a common option, and obtain the common option determination result for each function option. The common option is a necessary option specified in the configuration standard.

[0015] If the function option i in the configuration file is a common option, then determine whether the option value of the function option i meets the requirements of the configuration standard;

[0016] If the option value of function option i meets the requirements of the configuration standard, then the detection result of the option value of function option i being valid is obtained;

[0017] If the option value of function option i does not meet the requirements of the configuration standard, a detection result indicating that the option value of function option i is invalid is obtained.

[0018] Wherein, function option i is any one of the function options in the configuration file.

[0019] In one possible implementation, the method further includes:

[0020] Based on the result of judging the common options of all the function options, determine whether the configuration file is missing any necessary common options;

[0021] If the configuration file does not lack any necessary common options, then the detection result is that no common options are missing.

[0022] If the configuration file lacks necessary common options, a detection result indicating missing common options is obtained.

[0023] In one possible implementation, the method further includes:

[0024] The configuration file displays the function options and the corresponding option values ​​for each function option.

[0025] In one possible implementation, before obtaining the configuration file of the driver to be detected, the method further includes:

[0026] In response to the user's image forming apparatus selection operation, the image forming apparatus to be detected is determined;

[0027] The driver to be detected is the driver of the image forming apparatus to be detected.

[0028] In one possible implementation, the configuration file is a PPD file.

[0029] In one possible implementation, after obtaining the compliance detection result of the driver to be detected, the method further includes:

[0030] Output the compliance test results of the driver to be tested.

[0031] Secondly, embodiments of this application provide an image forming-driven compliance detection device, comprising:

[0032] The acquisition module is used to acquire the configuration file of the driver to be detected, the configuration file being used to describe the functional feature information of the image forming apparatus;

[0033] The verification module is used to match and verify the configuration file with the configuration standard to obtain the compliance detection result of the driver to be detected. The compliance detection result is used to characterize whether the configuration file meets the requirements.

[0034] Thirdly, embodiments of this application provide an image forming-driven compliance detection device, comprising:

[0035] processor;

[0036] Memory;

[0037] And a computer program, wherein the computer program is stored in the memory, the computer program including instructions that, when executed by the processor, cause the apparatus to perform the method described in any one of the first aspects.

[0038] Fourthly, embodiments of this application provide a computer-readable storage medium including a stored program, wherein, when the program is executed, it controls the device where the computer-readable storage medium is located to perform the method described in any one of the first aspects.

[0039] In this embodiment of the application, the configuration file of the driver is matched and verified based on the established configuration standard, so that the driver can execute according to the recommended configuration standard, thereby improving the compatibility between the application software and the driver. Attached Figure Description

[0040] To more clearly illustrate the technical solutions of the embodiments of this application, the drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0041] Figure 1 This is a schematic diagram of an application scenario provided by an embodiment of this application;

[0042] Figure 2 An image formation-driven compliance detection system architecture diagram provided in this application embodiment.

[0043] Figure 3 A flowchart illustrating the usage method of a driver detection tool provided in this application embodiment.

[0044] Figures 4A-4D This is a schematic diagram illustrating another application scenario provided by an embodiment of this application;

[0045] Figure 5 A flowchart illustrating an image formation-driven compliance detection method provided in this application embodiment;

[0046] Figure 6 A flowchart illustrating another image formation-driven compliance detection method provided in this application embodiment;

[0047] Figure 7 This is a schematic diagram of the structure of an image forming driven compliance detection device provided in an embodiment of this application. Detailed Implementation

[0048] To better understand the technical solution of this application, the embodiments of this application will be described in detail below with reference to the accompanying drawings.

[0049] It should be understood that the described embodiments are merely some, not all, of the embodiments in this application. All other embodiments obtained by those skilled in the art based on the embodiments in this application without inventive effort are within the scope of protection of this application.

[0050] The terminology used in the embodiments of this application is for the purpose of describing particular embodiments only and is not intended to be limiting of this application. The singular forms “a,” “the,” and “the” used in the embodiments of this application and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise.

[0051] It should be understood that the term "and / or" used in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this article generally indicates that the preceding and following related objects have an "or" relationship.

[0052] See Figure 1 This is a schematic diagram illustrating an application scenario provided by an embodiment of this application. For example... Figure 1 As shown, this application scenario includes a control device 110 and an image forming apparatus 120. The control device 110 and the image forming apparatus 120 are interconnected via a wired or wireless communication network for information transmission. During the image forming process, the control device 110 converts the image forming file into image forming data that can be recognized by the image forming apparatus 120, and sends the image forming data to the image forming apparatus 120, which then performs the image forming operation.

[0053] Specifically, the control device 110 may be equipped with application software (image forming application) and driver (image forming driver). The user can send image forming instructions to the driver through the application software. The driver converts the image forming instructions into image forming data that the image forming device can recognize, and performs image forming operations based on the image forming data.

[0054] It should be noted that, in addition to being installed in the control device 110, the application software and driver can also be selectively installed in the image forming apparatus 120. For example, the application software can be installed in the control device 110 and the driver can be installed in the image forming apparatus 120; or, both the application software and the driver can be installed in the image forming apparatus 120. It is understood that when both the application software and the driver are installed in the image forming apparatus 120, the control device 110 may not be necessary during the image forming process.

[0055] in addition, Figure 1 The control device 110 and image forming apparatus 120 shown are merely exemplary descriptions and should not be construed as limiting the scope of protection of this application. For example, the image forming apparatus 120 includes, but is not limited to, printers, copiers, fax machines, multi-function image making and copying apparatuses, electrostatic printing apparatuses, and any other similar devices; the control device 110 includes, but is not limited to, electronic devices capable of communicating with the image forming apparatus 120, such as computers, mobile phones, tablet computers, enterprise internal servers, and cloud servers.

[0056] In practical applications, poor compatibility between application software and drivers arises because different image forming apparatus manufacturers set different function options in their drivers or provide inconsistent descriptions of those options. The applicant's research revealed that this compatibility issue primarily stems from inconsistencies between the parameters provided by the application software and the driver's supported capabilities. This leads to a lack of coordination between the application and the print driver, ultimately affecting the user's normal use of the image forming apparatus.

[0057] For example, the option values ​​of the function options issued by the application software are different from the corresponding option values ​​in the driver. For instance, the option value of the color mode issued by the application software is "RGB", while the option value of the color mode defined in the driver is "color". This causes the driver to be unable to understand the option value of the color mode issued by the application software, and thus cannot perform the image forming operation normally according to the user's settings.

[0058] For example, the application software may provide incomplete function options. For instance, in the application software, the user device's resolution is 1200 DPI with a light density setting; the driver's default resolution is 600 DPI with normal density. However, because the application software's function options do not include resolution and density, the image forming apparatus cannot perform image forming operations according to the user device's resolution and density, affecting the user experience.

[0059] To address the aforementioned issues, this application provides an image forming driver compliance detection method. This method verifies the driver's configuration file based on established configuration standards, ensuring the driver executes according to the recommended standards and thus improving compatibility between application software and the driver. Specifically, this image forming driver compliance detection method can be implemented using an image forming driver compliance detection tool (hereinafter referred to as the "driver detection tool"). This driver detection tool can be a software program, and its implementation will be described in detail below.

[0060] See Figure 2 This is a diagram illustrating the architecture of an image-forming driven compliance detection system provided in an embodiment of this application. Figure 2 As shown, the system includes a driver detection tool, a system driver, a driver to be detected, and a system backend. Since the system driver, the driver to be detected, and the system backend are based on CUPS (Common UNIX Printing System), the driver detection tool can communicate with the system driver through the CUPS interface (CUPS API), and thus with the driver to be detected and the system backend.

[0061] It should be noted that since the research focus of this application is on the relationship between the driver detection tool and the driver to be detected, the following text will focus on these two parts. For the specific content of the system driver and the system backend, please refer to the relevant descriptions in the prior art. For the sake of brevity, they will not be repeated here.

[0062] Furthermore, the image forming-driven compliance detection system provided in this application embodiment can be deployed in Figure 1 In the control device 110 shown, or in the system, some functional units / modules are deployed in the control device 110, and other functional units / modules are deployed in the image forming apparatus 120. This application embodiment does not impose specific limitations on this.

[0063] See Figure 3 This is a schematic diagram illustrating the usage method of a driver detection tool provided in an embodiment of this application. Figure 3 As shown, it mainly includes the following steps.

[0064] Step S301: Open the driver detection tool.

[0065] like Figure 4A As shown, in this application scenario, the driver detection tool can be installed in the control device. Users can click the "Driver Detection Tool" control displayed on the screen through input devices such as mouse, keyboard or touch screen to input trigger commands in the control device and open the driver detection tool.

[0066] Step S302: Select the image forming apparatus to be detected.

[0067] Understandably, in practical applications, the same control device can connect to multiple image forming apparatuses. For example... Figure 4B As shown, after the driver testing tool is opened, three image forming devices are displayed on the tool's interface: image forming device 1, image forming device 2, and image forming device 3. Users can select any one of these image forming devices for driver compliance testing. For example, if a user wants to perform compliance testing on the driver for image forming device 2, they can click the "Image Forming Device 2" control displayed on the interface using an input device such as a mouse, keyboard, or touchscreen. At this time, image forming device 2 is selected. Figure 4C As shown.

[0068] Step S303: Input the start detection command.

[0069] In practice, after the user inputs the start test command, the driver testing tool begins to perform compliance testing on the driver program of the image forming apparatus selected by the user. For example, after the user selects image forming apparatus 2, they can continue to click the "Start Test" control displayed on the interface via an input device such as a mouse, keyboard, or touchscreen. The driver testing tool then begins to perform compliance testing on the driver program of image forming apparatus 2. Figure 4C As shown below, the detection process of the driver detection tool is described in detail.

[0070] Step S304: Output the compliance test results.

[0071] In practice, after the driver detection tool completes the driver detection, it can output the compliance detection results on the display interface for users to view, such as... Figure 4D As shown.

[0072] Understandable, Figure 3 This document primarily explains how to use driver detection tools from the user's perspective. The detection process of the driver detection tool is explained in detail below.

[0073] See Figure 5 This is a flowchart illustrating an image formation-driven compliance detection method provided in an embodiment of this application. This method can be applied to... Figure 1 In the application scenarios shown, the execution entity of this method can be... Figure 2 The driver detection tool shown is as follows: Figure 5 As shown, it mainly includes the following steps.

[0074] Step S501: Obtain the configuration file of the driver to be detected. The configuration file is used to describe the configuration information of the image forming apparatus.

[0075] In one application scenario, a driver detection tool can be installed in a control device, which can connect to multiple image forming apparatuses. After opening the driver detection tool, the user's interface displays the identifiers (which can be thumbnails and / or names of the image forming apparatuses connected to the control device). The user can then select one of these image forming apparatuses as the one to be detected. After determining the image forming apparatus to be detected, the corresponding driver to be detected can be determined based on it. In other words, the driver to be detected is the driver program corresponding to the image forming apparatus to be detected.

[0076] The configuration file involved in this application describes the functional characteristics of the image forming apparatus, such as the built-in fonts, paper sizes, optimized screens, and a list of resolution capabilities. This information is provided by the image forming apparatus manufacturer and reflects the most common configuration of the image forming apparatus.

[0077] In one possible implementation, the configuration file is a PPD (Postscript Printer Definition) file. Of course, in other application scenarios or system environments, the configuration file may be other types of files, and this application embodiment does not impose specific limitations on this.

[0078] Step S502: Match and verify the configuration file with the configuration standard to obtain the compliance test results of the driver to be tested.

[0079] To address the poor compatibility issue between application software and drivers in existing technologies, the applicant has developed a configuration standard that specifies recommended parameters for various check items. For example, the check items include various functional options; the functional options involved in this application's embodiments include public and private options. For public options, all image forming apparatus manufacturers must comply to ensure compatibility between application software and drivers; for private options, each image forming apparatus manufacturer can customize the settings, and the manufacturer is responsible for ensuring the functionality of the private options. In this application's embodiments, "compliance testing of the driver's configuration file" mainly refers to testing the public options in the driver's configuration file.

[0080] In practice, configuration standards can be pre-defined in the driver detection tool. After obtaining the configuration file of the driver to be tested, the tool can match and verify the configuration file against the configuration standards to obtain the compliance test result of the driver. Specifically, if the check items in the configuration file meet the requirements of the configuration standards, the test passes; if the check items in the configuration file do not meet the requirements of the configuration standards, the test fails. Furthermore, if the test fails, the user can modify the driver program according to the prompts from the driver detection tool until the test passes.

[0081] To facilitate understanding, the detection process of each check item in the driver detection tool will be explained below with reference to a specific implementation method.

[0082] See Figure 6 This is a flowchart illustrating another image-forming driven compliance detection method provided in this application embodiment. This method can be applied to... Figure 1 In the application scenarios shown, the execution entity of this method can be... Figure 2 The driver detection tool shown is as follows: Figure 6 As shown, it mainly includes the following steps.

[0083] Step S601: Obtain the configuration file of the driver to be detected.

[0084] Specifically, the user can select the image forming apparatus to be detected from among multiple image forming apparatuses, and then determine the driver of the image forming apparatus to be detected as the driver to be detected.

[0085] The configuration file of the driver to be tested describes the functional characteristics of the image forming apparatus, such as the built-in fonts, paper sizes, optimized screen settings, and a list of resolution capabilities. This information is provided by the image forming apparatus manufacturer and reflects the most common configuration of the image forming apparatus.

[0086] In one possible implementation, the configuration file is a PPD (Postscript Printer Definition) file. Of course, in other application scenarios or system environments, the configuration file may be other types of files, and this application embodiment does not impose specific limitations on this.

[0087] Step S602: Determine whether the configuration file conforms to the configuration specifications in the configuration standard.

[0088] To address the poor compatibility between application software and drivers in existing technologies, the applicant has developed a configuration standard that specifies recommended requirements for various check items.

[0089] In this embodiment, after obtaining the configuration file of the driver to be tested, the configuration file is first compared with the configuration specification in the configuration standard to determine whether the configuration file conforms to the configuration specification in the configuration standard. If the configuration file conforms to the configuration specification in the configuration standard, a detection result of conforming to the configuration specification requirement is obtained, and the process proceeds to step S603 to further determine the function options of the configuration file; if the configuration file does not conform to the configuration specification in the configuration standard, a detection result of not conforming to the configuration specification requirement is obtained, and the process proceeds to step S607.

[0090] Step S603: Traverse the function options in the configuration file.

[0091] For example, if the configuration file includes 10 function options, the subsequent judgment steps are executed sequentially for each of the 10 function options until the traversal is complete.

[0092] Step S604: Determine whether the function option i in the configuration file is a common option.

[0093] In this embodiment, function option i is any function option in the configuration file. That is, the same judgment steps are performed on any function option in the configuration file. For ease of explanation, function option i is used as an example in this document.

[0094] It is understood that the function options in the configuration file may be either common or private. For common options, all image forming apparatus manufacturers must comply to ensure compatibility between application software and drivers; for private options, each image forming apparatus manufacturer can customize the settings, and the manufacturer is responsible for ensuring the functionality of the private options. In other words, in this embodiment, only the conformity of common options with the recommended specifications in the configuration standard needs to be checked. Therefore, it is first necessary to determine whether function option i in the configuration file is a common option. If function option i is a common option, proceed to step S6041, i.e., obtain the detection result that function option i is a common option; if function option i is not a common option, proceed to step S6042, i.e., obtain the detection result that function option i is not a common option.

[0095] Step S605: Determine whether the option value of function option i meets the requirements of the configuration standard.

[0096] Specifically, if function option i in the configuration file is determined to be a common option, then the option value of function option i is further compared with the corresponding option value in the configuration standard to determine whether the option value of function option i meets the requirements of the configuration standard. If the option value of function option i meets the requirements of the configuration standard, then proceed to step S6051, that is, obtain the detection result that the option value of function option i is valid; if the option value of function option i does not meet the requirements of the configuration standard, then proceed to step S6052, that is, obtain the detection result that the option value of function option i is invalid.

[0097] Step S606: Has the function options in the configuration file been traversed completely?

[0098] It is understandable that the judgment steps S604 to S605 need to be executed for each function option in the configuration file. Therefore, if it is determined that the function options in the configuration file have not been traversed, it is necessary to return to step S604 and continue to execute the judgment steps S604 to S605 for the next function option; if it is determined that the function options in the configuration file have been traversed, then proceed to step S607.

[0099] In one possible implementation, after traversing all the function options in the configuration file, it can be further determined whether any necessary common options are missing from the configuration file's function options based on the results of judging the common options of all function options. Specifically, if no necessary common options are missing from the configuration file's function options, a detection result indicating that no common options are missing is obtained; otherwise, a detection result indicating that a common option is missing is obtained.

[0100] For example, if the configuration standard specifies that the driver's configuration file must contain 5 necessary common options, but the result of judging the common options of all function options indicates that the configuration file contains only 3 necessary common options, then the configuration file is considered to lack necessary common options; conversely, if the result of judging the common options of all function options indicates that the configuration file contains all 5 necessary common options, then the configuration file is considered to have no missing necessary common options.

[0101] Step S607: Output the compliance test results of the driver to be tested.

[0102] In practice, the compliance test result can include the overall test result or the test results of each inspection item. If all inspection items pass the test, the overall test result is considered passed; if any inspection item fails the test, the overall test result is considered failed.

[0103] In addition, the test results for each inspection item may include: meeting the configuration specification requirements, or not meeting the configuration specification requirements; function option i is a common option, or function option i is not a common option; the option value of function option i meets the configuration standard requirements, or the option value of function option i does not meet the configuration standard requirements; common options are not missing, or common options are not missing, etc.

[0104] In one possible implementation, outputting the compliance detection results of the driver to be detected may specifically include: displaying the compliance detection results in a display interface, such as... Figure 4D As shown. Of course, those skilled in the art can choose other output methods according to actual needs, such as voice broadcast of compliance test results; or, using an image forming apparatus to form the compliance test results (printed output), etc., and the embodiments of this application do not impose specific limitations on this.

[0105] It should be pointed out that, Figure 6 This is merely an illustrative example of an embodiment of this application and should not be construed as limiting the scope of protection of this application. Those skilled in the art can, according to actual needs, only select... Figure 6Some steps in the process perform compliance checks on the image forming driver, and all of these should fall within the scope of protection of this application.

[0106] Corresponding to the above embodiments, this application also provides an image forming driver compliance detection device, which includes: an acquisition module for acquiring a configuration file of a driver to be detected, the configuration file being used to describe the functional characteristics information of the image forming device; and a verification module for matching and verifying the configuration file with a configuration standard to obtain a compliance detection result of the driver to be detected, the compliance detection result being used to characterize whether the configuration file meets the requirements.

[0107] In one possible implementation, the verification module is specifically used to: determine whether the configuration file conforms to the configuration specifications in the configuration standard; if the configuration file conforms to the configuration specifications in the configuration standard, then obtain a detection result indicating that it conforms to the configuration specifications; if the configuration file does not conform to the configuration specifications in the configuration standard, then obtain a detection result indicating that it does not conform to the configuration specifications.

[0108] In one possible implementation, the verification module is further configured to: traverse the function options in the configuration file, sequentially determine whether each function option in the configuration file is a common option, and obtain the common option determination result for each function option, wherein the common option is a necessary option specified in the configuration standard; if function option i in the configuration file is a common option, then determine whether the option value of function option i meets the requirements of the configuration standard; if the option value of function option i meets the requirements of the configuration standard, then obtain a detection result that the option value of function option i is valid; if the option value of function option i does not meet the requirements of the configuration standard, then obtain a detection result that the option value of function option i is invalid; wherein, function option i is any function option in the configuration file.

[0109] In one possible implementation, the verification module is further configured to: determine whether the configuration file lacks necessary common options based on the common option judgment result of all the function options; if the configuration file does not lack necessary common options, then obtain a detection result that the common options are not missing; if the configuration file lacks necessary common options, then obtain a detection result that the common options are missing.

[0110] In one possible implementation, the verification module is further configured to: display the function options of the configuration file, and the option value corresponding to each function option.

[0111] In one possible implementation, the verification module is further configured to: determine the image forming apparatus to be detected in response to a user's image forming apparatus selection operation; the driver to be detected is the driver of the image forming apparatus to be detected.

[0112] It should be noted that the specific content involved in the embodiments of this application can be found in the description of the above method embodiments, and will not be repeated here for the sake of brevity.

[0113] Corresponding to the above embodiments, this application also provides another image forming driven compliance detection device.

[0114] See Figure 7 This is a schematic diagram of another image forming driven compliance detection device provided in an embodiment of this application. Figure 7 As shown, the image forming driver compliance detection device 700 may include a processor 701, a memory 702, and a communication unit 703. These components communicate via one or more buses. Those skilled in the art will understand that the structure of the image forming driver compliance detection device shown in the figure does not constitute a limitation on the embodiments of this application. It may be a bus-shaped structure or a star-shaped structure, and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0115] The communication unit 703 is used to establish a communication channel, thereby enabling the image forming drive compliance detection device to communicate with other devices.

[0116] The processor 701 serves as the control center of the image forming driver compliance detection device. It connects various parts of the device via various interfaces and lines, and executes software programs and / or modules stored in the memory 702, as well as calling data stored in the memory, to perform various functions and / or process data within the image forming driver compliance detection device. The processor can be composed of integrated circuits (ICs), such as a single packaged IC or multiple packaged ICs with the same or different functions connected together. For example, the processor 701 may consist only of a central processing unit (CPU). In this embodiment, the CPU may have a single processing core or include multiple processing cores.

[0117] Memory 702 is used to store the execution instructions of processor 701. Memory 702 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk or optical disk.

[0118] When the execution instructions in memory 702 are executed by processor 701, the image forming drive compliance detection device 700 is able to perform some or all of the steps in the above method embodiments.

[0119] Corresponding to the above embodiments, this application also provides a computer-readable storage medium, wherein the computer-readable storage medium may store a program, wherein when the program runs, it can control the device where the computer-readable storage medium is located to execute some or all of the steps in the above method embodiments. Specifically, the computer-readable storage medium may be a magnetic disk, an optical disk, read-only memory (ROM), or random access memory (RAM), etc.

[0120] Corresponding to the above embodiments, this application also provides a computer program product containing executable instructions that, when executed on a computer, cause the computer to perform some or all of the steps in the above method embodiments.

[0121] In this application embodiment, "at least one" refers to one or more, and "more than one" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent the existence of A alone, the simultaneous existence of A and B, or the existence of B alone. A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" and similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, and c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple.

[0122] Those skilled in the art will recognize that the units and algorithm steps described in the embodiments disclosed herein can be implemented using electronic hardware, computer software, or a combination of electronic hardware and software. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0123] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0124] In the several embodiments provided in this application, any function, if implemented as a software functional unit and sold or used as an independent product, can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0125] The above description is merely a specific embodiment of this application. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the protection scope of this application. The protection scope of this application should be determined by the protection scope of the claims.

Claims

1. An image formation-driven compliance detection method, characterized in that, include: Obtain the configuration file of the driver to be detected, which describes the functional characteristics of the image forming apparatus; The configuration file is matched and verified against the configuration standard to obtain the compliance test result of the driver to be tested. The compliance test result is used to characterize whether the configuration file meets the requirements. The step of matching and verifying the configuration file with the configuration standard to obtain the compliance detection result of the driver to be detected includes: Determine whether the configuration file conforms to the configuration specifications in the configuration standard; If the configuration file is determined to conform to the configuration specifications in the configuration standard, a detection result indicating compliance with the configuration specifications is obtained. If it is determined that the configuration file does not conform to the configuration specifications in the configuration standard, then a detection result indicating that it does not conform to the configuration specifications is obtained; After determining that the configuration file conforms to the configuration specifications in the configuration standard, the method further includes: Iterate through the function options in the configuration file, and determine in turn whether each function option in the configuration file is a common option, and obtain the common option determination result for each function option. The common option is a necessary option specified in the configuration standard. If the function option i in the configuration file is a common option, then determine whether the option value of the function option i meets the requirements of the configuration standard; If the option value of function option i meets the requirements of the configuration standard, then the detection result of the option value of function option i being valid is obtained; If the option value of function option i does not meet the requirements of the configuration standard, a detection result indicating that the option value of function option i is invalid is obtained. Wherein, function option i is any one of the function options in the configuration file.

2. The method according to claim 1, characterized in that, The method further includes: Based on the result of judging the common options of all the function options, determine whether the configuration file is missing any necessary common options; If the configuration file does not lack any necessary common options, then the detection result is that no common options are missing. If the configuration file lacks necessary common options, a detection result indicating missing common options is obtained.

3. The method according to claim 1, characterized in that, The method further includes: The configuration file displays the function options and the corresponding option values ​​for each function option.

4. The method according to claim 1, characterized in that, Before obtaining the configuration file of the driver to be detected, the method further includes: In response to the user's image forming apparatus selection operation, the image forming apparatus to be detected is determined; The driver to be detected is the driver of the image forming apparatus to be detected.

5. The method according to claim 1, characterized in that, The configuration file is a PPD file.

6. The method according to any one of claims 1-5, characterized in that, After obtaining the compliance detection result of the driver to be detected, the method further includes: Output the compliance test results of the driver to be tested.

7. An image formation-driven compliance detection device, characterized in that, include: The acquisition module is used to acquire the configuration file of the driver to be detected, the configuration file being used to describe the functional feature information of the image forming apparatus; The verification module is used to match and verify the configuration file with the configuration standard to obtain the compliance detection result of the driver to be detected. The compliance detection result is used to characterize whether the configuration file meets the requirements. The step of matching and verifying the configuration file with the configuration standard to obtain the compliance detection result of the driver to be detected includes: Determine whether the configuration file conforms to the configuration specifications in the configuration standard; If the configuration file is determined to conform to the configuration specifications in the configuration standard, a detection result indicating compliance with the configuration specifications is obtained. If it is determined that the configuration file does not conform to the configuration specifications in the configuration standard, then a detection result indicating that it does not conform to the configuration specifications is obtained; After determining that the configuration file conforms to the configuration specifications in the configuration standard, the device is further configured to: Iterate through the function options in the configuration file, and determine in turn whether each function option in the configuration file is a common option, and obtain the common option determination result for each function option. The common option is a necessary option specified in the configuration standard. If the function option i in the configuration file is a common option, then determine whether the option value of the function option i meets the requirements of the configuration standard; If the option value of function option i meets the requirements of the configuration standard, then the detection result of the option value of function option i being valid is obtained; If the option value of function option i does not meet the requirements of the configuration standard, a detection result indicating that the option value of function option i is invalid is obtained. Wherein, function option i is any one of the function options in the configuration file.

8. An image forming-driven compliance detection device, characterized in that, include: processor; Memory; And a computer program, wherein the computer program is stored in the memory, the computer program including instructions that, when executed by the processor, cause the apparatus to perform the method of any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a stored program, wherein, when the program is executed, it controls the device on which the computer-readable storage medium is located to perform the method according to any one of claims 1 to 6.

Images