Portable data reading device with integrated web server for configuration and data extraction

A portable data reading device, such as a barcode scanner or RFID reader, includes a Web server and a first server-side application to modify one or more settings of the portable data reading device. The settings may include, for example, symbology settings, device settings, and network settings. The Web server may receive formatted data from a client browser representing a requested modification of at least one setting of the portable data reading device. Upon receiving the formatted data, the Web server may automatically invoke the first server-side application to modify the at least one setting responsive to the formatted data.

Skip to: Description  ·  Claims  · Patent History  ·  Patent History
Description
CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a divisional of U.S. patent application Ser. No. 10/888,570, filed Jul. 9, 2004, for “Portable Data Reading Device with Integrated Web Server for Configuration and Data Extraction,” which is fully incorporated herein by reference.

BACKGROUND OF THE INVENTION

The field of the present invention relates generally to portable data reading devices and more particularly to a portable data reader with an integrated Web server for configuration and data extraction.

Data reading devices, such as barcode scanners, RFID readers, and the like, are a popular means for data acquisition in computerized processing systems. Barcode scanners are used to optically capture barcode patterns or other symbols or information imprinted on different surfaces in order to transmit the information encoded in the barcode pattern or symbol to a host processing device.

Two major types of commonly used barcode scanners are flying spot laser scanners and image based barcode scanners. Flying spot laser barcode scanners generally obtain barcode information by sweeping a laser spot across the barcode. The laser spot may be generated from a light source inside an oscillating reflecting surface, typically a mirror. The light reflected from the barcode is collected by a photosensor, which outputs an analog waveform representing the relative spacing of the bars in the barcode. The analog signal may then be digitized and decoded into data representing the information encoded in the barcode.

Barcode scanning devices based on solid state image circuitry, such as charge coupled devices (CCDs), are also conventionally known. These types of barcode scanners are typically implemented using either a one-dimensional or two-dimensional imaging array of photosensors (or pixels) to capture the barcode. One-dimensional CCD readers capture a linear cross section of the barcode at once, producing an analog waveform whose amplitude represents the relative darkness and lightness of the barcode. Two-dimensional CCD readers capture an entire two-dimensional image at once.

A relatively new type of data reading technology is radio frequency identification (RFID). An RFID system typically employs at least two components, a “transponder” or “tag,” which is attached to the physical item to be identified, and a “reader,” which sends an electromagnetic signal to the transponder and then detects a response. Typically, the reader emits an RF signal which is received by the transponder after the transponder comes within an appropriate range. In response to the signal from the reader, the transponder sends a modulated RF signal sent back to the reader. The reader detects this modulated signal and can identify the transponder by decoding the modulated signal. After identifying the transponder, the reader can either store the decoded information or transmit the decoded signal to a computer.

The transponder used in an RFID system may be either “passive” or “active.” A passive transponder can be a simple resonant circuit, including an inductive coil and a capacitor. Passive transponders are generally powered by the carrier signal transmitted from the reader. Active transponders, on the other hand, generally include transistors or other active circuitry, and require their own battery source.

Barcode scanners and RFID readers may be physically separate from host processing devices, such as personal computers, which provide decoding software, computer storage, and communication interfaces. Increasingly, however, barcode scanners and RFID scanners are being integrated into portable host processing devices. For instance, the Falcon® 4420 Data Collection Terminal manufactured by PSC Inc. of Eugene, Oreg., combines a laser barcode scanner, storage memory, and wireless communication interface in a compact, portable form factor. Such portable devices can be easily transported to different locations within a warehouse, retail store, or the like, greatly simplifying the tasks of receiving, inventorying, etc.

Currently, portable data readers, such as the Falcon® 4420 Data Collection Terminal, are set up and maintained using various client-side configuration programs running on remote personal computers. For instance, PSC Inc. provides a Falcon® Management Utility (FMU), which facilitates remote configuration of the Falcon® 4420 Data Collection Terminal via the device's wireless (RF) interface. Unfortunately, client-side configuration programs, such as FMU, present a number of drawbacks.

Initially, each remote computer that is to access a portable data reader must have a separate installation of FMU, which gives rise to management and maintenance issues. For instance, administrators must ensure that all computers are initially configured with FMU, and that all installations of FMU are of the correct version to be compatible with a particular data reading device.

Moreover, FMU and the like typically use synchronization programs, such as Microsoft ActiveSync®, to update the file system of the portable data reader. However, ActiveSync® and similar programs use point-to-point protocols that allow only a single connection to exist between a remote computer and a portable data reader. Thus, updating the file systems of multiple data readers must be done one at a time, which greatly increases maintenance time.

Finally, protocols used by FMU and others are not secure for use across the Internet. For example, FMU communicates with portable data readers using SNMP (simple network management protocol). However, SNMP uses specific ports in the TCP/IP stack that are vulnerable across the Internet. Competitors, hackers, or other malicious users could exploit the open architecture of SNMP to intercept data and even obtain information about other devices and computers on a company's network.

Because of security concerns, network administrators typically block all but a few ports (e.g., for HTTP, e-mail, etc.) using firewalls, preventing programs like FMU from working properly. While virtual private networks (VPNs) can be used to work around these limitations, VPNs increase the complexity and expense of a system.

Accordingly, the present inventors have recognized a need for a technique for configuring a portable data reader that does not require specialized client-side software to be installed on each personal computer that is to access the data reader. There is also a need for a technique for configuring and/or accessing multiple portable data readers at the same time. In addition, there is a need for a technique for securely configuring and/or accessing a portable data reader across a network, such as the Internet.

SUMMARY OF THE INVENTION

A portable data reading device uses an integrated Web server for various functions including device configuration, setting interrogation, data extraction, file system updates, and cloning. In one aspect, the portable data reading device includes a Web server and a first server-side application to modify one or more settings of the portable data reading device. The settings may include, for example, symbology settings, device (e.g., user interface) settings, and network settings. The Web server may receive formatted data from the client browser representing a requested modification of at least one setting of the portable data reading device. Upon receiving the formatted data, the Web server may automatically invoke the first server-side application to modify the at least one setting.

In another aspect, the portable data reading device includes a second server-side application to interrogate one or more settings of the portable data reading device. The Web server may automatically invoke the second server-side application to interrogate at least one specified setting of the portable data reading device, after which the Web server may send formatted data representing at least one interrogated setting to the client browser for display.

In yet another aspect, the portable data reading device may further include a third server-side application to update a file system of the portable data reading device. The Web server may receive formatted data from the client browser representing an updated file system or operating system image. In response, the Web server may automatically invoke the third server-side application to replace the file system of the portable data reading device with the updated file system.

In still another aspect, the portable data reading device may include a fourth server-side application to clone a file system of the portable data reading device to at least one other portable data reading device. The Web server may automatically invoke the fourth server-side application to create a cloned image of the file system of the portable data reading device and send formatted data representing the cloned image to at least one other portable data reading device with instructions for the at least one other portable data reading device to replace its file system with the file system from the cloned image.

In a further aspect, the portable data reading device may include a fifth server-side application to extract read data from the portable data reading device. The Web server may automatically invoke the fifth server-side application to extract the read data and send the extracted data to the client browser.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a portable data reader including a Web server and a number of server-side applications;

FIG. 2 is a data flow diagram illustrating a process for configuring a portable data reader;

FIG. 3A is an exemplary Web page for modifying symbology settings;

FIG. 3B is an exemplary Web page for modifying device settings;

FIG. 3C is an exemplary Web page for modifying network settings;

FIG. 4 is a data flow diagram illustrating a process for interrogating settings of a portable data reader;

FIG. 5 is a data flow diagram illustrating a process for extracting read data from a portable data reader;

FIG. 6 is a data flow diagram illustrating a process for updating a file system of a portable data reader;

FIG. 7 is a data flow diagram illustrating a process for cloning a file system of one portable data reader to one or more other portable data readers; and

FIG. 8 is a flowchart of a method for configuring a portable data reader using an integrated Web server.

DETAILED DESCRIPTION

Reference is now made to the figures in which like reference numerals refer to like elements. For clarity, the first digit of a reference numeral indicates the figure number in which the corresponding element is first used.

FIG. 1 is a block diagram of portable data reader 100, such as a barcode scanner or radio frequency identification (RFID) reader. The portable data reader 100 may include a reading engine 102, such as a barcode scan engine and/or RFID reading engine. In one embodiment, the reading engine 102 reads barcode symbols from a physical object and/or information from an RFID tag.

Various reading engines 102 are known in the art. For instance, a laser barcode scan engine 102 is available from Intermec Technologies Corp. of Everett, Wash. or other manufacturers. Similarly, an RFID reading engine is available from SAT Corporation of Houston, Tex. In various other embodiments, the reading engine 102 may provide dual barcode/RFID reading. As used herein, barcode scan engines 102 may also encompass CCD-based imagers.

The portable data reader 100 may further include a central processing unit (CPU) 104, such as an Intel® XScale™ PXA255 400 MHz processor. Likewise, the portable data reader 100 may include a standard input controller 106 to receive user input from a keypad 108 or other input device and a display controller 110 to drive an integrated LCD display 112.

The portable data reader 100 may also include a network interface 114 to communicate with an external network (not shown), the network interface 114 conforming to various wired or wireless networking standards, such as IEEE 802.3 (Ethernet), IEEE 802.11b, or Bluetooth™.

The portable data reader 100 further includes a memory 116, which may be implemented using one or more standard memory devices. The memory devices may include, for instance, RAM, ROM, and/or EEPROM devices, and may also include magnetic and/or optical storage devices, such as hard disk drives, CD-ROM drives, DVD-ROM drives, etc.

In one embodiment, the memory 116 stores various functional modules, settings, and user data. For instance, the memory 116 may include an operating system (OS) 118, such as Windows CE .NET 4.2 or the like.

As illustrated, the memory 116 may further include a Web server 120. The Web server 120 may be embodied as the HTTP daemon (HTTPD) for Windows CE .NET. However, those of skill in the art will recognize a variety of other Web servers 120 may be used, such as Apache or Microsoft Internet Information Services (IIS).

Whatever Web server 120 is chosen, it is preferably capable of executing server-side scripts and/or code written in various languages, such as Visual Basic, JavaScript, VBScript, C#, C++, or the like. As explained in greater detail below, scripts may be used, for instance, to automatically invoke one or more server-side applications 122 to perform various desirable functions, such as device configuration, setting interrogation, data extraction, file system updates, and cloning.

In one embodiment, the memory 116 may further store a number of settings 126 for the portable data reader 100. As described in greater detail below, the settings 126 may include, for instance, various symbology settings, device (e.g., user-interface) settings, and network settings.

As depicted, the memory 116 may store read data 128 (symbols and/or information read from barcodes, RFID tags, etc.) obtained by the reading engine 102. All of the foregoing may be stored within, or indexed by, a file system 130, which is typically managed by the OS 118.

The above-described components, including the reading engine 102, CPU 104, input controller 106, display controller 110, network interface 114, memory 116, and the like, may be interconnected via a bus 132. While the illustrated embodiment depicts one possible configuration of a portable data reader 100, it should be recognized that a wide variety of hardware and software configurations may be provided.

Referring to FIG. 2, a process is shown for configuring a portable data reader 100 using an integrated Web server 120. Initially, a Web browser 202 (“browser”) establishes a communication channel with the Web server 120 over a network 204. The network 204 may be embodied as a conventional local area network (LAN), wide area network (WAN), and/or the Internet.

The browser 202 may be hosted by a remote personal computer 206 connected to the network 204. In one embodiment, the browser 202 may comprise a conventional program for retrieving and displaying documents encoded in a markup language, such as the hypertext markup language (HTML) or extensible markup language (XML). For instance, the browser 202 may be embodied as Microsoft Internet Explorer. The communication channel is established using conventional protocols, such as the hypertext transfer protocol (HTTP), in response to a user providing a uniform resource locator (URL), Internet protocol (IP) address, or other suitable identifier of the Web server 120 to the browser 202.

Once a connection is established, the Web server 120 may serve (i.e., deliver) a Web page 124 to the browser 202 listing various settings 126 of the portable data reader 100 that can be modified by the user. As previously noted, the settings 126 may include, for instance, symbology settings, device settings, and network settings, as illustrated in the exemplary Web pages 124a-c of FIGS. 3A-C, respectively.

Referring to FIG. 3A, a first Web page 124a may allow a user to specify changes to symbology settings 126a, e.g., which symbology types the data reader 100 is enabled to read/decode. In the context of barcode scanning, symbologies are effectively barcode “languages.” Different symbologies provide different tradeoffs in terms of the size of the symbol set, the encoding density, the readability of the symbols, etc. Various symbologies are known in the art. For example, one-dimensional (1D) barcode symbologies may include Code 128, Code 29, Interleaved 2 of 5, Universal Product Code (UPC), Extended Code 39, Code 93, UCC 128, Codabar, EAN/JAN, MSI, Zip+4, DPBC POSTNET. Examples of two-dimensional (2D) symbologies include PDF 417, DataMatrix Code, and MaxiCode.

As illustrated, the Web page 124a of FIG. 3A may allow a user to enable or disable various symbologies, as well as configure various symbology-related settings, such as minimum length, maximum length, trioptic settings, etc. The particular settings 126a available within the Web page 124a will depend, of course, on the specific reading engine 102 being used.

As shown in FIG. 3B, a second Web page 124b may allow a user to specify various device settings 126b, such as user interface settings or other data reading functions. As illustrated, such settings may include, for instance, the beeper volume, the number of good read tones, label prefixes, label suffixes, whether the spotting beam should be enabled, the spotting beam timeout, etc. Again, the available settings 126b will vary depending on the particular reading engine 102 and portable data reader 100.

Referring to FIG. 3C, a Web page 124c may allow a user to specify various settings 126c for the network interface 114 of FIG. 1. Possible network settings 126c according to one embodiment of the invention are provided below in Table 1.

TABLE 1 Network Settings Description Action Service Set A sequence of characters that uniquely Type in Identifier (SSID) names a wireless local area network value. (WLAN). Allows workstations to connect to the network when multiple independent networks operate in the same physical area. Enable DHCP Automates configuring of computers using Check TCP/IP. to enable. IP Address Network address of a computer on a Type in network. value. Subnet Mask Number used to identify a subnetwork so an Type in IP address can be shared on a Local Area value. Network (LAN). Gateway System (bridge) for exchanging information Type in across networks. value. DNS Server Domain Name Server aka Domain Name Type in Service, server that resolves IP addresses value. from host names.

Referring again to FIG. 2, the user may specify one or more setting changes 208 within the Web page 124. For instance, the user may choose to enable the Code 39 symbology. In one implementation, the browser 202 in conjunction with the Web page 124 formats the requested setting changes 208 into HTML or another suitable format for transmission to the Web server 120 over the network 204.

In the depicted embodiment, setting changes 208 are passed as parameters on the URL address line. For example, symbology setting changes 208 may be formatted as follows:

    • http://<terminal IP>/SymSet?<command>

where the <command>is formatted as shown in Table 2.

TABLE 2 <command> Meaning C39EN=0,1 Code 39 Enable: 0 = Disabled, 1 = Enabled C39CDE=0,1 Code 39 Check Digit Enable: 0 = Disabled, 1 = Enabled C39CDS=0,1 Code 39 Send Check Digit: 0 = Disabled, 1 = Enabled CD39MIN=0x1,0x22 Code 39 Minimum Length: 0x1 = length of 1, 0x22 = length of 22 hex (50 decimal) CD39MAX=0x1,0x22 Code 39 Maximum Length: 0x1 = length of 1, 0x22 = length of 22 hex (50 decimal)

Thus, to enable Code 39 and the Code 39 check digit, the following setting URL may be constructed:
    • http://<terminal IP>/SymSet?C39EN=1&C39CDC=1

In the foregoing example, the identifier “SymSet” may be associated with a particular server-side application 122, i.e., a configuration application 210. Upon receiving the setting changes 208, the Web server 120 automatically invokes the configuration application 210 to make the requested changes 208 to the symbology settings 126a of the portable data reader 100. In one embodiment, the configuration application 210 may be automatically invoked using scripts (e.g., VBScript) or other server-side code.

Various techniques may be used to ensure that setting changes 208 sent over the network 204 remain secure. For instance, security protocols, such as SSL (Secure Sockets Layer) and HTTPS (HyperText Transfer Protocol Secure), may be used. In addition, authentication information, such as passwords, tokens, or the like, may be required to access the Web server 120.

Unlike conventional approaches, the above-described technique for configuring a portable data reader 100 is not limited to single connections via a synchronization program, such as ActiveSync®. The multithreaded nature of browsers 202 permit multiple portable data readers 100 to be configured at the same time. Furthermore, any number of portable data readers 100 may be configured with only a few mouse clicks on the remote personal computer 206 anywhere in the world where an Internet connection is available.

Referring to FIG. 4, a process is shown for interrogating (i.e., reading and reporting) one or more settings 126 of a portable data reader 100 using an integrated Web server 120. Initially, the browser 202 establishes a communication channel with the Web server 120 as described with reference to FIG. 2. Thereafter, using the Web page 124, the user specifies the desired settings 126 within the portable data reader 100 to interrogate. The Web page 124 may help the user formulate a settings inquiry 402 to be transmitted through the network 204 to the Web server 120.

In one implementation, a settings inquiry 402 is formatted in HTML as follows:

    • http://<terminal IP>/SymGet?<setting>
      where <setting> specifies the desired settings 126 or a string that can be matched with one or more settings 126. For instance, a user may desire to interrogate settings 126 related to Code 39. In this case, the settings inquiry 402 may be composed as http://<terminal IP>/SymGet?C39. In one embodiment, the identifier “C39” will be matched against any setting 126 having a name that begins with “C39.”

In response to the settings inquiry 402, the Web server 120 automatically invokes a particular server-side application 122, i.e., an interrogation application 404. As in the case of the configuration application 210, the interrogation application 404 may be automatically invoked using scripts or other server-side code. When invoked, the interrogation application 402 interrogates the specified settings 126 of the portable data reader 100 and provides one or more interrogated settings 406 to the Web server 120. For clarity of description, different server-side applications 122 are assigned to different functions, e.g., configuration and setting interrogation. However, a single server-side application 122 supporting multiple functions could also be used.

In one embodiment, the Web server 120 formats the interrogated settings 126 into a Web page 124. The Web page 124 produced in response to the above settings inquiry 402 may be formatted as follows:

<HTML> <HEAD> PSC Falcon Web Interface </HEAD> <BODY> Code39 Enable = 1 Code39 Check Digit Enable = 1 </BODY> </HTML>

Of course, the Web page 124 may be formatted in other ways. After creating the Web page 124, the Web server 120 transmits the Web page 124 including the interrogated settings 406 to the browser 202 for display.

Referring to FIG. 5, a process is shown for extracting read data 128 from a portable data reader 100 using an integrated Web server 120. As explained above, the reading engine 102 within a portable data reader 100 may read symbols 502 (such as barcodes) from physical objects 504. The symbols 502 may be stored as read data 128 within the portable data reader 100.

Initially, the browser 202 establishes a communication channel with the Web server 120 as described with reference to FIG. 2. Thereafter, the user may employ a Web page 124 retrieved from the Web server 120 to compose an extraction command 506. The extraction command 506 may be formatted in HTML, although the precise formatting is not crucial. In one embodiment, the extraction command 506 requests all read data 128 stored by the portable data reader 100. Alternatively, the extraction command requests some subset of the read data 128, e.g., a date or time range.

The browser 202 transmits the extraction command 506 to the Web server 120 via the network 204. In response, the Web server 120 automatically invokes a particular server-side application 122, i.e., a data extraction application 508. The data extraction application 508 reads the read data 128 or subset thereof and provides extracted data 510 to the Web server 120.

In one embodiment, the Web server 120 formats the extracted data 510 into a Web page 124, which is then sent to the browser 202 for display. The particular formatting of the extracted data 510 will vary depending on the type of reading engine 102. For instance, the extracted data 510 may include a list of scanned symbols with an indication of the date and time at which each symbol was scanned. Alternatively, the extracted data 510 may comprise various types of information read from RFID tags.

Referring to FIG. 6, a process is shown for updating a file system 130 of a portable data reader 100. As explained above, the memory 116 of the portable data reader 100 may include a file system 130, which may be used to store, among other things, the OS 118, settings 126, Web server 120, server-side applications 122, Web page 124, and the like.

In certain instances, it may be desirable to remotely deploy or update a file system 130 of one or more portable data readers 100. Installing individual applications on a portable data reader 100 is time consuming. The problem is compounded when dealing with multiple readers 100.

As illustrated, a file system image 602 containing all or a subset of the data within the file system 130 of a portable data reader 100 may be stored within a personal computer 206. The file system image 602 may be created using various available or custom-designed utilities running on the portable data reader 100 and/or the personal computer 206. Examples of available utilities for creating fie system images 602 include Windows CE NET Platform Builder, available from Microsoft, Norton GhoSt™ 2003, available from Symantec™, and Sprite Clone™, available from Sprite Software™. In other embodiments, an image backup utility packaged with the OS 118 may be used.

The file system image 602 or a link thereto may be provided to the browser 202, which formats the file system image 602 for transmission to the Web server 120 over the network 204. In one embodiment, upon receiving a file system image 602, the Web server 120 automatically invokes a particular server-side application 122, i.e., an update application 604, to replace the file system 130 (or portion thereof) of the portable data reader 100 with the file system represented within the file system image 602. In certain configurations, the update application 604 may be embodied as an image restoration utility packaged with the OS 118. In other embodiments, a commercially-available or custom-designed utility may be used for this purpose.

The above-described technique may be used to completely reconfigure the portable data reader 100, even replacing the OS 118, changing all or part of the settings 126, providing new or different server-side applications 122, etc. For instance, the portable data reader 100 may be switched between inventory, shipping, and receiving applications with a simple click of the mouse button on the personal computer 206.

FIG. 7 illustrates a related process of cloning a file system image 602 of one portable data reader 100 to one or more other portable data readers 100. Cloning may be performed with or without the intervention of a remote personal computer 206. For example, the browser 202 may send a clone command 702 to a Web server 120 within a first portable data reader 100a. In response, the Web server 120 may automatically invoke a particular server-side application 122, i.e., a cloning application 704, which creates an image 602 of the file system 130 of the portable data reader 100a.

The cloning application 704 provides the created file system image 602 to the Web server 120, which formats the file system image 602 for transmission over the network 204 to Web servers 120 in two other portable data readers 100b-c. The specific portable data readers 100b-c to receive the file system images 602 may be indicated within the clone command 702. In certain embodiments, the transmitted images 602 may be accompanied by instructions to cause the receiving portable data readers 100b-c to update their file systems 130.

When respective Web servers 120 of the portable data readers 100b-c receive the file system images 602, the Web servers 120 may automatically invoke update applications 604, as described with reference to FIG. 6, which replace the file systems 130 of each portable data reader 100 with that of the file system images 602. Thus, with a single command sent over a network 204, such as the Internet, a user may clone the file system 130 of one portable data reader 100a to any number of other portable data readers 100, saving significant time over conventional approaches.

In an alternative embodiment, the remote personal computer 206 may not be used. Instead, a user of the first portable data reader 100 may use local browser 202 (not shown) to access the Web server 120 and invoke a clone command 702. In such an embodiment, the user may specify, for example, which other portable data readers 100 are to receive copies of the file system image 602.

In addition to the configuration application 210, interrogation application 404, data extraction application 508, update application 604, and cloning application 704, various other server-side applications 122 may be included. For instance, server-side applications 122 may be provided for one or more of the following purposes:

    • file transfers
    • remote application launch
    • remote method invocation
    • distributed computing among peers
    • redundant data paths for file transfers and OS updates
    • remote registry setting
    • messaging
    • reporting, system level and system statistics.

Referring to FIG. 8, a flowchart is shown of a method 800 for configuring one or more settings 126 of a portable data reader 100. Initially, a user, administrator, or manufacturer integrates 802 a Web server 120 with the portable data reader 100, as described with reference to FIG. 1. The Web server 120 may be embodied, for instance, as a standard Windows CE-based Web server 120, such as HTTPD or the like.

In addition, the user, administrator, or manufacturer integrates 804 a server-side application 122 with the portable data reader 100 for modifying scanner settings 126. In one embodiment, the sever-side application 122 may be invoked using server-side scripts or other code within a Web page 124 served by the Web server 120 to a browser 202 within a remote personal computer 206.

To change a setting 126, the user/operator establishes 806 a communication channel between the portable data reader 100 and the browser 202 over a network 204, such as the Internet. Typically, a connection is accomplished in response to the user typing a URL for the desired portable data reader 100 into the browser 202. Once a communication channel is established, the user/operator causes the browser 202 to send formatted data representing requested setting changes 208 for the portable data reader 100, which are subsequently received 808 by the Web server 120. In response, the Web server 120 automatically invokes 810 the server-side application 122 to modify the settings 126 of the portable data reader 100 consistent with the requested setting changes 208.

Those of skill in the art will recognize that similar methods may be employed with respect to setting interrogation, data extraction, file system updating, cloning, and other features that can be implemented using server-side applications.

While specific embodiments and applications of the present invention have been illustrated and described, it is to be understood that the invention is not limited to the precise configuration and components disclosed herein. Various modifications, changes, and variations apparent to those of skill in the art may be made in the arrangement, operation, and details of the methods and systems disclosed herein without departing.

Embodiments may include various steps, which may be represented as machine-executable instructions to be executed by a general-purpose or special-purpose computer (or other electronic device). Alternatively, the steps may be performed by hardware components that contain specific logic for performing the steps, or by any combination of hardware, software, and/or firmware.

Embodiments may also be provided as a computer program product including a machine-readable medium having stored thereon instructions that may be used to program a computer (or other electronic device) to perform processes described herein. The machine-readable medium may include, but is not limited to, floppy diskettes, optical disks, CD-ROMs, DVD-ROMS, ROMs, RAMs, EPROMs, EEPROMs, magnetic or optical cards, propagation media or other type of media/machine-readable medium suitable for storing electronic instructions. For example, instructions for performing described processes may be transferred from a remote computer (e.g., a server) to a requesting computer (e.g., a client) by way of data signals embodied in a carrier wave or other propagation medium via a communication link (e.g., network connection).

Claims

1. A portable data reading device comprising:

a Web server to deliver Web pages to a client browser; and
a first server-side application to update a file system of the portable data reading device,
wherein the Web server is to receive formatted data from the client browser representing an updated file system, and
wherein the Web server is to automatically invoke the first server-side application to replace the file system of the portable data reading device with the updated file system

2. The portable data reading device of claim 1, further comprising a barcode scan engine to read one or more symbols from a physical object.

3. The portable data reading device of claim 1, further comprising a communication interface to communicate with the client browser through a network.

4. The portable data reading device of claim 1, further comprising a Web page comprising code to replace the file system of the portable data reading device with the updated file system.

5. The portable data reading device of claim 4, wherein the Web page comprises a server-side page, and wherein the code comprises an embedded script.

6. The portable data reading device of claim 1, further comprising:

a second server-side application to clone a file system of the portable data reading device to at least one other portable data reading device,
wherein the Web server to automatically invoke the second server-side application to create a cloned image of the file system of the portable data reading device, and
wherein the Web server is to send formatted data representing the cloned image to at least one other portable data reading device with instructions for the at least one other portable data reading device to replace its file system with the file system from the cloned image.

7. A portable scanning system comprising:

a reading engine;
a communication interface to connect the portable scanning system to a client browser through a network; and
a memory coupled to the reading engine and the communication interface, the memory comprising: a Web server to deliver Web pages to a client browser; and a first server-side application to update a file system of the portable data reading device, wherein the Web server is to receive formatted data from the client browser representing an updated file system and automatically invoke the first server-side application to replace the file system of the portable data reading device with the updated file system.

8. The portable scanning system of claim 7, wherein the memory further comprises:

a second server-side application to clone a file system of the portable data reading device to one or more other portable data reading devices,
wherein the Web server is to automatically invoke the second server-side application to create a cloned image of the file system of the portable data reading device and send formatted data representing the cloned image to at least one other portable data reading device with instructions for the at least one other portable data reading device to replace its file system with that of the cloned image.

9. A method for updating a file system of a portable data reader including an integrated Web server, the method comprising:

receiving at the Web server formatted data representing an updated file system; and
invoking a first server-side application to replace a file system of the portable data reader with the updated file system.

10. The method of claim 9, further comprising:

invoking a second server-side application to create a cloned image of a file system of the portable data reader; and
sending formatted data representing the cloned image to at least one specified portable data reader with instructions for the specified portable data reader to update its file system with the cloned image.

11. The method of claim 9, further comprising delivering to a client browser a Web page comprising code to automatically invoke the first server-side application.

12. A method comprising:

integrating a portable data reader with a Web server to deliver Web pages to a client browser;
integrating the portable data reader with a first server-side application to update a file system of the portable data reader;
receiving formatted data from the client browser representing an updated file system; and
automatically invoking the first server-side application to replace the file system of the portable data reader with the updated file system.

13. The method of claim 12, further comprising integrating the portable data reader with a communication interface to communicate with the client browser through a network.

14. The method of claim 13, further comprising integrating the portable data reader with a Web page comprising code to cause the Web server to automatically invoke the first server-side application.

15. The method of claim 14, wherein integrating the portable data reader with a Web page comprises integrating the portable data reader with an server-side page in which the code comprises an embedded script.

16. The method of claim 12, further comprising:

integrating the portable data reader with a second server-side application to clone a file system of the portable data reader to at least one specified portable data reader;
automatically invoking the second server-side application to create a cloned image of the file system of the portable data reader; and
sending formatted data representing the cloned image from the Web server to at least one specified portable data reader with instructions for the at least one specified portable data reader to replace its file system with the file system from the cloned image.

17. A portable data reader comprising:

a reading engine;
a Web server coupled to the reading engine; and
a server-side application coupled to the Web server to clone a file system of the portable data reading device to at least one other portable data reader,
wherein the Web server to automatically invoke the server-side application to create a cloned image of the file system of the portable data reader, and
wherein the Web server is to send formatted data representing the cloned image to at least one other portable data reader with instructions for the at least one other portable data reader to replace its file system with the file system from the cloned image.
Patent History
Publication number: 20070063049
Type: Application
Filed: Nov 17, 2006
Publication Date: Mar 22, 2007
Inventors: Gary Anson (Cheshire, OR), Ryan Elliott (Eugene, OR)
Application Number: 11/601,419
Classifications
Current U.S. Class: 235/462.460
International Classification: G06K 7/10 (20060101);