UNITED STATES PATENT AND TRADEMARK OFFICE
`
`____________________
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`_____________________
`
`LIGHTSPEED COMMERCE INC.,
`
`Petitioner,
`
`v.
`
`CLOUDOFCHANGE, LLC,
`
`Patent Owner.
`
`______________________________
`
`Case IPR2022-00997
`
`Patent 10,083,012
`
`DECLARATION OF STEPHEN B. ACKERMAN
`
`

`

`DECLARATION
`
`
`
`I, Stephen B. Ackerman, declare as follows:
`
`1.
`
`I am an attorney at Saile Ackerman LLC located at 28 Davis Avenue,
`
`Poughkeepsie, New York 12603. I am admitted to practice before United States
`
`Patent and Trademark Office (USPTO), and my registration number is 37,761. I
`
`am a member of the bar of the State of New York, and my registration number is
`
`2723351. I have personal knowledge of the matters stated in this declaration and
`
`would testify truthfully to them if called upon to do so.
`
`2.
`
`I was the attorney in charge of handling the prosecution of the
`
`following patent applications:
`
`Pub. Date
`
`Patent
`No.
`N/A
`
`N/A
`
`N/A
`
`Attorney
`Docket
`Number
`TY06-001
`
`TY06-002
`
`TY06-003
`
`9,400,640
`
`TY06-004
`
`App. No. Filing Date Patent Pub. Patent No.
`
`11/710,722
`Feb. 26,
`2008/0208696 Aug. 28,
`2007
`2008
`Feb. 26,
`2008/0208698 Aug. 28,
`2007
`2008
`Feb. 1,
`2009/0198595 Aug. 6,
`2008
`2009
`Feb. 5,
`2009/0199154 Aug. 6,
`2008
`2009
`
`
`
`11/710,723
`
`12/012,393
`
`12/012,666
`
`
`3.
`
`Attached as Exhibit A1 is a true and correct copy of a picture taken on
`
`July 14, 2022 of the case file folder associated with U.S. Patent Application No.
`
`11/710,722 (attorney docket number TY06-001) that my law firm has kept in its
`
`custody since the initiation of the case.
`
`

`

`4.
`
`Attached as Exhibit A2 is a true and correct copy of U.S. Publication
`
`No. 2008/0208696 for U.S. Patent Application No. 11/710,722.
`
`5.
`
`Attached as Exhibit B1 is a true and correct copy of a picture taken on
`
`July 14, 2022 of the case file folder associated with U.S. Patent Application No.
`
`11/710,723 (attorney docket number TY06-002) that my law firm has kept in its
`
`custody since the initiation of the case.
`
`6.
`
`Attached as Exhibit B2 is a true and correct copy of U.S. Publication
`
`No. 2008/0208698 for U.S. Patent Application No. 11/710,723.
`
`7.
`
`Attached as Exhibit C1 is a true and correct copy of a picture taken on
`
`July 14, 2022 of the case file folder associated with U.S. Patent Application No.
`
`12/012,393 (attorney docket number TY06-003) that my law firm has kept in its
`
`custody since the initiation of the case.
`
`8.
`
`Attached as Exhibit C2 is a true and correct copy of U.S. Publication
`
`No. 2009/0198595 for U.S. Patent Application 12/012,393.
`
`9.
`
`Attached as Exhibit D1 is a true and correct copy of a picture taken on
`
`July 14, 2022 of the case file folder associated with U.S. Patent Application No.
`
`12/012,666 (attorney docket number TY06-004) that my law firm has kept in its
`
`custody since the initiation of the case.
`
`10. Attached as Exhibit D2 is a true and correct copy of U.S. Patent No.
`
`9,400,640 which issued from U.S. Patent Application No. 12/012,666.
`
`

`

`11. Attached as Exhibit E is a true and correct copy of the Patent
`
`Assignment Cover Sheet and Assignment Documents recorded with the USPTO on
`
`March 2, 2017.
`
`12. Attached as Exhibit F is a true and correct copy of an invoice I
`
`provided to my client on March 6, 2007 in connection to filing the patent
`
`applications in Exhibits A2 and B2.
`
`13. At the time of opening the case numbers associated with Exhibits A1,
`
`B1, C1, and C2, my firm’s case file naming convention uses (at least) the first two
`
`letters of a client’s name at the front of our attorney docket number. For these
`
`cases, the Attorney Docket Numbers all start with “TY.” My firm continues to use
`
`the same naming convention.
`
`14. At the time of filing each of the patent applications described in
`
`paragraphs above, it was my understanding that any resulting issued patent from
`
`these patent applications would be assigned to the same person or entity.
`
`15. On the cover of the case file folders in Exhibits A1, B2, C1, and D1, I
`
`noted that the assignee would be “TYRAMM International Inc.”
`
`16. On the cover of the case file folders in Exhibits A1, B2, C1, and D1, I
`
`crossed off the assignee instruction (to “TYRAMM International Inc.”) after being
`
`corrected by the client that, although any issued patent would be assigned to the
`
`same entity, that entity would not be “TYRAMM International Inc.”
`
`

`

`17. The following patent applications were abandoned, and therefore did
`
`not issue as patents: Patent Application Nos. 11/710,722; 11/710,723; and
`
`12/012,393. Thus, I did not prepare assignment documents or an Assignment
`
`Cover Sheet for any of these abandoned patent applications.
`
`18. U.S. Patent Application No. 12/012,666 issued as U.S. Patent
`
`No. 9,400,640 (the “’640 Patent) on July 26, 2016. Thus, I prepared assignment
`
`documents for the inventors/assignors: Mr. Wayne Baratta and Mr. Quentin Olson.
`
`19. An assignment of the ’640 Patent was executed by the assignors,
`
`Mr. Wayne Baratta and Mr. Quentin Olson, to the assignee, CloudofChange, LLC,
`
`on the following dates:
`
`Execution Date
`Jan. 31, 2017
`Feb. 1, 2017
`
`Recorded Date
`Mar. 2, 2017
`Mar. 2, 2017
`
`Assignee
`Assignor
`Wayne Baratta CloudofChange, LLC
`Quentin Olson CloudofChange, LLC
`
`
`20.
`
`I filed a Patent Assignment Cover Sheet with the executed assignment
`
`documents for the ’640 Patent (Exhibit E) on March 2, 2017.
`
` understand that willful false statements and the like are punishable by fine
`
` I
`
`or imprisonment, or both (18 U.S.C. § 1001) and may jeopardize the validity of the
`
`application or any patent issuing thereon. All statements made of my own
`
`knowledge are true and all statements made on information and belief are believed
`
`to be true. I declare under the penalty of perjury that the foregoing is true and
`
`

`

`coffect to the best of my knowledge and that this declaration was executed on this
`
`22nd day of July 2022 in Poughkeepsie, New York.
`
`Stephen B. Ackerman
`
`5
`
`

`

`EXHIBIT A1
`EXHIBIT Al
`
`CloudofChange 2015 7 of 58
`Clover Network, LLC v. CloudofChange, LLC
`IPR2023-00287
`
`

`

`IPR2023-00287
`
`CloudofChange 2015 8 of 58
`Clover Network, LLC v. CloudofChange, LLC
`
`
`
`

`

`EXHIBIT A2
`EXHIBIT A2
`
`CloudofChange 2015 9 of 58
`Clover Network, LLC v. CloudofChange, LLC
`IPR2023-00287
`
`

`

`(19) United States
`(12) Patent Application Publication (10) Pub. No.: US 2008/0208696A1
`Olson
`(43) Pub. Date:
`Aug. 28, 2008
`
`US 20080208696A1
`
`(54) POINT OF SALE SYSTEM WITH WEB-BASED
`BACK-OFFICE
`
`(52) U.S. Cl. .......................................................... 705/16
`
`Quentin Olson, Poulsbo, WA (US)
`(76) Inventor:
`Correspondence Address:
`George O Saile and Assocs
`28 Davis Ave
`Poughkeepsie, NY 12603
`1
`)
`(21) Appl. No.:
`
`11/710,722
`
`(22) Filed:
`
`Feb. 26, 2007
`Publication Classification
`
`(51) Int. Cl.
`G06O 10/00
`
`(2006.01)
`
`ABSTRACT
`(57)
`This invention provides a system and a method for managing
`a range of businesses. The business operations range from a
`single branch to a large chain of stores or branches. This
`invention relates to the managing of the points of sale (POS)
`with Web-based back-office systems. POS transaction engine
`terminals are implemented on personal computer, PC hard
`ware using PC software with a relational database. The trans
`action engine architecture provides cost-effective application
`customization. Web-based back-office software is imple
`mented on servers. POS and BO systems are monitored and
`Supported via the web using protocol and open Software com
`ponents.
`
`Points of Sale in Stores &
`Back Office Seruer on the Web
`
`
`
`
`
`POS f
`
`POS 2
`
`POS 1
`
`POS 2
`
`Store 1
`
`Store 1
`
`Store 2
`
`Store 2
`
`21
`
`
`
`
`
`
`
`
`
`Retto t e PC
`Uth, Web
`OCC 2 SS
`
`22
`
`HTTP
`protocal
`to Web
`
`Back office implemented on various
`Web Se ryers
`
`24
`
`

`

`Patent Application Publication
`
`Aug. 28, 2008 Sheet 1 of 3
`
`US 2008/020869.6 A1
`
`d.L.I.H.
`
`1000 q oud
`QaÁM O 4
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`? sau o QS u? a 1 oS fo s? w? och
`qaM
`at?, uo uanuaS a o?.
`/.../ O 30 og
`
`? SOd?
`
`? SOCH
`
`2 240 4S
`
`| 9.104'S
`
`22! 2
`
`S.M.8
`(),
`laS Q2M
`sno?
`uton, wo pa quatua 1 d'u?, a o y ffo3,
`otoq
`
`/ º :) I , H.
`
`Þ2S S 2 0 0?O
`
`

`

`Patent Application Publication
`
`Aug. 28, 2008 Sheet 2 of 3
`
`US 2008/020869.6 A1
`
`Point of Sale Software (one store)
`
`20
`
`Core Transaction Engine
`
`Configurable Modules
`
`FI C. 2
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Is this a valid
`operation?
`
`Does user houe
`the Prive lege?
`
`Call PoSEuent
`uirtual method
`
`
`
`FI C. 3
`
`Stort
`Manager
`Ouerride
`Dialog
`
`

`

`Patent Application Publication
`
`Aug. 28, 2008 Sheet 3 of 3
`
`US 2008/020869.6 A1
`
`
`
`fz º f) / , H.
`
`
`
`
`
`
`
`
`
`->
`
`N a -1.0 || S. • No.
`
`

`

`US 2008/020869.6 A1
`
`Aug. 28, 2008
`
`PONT OF SALE SYSTEM WITH WEB-BASED
`BACK-OFFICE
`
`RELATED PATENT APPLICATION
`0001. This application is related to docket number
`TY2006-002, filed on
`, Ser. No.
`, which is
`herein incorporated by reference in its entirety.
`
`BACKGROUND OF THE INVENTION
`0002 1. Field of the Invention
`0003. This invention relates to a system and an apparatus
`for managing a range of businesses. The business operations
`range from a single branch to a large chain of stores or
`branches.
`0004 More particularly this invention relates to the man
`aging of the points of sale (POS) with Web-based back-office
`systems.
`0005 2. Description of Related Art
`0006 Currently, point of sale (POS) functions are imple
`mented with custom hardware and/or custom software in the
`stores or business branches. In addition, custom Software is
`currently used for server functions. Today, servers are
`required to be located in each store or branch for normal mode
`operation, and for a backup mode of operation, which is
`needed if the servers go down. The disadvantages of current
`practice are that store and branch changes require time and
`money for software development and testing. In addition,
`current practice has weak scalability and requires significant
`technical skill to manage the in-store components. As POS
`terminals are added within a store or branch or as stores or
`branches are added, the performance of the overall system
`degrades. Another disadvantage of current practice is the use
`of non-standard protocols. Many of these non-standard pro
`tocols were implemented before the availability of PC hard
`ware and software and before the widespread use of universal
`web protocols. Consequently, current practice includes pro
`prietary protocols which were implemented earlier, but their
`continued operation is required to enable enterprises to pre
`serve the large investment in proprietary business operations
`and systems.
`0007 U.S. Pat. No. 4,679,154 (Blanford) describes a
`checkout System for processing purchased merchandise
`items. The system includes a checkout counter which con
`tains a scanning assembly for scanning a coded label on the
`purchased item to produce data signals identifying the item
`purchased, a display member on the counter for displaying
`the price of the merchandise item purchased, an indicator
`light and a tone generator located in the display member, a
`back-office processor for obtaining the price of the merchan
`dise item, and a data terminal device for printing the price of
`the scanned items on a record member.
`0008 U.S. Pat. No. 6,856,970 B1 (Cambell et al.) dis
`closes a financial transaction system which allows clients of a
`financial institution to use a web-based workstation to inter
`face with a plurality of back-office systems within one or
`more financial institutions. This system comprises a hub
`server, a plurality of financial institutions, at least one web
`server, and at least one database server.
`0009 U.S. Pat. No. 6,504,481 B2 (Teller) describes a sys
`tem, method, and device for monitoring the dispensing of
`liquids, in particular, beverages dispensed at a bar or restau
`rant. The system includes an electronic sensor device, data
`receiver, personal computer, bottle opener/camera system,
`
`bar code scanner, point of sale, bar camera, network, Web
`server, and paging system. The method automatically detects
`and monitors dispensing events, including detecting the type
`and amount of liquid, reconciling dispensing events with
`register ring-ups, recording information, saving video spe
`cific to the dispensing event, and sending a page indicating
`anomalies.
`
`BRIEF SUMMARY OF THE INVENTION
`0010. It is the objective of this invention to provide a
`system and a method for a system and an apparatus for man
`aging a range of businesses. The business operations range
`from a single branch to a large chain of Stores or branches.
`This invention relates to the managing of the points of sale
`(POS) with Web-based back-office systems.
`0011. It is further an object of this invention to the manage
`the points of sale (POS) with Web-based back-office systems.
`0012. The objects of this invention are achieved by point
`of sale system with a web-based back-office system com
`prised of one or more point of sale (POS) terminals and one or
`more web servers. The POS terminals and web servers com
`municate via commonly used, standardized internet proto
`cols. The POS terminals are implemented with personal com
`puter hardware and software using one or more relational
`databases. The web server is implemented with web server
`hardware and Software, also using one or more relational
`databases.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`0013 FIG. 1 shows a high level diagram of this invention.
`0014 FIG. 2 gives a high level diagram of a point of sale
`(POS) terminal.
`0015 FIG.3 gives a core transaction engine/configurable
`module flow chart.
`0016 FIG. 4 is a more detailed diagram of a main embodi
`ment of this invention.
`
`DETAILED DESCRIPTION OF THE INVENTION
`0017 FIG. 1 shows a high level diagram of this invention.
`Each point of sale (POS) terminal such as POS 21 represents
`a single cash register in a store, retail location, or business
`location. POS 21 is in STORE 1 and POS 2 (22) is in store 2.
`Each POS includes personal computer hardware and soft
`ware. Additional POS terminals beyond the two shown, as
`well as additional stores beyond the two shown, are within the
`scope of the invention. Each POS normally operates with a
`hardware/software connection 23 to the Internet or Web.
`However, if the web goes down, the POS terminal continues
`to operate. There is a loose coupling of the POS to the back
`office (BO). The POS to BO connection is not required for the
`basic business functions of the POS. All transaction data is
`stored in a relational database on the hard drive in the POS.
`0018. A relational database stores all of its data inside
`tables. All operations on data are done on the tables them
`selves. Some operation produce other tables as the result. A
`table is a set of rows and columns. Each row is a set of
`columns with only one value for each. All rows from the same
`table have the same set of columns, although some columns
`may have NULL values. A NULL value is an “unknown”
`value. The rows from a relational table are analogous to a
`record, and the columns are analogous to a field. Below is an
`example of a relational table.
`
`

`

`US 2008/020869.6 A1
`
`Aug. 28, 2008
`
`NAME
`
`COMPANY
`
`E MAIL
`
`Jane A. Doe
`Bill X. Smith
`
`ABC
`XYZ
`
`jad(e)abc.com
`bXS(axy Z.com
`
`There are two basic operations one can perform on a rela
`tional table. The first one is retrieving a subset of its columns.
`The second is retrieving a subset of its rows. The field names
`Such as company describe the content of the columns of the
`relational table. The rows delineate the individual records
`stored in the relational tables.
`0019. As transactions are created at a POS a log entry for
`the newest transaction is also created, this log entry is used to
`flag if the transaction has been uploaded to the web server.
`Part of the POS application, the BO interface is continuously
`running in the background. This component reads the log of
`transactions. If a transaction needs to be sent, it tries to send
`it. If the send fails (for example, if the connection to, or the
`Internet itself, is down), it goes to sleep and tries again later.
`Additionally, the BO interface requests update from the BO
`Such as new items, price changes, employees, etc. The POS
`terminals communicate via HTTP protocol (hypertext trans
`fer protocol) 23 with Back-office BO software, which is
`implemented on web servers 24, which can be located any
`where in the world. In addition, the BO software and data can
`be viewed from any store employee at any PC who has Inter
`net access 26 and a password.
`0020. The POS such as 21 send transaction data to the BO
`in the form of an HTTP post or communication. The packet 23
`sent from the POS to the BO consists of transactions,
`employee clock, customer add/update, item add/update, pro
`motions and more. Promotions are configured in the back
`office and associated with items or customers or departments.
`For example, a promotion may be associated with a customer
`to implement customer loyalty points or a promotion may be
`associated with a certain item for a % discount. A client who
`is the store manager or owner selects a promotion type, asso
`ciates it with an item, department, etc, then sets the param
`eters that control how that promotion works. These transac
`tion transmissions between the POS and the BO can be
`encrypted to insure privacy and security. A typical encryption
`method is 128 bit SSL (secure sockets layer). A further ele
`ment of security is that each BO client (individual POS, store
`or multi-store owner) gets their own instance of a database.
`When they log into the BO they are attached to their own
`relational database associated and validated via their user
`login and password.
`0021
`FIG. 2 is a high-level diagram of a POS terminal 10.
`There is a core transaction Engine 20 which is software which
`processes all input and output at the POS terminal and invokes
`the appropriate retail logic. The core transaction engine inter
`faces with configurable modules 30, which handle the mean
`ing & processing steps of terminal keys required. For
`example, one business or one store may require a different
`function performed by the transaction engine when the
`“Total key on the POS terminal is pressed. A convenience
`store may have a different way of computing the Summation
`of taxable items than a restaurant business. These config
`urable modules allow the POS terminal to be very flexible for
`use by many different types of Stores and businesses.
`0022. An example of a promotion which requires some
`level of configuration information is "Buy 1 and get one free
`
`or buy 1 and get the second 50% off. Typically, these con
`figurable modules are preferably implemented in a computer
`language Such as JAVA which is a combined compile and
`interpretive language. The use of a JAVA-type object-oriented
`language allows the dynamic loading of executable config
`urable modules at run-time to handle things such as different
`operations of the “Total key, without changing the other
`transaction engine modules. Other examples of transaction
`engine modules are Cash Tender module and Sub-Total mod
`ule. This allows an efficient, low labor, low cost method of
`implementing different POS terminal functions.
`0023 FIG. 3 is a flowchart showing how core transaction
`Software could process a given key press action 11. This key
`press action 11 could be associated with one of the several
`keys on a point of sale terminal keyboard, touch screen or
`touch pad. The core transaction engine asks 12 if this key
`press action is a valid operation in the current state of the POS
`machine. If it is not 13, the user is warned via an indicator or
`message on the POS screen. If it is valid, the core transaction
`asks if the user has privilege 14. If the user does not have
`privilege, the transaction engine starts the manager override
`dialog 15, which asks the user for more information in order
`to gain access. If the user does have privilege, the transaction
`engine calls a configurable module 16 called the Poshvent
`virtual method to handle the required meaning of the key
`press action. After handling the tasks associated with the key
`press, the transaction engine returns control 17 back to the key
`press 11.
`0024. The POS transaction is engine designed to allow
`easy extension of retail business logic through Java dynamic
`class loading. For example, if an end user wants to modify the
`way the “Total Key operates they only need to sub-class an
`abstract class (Posvent) and make it available to the Java
`class loader. No other piece of code requires modification.
`The system accomplishes this design through a layered archi
`tecture. At the bottom is the POS context and electronic
`journal. These make up the core POS transaction engine by
`binding together the user context, system parameters and the
`transaction-processing engine. POS events interact with
`hardware and the core engine to accomplish the business
`logic. A hardware layer abstracts the POS events and the
`physical and virtual devices (key presses, peripheral I/O.
`input/output). Hardware abstraction classes manage receipt
`(or spooled) device I/O, interactive I/O (operator prompts)
`and peripherals that invoke business logic directly (Such as
`cash drawer close). The design utilizes an event model famil
`iar to most GUI application programmers. A listener is reg
`istered for events and these events are processed using classes
`derived from the base (virtual) PosFvent class. The POS event
`may be invoked or triggered in one of three ways: 1) Directly
`from a key press/GUI (graphical user interface) button press
`as shown in FIG. 3, 2) from a device event (credit card swipe,
`barcode scan, etc.), direct I/O or status change from JavaPOS
`devices or 3) programmatically from within other Poshvent
`derived classes or a dialog. An example of a dialog is shown
`in FIG. 3. A Start Manager override dialog box 15 is shown.
`This dialog box helps the system to determine ifa user should
`be able to trigger the POS event 16 even though the user does
`not have “privilege' rights to do so.
`0025 FIG. 4 is a more detailed diagram of the main
`embodiment of this invention. Stores 31, 32 illustrate several
`POS implemented with Java software using relational data
`bases. The boxes 31, 32 in FIG. 4 show each POS having its
`own relational database. This architecture offers an element
`
`

`

`US 2008/020869.6 A1
`
`Aug. 28, 2008
`
`of security. Each BO client, which is an individual POS gets
`their own instance of a database. When they log into the BO
`they are attached to their own relational database associated
`and validated via their user login and password.
`0026 Web Server 36 illustrates a BO implemented with
`Apache PHP using relational databases. PHP (recursive acro
`nym for “PHP: Hypertext Preprocessor) is a widely-used
`Open Source general-purpose Scripting language that is espe
`cially suited for Web development and can be embedded into
`HTML (hypertext markup language). Apache is a web server
`currently used in over half of all web sites worldwide. PHP
`code is different from a script written in other languages like
`Perl or C. Instead of writing a program with lots of commands
`to output HTML, one can write an HTML script with some
`embedded code to do something (ie. to output some text). The
`PHP code is enclosed in special start and stop tags that allow
`you to jump into and out of “PHP mode'. What distinguishes
`PHP from something like client-side JavaScript is that the
`code is executed on the server. If you were to have HTML
`script with PHP code imbedded in it, the client would receive
`the results of running that Script, with no way of determining
`what the underlying code may be. You can even configure
`your web serverto process all your HTML files with PHP. The
`advantages of using PHP are that it is extremely simple for a
`newcomer, free to use, but offers many advanced features for
`a professional programmer. A programmer can jump in and in
`a short time start writing simple Scripts. Remote and local
`web browsers 33 illustrate a method used by store managers,
`corporate administrators, or system administers to access and
`view a company & its store's instantaneous performance from
`minute to minute. The POS, BO, and Web Browsers all com
`municate via the Web. 34. The protocols between the POS and
`Web browsers and BO servers is HTTPs, XMURPC. 35.
`XML-RPC is a remote procedure call protocol which uses
`XML to encode its calls and HTTP as a transport mechanism.
`It is a very simple protocol which defines only a handful of
`data types and commands.
`0027. The key advantages of this point of sale system with
`a web-based back-office system are as follows. The web and
`PC architecture both offer full-scalability which results in
`improved performance and lower cost. There is a lower cost
`associated with projects developed with the technology of
`this invention due to the flexibility of easy design changes and
`well-understood software. There is less training required for
`programmers and system testers. Projects can draw on the
`huge talent pool in the open source development community.
`The inventionallows configurable modules for different types
`of businesses and sales promotions. The invention allows
`remote monitoring of both the POS and back-office systems
`from anywhere via the web. There is minimal time required
`for POS installation, since POS setup is as basic as a home PC
`setup. Another advantage is that the back-office system can be
`provided as a service or deployed within a corporation. For
`example, Software as a Service (SAAS) is a software distri
`bution model in which applications are hosted by a vendor or
`service provider and made available to customers over a net
`work, typically the Internet. Another advantage of this inven
`tion is that the back-office system is maintained in customer
`centric databases, making it impossible for customers to see
`other's data. Each BO client (individual POS, store or multi
`store owner) gets their own instance of a database. When they
`log into the BO they are attached to their own relational
`database associated and validated via their user login and
`password.
`
`0028. While this invention has been particularly shown
`and described with Reference to the preferred embodiments
`thereof, it will be understood by those Skilled in the art that
`various changes in form and details may be made without
`Departing from the spirit and scope of this invention.
`What is claimed is:
`1. A point of sale system with a web-based back-office
`System, comprising:
`one or more point of sale, POS, terminals and
`one or more web servers,
`wherein said POS terminals and said web servers commu
`nicate via internet protocols,
`wherein said POS terminals are implemented with per
`Sonal computer hardware and Software using one or
`more relational databases,
`wherein said web server is implemented with web server
`hardware and Software, using one or more relational
`databases.
`2. The point of sale system with a web-based back-office
`system of claim 1 wherein said POS terminals and said web
`servers are implemented with executable, configurable soft
`ware modules, wherein said modules can be easily changed to
`implement different functions for different businesses.
`3. The point of sale system with a web-based back-office
`system of claim 1, wherein said POS terminals can operate
`standalone without communicating with said web server.
`4. The point of sale system with a web-based back-office
`system of claim 1, wherein said POS system and said web
`based back-office servers are scalable allowing the addition
`of POS terminals and business locations without degrading
`system performance.
`5. The point of sale system with a web-based back-office
`system of claim 1, wherein a real-time status of said POS
`terminals and said back-office web servers is obtained at
`remote locations via personal computers with browser based
`web access.
`6. A web-based back-office system comprising:
`one or more web servers,
`wherein said web servers are implemented with web server
`hardware and Software, using one or more relational
`databases,
`wherein said web servers can communicate with point of
`sale, POS, terminals via internet protocols.
`7. The web-based back-office system of claim 6, wherein
`said web servers are implemented with executable, config
`urable software modules, wherein said modules can be easily
`changed to implement different functions for different busi
`SSS.
`8. The web-based back-office system of claim 6, wherein
`said web servers allow said POS terminals to operate standa
`lone without communicating with said web servers.
`9. The web-based back-office system of claim 6, wherein
`said web-based back office is scalable allowing the addition
`of POS terminals and business locations without degrading
`system performance.
`10. The web-based back-office system of claim 6, wherein
`a real-time status of said POS terminals and/or said back
`office system is obtained at remote locations via personal
`computers with browser based web access.
`11. A point of sale POS system comprising,
`one or more point of sale, POS, terminals,
`wherein said POS terminals can communicate with web
`servers via internet protocols,
`
`

`

`US 2008/020869.6 A1
`
`Aug. 28, 2008
`
`wherein said point of sale terminals are implemented with
`personal computer hardware and Software, using one or
`more relational databases.
`12. The point of sale POS system of claim 11, wherein said
`POS terminals are implemented with executable, config
`urable software modules, wherein said modules can be easily
`changed to implement different functions for different busi
`SSS.
`13. The point of sale POS system of claim 11, wherein said
`POS terminals can operate standalone without communicat
`ing with said web servers.
`14. The point of sale POS system of claim 11, wherein said
`POS system are scalable allowing the addition of POS termi
`nals and business locations without degrading system perfor
`aCC.
`15. The point of sale POS system of claim 11, wherein a
`real-time status of said POS terminals and/or said back-office
`web servers is obtained at remote locations via personal com
`puters with browser based web access.
`16. A method of providing a point of sale system with a
`web-based back-office system, comprising the steps of
`providing one or more point of sale, POS, terminals and
`providing one or more web servers,
`wherein said POS terminals and said web servers commu
`nicate via internet protocols,
`wherein said POS terminals are implemented with per
`Sonal computer hardware and software using one or
`more relational databases,
`wherein said web server are implemented with web server
`hardware and Software, using one or more relational
`databases.
`17. The method of providing a point of sale system with a
`web-based back-office system of claim 16 wherein said POS
`terminals and said web servers are implemented with execut
`able, configurable software modules, wherein said modules
`can be easily changed to implement different functions for
`different businesses.
`18. The method of providing a point of sale system with a
`web-based back-office system of claim 16, wherein said POS
`terminals can operate standalone without communicating
`with said web server.
`19. The method of providing a point of sale system with a
`web-based back-office system of claim 16, wherein said POS
`system and said web-based back-office servers are scalable
`allowing the addition of POS terminals and business locations
`without degrading system performance.
`20. The method of providing a point of sale system with a
`web-based back-office system of claim 16, wherein a real
`time status of said POS terminals and said back-office web
`servers is obtained at remote locations via personal comput
`ers with browser based web access.
`
`21. A method of providing a web-based back-office system
`comprising the steps of
`providing one or more web servers,
`wherein said web servers are implemented with web server
`hardware and Software, using one or more relational
`databases,
`wherein said web servers can communicate with point of
`sale, POS, terminals via internet protocols.
`22. The method of providing a web-based back-office sys
`tem of claim 21, wherein said web servers are implemented
`with executable, configurable software modules, wherein
`said modules can be easily changed to implement different
`functions for different busin