PTO/SB/14 (07-07)
`Approved for use through 06/30/2010. OMB 0651-0032
`U.S. Patent and Trademark Office; U.S. DEPARTMENT OF COMMERCE
`Under the Paperwork Reduction Act of 1995, no persons are required to respond to a collection of information unless it contains a valid OMB control number.
`
`Application Data Sheet 37 CFR 1.76
`
`Attorney Docket Number
`
`57442/10-351
`
`Application Number
`
`Title of Invention
`
`SYSTEM AND METHOD FOR DATA MANAGEMENT
`
`The application data sheet is part of the provisional or nonprovisional application for which it is being submitted. The following form contains the
`bibliographic data arranged in a format specified by the United States Patent and Trademark Office as outlined in 37 CFR 1.76.
`This document may be completed electronically and submitted to the Office in electronic format using the Electronic Filing System (EFS) or the
`document may be printed and included in a paper filed application.
`
`Secrecy Order 37 CFR 5.2
`D Portions or all of the application associated with this Application Data Sheet may fall under a Secrecy Order pursuant to
`37 CFR 5.2 (Paper filers only. Applications that fall under Secrecy Order may not be filed electronically.)
`
`Applicant Information:
`Applicant 1
`Applicant Authority @Inventor I QLegal Representative under 35 U.S.C. 117
`Prefix Given Name
`Middle Name
`
`I Remove I
`I QParty of Interest under 35 U.S.C. 118
`
`Family Name
`
`Suffix
`
`Payne
`Mr.
`David
`J.
`Residence Information (Select One) (!) US Residency 0 Non US Residency O Active US Military Service
`I Country of Residence i I us
`City
`Broken Arrow
`State/Province
`I OK
`us
`
`Citizenship under 37 CFR 1.41(b) i
`
`Mailing Address of Applicant:
`
`Address 1
`
`1717 South Boulder
`
`Address 2
`I Tulsa
`Postal Code
`
`City
`
`Suite 700
`
`I State/Province
`I Countryi I us
`74119
`All Inventors Must Be Listed - Additional Inventor Information blocks may be
`generated within this form by selecting the Add button.
`
`I OK
`
`I Add
`
`I
`
`Correspondence Information:
`Enter either Customer Number or complete the Correspondence Information section below.
`For further information see 37 CFR 1.33(a).
`D An Address is being provided for the correspondence Information of this application.
`Customer Number
`22206
`
`Email Address
`
`patents@fellerssnider.com
`
`Application Information:
`
`I I Add Email I
`
`!Remove Emaill
`
`Title of the Invention
`
`SYSTEM AND METHOD FOR DATA MANAGEMENT
`Attorney Docket Number 57442/10-351
`I Small Entity Status Claimed ~
`
`Application Type
`
`Nonprovisional
`
`Subject Matter
`
`Utility
`
`Suggested Class (if any)
`
`Suggested Technology Center (if any)
`
`I Sub Class (if any)I
`
`Total Number of Drawing Sheets (if any)
`
`I Suggested Figure for Publication (if any) I
`
`EFS Web 2.2.2
`
`Unified Patents
`Exhibit 1002
`Page 1 of 2584
`
`

`

`PTO/SB/14 (07-07)
`Approved for use through 06/30/2010. OMB 0651-0032
`U.S. Patent and Trademark Office; U.S. DEPARTMENT OF COMMERCE
`Under the Paperwork Reduction Act of 1995, no persons are required to respond to a collection of information unless it contains a valid OMB control number.
`
`Application Data Sheet 37 CFR 1.76
`
`Attorney Docket Number
`
`57442/10-351
`
`Application Number
`
`Title of Invention
`
`SYSTEM AND METHOD FOR DATA MANAGEMENT
`
`Publication Information:
`D Request Early Publication (Fee required at time of Request 37 CFR 1.219)
`Request Not to Publish. I hereby request that the attached application not be published under 35
`D U.S.C. 122(b) and certify that the invention disclosed in the attached application has not and will not be the
`subject of an application filed in another country, or under a multilateral international agreement, that requires
`publication at eighteen months after filing.
`
`Representative Information:
`
`Representative information should be provided for all practitioners having a power of attorney in the application. Providing
`this information in the Application Data Sheet does not constitute a power of attorney in the application (see 37 CFR 1.32).
`Enter either Customer Number or complete the Representative Name section below. If both sections
`are completed the Customer Number will be used for the Representative Information during processing.
`I 0 US Patent Practitioner 10 Limited Recognition (37 CFR 11.9)
`
`Please Select One:
`
`C!J Customer Number
`22206
`
`Customer Number
`
`Domestic Benefit/National Stage Information:
`This section allows for the applicant to either claim benefit under 35 U.S.C. 119(e), 120, 121, or 365(c) or indicate National Stage
`entry from a PCT application. Providing this information in the application data sheet constitutes the specific reference required by
`35 U.S.C. 119(e) or 120, and 37 CFR 1.78(a)(2) or CFR 1.78(a)(4), and need not otherwise be made part of the specification.
`I Remove I
`Filing Date (YYYY-MM-DD)
`
`Application Number
`
`Continuity Type
`
`Prior Application Number
`
`Prior Application Status Pending
`
`Prior Application Status Expired
`
`Continuation of
`
`10643516
`
`Application Number
`
`Continuity Type
`
`Prior Application Number
`
`10643516
`
`non provisional of
`
`60404491
`
`Additional Domestic Benefit/National Stage Data may be generated within this form
`by selecting the Add button.
`
`2003-08-19
`I Remove I
`Filing Date (YYYY-MM-DD)
`
`2002-08-19
`I Add I
`
`Foreign Priority Information:
`This section allows for the applicant to claim benefit of foreign priority and to identify any prior foreign application for which priority is
`not claimed. Providing this information in the application data sheet constitutes the claim for priority as required by 35 U.S.C. 119(b)
`and 37 CFR 1.55(a).
`I Remove I
`Parent Filing Date (YYYY-MM-DD)
`Priority Claimed
`C!J Yes 0 No
`I Add I
`
`Application Number
`
`Country i
`
`Additional Foreign Priority Data may be generated within this form by selecting the
`Add button.
`
`EFS Web 2.2.2
`
`Unified Patents
`Exhibit 1002
`Page 2 of 2584
`
`

`

`PTO/SB/14 (07-07)
`Approved for use through 06/30/2010. OMB 0651-0032
`U.S. Patent and Trademark Office; U.S. DEPARTMENT OF COMMERCE
`Under the Paperwork Reduction Act of 1995, no persons are required to respond to a collection of information unless it contains a valid OMB control number.
`
`Application Data Sheet 37 CFR 1.76
`
`Attorney Docket Number
`
`57442/10-351
`
`Application Number
`
`Title of Invention
`
`SYSTEM AND METHOD FOR DATA MANAGEMENT
`
`Assignee Information:
`Providing this information in the application data sheet does not substitute for compliance with any requirement of part 3 of Title 37
`of the CFR to have an assignment recorded in the Office.
`I Remove I
`
`Assignee 1
`If the Assignee is an Organization check here.
`
`Organization Name
`
`I Macrosolve, Inc.
`Mailing Address Information:
`
`1717 South Boulder
`
`Suite 700
`
`Tulsa
`
`Address 1
`
`Address 2
`
`City
`Country ii us
`
`Phone Number
`
`Email Address
`
`~
`
`State/Province
`
`Postal Code
`
`Fax Number
`
`OK
`
`74119
`
`Additional Assignee Data may be generated within this form by selecting the Add
`button.
`
`I Add I
`
`Signature:
`A signature of the applicant or representative is required in accordance with 37 CFR 1.33 and 10.18. Please see 37
`CFR 1.4(d) for the form of the signature.
`
`Signature
`
`/scot! r. zingerman/
`
`Date (YYYY-MM-DD) 2010-10-22
`
`First Name
`
`Scott
`
`I Last Name I Zingerman
`
`Registration Number
`
`35422
`
`This collection of information is required by 37 CFR 1.76. The information is required to obtain or retain a benefit by the public which
`is to file (and by the USPTO to process) an application. Confidentiality is governed by 35 U.S.C. 122 and 37 CFR 1.14. This
`collection is estimated to take 23 minutes to complete, including gathering, preparing, and submitting the completed application data
`sheet form to the USPTO. Time will vary depending upon the individual case. Any comments on the amount of time you require to
`complete this form and/or suggestions for reducing this burden, should be sent to the Chief Information Officer, U.S. Patent and
`Trademark Office, U.S. Department of Commerce, P.O. Box 1450, Alexandria, VA 22313-1450. DO NOT SEND FEES OR
`COMPLETED FORMS TO THIS ADDRESS. SEND TO: Commissioner for Patents, P.O. Box 1450, Alexandria, VA 22313-1450.
`
`EFS Web 2.2.2
`
`Unified Patents
`Exhibit 1002
`Page 3 of 2584
`
`

`

`Privacy Act Statement
`
`The Privacy Act of 1974 (P .L. 93-579) requires that you be given certain information in connection with your submission of the attached form related to
`a patent application or patent. Accordingly, pursuant to the requirements of the Act, please be advised that: (1) the general authority for the collection
`of this information is 35 U.S.C. 2(b)(2); (2) furnishing of the information solicited is voluntary; and (3) the principal purpose for which the information is
`used by the U.S. Patent and Trademark Office is to process and/or examine your submission related to a patent application or patent. If you do not
`furnish the requested information, the U.S. Patent and Trademark Office may not be able to process and/or examine your submission, which may
`result in termination of proceedings or abandonment of the application or expiration of the patent.
`
`The information provided by you in this form will be subject to the following routine uses:
`
`1.
`
`2.
`
`3.
`
`4.
`
`5.
`
`6.
`
`7.
`
`8.
`
`The information on this form will be treated confidentially to the extent allowed under the Freedom of Information Act (5 U.S.C. 552) anc
`the Privacy Act (5 U.S.C. 552a). Records from this system of records may be disclosed to the Department of Justice to determine whether
`the Freedom of Information Act requires disclosure of these records.
`
`A record from this system of records may be disclosed, as a routine use, in the course of presenting evidence to a court, magistrate, or
`administrative tribunal, including disclosures to opposing counsel in the course of settlement negotiations.
`
`A record in this system of records may be disclosed, as a routine use, to a Member of Congress submitting a request involving an
`individual, to whom the record pertains, when the individual has requested assistance from the Member with respect to the subject matter of
`the record.
`
`A record in this system of records may be disclosed, as a routine use, to a contractor of the Agency having need for the information in
`order to perform a contract. Recipients of information shall be required to comply with the requirements of the Privacy Act of 1974, as
`amended, pursuant to 5 U.S.C. 552a(m).
`
`A record related to an International Application filed under the Patent Cooperation Treaty in this system of records may be disclosed, a~
`a routine use, to the International Bureau of the World Intellectual Property Organization, pursuant to the Patent Cooperation Treaty.
`
`A record in this system of records may be disclosed, as a routine use, to another federal agency for purposes of National Security
`review (35 U.S.C. 181) and for review pursuant to the Atomic Energy Act (42 U.S.C. 218(c)).
`
`A record from this system of records may be disclosed, as a routine use, to the Administrator, General Services, or his/her designee,
`during an inspection of records conducted by GSA as part of that agency's responsibility to recommend improvements in records
`management practices and programs, under authority of 44 U.S.C. 2904 and 2906. Such disclosure shall be made in accordance with the
`GSA regulations governing inspection of records for this purpose, and any other relevant (i.e., GSA or Commerce) directive. Such
`disclosure shall not be used to make determinations about individuals.
`
`A record from this system of records may be disclosed, as a routine use, to the public after either publication of the application pursuan
`to 35 U.S.C. 122(b) or issuance of a patent pursuant to 35 U.S.C. 151. Further, a record may be disclosed, subject to the limitations of 37
`CFR 1.14, as a routine use, to the public if the record was filed in an application which became abandoned or in which the proceedings were
`terminated and which application is referenced by either a published application, an application open to public inspections or an issued
`patent.
`
`9.
`
`A record from this system of records may be disclosed, as a routine use, to a Federal, State, or local law enforcement agency, if the
`USPTO becomes aware of a violation or potential violation of law or regulation.
`
`EFS Web 2.2.2
`
`Unified Patents
`Exhibit 1002
`Page 4 of 2584
`
`

`

`METHOD AND SYSTEM FOR DATA MANAGEMENT
`
`CROSS REFERENCE TO RELATED APPLICATION
`
`[0001] This application claims the benefit of U.S. Provisional Application No.
`
`60/404,491 filed August 19, 2002, and is a continuation of co-pending U.S. Application No.
`
`10/643,516 filed on August 19, 2003, scheduled to issue as U.S. Patent No. 7,822,816 on
`
`October 26, 2010, herein incorporated by reference in its entirety for all purposes.
`
`BACKGROUND OF THE INVENTION
`
`1.
`
`Field of the Invention
`
`[0002] The present invention relates to a system of computing devices for the
`
`collection and management of information. More particularly, but not by way of limitation,
`
`the present invention relates to a system for collecting and managing information including
`
`a plurality of computer devices loosely networked to a server and an operating system for a
`
`computer which provides a number of features favorable for use in the inventive system.
`
`2.
`
`Background of the Invention
`
`[0003] Virtually all business software applications
`
`involve
`
`the collection of
`
`information in some form or another. Where information is gathered away from the
`
`convenience of a desktop, workers have traditionally entered the information on paper forms.
`
`This data is then entered into a computer in a second step. This extra step leads to delays and
`
`1
`
`Unified Patents
`Exhibit 1002
`Page 5 of 2584
`
`

`

`inaccuracies which are costly and, more importantly, unnecessary.
`
`[0004) Handheld computers are well known in the art. In fact such computers are
`
`presently available from numerous manufacturers offering a vast assortment of operating
`
`systems and hardware configurations. While such devices come in a host of variations,
`
`generally handheld computers include an LCD display, a method for gathering manual input,
`
`storage, and a variety of machine interfaces, i.e., an IR link, a USB port, a serial port, etc.
`
`[0005) As with their desktop, and laptop counterparts, a handheld computer will also
`
`include an operating system which provides an operator interface, file management, and
`
`standardized VO, as well as facilitating the running of application programs. Thus far,
`
`handheld operating systems mimic those of desktop and laptop systems, despite the fact that
`
`handheld devices are typically used in a different manner and have radically different
`
`resources.
`
`[0006) As with other types of computers, handheld computers suffer from
`
`compatibility issues, especially in the operation of application programs. Generally speaking,
`
`software programs must typically be tailored to a specific family of processors and to a
`
`specific operating system. Most applications are developed in a high level language and then
`
`compiled for a specific target processor. As different manufacturers select different
`
`processors, an application written for one family of processors must be recompiled to execute
`
`in a processor of a different family. Even when two manufacturers select compatible
`
`processors, if they chose different operating systems, applications written for one device will
`
`probably not run correctly on the other device. Since the operating system provides access
`
`2
`
`Unified Patents
`Exhibit 1002
`Page 6 of 2584
`
`

`

`to the various hardware resources and manages the file system, it is almost unfathomable that
`
`the operating systems of independent authors would be compatible, unless one specifically
`
`set out to copy the other. Thus, particular applications tend to grow up around a particular
`
`family of devices which share an operating system and, unfortunately, the application may
`
`not be available for non-compatible devices.
`
`[0007] Another issue which is common to all computers is the transferability of
`
`stored information, specifically, the ability to move files from machine-to-machine. While
`
`most handheld computers include an infrared port for communicating with other infrared
`
`devices, including other handhelds, files transferred in such a manner may not be usable by
`
`software on the receiving device. This is especially true of information formatted for a
`
`particular application such as a word processor, spread sheet program, data base manager,
`
`or the like.
`
`(0008] To overcome the necessity of compiling a program for a particular machine,
`
`an application may be written in an interpreted language, or a language which can be
`
`compiled to produce an intermediate language (i.e., a language that falls somewhere between
`
`source code and object code) such as i-code or tokens. In such a scheme, each device is
`
`provided with a run-time package which can execute the compiled i-code or tokens, the run(cid:173)
`
`time package having been written for that particular device, thus, only the run-time package
`
`needs to be modified in order to port a program to a new computing environment. Once ,the
`
`run-time package is installed, any application authored in the language and which has been
`
`compiled to i-code will run on the target device. Unfortunately, such languages typically
`
`3
`
`Unified Patents
`Exhibit 1002
`Page 7 of 2584
`
`

`

`lack effective optimization and generally do not provide a broad range. of support for
`
`hardware resources. Regardless of the language selected, whether compiled, interpreted, or
`
`whatever, software coding requires at least a nominal degree of programming skill to create
`
`the application program.
`
`[0009] Perhaps because handheld computers are not as evolved as their desktop
`
`counterparts, or because it is typically cumbersome to enter information, or maybe due to the
`
`lack of a true front-runner in operating systems, handheld computers have not inspired the
`
`full range of software products available for larger computers. The result has been a rather
`
`limited selection of retail software applications for handheld devices as compared with their
`
`desktop counterparts, such software is aimed primarily at organizational tools, e-mail, and
`
`games. However, at the other end of the spectrum, custom programs tailored for a specific
`
`customer, handheld computers are gaining momentum in replacing manual forms which are
`
`often filled-out in remote areas, away from a desktop, i.e. manufacturing inventory, quality
`
`inspections, delivery systems, and the like. One reason for the increasing movement toward
`
`the use of handheld computers for data gathering tasks is that they can be easily transported
`
`to the source of the data and have the information directly entered into them, thereby
`
`eliminating the potentially error-prone step of manual data entry of information on previously
`
`completed paper forms. Eliminating the extra step additionally saves unnecessary labor, and
`
`allows the data to be entered in a more timely fashion.
`
`(0010] Due to their incredible portability, handhelds are particularly well suited to
`
`this type of data gathering, despite an obvious lack of software infrastructure in this area.
`
`4
`
`Unified Patents
`Exhibit 1002
`Page 8 of 2584
`
`

`

`The present trend is for a business to commission the authoring of a custom program aimed
`
`at a particular need. While the cost of such an application is usually high, the accuracy of
`
`the information, the timeliness of the information, and the accessibility of the information
`
`are likely worth the cost. In fact, while such systems may seem cost prohibitive to develop,
`
`in many cases the actual cost on a per-data-entry basis may prove to be relatively small,
`
`especially in light of the timeliness and accuracy associated with real time data collection.
`
`[0011] To develop software for a handheld computer, a custom program is typically
`
`developed and tested on a larger system. When the developer is satisfied with the program,
`
`it is compiled for a particular target device and transferred to handheld devices through a
`
`communication link. If users are using more than one type of device, the same program must
`
`be tested and compiled for each type of device. If a change is required, the developer must
`
`make the change on the development system and re-transfer the entire program to each target
`
`device.
`
`[0012] In a typical data gathering application, information is entered into custom
`
`designed forms on the handheld computer. Eventually, the data entered in the handheld finds
`
`its way to a database, which is typically located on a server which is accessible to those
`
`needing the information or from which it may be accessed by other programs such as
`
`accounting systems, materials management programs, etc. Present day servers are well
`
`suited to the task of information management and generally provide broad access to and
`
`searchability to collected data.
`
`[0013] One problem area in such systems becomes apparent when the data is
`
`5
`
`Unified Patents
`Exhibit 1002
`Page 9 of 2584
`
`

`

`transferred from the handheld to the server. While it would seem that wireless interfaces and
`
`handhelds were made for each other, the marriage of the two is not without its own set of
`
`problems. Wireless interfaces fall into a number of different categories. At one extreme is
`
`the infrared ("IR") port often found on handheld devices. The range of this type of interface
`
`is usually limited to a few feet and typically supports transfer rates of 115 kbaud, or less.
`
`[0014) Another method for wireless communication is via a wireless local area
`
`network or "WLAN." A typical example of a WLAN is that defined by the IEEE 802.11
`
`standard. When a handheld computer is equipped with a WLAN interface, the device can
`
`communicate with other computers also equipped with a WLAN interface, or even
`
`computers networked to a WLAN equipped computer by a wired network. Typically,
`
`WLAN interfaces provide a range of several hundred feet. As long as a handheld is within
`
`the range of another WLAN equipped computer, the network connection is continuous.
`
`Wireless local area networks sport data rates from a few thousand bits per second up to at
`
`least 52 million bits per second, depending on the particular standard employed.
`
`[0015) Yet another known wireless interface for handheld computers is a CDPD
`
`interface, CDMA interface, GSM interface, or similar wireless interface or modem. While
`
`there are some variations, these systems are often built around a cellular phone network and
`
`provide coverage similar to that of a cellular phone, typically national, or even international,
`
`coverage. Such interfaces will experience the same gaps in service as can be expected with
`
`a cell phone. While such systems provide an exceptionally wide area of coverage, they
`
`typically do so at limited bandwidth, e.g. 19.2 kbaud.
`
`6
`
`Unified Patents
`Exhibit 1002
`Page 10 of 2584
`
`

`

`(0016) Of course handheld devices are not limited to wireless communications.
`
`Typically such devices can be connected to another computer through a universal serial bus
`
`("USB") connection, an RS-232 connection, an Ethernet connection on a properly equipped
`
`device, or similar hardwired connection. While these interfaces range from moderately
`
`paced to the extremely fast, they are exceptionally reliable, at least while the connection is
`
`in place. Unfortunately, few environments are well suited to tethering a handheld to allow
`
`a continuous wired connection.
`
`[0017) It can be seen that perhaps the greatest drawback to using a handheld for data
`
`gathering as part of a larger system are the limitations of the data link: 1) it is unlikely that
`
`the data link will always be available; and 2) the bandwidth of most of the practical wireless
`
`options is restrictive. Presently there are two methods for dealing with the problem of data
`
`link availability. In one scheme, data is transmitted as it is collected. The advantage of such
`
`a scheme is that the database is updated in real time and represents current data. The
`
`disadvantages are, for all practical purposes, the scheme is limited to systems using a
`
`wireless interface and when the wireless link is not operational, generally data cannot be
`
`entered.
`
`[0018) Alternatively, entered data can be stored locally on the handheld and
`
`transmitted in a batch process when a link is established. The advantage of this system is
`
`that it is tolerant of gaps in the communication link and works well with wired transfers of
`
`data. Unfortunately, data is not delivered in real time and the data base may be somewhat
`
`stale, depending on the length of time between the collection of data and the presence of the
`
`7
`
`Unified Patents
`Exhibit 1002
`Page 11 of 2584
`
`

`

`link.
`
`(0019] The issue of bandwidth may be problematic on several fronts. If programs
`
`are updated periodically, the entire program must be sent and the time to reload may be
`
`objectionable. In the opposite direction, iflarge amounts of data are collected, it may be time
`
`consuming to send the data collected from the handheld to the server, particularly when
`
`performed in a batch fashion.
`
`[0020) It is thus an object of the present invention to provide an operating system
`
`for a handheld computer which will allow a program to execute on any handheld computer.
`
`[0021] It is a further object of the present invention to provide an operating system
`
`for a handheld computer wherein programming changes will only necessitate incremental
`
`transfers of program instructions.
`
`(0022] It is still a further object of the present invention to provide an operating
`
`system for a handheld computer wherein files may be transferred among devices without a
`
`translation or conversion.
`
`(0023] It is yet a further object of the present invention to provide an operating
`
`system for a handheld computer wherein programming steps and data are tokenized to reduce
`
`the load on a communication channel of finite bandwidth.
`
`(0024) It is yet a further object of the present invention to provide a system of
`
`networked computers in which modifications to a computer program for a remote computer
`
`are sent in real time to the remote computer and are implemented immediately and
`
`seamlessly without the requirement of user installation.
`
`8
`
`Unified Patents
`Exhibit 1002
`Page 12 of 2584
`
`

`

`SUMMARY OF THE INVENTION
`
`[0025] The present invention provides a system and method for the management of
`
`information which solves the problems and alleviates the needs discussed above. In its
`
`broadest sense, the present invention is a method designed to accomplish the following:
`
`1) Allow any computer(s) (desktops, laptops, handhelds, portables,
`
`etc.) to be used to capture information;
`
`2) Transfer the information to a data center (via file transfer methods
`
`such as a network, to include, but not necessarily, Internet based) in
`
`a form that the data center can recognize;
`
`3) Allow another computer(s) to access the information and
`
`download it from the data center in a format that can be readily used
`
`regardless of the format in which the original information was
`
`gathered.
`
`[0026] In a preferred embodiment, a server is loosely networked to a plurality of
`
`computers (hand.held, laptop, or desktop). Each computer is equipped with an operating
`
`system which allows common programming to execute on any device, regardless of hardware
`
`differences or native operating system differences among the plurality of devices.
`
`[0027] With regard to the present invention, the term "loosely networked" is used
`
`to describe a networked computer system wherein devices on the network are tolerant of
`
`intermittent network connections and, in fact, tolerant of the type of network connection
`
`available.
`
`In particular, if any communication connection is available between devices
`
`9
`
`Unified Patents
`Exhibit 1002
`Page 13 of 2584
`
`

`

`wishing to communicate, network transmissions occur normally, in real time. If a network
`
`connection is unavailable at that moment, the information is temporarily stored in the device
`
`and later transmitted when the connection is restored. Unless otherwise specified, hereinafter
`
`the terms "network" or "networked" refer to loosely networked devices.
`
`[0028) Thus, the operating system may be thought of as device indifferent and
`
`communication channel indifferent. In the preferred embodiment, any computer can execute
`
`any program developed for the inventive system and will communicate with other members
`
`of the system through any communication method the device can find available.
`
`[0029) The operating system provided in each computer device allows the use of a
`
`common instruction set in any such device, regardless of compatibility issues between the
`
`devices, wherein "instruction set" is used herein to mean the commands, tokens, etc., that are
`
`recognized by the operating system as valid instructions. Unlike conventional computer
`
`programs, the operating system employed in the inventive system allows incremental changes
`
`to the program without the need to reload the entire program. Additionally, a programming
`
`change made at a central office will automatically propagate to loosely networked computers
`
`dispersed throughout the field.
`
`[0030) In one aspect of the invention, branching logic depending on the programs
`
`are created for handheld or other computer devices by simply entering questions and
`
`providing response specification, in the form of a questionnaire, for the end-user. Thus, no
`
`particular programming skill is required to generate programs for data gathering. As will be
`
`appreciated by those familiar with data collection, data can be collected by posing a series
`
`10
`
`Unified Patents
`Exhibit 1002
`Page 14 of 2584
`
`

`

`of questions, or otherwise prompting for specific input from the user, as in the manner used
`
`with paper forms. A number of useful subsystems, which may already be present in the
`
`handheld device, or easily added later, may be utilized so that at least some of the
`
`information which is responsive to the designed questionnaire may be collected
`
`automatically rather than entered manually, e.g., time and date, position information if the
`
`device includes a GPS receiver, etc.
`
`[0031] In another aspect of the present invention, the program and user responses
`
`are coded in such a fashion as to substantially reduce the bandwidth requirements of the
`
`network connection. Since many of the networking options for handheld devices provide
`
`limited bandwidth, best use may be made of the available throughput by coding, or
`
`tokenizing, program information and responses.
`
`[0032) In practice, a program is created by entering a series of prompts and
`
`providing direction for how the system is to respond to particular responses. This process
`
`of data gathering may then be performed by a person having no programming skill
`
`whatsoever. The program may then be sent to all, or selected, computer devices on the
`
`network. Those devices having a connection may immediately be updated. Those devices
`
`in which a network connection is temporarily not available will be updated when the
`
`connection is next restored.
`
`[0033) The user of the computer device is then prompted for specific input. As the
`
`user enters data, if the network connection is available, the information is immediately sent
`
`to the server. If the network connection is unavailable, the information is stored locally in
`
`11
`
`Unified Patents
`Exhibit 1002
`Page 15 of 2584
`
`

`

`the handheld device and sent upon restoration of the network connection. At the server, the
`
`information is typically processed upon receipt such that users of the data have real time, or
`
`virtually real time, information available.
`
`(0034] In another aspect of the invention, the inventive system may be provided to
`
`end users according to an application service provider ("ASP") business method. ASPs are
`
`an emerging trend in the computer software industry. Traditionally, a company seeking a
`
`software solution would either acquire a preprogrammed package which suits its needs or
`
`commission the programming of custom software. In many instances preprogrammed
`
`software is unavailable or requires too many compromises to be attractive. In either case,
`
`the software is purchased and, invariably, represents a large capital expense to the company.
`
`Once purchased, modifications, evolutional upgrades, changing management practices, and
`
`the