Network with mobile terminals as browsers having wireless access to the internet and method for using same

Patent No. US7526762 (titled "Network with mobile terminals as browsers having wireless access to the internet and method for using same") on Sep 11, 2000. The application was issued on Apr 28, 2009.

What is this patent about?

’762 is related to the field of wireless communication networks, specifically focusing on the management and delivery of software updates and service products to mobile terminals. In traditional thin-client architectures, maintaining consistent software versions and user-specific configurations across a fleet of mobile devices is challenging, especially when devices are intermittently connected or roaming between different access points. The background context involves a system where terminal servers act as intermediaries between mobile units and the broader internet, handling authentication and session-specific data.

The underlying idea behind ’762 is a multi-tier distribution architecture that ensures critical updates and service products reach their destination even if the target terminal is offline during the initial broadcast. Instead of relying on a single push attempt, the system utilizes a configuration server to track the delivery status of software objects across various terminal servers. By maintaining a persistent record of which servers have successfully received and acknowledged an update, the system can transition from a proactive push model to a reactive pull model based on real-time network events.

The claims of ’762 focus on a method and system for managing software and product distribution by identifying a specific subset of users entitled to an update and monitoring the transfer status at the terminal server level. The independent claims describe a process where a central configuration server receives an upgrade message, saves it to a database, and attempts to propagate it to terminal servers. Crucially, the claims cover the mechanism of identifying failed or pending transfers and triggering a re-delivery specifically when a terminal associated with a lagging server is activated.

In practice, the invention functions as a fail-safe synchronization layer between a central management authority and distributed network nodes. When a vendor or service provider releases a new software component or a digital product like a magazine, the central server filters the user base to determine who should receive the content. If a terminal server is unreachable or a transfer is interrupted, the central server flags that specific node. This conditional re-delivery mechanism ensures that as soon as a user powers on their device and authenticates, the system detects the pending update and completes the transfer immediately.

This approach differs from prior solutions by decoupling the initial update release from the final delivery, using the terminal activation event as a secondary trigger for synchronization. Traditional systems often fail if the endpoint or its local gateway is unavailable during a scheduled update window. By integrating a tracking database that associates specific sources with their respective updates and monitoring the delivery state, ’762 provides a robust way to maintain version consistency across a mobile network without requiring constant, high-bandwidth connectivity for every node simultaneously.

How does this patent fit in bigger picture?

Technical Landscape

In the late 1990s when ’762 was filed, mobile internet access was typically implemented using thin client architectures where the majority of application logic and processing resided on a remote server due to severe hardware constraints of mobile terminals. At a time when systems commonly relied on terminal-server models to compensate for limited local memory and processing power, providing a consistent user experience across different network access points was non-trivial. Hardware constraints made the local storage of complex browser configurations, history, and security protocols difficult, often forcing a trade-off between device portability and the richness of the browsing environment.

Prosecution Position

The disclosed invention represents a technical advancement through an architectural shift that decouples user-specific browser configurations from the physical terminal, centralizing them within a remote server that manages session-specific data such as cookies, bookmarks, and history. This integration enables a persistent 'look and feel' and personalized service environment regardless of the terminal's geographical location or the specific network access point used. Furthermore, the architecture overcomes security constraints by implementing a dual-memory isolation strategy within the server, where sensitive configuration parameters are stored in a first memory area physically or logically separated from a second memory area used for volatile Internet-sourced content, thereby preventing virus propagation from downloaded data to the core terminal configuration.

Claims

This patent contains 12 claims, with claims 1, 3, 7, 8, 9, 10, 11, and 12 being independent. The independent claims focus on methods, systems, apparatuses, and computer program products for managing the distribution of software upgrades or service products by receiving upgrade messages, identifying specific users or contracts, and ensuring delivery to terminal servers, including mechanisms to provide the upgrade upon terminal activation if a previous transfer was missed. The dependent claims serve to add specific operational details, such as updating the terminal itself, performing virus scans on the service product, and implementing additional tracking and delivery steps for product information.

Key Claim Terms New

Definitions of key terms used in the patent claims.

Term (Source)Support for SpecificationInterpretation
Activation of a terminal
(Claim 1, Claim 3, Claim 7, Claim 8, Claim 9, Claim 10, Claim 11, Claim 12)
The activation of the terminal initiates a request to the server for authentication of the terminal in order to establish a shared communication session. Accessing the remote server includes the steps of powering on the terminal, establishing a communication link with the gateway to obtain an internet address. Those parameters of the web browser and possible optional services are initialized when the terminal is powered on.The process of powering on a mobile device and establishing a communication link to trigger authentication and the retrieval of configuration parameters or pending upgrades.
At least partial software upgrade
(Claims 1, 7, 9, 11)
Advantageously, the new software components, also known as objects, may be downloaded from different sources from the network to network server of the terminal. Also, at least part of software object may be downloaded from server of terminal to terminal itself. The terminal configuration of memory means control, bearer connection configuration, and user interface, among others, may be downloaded from network to server and possibly also to terminal.The delivery of new software objects, program sections, or configuration parameters to update the terminal's capabilities, user interface, or security settings.
Configuration server
(Claims 1, 3, 7, 8)
The system includes at least one terminal that is capable of wireless communication, a gateway coupled to the terminal previously known as remote server of the terminal. A remote server is coupled to at least one specific register gateway for authenticating the terminal and providing information management services. Either gateway—the authentication register and/or remote server—may be integrated as a part of another server.A central network unit (also referred to as an upgrade server or gateway) that manages the identification of users requiring updates and coordinates the transfer of software to terminal servers.
Configuration upgrade message
(Claims 1, 7, 11)
The new software components, also known as objects, may be downloaded from different sources from the network to network server of the terminal. Software sources from where downloaded products may originate are vendor of the terminal system, Internet network operator, and possibly even content service provider. The update of a terminal and server allows the look and feel of the available user interface and available services to be the latest offered to the user.A communication sent from a software source (such as a vendor or operator) to a central server to initiate the distribution of new software components or settings to terminals and their associated servers.
End service product
(Claims 3, 8, 10, 12)
Optional and additional user specific services such as e-mail, calendar, etc. are isolated from other section of the system. Certain predictable configuration of the terminal browser needs to be in use all the time in order to be in compliance with service providers commercial agreements made with third parties. The service offered for the user terminal varies from full browsing capability to additional user services.A specific software application, service, or content package (such as e-mail or calendar) delivered to a user based on a commercial contract or service agreement.
Terminal server
(Claims 1, 3, 7, 8, 9, 10, 11, 12)
The remote server contains user specific browser parameters such as cookies, bookmarks, and browser history data and/or program sections that are session specific. In the server, the user may have storage of e-mails, calendar and other private applications as well as Internet downloaded information products. The server may contain general terminal specific configuration information and possibly part of terminal programs and data that can be used when web browser is used.A remotely located server that supports a mobile terminal by storing user-specific browser parameters, session-specific program sections, and private applications to enable thin-client functionality.
Terminal servers
(Claim 1, Claim 3, Claim 7, Claim 8, Claim 9, Claim 10, Claim 11, Claim 12)
The remote server contains user specific browser parameters such as cookies, bookmarks, and browser history data and/or program sections that are session specific. In the server, the user may have storage of e-mails, calendar and other private applications as well as Internet downloaded information products. The server may contain general terminal specific configuration information and possibly part of terminal programs and data that can be used when web browser is used.Remotely located servers associated with specific mobile terminal users that store user-specific browser parameters, configuration information, and private applications to support thin-client terminal functionality.

Litigation Cases New

US Latest litigation cases involving this patent.

Case NumberFiling DateTitle
2:25-cv-00333Feb 21, 2025Ecolab Usa Inc. V. Zappbug Inc

Patent Family

Patent Family

File Wrapper

The dossier documents provide a comprehensive record of the patent's prosecution history - including filings, correspondence, and decisions made by patent offices - and are crucial for understanding the patent's legal journey and any challenges it may have faced during examination.

  • Get instant alerts for new documents

US7526762

Application Number
US09659416A
Filing Date
Sep 11, 2000
Publication Date
Apr 28, 2009
External Links
Slate, USPTO , Google Patents