Pitney Bowes Inc.

Edward M Rauh

Jacques E Hasbani

Terri A Carroll

Kenneth Karbowski

Glen A Boucher

Glenn Boucher

Stephen C Nunnally

Angela M Njo

Brian D Flesser

Christopher S Kallas

John R Mattioli, Jr

A system and method of retrieving shipment data uses destination information, as well as the carrier and level of service data models to retrieve the appropriate shipment data which complies with the selected parameters. The delivery commitment systems returns information concerning the number of days, the delivery, the latest time of delivery, whether the delivery is guaranteed based upon selected parameters concerning the origin and destination of the package. Carrier specific data can be stored in a common, carrier-independent form including an origin map, (optional) one or more destination maps, a service token map, a zone token map, and a delivery commitment matrix. Origins and destinations can be defined by five-digit ZIP codes and the service can be identified by a TokenID. Each origin can be mapped to a destination within the destination map, where each destination in the destination map is resolved to a service level index. The desired class of service, as identified by a carrier's TokenID, is resolved in a look-up table to a service column index. The service level index and the service column index are then used as indices into a delivery commitment matrix so as to provide delivery commitment data. Zone mapping is also supported to obtain such delivery commitment data.

Method and system for resolution of carrier specific data utilizing a generic data model

The invention is a method and system of updating a set of data objects within a Data Access System (DAS). The method begins by initiating a communication link between a client and a host data processing system. Once a communications link is established, a set of object tables is uploaded from the client data processing system to the host. The object tables are read at the host; and, a determination is made as to which data objects in the set of object tables are to be updated. It is also determined which data objects in the set of object tables is to be simply maintained. A new set of object tables is then constructed at the host data processing system and transmitted to the client data processing system. Upon receipt of the new file tables, the client system performs the task of verifying accurate receipt of the new set of object tables prior to restarting the client data processing system. The verification step includes saving at the host, a first data map of the new set of object tables as a record of which objects were transmitted. The new set of object tables is then received and saved within a memory of the client data processing system before retransmitting the new set of object tables as a second data map back to the host from the client. The second data map is then compared with the first data map to form a comparison, and if the first data map and the second data map do not match, then the verification is nulled.

Method and system for changing rating data via internet or modem in a carrier management system

The present invention is directed to a platform independent rate data structure for representing a rate chart for a carrier manager system and a method of calculating a rate using the platform independent rate data structure and carrier rate calculation software of the carrier manager system. The rate data structure represents the rate chart, and comprises a header and a data area. The header contains information which describes the content of the rate data structure. The data area may comprise a collection of expressions and a collection of subtables. The expressions are mathematical formulas representing rates. The subtables are formats representing rate chart data. A rate chart may be represented by a combination of subtables and/or expressions in a rate data structure. The amount of space required to represent the rate chart is reduced by the rate data structure representation of the present invention. The rate data structure representation is also platform independent.

Platform independent rate data and method of calculating a rate for a carrier manager using platform independent rate data

A management librarian for shipping carriers is configured to access a registry containing carrier identifiers corresponding to the carriers and module identifier corresponding to carrier rate modules. The carrier rate modules contain item rating instructions arranged to rate the item for a respective carrier from among the carriers. The carrier management librarian is also configured to load into the executable space of a client application a selected carrier rate module corresponding to the selected carrier based on module identifiers accessed in the registry. An entry point for the item rating instructions is identified, based on an associated module identifier corresponding to the selected carrier.

Method and system of implementing a carrier manager librarian

A carrier rate module contains item rating instructions for rating an item for a carrier and self-registration instructions for storing registration information in a registry about the carrier rate module. The self-registration instructions are stored at an entry point with a predefined name so that a standard registration program can invoke the self-registration instructions through the entry point. The registration information stored in the registry includes a carrier identifier for the carrier in a one-to-one association with a module identifier. The module identifier indicates how to load the carrier rate module, so that a carrier manager librarian can identify an entry point of the item rating instructions based on the registration information stored in the registry.

Method and system of implementing a carrier manager registry

The invention is a method and system of loading a data object representative of carrier data and possible command structures, which can be identified by both name and date fields characteristics, into a Data Access System of a carrier management system. The method begins with receiving a request for an object and then determining whether or not the object resides in a first data table which is indicative of a plurality of characteristics of the object. If the object is not resident in the first data table, then the system assigns an initial time stamp and a permanence value to the object. Additionally, the method and system must determine the memory space, in the Data Access System, required for storing the object. De-referenced objects are removed from the memory until space is available that is greater than or equal to the memory requirement of the object. After memory is allocated to the object, the object is then loaded into the memory for use within the carrier management system. A directory table is then established for the object. The directory table includes: an object name; a set of associated data; and, an object table data pointer. The associated data includes an effective date; an expiration date; and, the modification status of the file.

Growing community of inventors

West Haven, CT, United States of America

Edward M Rauh