English:
[0001] Multi-function devices often combine different components such as a printer, scanner, and copier into a single device. Such devices frequently receive refills of consumables, such as print substances (e.g., ink, toner, and/or additive materials) and/or media (e.g., paper, vinyl, and/or other print substrates).
[0002] FIG. 1 is a block diagram of an example computing device for providing communication asset usage tracking.
[0003] FIG. 2 is a flowchart of an example method for providing communication asset usage tracking.
[0004] FIG. 3 is a block diagram of an example system for providing communication asset usage tracking.
[0005] Throughout the drawings, identical reference numbers designate similar, but not necessarily identical, elements. The figures are not necessarily to scale, and the size of some parts may be exaggerated to more clearly illustrate the example shown. Moreover the drawings provide examples and/or implementations consistent with the description; however, the description is not limited to the examples and/or implementations provided in the drawings.
[0006] Most multi-function-print devices (MFPs) provide several features, such as an option to scan a physical document, which may be controlled via an on-device control panel, a connected application, and/or a remote service. Other options may include printing, copying, faxing, document assembly, etc. The scanning portion of an MFP may comprise an optical assembly located within a sealed enclosure. The sealed enclosure may have a scan window through which the optical assembly can scan a document, which may be placed on a flatbed and/or delivered by a sheet feeder mechanism.
[0007] Printers and similar MFPs may sometimes present a security threat as they are ubiquitous yet often overlooked. These devices may be directly connected to public networks, such as the Internet and may have access to sensitive information like confidential reports, contracts, medical records, and the like in the form of documents being scanned, copied, printed, etc. In some circumstances, MFPs may offer numerous communication assets to enable easy use of the functionality they provide. Such communication assets may comprise, for example, physical communication ports (e.g., USB, serial, parallel, etc.) and/or wired and/or wireless network assets such as ethernet ports, radio frequency identification (RFID), near field communication (NFC), Bluetooth, WiFi, etc. Communication assets may also comprise, in some implementations, services and communication protocols used by the device, such as TCP/IP, UDP, web services, management console and mobile app communication ports, Simple Network Management Protocol (SNMP) services, etc.
[0008] This variety of communication assets may be enabled on various devices and in various configurations but may present an unnecessary security risk. By tracking usage metrics for these assets, unneeded assets may be disabled and/or secured. For example, an SNMP service that has not been used in over a threshold period, such as 90 days, may be automatically disabled. For another example, an NFC reader that has only been used once in the last month may be presented with a recommendation to disable it to an administrator of the device.
[0009] FIG. 1 is a block diagram of an example computing device 110 for providing communication asset usage tracking. Computing device 110 may comprise a processor 112 and a non-transitory, machine-readable storage medium 114. Storage medium 114 may comprise a plurality of processor-executable instructions, such as record usage metric instructions 120, usage metric threshold instructions 125, and cause asset to be disabled instructions 130. In some implementations, instructions 120, 125, 130 may be associated with a single computing device 110 and/or may be communicatively coupled among different computing devices such as via a direct connection, bus, or network.
[0010] Processor 112 may comprise a central processing unit (CPU), a semiconductor-based microprocessor, a programmable component such as a complex programmable logic device (CPLD) and/or field-programmable gate array (FPGA), or any other hardware device suitable for retrieval and execution of instructions stored in machine-readable storage medium 114. In particular, processor 112 may fetch, decode, and execute instructions 120, 125, 130.
[0012] The machine-readable storage medium 114 may comprise, for example, random access memory (RAM), read-only memory (ROM), hard disk drives, solid-state drives, USB flash drives, memory cards accessed via a memory card reader, floppy disks accessed via an associated floppy disk drive, optical discs accessed via an optical disc drive, magnetic tapes accessed via an appropriate tape drive, and/or other memory components, and/or a combination of any two and/or more of these memory components. In addition, the RAM may comprise, for example, static random access memory (SRAM), dynamic random access memory (DRAM), and/or magnetic random access memory (MRAM) and other such devices. The ROM may comprise, for example, a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), and/or other like memory device.
[0013] Record usage metric instructions 120 may record, for at least one of a plurality of communication assets, at least one usage metric. The communication assets may comprise, for example, a network port, an application, a service, a physical communication link such as a USB port and/or communication cable, and/or a wireless communication link, such as RFID, NFC, Bluetooth, WiFi, etc. In some implementations, the usage metric may comprise a last used time for the at least one of the plurality of communication assets, a usage frequency for the at least one of the plurality of communication assets, a count of requests to use the at least one of the plurality of communication assets within a time period, and/or a count of unique users who request to use the at least one of the plurality of communication asset.
[0014] Usage metric threshold instructions 125 may determine, for the at least one of the plurality of communication assets, whether the at least one usage metric fails to meet a threshold. For example, a threshold for a usage metric comprising a last used time may comprise a usage frequency and/or an amount of time since the last time the communication asset was used, such as a 30 day threshold. If the communication asset has not been used within the threshold amount of time, instructions 125 may determine that the usage metric has failed to meet the threshold. For another example, a threshold for a usage metric comprising a count of requests and/or users of the communication asset may comprise a minimum number to be considered not to have failed to meet the threshold (e.g., two uses and/or users within the last 30 days would not satisfy a threshold of five uses). In some implementations, multiple thresholds may need to be met to avoid a communication asset being disabled.
[0016] In some implementations, the instructions 130 to cause the at least one of the plurality of communication assets to be disabled may further comprise instructions to notify an administrator of an attempt to utilize the communication asset after causing the at least one of the plurality of communication assets to be disabled. For example, if a web server asset has been disabled, an administrator of device 110 may be notified if further connections to the web server are attempted.
[0017] FIG. 2 is a flowchart of an example method 200 for communication asset usage tracking. Although execution of method 200 is described below with reference to computing device 110, other suitable components for execution of method 200 may be used.
[0019] Method 200 may then advance to stage 220 where computing device 110 may determine whether the usage metric fails to meet a threshold for each of the plurality of communication assets. For example, device 110 may execute usage metric threshold instructions 125 to determine, for the at least one of the plurality of communication assets, whether the at least one usage metric fails to meet a threshold. For example, a threshold for a usage metric comprising a last used time may comprise a usage frequency and/or an amount of time since the last time the communication asset was used, such as a 30 day threshold. If the communication asset has not been used within the threshold amount of time, instructions 125 may determine that the usage metric has failed to meet the threshold. For another example, a threshold for a usage metric comprising a count of requests and/or users of the communication asset may comprise a minimum number to be considered not to have failed to meet the threshold (e.g., two uses and/or users within the last 30 days would not satisfy a threshold of five uses). In some implementations, multiple thresholds may need to be met to avoid a communication asset being disabled.
[0020] In response to determining that the usage metric fails to meet the threshold for at least one of the plurality of communication assets, method 200 may advance to stage 230 where computing device 110 may cause the at least one of the plurality of communication assets to be disabled. For example, device 110 may execute usage metric threshold instructions 125 to determine, for the at least one of the plurality of communication assets, whether the at least one usage metric fails to meet a threshold. For example, a threshold for a usage metric comprising a last used time may comprise a usage frequency and/or an amount of time since the last time the communication asset was used, such as a 30 day threshold. If the communication asset has not been used within the threshold amount of time, instructions 125 may determine that the usage metric has failed to meet the threshold. For another example, a threshold for a usage metric comprising a count of requests and/or users of the communication asset may comprise a minimum number to be considered not to have failed to meet the threshold (e.g., two uses and/or users within the last 30 days would not satisfy a threshold of five uses). In some implementations, multiple thresholds may need to be met to avoid a communication asset being disabled.
[0021] After causing the at least one of the plurality of communication assets to be disabled at stage 230, or if the usage metric was determined to not have been failed at stage 220, method 200 may end at stage 250.
[0022] FIG. 3 is a block diagram of an example apparatus 300 for providing communication asset usage tracking. Apparatus 300 may comprise a multi-function printer device 302 comprising a storage medium 310, and a processor 312. Device 302 may comprise and/or be associated with, for example, a general and/or special purpose computer, server, mainframe, desktop, laptop, tablet, smart phone, game console, printer, multi-function device, and/or any other system capable of providing computing capability consistent with providing the implementations described herein. Device 302 may store, in storage medium 310, a tracking engine 320 and an asset control engine 325.
[0023] Each of engines 320, 325 may comprise any combination of hardware and programming to implement the functionalities of the respective engine. In examples described herein, such combinations of hardware and programming may be implemented in a number of different ways. For example, the programming for the engines may be processor executable instructions stored on a non-transitory machine-readable storage medium and the hardware for the engines may include a processing resource to execute those instructions. In such examples, the machine-readable storage medium may store instructions that, when executed by the processing resource, implement engines 320, 325. In such examples, device 302 may comprise the machine-readable storage medium storing the instructions and the processing resource to execute the instructions, or the machine-readable storage medium may be separate but accessible to apparatus 300 and the processing resource.
[0024] Tracking engine 320 may track a usage metric for each of a plurality of communication assets, and determine whether the usage metric fails to meet a threshold for at least one of the plurality of communication assets. For example, tracking engine 320 may execute record usage metric instructions 120 to record, for at least one of a plurality of communication assets, at least one usage metric. The communication assets may comprise, for example, a network port, an application, a service, a physical communication link such as a USB port and/or communication cable, and/or a wireless communication link, such as RFID, NFC, Bluetooth, WiFi, etc. In some implementations, the usage metric may comprise a last used time for the at least one of the plurality of communication assets, a usage frequency for the at least one of the plurality of communication assets, a count of requests to use the at least one of the plurality of communication assets within a time period, and/or a count of unique users who request to use the at least one of the plurality of communication asset.
[0025] In some implementations, tracking engine 320 may execute usage metric threshold instructions 125 to determine, for the at least one of the plurality of communication assets, whether the at least one usage metric fails to meet a threshold. For example, a threshold for a usage metric comprising a last used time may comprise a usage frequency and/or an amount of time since the last time the communication asset was used, such as a 30 day threshold. If the communication asset has not been used within the threshold amount of time, instructions 125 may determine that the usage metric has failed to meet the threshold. For another example, a threshold for a usage metric comprising a count of requests and/or users of the communication asset may comprise a minimum number to be considered not to have failed to meet the threshold (e.g., two uses and/or users within the last 30 days would not satisfy a threshold of five uses). In some implementations, multiple thresholds may need to be met to avoid a communication asset being disabled.
[0026] Asset control engine 325 may, in response to determining that the usage metric fails to meet the threshold for the at least one of the plurality of communication assets, disable the at least one of the plurality of communication assets. For example, asset control engine 325 may execute usage metric threshold instructions 125 to determine, for the at least one of the plurality of communication assets, whether the at least one usage metric fails to meet a threshold. For example, a threshold for a usage metric comprising a last used time may comprise a usage frequency and/or an amount of time since the last time the communication asset was used, such as a 30 day threshold. If the communication asset has not been used within the threshold amount of time, instructions 125 may determine that the usage metric has failed to meet the threshold. For another example, a threshold for a usage metric comprising a count of requests and/or users of the communication asset may comprise a minimum number to be considered not to have failed to meet the threshold (e.g., two uses and/or users within the last 30 days would not satisfy a threshold of five uses). In some implementations, multiple thresholds may need to be met to avoid a communication asset being disabled.
[0027] In the foregoing detailed description of the disclosure, reference is made to the accompanying drawings that form a part hereof, and in which is shown by way of illustration how examples of the disclosure may be practiced. These examples are described in sufficient detail to allow those of ordinary skill in the art to practice the examples of this disclosure, and it is to be understood that other examples may be utilized and that process, electrical, and/or structural changes may be made without departing from the scope of the present disclosure.

中文:
[0001]多功能装置通常将诸如打印机、扫描仪和复印机的不同部件组合成单个装置。这种装置经常接收诸如打印物质(例如,墨水、调色剂和/或添加材料)和/或介质(例如,纸张、乙烯基塑料和/或其他打印基材)的耗材的补充。
[0002]图1是用于提供通信资产使用跟踪的示例计算装置的框图。
[0003]图2是用于提供通信资产使用跟踪的示例方法的流程图。
[0004]图3是用于提供通信资产使用跟踪的示例系统的框图。
[0005]在所有附图中,相同的附图标记表示相似但不一定相同的元件。附图不一定按比例绘制,并且一些部件的尺寸可能被放大以更清楚地说明所示出的示例。此外,附图提供了与描述一致的示例和/或实现;然而,描述不限于附图中所提供的示例和/或实现。
[0006]大多数多功能打印装置(MFP)提供了诸如扫描物理文档的选项的多种特征,这可以经由装置上的控制面板、连接的应用和/或远程服务来控制。其他选项可以包括打印、复印、传真、文件汇编等。MFP的扫描部分可以包括位于密封外壳内的光学组件。密封外壳可以具有扫描窗口,光学组件可以通过该扫描窗口扫描文档,该文档可以放置在平板上和/或由送纸机构传送。
[0007]打印机和类似的MFP有时可能呈现安全威胁,因为它们无处不在,但却经常被忽视。这些装置可以直接连接到诸如因特网的公共网络,并且可以访问敏感信息,例如采用被扫描、复制、打印等的文档的形式的机密报告、合同、医疗记录等。在某些情况下,MFP可以提供多种通信资产,以易于使用它们提供的功能。这种通信资产可以包括例如物理通信端口(例如,USB、串行、并行等)和/或有线和/或无线网络资产,诸如以太网端口、射频识别(RFID)、近场通信(NFC)、蓝牙、WiFi等。在一些实现中,通信资产还可以包括由装置使用的服务和通信协议,诸如TCP/IP、UDP、web服务、管理控制台和移动应用通信端口、简单网络管理协议(SNMP)服务等。
[0008]这些各式各样的通信资产可以在各种装置上并以各种配置实现,但是可能存在不必要的安全风险。通过跟踪这些资产的使用度量,可以禁用和/或保护不需要的资产。例如,可以自动禁用超过诸如90天的阈值时段未使用的SNMP服务。作为另一示例,可以将上个月只使用过一次的NFC读取器推荐给装置的管理员,以将其禁用。
[0009]图1是用于提供通信资产使用跟踪的示例计算装置110的框图。计算装置110可以包括处理器112和非暂时性机器可读存储介质114。存储介质114可以包括诸如记录使用度量指令120、使用度量阈值指令125和使资产被禁用指令130的多个处理器可执行指令。在一些实现中,指令120、125、130可以与单个计算装置110相关联和/或可以诸如经由直接连接、总线或者网络在不同的计算装置之间通信地耦接。
[0010]处理器112可以包括中央处理单元(CPU)、基于半导体的微处理器、诸如复杂可编程逻辑器件(CPLD)和/或现场可编程门阵列(FPGA)的可编程部件或者适用于检索并执行存储在机器可读存储介质114中的指令的任何其他硬件装置。具体地,处理器112可以获取、解码和执行指令120、125、130。
[0012]机器可读存储介质114可以包括例如随机存取存储器(RAM)、只读存储器(ROM)、硬盘驱动器、固态驱动器、USB闪存驱动器、经由存储卡读卡器访问的存储卡、经由关联的软盘驱动器访问的软盘、经由光盘驱动器访问的光盘、经由合适的磁带驱动访问的磁带和/或其他存储器部件和/或以上存储器部件中的任意两个和/或更多个的组合。此外,RAM可以包括例如静态随机存取存储器(SRAM)、动态随机存取存储器(DRAM)和/或磁性随机存取存储器(MRAM)和其他这种装置。ROM可以包括例如可编程只读存储器(PROM)、可擦除可编程只读存储器(EPROM)、电可擦除可编程只读存储器(EEPROM)和/或其他类似的存储装置。
[0013]针对多个通信资产中的至少一个,记录使用度量指令120可以记录至少一个使用度量。通信资产可以包括例如网络端口、应用、服务、诸如USB端口和/或通信电缆的物理通信链路和/或诸如RFID、NFC、蓝牙、WiFi的无线通信链路等。在一些实现中,使用度量可以包括多个通信资产中的至少一个的上次使用时间、多个通信资产中的至少一个的使用频率、在一时间段内使用多个通信资产中的至少一个的请求的计数和/或请求使用多个通信资产中的至少一个的唯一用户的计数。
[0014]针对多个通信资产中的至少一个,使用度量阈值指令125可以确定至少一个使用度量是否未能满足阈值。例如,包括上次使用时间的使用度量的阈值可以包括自上次使用通信资产以来的使用频率和/或时间量(诸如30天阈值)。如果通信资产在阈值时间量内未被使用,则指令125可以确定使用度量未能满足阈值。对于另一示例,包括通信资产的请求和/或用户的计数的使用度量的阈值可以包括被认为未能满足阈值的最小数量(例如,上次30天内的两次使用和/或用户将不满足五次使用的阈值)。在一些实现中,可能需要满足多个阈值以避免通信资产被禁用。
[0016]在一些实现中,使多个通信资产中的至少一个被禁用的指令130可以进一步包括在使多个通信资产中的至少一个被禁用之后通知管理员尝试利用通信资产的指令。例如,如果web服务器资产已经被禁用,则可以通知装置110的管理员是否尝试进一步连接到web服务器。
[0017]图2是用于通信资产使用跟踪的示例方法200的流程图。尽管在下文参考计算装置110描述了方法200的执行,但用于执行方法200的其他合适的部件也是可以使用的。
[0019]方法200然后可以前进到计算装置110可以针对多个通信资产中的每一个确定使用度量是否未能满足阈值的阶段220。例如,装置110可以执行使用度量阈值指令125以针对多个通信资产中的至少一个确定至少一个使用度量是否未能满足阈值。例如,包括上次使用时间的使用度量的阈值可以包括自上次使用通信资产以来的使用频率和/或时间量(诸如30天阈值)。如果通信资产在阈值时间量内未被使用,则指令125可以确定使用度量未能满足阈值。对于另一示例,包括通信资产的请求和/或用户的计数的使用度量的阈值可以包括被认为未能满足阈值的最小数量(例如,上次30天内的两次使用和/或用户将不满足五次使用的阈值)。在一些实现中,可能需要满足多个阈值以避免通信资产被禁用。
[0020]针对多个通信资产中的至少一个,响应于确定使用度量未能满足阈值,方法200可以前进到计算装置110可以使多个通信资产中的至少一个被禁用的阶段230。例如,装置110可以执行使用度量阈值指令125以针对多个通信资产中的至少一个确定至少一个使用度量是否未能满足阈值。例如,包括上次使用时间的使用度量的阈值可以包括自上次使用通信资产以来的使用频率和/或时间量(诸如30天阈值)。如果通信资产在阈值时间量内未被使用,则指令125可以确定使用度量未能满足阈值。对于另一示例,包括通信资产的请求和/或用户的计数的使用度量的阈值可以包括被认为未能满足阈值的最小数量(例如,上次30天内的两次使用和/或用户将不满足五次使用的阈值)。在一些实现中,可能需要满足多个阈值以避免通信资产被禁用。
[0021]在阶段230处使多个通信资产中的至少一个被禁用之后,或者如果在阶段220处确定使用度量合格,则方法200可以在阶段250结束。
[0022]图3是用于提供通信资产使用跟踪的示例设备300的框图。设备300可以包括包含存储介质310和处理器312的多功能打印机装置302。装置302可以包括和/或关联于例如通用和/或专用计算机、服务器、大型机、台式机、膝上型电脑、平板电脑、智能电话、游戏控制台、打印机、多功能装置和/或能够提供与提供本文中描述的实现一致的计算能力的任何其他系统。装置302可以在存储介质310中存储跟踪引擎320和资产控制引擎325。
[0023]引擎320、325中的每一个可以包括硬件和编程的任何组合,以实现相应引擎的功能。在本文中描述的示例中,硬件和编程的这种组合可以以多种不同的方式实现。例如,引擎的编程可以是存储在非暂时性机器可读存储介质上的处理器可执行指令,并且引擎的硬件可以包括执行这些指令的处理资源。在这种示例中,机器可读存储介质可以存储指令,该指令当由处理资源执行时,实现引擎320、325。在这种示例中,装置302可以包括存储指令的机器可读存储介质和执行指令的处理资源,或者机器可读存储介质可以是独立的但由设备300和处理资源可访问。
[0024]跟踪引擎320可以跟踪多个通信资产中的每一个的使用度量,并且确定使用度量是否未能满足多个通信资产中的至少一个的阈值。例如,跟踪引擎320可以执行记录使用度量指令120以针对多个通信资产中的至少一个记录的至少一个使用度量。通信资产可以包括例如网络端口、应用、服务、诸如USB端口和/或通信电缆的物理通信链路和/或诸如RFID、NFC、蓝牙、WiFi的无线通信链路等。在一些实现中,使用度量可以包括多个通信资产中的至少一个的上次使用时间、多个通信资产中的至少一个的使用频率、在一时间段内使用多个通信资产中的至少一个的请求的计数和/或请求使用多个通信资产中的至少一个的唯一用户的计数。
[0025]在一些实现中,跟踪引擎320可以执行使用度量阈值指令125以针对多个通信资产中的至少一个确定至少一个使用度量是否未能满足阈值。例如,包括上次使用时间的使用度量的阈值可以包括自上次使用通信资产以来的使用频率和/或时间量(诸如30天阈值)。如果通信资产在阈值时间量内未被使用,则指令125可以确定使用度量未能满足阈值。对于另一示例,包括通信资产的请求和/或用户的计数的使用度量的阈值可以包括被认为未能满足阈值的最小数量(例如,上次30天内的两次使用和/或用户将不满足五次使用的阈值)。在一些实现中,可能需要满足多个阈值以避免通信资产被禁用。
[0026]资产控制引擎325可以响应于针对多个通信资产中的至少一个确定使用度量未能满足阈值来禁用多个通信资产中的至少一个。例如,资产控制引擎325可以执行使用度量阈值指令125,以针对多个通信资产中的至少一个确定至少一个使用度量是否未能满足阈值。例如,包括上次使用时间的使用度量的阈值可以包括自上次使用通信资产以来的使用频率和/或时间量(诸如30天阈值)。如果通信资产在阈值时间量内未被使用,则指令125可以确定使用度量未能满足阈值。对于另一示例,包括通信资产的请求和/或用户的计数的使用度量的阈值可以包括被认为未能满足阈值的最小数量(例如,上次30天内的两次使用和/或用户将不满足五次使用的阈值)。在一些实现中,可能需要满足多个阈值以避免通信资产被禁用。
[0027]在本公开的前述详细描述中,参考了构成本公开一部分的附图,并且在附图中通过图示的方式示出了本公开的示例是如何实践的。这些示例被足够详细地描述,以允许本领域普通技术人员实践本公开的示例,并且应当理解,还可以利用其他示例,并且可以进行工艺、电气和/或结构的改变,而不脱离本公开的范围。