Back to results
US 9,002,993 B2Granted
Dynamic configuration of a client-server relationship
AssigneeGreenwave Systems PTE LTD
InventorChristian Vandendorpe
Life of this patent
Estimating the term…
Abstract
A network client may retrieve a unique ID for the network client and a first server identifier from within the network client. The network client may send the unique ID to a first server identified by the first server identifier. The first server may look up a second server identifier using the unique ID as a key in a database query and return the second server identifier to the network client. The network client may send data to a second server identified by the second server identifier.
Claims19
A method of configuring a client-server relationship, the method comprising:
- retrieving a unique identifier from non-volatile solid-state memory located within a network client;
- sending the unique identifier from the network client to a first server, without any user action, by using a first server identifier to communicate across an internet connection;
- receiving a packet of information at the network client from the first server identifying three different servers having three different functions;
- sending data from the network client to a second server using a second server identifier;
- retrieving a firmware update for the network client from a third server using a third server identifier;
- receiving a request for information from a networked device at the network client;
- and
- providing a fourth server identifier to the networked device from the network client in response to the request for information;
- wherein the packet of information received at the network client comprises:
- at least three different server identifiers including the second server identifier, the third server identifier, and the fourth server identifier;
- an interval to wait between checking for updated firmware;
- and
- at least one of:
- a first port number to use in communicating with at least one of the first server, the second server, or the third server, without security;
- a second port number to use in communicating with at least one of the first server, the second server, or the third server, using secure sockets layer (SSL) security;
- or
- a string to use as a NetBIOS name for the network client.
14 more elements
A non-transitory computer readable storage medium having computer readable program code embodied therewith, the computer readable program code comprising:
- computer readable program code configured to retrieve a unique identifier from within a network client;
- computer readable program code configured to send the unique identifier to a first server, without any user action, by using the first server identifier to communicate across an internet connection;
- computer readable program code configured to receive a packet of information from the first server to identify three different servers having three different functions;
- computer readable program code configured to send data to a second server using a second server identifier;
- computer readable program code configured to retrieve a firmware update from a third server using a third server identifier;
- computer readable program code configured to receive a request for information from a networked device;
- and
- computer readable program code configured to provide a fourth server identifier to the networked device in response to the request for information;
- wherein the packet of information received comprises:
- at least three different server identifiers including the second server identifier, the third server identifier, and the fourth server identifier;
- an interval to wait between checking for updated firmware;
- and
- at least one of:
- a first port number to use in communicating with at least one of the first server, the second server, or the third server, without security;
- a second port number to use in communicating with at least one of the first server, the second server, or the third server, using secure sockets layer (SSL) security;
- or
- a string to use as a NetBIOS name for the network client.
14 more elements
A network client comprising:
- a processor;
- and
- a network interface communicatively coupled to said processor and configured to send and receive data over a computer network;
- wherein the processor is configured to:
- retrieve a unique identifier and a first server identifier from within the network client;
- send the unique identifier to a first server, through the network interface, without any user action, by using the first server identifier to communicate across an internet connection;
- receive a packet of information from the first server, through the network interface, to identify three different servers having three different functions;
- send data to a second server, through the network interface, using a second server identifier;
- retrieve a firmware update from a third server, through the network interface, using a third server identifier;
- receive a request for information from a networked device, through the network interface;
- and
- provide a fourth server identifier to the networked device, through the network interface, in response to the request for information;
- wherein the packet of information received comprises:
- at least three different server identifiers including the second server identifier, the third server identifier, and the fourth server identifier;
- an interval to wait between checking for updated firmware;
- and
- at least one of:
- a first port number to use in communicating with at least one of the first server, the second server, or the third server, without security;
- a second port number to use in communicating with at least one of the first server, the second server, or the third server, using secure sockets layer (SSL) security;
- or
- a string to use as a NetBIOS name for the network client.
18 more elements
Dependencies are inferred from the claim text.