Point Of Sale—POS
Computer System—CS
Universal Product Code—UPC
Consumer IDentification—CID
Point of sale means a location where a sales transaction occurs.
Universal product code UPC means any code used to uniquely identify a product item, including the original UPC specification and subsequent variations and expansions thereupon.
Transaction data means data for a transaction, such as a transaction transacted at a POS. Transaction data includes UPC codes for product items purchased, product description, manufacturer, brand name, prices of those items, CID associated with the transaction, POS identifier (lane), date, time, discounts, coupon identifications, cashier identification, payment type, etc.
Individual transaction data means transaction data associated with a single transaction. Individual transaction data need not include all of the foregoing elements described for transaction data.
Print file for a printer means a file containing instructions in the printers native instruction set and all data to be contained in the printout by the printer of the print file.
Print data for a printer means data containing instructions for a printer including references to data objects stored by the printer, other than printer glyphs and individual text characters.
Printer glyphs are image objects used by printers to form text characters of font sets.
Computer system means one or more digital computers networked together.
In the prior art, combined POS and incentive offer generation CSs include a store controller CS and an incentive CS both located at a retail store in which the retail store in which the store controller CS operates. The store controller CS received the transaction data from the POS terminals from which it can track the inventory for that retail store, and provide to the POS terminals product pricing information for products identified at the POS terminals. For large retail stores, there are plural POS terminals. The store controller CS typically stores price, product item stock, and accounting information for the retail store, and transaction data obtained from the POS terminals in that retail store. The POS terminals may be specialized CSs performing POS terminal functions. Those functions included acquiring individual transaction data, transmitting the data to the store controller CS, and generating a printed register or sales receipt.
In the prior art, there is a POS black ink printer at each POS for printing register or sales receipts for each customer conducting an individual purchase transaction at the POS. At each POS there is a bar code reader for reading into the POS terminal UPCs, CIDs, and a magnetic strip reader for reading payment account identifications, such as customer credit or debit card number. These readers at the POS and the POS terminal are functionally interrelated so that the POS terminal may acquire the read data. There may also be readers associated with the POS designed to read checking account number from checks and biometric data, and to pass that information to the POS terminal. In the prior art, all of the POS terminals communicate with a store controller CS via network connections.
In the prior art, there is also an incentive CS located at the retail store. The incentive CS has a network connection to the network segment connecting the POS controller CS to the POS terminals. This enables the incentive CS to listen to the network traffic between the POS terminals and the POS controller CS. The incentive CS stores enough of the specification of the store controller CS to be able to decode the network traffic to determine lane, UPC, CID, and end of transaction data. This allows the incentive CS to obtain individual transaction data.
In the prior art, the incentive CSs had a means (either dial up or network connection to the Internet) to communicate with a central CS to provide individual transaction data, and other data, thereto. The central CS transmitted awards data to the incentive CS. Awards data includes a CID in association with incentive data. Incentive data is for example instructions for printing an incentive offer, a such as a coupon. The awards data may include a UPC for a product having the discount to be offered by the coupon.
The prior art systems did not include the novel features, network structure, processing, or business rules, and business methods, related to default and second printing, discussed below.
It is an object of the invention to provide systems and computer implemented methods for printing information.
The inventor conceived of using a printer, preferably a color printer, at a POS, to print receipts, data structures to store related graphics, and hardware to apply certain printer receipt related business rules (herein after business rules), for individual transactions occurring at each POS. Execution of some of the business rules results in generation of a default and a second print file, or default and second print data, and transmission of the default and second print file or print data to the printer at the POS. Some of the rules and the preferred embodiment relate to a color printer since they involve printing of color highlighting, such as water marking, and printing different colors.
Retail Store Network Configuration
The invention provides local retail store network architectures that enable a CS, preferably an incentive CS, to obtain data upon which it runs business rules to generate a second print file or second print data, and to send that second print file or second print data to a POS printer at a POS, in addition to a default print file or default print data sent to the POS printer. The data used to generate the first and second print files or print data includes individual transaction data, and optionally awards data and updated business rules data.
Alternative retail store CS network architectures include a network line connecting from the incentive CS to:
A—a line on which the prior art incentive CS listens to the network traffic in the POS CS;
B—a data line connecting the terminal CS to a network segment to which the incentive CS connects;
C—a data line connecting to the data line from the terminal POS to the printer; or
D—a data line connecting to both the incentive CS and the printer.
The data line D connecting to both the incentive CS and the printer preferably connects to a USB port on the printer.
The functional requirement of embodiments employing an incentive CS is to enable the incentive CS to obtain the transaction data from the POS and provide data to the printer, preferably a color printer, associated with the POS terminal at that POS.
In all embodiments, the POS printer may determine the origin of a print file sent to it by either a network address associated with the print file, or by a flag value associated with the print file, and a lookup table in the printer logic indicating by network address or flag value the origin of the print file.
In all embodiments, a CS refers to at least one central processing unit (CPU), memory the CPU accesses, and an operating system enabling the CPU, the memory, and optional input output (I/O devices to function based upon non operating system code.
In those instances where it is noted that a printer performs processing, the printer includes a CPU and memory accessible by the CPU of the printer enabling the printer to perform the indicated functions. The printer also includes printing hardware for printing to paper.
Reference to separate elements communicating with one another including the store controller POS, the incentive CS, the POS terminal, and the printer, indicates network communication between these elements employing one or more network protocols.
In all embodiments, optionally the CS generating the second print file or second print data, does not send that second print file or second print data to a printer if the second print file or second print data is not sent by a predetermined send time. The predetermined send time is either based upon a time starting from a time of completion of the transaction associated with the individual transaction data, or a time starting with receipt of individual transaction data by the CS generating the second print file or second print data.
In one alternative, the POS terminal or the store controller CS generates a default print file for printing a sales receipt for an individual transaction completed at a POS, and transmits that default print file to the POS printer at that POS. The POS printer is programmed to cache the default print file it received form the POS terminal for a predetermined period of time, a wait time period, such as 1, 2, of 5 seconds, while it awaits data from the incentive CS. If the POS printer receives a second print file from the incentive CS prior to the predetermined period of time, the POS printer is configured to print the second print file it received from the incentive CS and not print the default print file it received from the POS terminal or the store controller CS. If the POS printer does not receive the second print file from the incentive CS within the predetermined period of time, the POS printer is configured to print the default print file received from the POS terminal or the store controller CS, and to not print the second print file.
In a related alternative, the POS terminal or the store controller CS generates default printer data for transmission to the printer, and the POS printer uses that default printer data to look up additional data in a local printer database in the printer to generate a default print file including a sales receipt, and prints the default print file containing the sales receipt for the individual transaction completed at the POS terminal. The POS printer is programmed to cache either the default print data it receives from the POS terminal or the default print file the printer generates, for a predetermined period of time, such as 1, 2, of 5 seconds, while it awaits data from the incentive CS. If the POS printer receives second print data from the incentive CS for printing a sales receipt prior to the predetermined period of time, the POS printer uses that second print data to look up additional data in a local printer database to generate a second print file including a sales receipt, and the POS printer prints the second print file including the sales receipt for the individual transaction completed at the corresponding POS, and it does not print the default. If the POS printer does not receive the second print data from the incentive CS within the predetermined period of time, the POS printer is configured to print from the default.
In a related alternative, the POS printer may be configured to either receive print files, or use print data it receives to look up additional data in a local printer database to generate print files, from either or both of the incentive CS and the alternative source of data, either the POS terminal or the store controller CS. That is, the POS printer may receive any combination of either or both of print data or print files corresponding to the default print data or file, and any combination of the second print data or file.
In one alternative, the POS terminal is programmed to transmit the default print file or default printer data it generated to both the POS printer and to the incentive CS. The incentive CS then uses that default printer file or default printer data to determine the individual transaction data for the individual transaction and to implement its business rules on that individual transaction data, and the incentive CS subsequently transmits a second print file or second printer data, which is based upon implementation of its business rules on that transaction data, to the POS printer.
In one alternative, the store controller CS or the POS terminal assumes the functions of the incentive CS, in which case the incentive CS is redundant and not necessary. In this alternative, the store controller CS of the POS terminal stores the data indicated above for the incentive CS, and the store controller CS of the POS terminal transmits to the POS printer the data indicated above as being transmitted by the incentive CS. If the store controller CS assumes the functions of the incentive CS, it may receive the default print file or default print data indicated above as being sent to the incentive CS.
In one alternative, the POS printer assumes the functions noted above for the incentive CS. In this embodiment, the POS printer includes a central processing unit and memory and generates the second print data or second print file indicated above as being generated by the incentive CS. The POS printer does so by either concurrently processing individual transaction data to generate the default print file and the second print file, or by first generating the default print file and sequentially thereafter generating the second print file. Of course, the POS printer stores the code containing the business rules associated with the incentive computer, and the data associated with the incentive computer indicated above.
Timing
The predetermined period of time is preferably set to be a time during which a delay will not cause reduced efficiency or annoyance to customers completing a transaction at the POS. If the POS printer received a print file from the incentive CS within the specified period of time, the POS printer proceeds to print the print file received from the incentive CS and not print the print file received from the POS terminal.
The incentive CS receives individual transaction data for an individual transaction during or after the end of the individual transaction. The incentive CS may obtain the individual transaction data for the individual transaction from a network connection of the type described above while the transaction is occurring. Alternatively, the incentive CS may receive an individual transaction data file for the individual transaction, once that transaction is completed, from one of the other network nodes, including the store controller CS, the POS terminal, or the POS printer.
At some point, the incentive CS receives data indicating to it that the transaction at the POS has ended (end of transaction data signal, or tender data signal). If the incentive CS completes its business rule processing prior to receipt of the end of transaction data, it awaits that end of transaction data. If the incentive CS has received that end of transaction data prior to completion of processing of its business rules against the transaction data in response to an individual transaction, the incentive CS completes its business rule processing and generates either a second print file or second print data containing sales receipt data, and also additional print information, and transmits that second print file or second print data to the POS printer associated with the POS from which the individual transaction data originated.
Format of Data Sent to the Post Printer
The data that the POS printer receives include reference data specifying objects and print properties stored in the database in the POS printer and a sequence of printing of those objects. For example, the non print file data that the POS printer receives may be in vector graphics form, and the data stored in the database in a color printer may be objects including color objects, referenced in vector graphics files.
Business Rules Implemented in the Incentive CS
The incentive CS may run rules specific to individual UPCs, or any combination of UPC codes. Therefore, upon receipt of each UPC code, the incentive CS may run code implementing certain business rules that do not require prior completion of the customer's order.
The business rules executed by the incentive CS may be implemented against the individual transaction data for the current individual transaction at the POS, or against that data and also against data stored by the incentive CS from prior transactions associated with a CID associated with the current individual transaction data.
For example, a business rule implemented by the incentive CS may provide the consumer a coupon for one brand of a category of products when the consumer has consistently over a period of time purchased another brand in that category of products. That business rule may require examining individual transactions data for prior transactions associated with the CID associated with the current transaction, or both prior transactions data and the current individual transaction data.
For example, a business rule implemented by the incentive CS may be to highlight, enlarge in font size, change font, add a watermark background color, or add branding text, to print in the register receipt for a product identification associated with a certain UPC in the individual transaction data. See for example
Definition of Additional Print Information
The data stored by the incentive CS may include individual transaction data, business rules data specifying information to include in printing in addition to the conventional the register receipts information. Conventional register receipts information includes product identification, price, quantity, and total cost. This additional information relating to the register receipt is called herein below ‘additional print information.’ The additional print information results in the second print data and the second print data for an individual transaction being different from the default print file and default print data for that transaction.
The additional print information to include in printing of the register receipt results from applying business rules to the individual transaction data for transactions. This additional print information may include any or all of color, size, and location, of printed text and image data, such as color highlighting of certain product identifications, change in dimension or font type of text associated with certain product descriptions, inclusion of product logos, order of printing of descriptions of products (which ones to print first for higher visibility), and also information for printing coupons and product redemption forms, including coupon and redemption form product identifications, and amount of coupon or redemption form value.
The incentive CS applies the business rules to either generate a second print file in which the additional print information has been used to specify the second print file or generate second print data instructions used by the printer to generate and print, including printing of data objects stored in a database in the POS printer.
For example, the business rules may result in additional print information specifying highlighting with a water mark, a certain color border, a certain color text, a font, a character code size, text or graphics, and text or graphics objects to include in print.
Skippy Example
As a concrete example, one business rule is to print the portion fo the register receipt containing identification of a particular Skippy brand peanut butter product item showing the item description (Skippy 12 Oz bottle) and cost along with a light blue background, a foreground image of a can of Skippy peanut butter, and the statement “More Skippy has been sold than any other peanut butter in the world!” See
Central CS
The business rules and data applicable to the incentive CS and the POS printer may be periodically or aperiodically updated. The updates may be transmitted from the central CS to each incentive CS in each retail store, to each store controller CS, and each networked POS printer. The updates include be new business rules for the incentive CS to implement sent to the incentive CS, reference identifications for data objects which are transmitted to both the incentive CS and the POS printer, and corresponding data objects transmitted to the POS printer.
In addition, the central CS could transmit to each incentive CS, each store controller POS, each POS printer, or to a central retail store CS, changes and updates to retailer product descriptions. The central CS can receive retailer specific updates via communication from a master retailer CS via the Internet.
Validation Checks
The incentive CS may perform pre business rule validation checks on the transaction data it receives. These validation checks may include (1) that all UPCs in the transaction data are in the incentive CSs local database and (2) that transaction data received by it for the same transaction from two different sources (such as the POS terminal and the store controller CS), contained the same data. If the incentive CS determines a discrepancy between two data sets, it may not generate and send a print file or print data to the POS printer. Instead, it may send a non validation signal to the POS printer, and the POS printer may be configured to respond by printing the print file or print data it previously received from the store controller POS in response to receipt of the non validation signal.
Related Invention
In a related invention, retailer computer system 10 is configured to always print on the POS printer the default print file or default print data. In addition, the POS printer is configured to thereafter print a second print file if the POS printer receives the second print file within the wait time period. In this related invention, retail store CS generates a second print file or second print data which does not instruct the POS printer to print register receipt information contained in printing of the default. Instead, the second print file or second print data only instructs the POS printer to print information in addition to the default register receipt information, including specifically coupons resulting from processing individual transaction data by the retail store CS and awards determined by the CID associated with each individual transaction and a lookup table of CIDs and associated awards.
In one aspect, the invention provides a system and computer implemented method for printing information, comprising:
receiving in a POS terminal of a POS of a first retail store individual transaction data for an individual transaction;
generating from said individual transaction data for said individual transaction either a default print file or default print data for printing a sales receipt for said individual transaction;
printing from a POS printer, if said POS printer at said POS receives a second print file or second print data associated with said individual transaction data prior to expiration of a wait period of time associated with at time of said individual transaction, using said second print file or said second print data;
printing from said POS printer, if said POS printer does not receive said second print file or said second print data prior to expiration of said wait period of time, using said default print file or said default print data.
In another aspect, the invention provides a computer implemented system and method for printing information, comprising:
receiving, in a POS terminal of a retail store CS at a POS in a retail store, individual transaction data for an individual transaction;
generating from said individual transaction data for said individual transaction a default print file or default print data for printing a sales receipt for said individual transaction;
printing, using said default print file or said default print data, said sales receipt at a POS printer;
printing from said POS printer, using a second print file or second print data, at least one coupon, only if said POS printer receives said second print file prior to expiration of a specified wait period of time.
Other dependent aspects are described below and appear in the dependent claims.
The invention is also described with reference to the following figures.
Central CS 30 includes a database storing data received from a plurality of retail store CSs. This data includes individual transaction data, awards log data, and it may include printer description data and printer software data, such as printer drivers.
Manufacturer CS 20 may include manufacturer data specifying manufacturers products, coupons or advertising to associate with that product, and may also include manufacturer criteria applicable to purchase history data (historical individual transaction data) associated with a CID indicating if that CID qualifies for the coupons or advertising. Central CS preferable includes code for receiving that data from the manufacturer CSs for multiple manufacturers, and applying the foregoing manufacturer criteria to transaction data, generating corresponding awards data (awards in association with the CID), and transmitting the awards data to the retail store CS associated by the central CS with the CID.
Retail store CS 10 includes code for logging transactions occurring in the POSs of the corresponding retail store, generating a default print file for individual transaction data for each individual transaction, generating a second print file for individual transaction data for each individual transaction, determining if CIDs associated with individual transaction data for each individual transaction qualify for awards, and printing a register receipt and awards data. A POS printer prints the register receipt based upon either the default print of second print file or data. The POS printer or a second marketing printer optionally prints awards associated with the individual transaction data for an individual transaction, after the retail store CS 10 determines awards for which that CID and that individual transaction qualify.
Master retailer CS optionally receives transaction data from retail store CS 10 and sends retail store CS 10 updates to product descriptions, UPCs, and other information. Central CS 30 may alternatively perform any of these functions.
Printer P1 may be a local printer controlled by POS terminal T1, or it may be a network addressable node in the retail store CS local area network.
The printed segments corresponding to data fields for purchased product information 320's in line image data objects correspond for example to the image “Pic ID” 320A; for large image data objects correspond for example to “Pic ID” 320B, for product descriptions correspond for example to “Fresca” 320C, for large image additional descriptions for example to “More Skippy has been sold than any other peanut butter in the world” 320D, product description formatting for example to the relative locations of the information corresponding to the Skippy product, and coloring corresponding for example to watermark 320E, indicated by slanted lines, over the information for the Skippy product. The enlarged size of the information relating to the Skippy product and the distinct coloring (such as water marking) associated therewith makes the Skippy related information more discernable to a viewer.
Optionally, coupons may be printed on the printer printing the register receipt, on the same paper tape on which the register receipt 300 is printed. Preferably, such coupons are printed before or after regions 310-330. The coupons so printed may be based upon processing by retail store CS 10 is described above.
This application claims priority to U.S. provisional application 60/778,410 filed Mar. 3, 2006, entitled “POS Network Including Color Printing and Color Highlighting”
Number | Name | Date | Kind |
---|---|---|---|
3925788 | Kashio | Dec 1975 | A |
4261036 | Nagasaka et al. | Apr 1981 | A |
4980725 | Sumida | Dec 1990 | A |
5456539 | Wright et al. | Oct 1995 | A |
5570451 | Sakaizawa et al. | Oct 1996 | A |
5619558 | Jheeta et al. | Apr 1997 | A |
5633662 | Allen et al. | May 1997 | A |
5634090 | Narukawa et al. | May 1997 | A |
5666215 | Fredlund et al. | Sep 1997 | A |
5688154 | Goda et al. | Nov 1997 | A |
5737729 | Denman | Apr 1998 | A |
5767886 | Kawakami et al. | Jun 1998 | A |
5857175 | Day et al. | Jan 1999 | A |
5917513 | Miyauchi et al. | Jun 1999 | A |
6021362 | Maggard et al. | Feb 2000 | A |
6076068 | De Lapa et al. | Jun 2000 | A |
6119933 | Wong et al. | Sep 2000 | A |
6129274 | Suzuki | Oct 2000 | A |
6151038 | Suzuki | Nov 2000 | A |
6203131 | Wiklof | Mar 2001 | B1 |
6231249 | Harris | May 2001 | B1 |
6246997 | Cybul et al. | Jun 2001 | B1 |
6252673 | Miyasaka et al. | Jun 2001 | B1 |
6313925 | Decker et al. | Nov 2001 | B1 |
6341269 | Dulaney et al. | Jan 2002 | B1 |
6344899 | Tabata et al. | Feb 2002 | B1 |
6351735 | Deaton et al. | Feb 2002 | B1 |
6415261 | Cybul et al. | Jul 2002 | B1 |
6663304 | Vives et al. | Dec 2003 | B2 |
6721613 | Yamamoto et al. | Apr 2004 | B1 |
6767073 | Tschida | Jul 2004 | B2 |
7014110 | Minowa et al. | Mar 2006 | B2 |
7145673 | Lin | Dec 2006 | B1 |
7156304 | Minowa et al. | Jan 2007 | B2 |
7424443 | Yanagisawa et al. | Sep 2008 | B2 |
7689461 | Minowa | Mar 2010 | B2 |
7708360 | Byerly et al. | May 2010 | B2 |
7914213 | Scarton | Mar 2011 | B2 |
8159709 | Young et al. | Apr 2012 | B2 |
8764138 | Byerly et al. | Jul 2014 | B2 |
8964244 | Mount et al. | Feb 2015 | B2 |
20010021331 | Brewington et al. | Sep 2001 | A1 |
20010032128 | Kepecs | Oct 2001 | A1 |
20010032130 | Gabos et al. | Oct 2001 | A1 |
20010034775 | Minowa | Oct 2001 | A1 |
20020109729 | Dutta | Aug 2002 | A1 |
20020120514 | Hagmeier et al. | Aug 2002 | A1 |
20020129002 | Alberts et al. | Sep 2002 | A1 |
20020143655 | Elston et al. | Oct 2002 | A1 |
20030023492 | Riordan et al. | Jan 2003 | A1 |
20030036979 | Tokorotani | Feb 2003 | A1 |
20030046154 | Larson et al. | Mar 2003 | A1 |
20030050842 | Wada et al. | Mar 2003 | A1 |
20030061100 | Minowa | Mar 2003 | A1 |
20030081238 | Lester et al. | May 2003 | A1 |
20030101095 | Suzuki | May 2003 | A1 |
20030121929 | Liff et al. | Jul 2003 | A1 |
20030197782 | Ashe et al. | Oct 2003 | A1 |
20030227510 | Payne | Dec 2003 | A1 |
20040004644 | Komatsu et al. | Jan 2004 | A1 |
20040030600 | Lacroix | Feb 2004 | A1 |
20040034570 | Davis | Feb 2004 | A1 |
20040046971 | Lapstun et al. | Mar 2004 | A1 |
20040054583 | Nye, III et al. | Mar 2004 | A1 |
20040059634 | Tami et al. | Mar 2004 | A1 |
20040109190 | Nagai | Jun 2004 | A1 |
20040148223 | Ghaffar et al. | Jul 2004 | A1 |
20040227972 | Uchikawa | Nov 2004 | A1 |
20040246287 | Usuda | Dec 2004 | A1 |
20050040230 | Swartz et al. | Feb 2005 | A1 |
20050080651 | Morrison et al. | Apr 2005 | A1 |
20050171845 | Halfman et al. | Aug 2005 | A1 |
20050242178 | Minowa | Nov 2005 | A1 |
20050247781 | Minowa et al. | Nov 2005 | A1 |
20050264850 | Kim et al. | Dec 2005 | A1 |
20050270550 | Sumio | Dec 2005 | A1 |
20050271446 | Minowa | Dec 2005 | A1 |
20060126102 | Sakuda | Jun 2006 | A1 |
20060143075 | Carr et al. | Jun 2006 | A1 |
20060287872 | Simrell | Dec 2006 | A1 |
20060289633 | Moreland et al. | Dec 2006 | A1 |
20070045405 | Rothschild | Mar 2007 | A1 |
20070120943 | Van Demark et al. | May 2007 | A1 |
20070206209 | Mount | Sep 2007 | A1 |
20070221728 | Ferro et al. | Sep 2007 | A1 |
20140312111 | Byerly et al. | Oct 2014 | A1 |
Number | Date | Country |
---|---|---|
1702695 | Nov 2005 | CN |
0928698 | Jul 1998 | EP |
1292096 | Mar 2003 | EP |
1321307 | Jun 2003 | EP |
1267565 | Dec 2003 | EP |
1 467 301 | Oct 2004 | EP |
2 548 805 | Jan 1985 | FR |
2-207397 | Aug 1990 | JP |
10-214383 | Aug 1998 | JP |
H10-214383 | Aug 1998 | JP |
11-212527 | Aug 1999 | JP |
H11-212527 | Aug 1999 | JP |
2000-105786 | Apr 2000 | JP |
2000105786 | Apr 2000 | JP |
2002-14917 | Jan 2002 | JP |
2002-234215 | Aug 2002 | JP |
2004-013708 | Jan 2004 | JP |
2004098503 | Apr 2004 | JP |
2005-182396 | Jul 2005 | JP |
2005-335125 | Dec 2005 | JP |
2005-343028 | Dec 2005 | JP |
WO 9821713 | May 1998 | WO |
Entry |
---|
Nov. 9, 2007 ,PCT International Search Report PCT/US07/63051. |
Dec. 26, 2007, PCT International Search Report PCT/US06/30716. |
Dec. 26, 2007, PCT Written Opinion PCT/US06/30716. |
Nov. 9, 2007, PCT Written Opinion of the ISA PCT/US07/63051. |
Supplemental European Search Report dated Feb. 4, 2011 in related application 06789518. |
Abstracts of Japan, publication No. 2004098503, published Apr. 2, 2004. |
Office action in related application CA 2,624,622, dated Jul. 11, 2011. |
Nov. 9, 2007, PCT International Search Report PCT/US07/63051. |
Nov. 9, 2007, PCT Written Opinion PCT/US07/63051. |
Dec. 26, 2007, PCT International Search Report PCT/US06/26313. |
Dec. 26, 2007, PCT Written Opinion PCT/US06/26313. |
Jun. 17, 2008, PCT International Search Report PCT/US06/30716. |
Jun. 17, 2008, PCT Written Opinion PCT/US06/30716. |
Aug. 15, 2007, PCT International Search Report PCT/US06/11843. |
Aug. 15, 2007, PCT Written Opinion of the ISA PCT/US06/11843. |
Jun. 10, 2009, European Search Report EP 06 78 6463. |
Jul. 19, 2007, Claims filed by amendment filed Apr. 7, 2009 in U.S. Appl. No. 11/366,397. |
Jun. 7, 2007, Claims allowed by Notice of Allowance mailed Dec. 16, 2009 in U.S. Appl. No. 11/488,126. |
Claims filed Jan. 22, 2010 in application U.S. Appl. No. 12/692,419. |
Jun. 7, 2007, Claims filed by preliminary amendment filed Jun. 3, 2008 in U.S. Appl. No. 11/481,789. |
English translation of Feb. 5, 2010 Chinese office action in related case, application No. CN 200680045022.3. |
Extended European Search Report in EP 09012094, dated Nov. 9, 2009. |
US Office Action dated Apr. 16, 2010 in related U.S. Appl. No. 11/481,789. |
English translation of Mar. 11, 2010 Chinese office action in related case, application No. CN 200680045132.X. |
English translation of Mar. 2, 2010 Chinese office action in related case, application No. CN 200780005831.6. |
CIPO office action dated May 19, 2010 in related case CA 2,624,620. |
Jul. 13, 2010, CIPO office action dated Jul. 13, 2010 in related case CA 2,637,946. |
European Search Report dated Aug. 13, 2010 in related case EP 06786463.7. |
English translation of Abstract EP 09012094.0. |
European Office Action dated Dec. 12, 2011 in EP Application No. 09012094.0, 6 pages. |
Chinese Office Action dated Dec. 16, 2011 in Application No. CN 200680045022.3, with English translation, 9 pages. |
Canadian Office Action dated Feb. 10, 2012 in Application No. CA 2,637,946, 4 pages. |
European Office Action dated Feb. 17, 2012 in Application No. EP 06786463.7, 6 pages. |
U.S. Office Action dated Mar. 29, 2012 in U.S. Appl. No. 12/692,419, 16 pages. |
U.S. Office Action dated Mar. 30, 2012 in U.S. Appl. No. 11/481,789, 10 pages. |
Japanese Office Action dated May 15, 2012 in Application No. JP 2008-557494, with English translation, 6 pages. |
Japanese Office Action dated May 29, 2012 in Application No. JP 2008-544322, with English translation, 6 pages. |
Japanese Office Action dated May 29, 2012 in Application No. JP 2008-544317, with English translation, 5 pages. |
Chinese Office Action dated Jun. 15, 2012 in Application No. CN 200680045022.3, with English translation, 12 pages. |
U.S. Office Action dated Jun. 25, 2012 in U.S. Appl. No. 12/758,901, 10 pages. |
U.S. Notice of Allowance dated Sep. 4, 2012 in U.S. Appl. No. 11/481,789, 7 pages. |
Japanese Office Action dated Oct. 9, 2012 in Application No. JP 2008-544322, with English translation, 4 pages. |
Chinese Office Action dated Oct. 9, 2012 in Application No. Cn 200680045022.3, with English translation, 14 pages. |
Canadian Office Action dated Oct. 29, 2012 in Application No. CA 2,624,622, 3 pages. |
Japanese Office Action dated Nov. 1, 2012 in Application No. JP 2008-557494, with English translation, 4 pages. |
U.S. Office Action dated Nov. 8, 2012 in U.S. Appl. No. 12/692,419, 20 pages. |
U.S. Office Action dated Mar. 18, 2013 in U.S. Appl. No. 12/758,901, 12 pages. |
Canadian Office Action dated Mar. 21, 2013 in Application No. CA 2,637,946, 5 pages. |
U.S. Office Action dated May 29, 2013 in U.S. Appl. No. 12/692,419, 17 pages. |
U.S. Office Action dated Jul. 19, 2013 in U.S. Appl. No. 12/758,901, 18 pages. |
U.S. Office Action dated Jan. 3, 2014 in U.S. Appl. No. 12/692,419, 10 pages. |
U.S. Notice of Allowance dated Mar. 3, 2014 in U.S. Appl. No. 12/692,419, 9 pages. |
Chinese Office Action dated Mar. 19, 2014 in Application No. CN 201110360158.6, 16 pages. |
U.S. Office Action dated Aug. 1, 2014 in U.S. Appl. No. 12/758,901, 21 pages. |
European Office Action dated Sep. 2, 2014 in Application No. 07757700.5, 5 pages. |
U.S. Notice of Allowance dated Oct. 20, 2014 in U.S. Appl. No. 12/758,901, 31 pages. |
European Office Action dated Feb. 24, 2015 in Application No. 06786463.7, 6 pages. |
Anonymous: “SVG.Open/Carto.net 2002, Zurich, SVG as a Page Description Language”, Feb. 18, 2015, XP055170440, Retrieved from the Internet: URL: http://www.svgopen.org/2002/papers/danilo—fujisawa—svg—as—page—description—language/ [retrieved on Deb. 18, 2015], 11 pages. |
Number | Date | Country | |
---|---|---|---|
20070206209 A1 | Sep 2007 | US |
Number | Date | Country | |
---|---|---|---|
60778410 | Mar 2006 | US |