Method and system for the optimal formating, reduction and compression of DEX/UCS data

Abstract

A method and system for communicating data between a network operations center and a remote device is described. Vending machine state information is communicated between a vending site and a network operations center using a delta scheme. A database, maintained by the network operations center, maintains a history of the activity of a variety of vending machines located at a variety of vending sites. To minimize the data needed to be transmitted between the vending site and the network operations center, the network operations center, in one embodiment, will request information from the vending site regarding the change in state of the various vending machines. The vending machines are responsible for restructuring a data block, calculating a delta for the change in state of the machine, applying a compression algorithm to the calculated delta and then transmitting the delta to the network operations center. Upon receipt of the delta, the network operations center can update the database by combining the delta with the previous state information stored in the database.

Description

TECHNICAL FIELD

[0002] The present invention relates generally to data formatting, reduction and compression. More particularly, the present invention relates to a data formatting, reduction and compression method and system for use in wireless and/or wireline communication networks.

BACKGROUND OF THE INVENTION

[0003] Over the past decade, vending machine manufacturers have developed new and innovative vending equipment in response to market needs and vending operator demands. These innovations have been, for the most part, adopted by the beverage vending industry. This trend has been influenced by the accelerating rate of technological innovation in the electronic and electro-mechanical component industry. The availability of new technologies has given vending machine manufacturers the tools to address many of the requirements of vending operators. Advances in electronics are now enabling the use of computer controls and data acquisition systems directly inside the vending machine. Some of the latest vending machines now make it possible for vending machine operators to download sales, inventory, and machine health information on-site onto portable computers or to transmit the vending machine information to a central operations location.

SUMMARY OF THE INVENTION

[0004] In accordance with the teachings of the present invention, a system and method are provided to allow users to extend their corporate enterprise systems into the field using wireless data technologies. The system and method offer information solutions for a wide variety of e-commerce services. One aspect of the present invention is based on an application services platform or network operations center (NOC) upon which users host their wireless-enabled enterprise applications. The NOC manages the complexities of the wireless data realm while providing users with seamless access to their field data and enabling the integration of hand held wireless devices into the system. The present invention may be efficiently used in vertical industries such as cold drink vending, fast food restaurants (fountain drinks), ice merchandising, printing and imaging. Horizontal industries which may benefit from the teachings of the present invention include refrigeration, field service, and end-customer enablement using wireless data.

[0005] The present invention is particularly useful as a wireless data solution for vending machines that makes use of narrowband wireless networks and Internet-based e-commerce application services (using Java, XML, WAP, etc.) to enable vending operators to improve their sales and reduce their operational costs.

[0006] Accordingly, a method for efficiently and cost effectively communicating data between a network operations center and a remote device is provided. The method may involve transmitting a request for data to at least one remote device. Upon receipt of the request for data by the remote device, a current state for the remote device is preferably established. After accessing a previous state for the remote device, a delta value is then preferably calculated between the current state and the previous state for the remote device. The delta data is then written to a device response and the device response is sent to the network operations center for database updating. In a further embodiment, the delta data is compressed before transmission to the network operations center.

[0007] The present invention also provides a method and system for communicating information between a network operations center and a remote device. This method of communication preferably begins by transmitting at least one request for information to the remote device. Upon receipt of the request, records are selected from a data block based upon the request. The selected records are then preferably restructured according to a template prior to transmitting the restructured records to the network operations center. In a further embodiment, the method may also compress a delta value calculated between a current set of restructured records and a previously stored set of restructured records.

[0008] In another embodiment, the present invention provides a method for communicating information between a network operations center and a remote device. In this “call-in” mode, the method preferably includes selecting records from a data block communicatively coupled to the device. The selected records are then preferably restructured according to a template and a delta is calculated between the restructured records and a stored set of records. Once the delta has been calculated, the delta is preferably transmitted to the network operations center.

[0009] In yet another embodiment, the present invention provides a system for acquiring data at a remote device and communicating between a network operations center and the remote device. In this preferred “call-in” system, the remote device is preferably operable to establish communications with the network operations center. The remote device is preferably further operable to select at least one record from a data block communicatively coupled to the device. Upon selection of the record, the remote device is preferably operable to restructure the record according to a template available to the remote device. Once the record has been restructured, the remote device preferably calculates a delta between the delta and a stored set of records. The remote device then preferably transmits the delta to the network operations center via a network.

BRIEF DESCRIPTION OF THE DRAWINGS

[0010] A more complete and thorough understanding of the present embodiments and advantages thereof may be acquired by referring to the following description taken in conjunction with the accompanying drawings, in which like reference numbers indicate like features, and wherein:

[0011] FIG. 1 is a block diagram of a system for communicating between a remote device and a network operations center incorporating teachings of the present invention;

[0012] FIG. 2 is a block diagram of one embodiment of a remote data acquisition system for vending machines according to the present invention;

[0013] FIGS. 3A-3B illustrates a template form for restructuring a DEX file according to one embodiment of the present invention;

[0014] FIGS. 4-8 illustrate various scenarios of data transmission and processing according to one embodiment of the present invention;

[0015] FIGS. 9A-9B is a flow chart illustrating one example of preferred processing performed by a remote device according to one embodiment of the present invention; and

[0016] FIGS. 10A-10B is a flow chart illustrating one example of preferred processing performed by a network operations center according to one embodiment of the present invention.

DETAILED DESCRIPTION OF THE INVENTION

[0017] Preferred embodiments of the invention and its advantages are best understood by referring to FIGS. 1-10 of the drawings, like numerals being used for like and corresponding parts of the various drawings.

Variable Descriptions, Values and Definitions

[0018] The following variable descriptions, values and definitions will be used to describe various features of the present invention.

[0019] Refill-data—Data stored in the Refill-data portion of a getStructuredDexData response. It could be StateRefill, delta (Δ) data between StateRefill and StateRefill-Old or other refill related information associated with the current state of a device.

[0020] Current-data—Data stored in the Current-data portion of a getStructuredDexData response. It could be StateCurrent, or delta (Δ) data between StateCurrent and StateRefill-old or other information related to the current state of a device.

[0021] StateRefill-database—The refill state that is stored in the Network Operations Center (NOC) database. For a new device entry in the database, this value is preferably null (0). In the case where the NOC database has the latest refill state, StateRefill-database=StateRefill. In the case where the NOC database does not have the latest refill state, StateRefill-database=StateRefill-old.

[0022] StateRefill—The most current refill state stored on the remote data acquisition and transmission device (RDATD). If the Controller on the RDATD has only been reset once, StateRefill=StateRefill-old.

[0023] StateRefill-old—The refill state previous to the current refill state, i.e., StateRefill, stored on the RDATD. If the Controller has only been reset once StateRefill=StateRefill-old. StateRefill-Old is also used as a reference state variable for a remote device.

[0024] StateCurrent—The complete current state of a RDATD controller.

[0025] DataLengthCurrent—Length of the Current-data block in a getStructuredDexData response:

[0026] If DataLengthCurrent=0, there is no data for the current state.

[0027] If DataLengthCurrent=FFFF, there is no change in current state since last retrieved.

[0028] If DataLengthCurrent=xxx, the information contained in the Current-data block of the getStructuredDexData response is the actual length of the Current-data block.

[0029] DataLengthRefill—Length of the Refill-data block in a getStructuredDexData response.

[0030] If DataLengthRefill=0, there is no data for the current state.

[0031] If DataLengthRefill=FFFF, there is no change in Refill-data since last retrieved.

[0032] If DataLengthRefill=xxx, the information contained in the Refill-data portion of the getStructuredDexData response is the actual length of the Refill-data block.

[0033] CRCRefill-database—Cyclic Redundancy Check Value (CRC) for the Refill-data that was last received by the NOC and that is stored in the NOC database. For a new device, a value of zero (0) is preferably stored in the database for this field.

[0034] CRCRefill—the CRC for StateRefill, cached on the RDATD.

[0035] CRCRefill-old—the CRC for StateRefill-old, cached on the RDATD.

[0036] ΔRefill=StateRefill−StateRefill-old.

[0037] ΔCurrent=StateCurrent−StateRefill.

[0038] The term “wire-line transmissions” is used to refer to all types of electromagnetic communications over wires, cables, or other types of conduits. Examples of such conduits include, but are not limited to, metal wires and cables made of copper or aluminum, fiber-optic lines, and cables constructed of other metals or composite materials satisfactory for carrying electromagnetic signals. Wire-line transmissions may be conducted in accordance with teachings of the present invention over electrical power lines, electrical power distribution systems, building electrical wiring, conventional telephone lines, ethernet cabling (10baseT, 100baseT, etc.), coaxial cables, etc.

[0039] The term “wireless transmissions” is used to refer to all types of electromagnetic communications which do not require a wire, cable, or other types of conduits. Examples of wireless transmissions for use in local area networks (LAN) include, but are not limited to, radio frequencies, such as the 900 MHz and 2.4 GHz bands, infra-red, and laser. Examples of wireless transmissions for use in wide area networks (WAN) include, but are not limited to, radio frequencies, such as the 800 MHz, 900 MHz, and 1.9 GHz ranges, infra-red, and laser.

[0040] FIG. 1 is a block diagram of a system for communicating between a remote device and a network operations center incorporating teachings of the present invention. System 100 of FIG. 1 preferably includes network operations center 126 communicatively coupled to wide area network (WAN) device 130 and local area network (LAN) device 134 via wide area network 124. Wide area network 124 can be either a wireless or a wire-line network.

[0041] System 100 can preferably utilize at least two different communication schemes for communicating between the network operations center 126 and WAN device 130 and/or LAN device 134. One communication scheme is the DEX/UCS protocol of data transfer as indicated at 138. The second communication scheme is a delta scheme for transmitting data from LAN device 134 and WAN device 130 to NOC 126 and vice versa as indicated at 142. The delta scheme of communication reduces the amount of data necessary to provide complete updated information to NOC 126 and database 230.

[0042] The delta scheme of the present invention utilizes a getStructuredDexData command to achieve this reduction in transmitted information. The getStructuredDexData command preferably selects records specified in a template from an original DEX/UCS data block associated with a remote device, restructures the records in a preferred order, and calculates a delta (Δ) or difference between a previous state and the current state of the remote device. Instead of sending the entire restructured data block, only the delta (Δ) is transmitted to NOC 126. In one embodiment, the delta is compressed, using a conventional compression algorithm such as zip, gzip, etc., before transmitting the delta to the NOC 126. NOC 126 can recreate the current state of the remote device from delta (Δ) and values for a previous state that are stored in a database. The information associated with the various states of the remote device can include inventory levels, number of vends, condition of device hardware, as well as any other characteristic capable of being monitored and contained in the original DEX/UCS data block.

[0043] FIG. 2 is a functional block diagram of one embodiment of a remote data acquisition system for vending machines, indicated generally at 210, according to the present invention. In general, system 210 of FIG. 2 communicates information from a vending site 212 externally over a wide area wireless or wire-line network and internally over a local area wireless or wire-line network. As shown, the local area network at vending site 212 can be referred to as a device interrogation LAN subsystem (DIL). Vending site 212 may include only one vending machine 214 or a plurality of vending machines 214. Each vending machine 214 may include vending hardware (not expressly illustrated) and inventory 216 for performing vending functions and electronically tracking some vending information. Vending machines 214 may provide various types of products to customers such as soft drinks, snacks, etc.

[0044] According to the present invention, each vending machine 214 may include an application controller 218 coupled to and interfacing with vending hardware and inventory 216. Many vending machines 214 are equipped with electronics for controlling vending operations as well as tracking some vending events such as money received, change given and number of vends from each slot. Application controllers 218 can communicate with such embedded electronics as well as be equipped to directly sense other vending events and vending equipment parameters (e.g. compressor performance). Application controllers 218 can also communicate with one another and the application host 222 via onboard transceivers using wire-line or wireless transmissions. According to the present invention, either the application controller 218 or the application host 222 can be configured to process the getStructuredDexData request or command, to restructure a DEX/UCS data block or to calculate delta (Δ) values.

[0045] Together, application controllers 218 and application host 222 form a LAN supported by the wireline and/or wireless transmissions 220. In addition, application controllers 218 can also act as repeaters in case application host 222 cannot directly communicate with a particular application controller 218 while another application controller 218, which does have an established communication link with application host 222, can directly communicate.

[0046] Application host 222 acquires data captured by application controllers 218 and, preferably using the delta scheme of the present invention, can package and communicate that data across an external network 124 using a wide area network (WAN) interface. Application host 222 can be installed together with application controller 218 inside a vending machine or housed separately in another location. In the event that the application host 222 is placed inside a vending machine together with an application controller 218, it is possible to share some of the electronic components between them, the LAN transceiver for example, in order to reduce the cost of the hardware. In this case, the application host 222 and application controller 218 inside the same vending machine, would preferably communicate with each other over a hardwired interface between the two components. Alternatively, the application host 222 and application controller 218 can be designed to be a single integrated component within a vending machine. Furthermore, an application host 222 can be used whose function preferably consists of monitoring the application controllers 218. For example, such an application host 222 could take the form of a hand-held portable computer 223 to be carried by service or delivery personnel in order to query the application controllers 218 without having to interact via the WAN interface 229. In one embodiment, application host 222 and/or application controller 218 may be used to perform the preferred functions associated with the automated or “Call-In” mode of operation mentioned above.

[0047] The WAN interface 229 can be implemented in a number of ways. In particular, WAN interface 229 is designed to support a wide area network 124 that can be implemented via wire-line or wireless transmissions. If a wireless narrowband PCS paging network is used to implement the WAN, messages from application host 222 can be communicated as digital messages through the paging network, stored and delivered by the network carrier to the NOC using, for example, a secure Internet connection.

[0048] As shown in FIG. 2, a network operations center (NOC) 126 communicates with one or more vending sites 212 across wide area network 124 using the delta scheme of the present invention. As mentioned, in one implementation, network operations center 126 can access information transmitted by application hosts 222 at vending sites 212 using the network carrier's infrastructure. In the embodiment of FIG. 2, network operations center 126 includes a NOC control 228 that communicates with wide area network 124 through a WAN interface 229. NOC control 228 can receive data acquired from and transmit data to vending sites 212, process the data and store the data into database 230. NOC control 228 can also perform instant alert paging, direct dial alarms and other functions to provide real time notification to a vending operator upon the occurrence of certain events (e.g., out-of-stock, power outage, vandalism, etc.). NOC control 228 can also provide third party transaction processing such as allowing queries on database 230. The WAN interface 229 between NOC control 228 and the wide area network 124 can be implemented through the use of either wire-line or wireless transmissions.

[0049] At network operations center 126, a client access point 232 provides access from a client interface subsystem (CI) 234 across external network 224. In one implementation, client access point 232 can be a web-based interface allowing user access from a client computer across a network such as the Internet. Other implementations include providing a direct-dial connection between client interface subsystem 234 and client access point 232. Once connected, a user can use client interface subsystem 234 to obtain information from database 230 based upon data acquired from vending sites 212. Further, users can be provided with extended services such as trend information developed by mining and analyzing database 230.

[0050] According to the present invention, system 210 of FIG. 2 combines a number of technologies to provide technical advantages in the area of vending machine management, to reduce various operational costs and to overcome existing network traffic problems with conventional remote data acquisition systems for vending machines. As mentioned above, some conventional remote data acquisition systems employ a point-to-point wireless communication link to retrieve information from and send information to a plurality of remote devices. Further, wide-area networks (WAN) are often formed from a plurality of local area networks (LANs), and such LANs are often interconnected using a wire-line or wireless data transmission system. In other technical areas, wire-line and wireless transceivers have been used for local area network communication.

[0051] Delta scheme 142 of the present invention enables network data volume and communication time between NOC 126 and remote devices 130 and 134 to be minimized. Delta scheme 142 functions to minimize the amount of information necessary to be communicated between NOC 126 and devices 130 and 134 such that the complete state information of each device is maintained at NOC 126.

[0052] FIGS. 3A-3B illustrate one embodiment of the fields of a DEX/UCS block which has been restructured in response to a getStructuredDexData request. As illustrated in FIGS. 3A-3B, the DEX/UCS data block is preferably sectioned off into four categories. Category 305 preferably includes special fields, category 310 preferably includes fields that do not change frequently while category 315 preferably contains the fields that are likely to change frequently. Category 320 preferably includes the non-standard fields of a DEX/UCS data block. Restructuring the DEX/UCS data block allows for very high compression ratios to be achieved after the delta is calculated. These compression ratios may not be achievable without the restructuring of the DEX/UCS data block.

[0053] Software (not expressly shown) incorporating teachings of the present invention running on a device end, such as software running on application controller 218 or application host 222, will restructure the DEX/UCS data block according to a template framework, such as that illustrated in FIGS. 3A-3B, and by following a preferred set of rules. The preferred set of rules includes: to calculate Δ10, state0 is subtracted from state1; if the DEX/UCS data block obtained from the RDATD controller does not contain a particular record type expected in the template, a character, such as a carriage return character (<CR>), is written to the restructured data block; if the data block from the RDATD controller contains a particular record type that is not expected in the template, it is ignored; for each record, only the fields of interest are considered (For example, for the record “PA2*9888*543660*9882*543510” we may only need to send information “9888” and “543660,” making our desired record “PA2*9888*543660.”); for records that match, a <CR> is written to the restructured block; for records that don't match, the record identifier is skipped and a delta is calculated only for the remaining portion, (For example, for the two records “MA5*SEL1*1,7*9821,10086” and “MA5*SEL1*1,7*5696*5845,” the delta is calculated for “1,7*9821*10086” and “1,7*5696*5845” portions only.); the delta is calculated on a per field basis, i.e., the fields separated by “*'s”; if a required field is absent in the DEX data block received from the RDATD controller, the restructured data block will have two contiguous “*'s” for that field; if all the bytes in the delta for a field are binary 0's (zeroes), the delta is considered to be empty and there is no delta data for that field to be written, (In this situation, there will be only two “*'s” in the record with no field value in between.); each such delta, except for the last record in line, is written to the restructured block followed by a “*”; the last record written to the restructured data block is followed by a <CR>; for fields that are not of equal length, e.g., “5845” and “10086,” the shorter field is padded at the end with the appropriate number of 0's (zeroes) to make it equal in length to the longer field, (A delta is preferably calculated on two equal length fields.); since blank characters are allowed in the DEX/UCS data block, binary zeroes (0's) will be used for padding a shorter field to make it equal in length to the longer field, (This helps in reconstructing state1 from state0 and delta.); instead of “1 * 55”, it is desirable to minimize the size of the restructured data block and use “1*55” instead; by using 0 (zero) when adding the state0 byte and the delta byte equals 0 (zero) we discard that byte since it was used for padding; and non-standard records are written to the very end of the restructured data block without calculating a delta.

[0054] FIGS. 4-8 illustrate one example of preferred steps processed by NOC 126 and device 400, such as a remote vending unit 214, during various getStructuredDexData requests. In FIGS. 4-8, the DEX data block is restructured at the remote device upon receipt of the getStructuredDexData request. Restructuring the DEX/UCS data block can also occur at other times during the processing of the getStructuredDexData request. In addition to calculating a delta in response to receipt of a getStructuredDexData request, a remote device may be configured to operate in an automated mode. This automated or “Call-In” mode is preferably configured such that a delta is calculated, generally as defined below, in response to a predetermined event, such as at a certain time, a threshold number of transactions, etc., and then transmitted to NOC 126.

[0055] FIG. 4 illustrates the processing and transmissions which occur when NOC 126 transmits a getStructuredDexData request for StateCurrent or the complete current state of device 400. As illustrated in FIG. 4, NOC 126 transmits a getStructuredDexData request to get an update of the StateCurrent of device 400. Included in the getStructuredDexData request for a StateCurrent update, is the check value CRCRefill-Database as indicated at 405. In response to receipt of the getStructuredDexData request for a StateCurrent update, device 400 preferably writes CRCCurrent and StateCurrent to a device response and then transmits the device response to NOC 126 as indicated at 410. In one embodiment, the information written to the device response is compressed prior to being written. Upon receipt of the device response containing CRCCurrent and StateCurrent, NOC 126 preferably recreates a current state from values stored in database 230 and the values of CRCCurrent and StateCurrent provided in the device response.

[0056] FIGS. 5A-5C illustrate the processing which can occur in response to a getStructuredDexData request for the ΔCurrent of device 400. FIG. 5A illustrates one embodiment of the preferred steps that occur when updating database 230 with the changes which have occurred at device 400 since database 230 was last updated. As indicated at 505, to update database 230 with the current changes that have occurred at remote device 400, NOC 126 sends a getStructuredDexData request for ΔCurrent to device 400. Included in the getStructuredDexData request for ΔCurrent is error checking value CRCRefill-Database. Upon receipt of the ΔCurrent request and the CRCRefill-Database value, device 400 performs the steps indicated at 510. Device 400 begins by comparing the value of CRCRefill-Database provided by NOC 126 to a value of CRCRefill accessible by device 400. A comparison of the values of CRCRefill-Database and CRCRefill is performed to verify that NOC 126 and database 230 have the most current value for StateRefill of device 400. If the values of CRCRefill-Database and CRCRefill are found to be equivalent, device 400 can then calculate ΔCurrent by subtracting StateRefill from StateCurrent using a previously restructured data block or by restructuring a data block before calculating ΔCurrent. Device 400 will also preferably calculate a CRCCurrent value by applying a CRC function to StateCurrent. Once device 400 has completed all of the processing steps necessary to provide NOC 126 with the information requested, CRCCurrent and ΔCurrent are written to a device response and transmitted to NOC 126 for processing as indicated at 515. The current state of device 400, the CRC calculated as well as other variables are stored by device 400 as previous state information for use with the next getStructuredDexData request once the device response has been transmitted.

[0057] Upon receipt of CRCCurrent and ΔCurrent by NOC 126, database 230 is updated to reflect the current state of device 400. As indicated at 520, to update database 230, ΔCurrent is added to the value of StateRefill-Database stored in database 230 to recreate StateCurrent or the current state of device 400. Once StateCurrent has been stored, database 230 will then contain the current state of device 400. This updated information can be used to issue service calls, page a distributor to replenish inventory, or perform a myriad of other functions.

[0058] FIG. 5B illustrates the processing which preferably occurs when CRCRefill-Database is compared to the value of CRCRefill, during the processing of a getStructuredDexData request for ΔCurrent by device 400, and the two are not equal. As indicated at 525, an attempt by device 400 to interpret the value of CRCRefill-Database provided is made by comparing the value of CRCRefill-Database against the value of CRCRefill-Old that is available to device 400. If the value of CRCRefill-Database matches the value of CRCRefill-Old, this indicates that the value of CRCRefill-Database provided by NOC 126 represents an older StateRefill at NOC 126 than the latest StateRefill transmitted by device 400. In such a situation, device 400 preferably provides ΔCurrent and ΔRefill to NOC 126 in order to update their corresponding values in database 230. As indicated at 525, ΔRefill is calculated by subtracting StateRefill-Old from StateRefill. ΔCurrent is calculated as described above.

[0059] Once ΔCurrent and ΔRefill have been calculated, a device response is written, preferably using compressed data, and the update information is then transmitted to NOC 126. As indicated at 530, the information preferred to properly update database 230 includes ΔCurrent, ΔRefill, CRCRefill, CRCRefill-Old and CRCCurrent. Upon receipt of ΔCurrent, ΔRefill, CRCRefill, CRCRefill-Old and CRCCurrent by NOC 126, database 230 is updated. As indicated at 535, the current refill state or StateRefill of device 400 is calculated by adding ΔRefill to StateRefill-Database at NOC 126. The StateRefill value is then stored as an updated StateRefill-Database value. The current state or StateCurrent of device 400 is recreated by adding ΔCurrent to StateRefill. The new StateCurrent value is then stored in database 230. Each CRC check value is also preferably stored in database 230 to update the check values each represents.

[0060] If device 400 determines that the value of CRCRefill-Database does not equal the value of CRCRefill or CRCRefill-Old, device 400 preferably transmits the complete StateRefill and ΔCurrent based on the current state of device 400. As illustrated at 540 of FIG. 5C, ΔCurrent is calculated by subtracting StateRefill from StateCurrent. Once ΔCurrent has been calculated, device 400 transmits ΔCurrent, StateRefill, CRCCurrent and CRCRefill in a device response to NOC 126, as indicated at 545. Upon receipt, NOC 126 recreates and updates the appropriate variables stored in database 230.

[0061] To obtain the refill state or StateRefill from device 400, NOC 126 may transmit a getStructuredDexData indicating such a request. As illustrated at 605 of FIG. 6, a request for a StateRefill update includes the transmission of CRCRefill-Database. Similar to the request for the StateCurrent update of FIG. 4, device 400 preferably does not compare the value of CRCRefill-Database to any local CRC values. As indicated at 610, device 400 transmits CRCRefill and StateRefill to NOC 126 in response to the request for a StateRefill update. Upon receipt of the device response containing the StateRefill update, NOC 126 recreates the current state of device 400 based upon values stored in database 230 and the values of CRCRefill and StateRefill. Database 230 is then updated accordingly.

[0062] Illustrated in FIGS. 7A-7C is the processing and transmissions which occur when NOC 126 transmits a getStructuredDexData request for ΔRefill to device 400. As indicated at 705, transmitting a getStructuredDexData request for ΔRefill preferably includes transmitting CRCRefill-Database to device 400 from NOC 126. Upon receipt of the getStructuredDexData request for ΔRefill, device 400 uses the CRCRefill-Database value supplied to verify that NOC 126 has the most current refill state or StateRefill for device 400. If the value of CRCRefill-Database matches the value of CRCRefill when compared, as illustrated at 710, device 400 can then transmit the information requested by NOC 126 in a device response. If the StateRefill of device 400 has not changed since the last time device 400 updated database 230, device 400 transmits a DataLengthRefill value equal to “FFFF,” as indicated at 715, to NOC 126 to indicate that no change has occurred.

[0063] If device 400 compares the value of CRCRefill-Database to the value of CRCRefill and determines the values to not be equal, as indicated at 720 of FIG. 7B, device 400 will then compare the value of CRCRefill-Database to the value of CRCRefill-Old. If the value of CRCRefill-Old matches the value of CRCRefill-Database, indicating that the StateRefill of device 400 has indeed changed since database 230 was last updated, ΔRefill is calculated by subtracting StateRefill-Old from StateRefill. ΔRefill is then written to a device response and transmitted to NOC 126. In addition to ΔRefill, CRCRefill and CRCRefill-Old are also transmitted to NOC 126 in the device response as indicated at 725.

[0064] Should device 400 determine that the value of CRCRefill-Database transmitted by NOC 126 does not equal the value of CRCRefill or the value of CRCRefill-Old, as indicated at 730 of FIG. 7C, device 400 will then transmit StateRefill to NOC 126. In addition to StateRefill, device 400 transmits CRCRefill and CRCRefill-Old to NOC 126 as indicated at 735 such that database 230 can be updated accordingly.

[0065] FIG. 8 illustrates one method of adding a new device to database 230. As illustrated at 805 of FIG. 8, device 400 transmits unsolicited state information to NOC 126, i.e. in an automated or “Call-In” operating environment. Information included in an unsolicited transmission from a newly added device 400 might include CRCRefill, CRCCurrent, and ΔCurrent. The ΔCurrent transmitted by device 400 is calculated by subtracting StateRefill from StateCurrent.

[0066] Upon receipt of the unsolicited transmission indicated at 805, NOC 126 begins processing by comparing the value of CRCRefill provided by newly added device 400 with the value of CRCRefill-Database in database 230 for device 400. Since, in this scenario, device 400 is new to the system, the value of CRCRefill-Database will be empty or zero (0). After determining that device 400 has recently been added to the system, NOC 126 transmits a getStructuredDexData request to device 400 as indicated at 810. In the getStructuredDexData request sent at 810, NOC 126 requests both StateRefill and ΔCurrent from device 400.

[0067] Device 400 responds to the receipt of the getStructuredDexData request from NOC 126 by transmitting the information requested. As indicated at 815, information included in a getStructuredDexData request for StateRefill and ΔCurrent preferably includes CRCRefill, CRCCurrent, StateRefill and ΔCurrent.

[0068] Once NOC 126 receives the information requested, database 230 can then be updated as indicated at 820. Database 230 updates the value of CRCRefill-Database by setting its value equal to the value of CRCRefill received. StateRefill is also stored in database 230. The value of StateCurrent in database 230 is created by summing ΔCurrent and StateRefill.

[0069] An alternative to the method of FIG. 8 for adding a new device to the system involves scheduling NOC 126 to transmit a getStructuredDexData request for StateRefill and ΔCurrent immediately after a new device is brought online. This proactive approach would eliminate the transmission which occurs at 805 of FIG. 8 leaving only the processes and transmissions indicated at 810, 815 and 820.

[0070] FIGS. 9A-9B illustrates a flow chart indicating the preferred processing performed by device 400 upon receipt from NOC 126 or upon the automated execution of a getStructuredDexData request. Each of the scenarios encountered by device 400 in FIGS. 4-8 are generally processed according to method 900 of FIGS. 9A-9B.

[0071] Persons having ordinary skills in the art can appreciate the changes to FIGS. 4-9 which occur in a “Call-In” mode of generation. Upon receipt of the getStructuredDexData request from NOC 126, any information, such as return Node ID, CRCRefill-Database, and flag information, included in the getStructuredDexData request is extracted, as indicated at step 905. Once the information has been extracted, the flag information is evaluated to determine if the getStructuredDexData request includes a request for the Refill-data information of device 400. If it is determined, at step 910, that the getStructuredDexData request includes a request for the Refill-data of device 400, method 900 proceeds to step 915 to determine if the Refill-data request is a request for the StateRefill or a request for the ΔRefill of device 400. Alternatively, if at step 910 it is determined that the getStructuredDexData request received from NOC 126 does not include a request for the Refill-data of device 400, method 900 proceeds to step 917 where a DataLengthRefill value equal to zero (0) is written to the device response. In a preferred embodiment of the present invention, data is compressed before being written to a device response.

[0072] At step 915, if it is determined that the getStructuredDexData request includes a request for ΔRefill, method 900 proceeds to step 920 for a comparison of the CRCRefill value of device 400 with the value of CRCRefill-Database provided by NOC 126. If the value of CRCRefill is equal to the value of CRCRefill-Database, method 900 proceeds to step 925 where a DataLengthRefill value equal to “FFFF” is written in the device response. A DataLengthRefill value equal to “FFFF” indicates to NOC 126 that there has been no change in the Refill-data since the last update requested from and transmitted by device 400. Once the device response has been written, method 900 proceeds to step 930.

[0073] Alternatively, if at step 920 the value of CRCRefill is determined to be different than the value of CRCRefill-Database, method 900 proceeds to step 935. At step 935, the value of CRCRefill-Database is compared to the value of CRCRefill-Old. If the value of CRCRefill-Old equals the value of CRCRefill-Database, method 900 proceeds to step 940. At step 940, ΔRefill is calculated by subtracting StateRefill-Old from StateRefill. ΔRefill is then written into a device response. Additionally, CRCRefill is written in the device response to enable the value of CRCRefill-Database in database 230 to be updated. Upon completion of step 940, method 900 proceeds to step 930.

[0074] Should the value of CRCRefill-Old differ from the value of CRCRefill-Database, method 900 proceeds from step 935 to step 945. If the value of CRCRefill-Old should differ from the value of CRCRefill-Database, database 230 at NOC 126 will require a StateRefill update. At step 945, a StateRefill and a CRCRefill value are written to a device response. Upon receipt of the device response at NOC 126, database 230 can then be updated with the values of CRCRefill and StateRefill provided. Upon completion of step 945, method 900 proceeds to step 930.

[0075] At step 930, the flags received in the getStructuredDexData request sent by NOC 126 are evaluated to determine if NOC 126 is requesting Current-data information from device 400. If, at step 930, it is determined that the getStructuredDexData request does not include a request for Current-data, method 900 proceeds to step 950 where a value of zero (0) is written in the device response for Current-data. Once step 950 has been completed, method 900 proceeds to step 955 where the response written by method 900 is transmitted to NOC 126.

[0076] Should it be determined at step 930 determine that the getStructuredDexData request includes a request for Current-data from device 400, method 900 proceeds to step 960. At step 960, it is determined whether the getStructuredDexData request includes a request for a ΔCurrent update or a request for a StateCurrent update. If a StateCurrent update is requested, method 900 proceeds to step 965 where StateCurrent and CRCCurrent for device 400 are written a device response. Once StateCurrent and CRCCurrent have been written to the device response at step 965, method 900 proceeds to step 955 where the device response is transmitted to NOC 126.

[0077] If a request for ΔCurrent is included in the getStructuredDexData requested sent by NOC 126 as determined at step 960, method 900 proceeds to step 970. CRCRefill is compared to the value of CRCRefill-Database at step 970. If the value of CRCRefill is determined to equal the value of CRCRefill-Database at step 970, method 900 proceeds to step 975. At step 975, ΔCurrent is calculated by subtracting StateRefill from StateCurrent and written to a device response as is a CRCCurrent value. Once ΔCurrent and CRCCurrent have been written to the device response, method 900 proceeds to step 955 where the device response is transmitted to NOC 126.

[0078] Should it be determined at step 970 that the value of CRCRefill does not equal the value of CRCRefill-Database, method 900 proceeds to step 980 where the value of CRCRefill-Old is compared against the value of CRCRefill-Database. If the value of CRCRefill-Old is determined to not equal the value of CRCRefill-Database at step 980, StateRefill and CRCRefill are written to a device response at step 985. If the value of CRCRefill-Old is determined to equal the value of CRCRefill-Database at step 980, ΔRefill is calculated by subtracting StateRefill-Old from StateRefill. ΔRefill is then written to the device response along with CRCRefill at step 990. Upon completion of either step 985 or 990, method 900 proceeds to step 975 for the processing described above and then on to step 955 where the device response is transmitted to NOC 126. Based upon the above descrition, a person having ordinary skill in the art can appreciate the changes to FIGS. 4-9 which occur when device 400 is operated in a “Call-In” mode.

[0079] FIGS. 10A-10B illustrates a flow chart indicating the preferred processing performed by NOC 126 upon receipt of the device response created by device 400 in response to a getStructuredDexData request. Each of the scenarios encountered by NOC 126 in FIGS. 4-8 are preferably performed according to method 1000 of FIGS. 10A-10B. Upon receipt of the device response created by method 900, method 1000 preferably begins by extracting, such as uncompressing compressed data, the value of DataLengthRefill as indicated at step 1005. Once the value of DataLengthRefill has been obtained, method 1000 proceeds to step 1010 where DataLengthRefill is compared against a null (0) character. If it is determined at step 1010 that the value of DataLengthRefill is equal to the null (0) character, method 1000 proceeds to step 1015 where the value of CRCRefill, provided in the device response created by method 900, is stored in database 230 as the value of CRCRefill-Database. As a result, method 1000 is complete and the appropriate values of database 230 have been updated as indicated at 1020.

[0080] At step 1010, if it is determined that the value of DataLengthRefill is something other than the null (0) character, method 1000 proceeds to step 1025. At step 1025, the value of DataLengthRefill is compared to the value “FFFF”. If the Refill-data of device 400 has not changed since the last device response transmitted by device 400, the value of DataLengthRefill is equal to “FFFF” and method 1000 will then proceed to step 1020.

[0081] If, at step 1025, it is determined that the value of DataLengthRefill does not equal “FFFF”, method 1000 proceeds to step 1035. At step 1035, the values of StateRefill, Date/TimeRefill, FlagRefill, CRCRefill, CRCRefill-Old and Refill-data are obtained. Once the desired values have been obtained, FlagRefill is tested at step 1040 to determine whether the Refill-data included in the device response is a StateRefill update or ΔRefill information. If FlagRefill indicates the information included in the device response is for a StateRefill update, method 1000 proceeds to step 1045 where the Refill-data information and the value of CRCRefill are stored in database 230. Once the storage is complete, method 1000 proceeds to step 1020 to repeat the method of FIGS. 10A-10B using Current-data vales and variables in place of Refill-data values and variables.

[0082] Alternatively, if it is determined at step 1035 that the value of FlagRefill indicates that ΔRefill information is included in the device response received by NOC 126, method 1000 proceeds to step 1050. At step 1050, the value of CRCRefill-Old is compared to the value of CRCRefill-Database. If the value of CRCRefill-Old does not equal the value of CRCRefill-Database, method 1000 proceeds to step 1055 where a getStructuredDexData request for a StateRefill update and ΔCurrent is preferably generated and subsequently transmitted to device 400 before NOC 126 ends current processing at 1060.

[0083] If it is determined that the value of CRCRefill-Old equals the value of CRCRefill-Database at step 1050, method 1000 proceeds to step 1065 where StateRefill is calculated by summing Refill-Data and StateRefill-Database. Also at step 1065, CRCRefill-Calc is calculated by applying an appropriate CRC function to the value of StateRefill. Once a value of CRCRefill-Calc has been calculated, it is compared to the value of CRCRefill at step 1070. The value of CRCRefill-Calc is compared to the value of CRCRefill to determine if the information included in the device response received can be used to update the information maintained by database 230. If the value of CRCRefill-Calc does not equal the value of CRCRefill, method 1000 proceeds to step 1055 for the processing described above and ends at 1060. If the value of CRCRefill-Calc equals the value of CRCRefill, method 1000 proceeds first to step 1045 database 230 is updated and then on to 1020. Based on the above description, a person having ordinary skills in the art can appreciate the changes to FIGS. 4-10 when device 400 is operating in a “Call-In” mode.

[0084] Although the present invention has been described with respect to a specific preferred embodiment thereof, various changes and modifications may be suggested to one skilled in the art and it is intended that the present invention encompass such changes and modifications fall within the scope of the appended claims.

Claims

1. A method for communicating information between a network operations center and a remote device comprising: transmitting at least one request for information from the network operations center to the remote device; receiving the at least one request by the remote device; selecting records from a data block at the remote device based upon the at least one request; restructuring the selected records according to a template; and transmitting the restructured records to the network operations center.

2. The method of claim 1 further comprising calculating a delta between the restructured records and a stored set of restructured records.

3. The method of claim 1 further comprising storing the restructured records by the remote device.

4. The method of claim 1 further comprising evaluating at least one characteristic of the request for information to determine the type of information being requested.

5. The method of claim 1 further comprising writing the restructured records to a device response.

6. The method of claim 1 further comprising: receiving the restructured records by the network operations center; and updating at least one value stored in a database using the restructured records.

7. The method of claim 6 further comprising combining the restructured records received by the network operations center with at least one value stored in the database.

8. The method of claim 1 further comprising: transmitting at least one check value; and comparing at least one check value with at least one stored value.

9. The method of claim 1 further comprising selecting the records from a DEX/UCS data block.

10. The method of claim 1 wherein transmitting is supported by a wireless network.

11. The method of claim 1 wherein transmitting is supported by a wire-line network.

12. A method for communicating data between a network operations center and a remote device comprising: transmitting a request for data to at least one remote device; receiving the at least one request for data by the at least one remote device; establishing a current state for the at least one remote device; accessing a previous state for the at least one remote device; calculating a delta between the current state and the previous state for the at least one remote device; writing the delta to a device response; and transmitting the device response to the network operations center.

13. The method of claim 12 further comprising recreating the current state of the remote device at the network operations center.

14. The method of claim 12 further comprising updating a database at the network operations center based upon the delta and a stored value in the database.

15. The method of claim 12 further comprising: storing the current state of the remote device as the previous state of the remote device; and storing the previous state of the remote device as a reference state for the remote device.

16. The method of claim 12 further comprising selecting records from a data block at the remote device indicative of the current state of the remote device.

17. The method of claim 16 further comprising restructuring the selected records based upon a template to establish the current state of the remote device.

18. The method of claim 12 further comprising applying a data compression algorithm to the calculated delta.

19. The method of claim 12 further comprising: transmitting at least one check value; and comparing the at least one check value with at least one stored value.

20. A system for acquiring data at a remote device and communicating information between a network operations center and the remote device comprising: the remote device operable to receive a request for information from the network operations center; a data block having at least one set of records stored at the remote device; a template accessible by the remote device for restructuring a record selected from the data block; the remote device operable to select a record from the data block based on the request for information; a network for communicating information between the network operations center and the remote device; and the remote device operable to restructure the selected records according to the template and to transmit the restructured record to the network operations center using the network.

21. A method for communicating information between a network operations center and a remote device comprising: selecting records from a data block communicatively coupled to device; restructuring the selected records according to a template; calculating a delta between the restructured records and a stored set of records; and transmitting the delta to the network operations center.

22. The method of claim 21 further comprising applying a data compression algorithm to the delta.

23. The method of claim 21 further comprising sorting the delta by the remote device.

24. The method of claim 21 further comprising writing the delta to a device response.

25. The method of claim 21 further comprising combining the delta with at least one value stored in a database communicatively coupled to the network operations center.

26. The method of claim 21 further comprising: transmitting at least one check value; and comparing the at least one check value with at least one stored value.

27. The method of claim 21 further comprising selecting the records from a DEX/UCS data block.

28. A system for acquiring data at a remote device and communicating between a network operations center and the remote device comprising: the remote device operable to establish communications with the network operations center; a data block having at least one set of records communicatively coupled to the remote device; a template at the remote device for restructuring a record selected from the data block; the remote device operable to select a record from the data block; a network for communicating between the network operations center and the remote device; and the remote device operable to restructure the selected records according to the template, to calculate a delta based upon the restructured records and a stored set of records and to transmit the delta to the network operations center using the network.

29. The system of claim 28 further comprising: a data compression algorithm operably coupled to the remote device; and the data compression algorithm operable to reduce delta in size.

30. The system of claim 28 further comprising the remote device operable to calculate delta in response to a predetermined event.