Printer management method and system
Through dynamic configuration printer status fields and finding object identifiers OID, the problem of high cost and insufficient scalability of traditional printer management solutions has been solved, and efficient and flexible printer data collection and management is achieved.
Patent Information
- Application Number
- CN202411153256.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-21
- Publication Date
- 2025-01-24
Smart Images

Figure CN119356630A_ABST
Abstract
Description
Technical Field
[0001] The disclosed embodiments relate to the technical field of enterprise equipment management, and more particularly to a printer management method and system. Background Art
[0002] Currently, in the enterprise management environment, there are many types and models of printers involved, and the management requirements of various types of printers are different. For example, different printers have different data collection requirements. Traditional printer management solutions usually require system code modification and redeployment updates for each new printer type or data collection requirement, which increases the workload of developers, resulting in high system maintenance costs, and insufficient system scalability and flexibility. For example, it is difficult to adapt to the data collection and management requirements of more types of printers, which reduces the overall printer management efficiency and makes it difficult to achieve efficient and accurate management of printer resources. Summary of the invention
[0003] In order to solve the above technical problems or at least partially solve the above technical problems, an embodiment of the present disclosure provides a printer management method and system.
[0004] In a first aspect, an embodiment of the present disclosure provides a printer management method, which is applied to a printer management device, wherein the printer management device is communicatively linked to a plurality of printers, and the method includes:
[0005] Acquire data collection requirement information of a target printer, and set status field information in a printer status field configuration table based on the data collection requirement information; wherein the target printer is any one of the multiple printers, and the data collection requirement information is used to indicate the collection of at least one type of status information of the target printer; the status field information includes at least one field type and field identifier corresponding to the at least one type of status information;
[0006] Determine the printer brand and model of the target printer, and based on the printer brand and model and at least one field identifier in the status field information, search and obtain at least one corresponding object identifier OID from the first data table;
[0007] A data acquisition request is generated based on the at least one object identifier OID, and the data acquisition request is sent to the target printer; and at least one parameter value corresponding to the at least one object identifier OID returned by the target printer is received.
[0008] In one embodiment, the printer management device and the multiple printers are linked based on a preconfigured Simple Network Management Protocol (SNMP) communication link; the data acquisition request is a UDP request, the UDP request carries at least the at least one object identifier (OID), and the UDP request is sent to the IP address and target port of the target printer.
[0009] In one embodiment, the determining the printer brand and model of the target printer includes: acquiring the printer brand and model of the target printer from a second data table, wherein the second data table is pre-configured with the brand and model of each of the plurality of printers;
[0010] or,
[0011] The first data table is pre-configured with a plurality of object identifiers OIDs corresponding to different printer brands and models, and field identifiers corresponding to the plurality of object identifiers OIDs corresponding to each of the printer brands and models.
[0012] In one embodiment, the method further comprises:
[0013] When the status field information is set in the printer status field configuration table, at least one field type and field identifier in the status field information is synchronously inserted into the third data table;
[0014] Execute a real-time acquisition task, send the data acquisition request to the target printer in real time; receive at least one parameter value corresponding to the at least one object identifier OID returned by the target printer in real time;
[0015] At least one parameter value corresponding to the at least one object identifier OID returned in real time by the target printer is written into the third data table, and the third data table is used to store the current real-time status information of the target printer.
[0016] In one embodiment, the method further comprises:
[0017] When the status field information is set in the printer status field configuration table, at least one field type and field identifier in the status field information is synchronously inserted into the fourth data table;
[0018] Execute the pipeline collection task, send the data acquisition request to the target printer at a preset time interval, receive at least one parameter value corresponding to the at least one object identifier OID returned by the target printer and write it into the fourth data table, where the fourth data table is used to store the historical status information of the target printer.
[0019] In one embodiment, the method further comprises:
[0020] Obtaining a printer ledger information table, wherein the printer ledger information table includes ledger information of the plurality of printers, wherein the ledger information includes at least one or more of printer brand model, printer serial number, purchase date, warranty period, and affiliated institution information;
[0021] Obtaining the record information of the target printer from the printer record information table;
[0022] Based on the ledger information of the target printer and the first data table, historical status information of the target printer is obtained from the fourth data table.
[0023] In one embodiment, the method further comprises:
[0024] Generate statistical report information based on the data in the fourth data table.
[0025] In a second aspect, an embodiment of the present disclosure provides a printer management system, which is applied to a printer management device, wherein the printer management device is communicatively linked with a plurality of printers, and the system includes:
[0026] An information configuration module, used to obtain data collection requirement information of a target printer, and to set status field information in a printer status field configuration table based on the data collection requirement information; wherein the target printer is any one of the plurality of printers, and the data collection requirement information is used to indicate the collection of at least one type of status information of the target printer; and the status field information includes at least one field type and field identifier corresponding to the at least one type of status information;
[0027] An information search module, used to determine the printer brand and model of the target printer, and based on the printer brand and model and at least one field identifier in the status field information, search and obtain the corresponding at least one object identifier OID from the first data table;
[0028] The data acquisition module is used to generate a data acquisition request based on the at least one object identifier OID, send the data acquisition request to the target printer, and receive at least one parameter value corresponding to the at least one object identifier OID returned by the target printer.
[0029] In a third aspect, an embodiment of the present disclosure provides a computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the printer management method described in any of the above embodiments is implemented.
[0030] In a fourth aspect, an embodiment of the present disclosure provides an electronic device, including:
[0031] Processor; and
[0032] Memory for storing computer programs;
[0033] The processor is configured to execute the printer management method described in any one of the above embodiments by executing the computer program.
[0034] Compared with the prior art, the technical solution provided by the embodiments of the present disclosure has the following advantages:
[0035] The printer management method and system provided by the embodiments of the present disclosure are applied to a printer management device, which is linked to multiple printers in communication, obtains data collection requirement information of a target printer, and sets status field information in a printer status field configuration table based on the data collection requirement information; the target printer is any one of the multiple printers, and the data collection requirement information is used to indicate the collection of at least one type of status information of the target printer; the status field information includes at least one field type and field identifier corresponding to the at least one type of status information; the printer brand model of the target printer is determined, and based on the printer brand model and at least one field identifier in the status field information, the corresponding at least one object identifier OID is searched and obtained from a first data table; a data acquisition request is generated based on the at least one object identifier OID, and the data acquisition request is sent to the target printer; and at least one parameter value corresponding to the at least one object identifier OID returned by the target printer is received. In this way, the solution in this embodiment can be adaptive to different data collection needs of different printers by simply configuring the status fields in the printer status field configuration table. In combination with the field identifiers corresponding to different printer brands and models and the corresponding multiple OIDs pre-configured in the first data table, at least one OID corresponding to the target printer can be determined, and a data acquisition request is generated accordingly to obtain the corresponding parameter value of at least one type. It does not require traditional system code modifications and redeployment updates, but only requires a simple configuration file to dynamically expand the type of printer data collection, and can quickly respond to new printer types and data collection needs, thereby improving the scalability and flexibility of the system, and improving maintenance efficiency. It can adapt to the data collection and management needs of more types of printers, thereby improving the overall printer management efficiency and facilitating the efficient management of printer resources. BRIEF DESCRIPTION OF THE DRAWINGS
[0036] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the present disclosure.
[0037] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.
[0038] Figure 1 This is a flow chart of the printer management method according to an embodiment of the present disclosure;
[0039] Figure 2 A schematic diagram of the communication relationship between the printer management device and the printer according to an embodiment of the present disclosure;
[0040] Figure 3 This is a flow chart of a printer management method according to another embodiment of the present disclosure;
[0041] Figure 4 is a schematic diagram of a printer management system according to an embodiment of the present disclosure;
[0042] Figure 5 Schematic diagram of an electronic device according to an embodiment of the present disclosure. DETAILED DESCRIPTION
[0043] In order to more clearly understand the above-mentioned objectives, features and advantages of the present disclosure, the scheme of the present disclosure will be further described below. It should be noted that the embodiments of the present disclosure and the features in the embodiments can be combined with each other without conflict.
[0044] In the following description, many specific details are set forth to facilitate a full understanding of the present disclosure, but the present disclosure may also be implemented in other ways different from those described herein; it is obvious that the embodiments in the specification are only part of the embodiments of the present disclosure, rather than all of the embodiments.
[0045] It should be understood that, in the following, "at least one (item)" means one or more, and "plurality" means two or more. "And / or" is used to describe the association relationship of associated objects, indicating that three relationships may exist. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist at the same time, where A and B can be singular or plural. The character " / " generally indicates that the associated objects before and after are in an "or" relationship. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, c can be single or multiple.
[0046] Figure 1The flowchart of the printer management method shown in the embodiment of the present disclosure is applied to Figure 2 The printer management device shown is a computer, and the printer management device is linked to multiple printers, such as N printers. The method may include the following steps:
[0047] Step S101: Acquire data collection requirement information of a target printer, and set status field information in a printer status field configuration table based on the data collection requirement information. The target printer is any one of the multiple printers, and the data collection requirement information is used to indicate the collection of at least one type of status information of the target printer; the status field information includes at least one field type and field identifier corresponding to the at least one type of status information.
[0048] Exemplarily, different types of status information of a printer may include but are not limited to the total number of printed pages, A4 single-page print volume, A3 single-page print volume, power-on time, etc. For different printers, the data collection requirement information may be different. For example, printer 1 needs to collect two types of status information, namely, the total number of printed pages and the power-on time, while printer 2 needs to collect two types of status information, namely, the A4 single-page print volume and the A3 single-page print volume. Therefore, the status field information in the printer status field configuration table may be set by at least one type of status information indicated by the data collection requirement information of the target printer.
[0049] Exemplarily, the printer status field configuration table pms_rtstatefld_cfg is used to configure the status field information of at least one type of status information to be collected by the printer, such as at least one field type and field identifier, each field identifier is used to identify the type of corresponding status information, such as field identifier ID1 represents the total number of printed pages, and field identifier ID2 represents the power-on time. Among them, ID1 and ID2 can specifically be a combination of one or more numbers and / or letters, which is not limited. In some embodiments, field descriptions can also be added to explain the field identifiers. The printer status field configuration table is a dynamic configuration table, which is configured according to the data collection requirements of different printers.
[0050] As a specific example, the status field information in the printer status field configuration table corresponding to the target printer may include a field identifier, a field type, and a field description, as shown in Table 1 below, but is not limited thereto.
[0051] Table 1
[0052] Field Tags Field Type Field Description ID1 number Total number of printed pages ID2 String Boot time
[0053] Step S102: Determine the printer brand and model of the target printer, and based on the printer brand and model and at least one field identifier in the status field information, search and obtain at least one corresponding object identifier OID from the first data table.
[0054] It is understandable that different attributes of a brand model of printer correspond to different OID (Object Identifier) values. Specifically, the OID value corresponding to each attribute of the printer can be found through the standard OID information manual provided by the printer manufacturer. Alternatively, use the mibbrowser software tool to send a walk command to the printer port 161 to traverse all the OID information and current values of the printer. The OID values corresponding to different attributes of printers of different brands and models may be different. Therefore, it is necessary to determine the OID values corresponding to different attributes of the corresponding printer based on the specific brand model. These can be understood by referring to the existing technology and will not be repeated here.
[0055] The first data table is a configuration parameter table pms_devparm_cfg, which is used to pre-configure a plurality of object identifiers OIDs corresponding to different printer brands and models, and field identifiers corresponding to the plurality of object identifiers OIDs corresponding to each printer brand and model.
[0056] That is to say, the first data table is pre-configured with multiple OID values corresponding to different printer brands and models (i.e., the OID value corresponding to each attribute of the printer). For each printer brand and model, each corresponding OID value corresponds to a field identifier, and each field identifier indicates the field corresponding to the parameter value to be obtained of the attribute corresponding to the corresponding OID value, that is, it indicates the corresponding field in the stored data table of the parameter value to be obtained corresponding to each attribute of each brand and model of printer.
[0057] As a specific example, the first data table takes the OID values corresponding to the three attributes of two printer brands and models as an example, as shown in the following Table 2, where ID3 can represent the A4 single-page print volume or the A3 single-page print volume.
[0058] Table 2
[0059] Printer brand model OID Field Tags Brand Model 1 OID value 1 ID1 Brand Model 1 OID value 2 ID2 Brand Model 1 OID value 3 ID3 Brand Model 2 OID value 4 ID1 Brand Model 2 OID value 5 ID2 Brand Model 2 OID value 6 ID3
[0060] Taking Table 2 as an example, it is assumed that the printer of brand model 1 has 3 different OID values and 3 different corresponding field identifiers. Assume that the printer brand model of the target printer is brand model 1, and the field identifiers in the status field information in the printer status field configuration table previously configured according to the data collection requirement information of the target printer are ID1 and ID2, that is, the target printer only needs to collect these 2 types of status information, not 3, that is, the status information corresponding to ID3 is not included. Therefore, according to the target printer's brand model 1 and field identifiers ID1 and ID2, Table 2 can be used to determine the OID value 1 and OID value 2 corresponding to the target printer.
[0061] Step S103: Generate a data acquisition request based on the at least one object identifier OID, and send the data acquisition request to the target printer; receive at least one parameter value corresponding to the at least one object identifier OID returned by the target printer.
[0062] Exemplarily, data acquisition requests are generated based on OID value 1 and OID value 2 corresponding to the target printer, and the data acquisition requests are sent to the target printer to obtain two parameter values corresponding to OID value 1 and OID value 2, such as the total number of printed pages and the power-on time.
[0063] In this embodiment, dynamic expansion technology is used to meet the different types of data collection requirements of different printers. New data collection types can be added directly through simple configuration without modifying the core code. This can adapt to more printer types. Whether it is an existing printer type or a new type of printer that may appear in the future, it can be flexibly adapted through simple configuration. New data collection types can be added without modifying the code, thereby improving the scalability and flexibility of the system, reducing the maintenance cost of the system, and simplifying the process of system upgrades and maintenance. This solution can dynamically expand and adjust the printer data collection type without modifying the code, so that the system can quickly respond to changing management needs, adapt to the data collection and management needs of more types of printers, improve the overall printer management efficiency, and facilitate the efficient management of printer resources.
[0064] In one embodiment, the printer management device and the multiple printers are linked based on a preconfigured Simple Network Management Protocol (SNMP) communication link; the data acquisition request is a UDP request, the UDP request carries at least the at least one object identifier (OID), and the UDP request is sent to the IP address and target port of the target printer.
[0065] SNMP (Simple Network Management Protocol) is a standard protocol widely used in network device management. In this embodiment, the SNMP protocol is used for remote data collection to obtain the operating data of each networked printer of the enterprise in real time through the network. The SNMP protocol has the characteristics of universality and standardization, which makes the system compatible with printers of various brands and models, ensuring the accuracy and consistency of data collection.
[0066] Specifically, the current status information of the printer can be obtained through SNMP using the default port 161 of the UDP protocol. For example, a UDP request containing three parameters (community community string defaults to public, version number defaults to 1, object identifier oid) is sent to the IP address and target port of the target printer, such as port 161. After receiving the UDP request, the target printer will return the oid corresponding parameter value, that is, the status value of a certain attribute of the printer. For example, the oid value of the total number of printed pages of the brand model Pantum P3380DN printer is .1.3.6.1.4.1.40093.1.1.3.3, then a UDP request carrying three parameters [community=public, version=1, oid=.1.3.6.1.4.1.40093.1.1.3.3] can be sent to the target printer. The parameter value returned by the target printer is the current total number of printed pages. Different OID values correspond to different parameter values.
[0067] Based on any one of the above embodiments, in one embodiment, determining the printer brand and model of the target printer in step S102 may specifically include: obtaining the printer brand and model of the target printer from a second data table, in which the brand and model of each of the multiple printers are pre-configured.
[0068] Exemplarily, the second data table can be a standard code table pms_code_info, which is used to store standardized code data in the system, including at least printer brand and model. Specifically, the brand and model of all the current enterprise's printers can be pre-maintained in the standard code table pms_code_info. Exemplarily, the standard code table is used to store standardized code data in the system, mainly composed of a device unique identifier such as a universal unique identifier UUID, a code classification identifier codekey, a standard code value codevalue under the classification, and a standard code name codename under the classification. For example, in this embodiment, the codekey of the printer brand model is 0001, and the brand model is standardized into a code such as "LBP6300" through codevalue in the system, and the codename code name, i.e., the brand model name such as "Canon Printer LBP6300", is displayed to the user. Obtain the UUID of the target printer, and query the first data table accordingly to obtain the corresponding printer brand and model. Exemplarily, the above-mentioned first data table, second data table and printer status field configuration table can all be set in the database.
[0069] Based on any of the above embodiments, in one embodiment, reference Figure 3 As shown, the method may further include the following steps:
[0070] Step S301: when the status field information is set in the printer status field configuration table, at least one field type and field identifier in the status field information is synchronously inserted into the third data table;
[0071] Step S302: executing a real-time acquisition task, sending the data acquisition request to the target printer in real time; receiving at least one parameter value corresponding to the at least one object identifier OID returned by the target printer in real time;
[0072] Step S303: writing at least one parameter value corresponding to the at least one object identifier OID returned in real time by the target printer into the third data table, wherein the third data table is used to store the current real-time status information of the target printer.
[0073] Exemplarily, the third data table, i.e., the printer real-time status detail table pms_rtstate_dtl, can also be set in the database to store the current real-time status information of the target printer. Specifically, the printer status field configuration table pms_rtstatefld_cfg is a dynamic configuration table, which is used to record the parameter value corresponding to a certain attribute of the target printer obtained and stored in the database. The field identifier and field type, inserting a record into the printer status field configuration table is to configure the above status field information, and the synchronization field will be dynamically added to the table pms_rtstate_dtl, i.e., the printer real-time status detail table, i.e., adding at least one field type and field identifier in the above status field information, so that the collected parameter value can be stored in the corresponding field in the third data table.
[0074] In this embodiment, automatic collection tasks such as real-time collection tasks can be set. When executing real-time collection tasks, for example, the status information of the target printer is obtained once every hour, updated and synchronized to the table pms_rtstate_dtl (printer real-time status details table). In this way, real-time status information can be obtained from all printers and synchronized to the database. The management method of automated real-time data collection and adding synchronization fields not only improves efficiency, but also ensures that the collected data is stored in the database in a timely and accurate manner. Administrators can easily manage a large number of printer devices by setting automatic collection tasks, reducing the tediousness of manual operations and the possibility of errors.
[0075] The printer real-time status details table stores the current real-time status information of the printer. The status information can only be obtained through the printer ledger information + SNMP configuration information, that is, the data information in the first data table. The number of records should be consistent with the records in the printer ledger information table. If it is inconsistent or the obtained status information is empty, it may be because a certain printer brand model in the ledger is not configured with SNMP information, that is, the corresponding information of OID and field identifier, or the configured OID corresponding information is incorrect.
[0076] In one embodiment, the method may also include: when the status field information is set in the printer status field configuration table, synchronously inserting at least one field type and field identifier in the status field information into a fourth data table; executing a flow collection task, sending the data acquisition request to the target printer at a preset time interval, receiving at least one parameter value corresponding to the at least one object identifier OID returned by the target printer and writing it into the fourth data table, wherein the fourth data table is used to store the historical status information of the target printer.
[0077] Exemplarily, the fourth data table is the printer history status flow table pms_rtstate_his, which stores the target printer history status information. The printer status field configuration table pms_rtstatefld_cfg is a dynamic configuration table, which is used to record the parameter value corresponding to a certain attribute of the target printer obtained and stored in the database. The field identifier and field type, inserting a record into the printer status field configuration table is to configure the above status field information, and the synchronization field will also be dynamically added to the table pms_rtstate_his, i.e., the printer history status flow table, i.e., adding at least one field type and field identifier in the above status field information, so that the collected parameter value can be stored in the corresponding field in the fourth data table.
[0078] In this embodiment, automatic collection tasks such as flow collection tasks can be set, for example, a task is executed once at 10 am and 16 pm every day, and updated and synchronized to the table pms_rtstate_his, i.e., the printer history state flow table. The management method of automated data flow collection and adding synchronization fields not only improves efficiency, but also ensures that the collected data is stored in the database in a timely and accurate manner.
[0079] The printer history status flow table stores the flow records of the printer's historical status information. The methods for obtaining the flow records of the status information include: obtaining it through the printer ledger information + SNMP configuration information, that is, the data information in the first data table. A printer ledger information will have multiple historical records in the printer history status flow table. The data in this table can provide data support for report statistics.
[0080] In one embodiment, the method may further include: obtaining a printer ledger information table, the printer ledger information table including the ledger information of the multiple printers, the ledger information including at least one or more of the printer brand model, printer serial number, purchase date, warranty period, and affiliated organization information; obtaining the ledger information of the target printer from the printer ledger information table; and obtaining the target printer historical status information from the fourth data table based on the ledger information of the target printer and the first data table.
[0081] Specifically, the data collection module can be used to establish and maintain the ledger information of all networked printers in the enterprise. The ledger information includes the equipment information of each printer (such as brand model, serial number), purchase date, warranty period, affiliated organization information (such as organization name, number), etc. Through unified ledger management, the enterprise can fully grasp the distribution and use of all current printers, which is convenient for subsequent maintenance and management.
[0082] In one embodiment, the method further includes: generating statistical report information based on the data in the fourth data table. This embodiment provides data visualization and report statistical support. Through the data of the historical status flow table, detailed statistical reports such as statistical charts can be generated, which can help enterprise managers to make decision analysis and optimize printing resources. For example, printer resources can be used more efficiently, reducing unnecessary maintenance costs and time costs.
[0083] Specifically, in one example, the data collected in the fourth data table is cleaned, sorted and stored, and the report statistics module generates reports such as print volume statistics, consumables (such as paper or ink) usage statistics and energy consumption statistics based on the processed data. These reports can provide intuitive data display to help enterprise managers accurately understand the usage of all printers and consumables consumption.
[0084] Based on the energy consumption statistical analysis results of the report, optimize the usage strategy of each printer to improve the utilization rate of printing equipment, reduce operating costs, and improve the overall management level.
[0085] By analyzing the energy consumption statistics of each printer, we can identify high-energy-consuming devices and provide corresponding energy-saving suggestions. These suggestions can include optimizing the distribution of printing tasks, reducing the idle time of printers, etc. In this way, through reasonable energy consumption management, we can effectively reduce energy consumption, save costs, and achieve green office.
[0086] In the above-mentioned embodiments of the present disclosure, the dynamic collection of printer attribute parameters can be realized by configuring the relevant tables in the database, and the real-time status display can be performed, and the data basis can be provided for data statistics, which is mainly completed by the cooperation of the above-mentioned six tables. It is based on the SNMP protocol for printer management, and through dynamic expansion technology and perfect database table design, it realizes efficient management and real-time status monitoring of all networked printers in the enterprise. By obtaining printer status information through the SNMP protocol, the printer data collection type can be dynamically expanded, and the printer ledger management, status monitoring and data statistics can be realized through six core tables (pms_code_info, pms_ledger_info, pms_rtstatefld_cfg, pms_devparm_cfg, pms_rtstate_dtl, pms_rtstate_his). This solution effectively improves the scalability, flexibility and maintenance efficiency of the system, and meets the needs of enterprises for high efficiency and accuracy of printer management.
[0087] The configuration file can dynamically expand the type of printer data collection, and can quickly respond to new printer types and data collection requirements. When configuring a new printer, you only need to configure and update the pms_rtstatefld_cfg and pms_devparm_cfg tables without modifying the system code, which improves the scalability and flexibility of the system, improves maintenance efficiency, and reduces maintenance costs and difficulties.
[0088] It should be noted that, although the steps of the method in the present disclosure are described in a specific order in the accompanying drawings, this does not require or imply that the steps must be performed in this specific order, or that all the steps shown must be performed to achieve the desired results. Additionally or alternatively, some steps may be omitted, multiple steps may be combined into one step for execution, and / or one step may be decomposed into multiple steps for execution, etc. In addition, it is also easy to understand that these steps may be, for example, executed synchronously or asynchronously in multiple modules / processes / threads.
[0089] like Figure 4 As shown, an embodiment of the present disclosure provides a printer management system, which is applied to a printer management device, wherein the printer management device is communicatively linked with a plurality of printers, and the system includes:
[0090] The information configuration module 401 is used to obtain data collection requirement information of a target printer, and to set status field information in a printer status field configuration table based on the data collection requirement information; wherein the target printer is any one of the plurality of printers, and the data collection requirement information is used to indicate the collection of at least one type of status information of the target printer; and the status field information includes at least one field type and field identifier corresponding to the at least one type of status information;
[0091] An information search module 402 is used to determine the printer brand and model of the target printer, and based on the printer brand and model and at least one field identifier in the status field information, search and obtain at least one corresponding object identifier OID from a first data table;
[0092] The data acquisition module 403 is used to generate a data acquisition request based on the at least one object identifier OID, send the data acquisition request to the target printer, and receive at least one parameter value corresponding to the at least one object identifier OID returned by the target printer.
[0093] In one embodiment, the printer management device and the multiple printers are linked based on a preconfigured Simple Network Management Protocol (SNMP) communication link; the data acquisition request is a UDP request, the UDP request carries at least the at least one object identifier (OID), and the UDP request is sent to the IP address and target port of the target printer.
[0094] In one embodiment, the information search module 402 determines the printer brand and model of the target printer, including: obtaining the printer brand and model of the target printer from a second data table, wherein the second data table is pre-configured with the respective brands and models of the plurality of printers.
[0095] In one embodiment, the first data table is pre-configured with a plurality of object identifiers OIDs corresponding to different printer brands and models, and field identifiers corresponding to the plurality of object identifiers OIDs corresponding to each of the printer brands and models.
[0096] In one embodiment, the system may further include a first execution module, configured to:
[0097] When the status field information is set in the printer status field configuration table, at least one field type and field identifier in the status field information is synchronously inserted into the third data table;
[0098] Execute a real-time acquisition task, send the data acquisition request to the target printer in real time; receive at least one parameter value corresponding to the at least one object identifier OID returned by the target printer in real time;
[0099] At least one parameter value corresponding to the at least one object identifier OID returned in real time by the target printer is written into the third data table, and the third data table is used to store the current real-time status information of the target printer.
[0100] In one embodiment, the system may further include a second execution module, configured to:
[0101] When the status field information is set in the printer status field configuration table, at least one field type and field identifier in the status field information is synchronously inserted into the fourth data table;
[0102] Execute the pipeline collection task, send the data acquisition request to the target printer at a preset time interval, receive at least one parameter value corresponding to the at least one object identifier OID returned by the target printer and write it into the fourth data table, where the fourth data table is used to store the historical status information of the target printer.
[0103] In one embodiment, the system may also include a data reading module, which is used to: obtain a printer ledger information table, the printer ledger information table contains the ledger information of the multiple printers, the ledger information contains at least one or more of the printer brand model, printer serial number, purchase date, warranty period, and affiliated organization information; obtain the ledger information of the target printer from the printer ledger information table; based on the ledger information of the target printer and the first data table, obtain the target printer historical status information from the fourth data table.
[0104] In one embodiment, the system may further include a report generation module, which is used to generate statistical report information based on the data in the fourth data table.
[0105] In one example, the data collected in the fourth data table are cleaned, sorted and stored, and the report statistics module generates reports such as printing volume statistics, consumables (such as paper or ink) usage statistics and energy consumption statistics based on the processed data.
[0106] Based on the energy consumption statistical analysis results of the report, optimize the usage strategy of each printer to improve the utilization rate of printing equipment, reduce operating costs, and improve the overall management level.
[0107] By analyzing the energy consumption statistics of each printer, we can identify high energy consumption devices and provide corresponding energy saving suggestions. These suggestions can include optimizing the distribution of printing tasks, reducing the idle time of printers, etc.
[0108] Regarding the system in the above embodiment, the specific manner in which each module performs operations and the corresponding technical effects brought about have been described in detail in the embodiment of the method, and will not be elaborated here.
[0109] It should be noted that although several modules or units of the device for action execution are mentioned in the above detailed description, this division is not mandatory. In fact, according to the embodiment of the present disclosure, the features and functions of two or more modules or units described above can be concretized in one module or unit. Conversely, the features and functions of a module or unit described above can be further divided into multiple modules or units for concretization. The components displayed as modules or units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the disclosed solution. Those of ordinary skill in the art can understand and implement it without paying creative work.
[0110] The embodiment of the present disclosure further provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the printer management method described in any one of the above embodiments is implemented.
[0111] Exemplarily, the readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination thereof. More specific examples of readable storage media (a non-exhaustive list) include: an electrical connection with one or more wires, a portable disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof.
[0112] The computer readable storage medium may include a data signal propagated in a baseband or as part of a carrier wave, wherein a readable program code is carried. This propagated data signal may take a variety of forms, including but not limited to an electromagnetic signal, an optical signal, or any suitable combination of the above. The readable storage medium may also be any readable medium other than a readable storage medium, which may send, propagate, or transmit a program for use by an instruction execution system, an apparatus, or a device or used in combination with it. The program code contained on the readable storage medium may be transmitted with any appropriate medium, including but not limited to wireless, wired, optical cable, RF, etc., or any suitable combination of the above.
[0113] The embodiment of the present disclosure further provides an electronic device, comprising a processor and a memory, wherein the memory is used to store a computer program, wherein the processor is configured to execute the printer management method in any of the above embodiments by executing the computer program.
[0114] Refer to the following Figure 5 The electronic device 600 according to this embodiment of the present invention is described. Figure 5 The electronic device 600 shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present invention.
[0115] like Figure 5 As shown, the electronic device 600 is in the form of a general computing device. The components of the electronic device 600 may include, but are not limited to: at least one processing unit 610, at least one storage unit 620, a bus 630 connecting different system components (including the storage unit 620 and the processing unit 610), a display unit 640, etc.
[0116] The storage unit stores program codes, which can be executed by the processing unit 610, so that the processing unit 610 performs the steps according to various exemplary embodiments of the present invention described in the above method embodiment section of this specification. For example, the processing unit 610 can perform the following steps: Figure 1 The steps of the method shown in .
[0117] The storage unit 620 may include a readable medium in the form of a volatile storage unit, such as a random access memory unit (RAM) 6201 and / or a cache memory unit 6202 , and may further include a read-only memory unit (ROM) 6203 .
[0118] The storage unit 620 may also include a program / utility 6204 having a set (at least one) of program modules 6205, such program modules 6205 including but not limited to: an operating system, one or more application programs, other program modules and program data, each of which or some combination may include the implementation of a network environment.
[0119] Bus 630 may represent one or more of several types of bus structures, including a memory unit bus or memory unit controller, a peripheral bus, an accelerated graphics port, a processing unit, or a local bus using any of a variety of bus architectures.
[0120] The electronic device 600 may also communicate with one or more external devices 700 (e.g., keyboards, pointing devices, Bluetooth devices, printers, etc.), may also communicate with one or more devices that enable a user to interact with the electronic device 600, and / or communicate with any device that enables the electronic device 600 to communicate with one or more other computing devices (e.g., routers, modems, etc.). Such communication may be performed via an input / output (I / O) interface 650. Furthermore, the electronic device 600 may also communicate with one or more networks (e.g., a local area network (LAN), a wide area network (WAN), and / or a public network, such as the Internet) via a network adapter 660. The network adapter 660 may communicate with other modules of the electronic device 600 via a bus 630. It should be understood that, although not shown in the figure, other hardware and / or software modules may be used in conjunction with the electronic device 600, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.
[0121] Through the description of the above implementation methods, it is easy for those skilled in the art to understand that the example implementation methods described here can be implemented by software, or by software combined with necessary hardware. Therefore, the technical solution according to the implementation methods of the present disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which can be a personal computer, a server, or a network device, etc.) to execute the method steps of the above-mentioned embodiments according to the implementation methods of the present disclosure.
[0122] It should be noted that, in this article, relational terms such as "first" and "second" are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.
[0123] The above description is only a specific embodiment of the present disclosure, so that those skilled in the art can understand or implement the present disclosure. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present disclosure. Therefore, the present disclosure will not be limited to the embodiments described herein, but will conform to the widest scope consistent with the principles and novel features disclosed herein.
Claims
1. A printer management method, characterized in that: The method is applied to a printer management device, wherein the printer management device is communicatively linked with a plurality of printers, and the method comprises: Acquire data collection requirement information of a target printer, and set status field information in a printer status field configuration table based on the data collection requirement information; wherein the target printer is any one of the multiple printers, and the data collection requirement information is used to indicate the collection of at least one type of status information of the target printer; the status field information includes at least one field type and field identifier corresponding to the at least one type of status information; Determine the printer brand and model of the target printer, and based on the printer brand and model and at least one field identifier in the status field information, search and obtain at least one corresponding object identifier OID from the first data table; A data acquisition request is generated based on the at least one object identifier OID, and the data acquisition request is sent to the target printer; and at least one parameter value corresponding to the at least one object identifier OID returned by the target printer is received.
2. The method according to claim 1, characterized in that The printer management device and the multiple printers are linked based on a preconfigured Simple Network Management Protocol (SNMP) communication link; the data acquisition request is a UDP request, the UDP request carries at least the at least one object identifier (OID), and the UDP request is sent to the IP address and target port of the target printer.
3. The method according to claim 2, characterized in that The determining the printer brand and model of the target printer comprises: acquiring the printer brand and model of the target printer from a second data table, wherein the second data table is pre-configured with the respective brand and model of the plurality of printers; or, The first data table is pre-configured with a plurality of object identifiers OIDs corresponding to different printer brands and models, and field identifiers corresponding to the plurality of object identifiers OIDs corresponding to each of the printer brands and models.
4. The method according to claim 3, characterized in that The method further includes: When the status field information is set in the printer status field configuration table, at least one field type and field identifier in the status field information is synchronously inserted into the third data table; Execute a real-time acquisition task, send the data acquisition request to the target printer in real time; receive at least one parameter value corresponding to the at least one object identifier OID returned by the target printer in real time; At least one parameter value corresponding to the at least one object identifier OID returned in real time by the target printer is written into the third data table, and the third data table is used to store the current real-time status information of the target printer.
5. The method according to claim 3, characterized in that: The method further includes: When the status field information is set in the printer status field configuration table, at least one field type and field identifier in the status field information is synchronously inserted into the fourth data table; Execute the transaction collection task, send the data acquisition request to the target printer at a preset time interval, receive at least one parameter value corresponding to the at least one object identifier OID returned by the target printer and write it into the fourth data table, where the fourth data table is used to store the historical status information of the target printer.
6. The method according to claim 5, characterized in that The method further includes: Obtaining a printer ledger information table, wherein the printer ledger information table includes ledger information of the plurality of printers, wherein the ledger information includes at least one or more of printer brand model, printer serial number, purchase date, warranty period, and affiliated institution information; Obtaining the record information of the target printer from the printer record information table; Based on the ledger information of the target printer and the first data table, historical status information of the target printer is obtained from the fourth data table.
7. The method according to claim 5 or 6, characterized in that: The method further includes: Generate statistical report information based on the data in the fourth data table.
8. A printer management system, characterized in that: The system is applied to a printer management device, wherein the printer management device is linked to multiple printers in communication, and the system comprises: An information configuration module, used to obtain data collection requirement information of a target printer, and to set status field information in a printer status field configuration table based on the data collection requirement information; wherein the target printer is any one of the plurality of printers, and the data collection requirement information is used to indicate the collection of at least one type of status information of the target printer; and the status field information includes at least one field type and field identifier corresponding to the at least one type of status information; An information search module, used to determine the printer brand and model of the target printer, and based on the printer brand and model and at least one field identifier in the status field information, search and obtain the corresponding at least one object identifier OID from the first data table; The data acquisition module is used to generate a data acquisition request based on the at least one object identifier OID, send the data acquisition request to the target printer, and receive at least one parameter value corresponding to the at least one object identifier OID returned by the target printer.
9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the printer management method according to any one of claims 1 to 7 is implemented.
10. An electronic device, characterized in that: include: processor; as well as Memory for storing computer programs; The processor is configured to execute the printer management method according to any one of claims 1 to 7 by executing the computer program.
Citation Information
Cited By
Method and system for realizing voice interaction of printer
CN121807246A
A method and system for printer voice interaction implementation
CN121807246B