US007051091B1
`
`(12) United States Patent
`Cohen et al.
`
`(10) Patent No.:
`(45) Date of Patent:
`
`US 7,051,091 B1
`May 23, 2006
`
`(54) REMOTE SYSTEM TO CONFIGURE
`MANAGEMENT CENTER OF POINT OF
`SALE TERMINALS
`
`(*) Notice:
`
`• A la
`w
`75
`(75) Inventors: Elle, yass Arie
`s
`y Yag
`(73) Assignee: Lipman Electronic Engineering Ltd.,
`Rosh Haayin (IL)
`0
`-
`Subject to any disclaimer, the term of this
`patent is extended or adjusted under 35
`U.S.C. 154(b) by 669 days.
`(21) Appl. No.: 09/710,171
`(22) Filed:
`Nov. 10, 2000
`Related U.S. Application Data
`(60) Provisional application No. 60/165.489, filed on Nov.
`15, 1999.
`
`O
`O
`Foreign Application Priority Data
`(30)
`Nov. 15, 1999 (IL)
`...................................... 132942
`(51) Int. Cl.
`"oal. 717/178: 705/26
`(52) sefir
`(58) Fi id f Cl- - - - - - ficati - - - - - -s
`h
`s
`709,227
`O SSCO Sea
`................
`s
`709/229, 217 222, 223-226, 201-205, 244:
`717/174–178; 705/26, 10, 14, 64; 345/744,
`345/746; 707/100 104.1, 501, 513; 713/200 201,
`713/235
`See application file for complete search history.
`References Cited
`
`(56)
`
`U.S. PATENT DOCUMENTS
`5.535.407 A * 7/1996 Yanagawa et al. ............ 705/39
`5,900.870 A
`5, 1999 Malone et al. .............. 345,333
`5.936.860 A
`8, 1999 Arnold et all
`364/468.01
`5,987,135 A 1 1/1999 Johnson et al. ............... 380.25
`6,016,957 A *
`1/2000 Ohki et al. ................. 235,380
`
`2/2000 Takahashi et al. .......... 455.426
`6,029,068 A
`3/2000 Hayafune et al. .....
`... 395,712
`6,041,183 A
`6, 195,694 B1* 2/2001 Chen et al. .......
`... 709.220
`6,311, 165 B1
`10/2001 Coutts et al. ................. 705/21
`6,466.972 B1 * 10/2002 Paul et al. ........
`... 709,222
`6,470,288 B1 * 10/2002 Keidel et al. .....
`... 702/122
`6,520,411 B1* 2/2003 Goodwin, III .............. 235/383
`6,532.435 B1* 3/2003 Aoshika et al. ............. 702/188
`6,615, 183 B1* 9/2003 Kolls .....
`... TOS/26
`6,738,749 B1* 5/2004 Chasko ..........
`... TO5, 17
`2001 OO15375 A1* 8, 2001 Swartz et al. .....
`... 235,383
`2001/00 16514 A1* 8, 2001 Walker et al. ................ 463/17
`2002/0077889 A1* 6/2002 Kolls .......................... TO5/14
`OTHER PUBLICATIONS
`Lipman Electronic Engineering, Ltd., NURIT CC Manage
`ment Software, pp. 1-15, Nov. 16, 1999.
`Lipman Electronic Engineering, Ltd., NURIT Control Cen
`ter (TCC), pp. 1-4, http://www.lipman.co.il/content/tc.html,
`Nov. 22, 2000.
`* cited by examiner
`
`Primary Examiner John Follansbee
`Assistant Examiner Haresh Patel
`(74) Attorney, Agent, or Firm-Ladas and Parry LLP
`(57)
`ABSTRACT
`A configuration builder useful in configuring Software
`containing hardware units which are serviced by a center
`which services a multiplicity of similar units having a
`plurality of different configurations, the configuration
`builder including:
`functionality enabling configuration of at least one soft
`ware-containing hardware unit by a configurer, and
`functionality operative automatically in response to con
`figuration of the at least one software-containing hard
`ware unit for correspondingly configuring the center,
`thereby to enable the center to interface with the at least
`one software-containing hardware unit.
`Methodologi
`d
`f sal
`lovi
`h
`ethodologies and point of sale systems employing the
`configuration building functionality are also disclosed.
`
`2 Claims, 9 Drawing Sheets
`
`
`
`
`
`
`
`
`
`APPLICATION
`
`APPLICATION
`PROGRAMMER
`
`INTEGRATED
`SN
`Air APPLICATION
`EDITING
`106
`
`130
`
`30
`
`POS
`TERNAL
`
`POS
`TERMINAL
`
`POS MANAGEMENT CENTER
`
`POS
`TERMINAL
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`CONFIGURATION
`BUILDER
`
`EDfING, CoMPILING
`BLE
`LINKING
`
`DEFINITIONS
`FILE
`
`
`
`FEBE E. STRUCTURE
`
`CENTER OPERATOR
`
`Lightspeed Ex. 1020.1
`
`

`

`TVNINGALLNAWASYNVA
`
`
`SdYUINGOININGOYNYNSOd
`
`
`‘TWNINGSLTWNINGSL
`SOdS0d
`OTOT
`LNdLN0/LAdNIWHINE.
`NONVOMdd¥=DNITIdNOD‘ONILIGA
`
`Vl‘Old
`(LUVword)
`=YINNVADONd
`adYAdVaH=22
`
`
`
`NOILVOFIdd¥1|CC];4aq09NOILVOMIdd¥
`
`
`axl=aSvavlvdy
`
`U.S. Patent
`
`May 23, 2006
`
`
`
`NVEO0UdYaLNA)
`
`Sheet 1 of 9
`
`US 7,051,091 B1
`
`daXld
`
`FANLONALS
`
`2]
`
`Lightspeed Ex. 1020.2
`
`ONDINTT
`
`
`<<eSi
`
`Lightspeed Ex. 1020.2
`
`
`
`
`
`

`

`U.S. Patent
`
`May23, 2006
`
`Sheet 2 of 9
`
`US 7,051,091 B1
`
`SOd
`
`
`
`
`
`WNINYGLTWNINYGLai
`
`oeteT
`
`
`
`NERDWORTHELD1on]
`SUALINVUVdAldYadvaH
`NOLLVOFTdd¥C4qq00_
`mecauvaoanl«=TWNINSSL
`SOdSOdC|=C1aaOmGl“Old
`
`
`
`LAdLNo/LAdNI0dIPOT¥I0148
`
`AUNLONULSSNOILINIAG
`aTaIXaApaYL
`NITdNOD‘ONILIGSYaCTING
`
`
`NINNITTrax
`SSryNOILVUNDINOD
`
`
`
`YOLVaddOWaLNao
`
`Td
`
`
`
`
`
`YaLNd)LNAWADVNVNSOd
`
`ONILIGA
`
`NOLLYORTddVINSNSYINOSYAH
`
`
`
`a)
`
`ADUNOSOT001
`
`NOILVOrIddV
`
`YaWNVad0dd
`
`Lightspeed Ex. 1020.3
`
`Lightspeed Ex. 1020.3
`
`
`
`
`
`

`

`U.S. Patent
`
`May 23, 2006
`
`Sheet 3 of 9
`
`US 7,051,091 B1
`
`DEFINE A NEW BLOCK NAME OF PARAMETERS
`FOR EACH POS APPLICATION PORTION
`
`DEFINE BLOCK TYPE: E.G. STRUCTURE, ARRA
`OF STRUCTURES, FILE, IMAGES
`
`DEFINE BLOCK APPLICABILITY (E.G. ALL TERMINALS,
`SINGLE POSTERMINAL, GROUP OF POSTERMINALS
`
`FG. 2
`
`FOR EACH BLOCK:
`DEFINE FIELDS TITLE
`DEFINE FIELDS TYPE
`
`ASSIGN INPUT WALUE TO EACH FIELD
`
`FOR EACH FIELD DEFINE DISPLAY FORMAT
`
`SOURCE CODE
`OF THE POS
`APPLICATION
`PORTION
`
`OUTPUT HEADER FILE FOR A POS
`APPLICATION PORTION
`
`BLOCK DEFINITION
`OUTPUT FILE FOR A
`POS APPLICATION
`PORTION
`
`
`
`COMPILATION
`AND LINKING
`
`POSTERMINAL
`APPLICATION FILE
`
`HW REQUIREMENTS INFORMATION
`AS THE POSTERMINAL
`
`TO POS
`INTEGRATED APPLICATION INCLUDING:
`MANAGEMENT
`-THE POSTERMINAL APPLICATION
`-PARAMETER STRUCTURE FOR THE POSTERMINAL CENTER 120
`APPLICATION
`-HW REQUIREMENT AT THE POSTERMINAL
`
`
`
`Lightspeed Ex. 1020.4
`
`

`

`U.S. Patent
`
`May 23, 2006
`
`Sheet 4 of 9
`
`US 7,051,091 B1
`
`FIG 3
`
`SELECT AN APPLICATION
`
`
`
`
`
`
`
`
`
`
`
`
`
`DISPLAY APPLICATION BLOCK FIELDS
`
`
`
`INSERT WALUES IN MERCHANT
`DEFINITION FIELDS
`
`INSERT WALUES IN TERMINAL
`DEFINITION FIELDS
`
`INSERT WALUES IN TRANSACTION
`DEFINITION FIELDS
`
`Lightspeed Ex. 1020.5
`
`

`

`U.S. Patent
`
`May23, 2006
`
`Sheet 5 of 9
`
`US 7,051,091 B1
`
`ul-sn|g VyOld
`
`
`
`
`
`
`some199d]LIaaG|pamonys]POOa49PLOJa]LSTOCA||Pssajoureredqa]suesedaNQON.S[qa]Lal|/aimanngsuredweal
`
`
`
`
`
`
`
`
`
`
`
`
`—_4epeAH|LNHOUN||ammyonsys|fopeaHWeyoreH]paanjons«IKNSOd,¥°014YSh|__INNSOd|INWSOd)||aamjonas
`
`
`
`pLa<-HNG]YLNGO|WLSoubdedpanos)siayaureredWpas9|wesedped]TLCaYO|NoaugMetedeIANvAH|q
`
`
`
`
`[among]ouene9qa]wgoust]yang9|srmjeuiezeg
`
`(sad‘Td‘Telsads)shayyon}=SAay10H]AALOH|
`
`aNX01jaweNWold|ous|ele]SS)
`
`woroa}o14PeofuMog)Tli<-L)Yd| LOolad|
`
`
`
`mls[slele
`
`St]syoojg
`
`Lightspeed Ex. 1020.6
`
`Lightspeed Ex. 1020.6
`
`
`

`

`U.S. Patent
`
`May 23, 2006
`
`Sheet 6 of 9
`
`US 7,051,091 B1
`
`
`
`
`
`Lightspeed Ex. 1020.7
`
`

`

`U.S. Patent
`
`May 23, 2006
`
`Sheet 7 Of 9
`
`US 7,051,091 B1
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Lightspeed Ex. 1020.8
`
`

`

`U.S.
`
`Patent
`
`May 23, 2006
`
`Sheet 8 of 9
`
`,051,091 B1
`US 7
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Lightspeed Ex. 1020.9
`
`

`

`U.S. Patent
`
`May 23, 2006
`
`Sheet 9 Of 9
`
`US 7,051,091 B1
`
`
`
`
`
`| <-i sâu?as
`
`
`
`
`
`$| ‘sueu], ales lød oleH
`
`
`
`
`
`
`
`
`
`Lightspeed Ex. 1020.10
`
`

`

`US 7,051,091 B1
`
`1.
`REMOTE SYSTEM TO CONFIGURE
`MANAGEMENT CENTER OF POINT OF
`SALE TERMINALS
`
`CROSS-REFERENCE TO RELATED
`PUBLICATIONS
`
`Applicant hereby claims priority of U.S. Provisional
`Patent Application Ser. No. 60/165.489, entitled “ADAP
`TIVE MANAGEMENT CENTER ESPECIALLY USED
`10
`FOR PONT OF SALE TERMINALS, filed Nov. 15, 1999.
`The material on the compact discs labeled COPY 1 and
`COPY 2 is incorporated by reference. The compact discs are
`identified in the LIST OF APPENDICES below.
`
`FIELD OF THE INVENTION
`
`15
`
`The present invention relates to point of sale systems
`generally.
`
`BACKGROUND OF THE INVENTION
`
`The following U.S. patents and other publications are
`believed to have possible relevance to the subject matter of
`the present invention: U.S. Pat. Nos. 6,041,183; 6,029,068;
`5,987,135; 5,936,860 & 5,900,870.
`A detailed explanation of the difference between the
`present invention and applicants own prior art, which is
`believed to be the closest prior art, is set forth hereinbelow
`in the Detailed Description of a Preferred Embodiment.
`
`25
`
`30
`
`SUMMARY OF THE INVENTION
`
`35
`
`40
`
`The present invention seeks to provide a configuration
`builder Suitable for use in configuring point of sale systems
`and a point of sale system and configuration methodology
`employing the configuration builder.
`There is thus provided in accordance with a preferred
`embodiment of the present invention a configuration builder
`useful in configuring Software-containing hardware units
`which are serviced by a center which services a multiplicity
`of similar units having a plurality of different configurations,
`the configuration builder including:
`functionality enabling configuration of at least one soft
`ware-containing hardware unit by a configurer; and
`45
`functionality operative automatically in response to con
`figuration of the at least one software-containing hardware
`unit for correspondingly configuring the center, thereby to
`enable the center to interface with the at least one software
`containing hardware unit.
`There is also provided in accordance with a preferred
`embodiment of the present invention, a configuration build
`ing method useful in configuring Software-containing hard
`ware units which are serviced by a center which services a
`multiplicity of similar units having a plurality of different
`configurations, the configuration building method including:
`enabling configuration of at least one software-containing
`hardware unit by a configurer, and
`automatically in response to configuration of the at least
`one software-containing hardware unit, correspondingly
`configuring the center, thereby to enable the center to
`interface with the at least one software-containing hardware
`unit.
`There is additionally provided in accordance with a
`preferred embodiment of the present invention a point of
`sale system including:
`a multiplicity of point of sale (POS) terminals;
`
`50
`
`55
`
`60
`
`65
`
`2
`at least one management centers which interact with the
`multiplicity of point of sale (POS) terminals; and
`a configuration builder useful in configuring the multi
`plicity of point of sale terminals, the configuration builder
`including:
`functionality enabling configuration of at least one soft
`ware-containing hardware unit by a configurer; and
`functionality operative automatically in response to con
`figuration of the at least one software-containing hardware
`unit for correspondingly configuring the center, thereby to
`enable the center to interface with the at least one software
`containing hardware unit.
`Preferably, the software-containing hardware units
`include point of sale terminals.
`In accordance with a preferred embodiment of the present
`invention, the center interfaces with the at least one soft
`ware-containing hardware unit for determining parameters
`of applications operative thereon.
`Preferably, the center interfaces with the at least one
`Software-containing hardware unit for determining param
`eters of applications operative thereon.
`In accordance with a preferred embodiment of the present
`invention the configuration includes programming of an
`application to run on the Software-containing hardware unit.
`Preferably, the configuration includes defining a plurality
`of block structures.
`In accordance with a preferred embodiment of the present
`invention, the configuration includes producing at least one
`flexible header file and at least one block definition file.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`The present invention will be understood and appreciated
`more fully from the following detailed description, taken in
`conjunction with the drawings in which:
`FIGS. 1A and 1B are simplified illustrations of prior art
`and present functionalities for configuring point of sale
`systems;
`FIG. 2 is a simplified flow chart of functionality for
`configuring point of sale systems operative in accordance
`with a preferred embodiment of the present invention;
`FIG. 3 is a simplified flow chart of functionality for
`utilizing the results of the functionality of FIG. 2;
`FIGS. 4A-4E are screen shots illustrating various stages
`in the functionality of FIGS. 2 & 3.
`
`LIST OF APPENDICES
`
`CD-ROM Appendix A includes software object code for
`carrying out a preferred embodiment of the invention.
`Appendix A is included on Copy 1 and Copy 2 of the
`CD-ROMs attached herewith to the present application.
`Each CD-ROM includes the file ADAPTMGT hex (Appen
`dix A) of Nov. 8, 2000 and of length 120,551,213 bytes.
`
`DETAILED DESCRIPTION OF A PREFERRED
`EMBODIMENT
`
`The present invention will now be described with refer
`ence to an environment of a point of sale system comprising
`one or more management centers which interact with a
`multiplicity of point of sale (POS) terminals. In order for the
`uniqueness of the present invention to be fully understood,
`assignee's prior art system and methodology is initially
`described hereinbelow with reference to FIG. 1A.
`As seen in FIG. 1A, in the prior art a multiplicity of POS
`terminals 10 communicate with a POS management center
`
`Lightspeed Ex. 1020.11
`
`

`

`US 7,051,091 B1
`
`5
`
`10
`
`15
`
`25
`
`30
`
`35
`
`3
`12. The POS terminals are typically NURIT terminals,
`commercially available from Lipman USA, Inc. of Syosset,
`N.Y., U.S.A. The POS management center 12 is typically a
`NURIT CC management center, also, commercially avail
`able from Lipman USA, Inc. Communication between POS
`terminals 10 and the POS management center 12 may be via
`a PSTN network or any other suitable wired or wireless
`communication network.
`As seen in FIG. 1A, one or more software programmers
`typically write source code, designated by reference numeral
`20 which, together with a fixed header file 22, is supplied to
`a computer system 24 which perform editing, compiling and
`linking thereof so as to provide applications 26.
`The POS management center 12 typically includes a
`management center program 28, which controls the func
`tionality of the management center 12, an applications
`database 30 which stores applications 26, a terminal param
`eters database 32, which stores parameters of various POS
`terminals 10 and a fixed input/output structure 34 which
`interfaces with the terminal parameters database 32 and
`requires a management center operator to enter parameters
`for given POS terminals in a fixed framework.
`In each POS terminal 10, there is provided, inter alia, an
`application file 40 which receives downloads from applica
`tions database 30 from time to time and a parameters file 42,
`which receives downloads from parameters database 32
`from time to time.
`In the prior art, every change made at the POS manage
`ment center 12 in the input/output structure 34 required that
`the applications programmers learn and understand the
`changed input/output structure in order to be able to write
`applications.
`Moreover, many of the changes made to the input/output
`structure 34 were the result of requests made by the appli
`cations programmers. The result was a never-ending cycle of
`reconfiguration and relearning, which involved significant
`cost and delay in implementation changes in POS terminal
`functionality.
`Furthermore, the POS management center operator was
`required to adapt previously set parameter settings to ensure
`40
`compatibility with changed parameter structures. When
`many changes in the parameter structure were being made
`and a great number of terminals were involved, the man
`agement burden on the POS management center operator
`became unbearable and uneconomic.
`Referring now to the present invention, illustrated in FIG.
`1B, it is seen that a configuration builder 100 constructed
`and operative in accordance with a preferred embodiment of
`the present invention is employed by an application pro
`grammer, preferably to write flexible header files 102 and
`block definitions files 104. Having written the flexible
`header files 102 and block definitions files 104, the software
`programmer writes source code 106 based on the structure
`defined in the flexible header files 102.
`The Source code 106 and the flexible header files 102 are
`supplied to computer system 108 which perform editing,
`compiling and linking thereof So as to provide applications
`110.
`Applications 110 are preferably then further processed by
`a computer system 112 which performs editing of the
`application to incorporate therewithin minimum hardware
`requirements at the POS terminal 130 for running the
`application. Typical hardware requirements include: mini
`mum memory capacity, minimum modem baud rate, display
`requirements and card reader requirements.
`The resulting integrated applications 114 are then Sup
`plied to a POS management center 120.
`
`50
`
`45
`
`55
`
`60
`
`65
`
`4
`The POS management center 120 typically includes a
`management center program 122, which controls the func
`tionality of the management center 120, an applications
`database 124 which stores applications 114, a terminal
`parameters database 126, which stores parameters of various
`POS terminals 130 and a flexible input/output structure 134
`which interfaces with the terminal parameters database 126
`and allows a management center operator to enter param
`eters for given POS terminals in a flexible framework.
`In accordance with a preferred embodiment of the present
`invention, the block definitions file 104 is supplied to a
`parameter structure and parameter entry screen database 136
`which stores a plurality of parameter entry screens which are
`used by the flexible input/output structure 134 for entry of
`parameters for given POS terminals 130 by a management
`center operator.
`Parameter entry screen database 136 interfaces with appli
`cations database 124, in order that the parameter structure
`and the parameter entry Screen shown to the management
`center operator is adapted to each given application.
`In each POS terminal 130, there is provided, interalia, an
`application file 140 which receives downloads from appli
`cations database 124 from time to time and a parameters file
`142, which receives downloads from parameters database
`126 from time to time.
`In contrast to the prior art, wherein every change made at
`the POS management center 12 in the input/output structure
`34 required that the applications programmers learn and
`understand the changed input/output structure in order to be
`able to write applications, in accordance with the present
`invention, most changes made at the POS management
`center 120 do not affect the work of the applications pro
`grammerS.
`Moreover, in accordance with the present invention and
`its flexible input/output structure 134, few or no changes
`need be made to the input/output structure 134 as a result of
`requests made by the applications programmers. This avoids
`the prior art never-ending cycle of reconfiguration and
`relearning, which involved significant cost and delay in
`implementation changes in POS terminal functionality.
`Furthermore, an operator of a POS management center
`120 is no longer required to adapt previously set parameter
`settings to ensure compatibility with changed parameter
`structures since each application is accompanied by a
`parameter structure adapted thereto.
`In the present invention, as distinguished from the prior
`art, every change made by the Software programmer in the
`application using the configuration builder is automatically
`reflected in the parameters structure stored in database 136,
`which automatically interfaces with the applications data
`base 124. This obviates the need for a POS management
`center operator to learn and understand the changed param
`eter structure in order to be able to configure each terminal.
`Furthermore, the POS management center operator is no
`longer required to adapt previously set parameter settings to
`ensure compatibility with changed parameter structures.
`When many changes in the parameter structure are being
`made and a great number of terminals are involved, the
`management burden on the POS management center opera
`tor resulting from Software changes to and developments in
`applications and parameter structures is minimized.
`Reference is now made to FIG. 2, which is a simplified
`flow chart of functionality for configuring point of sale
`systems operative in accordance with a preferred embodi
`ment of the present invention. A principal portion of the
`functionality of FIG. 4 takes place in the configuration
`
`Lightspeed Ex. 1020.12
`
`

`

`US 7,051,091 B1
`
`5
`builder 100 when employed by an application programmer.
`The remainder takes place in computer systems 108 and 112.
`The application programmer initially defines names of
`blocks of parameters for each portion of a POS application.
`Examples of Such blocks are include, for example, function
`alities for dealing with checks, credit purchases, debit pur
`chases, electronic benefit transfers (EBTs), electronic draft
`captures (EDCs), host-merchant transactions, man-machine
`interface functions.
`A screen shot, presenting, interalia, a listing of Such block
`names, appears in FIG. 4A.
`For each block defined by the application programmer,
`the programmer defines the type of block. Examples of types
`of blocks include, for example: structure, array, file and
`image. A typical structure applicable to a block relating to
`credit purchase functionalities includes the following
`parameters:
`minimum transaction amount;
`maximum transaction amount;
`host ID:
`communication protocol ID.
`A typical array comprises a plurality of structures.
`A typical file comprises, for example, a list of restricted
`credit cards.
`A typical image comprises a logo of a merchant or a
`header of a merchant's receipt.
`The application programmer may next define the appli
`cability of each block. For example, the block may impact
`only a single POS terminal, a single type of POS terminals,
`a group of POS terminals belonging to a certain customer or
`an entire class of functionalities of many types of POS
`terminals.
`A screen shot, presenting, interalia, a listing of selectable
`block attributes, including both the type of block and its
`applicability, appears in FIG. 4B.
`The application programmer preferably next defines the
`titles of fields for each block of parameters corresponding to
`each portion of a POS application. Typical field titles for a
`typical block Such as the block dealing with credit purchases
`include: host name, transaction type and help desk phone
`number. The type of the field is also preferably defined.
`Typical types of fields are: long, short and text.
`The application programmer then assigns to each field of
`each block of parameters a value which serves as an input to
`a portion of a POS application to which the field corre
`sponds.
`The application programmer also defines the display
`format of each field at the input/output structure 134 of the
`POS management center 120. For example, the display
`format may include display as a label and/or as a hint and
`may define the location of the field on a display provided by
`the input/output structure 134.
`A screen shot, presenting, interalia, field titles, field types
`and the values corresponding to a given field, appears in
`FIG 4C.
`At this stage, a header file, such as header file 102 (FIG.
`1B), is output by the configuration builder 100. Normally
`each header file corresponds to one block of an application.
`Also at this stage, a block definitions file, such as block
`definitions file 104 (FIG. 1B), is output by the configuration
`builder 100. Normally, each block definitions file 104 cor
`responds to one block of an application. The block defini
`tions file typically includes information relating to the block
`type, field titles, field types, field values and corresponding
`display formats therefor.
`As noted above, computer system 108 compiles and links
`the header file 102 for each given block with the source code
`
`40
`
`45
`
`6
`106 of the corresponding block of the POS application and
`produces an application. The resulting application 110 is
`Supplied to computer system 112 at which hardware require
`ments information is appended to the application.
`The resulting integrated application 114 includes the at
`least the following elements:
`the POS terminal application written by the application
`programmer without using the configuration builder 100:
`the parameter structure for the POS terminal application
`written by the application programmer using the configura
`tion builder 100 and the hardware requirements at the POS
`terminal which are added downstream of the work of the
`application programmer.
`The integrated application 114 is typically stored in
`applications database 124 in the POS management center
`120.
`Reference is now made to FIG. 3, which is a simplified
`flow chart of functionality for utilizing the results of the
`functionality of FIG. 2. The functionality of FIG. 3 is
`employed by a management center operator to configure a
`given POS terminal 130, having a given hardware configu
`ration, for a given application and also to establish a basis for
`management communication between that terminal and the
`management center 120.
`As seen in FIG. 3, once all necessary integrated applica
`tions have been received in database 124 of the POS
`management center 120, a management center operator may
`select one or more given applications stored in database 124.
`Upon selecting a given application, the operator is presented
`by the input/output structure 134 (FIG. 1B) with one or more
`screens, earlier defined by the application programmer using
`the configuration builder 100 (FIG. 1B) in order to adapt the
`selected application to a given POS terminal 130.
`Typically, the management center operator may select an
`application, Such as a restaurant application and may wish to
`adapt it to a given branch of a restaurant chain at a given
`location, having a given POS terminal hardware configura
`tion. A screen shot of the type presented to the management
`center operator at this stage, appears in FIG. 4D.
`Typically the management center operator inserts values
`into fields of application blocks, relating for example to
`merchant definition, terminal definition, transaction defini
`tion.
`Examples of such fields relating to merchant definition
`include: host merchant ID, merchant location, merchant
`telephone number.
`Examples of such fields relating to terminal definition
`include: terminal ID, terminal software ID and terminal
`hardware configuration ID.
`Examples of Such fields relating to transaction definition
`include: credit transaction capability YES/NO, check trans
`action capability YES/NO. . . . .
`A screen shot corresponding to that of FIG. 4D showing
`entry of various parameter values appears in FIG. 4E.
`It is appreciated that using the functionality of FIG. 3,
`which is predicated on the functionality of FIG. 2, the
`management center operator is enabled to easily configure
`disparate types of POS terminals 130 having disparate
`Software and hardware configurations for disparate specific
`applications and operating environments.
`Reference is now made to CD-ROM Appendix A, which
`includes Software object code for carrying out a preferred
`embodiment of the invention. This code may be operated by
`installation thereof in accordance with the following instal
`lation instructions:
`1) Provide a computer terminal, such as an Intel-based
`Pentium III 550 Mhz computer, 128 Mbyte RAM, 1
`
`10
`
`15
`
`25
`
`30
`
`35
`
`50
`
`55
`
`60
`
`65
`
`Lightspeed Ex. 1020.13
`
`

`

`7
`Gbyte Hard Disk, a modem and dial up line, configured
`with the Microsoft Windows 98/NT operating system;
`2) Unhex the computer listing ADAPTMGT. HEX of
`Appendix A using HEX ITV1.8 or greater by John
`Augustine creating file ADAPTMGTZIP.
`3) Decompress the file ADAPTMGTZIP using WINZIP
`version 6.2 or greater, extracting all files into their
`respective directories utilizing the WINZIP version 6.2
`option “Use folder names'.
`4) In directory BDEINST execute the file SETUPEXE
`and proceed to follow the default prompts.
`5) In directory WNURITCC execute the file SETUPEXE
`and proceed to follow the default prompts. This pro
`cedure installs the center files, including WNLSP.EXE
`6) Execute the file NURITCDK.EXE. This procedure
`installs the center files, including PLUGIN.EXE
`7) To complete the installation, execute the file SERIAL
`.EXE This procedure installs the center files, including
`SERLBLD.EXE
`8) Execute SERLBLD.EXE to generate a serial number
`for the center.
`9) To run the configuration builder, execute the file
`PLUGIN.EXE to generate the header file and block
`definitions file.
`10) To run the center, execute the file WNLSPEXE.
`Select in this program “menu/files/import operating
`systems’
`and
`select
`the
`file:
`\OS IMPORT\001 USA\OS Data 01 06.OSN
`It will be appreciated by persons skilled in the art that the
`present invention is not limited by what has been particu
`larly shown and described hereinabove. Rather the scope of
`the present invention includes both combinations and sub
`combinations of the various features described hereinabove
`as well as variations and modifications which would occur
`to persons skilled in the art upon reading the specification
`and which are not in the prior art.
`The invention claimed is:
`1. A method, tangibly embodied on a computer readable
`medium, to configure selected point-of-sale terminals and a
`
`25
`
`30
`
`35
`
`US 7,051,091 B1
`
`10
`
`15
`
`8
`management center controlling said selected point-of-sale
`(POS) terminals as well as non-selected point of sale (POS)
`terminals, the method comprising:
`employing a configuration builder to create first and
`second linked files;
`utilizing said first file by an application generator to create
`an application, wherein said application is not used for
`the non-selected point-of-sale terminals;
`Supplying said second file by the configuration builder to
`said management center;
`utilizing said second file by a parameter structure genera
`tor to define a parameter structure which is adapted to
`said application and linked thereto;
`Supplying said application to said management center;
`operating said management center, to select said applica
`tion for said selected point-of-sale terminals and to
`associate said parameter structure with said selected
`point of sale terminals;
`employing said parameter structure for setting parameter
`values suitable to both said selected application and
`said selected point-of-sale terminals;
`automatically employing said parameter structure by said
`management center to configure an operator interface
`in said management center, and
`Supplying said application and said parameter values to
`said selected point of sale terminals,
`wherein said management center automatically reflects
`changes made by a software programmer in said
`Selected application using said configuration builder in
`said parameter structure stored in at least one database.
`2. The method to configure selected point-of-sale termi
`nals and a management center according to claim 1 and
`wherein said management center automatically configures at
`least one database in said management center according to
`said parameter structure.
`
`Lightspeed Ex. 1020.14
`
`