Abstract:
Method of managing printing using multiple workstations, each with unique ID, and multiple printers having a type and configuration dependent on the ID, in a network including a document server and identification generator. At least one printer is connected to a workstation. The network polls a workstation upon connection to the network to determine what printers are connected to it; determines workstation ID, printer type and configuration from type and workstation location, and ID code for each connected printer using the identification generator; develops a look-up table of workstation ID, type and configuration of printer, and ID code; receives a print request from a workstation at the document server; in response to the request identifies from the look-up table the configuration of a printer that can receive the print request; and sends the print request to the identified printer with the appropriate ID code, as identified by the look-up table.

Description:
FIELD OF THE INVENTION 
     The present invention relates to a method and apparatus for managing printing solutions in one or more local area networks, in particular in the travel reservation domain but also anywhere where large numbers of work stations and printers which need not be dependant on each other are operated. 
     BACKGROUND OF THE INVENTION 
     There is a vast number of patents related to the management and the control of peripheral devices such as printers for example, in networks. 
     WO2000/052601 discloses a system that is capable of booking travel through a computer network by allocating communication links on a dynamic and distributed basis. It does not deal with the generation, storage, or auto adaptation of printer configurations and a management of the same by location or type identifiers. 
     US2003/145070 discloses a method for configuring a printer device with a specific controller. This controller can determine the physical environment of the printing device and what kind of device is asking for a printer. The controller can then configure the printer depending on the source device and in relation to a printing solution based on location and addresses for a mobile printer. The location of the printer, which is established by a position beacon, is determined in order to establish a link with a work station locally or remotely. It deals with a different set of issues than the current invention. 
     US2004/156074 discloses a method of printing data using a identification number of a printer instead of a network address. Thus if the network address of the printer is changed the user does not need to reset the printer port in order to update it with the new address of the printer. The port can still process the printing. This type of system is commonly referred to a fixed mode terminal identifier (TID). This fixed mode type of system requires an inventory of fixed work stations and devices. One configuration (including type, set up, TID, etc. . . . ) is defined per work station and per application. A device administrator administers this inventory using device administration. This requires continual manual input and activity whenever there are changes to the work stations and other peripheral devices. 
     In general the systems described in the prior art raise operational issues when dealing with very large number of devices. 
     SUMMARY OF THE INVENTION 
     An object of the present invention is to overcome at least some of the problem associated with the prior art method of controlling printing management. 
     Another object of the present invention is to define a manner in which to manage and administrate the logical address and physical configuration of a set of printers and how this may be automated. 
     According to one object of the present invention there is provided a method of managing printing in an environment with a plurality of work stations and a plurality of printers in one or more networks each work station having a unique identifier (ID) and each printer having a type and a configuration which is dependant on the unique ID, wherein one or more of the printers is connected to a one of the plurality of work stations; and wherein the network also includes a document server and an identity generator, the method comprising:
         polling a work station when it connects to the network to determine what printers are connected thereto;   determining the unique ID of the work station;   determining the type of printers;   determining the configuration of the printer from the type and work station unique ID;   determining an identification code (ID code) for each printer connected to the connected work station using the identity generator;   developing a look up table of unique ID of the work station; type and configuration of the printer and ID code;   receiving a print request from a client application or user at the document server;   identifying the configuration of the printer from the look up table in response to the print request;   sending the print request to the printer with the appropriate ID code, as identified by the look up table.       

     This invention has a number of advantages. It provides an auto registration process which allows retrieving, creating and updating a workstation configuration, including the configuration of its attached devices, without any administration. The storage of work station data in an identity generator data base allows transparent handling of fixed and dynamic addressing as well as configuration. The inventive identity generator can be used in any environment where a work station has a unique identifier and a list of attached devices for each type of workstation is well-known. For example, this may be of used in airports, stations, call centers, and possibly in shops where there are large number of tills and printing devices for printing out receipts etc. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
       Reference will now be made by way of example to accompanying drawings in which: 
         FIG. 1  is a high level view of the present invention. 
         FIG. 2  is a high level view of a second embodiment of the present invention. 
         FIG. 3  is a block diagram of the system including a terminal identity generator (TID dispenser) in accordance with one aspect of the present invention. 
         FIG. 4  is a diagram showing the auto registration for a first login to the TID dispenser of a work station. 
         FIG. 5  is auto registration process for the next login of a work station. 
         FIG. 6  is an auto registration example with the next login with updated work station configuration. 
         FIG. 7  are the configuration templates and configuration areas in accordance with one aspect of the present invention. 
         FIG. 8  is a representation of a work station configuration. 
         FIG. 9  is a diagram of auto registration configuration example. 
         FIG. 10  is a flow chart other method steps is associated with the choice between fixed and auto-registration modes. 
     
    
    
     DETAILED DESCRIPTION OF THE INVENTION 
     Referring now to  FIG. 1 , the architecture of the printing solution and the position of the identity generator or TID dispenser is shown. The diagram shows an airport LAN or full IP network  100  which is connected to a GDS LAN  114  by means of a communication module  104 . 
     The airport LAN includes one or more work stations  106 . A work station may have connected thereto a number of attached devices of different types. In this example, this could be an automatic ticket and boarding pass (ATB) printer  108 , a bag-tag printer (BTP)  110  and an optical character recognition (OCR) reader or printer  112 . 
     The global distribution system LAN, GDS LAN, includes the following elements: A GDS module  116 , a departure control system (DCS)  118 , a print server or document server (TDS)  120 , and a terminal ID dispenser (TID Dispenser)  122 . There may also be a TID database  124  for facilitating replication of the data in the TID dispenser  122 . This may also include redundancy. 
     Local communication between the work station and the printing devices is effected by a printer emulator  126  installed on the work station. A printer manager  128  is also shown that manages any printing events. The communication between the printer emulator and printer manager is via a TCP/IP link, for example. The work station also includes a java front end (JFE)  130  or any other type of Graphical User Interface (GUI) or user interface. Auto registered devices in accordance with the present invention do not require any device identity inventory maintained by a device administrator. Instead the device identity inventory is built and maintained automatically by the TID dispenser as the work stations log in. Device address attribution and configuration management is carried out by the terminal identity dispenser (TID) dispenser, and document formatting and delivery is managed by the document server (TDS). 
     The TID dispenser assigns TIDs to devices according to a work station ID and an application identifier and can review, create, update, retrieve or otherwise determine the configuration of those devices. This will be described in greater below. The print server formats the document requested by the DCS, and then route the print traffic to the identified printer that has been identified by the TID dispenser and the management thereof. The TID dispenser of the present invention can be adapted to different system requirements and is compatible with both fixed and automated TID devices. In the automated TID devices there would no longer be a requirement for device administrators maintaining a full device inventory. Instead an auto registration process will allow a work station to retrieve, create and update configuration without administration. This will now be described in greater detail. 
     The TID dispenser requires that each work station has an identifier that is unique on the worldwide basis. It would have been appreciate that the worldwide basis in this example relates to the extent of the network over which the invention applies. This may be an individual airport, this may be a number of different airport in different geographic location or maybe genuinely be on a worldwide basis. The identifier must be available on the work station and it is read by the printer emulator on the work station and provided to the TID dispenser. Work station identifier is essential for all work stations. The TID dispenser also uses the full location, i.e. the physical location of the work station. The full location can include for example airport, city, terminal, building, category, index, field etc. Not all fields of the full location are necessarily required. For example, for locations where the index is not meaningful it does not need to be specified. Similarly any other type of location codes could be a use for example building, stage, orientation, etc. . . . Any other type of discrimination or definition could be used in addition to (or instead of) the full location for example the function of the device, the level of priority, the year of deployment, company, etc. . . . The full location or an other discrimination or definition can be incorporated into the unique identifier of the work station. This means that only a unique identifier needs to be determined in the simplest case. The full location or other discrimination or definition is sent to the TID dispenser. The full location or other discrimination or definition is an essential feature for all auto register devices. 
     Each printer emulated embedded application may benefits from an application identifier, the application identifier including an application label and an application index field. For example two graphical user interfaces or client application started on a work station will be referred to as App  1  and App  2  respectively. In an embodiment of the invention, the application label is stored in the GUI and the application index is provided to the printer emulator in the start command line. Application label and index are essential in circumstances where multiple applications are running at the same time on a specific work station and if it is required that the printers have different ID and configuration according to the application. The system can work without application identifier in the situation where each printer or device has the same ID and configuration whatever the application running on the workstation. Any different identifier could be used to allocate different IDs and configurations to the same device such as for example a category code, a user identifier instead of the application identifiers mentioned above. 
     Device set up record gives us some low level parameters of the physical devices. These parameters are used by document servers for formatting and printing. In an embodiment of the invention, the administration of device set-ups is available in a device administration GUI. 
     In the auto registration mode described below, device set ups are generally homogenous with the full location or any other type of discriminator or definition deployed for a given device type. 
     Referring now to  FIG. 2  a more expansive network set up is shown. Here there are two airport LANs  200  and  202  connected to a GDS LAN  204 . All the LANs may be in the same or different physical/geographic locations. Each airport LAN includes one or more work stations and printers equivalent to work station  106  and printers  108 ,  110  and  112  in  FIG. 1 . The GDS LAN is substantially similar to the GDS LAN  114  in  FIG. 1 . 
     The manner in which the TID dispenser is connected into the system is shown with respect to  FIG. 3 . The TID dispenser  300  is connected to the work station  302  via a bidirectional connection. The work station is also connected to a document server  304 . The work station is shown having two printer ports an automatic ticket and boarding pass ATB printer  306  and a bag-tag printer BTG  308 . 
     Information is passed from the work station (arrow  1  the information includes work station ID (identifier and full location); application identifier (label and index); and list of detected devices with type. This information is registered in the TID dispenser  300 . The TID dispenser then generates a list of TIDs that may be fixed or auto registered. This information is then returned to the work station by means of communication in the direction of arrow  2 . Similarly, data is communicated with the document server so the document server knows the relevant printers for a specific work station. The information in a line of the database that constitutes the TID dispenser indicates a carrier, a work station ID and an application identifier and the configuration of all printers attached to the work station. Accordingly if there is more than one application on a specific work station each of application will have a different configuration in the TID dispenser data base. 
     Referring to  FIG. 4  when a work station first logs into the system via the TID dispenser, the following sequence of events occurs. The work station  400  is connected to two active application devices  402  and  404  respectively. The work station is connected to the TID dispenser  406  and the document server  408 . Similarly the document server and TID dispenser are connected to one of the other. The TID dispenser generates the configuration for the workstation and its connected devices. This configuration is stored in the TID dispenser database  410 . 
     A print request may be generated and communicated to the document server. At that point the document server will interrogate the TID dispenser to determine the appropriate configurations templates and printers for the print request. The document server will then transmit the print request directly to the appropriately identify printer. 
     Referring now to  FIG. 5  the next time login of a work station is explained. As under the first example the printer emulator requests the TIDs for the work station/application combination. 
     It is considered as known work station as the work station identifiers are recognized. This step will be referred to as next login in the rest of the document. Again if a printer request is received at the document server, the document server will retrieve the relevant TID and configuration from the TID dispenser and implement the printing action at the required printer. 
     Referring now to  FIG. 6  a new printer PRT  600  has been added to the work station  602 . At this time when the work station connects to the TID dispenser it is recognized as a known work station but that new device is identified. This causes an additional a TID to be provided by the TID dispenser for that work station and included in the work station configuration. The update is communicated with the work station and the document server as has been described with reference to  FIG. 4 . These changes are stored and maintained until such time as the work station changes again. Similarly, if the work station reconnects in the next log in the new printer  600  will already identified and recognize and the actions will be equivalent to those shown with reference to  FIG. 5  thereafter. 
     Further detail of the auto registration mechanism is now described. The auto registration of a work station is authorized on the basis of its full location or other discrimination or definition. A device administrator or an external application defines the locations where work stations can auto register. It is the role of the administrator to define two objects, configuration templates and configuration areas. Configuration templates store the links between device types and device set-ups. It is expected the configuration templates list all the possible device types that could be provided by a work station. This is the only role played by the device administrator. A configuration area associates a configuration template with a full location or other discriminator or definition. In the example shown in  FIG. 7 , configuration template have been attributed to NCE/T 2 /G/ 3  and NCE/T 1  where NCE stands for Nice airport, T 1  stands for Terminal  1 , T 2  stands for Terminal  2  and G stands for a gate number. NCE/T 1  is considered as a full location distinct from for example NCE/T 1 /G/ 20  or NCE/T 1 /LNG. A wild card functionality is available to attribute a configuration template to several full locations. For example LHR/T 1 /G/* includes all the gates in terminal  1  of LHR airport whatever the index. That is a work station on LHR/T 1 /G/ 20  will use the configuration template, configuration T_ 2 . Looking more closely at  FIG. 7 , it can be seen that configuration T_ 1 ,  700  shows the device type and the device set up. The configuration template name is identified in the top row and the whole of the table  702  constitutes one configuration templates. Dealing with the configuration areas, the full location is shown in the left column and the configuration template is in the right column. One configuration area is equivalent to one row of the table  704 . In an embodiment, these configuration areas and templates can be created using a device administration GUI. 
       FIG. 8  shows an extract from the TID dispenser table which identifies the work station name and the application identifier along with the type, set up and TID indicator for the same. It can also be seen in  FIG. 8  that each column constitutes one device attached to a specific work station. 
       FIG. 9  shows a configuration generated with the auto registration process. It also shows the information used by the auto registration process. 
     Referring now to  FIG. 10 , the process for determining whether the devices, workstations and printers etc are operated in fixed mode or auto registration mode is explained. The decision as to which mode should be selected is made in order to deal with the situation where certain workstations connected to one or more of the LANs is unable to operate in an auto registration mode. The steps carried out to achieve this selection are shown in  FIG. 10  and starts with the retrieval of identity of a certain work station step  1000 . A determination is made as to whether the application label for the workstation is a known organization (step  1002 ) and if the full location details are valid (step  1004 ). In each case if the answer to this question is no the process stops (steps  1006  and  1008  respectively). If the answer to each question is yes the process continues. 
     The next determination at step  1010  is to determine whether the workstation ID is known in the TID dispenser database. If the answer to this question is no this equates to a first login step for the workstation and an auto registration mode is entered. A determination is then made as to whether the full location match is a configuration area (step  1012 ) if the answer is yes the configuration template is retrieved from the configuration area (step  1014 ). A determination is then made as to whether the full location matches an office identifier (step  1016 ) and then a determination as to whether there are enough TIDs in the pool (step  1018 ). If the answers to all of these questions are yes then a workstation configuration is created (step  1020 ). After the workstation configuration has been created the identity of the workstation is returned to the workstation, the TID dispenser, and any other media that needs to know ( 1028 ). In each case if the response to the question is no the process is exited ( 1022 ,  1024 ,  1026 ). 
     At step  1010  if the workstation ID is known to the TID dispenser database this equates to next login step ( 1030 ). A determination is then made as to whether the application identifier is known in the database (step  1032 ). If no, there may be a new application ( 1034 ). If there is a new application or not as the application identifier is not known in the database the process returns to step  1012  and determination of whether the full location matches configuration area is made. On the other hand, if the application identifier is known in the database workstation configuration is retrieved at step  1036 . At step  1038  a determination is made as to whether the type list is compliant with the workstation configuration. If yes the identity is returned as above at step  1028 . 
     If the answer is no at step  1038  a determination is made as to whether the workstation is in an auto registration or fixed mode (step  1040 ). If the workstation is in a fixed mode the identity of the workstation is returned and a warning is sent step  1042 . The identify has the format as described in  FIG. 8 . The warning shows any discrepancy between stored identity and information received from the workstation. If the workstation is an auto registration mode a determination is made at step  1042  as to whether there are enough TIDs in pool. If yes, the workstation configuration is updated (step  1044 ) and any updates are registered (step  1046 ). The identities are then returned as above in step  1028 . If at step  1042 , there are not enough TIDs in the pool the process is exited ( 1048 ). 
     In this way the system according to the present invention can operate for all workstations in a given environment. The ability to identify whether the workstation is in a fixed or auto registration mode enables greater flexibility in the system and method of the present invention. In addition, it enables the gradual transfer of workstations from a fixed mode to an auto registration mode in a controlled and managed fashion. 
     At the stage of next log in, if the list of device types provided to the TID dispenser changes (in other words is different from the list provided at the previous login) the TID dispenser will automatically adapt the work station configuration by reusing the configuration template. Devices can thus be removed from or added to the work station configuration without any manual update from the device administrator. Device set ups of all the devices located in a location can be updated by changing the configuration template. 
     As has been indicated this invention relates to many different environments. The airport scenario described above, is just by way of example and it is clear that the invention can be used in any contexts. It will also be appreciated that the scenario described can have many variations and still remain within the spirit and scope of the present invention.