Search

The TeleWeb system was developed to allow World Wide Web browsing from loosely connected mobile hosts. A 'reactive architecture' that supports user-specified adaptation under various operating conditions was developed in line with a belief in the importance of fine-grained cost control. The TeleWeb architecture's four key features collectively provide an asynchronous, e-mail-style of browsing in which users can trade off communication cost against information needs or work disconnected from a cache of documents.

The article describes the Lucent Personalized Web Assistant (LPWA), a software system designed to address Internet users' concerns. Users may browse the Web in a personalized, simple, private and secure fashion using LPWA-generated aliases and other LPWA features. LPWA generates secure, consistent, and pseudonymous aliases for Web users. Each alias consists of an alias username, an alias password and an alias email address. The alias email addresses allow Web sites to send messages to users and enable effective spam filtering. LPWA forwards mail addressed to the alias email address to the actual user. LPWA allows users to filter incoming messages based on the recipient address, which is an effective method for detecting and blocking spam. In this way, the LPWA site does not attract break-ins, and the LPWA service may be replicated easily. The absence of state information also implies there are no records to which an outside agency can demand access. INSET: Usage of LPWA..

Internet protocol (IP) networks were originally designed by universities and government research agencies, not by network operators with commercial objectives. As a result, while aggregate accounting is possible for network management, detailed accounting at the level of individual users is often not possible. In today's networks, this limitation hinders the effective introduction of a variety of new IP‐based services. Network operators lack the tools to monitor individual customers' use of network services, measure the type and quality of service that they receive, and ultimately establish service‐level agreements and bill for those services. This paper presents an approach to accounting in IP networks that meets these needs based on a special‐purpose network probe, which we term a NetCounter. The key functionality of a NetCounter is real‐time, in‐network correlation of network traffic with the individual users that generated it. This approach has several technical advantages over alternative approaches. Most importantly, the NetCounter achieves substantial in‐network aggregation, reducing the volume of usage data generated by between two and four orders of magnitude (when compared to flow‐logging systems). In addition, NetCounters capture usage data at the level of individual users and record detailed, user‐ and service‐specific performance metrics.