EP3063649A1

EP3063649A1 - Initializing printers

Info

Publication number: EP3063649A1
Application number: EP13896218.8A
Authority: EP
Inventors: Nilay Shashikant SHETH; Mark A. YEARICK; Dmytro KHAYNATSKYY; Sivakumar Neelamegam KAILASAM
Original assignee: Hewlett Packard Enterprise Development LP
Current assignee: Ent Services Development Corp LP
Priority date: 2013-10-31
Filing date: 2013-10-31
Publication date: 2016-09-07
Also published as: CN106062729A; WO2015065409A1; EP3063649A4

Abstract

Initializing printers can include identifying an existence of a printer, requesting configuration details associated with the printer in response to identifying the existence of the printer, receiving configuration details from a data store, and/or initializing the printer using the received configuration details.

Description

INITIALIZING PRINTERS

Background

[0001] Business processes may be a factor in the operational success of an organization. The business processes may utilize printers to provide tangible sources of information. As such, the organization may have an interest in ensuring that the printers operate properly (e.g., as intended) from initial implementation and throughout a useful lifetime.

Brief Description of the Drawings

[0002] Figure 1 illustrates an example of an environment in which various example processes can be implemented for initializing printers according to the present disclosure.

[0003] Figure 2 illustrates a flow diagram of an example process for initializing printers according to the present disclosure.

[0004] Figure 3A illustrates a diagram of an example of a system for initializing printers according to the present disclosure.

[0005] Figure 3B illustrates a diagram of an example of a computing device for initializing printers according to the present disclosure.

[0006] Figure 4 illustrates a flow diagram of an example of a method for initializing printers according to the present disclosure. Detailed Description

[0007] An organization may employ printers to perform various aspects of its business processes. With increasing pressure on organizations, such as airlines, to improve their performance, the organizations may seek to increase efficiencies related to hardware supporting their business processes, for instance, by pursuing efficient initializing of the printers.

[0008] Printers can include parametric table (PECTAB) printers.

PECTAB printers refer to printers, such as boarding pass printers and/or bag tag printers, which rely on a parametric (e.g., parameter) table to decipher formatted data i.e. , PECTAB data. The PECTAB data can, for example, be received from a departure control system (DCS), among other locations. The DCS may act as a central depository, providing PECTAB data to one or more businesses processes within the organization, such as PECTAB data regarding particular passengers, flights, baggage, and/or luggage, etc. For instance, the DCS may provide formatted flight and/or passenger data to a boarding pass printer to generate a boarding pass. The PECTAB data associated with the PECTAB printers, may be unique for each airline, each airport, and/or for varying standards specified by a group external to the organization such as the Association of European Airlines (AEA).

Additionally, PECTAB printers may not provide monitoring capabilities, such as, monitoring traffic associated with a plurality of printers (e.g. , PECTAB printers), etc. Variations between PECTAB standards and/or a lack of monitoring capabilities, can make management (e.g., initializing) of PECTAB printers difficult, costly (e.g., time-consuming), and/or ineffective, among other difficulties.

[0009] Such difficulties can be compounded by disjointed and/or disorganized procurement of PECTAB printers by the organization. That is, organizations, such as airlines, may purchase PECTAB printers on an as needed basis and/or when funding permits, rather than purchasing (e.g., upgrading) all PECTAB printers of an organization to a particular type of PECTAB printer. As a result, there may be a plurality of types of PECTAB printers (e.g. , makes and/or models of PECTAB printers) in operation for the organization at any given time. [0010] For instance, the various types of PECTAB printers may adhere to various versions of PECTAB. For example, a particular PECTAB printer (e.g., a legacy printer) may employ a comparatively older version of PECTAB compared to a PECTAB printer employing a prevailing version (e.g., a current standard adopted by the AEA). Such a legacy printer may experience events (e.g., compatibility events with devices utilizing a comparatively newer version of PECTAB, etc.). Additionally, regardless of a version of PECTAB installed, over the course of an operational lifetime each of the plurality of PECTAB printers experiences events.

[0011] An event refers to a change in a status of a printer (e.g., a

PECTAB printer). Events can include, for example, out of paper/ink, initialized/not initialized, printing a document, receiving a print request, powering on/off a printer "plugged in" to a network, entering "ready" mode (e.g., a mode associated with a printer able to print as intended), experiencing an error (e.g. a paper jam), among other events the correspond to a change in a status of the printer. Occurrence of an event may prohibit a printer from functioning as intended (e.g. , being able to print) or signify that a printer is "ready" to be initialized, etc.

[0012] When a printer is first connected (e.g., plugged-in) to a network and/or provided power (e.g., powered on) the printer is ready to be initialized to function as intended. Initializing refers to providing data (e.g., an

initialization sequence and/or PECTAB tables) to a particular printer that results in the printer being able to function as intended (e.g. , being able to print). For example, initializing can include providing and/or storing a parametric table in memory of a printer and/or performing an initialization sequence, as described herein, among other items to initialize the printer such that the printer can function as intended. Accordingly, initializing printers to ensure proper functionality can be desirable.

[0013] However, previous approaches for initializing printers, in particular PECTAB printers, may include a manual process, for example, employing a user to manually provide various inputs to initialize a particular printer when the printer is ready to be initialized. Thus, initialization can be delayed and/or ineffective. Such inefficiencies can be compounded due to the different types of printers and/or the different versions of PECTAB (e.g., PECTAB tables) utilized by printers.

[0014] In contrast, examples of the present disclosure include methods, systems, and computer-readable and executable instructions for initializing printers. Initializing printers can include identifying an existence of a printer, requesting configuration details associated with the printer in response to identifying the existence of the printer, receiving configuration details from a data store, and/or initializing the printer using the received configuration details. Such initializing can promote consistent, efficient, and/or reliable functioning of printers, ensuring currency of software/firmware on printers, and/or verifying printer compliance with organizational policies, among other advantages.

[0015] Figure 1 illustrates an example of an environment 100 in which various example processes can be implemented for initializing printers according to the present disclosure. The environment 100 is shown to include a system 112 for initializing printers, offices 101-1 , 101-2,... , 101-O, printers

102- 1 , 102-2, 102-3, 102-4, 102-5, 102-6, 102-7, ... , 102-P, remote agents

103- 1 , 103-2, 103-3,... , 1 03-A, workstations 104-1 , 104-2, 104-3,... , 104-C, support devices 110-1 , 1 10-2,..., 1 0-G, a data store 108, and a link 106. The data store 108 can be analogous to those discussed with respect to Figures 2 and 3A. The system 1 12 can include a computing device analogous to the computing device discussed with respect to Figure 3B.

[0016] Initializing printers can be performed using a workstation, such as workstations 104-1 ,... , 1 04-C, remote agents 103-1 ,. .. , 103-A, link 106, data store 108, and/or servers, such as those described herein. Workstations

104- 1 ,... , 104-C represent computing devices that can generate/receive electronic data having browsers and/or other applications to communicate such data and/or facilitate initializing printers, among other abilities.

Examples of workstations 104-1 104-C include desktop/laptop computers, mobile phones, and/or servers, among other devices suitable for initializing printers. In some examples, each of the plurality of printers can have a respective workstation corresponding thereto.

[0017] In various examples, the workstations and/or data store(s) can be separate and distinct from the plurality of printers. As described herein, being separate and distinct refers to an environment being physically separate and/or having separate network resources (e.g., network resources to monitor traffic) with respect to each other, in this manner, a workstation can monitor (e.g. , remotely monitor) traffic from the printers 102-1 , ... , 102-P. Such monitoring of printers using a workstation that is separate and distinct from the printer can avoid difficulties associated with legacy printers the may not provide monitoring capabilities, such as, monitoring traffic associated with a plurality of printers (e.g., PECTAB printers), etc., among other advantages.

[0018] Remote agents 103-1 ,... , 103-A refer to hardware (e.g., a probe, etc.), software, and/or firmware that can communicate with the printers 02- 1 , .. . , 102-P, communicate with servers, intercept traffic, initialize the printers, and/or monitor the printers, among other abilities. Examples of remote agents include plugins (e.g., browser plugins), firmware applications, and/or downloadable software (e.g., downloadable browser instances), among other suitable remote agents for initializing printers.

[0019] In some examples, remote agents 103-1 ,... , 103-A can include a network monitoring probe (not shown) to collect traffic (e.g. , live print traffic). For example, the network monitoring probe can monitor a plurality of printing requests and/or printing responses sent via transmission control

protocol/internet protocol (TCP/IP) on a main communication path that passes through a switch. The network monitoring probe can monitor the traffic, for example, through the switch to extract traffic and/or data (e.g. , printer statuses). For example, an identify engine, such as identify engine 343 describe with respect to Figure 3A, can be coupled to the network monitoring probe (e.g., a Real User Monitor (RUM) probe), so as to receive the network traffic (e.g., live network traffic associated with a client-facing server and/or printer) collected by the network monitoring probe. Examples of the present disclosure can include one network monitoring probe or a plurality of network monitoring probes. The network traffic (e.g., print traffic including statuses and/or identifying information associated with a printer) can be collected with the network monitoring probe directly from a network device (e.g., a switch) and/or the network traffic can be mirrored to the identify engine 343.

[0020] For example, the identify engine 343 can include a network monitoring application (e.g., a port sniffer) to mirror the traffic. Traffic (e.g. , collected print traffic) that is derived from the network monitoring probe, whether by mirroring or other methodology, can be referred to as captured print traffic. Various tools (e.g., computing devices) exist to collect print traffic (e.g., TCP packets), process the captured network traffic (e.g. , for business analysis, status identification, or other use), and/or provide various reports based on the captured network traffic

[0021] The network monitoring probe and the identify engine 343 (e.g., computing device) and/or a network monitoring application can be coupled in a wired or wireless manner. The network monitoring probe and/or the network monitoring application can be a discrete computing device having a processing resource and memory resources. The network monitoring application can be an application running on a separate computing device such as a server, router, switch, printer, etc., or can be provided by another implementation.

[0022] Offices 101-1 , ... , 101-O refer to physical locations housing printers. Printers 102-1 ,... , 102-P can include parametric table (PECTAB) printers and/or non-PECTAB printers. PECTAB printers 102-1 ,... , 102-P refer to printers that utilize PECTAB to perform some or all of their respective operations (e.g. , printing, receiving data, sending data, etc.). Non-PECTAB printers refer to printers that do not utilize PECTAB to perform operations. In various examples, the printers 102-1 , ... , 102-P can include a plurality of PECTAB printers (e.g., a plurality of types of PECTAB printers). Examples of PECTAB printers can include automated ticketing and boarding (ATB) printers, boarding pass printers, and/or bag tag printers, among others.

[0023] The support devices 1 10-1 , ... , 1 10-G represent computing devices that can generate and/or receive electronic data associated with printers having browsers and/or other applications to communicate such information, among other abilities. The support devices 1 10-1 , ... , 1 10-G can include an electronic display such as a graphical user interface (GUI) 11 1 . Similarly, in some examples, the workstations 104-1 ,... , 104-C and/or servers, such as those described herein, can include an electronic display (not shown) suitable for display of electronic data.

[0024] A user interface (Ul) can include hardware components and/or computer-readable instruction components. For instance, hardware components can include input components (e.g. , a mouse, a touch screen, and a keyboard) and/or output components (e.g. , a display). An example Ul can include a GUI. A GUI can, for example, electronically represent an indication of a status (e.g., a non-initialized status) of a printer and/or an indication of a printer associated with an event (e.g., a name, type, location, make, and/or component identification number of a printer associated with an event), among other electronic representations.

[0025] An occurrence of an event, for instance, can be identified based on a performance standard and/or based upon a service level agreement (SLA), among other ways to identify an occurrence of an event. For example, an event can be based upon a change resulting in an ability to meet a performance standard (e.g., a "ready" to print/initialized status) and/or a change resulting in an inability to meet a performance standard (e.g., an "out of paper" status). Occurrences of such events can be automatically identified, for example, by a remote agent and/or by self-diagnosis of a printer

experiencing an event. However, even in the instance of a printer self- diagnosing an occurrence of an event, a remote agent can monitor traffic to facilitate identifying an indication of the printer associated with event and/or initializing printers.

[0026] Such an indication can include, for example, a location associated with a particular printer, a printer name, a printer make, a printer model, a version of firmware (e.g., a version of PECTAB) utilized by the printer, and/or a status of a printer (e.g., information pertaining to a status of the printer), among other information. Statuses can correspond to events, such as those described herein. For example, an event (e.g. , a printer running out of paper) can have a corresponding status associated with the printer (e.g., an "out of paper" status). Such a status (e.g., information that identifies a particular status) can be received from traffic. Traffic refers to network traffic (e.g. , packets) to and/or from the plurality of printers. For example, the traffic can include print requests (e.g., print requests sent to an initialized printer), printer responses (e.g., updates corresponding to the progress of a printer job), various information associated with an indication of a printer experiencing an event, initialization information, among other types of traffic. Traffic to the printer passes through a remote agent, as described herein, which can monitor the traffic, for instance, to identify an existence of and/or status of a printer.

[0027] In some examples, an indicator can be displayed by a Ul of a support device. For example, the indicator can be a numeric indicator, a textual indicator, a pop-up window, and/or a particular color (e.g., display of the color green to indicate a particular printer has a "normal"/" ready" status and/or is not indicated as associated with an event), among other possible types of indicators. Conversely, a red color can be displayed to indicate a particular printer has been associated with an event and/or is ready to be initialized. Such displays can facilitate interactions between a user and a computer (e.g. , allows a user to interact with a computer using images and/or text).

[0028] Link 106 (e.g., a network) represents a cable, wireless, fiber optic, and/or remote connection via a telecommunication fink, an infrared link, a radio frequency link, and/or other connectors or systems that provide electronic communication. That is, the link 106 can, for example, include a link to an intranet, the Internet, or a combination of both, among other communication interfaces. The link 106 can also include intermediate proxies, for example, an intermediate proxy server, routers, switches, load balancers, and the like.

[0029] For instance, the link 106 can include an intermediate server such as an asynchronous protocol server, for example, a java-based server such as an extensible messaging and presence protocol (XMPP) server (not shown) a synchronous server, and/or an application server (not shown). The asynchronous protocol server can communicate by an asynchronous protocol with a remote agent, such as those described herein, the application server, and/or a data store (e.g., data store 108) to promote initializing printers. For instance, a status can be provided (e.g., by the remote agent) to a java-based server (e.g., a XMPP server and/or a Java 2 Platform Enterprise Edition (J2EE) server) capable of storing a status (e.g., an identified current status) of the printer. Such a status can indicate a printer is ready to be initialized (e.g., has been "plugged-in" to a network and has not been initialized and/or is not initialized with configuration details associated with a desired version of PECTAB). However, the present disclosure is not so limited. That is, link 106 can represent a physical connection between the workstations 104-1 , ... , 104- C and the support devices 1 10-1 ,..., 1 10-G to communicate instructions (e.g., instructions to initialize a printer) between the support devices, the

intermediate server, the application server, and/or the data store 108.

[0030] In some examples, link 106 can represent a common

abstraction layer. That is, the printer 102-1 ,... , 102-P, the remote agents 103- , .. . , 103-A , the workstations 104-1 , ... , 104-C, and/or the support devices 1 10-1 ,..., 1 10-G can be included on a common abstraction language. Such commonality can promote monitoring and/or initializing of printers, as described herein.

[0031] The system 1 12 for initializing printers can represent different combinations of hardware and instructions to initialize printers. The system 1 12 for initializing printers can include a computing device (not shown), for instance, computing device 355 as discussed with respect to Figure 3B.

[0032] Figure 2 illustrates a flow diagram 215 of an example process for initializing printers according to the present disclosure. Printer 201 , remote agent 203, workstation 204, link 206, and/or data store 208 can be analogous to those discussed with respect to Figure 1.

[0033] Flow diagram 21 5 includes a plurality of representations (e.g., arrow) 220-1 , 220-2, 220-3, 220-4, 220-5, 220-6, 220-7, 220-8, 220-9, 220-N representing of various aspects of initializing printers. Arrow 220-1 represents an occurrence of an event, as described herein, such as powering on/off a printer 'plugged in' to a network. For instance, the printer can transmit information upon powering on the printer 'plugged in' to a network.

[0034] Arrow 220-2 represents identifying an existence of a printer 201 . Existence of a printer (e.g. , a PECTAB printer) can, for example, be identified based on information transmitted by the printer to a remote agent, data store and/or server, etc. , as represented at arrow 220-3, among other ways to identify the existence of a printer. Information (e.g., packets) can pass along a path that includes the remote agent and/or the server, among other network devices such as routers, switches, etc. , and/or a data store, such as those described herein.

[0035] Identifying the existence of the printer 201 , as represented by arrow 220-2, can include the remote agent 203 sending information (e.g., commands) to the printer to discover identifying information associated with the printer. For example, the identifying information can include a name and/or version of PECTAB utilized by the printer 201 , among other information. The information sent by the remote agent can originate from the remote agent itself and/or be received by the remote agent form another device, such as server 217.

That is, in some examples, Information can be sent, for example, from a server (e.g., server 217 as illustrated in Figure 2) via a remote agent 203 to the printer 201 , among other ways to enable a printer to receive information (e.g., a discovery command).

[0036] Arrow 220-3 represents the printer 201 response to receipt of information (e.g., a command, etc.) sent at arrow 220-2. Such a response can include information such as the name and/or the version of PECTAB utilized by the printer 201 , among other information.

[0037] The information in the printer response represented by arrow

220-3 can enable a remote agent to transmit a request to a server 2 7 as represented at arrow 220-4. The request, such as those described herein, can include a request for configuration details (e.g., a response configuration including configuration details). The configuration details can include an initialization sequence and/or a parametric table, among other items. An initialization sequence refers to ordered actions and/or instructions that result in a printer being initialized. The initialization sequence can be specific to a version of firmware and/or a type of printer, etc.

[0038] The request for configuration details can be provided via a synchronous protocol (e.g., to a synchronous server) or via a synchronous request (e.g., to a synchronous server). That is, servers, as described herein in greater detail, can include synchronous servers, for example, hypertext transfer protocol (HTTP) servers and/or a synchronous servers such as an extensible messaging and presence protocol (XMPP) server, among various other types of servers such as those described herein, capable of receiving such a request. For example, the request can be received by a server 217. Server 217 can respond, as represented at arrow 220-9, and/or can query a data store such as data store 208, as represented by arrow 220-5. For instance, as represented by arrow 220-5, the server 217 can query the data store 208 for a response configuration (e.g., a response configuration corresponding to the requested response configuration) and/or configuration details, among other items.

[0039] As represented by arrow 220-6, the data store 208 can respond to the server 2 7. Such a response can include a response configuration, for instance, a response configuration can be associated with (e.g., matching) a version of firmware, such as, a version of firmware corresponding to the printer 201. In such a scenario, the method can proceed to arrow 220-9, as described herein.

[0040] However, when the response represented by arrow 220-6 does not include a response configuration the server can again query the data store 208 for another response configuration present in the data store that corresponds to a different version of firmware, as illustrated at arrow 220-7. That is, a response configuration associated with the default version of firmware i.e., a default response configuration, refers to a response

configuration associated with a version of firmware other than an identified version of firmware (e.g., identified as corresponding to a particular printer). The default response configuration can be received in various circumstances; for instance, when the data store 208 does not contain the response configuration associated with the identified version of firmware and/or when the version of firmware version of firmware corresponding to the printer has not been identified (e.g., identification has not yet occurred and/or is not possible, etc.). In some examples, the default configuration can refer to a comparatively older version of firmware, for instance, the next most recent version of firmware compared to an identified version of firmware

corresponding to the PECTAB printer.

[0041] The server 217 can transmit the response configuration received from the data store 208, as described at arrow 220-6 and/or arrow 220-8, to the remote agent 203, as represented by arrow 220-9. As represented by arrow 220-N, the remote agent 203 can initialize the printer 201 using the received configuration details included within a response configuration. While the plurality of representations 220-1 220-N are sequentially numbered, the various aspects of initializing printers can occur in an order other than that depicted, can be combined, and/or can include more or less representations than those depicted, among other variations. Additionally, while the majority of representations shown in Figure 2 are represented by a unidirectional arrow the representations and/or information/processes represented by the arrows can flow in either direction and/or in both directions (e.g.,

simultaneously and/or at different times) to promote initializing printers.

[0042] Figure 3A illustrates a diagram of an example of a system 340 for initializing printers according to the present disclosure. The system 340 can include a data store 308 (e.g., analogous to data store 108 as referenced in Figure 1), a initializing system 342, and/or a number of engines. The initializing system 342 can be in communication with the data store 308. The initializing system 342 can include a number of engines (e.g., identify engine 343, request engine 344, receive engine 346, etc.). The initializing system 342 can include additional or fewer engines than illustrated to perform the various functions described herein.

[0043] The number of engines can include a combination of hardware and programming to perform a number of functions described herein (e.g., a receive engine to receive a response configuration including configuration details to initialize the PECTAB printer, etc.). Each of the engines can include hardware or a combination of hardware and programming designated or designed to execute a module (e.g., a particular module). The programming can include instructions (e.g., software, firmware, etc.) stored in a memory resource (e.g., computer-readable medium) as well as a hard-wired program (e.g., logic).

[0044] The identify engine 343 can identify engine to identify, from traffic associated with a plurality of parametric table (PECTAB) printers monitored by remote agents, an existence of a PECTAB printer, where identifying includes identifying a version of firmware corresponding to the PECTAB printer, such as those described herein. Identifying an existence refers to identifying a presence, a current status, and/or identification information associated with a PECTAB printer. In some examples, the identify engine 343 can identify the existence of the PECTAB printer from traffic associated with a plurality of types of PECTAB printers. For example, the plurality of printers can, in some examples, include only PECTAB printers and not any non-PECTAB printers. [0045] A current status refers to a comparatively most recent status (e.g., most recent information) identified by the identify engine 343. The current status can be stored in an intermediate sever, an application server, and/or a data store (e.g. , data store 308). In some examples, storing the current status can include replacing the previous status (e.g., a status immediately prior to the current status) with the current status. In some examples, the current status can be stored along with a plurality of other status, for instance, in chronological order based on a time of identification associated with each of the respective statuses.

[0046] Identifying information refers to information that can identify a particular printer and/or particular aspects of the printer. Identifying

information can include information pertaining to a type (e.g., a make and/or model) of a printer, a location associated with a printer, a name, and/or a component identifier, among other identifying information associated with a printer. The identifying information can include information providing a timeframe (e.g., a time such as day, month, etc.) associated with identification of a status and/or initialization of a printer (e.g., a time associated with originally initializing the printer). Such a timeframe can promote the chronological ordering of statues described above and/or periodically reinitializing the printer. Advantageously, reinitializing the printer in

accordance with a comparatively newer PECTAB table(s)) and/or

comparatively newer version of PECTAB can enable the printer to implement additional features and/or improve efficiencies of the printer, among other advantages.

[0047] The identify engine 343 can include and/or can be in

communication with a monitoring engine (not shown) that can monitor traffic associated with the plurality of PECTAB printers, among other monitoring capabilities. In some examples, the plurality of PECTAB printers can include a plurality of versions of firmware. For instance, each of the PECTAB printers can include a respective version of firmware installed thereon. Consequently, the PECTAB printers may have a single version of firmware installed on each of the PECTAB printers.

[0048] Identifying, can in some examples, include implementing the identify engine 343 to identify information that identifies a version of firmware corresponding to the PECTAB printer (e.g., the single version of firmware installed on the PECTAB printer). The identify engine 343 can identify the existence of the PECTAB printer and/or an indication of a PECTAB printer associated with an event upon request (e.g., a request initiated by an information technology (IT) administrator) and/or automatically upon an occurrence of an event (e.g., immediately following occurrence of an event).

[0049] The request engine 344 can request configuration details particular to the version of firmware (e.g. , the version of firmware identified by the identify engine 343). In some examples, the request engine 344 can request the configuration details without a user input request. For example, the request engine 344 can request the configuration details automatically upon receipt of the version from the identify engine 343.

[0050] The receive engine 346 can receive a response configuration including configuration details to initialize the PECTAB printer. For instance, a response configuration can be received from a data store, as described with respect to Figure 2. For example, the response configuration can, in some examples, be received from a data store using a synchronous protocol, such as HTTP, among other synchronous protocols. The printer can, in some examples, be initialized, for example by a initialization engine (not shown), using a received configuration details including a parametric table and/or an initialization sequence.

[0051] As described with respect to Figure 2, the response

configuration can, in some examples, be associated with the identified version of firmware (identified by the identify engine 343). In some examples, response configuration can be associated with a default version of firmware.

[0052] In some examples, a display engine (not shown) can provide a notification the PECTAB printer has been initialized using the response configuration associated with a default version of firmware. Similarly, the display engine can provide an indication a printer has been initialized with a response configuration associated with a identified version of firmware (e.g., initialized using configuration details that match the identified version).

However, providing a notification in response to initializing using a response configuration associated with the default version of firmware can enable subsequent reinitializing with another response configuration (e.g., a response configuration associated with a comparatively newer version of firmware), among other advantages.

[0053] In some examples, the display engine can cause a display (e.g. , cause the display without a user request/user input), for example, a display of a status (e.g., initialized) associated with a printer. In various examples, the display engine can cause the display, via the GUI, of the information pertaining to a status (e.g., a current status) of the PECTAB printer and/or the corresponding identifying information associated with the PECTAB printer.

[0054] In some examples, a display engine can provide a notification the PECTAB printer has been initialized using the response configuration associated with a default version of firmware. The notification can include email and/or displaying an indication, such as those described herein. Such a display, can lead to a remediation action, such as reinitializing the printer, ensuring power is supplied to the printer, upgrading firmware of the printer, supplying ink/paper to the printer, among other possible remediations to restore the printer to a non-event (e.g., fully functional) status. For instance, in some examples, the remediation can include reinitializing a PECTAB printer associated with an event.

[0055] Figure 3B illustrates a diagram of an example of a computing device for initializing printers according to the present disclosure. The computing device 355 can utilize software, hardware, firmware, and/or logic to perform a number of functions described herein.

[0056] For example, the computing device 355 can be a combination of hardware and instructions for initializing printers. The hardware, for example can include a processing resource 360 and/or a memory resource 364 (e.g. , computer-readable medium (CRM), data store, etc.) A processing resource 360, as used herein, can include a number of processors capable of executing instructions stored by a memory resource 364. Processing resource 360 can be integrated in a single device or distributed across multiple devices. The instructions (e.g., computer-readable instructions (CRI)) can include instructions stored on the memory resource 364 and executable by the processing resource 360 to implement a desired function (e.g., initialize a printer, etc.). [0057] The memory resource 364 can be in communication with a processing resource 360. A memory resource 364, as used herein, can include a number of memory components capable of storing instructions that can be executed by processing resource 360. Such memory resource 364 can be a non-transitory CRM. Memory resource 364 can be integrated in a single device or distributed across multiple devices. Further, memory resource 364 can be fully or partially integrated in the same device as processing resource 360 or it can be separate but accessible to that device and processing resource 360. Thus, it is noted that the computing device 355 can be implemented on a support device and/or a collection of support devices, on a workstation and/or a collection of workstations, and/or on a combination of the support devices and the workstations.

[0058] The memory resource 364 can be in communication with the processing resource 360 via a communication link (e.g., path) 362. The communication link 362 can be local or remote to a computing device associated with the processing resource 360. Examples of a local

communication link 362 can include an electronic bus internal to a computing device where the memory resource 364 is one of volatile, non-volatile, fixed, and/or removable storage medium in communication with the processing resource 360 via the electronic bus.

[0059] The memory resource 364 can include a number of modules such as an identify module 366, a request module 368, a receive module 370, and a initialize module 372, etc. The number of modules 366, 368, 370, 372 can include CRI that when executed by the processing resource 360 can perform a number of functions. The number of modules 366, 368, 370, 372 can be sub-modules of other modules. For example, the identify module 366 and the request module 368 can be sub-modules and/or contained within the same computing device. In another example, the number of modules 366, 368, 370, 372 can comprise individual modules at separate and distinct locations (e.g., CRM, etc.).

[0060] Each of the number of modules 366, 368, 370, 372 can include instructions that when executed by the processing resource 360 can function as a corresponding engine, including those as described herein. For example, the identify module 366 can include instructions that when executed by the processing resource 360 can function as the identify engine 343, for instance, to identify an existence of a printer, in some examples, identify module 366 can an existence of a parametric table (PECTAB) printer.

[0061] A request module 368 can include instructions that when executed by the processing resource 360 can function as a request engine 344 to request configuration details associated with the printer in response to identifying the existence of the printer. The receive module 370 can include instructions that when executed by the processing resource 360 can function as the receive engine 346 to receive configuration details from a data store.

[0062] The initialize module 368 can include instructions that when executed by the processing resource 360 can function as a initialize engine (not shown) to initialize the printer using the received configuration details. The initialize module 368 can initialize a printer using an initialization sequence and/or a parametric table, as described herein.

[0063] Figure 4 illustrates a flow diagram of an example of a method for initializing printers according to the present disclosure. As shown at block 484, in various examples, the method 480 can include storing a plurality of response configurations in a data store (e.g. , data store 308 as illustrated in Figure 3). Storing can include providing data (e.g., a response configuration) and/or maintaining data in a data store. In some examples, the method 480 can include storing a plurality of response configuration in a data store that is separate and distinct, as described herein, from a PECTAB printer.

[0064] As shown at block 486, the method can include identifying an existence of a PECTAB printer, where identifying can include identifying a version of firmware corresponding to the PECTAB printer. The existence can be identified from the monitored traffic, as described herein. In some examples, the method can include identifying an existence of the PECTAB printer in response to (e.g., after) storing the plurality of response

configurations, as described at 484.

[0065] In various examples, requesting configuration details to initialize the PECTAB printer having the identified version of firmware, as shown at block 488. The identified version can correspond to the version identified as shown at block 486. Requesting configuration details can include requesting a response configuration including configuration details. [0066] The method 480, as shown a block 490, can include receiving a response configuration including configuration details to initialize the PECTAB printer from the plurality of response configurations stored in the data store. The received configuration can correspond (e.g., be identical to) the requested configuration) and/or can correspond to a default configuration, as described herein. As shown at block 492, the method 480 can include initializing the PECTAB printer using the received configuration details.

[0067] In some examples, the method 480 can include displaying an electronic representation indicative of an initialized status of the PECTAB printer. Such a display can be displayed via a user interface (Ul). The Ul (not shown) can be displayed via a display of a support device upon, for example, a status of a printer can be displayed in response to an occurrence of an event, in response to initializing a printer, as described herein, and/or upon receipt of an indication of a printer associated with the event. The Ul can include a plurality of electronic representations (not shown), a plurality of names and/or a plurality of statuses corresponding to a plurality of printers, among other displayed items included in the Ul. For example, a Ul can simultaneously display of a particular total number of printers located at a various locations, however, the present disclosure is not so limited. That is, a total number of the plurality of printers, a number of locations, a naming convention (e.g., a legend), a name (e.g., a location as a name), and/or a respective types of statuses displayed are not so limited. Rather, the displayed items (e.g. , the a plurality of electronic representations, etc.) can be varied and/or include more of less displayed items to promote initializing printers, as described herein

[0068] The plurality of electronic representations, the plurality of names, and/or a plurality of statuses can each have a functionality (e.g., a respective functionality) associated therewith. For example, selection of an electronic representation may cause the Ul to perform an action (e.g., display a drop down menu, display a free text area, display a drill down menu, and/or cause an application utilizing the Ul to perform a function). That is, the plurality of electronic representations, the plurality of names, and/or a plurality of statuses can facilitate a user to interact with the Ul (e.g., provide an input to cause the Ul to perform the functionality). For example, displaying the electronic representation can include providing, via an asynchronous message protocol, the indication to a graphical user interface (GUI)

[0069] In some examples, displaying can include causing a

simultaneous display of a plurality of electronic representations, indicative of respective statuses associated with each of the plurality of PECTAB printers, including an electronic representation indicative of the received information of the PECTAB printer. A simultaneous display refers to displaying the statuses (e.g., current statuses) of a plurality of PECTAB printers at the same time via an individual device (e.g., a single GUI of the individual device). An example of such a simultaneous display is detailed with respect to Figure 2 herein.

[0070] Causing can include executing instructions stored in memory to directly cause a support device to display, for example, electronic

representations, indicative of respective statuses associated with each of the plurality of PECTAB printers and/or to communicate data with an expectation that it be processed by another device to cause the support device to display the electronic representations, indicative of respective statuses associated with each of the plurality of PECTAB printers. Similarly, blocks 484, 486, 488, 490, 492 can include executing instructions, for example, as described with regard to the engines herein, stored in memory to perform the examples of the method described therein.

[0071] In some examples, the method 480 can include remediating the event based upon the display of the electronic representation indicative of the status of a printer. Remediation refers to restoration of a non-event status (e.g., a status of a printer in compliance with an SL.A) and initializing (e.g., reinitializing) a printer to ensure the printer can function as intended.

[0072] As used herein, "logic" is an alternative or additional processing resource to execute the actions and/or functions, etc., described herein, which includes hardware (e.g., various forms of transistor logic, application specific integrated circuits (ASICs), etc.), as opposed to computer executable instructions (e.g., software, firmware, etc.) stored in memory and executable by a processing resource. The figures herein follow a numbering convention in which the first digit or digits correspond to the drawing figure number and the remaining digits identify an element or component in the drawing. Similar elements or components between different figures may be identified by the use of similar digits. For example, 08 may reference element "08" in Figure , and a similar element may be referenced as 308 in Figure 3.

[0073] In the detailed description of the present 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 present disclosure can be practiced. These examples are described in sufficient detail to enable those of ordinary skill in the art to practice the examples of this disclosure, and it is to be understood that other examples can be utilized and that process, electrical, and/or structural changes can be made without departing from the scope of the present disclosure.

[0074] As will be appreciated, elements shown in the various examples herein can be added, exchanged, and/or eliminated so as to provide a number of additional examples of the present disclosure. In addition, the proportion and the relative scale of the elements provided in the figures are intended to illustrate the examples of the present disclosure, and should not be taken in a limiting sense. As used herein, "a number of" an element and/or feature can refer to one or more of such elements and/or features. In addition, "for example" and similar phrasing is intended to mean, "by way of example and not by way of limitation".

[0075] The specification examples provide a description of the applications and use of the system and method of the present disclosure. Since many examples can be made without departing from the spirit and scope of the system and method of the present disclosure, this specification sets forth some of the many possible example configurations and

implementations.

Claims

What is claimed:

1 . A non-transitory computer-readable medium storing instructions executable by a processing resource to:

identify an existence of a printer;

request configuration details associated with the printer in response to identifying the existence of the printer;

receive configuration details from a data store; and

initialize the printer using the received configuration details.

2. The medium of claim 1 , wherein the instructions executable to identify include instructions executable to identify the existence of a parametric table (PECTAB) printer.

3. The medium of claim 2, wherein the configuration details include an initialization sequence, and wherein the instructions executable to initialize include instructions executable to initialize the PECTAB printer using the initialization sequence.

4. The medium of claim 3, wherein the configuration details include a parametric table, and wherein the instructions executable to initialize include instructions executable to initialize the PECTAB printer using the parametric table.

5. The medium of claim 1 , wherein the instructions executable to receive include instructions executable to receive the configuration details from a data store using a synchronous protocol.

6. A system, comprising a processing resource in communication with a non-transitory computer-readable medium having instructions executable by the processing resource to implement:

an identify engine to identify, from traffic associated with a plurality of parametric table (PECTAB) printers monitored by remote agents, an existence of a PECTAB printer, wherein identifying includes identifying a version of firmware corresponding to the PECTAB printer; a request engine to request configuration details particular to the version of firmware; and

a receive engine to receive a response configuration including configuration details to initialize the PECTAB printer.

7. The system of claim 6, wherein the response configuration is associated with the identified version of firmware.

8. The system of claim 6, wherein the response configuration is associated with a default version of firmware.

9. The system of claim 8, including instructions executable to implement a display engine to provide a notification the PECTAB printer has been initialized using the response configuration associated with a default version of firmware.

10. The system of claim 6, wherein the instructions are executable to implement the identify engine to an identify engine to identify the existence of the PECTAB printer from traffic associated with a plurality of types of

PECTAB printers.

1 1 . The system of claim 6, including instructions executable to implement the receive engine to receive the response configuration without a user input.

12. The system of claim 6, wherein the instructions include instructions executable to implement a display engine to display, via a graphical user interface (GU I), a status of the PECTAB printer provided via the

asynchronous message protocol.

13. A method for initializing printers, comprising:

storing a plurality of response configurations in a data store;

identifying an existence of a PECTAB printer, wherein identifying includes identifying a version of firmware corresponding to the PECTAB printer; requesting configuration details to initialize the PECTAB printer having the identified version of firmware;

receiving a response configuration including configuration details to initialize the PECTAB printer from the plurality of response configurations stored in the data store; and

initializing the PECTAB printer using the received configuration details.

14. The method of claim 13, including displaying an electronic

representation indicative of an initialized status of the PECTAB printer.

15. The method of claim 14, wherein displaying the electronic

representation includes providing, via an asynchronous message protocol, an indication of the electronic representation to a graphical user interface (GUI).