SMART LIST

Brand Owner (click to sort) Address Description
SMARTLIST HLC Internet Incorporated 19800 MacArthur Blvd., Suite 700 Irvine CA 92715 SMART LIST;assisting customers in creating a database of registered electronic mail users and leasing time on a computer server and providing an interface for the purpose of permitting customers to transmit electronic mail messages via a global computer network to a select segment of the database defined by identifable attributes and consulting services associated therewith;
SMARTLIST Athens Group Suite 500 3301 Northland Drive Austin TX 78731 SMART LIST;Engineering services, namely, engineering for the oil and gas exploration and production industries; Technical support services, namely, troubleshooting of computer software problems; Technical support services, namely, troubleshooting of industrial process control computer software problems; Technological planning and consulting services in the field of oil and gas, exploration and production industries;
 

Where the owner name is not linked, that owner no longer owns the brand

   
Technical Examples
  1. A portable electronic data storage/processing device, e.g., smart card maintains an account including benefit packages. Each benefit package includes multiple items with associated quantity information. A smart card includes an account benefits interface and a retailer interface, each interface using different security measures. New benefit packages are added to the smart card through the account benefit interface by a benefit provider. Benefits debit request lists including multiple items and associated quantities are submitted to the smart card through the retailer interface. The smart card is the trusted member and checks if all requested items in quantities requested can be debited. If all requests can be fulfilled, the smart card executes the debiting from the currently valid benefit package and returns a transaction success indication to the retailer. If any of the requests of the list cannot be met, the entire request list is rejected and no debiting occurs. Benefit quantity addition is not possible through the retailer interface. Transactions are performed as block transactions.