JP2008134933A - Network card - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To achieve development without being conscious of the model difference of every printer controller in preparing an application program. <P>SOLUTION: The model difference API absorption layer of a mounted printer controller is mounted on an API provided to an application program. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to a network card attached to a printer apparatus.

  In recent years, with the widespread use of the Internet, a form in which a printing apparatus is used in a network has become common. Usually, high-priced machines such as high-speed machines and color machines tend to have a built-in network interface. However, in the case of a low-priced monochrome machine, the network interface is not included in the main unit. In general, the network card module is supplied separately.

  In this case, the printing apparatus main body and the network card module are intelligent forms each having a CPU. Further, the normal network card module side is provided with a print server function for performing overall control of various print services via the network. In addition, the printing apparatus and the network card module communicate with each other via a connection interface to implement a desired service.

  This, on the contrary, makes it possible to drive heavy network services to the network card module, relatively lowering the CPU and peripheral performance of the printing apparatus main body, and reducing the cost of the printing apparatus main body.

  The conventional network interface only needs to be able to transmit print data as typified by LPR (RFC1179), for example. Recently, there is a growing need for information management for printing apparatuses, and various means are provided as additional techniques.

  The simplest example is a form in which information management data (job control language = Job Language) is added to a port for transmitting print data. Since the job control language shares a port for sending print data, it is not necessary to increase the service port and is relatively easy to implement. However, if a large amount of data is transmitted during reception of print data, the port is occupied, and there is a problem that the exchange of information management data is stopped. In addition, in the case of a one-way connection such as the LPR protocol in a network, there is a disadvantage that information cannot be acquired in the first place.

  As the next method, there is a method using SNMP / MIB (RFC1157). In this method, a dedicated port for data transmission / reception is used, and the standard SNMP (Simple Network Management Protocol) is used. However, this method requires proprietary development of a dedicated client program that receives SNMP and provides a UI. In addition, since this method is a protocol for exchanging simple information in the first place, only simple databases such as numbers and character strings can be provided. As a result, there is a problem that information that constitutes the UI, such as a bitmap image indicating the configuration of the device, must be owned by the client program, and the client program must correspond to the model accordingly.

  More recently, methods using the HTTP protocol (RFC1945, RFC2616) are becoming mainstream. According to this method, an HTTP service is provided in the network card module, and WEB contents such as HTML data related to device information and bitmap images are provided. Further, if the client displays the WEB content on the GUI using a general WEB browser and enables the operation, the same effect can be obtained without providing a client program. In the conventional method, the client program needs to manage information (message character strings, bitmap images) unique to a wide variety of devices. It is the most suitable way to provide.

  However, any of the above-mentioned means is a means for providing a static function incorporated in the network card module in advance, and the function itself is added later, or the control method by the incorporated function is changed. A dynamic service could not be added.

  Therefore, recently, a platform technology has been proposed that enables an application program module created using the Java (registered trademark) language to operate on a Java (registered trademark) virtual machine mounted on an embedded device. By using this technology, it has become possible to add new functions to a device afterwards in an embedded device such as a conventional printing apparatus.

  The Java (registered trademark) virtual machine described above has an application program interface (API) for providing various functions necessary for controlling an embedded device, including a network communication function. Therefore, application program modules created in the Java (registered trademark) language call these APIs to control embedded devices and process requests from host computers connected via a network.

Also, some conventional technologies provide a Java (registered trademark) development environment that runs on a PC in order to provide an environment that enables more efficient development of Java (registered trademark) applications. . (For example, refer to Patent Document 1.)
JP 2005-038010 A

  The API provided on the Java (registered trademark) virtual machine includes functions necessary for network communication, and is usually implemented on a network card module in order to share a basic module for processing a network communication protocol. It is a function.

  However, for these APIs, the information that can be acquired may differ depending on the function of the printing apparatus main body in which the network card module is mounted. For this reason, when trying to create an application program in the Java (registered trademark) language, it is necessary to create it in consideration of the functions of the installed printing device, and it is necessary to develop a common application program that runs on multiple printing devices. It was hindering.

The present invention has been made in view of the above problems,
A network card equipped with a CPU separate from the printing device, attachable to the printing device main body,
Means for allowing an application program operable on a virtual machine included in the network card to be added from the client to the network card;
A virtual machine capable of operating an application program for controlling the printing apparatus and controlling communication with the client;
When executing an application program interface that can be used from an application program, a model difference absorbing unit that determines a model according to a printing device on which a network card is mounted and performs processing according to the model;
And information changing means for changing the information acquired by the model difference absorbing means to information corresponding to the application program interface.

Furthermore, a network card comprising a CPU separate from the printing apparatus, which can be attached to the printing apparatus body,
In the printing apparatus, when an application program interface that can be used by an application program is executed, the printing apparatus is configured to identify a model of the printing apparatus main body.

Furthermore, a network card comprising a CPU separate from the printing apparatus, which can be attached to the printing apparatus body,
And means for specifying the model of the printing apparatus main body when the power is turned on.

Furthermore, a network card comprising a CPU separate from the printing apparatus, which can be attached to the printing apparatus body,
When the model of the printing apparatus main body is unknown, it is composed of model difference absorbing means for performing processing when it is identified as an unknown model.

  According to the present invention, for the API provided to the application program, the model difference API absorption layer of the installed printer controller is mounted. This makes it possible to develop an application program without being aware of the model differences for each printer controller.

(Example 1)
FIG. 1 is a block diagram illustrating a hardware configuration of a printing system according to an embodiment of the present invention. Reference numeral 1000 denotes a printer, which is mainly composed of devices that control different control systems, including a network printer server 1500 and a printer controller 1600. In the network print server 1500, reference numeral 1 denotes a network print server CPU. The network print server CPU operates based on a control program stored in the rewritable Flash ROM 3. Further, it communicates with a plurality of external devices (not shown) such as a host computer connected to a local area network (LAN2000) via a network controller (LANC5) connected to the system bus 4. For communication, a predetermined network communication protocol is used to comprehensively control various data transmission / reception requests such as print data and printer control commands sent from the external device. Then, appropriate data transfer control is performed for the printer controller 1501 connected via the expansion interface controller (EXPC7).

  The RAM 2 is used as a temporary storage area such as the main memory and work area of the CPU 1.

  The LED 6 is used as a display unit indicating the operation state of the network print server. For example, the electrical connection state (LINK) between the network controller (LANC5) and the local area network (LAN2000) is displayed. Alternatively, various operation states such as the network communication mode (10Base, 100Base, full duplex, half duplex) can be indicated by the blinking pattern and color of the LED.

  Further, the expansion interface 17 that connects the network print server 1500 and the printer controller 1501 is configured by a connector (not shown). Therefore, only the network print server 1500 can be attached and detached, and the network print server 1500 can be attached to another printer 1000 having the same configuration.

  In the printer controller 1600, 8 is a printer controller CPU. The printer controller CPU operates based on a control program or the like stored in the ROM 9 or a control program or resource data (resource information) stored in the external memory 10 connected via the disk controller (DKC 15). Further, it comprehensively controls access to various devices connected to the system bus 11. Further, output image information is generated by the raster controller 12 based on print data received from the network print server 1500 connected via the expansion interface controller (EXPC 13), and an image signal is output to the print engine 16.

  Reference numeral 14 denotes a RAM that functions as a main memory, a work area, and the like of the CPU 8, and is configured so that the memory capacity can be expanded by an optional RAM connected to an expansion port (not shown).

  Reference numeral 18 denotes an operation panel (operation unit) which is provided with buttons for performing operations such as setting the operation mode of the printer 1000 and canceling print data, and a display unit such as a liquid crystal panel and an LED indicating the operation state of the printer 1000. Yes.

  The printer engine 16 shown in the figure uses a known printing technology, and examples of suitable implementation systems include an electrophotographic system (laser beam system), an ink jet system, and a sublimation method (thermal transfer) system. .

  FIG. 2 is a block diagram illustrating a software configuration in a control program stored in each storage device of the network print server 1500 / printer controller 1600, which is a control device in the printer 1000 in the printing system suitable for the embodiment of the present invention. It is.

  Each control program is analyzed and processed by the CPU of each control device.

  An operating system 1501 controls basic data input / output control of the network print server 1500. Further, the operating system 1501 includes a file system 1505, an extended interface driver 1506, and a network interface driver 1507.

  The file system 1505 performs input / output control with the program / data storage unit 9. The extension interface driver 1506 performs communication control via the printer controller 1600 and the extension interface 17. The network interface driver 1507 communicates with an external device such as a host computer (not shown) via a local area network (LAN2000) communication medium.

  Reference numeral 1502 denotes an application program interface (API). The API provides a user application 1503 that runs on the network print server 1500. Furthermore, various functions of the operating system are provided to application programs such as a management application for registering and managing the printer 1000 and user applications.

  The functions provided by the application program interface 1502 include the following APIs.

  A data transfer API that provides a print data transmission / reception function, and a resource control API that controls input / output of resource data such as bitmap images and display messages.

  A printer control API that controls the restart of the printer 1000, initialization of setting values, and settings. A job control API that controls cancellation of print jobs and reprint instructions. Print server control API for restarting the network print server 1500, initializing and setting values, and starting, registering, and deleting application programs. A hard disk control API for controlling writing / reading to / from the hard disk drive, a panel API for controlling switching of the operation panel display of the printing apparatus, and the like. These APIs include those having different availability and information that can be acquired depending on the function of the printer controller 1600 connected to the network print server 1500.

  Reference numeral 1512 denotes a model difference API absorption layer positioned above the above-mentioned various APIs, which is a middleware layer for absorbing functional differences between various APIs caused by functional differences between the printer controller 1600 connected to the network print server 1500. is there.

  Reference numeral 1601 denotes an operating system that controls various processing controls of the printer controller 1600. There, the printer engine control unit 1603 for controlling communication with the print engine and model-dependent resources such as bitmap images and error messages referenced from the network print server 1500 are included. Furthermore, a file system 1604 for controlling input / output with a model-dependent resource / program storage unit that stores a model-dependent application program or the like operating on the network print server is included.

  Reference numeral 1602 denotes an expansion interface control unit, which controls communication with the network print server 1500 via the expansion interface 17. The extended interface control unit further includes a data transfer logical interface that controls input / output of print data for each control type. Further, a resource control logic interface for controlling input / output of various data stored in the model-dependent resource / program storage unit 9 and a printer control logic interface for controlling restart of the printer 1000, initialization of setting values, setting, and the like are provided. . In addition, a job control logical interface for controlling cancellation of a print job, reprint instruction, and the like is provided. Further, the command requested from the network print server 1500 is transferred to the operating system 1601 via each logical interface, and the processing result is returned to the network print server 1500.

  FIG. 3 is a description example of an application program operating on the network print server 1500, and shows a description example in Java (registered trademark) language as a preferred example of the present invention. A line indicated by 301 in FIG. 3 is an example of calling the data transfer API described in FIG. In the figure, “printer.outdata (“ Test ”)” is a data transfer API, and here is a command to print text data “Test” as print data from the print engine via the printer controller. The processing result is stored in "result" as a numeric type.

  A line indicated by 302 in FIG. 3 indicates a standard output destination of the processing result indicated by the line 301. For example, it is a description example of a command for converting a text message into an LCD display part of the operation panel 17 of the printer 1000 or an application and displaying it on a browser display part of a host computer that is a caller.

  FIG. 4 is a flowchart showing an embodiment when the user application 1509 according to the present invention executes an API provided by the model difference API absorption layer 1512.

  In S401, the user application executes the API (XXX). When API (XXX) is executed in S401, the model difference API absorption layer identifies the model of the printer controller 1501 in which the network print server 1500 is mounted in S402. The specifying means is not particularly described, but various means such as using a controller name or a printer product name can be considered. When the model is specified in S402, it is determined whether or not the printer controller corresponds to A in S403. If Yes, the process proceeds to S404, and processing corresponding to printer A is executed for API (XXX). If No, the process proceeds to S405, and it is determined whether or not the printer controller corresponds to B. If Yes, the process proceeds to S406, and processing corresponding to printer B is executed for API (XXX). In the case of No, it is determined that the printer is not a corresponding printer, and in S407, it is executed as a process for other general printers.

  In the present embodiment, the processing for the printer A and the printer B is described, but the type of the printer is not limited thereto.

  After executing the process for each printer, the result of each process is replied to the application in S408, and the process ends.

(Example 2)
FIGS. 5 and 6 are flowcharts showing an embodiment when the user application 1509 according to the present invention executes an API provided by the model difference API absorption layer 1512.

  FIG. 5 is a sequence diagram for identifying the installed printer controller 1501 in the model difference API absorption layer when the power is turned on.

  When the apparatus is turned on in S501, the model difference API absorption layer identifies the model of the printer controller 1501 in which the network print server 1500 is mounted in S502. The specifying means is not particularly described, but various means such as using a controller name or a printer product name can be considered. When the model is specified in S502, the specified model information is stored in the internal memory in S503.

  FIG. 6 is a flowchart showing an embodiment when the user application 1509 according to the present invention executes an API provided by the model difference API absorption layer 1512.

  In S601, the user application executes API (XXX). When API (XXX) is executed in S601, the model difference API absorption layer acquires the model information of the printer controller 1501 in which the network print server 1500 is mounted from the internal memory in S602. When the model is specified in S602, it is determined whether or not the printer controller corresponds to A in S603. If Yes, the process proceeds to S604, and processing corresponding to printer A is executed for API (XXX). If No, the process proceeds to S605, and it is determined whether or not the printer controller corresponds to B. In the case of Yes, the process proceeds to S606, and processing corresponding to the printer B is executed for API (XXX). In the case of No, it is determined that the printer is not a corresponding printer, and in S607, it is executed as a process for other general printers.

  In the present embodiment, the processing for the printer A and the printer B is described, but the type of the printer is not limited thereto.

  After executing the process for each printer, the result of each process is replied to the application in S608, and the process ends.

1 is a block diagram of a hardware configuration of a printing system according to an embodiment of the present invention. FIG. 2 is a block diagram of a printing system software configuration according to the embodiment of the present invention. The example of a source code description of the application program in this invention. 10 is a flowchart showing an embodiment when a user application 1509 according to the present invention executes an API provided by a model difference API absorption layer 1512; The sequence which identifies the printer controller 1501 with which the model difference API absorption layer at the time of power activation concerning this invention is mounted | worn. 10 is a flowchart showing an embodiment when a user application 1509 according to the present invention executes an API provided by a model difference API absorption layer 1512;

Explanation of symbols

1000 Printer 1500 Network Print Server 1600 Printer Controller 2000 Local Area Network 1 CPU
2 RAM
3 Flash ROM
4 System bus 5 LAN controller 6 LED
7 Expansion interface controller 8 CPU
9 ROM
10 External memory 11 System bus 12 Raster controller 13 Extended interface controller 14 RAM
15 Disk Controller 16 Print Engine 17 Expansion Interface Bus 18 Operation Panel

Claims (5)

A network card equipped with a CPU separate from the printing device, attachable to the printing device main body,
Means for allowing an application program operable on a virtual machine included in the network card to be added from the client to the network card;
A virtual machine capable of operating an application program for controlling the printing apparatus and controlling communication with the client;
When executing an application program interface that can be used from an application program, a model difference absorbing unit that determines a model according to a printing device on which a network card is mounted and performs processing according to the model;
Information changing means for changing the information acquired by the model difference absorbing means to information corresponding to the application program interface;
A network card comprising:   2. The network card according to claim 1, further comprising means for specifying a model of a printing apparatus main body when an application program interface that can be used by an application program is executed.   2. The network card according to claim 1, further comprising means for specifying a model of the printing apparatus main body when the power is turned on.   The network card according to claim 2, further comprising a model difference absorbing unit that performs processing when the printer is identified as an unknown model when the model of the printer main body is unknown. Network card.   The network card according to claim 3, further comprising a model difference absorbing unit that performs processing when the printer is identified as an unknown model when the model of the printer main body is unknown. Network card.

Images