USOO713 0622B2
`
`(12) United States Patent
`Vänska et al.
`
`(10) Patent No.:
`45) Date of Patent:
`
`US 7,130,622 B2
`*Oct. 31, 2006
`
`9
`
`(54) DISPOSABLE MINI-APPLICATIONS
`
`(75) Inventors: Marko Vänskä, Espoo (FI); Sami
`Ranta, Helsinki (FI); Raimo Malila
`Helsinki (FI)
`s
`s
`
`(73) Assignee: Nokia Corporation, Espoo (FI)
`
`(*) Notice:
`
`Subject to any disclaimer, the term of this
`patent is extended or adjusted under 35
`U.S.C. 154(b) by 0 days.
`This patent is Subject to a terminal dis-
`claimer.
`
`(21) Appl. No.: 11/143,314
`
`(22) Filed:
`
`Jun. 1, 2005
`
`(65)
`
`Prior Publication Data
`US 2005/0222918 A1
`Oct. 6, 2005
`
`6, 1988 Brass et al.
`4,754,127 A
`4,782,221 A 11/1988 Brass et al.
`4,794,239 A 12/1988 Allais
`4,874,936 A 10, 1989 Chandler et al.
`4,896,029 A
`1/1990 Chandler et al.
`4.924,078 A
`5/1990 Sant'Anselmo et al.
`4,939,354 A
`7, 1990 Priddy et al.
`4,958,064 A
`9, 1990 Kiai,
`tal.
`4,972.475 A 11/1990 Sant'Ansel
`4,998,010 A
`3, 1991 NE al
`
`(Continued)
`FOREIGN PATENT DOCUMENTS
`
`DE
`
`10042914
`
`4/2001
`
`(Continued)
`OTHER PUBLICATIONS
`“CodeXML Router—Bluetooth Edition'. http//www.gocode.com/
`products/coderouter.htm, 2 pages, printed on Jul. 2, 2004.
`
`Related U.S. Application Data
`(63) Continuation of application No. 10/286.221, filed on
`Nov. 1. 2002, now Pat. No. 7,072,672.
`
`(Continued)
`Primary Examiner Jean Gelin
`(74) Attorney, Agent, Of Firm Morgan & Finnegan, L.L.P.
`
`(51) Int. Cl.
`(2006.01)
`H04O 7/20
`(52) U.S. Cl. ................... 455/419,455/414.1:455/418:
`455/456.3
`(58) Field of Classification Search ............. 455,412.1
`455/412.2, 41.4.1, 414.2, 418, 419, 422.1
`455/426.1,426.2 432.3 456.1 456.3. 707/10.
`707/100.345,737.739. 705/110 26 200 208
`See application file for complete search history.
`References Cited
`U.S. PATENT DOCUMENTS
`
`(56)
`
`3,916, 160 A 10, 1975 Russo et al.
`3,971,917 A
`7, 1976 Maddox et al.
`4,692.603 A
`9, 1987 Brass et al.
`4,728,783 A
`3, 1988 Brass et al.
`4,745,269 A
`5, 1988 Van Gils
`
`(57)
`
`ABSTRACT
`
`Disposable mini-applications are executable software items
`whose activation, deactivation and deletion in a mobile
`terminal are defined by trigger parameters and rules. Trigger
`parameters may include, but are not intended to be limited
`to, location, time, stored user data and the like. Rules are one
`or more trigger parameters needed to effect one of the
`foregoing actions. In one embodiment, a housekeeping
`means monitors for data that corresponds to the parameters
`and satisfies the rules, and performs a variety of housekeep
`ing functions relating to the disposable mini-applications.
`The deletion of the disposable mini-application clears
`memory space associated with storing and executing the
`disposable mini-application, and thus, makes that space
`available for other purposes.
`
`57 Claims, 6 Drawing Sheets
`
`SERVICE ROWER
`
`150
`
`157
`
`
`
`
`
`
`
`Short-range
`Wireless
`Network
`
`Twitter Exhibit 1011
`Page 00001
`
`

`

`US 7,130,622 B2
`Page 2
`
`6,332,062 B1 12/2001
`6,356,543 B1
`3, 2002
`6,370,389 B1
`4, 2002
`6,389,278 B1
`5/2002
`6,397,057 B1
`5/2002
`6,401,085 B1
`6, 2002
`6,446,004 B1
`9, 2002
`6,446,208 B1
`9, 2002
`6,448,979 B1
`9, 2002
`6,456,039 B1
`9, 2002
`6,462,660 B1 10/2002
`6,470,096 B1 10/2002
`6,491,217 B1 12/2002
`6,512.919 B1
`1, 2003
`6,542.933 B1
`4/2003
`6,577,901 B1
`6, 2003
`6,587,684 B1
`T/2003
`6,611,673 B1
`8, 2003
`6,622,017 B1
`9, 2003
`6,641,051 B1
`11/2003
`6,647,269 B1
`11/2003
`6,650,761 B1
`11/2003
`6,678.425 B1
`1, 2004
`6,687,793 B1
`2, 2004
`6,753,883 B1
`6, 2004
`6,950,646 B1* 9/2005
`6,985,562 B1* 1/2006
`6,993,326 B1* 1/2006
`6,996,537 B1 * 2/2006
`2001 OO11247 A1
`8, 2001
`2001 OO18349 A1
`8, 2001
`2001/0041566 A1 11, 2001
`2002fOO39.909 A1
`4, 2002
`2002fOO72355 A1* 6, 2002
`2002fOO86680 A1
`T/2002
`2002fOO87392 A1
`T/2002
`2002fOO87529 A1
`T/2002
`2002fOO94797 A1
`T/2002
`2002fOO9545.6 A1
`T/2002
`2002/O121544 A1
`9, 2002
`2002/O122055 A1
`9, 2002
`2002/0130.178 A1
`9, 2002
`2002fO151326 A1 10, 2002
`2002fO165008 A1 11, 2002
`2003, OO17848 A1
`1, 2003
`2003, OO19929 A1
`1, 2003
`2003, OO30542 A1
`2, 2003
`2003.0056019 A1
`3, 2003
`2003/0074566 A1
`4/2003
`2003, OO88496 A1
`5/2003
`2003. O191839 A1 10, 2003
`2003. O194989 A1 10, 2003
`2004/OOOO585 A1
`1, 2004
`2004/OOO6517 A1* 1/2004
`2004/OO33798 A1* 2, 2004
`2004/OO75675 A1
`4, 2004
`2004/0083138 A1
`4, 2004
`2004/0203693
`A1* 10, 2004
`
`U.S. PATENT DOCUMENTS
`Priddy et al.
`Shamir
`Priddy et al.
`Sakiyama et al.
`Batterman et al.
`Petigrew et al.
`Batterman et al.
`Wang
`Jonsen
`Sant'Anselmo et al.
`Shamir
`Batterman et al.
`Swartz et al.
`Wilk
`Hecht et al.
`Shepley
`Theimer et al.
`Nelson et al.
`Chandler et al.
`Hecht et al.
`Park
`DeLorime et al.
`Lipp et al.
`Allard et al.
`DeTemple et al.
`Longacre, Jr. et al.
`Salmon et al.
`Sant'Anselmo et al.
`Nerlikar
`Vela et al.
`Small et al.
`Deaton et al.
`Honbuckle
`MacKinlay et al.
`Loosmore et al.
`Payne et al.
`Schkolnick et al.
`Dickinson
`Shachar et al.
`Patton et al.
`Vanttila et al.
`Lodenius
`Liliu
`O'Hagan et al.
`Carrender et al.
`Watanabe et al.
`Durst et al.
`DeLorime et al.
`Maynard
`Lupien, Jr. et al.
`Scroggie et al.
`Hudetz et al.
`Tracy et al.
`Clapper
`Hall et al.
`Farris et al.
`Dietrich
`Callaghan et al.
`Durst et al.
`Birgerson
`Kari et al.
`Antognini et al.
`Cromer et al.
`Hudetz et al.
`Batterman et al.
`Harrison et al.
`Klein
`Heinonen et al.
`Itabashi et al.
`Schena et al.
`Stevens
`
`10, 1991
`6, 1992
`6, 1992
`10, 1992
`2, 1993
`4, 1993
`6, 1993
`9, 1993
`10, 1993
`T. 1994
`11, 1994
`1, 1995
`5, 1995
`5, 1995
`9, 1995
`12, 1995
`2, 1996
`4, 1996
`4, 1996
`5, 1996
`8, 1996
`9, 1996
`10, 1996
`10, 1996
`11, 1996
`1/1997
`1/1997
`3, 1997
`5, 1997
`5, 1997
`6, 1997
`7, 1997
`7, 1997
`9, 1997
`10, 1997
`2, 1998
`3, 1998
`3, 1998
`6, 1998
`6, 1998
`8, 1998
`8, 1998
`9, 1998
`10, 1998
`12, 1998
`3, 1999
`8, 1999
`9, 1999
`9, 1999
`9, 1999
`10, 1999
`11, 1999
`11, 1999
`2, 2000
`2, 2000
`2, 2000
`4, 2000
`5, 2000
`8, 2000
`10, 2000
`11, 2000
`1, 2001
`1, 2001
`3, 2001
`5, 2001
`6, 2001
`T/2001
`9, 2001
`10, 2001
`11, 2001
`12, 2001
`
`5,053,609
`5,118,369
`5,124,536
`5,153,148
`5,189,292
`5,206,490
`5,223,701
`5,243,655
`5,250,789
`5,331, 176
`5,369,261
`5,378,883
`5,412, 193
`5,415, 167
`5.449,895
`5,478,989
`5,493,692
`5,508,695
`5,512,739
`5,521,372
`5,550,535
`5,559,707
`5,561,702
`5,561,705
`5,572,653
`5,591.956
`5,592,375
`5,612,524
`5,629,981
`5,630,068
`5,642,303
`5,649,114
`5,649,187
`5,666,214
`5,682,142
`5,715,314
`5,729,697
`5,732,229
`5,764,736
`5,764,739
`5,794, 142
`5,799,091
`5,811,776
`5,821,513
`5,850,187
`5,886,646
`5,933,829
`5.948,040
`5,949,335
`5,959,530
`5,970,469
`5,978,773
`5,979,757
`6,023,241
`6,026,375
`6,029,064
`6,055,442
`6,058,304
`6,108,656
`6,138,009
`6,154,745
`6,176.427
`6,177,860
`6,199,048
`6,223.988
`6,249,226
`6,259,367
`6,295,506
`6,308,203
`6,314.457
`6,327,570
`
`- - - - - - - - - - - - - - - 455,419
`
`FOREIGN PATENT DOCUMENTS
`
`EP
`EP
`EP
`EP
`EP
`FI
`GB
`WO
`WO
`WO
`WO
`WO
`
`O8O1512
`O853287
`10595.99
`1130495
`1130933
`2002/2288
`2 246 491 A
`WO 97/10558
`WO 97/17790
`WO 97.28736
`WO 97/46960
`WO 98.35469
`
`10, 1997
`7, 1998
`12/2000
`9, 2001
`9, 2001
`12/2002
`1, 1992
`3, 1997
`5, 1997
`8, 1997
`12/1997
`8, 1998
`
`Phillips et al.
`Hall et al.
`Isomursu et al.
`Singh
`Malackowski et al.
`Gershman et al.
`Cao et al.
`Gujar et al.
`Schena et al.
`Lauper et al.
`Cannon et al.
`Davies et al.
`Catan
`Ogasawara
`Durst, Jr. et al.
`Thompson
`Hsu et al.
`Bayley et al.
`Hoffman
`Illowsky et al.
`Hendrey et al.
`Rodriguez et al.
`Flores et al.
`Thomas et al.
`Schena et al.
`Pradhan et al. ............. 455,406
`Matsuda et al.
`379.88.06
`Link et al. ......
`455,414.1
`Minear et al.
`... TOS/26
`O'Flaherty et al.
`Kinnunen et al.
`Xanthos et al.
`Rankin
`Jeong et al. ................ 455,419
`Hunzinger
`Stevens
`Dutcher et al.
`Marshall et al.
`Wensheng
`Ito et al.
`Parupudi et al.
`Wan et al.
`Awada et al.
`Sashihara et al.
`Engstrom et al.
`Stewart et al.
`Von Hoffman
`Kehr et al.
`Hypponen
`Piotrowski
`Seljeseth
`Guion
`Silverbrook et al.
`Takatori
`Robin et al. ....
`Raivisto et al.
`Silverbrook et al.
`Mehta et al.
`
`705/26
`
`
`
`- - - - - - - - - 455,419
`
`Page 00002
`
`

`

`US 7,130,622 B2
`Page 3
`
`4f1999
`WO 99.17230
`WO
`6, 1999
`WO 99 30257
`WO
`3, 2000
`WOOOf 16507
`WO
`12/2000
`WOOOf 74406
`WO
`1, 2001
`WO O1/06507
`WO
`3, 2001
`WO Of 17297
`WO
`3, 2001
`WO O1?2O542
`WO
`4/2001
`WO O1/25985
`WO
`5, 2001
`WO O1/39 103
`WO
`5, 2001
`WO O1/39108
`WO
`6, 2001
`WO O1/45038
`WO
`6, 2001
`WO O1/45061 A2
`WO
`6, 2001
`WO O1/45319
`WO
`6, 2001
`WO O1? 47291
`WO
`10, 2001
`WOO 1/73687
`WO
`10, 2001
`WOO 1/74O11
`WO
`10, 2001
`WO O1 (75815
`WO
`12/2001
`WO O1 (99410
`WO
`1, 2004
`WO 2004,3829
`WO
`4/2004
`WO WO 2004/27689
`WO WO 2005,101.337 A1 10, 2005
`
`OTHER PUBLICATIONS
`“CodeXML Bluetooth Modem”. product sheets (2 pp), printed from
`www.gocode.com on Jul. 2, 2004.
`“CodeXML Router—Bluetooth Edition”, product sheets (2 pp),
`printed from www.gocode.com on Jul. 2, 2004.
`“Code
`Router
`BE Diagram'.
`http://www.gocode.com/
`routerdiagram.htm, 1 page, printed on Jul. 2, 2004.
`“CodeXML. Maker Pro'. http://www.gocode.com/products/maker.
`htm, 1 page, printed on Jul. 2, 2004.
`“CodeXML. Maker Pro Screen'. http://www.gocode.com/products/
`images/makerpro-screen.jpg, 1 page, printed on Jul. 2, 2004.
`“CodeXML Bluetooth Modem”. http://www.gocode.com/products/
`modem.htm, 1 page, printed on Jul. 2, 2004.
`“Code Router BE Use Case Diagram'. http://www.gocode.com/
`routerdiagram2.htm, 1 page, printed on Jul. 2, 2004.
`“GoCode—Secure Data Soltions'. http://www.gocode.com/prod
`ucts/gocode.htm, 3pp, printed on Jul. 2, 2004.
`NeoMedia Technologies Inc., “Patent Infringement Lawsuit
`Brought by NeoMedia Against AirClic Inc., Scanbuy, Inc., and
`LScan Technologies Inc.', dated Jan. 26, 2004, 2 pages, http://www.
`neom.com/corporate/press/2004/20040 126.jsp. printed Apr. 15,
`2004.
`
`Symbol Technologies Ltd., “Solutions 8 Fastfrog Case Study”.
`http://www.symbol.com/uk/News/
`Solutions 8 fastfrog case stud.html, 2 pages, printed on Apr. 15,
`2004.
`“CueCat Barcode scanner from Digital Convergence Information'.
`http://www.cuecat.com, 2 pages, printed on Sep. 16, 2005.
`iTCaseStudies.com “Uniting Space and Place for Future Growth',
`4 pages, http://www.itcasestudies.com/case/retj7.html, printed on
`Apr. 15, 2004.
`Stephen Satchell, “CueCat Principles of Operation', 4 pages, http://
`www.fluent-access.com/wtpapers/cuecat, printed on Apr. 15, 2004.
`Symbol Technologies, Inc. "Symbol Technologies’ Consumer Scan
`ners Provide Mall Shoppers With Internet Shopping Experience”,
`dated Dec. 6, 1999, 3 pages, http://www.symbol.com/news/
`pressreleases/press releases retail consumer.html, printed on
`Apr. 15, 2004.
`NeoMedia Technologies, “Virgin Entertainment, Virgin Megstore
`Online and Virgin Mega Store Are Charged with Patent Infringe
`ment by NeoMedia Technologies, Inc.', dated Jan. 5, 2004, 2 pages,
`http://www.neom.com/corporate/press/2004/20040 105.jsp. printed
`on Apr. 15, 2004.
`12snap UK Ltd. 12snap That's Mobile Marketing, 38 pages, http://
`www.12snap.com/uk/index2.html, printed on Apr. 15, 2004.
`AIM Inc. “Radio Frequency Identification RFID—A Basic Primer'
`White paper, V 1.2, Aug. 23, 2001.
`Mandato et al. “CAMP: A context-Aware Mobile Portal', IEEE,
`vol. 40 No. 1, Jan. 2002, pp. 90-97.
`“User's Guide Nokia 6310i' 2002, pp. 1-115, no month listed.
`“vOard: The Electronic Business Card”. White Paper, webpage
`online). IMC, 5 pages retrieved on Feb. 5, 2002). Retrieved from
`the Internet: <http://www.imc.org/pdivcardwhite.html>.
`“vOard Overview', webpage online). IMC, 3 pages retrieved on
`Feb. 5, 2002). Retrieved from the Internet: < http://www.imc.org/
`pdi//vcardoverview.html>.
`“Products. Using vCard and vCalendar Technology', webpage
`online). IMC (9 pages retrieved on Feb. 5, 2002). Retrieved from
`the Internet < http://www.imc.org/pdi/pdiprodslits.html>.
`“UMTS and Mobile Computing, Huber et al. Mar. 2002, Artech
`House Mobile Communication Series, pp. 170-187 and 321-232.
`* cited by examiner
`
`Page 00003
`
`

`

`U.S. Patent
`
`Oct. 31, 2006
`
`Sheet 1 of 6
`
`US 7,130,622 B2
`
`
`
`
`
`
`
`
`
`1oo
`
`MOBILETERMINAL
`
`150
`
`
`
`
`
`
`
`
`
`Processing
`Means
`
`RFID
`
`rfd
`Tag
`Reade
`
`Short Range
`Wireless
`Connection
`
`Short-Range
`Wireless
`Network
`
`F.G. 1
`
`Page 00004
`
`

`

`U.S. Patent
`
`Oct. 31, 2006
`
`Sheet 2 of 6
`
`US 7,130,622 B2
`
`
`
`interface(s)
`
`(102,104)
`
`Mini Appl. 1
`
`Mini Application
`Housekeeping
`
`Data Storage
`(e.g., riggering
`Parameters,Rules, etc.
`
`FIG. 2
`
`Page 00005
`
`

`

`U.S. Patent
`
`Oct. 31, 2006
`
`Sheet 3 of 6
`
`US 7,130,622 B2
`
`
`
`3.12a
`
`FIG. 3
`
`Page 00006
`
`

`

`U.S. Patent
`
`Oct. 31, 2006
`
`Sheet 4 of 6
`
`US 7,130,622 B2
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Store
`Miniapplication
`418
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Download
`Miniapplication
`402
`
`Precorditions
`For Activation Met?
`404
`
`Activate Miniapplication
`408
`
`Execute Miniapplication
`410
`
`Deactivate
`Miniapplication?
`412
`
`Deactivate
`Miniapplication
`414
`
`
`
`Delete
`Miniapplication?
`416
`
`Delete
`Miniapplication
`420
`
`FIG. 4
`
`Page 00007
`
`

`

`U.S. Patent
`
`Oct. 31, 2006
`
`Sheet S of 6
`
`US 7,130,622 B2
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Miniapplication
`Housekeeping Means
`
`
`
`106a
`
`Activation
`Trigger
`Conditions
`
`Deactivation
`Trigger
`Conditions
`
`Deletion
`Trigger
`Conditions
`
`Executable
`Software
`
`502
`
`504
`
`506
`
`508
`
`FIG. 5
`
`Page 00008
`
`

`

`U.S. Patent
`
`Oct. 31, 2006
`
`Sheet 6 of 6
`
`US 7,130,622 B2
`
`210a
`
`RFID input
`Storage
`
`602
`
`#12345
`
`604
`
`606
`
`608
`
`#2345
`
`#A6789
`
`110a
`
`USer Data
`Storage
`
`D 9876
`
`Shoe
`Size = 41
`
`S16
`
`XR56W
`
`an
`
`Price = $50
`
`Miniapplication #1
`
`Bluetooth
`Module
`
`Service
`Provider
`
`
`
`Data Storage
`(e.g., Triggering
`Parameters, Rules
`
`250
`
`/
`
`A ra
`
`REAGER
`
`112
`
`FIG. 6
`
`Page 00009
`
`

`

`1.
`DISPOSABLE MINI-APPLICATIONS
`
`US 7,130,622 B2
`
`This is a continuation of application Ser. No. 10/286.221,
`filed Nov. 1, 2002, now U.S. Pat. No. 7,072,672.
`
`FIELD OF THE INVENTION
`
`The present invention relates to wireless communications
`systems in general and, more particularly, to an apparatus
`and method for efficiently managing the memory of a mobile
`terminal.
`
`10
`
`BACKGROUND OF THE INVENTION
`
`Mobile terminals have become ubiquitous. One of the
`reasons for their popularity is their compact size. Another
`reason is their ability to run Software applications that permit
`users to perform a variety of enhanced functions, beyond
`those relating to traditional telephony, while in a mobile
`environment. Unfortunately, the terminals Small size trans
`lates into a limited memory capability for storing applica
`tions and associated data, and thus, ultimately imposes
`limitations on the terminal's functionality. Another problem
`faced by users of mobile terminals equipped with software
`applications that provide enhanced functionality is having to
`ensure that they have the latest or most suitable versions of
`the applications stored on their terminals by manually updat
`ing or reconfiguring the applications. What is needed is a
`mechanism for efficiently managing software applications
`used by these mobile terminals and, more particularly, for
`efficiently managing a mobile terminal's memory space
`where applications are stored.
`
`15
`
`25
`
`30
`
`SUMMARY OF THE INVENTION
`
`The above-identified problems are solved and a technical
`advance is achieved in the art by an apparatus and method
`for managing the storage of disposable mini-applications in
`a mobile terminal. Such as a mobile telephone. An applica
`tion, which comprises an executable Software item of lim
`ited operability associated with conditions for one or more
`of downloading, activating, deactivating and deleting the
`software item, is referred to herein as a disposable mini
`application, as will be discussed in detail hereinafter.
`An exemplary method for a mobile terminal having a
`processor and a memory for processing and storing data to
`manage storage of executable software items of limited
`operability comprises: downloading an executable Software
`item comprising at least one condition for deletion of the
`executable software item over a wireless connection,
`wherein the executable software item enables access to at
`least one service at a specified location; storing the execut
`able software item including the condition for deletion of the
`executable software item in storage of the mobile terminal;
`and if the condition for deletion of the executable software
`item is satisfied, deleting the executable software item from
`storage of the mobile terminal.
`In an alternate embodiment, an exemplary method com
`prises: downloading an executable Software item together
`with trigger conditions for activation and deletion of the
`executable software item over a wireless connection,
`wherein the executable software item enables access to at
`least one service at a specified location; storing the execut
`able software item together with the trigger conditions for
`activation and deletion of the executable software item in
`storage of the mobile terminal; if a trigger condition for
`activation of the executable software item is satisfied, acti
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`2
`Vating the executable software item; and if a trigger condi
`tion for deletion of the executable software item is satisfied,
`deleting the executable software item from storage of the
`mobile terminal.
`In yet an alternate embodiment, an exemplary method
`comprises: downloading a first executable software item
`upon entry of the mobile terminal into a first location
`together with a trigger condition for deletion of the first
`executable software item; downloading a second executable
`software item upon entry of the mobile terminal into a
`second location together with a trigger condition for deletion
`of the second executable software item; monitoring for
`trigger data that satisfies the trigger condition for deletion of
`the second executable software item; and deleting the sec
`ond executable software item upon detection of trigger data
`that satisfies the trigger condition for deletion of the second
`executable software item.
`In an embodiment directed to a method for a mobile
`terminal having a processor and a memory for processing
`and storing data to manage storage of an executable software
`item of limited operability that provides a user of the mobile
`terminal with shopping assistance, an exemplary method
`comprises: downloading an executable Software item for
`providing a user of a mobile terminal with assistance while
`shopping, wherein the executable software item comprises
`data comprising an identification of one or more shopping
`service locations and trigger conditions for activation and
`deletion of the executable software item from memory of the
`mobile terminal; detecting, via a short range wireless con
`nection, that the user is located within proximity of one of
`the shopping service locations; accessing user data compris
`ing indications of goods and/or services of interest to the
`user, comparing goods and/or services offered by the shop
`ping service location with the user data to determine whether
`there is a match; if there is a match, activating the executable
`Software item; and executing the executable Software item,
`wherein execution of the executable software item com
`prises: generating a query for transmission to the shopping
`service location, the query including the user data; and
`transmitting the query to the shopping service location via a
`short range wireless connection. In this embodiment, a
`shopping service location may be a service desk, a shop or
`the like in a shopping center/mall or any Smaller location
`therein including an aisle, shelf, counter, stand, etc. where
`goods and/or services are made available for consumption,
`as will be discussed in detail hereinafter.
`In one embodiment of the present invention, the data or
`the individual data items mentioned above that are stored in
`the mobile terminal. Such as user data and the data relating
`to trigger parameters and trigger conditions downloaded to
`the mobile terminal or stored therein, may be expressed
`using markup language expressions or compressed markup
`language expressions of an XML-based markup language.
`Other and further aspects of the present invention will
`become apparent during the course of the following descrip
`tion and by reference to the attached drawings.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`FIG. 1 is a block diagram illustrating an exemplary
`arrangement between a mobile terminal and a service pro
`vider in which a disposable mini-application may be down
`loaded and used in accordance with one embodiment of the
`present invention.
`FIG. 2 is a block diagram illustrating an exemplary
`mobile terminal in accordance with one embodiment of the
`present invention.
`
`Page 00010
`
`

`

`US 7,130,622 B2
`
`3
`FIG. 3 is a simplified layout of an area such as a shopping
`mall, department store or shop illustrating the location of
`nodes for data transfer between mobile terminals and one or
`more service providers in accordance with one embodiment
`of the present invention.
`FIG. 4 is a flowchart illustrating an exemplary process by
`which a disposable mini-application may be used in a
`mobile terminal.
`FIG. 5 is a block diagram illustrating the performance of
`a disposable mini-application housekeeping function.
`FIG. 6 is a block diagram illustrating an exemplary
`disposable mini-application for providing purchasing assis
`tance to a user while the user is shopping in a shopping mall,
`a shop or any shopping service location thereof in accor
`dance with one embodiment of the present invention.
`
`10
`
`15
`
`DETAILED DESCRIPTION
`
`4
`or service provider 150 have been satisfied, as will be
`discussed in detail hereinafter in connection with FIG. 4.
`Once downloaded, the disposable mini-application may be
`activated, deactivated and/or deleted from storage 106 based
`on whether trigger conditions for doing so have been satis
`fied, as will also be discussed in detail in connection with
`FIG. 4. These trigger conditions are preferably downloaded
`together with the disposable mini-application from service
`provider 150. In one embodiment, a trigger condition may
`comprise trigger parameters and rules, as will be discussed
`in detail hereinafter. The downloaded trigger conditions,
`trigger parameters and rules may be expressed using markup
`language expressions or compressed markup language
`expressions preferably using an XML-based markup lan
`gllage.
`Briefly, trigger parameters may be based upon one or
`more of a location, a date/time, user input, etc. Trigger
`parameters also may be based upon personal user data Such
`as profile, calendar, intents and notes data. A user's profile
`may include a user's name, address, phone number(s),
`gender, age, employer, hobbies, car model, car registration
`number, preferences (e.g., a preferred genre of books),
`loyalty card memberships, credit/debit card information and
`the like. A user's calendar Stores user generated entries for
`events such as appointments, birthdays, visits, holidays,
`vacations, shows, etc. correlated to a date and time when the
`event is to occur. A user's intentions may be user-specified
`intended tasks or acts to be performed by her such as
`'grocery shopping”, “birthday present shopping”, “car
`wash”, “hair cut’, etc. Notes may include user-generated
`instructions to be followed by the user when performing a
`task. Exemplary notes include a shopping list, a wish list for
`a family member, a spouse's perfume or cologne prefer
`ences, etc. Preferably, the user may activate these intents/
`notes at any time for a period of time (such as from now until
`otherwise indicated) or can associate them with a date/time
`in a calendar or to a location for automatic activation. In any
`event, such personal data may be stored either locally in user
`data storage 108a or remotely in user data storage 108b
`where mobile terminal 100 may readily access it whenever
`needed over, e.g., mobile WAN 130, for use in determining
`whether trigger parameters associated with a disposable
`mini-application have been satisfied. The data relating to
`personal user data may be stored using markup language
`expressions or compressed markup language expressions,
`preferably using an XML-based markup language.
`As mentioned above, in one embodiment of the present
`invention, trigger conditions may comprise rules in addition
`to trigger parameters. Rules are one or more trigger param
`eters needed to effect an action Such as activating, deacti
`Vating or deleting a disposable mini-application, as will also
`be discussed in detail hereinafter.
`As further shown in FIG. 1, mobile terminal 100 includes
`an RF-ID tag 110 and an RF-ID tag reader 112. Service
`provider 150 likewise includes RF-ID tag readers 158 and
`RF-ID tags 159. As will be discussed in detail hereinafter, an
`RF-ID wireless system comprising an RF-ID tag 110 of
`mobile terminal 100 and RF-ID tag readers 158 of service
`provider 150 or, alternatively, an RF-ID tag reader 112 of
`mobile terminal 100 and RF-ID tags 159 of service provider
`150, may be used in one embodiment of the present inven
`tion to determine the user's location within a service pro
`vider 150's premises for use in satisfying a precondition for
`downloading a disposable mini-application or, satisfying a
`trigger condition for activating, deactivating and/or deleting
`the disposable mini-application.
`
`25
`
`35
`
`40
`
`In the following description of the various embodiments,
`reference is made to the accompanying drawings which
`form a part hereof, and in which are shown by way of
`illustration various embodiments in which the invention
`may be practiced. It is to be understood that other embodi
`ments may be utilized and structural and functional modi
`fications may be made without departing from the scope of
`the present invention.
`FIG. 1 is a block diagram illustrating an exemplary
`arrangement between a mobile terminal and a service pro
`vider in which a disposable mini-application may be down
`loaded and used in accordance with one embodiment of the
`30
`present invention. As shown in FIG. 1, mobile terminal 100,
`which may be a hand-held wireless telephone, a mobile
`handset terminal, a personal digital assistant ("PDA), a
`portable computer or the like includes storage 106 for one or
`more disposable mini-applications downloaded from a ser
`vice provider 150, preferably over a wireless connection.
`A disposable mini-application is an executable Software
`item, such as a Java applet, a script or a software agent of
`limited operability for performing one or more functions on
`a mobile terminal 100. With respect to its limited operability,
`in addition to being associated with one or more conditions
`for its deletion, a disposable mini-application is preferably
`also associated with one or more conditions (such as the
`physical location of the mobile terminal) for one or more of
`its downloading, activation and deactivation, as will be
`45
`discussed in detail hereinafter.
`Mobile terminal 100 may download a disposable mini
`application from service provider 150 over either a short
`range wireless network 120, such as a Personal Area Net
`work (e.g., IrDA or Bluetooth PANs) or a wireless LAN
`50
`(e.g., wireless IEEE 1394, IEEE 802.11 or HiperLAN/2) or
`a mobile WAN 130 (e.g. GPRS, GSM, etc.). In this regard,
`service provider 150 includes a short range wireless con
`nection 156 and/or WAN connection 157 for use in down
`loading a disposable mini-application to mobile terminal
`55
`100 over short range wireless network 120 or mobile WAN
`130, respectively. Service provider 150, which may be a
`single entity, such as a single store, or an entity representing
`a plurality of stores, such as a shopping mall, includes a
`processor 152 coupled to a database 154 for storing one or
`more disposable mini-applications (together with any asso
`ciated data) for downloading to mobile terminal 100 for
`activation and use.
`In accordance with one embodiment of the present inven
`tion, a mobile terminal 100 may download a disposable
`mini-application provided that any preconditions for down
`loading it that have been established by either terminal 100
`
`60
`
`65
`
`Page 00011
`
`

`

`5
`An RF-ID tag is a wireless transponder that may contain
`varying amounts of information ranging from a tag identifier
`to 128 Kbytes of variable memory that can be programmed
`with additional information. An RF-ID tag reader commu
`nicates with a tag through the use of RF energy. In particular,
`an RF-ID tag reader sends out an interrogation signal which
`“wakes up' a tag situated within a predetermined proximity
`to the reader. A tag may be “passive' in that it operates
`without an internal battery source, deriving the power to
`operate from the RF field generated by the RF-ID reader,
`which is inductively coupled to the tag. Alternatively, a tag
`may be “active', and thus, powered by an internal battery
`that allows a greater communication range and higher data
`transmission rates. Once interrogated, the tag will transmit a
`signal including its ID number and possibly other informa
`tion back to the RF-ID tag reader. RF-ID wireless network
`principles are described in a publication entitled “Radio
`Frequency Identification: A Basic Primer', published by
`Automatic Identification Manufacturers (AIM), website:
`(www.aimglobal.org), Aug. 23, 2001, a copy of which is
`incorporated herein by reference. The data stored in an
`RF-ID tag may be stored at least partly in a format of a
`markup language expression of an XML-based markup
`language.
`In one embodiment, service provider 150 may have
`installed RF-ID tags 159 throughout its premises. Mobile
`terminal 100 may use its RF-ID tag reader 112 to determine
`its entrance into, current location within, and departure
`from, a predetermined area by sensing one or more of
`service provider 150's RFID tags 159, as will be discussed
`in detail hereinafter in connection with FIG. 6, and use this
`location information for downloading, activating, deactivat
`ing and/or deleting a disposable mini-application without the
`mobile terminal 100 having to disclose its location to service
`provider 150.
`Given the foregoing, an exemplary trigger parameter for
`activation of a mini-application may be the identification
`number of an RF-ID tag 159 read by RF-ID tag reader 112
`of mobile terminal 100. Another trigger parameter may be a
`specific number, such as the numeral “1”, entered by the user
`via keyboard 104. In view of these trigger parameters, an
`exemplary rule may be that if the first number of the RF-ID
`tag's identification number read by RF-ID tag reader 112 is
`a “1” and the number entered by the user is a “1”, then the
`disposable mini-application is activated.
`In an alternate embodiment, service provider 150 may
`have RF-ID tag readers 158, rather than RF-ID tags 159,
`installed throughout its premises for use in detecting an
`RF-ID tag 110 of mobile terminal 100. Service provider 150
`associates each tag reader 158 with a location in the pre
`mises. Thus, in one embodiment, service provider 150 may
`use a signal generated by an RF-ID tag 110 that has been
`detected by an RF-ID tag reader 158 located at the entrance
`of its premises to detect the user's entry so that a disposable
`mini-application may be downloaded to terminal 100 via a
`bi-directional network, such as short range wireless network
`120. The signal generated by the RF-ID tag 110 of mobile
`terminal 100 may include information concerning the user's
`identity for use in personalizing the disposable mini-appli
`cation to the user based on data stored locally in service
`provider data base 154 (e.g., loyalty data and/or the user's
`past purchasing history) and/or remotely in user data storage
`108c. Personalization also may be based upon user data
`stored in terminal 100 (e.g., in user data storage 108a) that
`is transmitted to service provider 150 over, e.g., short range
`wireless network 120.
`
`25
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`US 7,130,622 B2
`
`10
`
`15
`
`6
`In this alternate embodiment, RF-ID tag 110 of mobile
`terminal 100 also may be used to provide the service
`provider 150 with terminal 100's current location within,
`and departure from, its premises. In particular, service
`provider 150 may determine the user's location based on the
`identity of the RF-ID reader 158 that received the RF-ID tag
`signal. The service provider 150 may transmit this loca