Printing equipment data report generation method and device, equipment and storage medium

Abstract

The invention discloses a printing equipment data report generation method and device, equipment and a storage medium, and relates to the technical field of printing equipment monitoring. The equipment in the local area network is scanned by utilizing the ARP protocol, and the IP-MAC mapping table is generated, so that a basis is provided for subsequent equipment screening. And screening the local area network equipment based on the IP-MAC mapping table to obtain all printing equipment in the local area network as a candidate printing equipment set. And determining a target printing device set comprising different types of printing devices through an SNMP protocol and the candidate printing device set. And obtaining the printing quantity data of the target printing equipment through a pre-configured OID mapping table and an SNMP protocol, wherein the printing quantity data identifiers in the OID mapping table are in one-to-one correspondence with the OIDs. And finally, a printing equipment data report is generated based on the collected printing quantity data of each target printing equipment, so that a comprehensive and accurate printing equipment operation condition overview is provided for an enterprise or an institution, and optimization of printing resource management is facilitated.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of printing equipment monitoring, and more particularly to a printing equipment data report generation method and device, equipment and a storage medium. BACKGROUND

[0002] With the promotion of enterprise digital office, the management demand of printers as basic office equipment is increasing, especially the demand for unified monitoring and analysis of print volume data of multiple brands and types of printers is increasingly urgent. At present, the printing machine monitoring technology has obvious deficiencies in print volume data aggregation. The existing solutions can usually only collect and analyze data of specific brands or types of printers, and it is difficult to effectively integrate print volume data of different brands or types of printers, resulting in great challenges in collecting and aggregating print volume data of multiple types of printing equipment for the existing system, which affects the unified management and optimal configuration of printing resources. SUMMARY

[0003] In view of the above problems, the present application provides a printing equipment data report generation method, device, equipment and storage medium to aggregate print volume data of multiple types of printing equipment. The specific scheme is as follows:

[0004] In a first aspect, a printing equipment data report generation method is provided, comprising:

[0005] Scanning each device in the local area network based on an address resolution protocol (ARP) protocol, and generating an IP-MAC mapping table containing the mapping relationship between the IP address and the MAC address of each device in the local area network;

[0006] Performing a filtering operation on the devices in the local area network based on the IP address of each device in the IP-MAC mapping table to obtain a candidate printing equipment set, the candidate printing equipment set being all printing equipment in the local area network;

[0007] Determining a target printing equipment set through a simple network management protocol (SNMP) protocol and the candidate printing equipment set, the target printing equipment set including target printing equipment of different types;

[0008] Based on a pre-configured OID mapping table corresponding to the target printing equipment and the SNMP protocol, obtaining print volume data of the target printing equipment, the OID mapping table including the mapping relationship between at least one print volume data identifier and an object identifier (OID) in the target printing equipment, the number of print volume data identifiers being the same as the number of OIDs;

[0009] Generating a printing equipment data report based on each print volume data corresponding to the target printing equipment set.

[0010] In a possible design, in another implementation manner of the first aspect of the embodiment of the present application, the process of determining the target print device set from the candidate print device set through the simple network management protocol (SNMP) and the candidate print device set comprises the following steps.

[0011] The IP address of each candidate print device is used to obtain a first print device identifier set corresponding to the candidate print device through the SNMP.

[0012] A second print device identifier set pre-configured in the server is obtained.

[0013] The first print device identifier set and the second print device identifier set are compared to obtain a comparison result, wherein the comparison result comprises a target print device identifier set, a server-only print device identifier set and a client-only print device identifier set, the target print device identifier set comprises each print device identifier common to the first print device identifier set and the second print device identifier set, the server-only print device identifier set comprises each print device identifier existing in the second print device identifier set but not existing in the first print device identifier set, and the client-only print device identifier set comprises each print device identifier existing in the first print device identifier set but not existing in the second print device identifier set.

[0014] The target print device set is determined based on the target print device identifier set.

[0015] In a possible design, in another implementation manner of the first aspect of the embodiment of the present application, the process further comprises the following steps.

[0016] It is judged whether each client-only print device corresponding to the client-only print device identifier set has a print function based on the client-only print device identifier set, and if there is a target client-only print device having a print function, a target client-only print device identifier is uploaded to the second print device identifier set.

[0017] In a possible design, in another implementation manner of the first aspect of the embodiment of the present application, the process further comprises the following steps.

[0018] It is judged whether each server-only print device corresponding to the server-only print device identifier set is stopped from being used based on the server-only print device identifier set, and if there is a target server-only print device stopped from being used, a target server-only print device identifier in the second print device identifier set is deleted.

[0019] In a possible design, in another implementation manner of the first aspect of the embodiment of the present application, the process of obtaining the print volume data of the target print device based on the pre-configured OID mapping table corresponding to the target print device and the SNMP comprises the following steps.

[0020] Based on the SNMP protocol and the OID corresponding to each print volume data identifier in the OID mapping table, a corresponding data request instruction is sent to the target printing device, and print volume data of the target printing device is obtained based on the data request instruction.

[0021] In a possible design, in another implementation manner of the first aspect of the embodiment of the present application, the process of generating a printing device data report based on each print volume data corresponding to the target printing device set comprises:

[0022] Each print volume data corresponding to the target printing device set is sent to a server, and a printing device data report containing a time period is generated based on the server.

[0023] In a possible design, in another implementation manner of the first aspect of the embodiment of the present application, the print volume data comprises any one or more of black-and-white cumulative print number, color cumulative print number, high-coverage cumulative print number, medium-coverage cumulative print number, and low-coverage cumulative print number.

[0024] The second aspect provides a printing device data report generation apparatus, comprising:

[0025] A mapping table generation unit is configured to scan each device in a local area network based on an address resolution protocol (ARP) protocol, and generate an IP-MAC mapping table containing a mapping relationship between an IP address and a MAC address of each device in the local area network.

[0026] A candidate printing device set determination unit is configured to perform a screening operation on devices in the local area network based on an IP address of each device in the IP-MAC mapping table, and obtain a candidate printing device set, wherein the candidate printing device set comprises all printing devices in the local area network.

[0027] A target printing device set determination unit is configured to determine a target printing device set through a simple network management protocol (SNMP) protocol and the candidate printing device set, wherein the target printing device set comprises target printing devices of different types.

[0028] A print volume data acquisition unit is configured to acquire print volume data of the target printing device based on a preconfigured OID mapping table corresponding to the target printing device and the SNMP protocol, wherein the OID mapping table comprises a mapping relationship between at least one print volume data identifier and an object identifier (OID) in the target printing device, and the number of print volume data identifiers is the same as the number of the OID.

[0029] A report generation unit is configured to generate a printing device data report based on each print volume data corresponding to the target printing device set.

[0030] Thirdly, an electronic device is provided, comprising: a memory and a processor;

[0031] The memory is used to store programs;

[0032] The processor is configured to execute the program to implement the various steps of the printing device data report generation method described in any of the first aspects of this application.

[0033] Fourthly, a readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements the steps of the printing device data report generation method described in any of the first aspects of this application.

[0034] Using the above technical solution, the printing device data report generation method proposed in this application first uses the ARP protocol to scan devices in the local area network (LAN) and generate an IP-MAC mapping table, establishing a mapping relationship between the IP addresses and MAC addresses of each device in the LAN, providing a foundation for subsequent device screening. Next, based on the IP-MAC mapping table, devices in the LAN are screened to obtain a candidate set of all printing devices in the LAN, ensuring the comprehensiveness and accuracy of the screening process. Subsequently, the target set of printing devices, including different types of printing devices, is determined through the SNMP protocol and the candidate set of printing devices, solving the compatibility problem of different brands of printing devices and achieving unified management of multiple types of devices. Then, the print volume data of the target printing devices is obtained through a pre-configured OID mapping table and the SNMP protocol. The print volume data identifiers in the OID mapping table correspond one-to-one with the OIDs, ensuring the accuracy and efficiency of data collection. Finally, a printing device data report is generated based on the collected print volume data of each target printing device, providing enterprises or organizations with a comprehensive and accurate overview of the printing device's operating status, which helps optimize printing resource management. Attached Figure Description

[0035] Various other advantages and benefits will become apparent to those skilled in the art upon reading the following detailed description of preferred embodiments. The accompanying drawings are for illustrative purposes only and are not intended to limit the scope of this application. Furthermore, the same reference numerals denote the same parts throughout the drawings. In the drawings:

[0036] Figure 1 A flowchart illustrating a method for generating a printing device data report provided in this application;

[0037] Figure 2 This application provides a schematic diagram illustrating the interaction between a printing device data report generation and a target printing device in an embodiment of the present application.

[0038] Figure 3This application provides an embodiment of an interaction diagram between a server, a printing device data report generation system, and a target printing device.

[0039] Figure 4 A schematic diagram of a data report generation device for a printing device provided in this application embodiment;

[0040] Figure 5 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0041] Before introducing the solution of this application, some of the technical terms involved in the embodiments of this application will be explained and described first:

[0042] ARP (Address Resolution Protocol) is a data link layer protocol located in the TCP / IP protocol stack. Its main function is to resolve network layer IP addresses into data link layer physical MAC addresses, so that they can be directly used in subsequent communications, reducing the number of ARP queries and improving communication efficiency.

[0043] SNMP Protocol: Simple Network Management Protocol is an application protocol used for network device management. It allows network administrators to remotely monitor and manage devices in the network, such as routers, switches, and servers.

[0044] OID: Object Identifier, is a numerical sequence used to uniquely identify various managed objects in a network device, defined by the International Organization for Standardization (ISO). It adopts a hierarchical structure, similar to a directory path in a file system, with each node representing a managed object category or object. In the SNMP protocol, OIDs are used by management stations to query or set specific parameters on network devices, enabling device status monitoring and configuration management.

[0045] The embodiments of this application are described below with reference to the accompanying drawings. The terminology used in the implementation section of this application is for explaining specific embodiments only and is not intended to limit the scope of this application.

[0046] The terms "first," "second," etc., used in this application's specification are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such terms are interchangeable where appropriate; this is merely a way of distinguishing objects with the same attributes in the embodiments of this application. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion, so that a process, method, system, product, or apparatus that comprises a series of units is not necessarily limited to those units, but may include other units not explicitly listed or inherent to those processes, methods, products, or apparatuses.

[0047] This application can be applied to the field of printing equipment monitoring technology. The following section uses a corporate office environment as an example to introduce the application scenarios of this application. In a corporate office environment, printing equipment is an important piece of equipment for daily office work, providing services such as printing, copying, and scanning. However, existing printing equipment monitoring technologies have many limitations: they only collect basic status data (such as sleep mode and consumables), and cannot obtain print volume data such as coverage and paper type; they are difficult to adapt to the customized collection needs of private OIDs; statistics are limited to local use and lack multi-level aggregation capabilities in the cloud; and they cannot filter target printing equipment.

[0048] To overcome these problems and achieve the collection and analysis of print volume data from multiple types and brands of printing equipment, the printing equipment data report generation method of this application not only solves the compatibility problem of multiple types and brands of printing equipment and achieves adaptation to different brands of printing equipment, improving the accuracy and comprehensiveness of data collection, but also enhances the system's flexibility and data analysis capabilities, providing stronger support for printer management.

[0049] Next, see Figure 1 , Figure 1 The flowchart illustrates a method for generating a printing device data report provided in this application. This method can be implemented using a printing device data report generation system deployed on a terminal, and specifically includes the following steps:

[0050] Step S100: Scan each device in the local area network based on the Address Resolution Protocol (ARP) and generate an IP-MAC mapping table.

[0051] Specifically, the printing device data report generation method of this application first invokes the ARP protocol to scan all devices within the local area network (LAN). Optionally, all devices within the LAN may include printing devices, routers, switches, and tablets. The ARP protocol sends ARP request packets to the LAN. When other devices receive the ARP request packets, they parse them and return their own IP address and MAC address information to the requesting device. This allows the device to obtain the mapping between the IP addresses and MAC addresses of each device within the LAN, forming an IP-MAC mapping table containing the mapping relationship between the IP addresses and MAC addresses of all devices within the LAN. The IP-MAC mapping table provides the foundation for subsequent device identification and data collection.

[0052] Step S110: Based on the IP addresses of each device in the IP-MAC mapping table, perform a filtering operation on the devices in the local area network to obtain a set of candidate printing devices.

[0053] Specifically, after constructing an IP-MAC mapping table containing the IP address and MAC address mapping relationships of each device within the local area network (LAN), the devices in the LAN are further filtered based on the IP addresses of each device in the IP-MAC mapping table. One optional approach is to base the filtering process on the specific attributes and behavioral characteristics of the printing devices within the LAN. For example, they might identify themselves as printing devices by responding to specific network requests. This can be achieved by sending configured probe packets to each IP address in the IP-MAC mapping table and analyzing the returned response information to identify and filter the printing devices in the LAN. The set of identified printing devices constitutes the candidate printing device set for all printing devices in the LAN, laying the foundation for subsequent data collection and analysis.

[0054] Step S120: Determine the target printing device set using the Simple Network Management Protocol (SNMP) and the candidate printing device set.

[0055] Specifically, during the device identification process based on the SNMP protocol, a communication connection is established with each candidate printing device in the candidate printing device set. This allows for the acquisition of information about the candidate printing devices, enabling the determination of which devices are the target printing devices that the system needs to monitor. The SNMP protocol allows for the collection of standardized management information from devices on the network, ensuring that printing devices of different brands and models can be managed and monitored uniformly. Through this process, all printing devices on the local area network can be identified and grouped into the target printing device set, providing a prerequisite for subsequent multi-dimensional print volume data collection and analysis. The target printing device set includes various types of target printing devices, including but not limited to monochrome printers, color printers, and multifunction printers, and can also include target printing devices from multiple brands, thus ensuring the comprehensiveness and accuracy of monitoring.

[0056] Step S130: Based on the pre-configured OID mapping table corresponding to the target printing device and the SNMP protocol, obtain the print volume data of the target printing device.

[0057] Specifically, after acquiring the target set of printing devices, print volume data can be collected from these devices based on a pre-configured OID mapping table and SNMP protocol. The OID mapping table includes a mapping relationship between at least one print volume data identifier and an object identifier (OID) for each target printing device. The number of print volume data identifiers and OIDs is the same and they correspond one-to-one, enabling the identification and collection of the required print volume data. This method allows for the efficient and accurate acquisition of multi-dimensional print volume data from printing devices of different brands and models, providing a solid data foundation for subsequent data analysis and management.

[0058] Step S140: Generate a printing device data report based on the print volume data corresponding to each of the target printing device sets.

[0059] Specifically, after determining the target set of printing devices and collecting print volume data, a printing device data report can be generated based on the print volume data corresponding to each target set of printing devices. Alternatively, the collected print volume data can be classified and organized according to preset data processing rules, categorizing print volume data from different dimensions to clearly show the usage of printing devices over different time periods.

[0060] Alternatively, print volume data may include any one or more of the following: cumulative black and white print volume, cumulative color print volume, cumulative high coverage print volume, cumulative medium coverage print volume, and cumulative low coverage print volume. Specifically, cumulative black and white print volume refers to the total number of black pages printed by the printing device within a predetermined time period; cumulative color print volume refers to the total number of color pages printed by the printing device within the predetermined time period; cumulative high coverage print volume refers to the total number of high coverage pages printed by the printing device within the predetermined time period; cumulative medium coverage print volume refers to the total number of medium coverage pages printed by the printing device within the predetermined time period; and cumulative low coverage print volume refers to the total number of low coverage pages printed by the printing device within the predetermined time period. The "coverage" of the printing device refers to the percentage of the paper area actually covered by the printed content (such as text, graphics, and images) relative to the total usable printable area of ​​the sheet. Coverage can be used to measure the consumption rate of consumables (ink cartridges, toner cartridges, ink, etc.); generally speaking, the higher the coverage, the more toner or ink is consumed. Alternatively, coverage is used as a statistical dimension for color printing, while it is not considered or differentiated in black and white printing. Another possible approach is to define high coverage pages as those with a toner density greater than a first configured value, typically representing pages with high toner coverage; medium coverage pages as those with a toner density no greater than the first value and no less than a second configured value, corresponding to pages with moderate toner coverage; and low coverage pages as those with a toner density less than the second value, typically representing pages with low toner coverage.

[0061] It should be noted that when acquiring print volume data, this invention only needs to directly obtain three specific values: cumulative print volume for high coverage, cumulative print volume for medium coverage, and cumulative print volume for low coverage. The distinction between these three cumulative print volumes is handled independently by each brand of printing equipment. Different brands of printing equipment define which printed pages belong to high coverage, medium coverage, and low coverage based on their own set first and second values. This distinction process is autonomous, and this invention only needs to directly obtain the cumulative print volume for high coverage, medium coverage, and low coverage, without needing to concern itself with how to distinguish between the three based on the first and second values. By obtaining the cumulative print volume for high coverage, medium coverage, and low coverage, printer toner usage can be monitored and managed more accurately, print jobs can be optimized, operating costs can be reduced, and it also helps to predict and schedule consumable replacement and maintenance times.

[0062] An alternative approach is to perform preliminary statistical analysis on print volume data to calculate the total, average, and percentage of various print volume data, reflecting the efficiency of printing equipment usage and potential resource waste.

[0063] Alternatively, the generated printing equipment data report can include information and charts, such as trend charts of various print volumes, equipment usage efficiency comparison tables, and resource consumption statistics, providing printing equipment managers with comprehensive and in-depth data insights to help them make more scientific and reasonable equipment management decisions and achieve optimized allocation of printing resources and effective cost control.

[0064] The printing device data report generation method in this embodiment first uses the ARP protocol to scan devices in the local area network (LAN) and generate an IP-MAC mapping table, establishing a mapping relationship between the IP addresses and MAC addresses of each device in the LAN, providing a foundation for subsequent device screening. Next, based on the IP-MAC mapping table, devices in the LAN are screened to obtain a candidate set of all printing devices in the LAN, ensuring the comprehensiveness and accuracy of the screening process. Subsequently, the SNMP protocol and the candidate set of printing devices are used to determine the target set of printing devices, including different types of printing devices, solving the compatibility problem of different brands of printing devices and achieving unified management of multiple types of devices. Then, the print volume data of the target printing devices is obtained through a pre-configured OID mapping table and the SNMP protocol. The print volume data identifiers in the OID mapping table correspond one-to-one with the OIDs, ensuring the accuracy and efficiency of data collection. Finally, a printing device data report is generated based on the collected print volume data of each target printing device, providing enterprises or organizations with a comprehensive and accurate overview of the printing device's operating status, which helps optimize printing resource management.

[0065] Furthermore, in some embodiments of this application, the process of determining the target printing device set through the SNMP protocol and the candidate printing device set can be further described, and this part will be described in detail below.

[0066] One alternative approach is to first invoke the SNMP protocol, using the IP address of the candidate printing device as an index, to send a query request to each candidate printing device. The query request user obtains information that can uniquely identify the printing device, which constitutes the first set of printing device identifiers corresponding to the set of candidate printing devices. The printer number (SN) of the printing device can be used as the printing device identifier because the SN has global uniqueness and can accurately identify each printing device.

[0067] Next, the second set of print device identifiers is extracted from the configuration data pre-stored on the server. This second set of print device identifiers can be a theoretical set representing the print devices currently being monitored, manually or automatically entered by the administrator based on actual monitoring needs during deployment or previous operation. It also uses the printer serial number (SN) as the print device identifier. Alternatively, the server can be a cloud server.

[0068] After obtaining the first set of printing device identifiers and the second set of printing device identifiers, a comparison operation can be performed. In one optional method, the comparison operation can be based on an intelligent comparison algorithm.

[0069] The comparison results are categorized into three types: First, the target printing device identifier set, which includes common printing device identifiers that exist in both the first and second printing device identifier sets, i.e., the printing devices that should actually be monitored; second, the server-specific printing device identifier set, which includes each printing device identifier that exists in the second printing device identifier set but not in the first printing device identifier set, possibly indicating that the device is offline or that the network configuration has changed; and third, the client-specific printing device identifier set, which includes each printing device identifier that exists in the first printing device identifier set but not in the second printing device identifier set, possibly indicating newly deployed or accidentally overlooked printing devices.

[0070] Finally, the target printing device is determined based on the set of target printing device identifiers in the comparison results.

[0071] This embodiment obtains a first set of print device identifiers for candidate printing devices via the SNMP protocol and compares it with a second set of print device identifiers pre-stored on the server. This identifies the actual set of target print device identifiers to be monitored, and the target printing device is determined based on this set. This not only ensures monitoring accuracy but also promptly identifies server-specific and client-specific sets of print device identifiers, effectively avoiding monitoring omissions or redundancy. In multi-device, complex network environments, this method effectively improves the efficiency and accuracy of print device management, providing a solid foundation for subsequent print volume data collection and analysis, and contributing to the management of print devices and the rational utilization of resources.

[0072] Furthermore, one possible implementation involves initiating print function verification requests to each client-specific print device one by one, based on a set of client-unique print device identifiers. By sending these verification requests, it can be checked whether the print device can correctly respond and execute basic print jobs. If a target client-specific print device with normal printing functionality is detected, an update process can be triggered to upload its identifier to a second set of print device identifiers on the server. This expands the monitoring scope, ensuring no omissions and achieving dynamic expansion of the monitoring range, thus ensuring the real-time performance and completeness of the monitoring system.

[0073] Furthermore, in some embodiments of this application, a status monitoring program can be used to determine whether each server-specific printing device is still in effective use based on preset rules, targeting a server-unique set of printing device identifiers. Once it is confirmed that a device has stopped using, the corresponding identifier can be removed from the server's second set of printing device identifiers, maintaining the timeliness and accuracy of the monitoring configuration and optimizing the server configuration.

[0074] Furthermore, in some embodiments of this application, when collecting print volume data from the target printing device, a data request command can be sent to the target printing device based on the correspondence between each print volume data identifier and its OID in the OID mapping table. The data request command, formatted according to the SNMP protocol, can point to various types of print volume data required by the target device, such as cumulative black and white print count, cumulative color print count, and print volume under different coverage rates. Upon receiving these request commands, the target printing device will quickly retrieve the corresponding print volume data according to the data request command and feed it back via the SNMP protocol. This acquisition process is efficient and accurate, ensuring that the collected print volume data truly reflects the actual usage of the target printing device, providing a reliable basis for subsequent data analysis and management decisions.

[0075] Furthermore, in some embodiments of this application, after the print volume data of the target printing device set is collected, data integration and report generation can be performed based on the server (cloud). This part will be described in detail below.

[0076] One optional approach is to send various types of print volume data, including but not limited to cumulative black and white print volume, cumulative color print volume, high coverage cumulative print volume, medium coverage cumulative print volume, and low coverage cumulative print volume, to the server via a network transmission protocol. On the server, the received print volume data undergoes a series of preprocessing steps, including data cleaning, format standardization, and data integrity verification, to ensure data accuracy and consistency. Subsequently, based on this processed print volume data and a user-preset time period (such as daily, weekly, monthly, yearly, or a custom time period), a printing equipment data report is generated. This report not only presents the statistical results of various print volume data but also visually demonstrates the printing equipment's usage patterns, resource consumption, and potential optimization points through charts, trend analysis, and other intuitive methods.

[0077] Alternatively, the server-generated printing equipment data reports can be customized to meet user needs. Through in-depth data analysis, these reports can reveal fluctuations in print volume over different time periods, helping users identify peak usage times and thus schedule printing tasks more efficiently. Furthermore, by incorporating historical data, the reports can predict future consumable needs, providing a scientific basis for equipment maintenance and resource procurement, thereby enabling refined management of printing resources and effective cost control.

[0078] This embodiment combines the printing equipment data report generated by the user's preset time period, which not only provides detailed print volume statistics, but also clearly shows the equipment usage patterns, resource consumption and optimization points with intuitive charts and trend analysis. This helps users grasp the operating status of the printing equipment, provides scientific support for equipment maintenance and resource procurement, realizes refined management and cost control of printing resources, and significantly improves the management efficiency and resource utilization of printing equipment.

[0079] Further, see Figure 2 , Figure 2 This is a schematic diagram illustrating the interaction between a printing device data report generation and a target printing device, provided in an embodiment of this application. Figure 2This demonstrates the relationship between the printing equipment data report generation system and three target printing devices (the first target printing device, the second target printing device, and the third target printing device). The system connects to these three devices and collects print volume data from them, including cumulative print runs for both black and white and color printing, and cumulative print runs at different coverage rates. The system then processes this data and generates printing equipment data reports according to a user-preset time period.

[0080] Further, see Figure 3 , Figure 3 This application provides a schematic diagram illustrating the interaction between a server, a printing device data report generation system, and a target printing device, as shown in the embodiments of this application. Figure 3 This diagram illustrates the overall architecture and data flow of a printing equipment data report generation system. It includes a server, the system, and three target printing devices (target device 1, target device 2, and target device 3). The data flow begins at the server, which sends instructions or preset configuration information, such as time periods and data format requirements, to the system. Based on the preset rules and configuration, the system sends data request instructions to the three target printing devices via the SNMP protocol. Using the SNMP protocol and a preset object identifier (OID) mapping table, it collects print volume data, which is then transmitted back to the system via a network protocol. The system uploads the print volume data to the server, which then generates a printing equipment data report based on this data.

[0081] The above describes a method for generating a printing device data report according to an embodiment of this application. The following describes the apparatus for performing the above-described method for generating a printing device data report.

[0082] Please see Figure 4 , Figure 4 This is a schematic diagram of a data report generation device for a printing device provided in an embodiment of this application. Figure 4 As shown, the printing equipment data report generation device includes:

[0083] The mapping table generation unit 11 is used to scan each device in the local area network based on the Address Resolution Protocol (ARP) and generate an IP-MAC mapping table, which contains the mapping relationship between the IP address and MAC address of each device in the local area network.

[0084] The candidate printing device set determination unit 12 is used to perform a filtering operation on the devices in the local area network based on the IP address of each device in the IP-MAC mapping table to obtain a candidate printing device set, wherein the candidate printing device set is all printing devices in the local area network;

[0085] The target printing device set determination unit 13 is used to determine the target printing device set through the Simple Network Management Protocol (SNMP) and the candidate printing device set, wherein the target printing device set includes different types of target printing devices;

[0086] The print volume data acquisition unit 14 is used to acquire print volume data of the target printing device based on the pre-configured OID mapping table corresponding to the target printing device and the SNMP protocol. The OID mapping table includes a mapping relationship between at least one print volume data identifier and an object identifier (OID) in the target printing device, and the number of print volume data identifiers is the same as the number of OIDs.

[0087] The report generation unit 15 is used to generate a printing device data report based on the print volume data corresponding to each of the target printing device sets.

[0088] In one possible implementation, the process by which the target printing device set determination unit 13 determines the target printing device set through the Simple Network Management Protocol (SNMP) and the candidate printing device set includes:

[0089] The first set of printer identifiers corresponding to each candidate printer is obtained by using the IP address of each candidate printer via the SNMP protocol.

[0090] Obtain the second set of printing device identifiers pre-configured on the server;

[0091] The first set of printing device identifiers is compared with the second set of printing device identifiers to obtain a comparison result. The comparison result includes a target set of printing device identifiers, a server-specific set of printing device identifiers, and a client-specific set of printing device identifiers. The target set of printing device identifiers includes all printing device identifiers common to the first set of printing device identifiers and the second set of printing device identifiers. The server-specific set of printing device identifiers includes all printing device identifiers that exist in the second set of printing device identifiers but not in the first set of printing device identifiers. The client-specific set of printing device identifiers includes all printing device identifiers that exist in the first set of printing device identifiers but not in the second set of printing device identifiers.

[0092] The target printing device set is determined based on the target printing device identifier set.

[0093] In one possible implementation, the printing device data report generation apparatus of this embodiment further includes:

[0094] The identifier upload unit is used to determine whether each client-specific printing device has printing function based on the client-specific printing device identifier set. If there is a target client-specific printing device with printing function, the identifier of the target client-specific printing device is uploaded to the second printing device identifier set.

[0095] In one possible implementation, the printing device data report generation apparatus of this embodiment further includes:

[0096] The identifier deletion unit is used to determine whether each server-unique printing device is no longer in use based on the server-unique printing device identifier set. If there is a target server-unique printing device that is no longer in use, the target server-unique printing device identifier is deleted from the second printing device identifier set.

[0097] In one possible implementation, the process by which the print volume data acquisition unit 14 acquires print volume data of the target printing device based on a pre-configured OID mapping table corresponding to the target printing device and the SNMP protocol includes:

[0098] Based on the SNMP protocol and the OID corresponding to each print volume data identifier in the OID mapping table, a corresponding data request instruction is sent to the target printing device, and the print volume data of the target printing device is obtained based on the data request instruction.

[0099] In one possible implementation, the process by which the report generation unit 15 generates a printing device data report based on the print volume data corresponding to each of the target printing device sets includes:

[0100] The print volume data corresponding to each of the target printing devices is sent to the server, and a printing device data report containing time periods is generated based on the server.

[0101] In one possible implementation, the print volume data includes any one or more of the following: cumulative black and white print volume, cumulative color print volume, cumulative high coverage print volume, cumulative medium coverage print volume, and cumulative low coverage print volume.

[0102] This application also provides an electronic device in its embodiments. (See reference...) Figure 5 The diagram illustrates a structural schematic suitable for implementing the electronic device in the embodiments of this application. The electronic device in the embodiments of this application may include, but is not limited to, fixed terminals such as mobile phones, laptops, PDAs (personal digital assistants), PADs (tablet computers), desktop computers, etc. Figure 5The electronic device shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments of this application.

[0103] like Figure 5 As shown, the electronic device may include a processing unit (e.g., a central processing unit, a graphics processing unit, etc.) 601, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 602 or a program loaded from a storage device 608 into a random access memory (RAM) 603. When the electronic device is powered on, the RAM 603 also stores various programs and data required for the operation of the electronic device. The processing unit 601, ROM 602, and RAM 603 are interconnected via a bus 604. An input / output (I / O) interface 605 is also connected to the bus 604.

[0104] Typically, the following devices can be connected to I / O interface 605: input devices 606 including, for example, touchscreens, touchpads, keyboards, mice, cameras, microphones, accelerometers, gyroscopes, etc.; output devices 607 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 608 including, for example, memory cards, hard drives, etc.; and communication devices 609. Communication device 609 allows electronic devices to communicate wirelessly or wiredly with other devices to exchange data. Although Figure 5 Electronic devices with various devices are shown, but it should be understood that it is not required to implement or have all of the devices shown. More or fewer devices may be implemented or have alternatively.

[0105] It should also be noted that the device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. In addition, in the device embodiment drawings provided in this application, the connection relationship between modules indicates that they have a communication connection, which can be implemented as one or more communication buses or signal lines.

[0106] This application also provides a computer-readable storage medium that carries one or more computer programs. When the one or more computer programs are executed by an electronic device, the electronic device can implement any of the printing device data report generation methods provided in this application.

[0107] Through the above description of the embodiments, those skilled in the art can clearly understand that this application can be implemented by means of software plus necessary general-purpose hardware, or it can be implemented by special-purpose hardware including application-specific integrated circuits, special-purpose CPUs, special-purpose memory, special-purpose components, etc. Generally, any function performed by a computer program can be easily implemented by corresponding hardware, and the specific hardware structure used to implement the same function can also be diverse, such as analog circuits, digital circuits, or special-purpose circuits. However, for this application, software program implementation is more often the preferred implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a readable storage medium, such as a computer floppy disk, USB flash drive, mobile hard disk, ROM, RAM, magnetic disk, or optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, training equipment, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0108] In the above embodiments, the implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, in the form of a computer program product.

[0109] In the embodiments of this application, the terms "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., refer to specific features, structures, materials, or characteristics described in connection with that embodiment or example, which are included in at least one embodiment or example of this application. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples. Furthermore, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of different embodiments or examples.

[0110] Although embodiments of this application have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting this application. Those skilled in the art can make changes, modifications, substitutions and variations to the above embodiments within the scope of this application.

[0111] The various embodiments in this specification are described in a progressive manner. Each embodiment focuses on the differences from other embodiments. The various embodiments can be combined as needed, and the same or similar parts can be referred to each other.

Claims

1. A method for generating data reports for a printing device, characterized in that, include: The local area network (LAN) is scanned based on the Address Resolution Protocol (ARP) and an IP-MAC mapping table is generated. The IP-MAC mapping table contains the mapping relationship between the IP address and MAC address of each device in the LAN. Based on the IP addresses of each device in the IP-MAC mapping table, the devices in the local area network are filtered to obtain a candidate printing device set, which consists of all printing devices in the local area network. The target printing device set is determined using the Simple Network Management Protocol (SNMP) and the candidate printing device set, wherein the target printing device set includes different types of target printing devices. Based on the pre-configured OID mapping table corresponding to the target printing device and the SNMP protocol, the print volume data of the target printing device is obtained. The OID mapping table includes the mapping relationship between at least one print volume data identifier and object identifier OID in the target printing device, and the number of print volume data identifiers is the same as the number of OIDs. A printing device data report is generated based on the print volume data corresponding to each of the target printing device sets.

2. The method according to claim 1, characterized in that, The process of determining the target printing device set using the Simple Network Management Protocol (SNMP) and the candidate printing device set includes: The first set of printer identifiers corresponding to each candidate printer is obtained by using the IP address of each candidate printer via the SNMP protocol. Obtain the second set of printing device identifiers pre-configured on the server; The first set of printing device identifiers is compared with the second set of printing device identifiers to obtain a comparison result. The comparison result includes a target set of printing device identifiers, a server-specific set of printing device identifiers, and a client-specific set of printing device identifiers. The target set of printing device identifiers includes all printing device identifiers common to the first set of printing device identifiers and the second set of printing device identifiers. The server-specific set of printing device identifiers includes all printing device identifiers that exist in the second set of printing device identifiers but not in the first set of printing device identifiers. The client-specific set of printing device identifiers includes all printing device identifiers that exist in the first set of printing device identifiers but not in the second set of printing device identifiers. The target printing device set is determined based on the target printing device identifier set.

3. The method according to claim 2, characterized in that, Also includes: Based on the client-specific printing device identifier set, it is determined whether each client-specific printing device has printing function. If there is a target client-specific printing device with printing function, the target client-specific printing device identifier is uploaded to the second printing device identifier set.

4. The method according to claim 2, characterized in that, Also includes: Based on the set of server-specific printing device identifiers, it is determined whether each server-specific printing device is no longer in use. If there is a target server-specific printing device that is no longer in use, the target server-specific printing device identifier is deleted from the second set of printing device identifiers.

5. The method according to claim 1, characterized in that, The process of obtaining print volume data of the target printing device based on the pre-configured OID mapping table corresponding to the target printing device and the SNMP protocol includes: Based on the SNMP protocol and the OID corresponding to each print volume data identifier in the OID mapping table, a corresponding data request instruction is sent to the target printing device, and the print volume data of the target printing device is obtained based on the data request instruction.

6. The method according to claim 1, characterized in that, The process of generating a printing device data report based on the print volume data corresponding to each of the target printing device sets includes: The print volume data corresponding to each of the target printing devices is sent to the server, and a printing device data report containing time periods is generated based on the server.

7. The method according to any one of claims 1-6, characterized in that, The print volume data includes any one or more of the following: cumulative black and white print volume, cumulative color print volume, cumulative high coverage print volume, cumulative medium coverage print volume, and cumulative low coverage print volume.

8. A data report generation device for a printing device, characterized in that, include: The mapping table generation unit is used to scan each device in the local area network based on the Address Resolution Protocol (ARP) and generate an IP-MAC mapping table, which contains the mapping relationship between the IP address and MAC address of each device in the local area network. The candidate printing device set determination unit is used to perform a filtering operation on devices in the local area network based on the IP address of each device in the IP-MAC mapping table to obtain a candidate printing device set, wherein the candidate printing device set is all printing devices in the local area network; A target printing device set determination unit is used to determine a target printing device set through a Simple Network Management Protocol (SNMP) and the candidate printing device set, wherein the target printing device set includes different types of target printing devices; The print volume data acquisition unit is used to acquire print volume data of the target printing device based on a pre-configured OID mapping table corresponding to the target printing device and the SNMP protocol. The OID mapping table includes a mapping relationship between at least one print volume data identifier and an object identifier (OID) in the target printing device, and the number of print volume data identifiers is the same as the number of OIDs. The report generation unit is used to generate a printing device data report based on the print volume data corresponding to each of the target printing device sets.

9. An electronic device, characterized in that, include: Memory and processor; The memory is used to store programs; The processor is used to execute the program to implement each step of the printing device data report generation method as described in any one of claims 1 to 7.

10. A readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements each step of the printing device data report generation method as described in any one of claims 1 to 7.

Images