# US 2017/0286126 A1 · Dynamically loading firmware based on geographic location

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2017/0286126 A1
- Document ID: US20170286126A1
- Status: Published application
- Kind: A1
- Application number: 15/084,846
- Filed: 2016-03-30
- Published: 2017-10-05
- Earliest claimed: 2016-03-30
- Assignees: Lenovo Enterprise Solutions (Singapore) Pte. Ltd.
- Applicants: LENOVO Enterprise Solutions (Singapore) PTE. LTD.
- Inventors: PAUL ARTMAN; GARY D. CUDAK
- Web page: https://patentgrep.com/patent/US20170286126A1

## CPC

- G06F 8/654: using techniques specially adapted for alterable solid state memories, e.g. for EEPROM or flash memories
- G06F 9/4411: {Configuring for operating with peripheral devices; Loading of device drivers}
- G06F 9/4416: {Network booting; Remote initial program loading [RIPL]}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Apparatuses, methods, systems, and program products are disclosed for dynamically loading firmware based on geographic location. A location module determines a geographic location associated with a system. A firmware module determines a firmware configuration associated with the geographic location. A loading module dynamically accesses the firmware configuration associated with the geographic location from a remote data store, and loads the firmware configuration on the system.

## Claims

### Claim 1

An apparatus comprising:
a location module that determines a geographic location associated with a system;
a firmware module that determines a firmware configuration associated with the geographic location; and
a loading module that dynamically accesses the firmware configuration associated with the geographic location from a remote data store, and loads the firmware configuration on the system.

### Claim 2 (depends on 1)

The apparatus of claim 1, wherein the remote data store is one of a plurality of remote data stores, each remote data store being associated with a geographic location and storing firmware configurations intended for systems located at the geographic location.

### Claim 3 (depends on 1)

The apparatus of claim 1, further comprising an association module that associates one or more firmware configurations with a combination of a geographic location and one or more systems.

### Claim 4 (depends on 1)

The apparatus of claim 1, wherein the location module determines the geographic location for the system after the system is booted, but before a firmware configuration stored on the system is loaded.

### Claim 5 (depends on 1)

The apparatus of claim 1, wherein a firmware configuration determined for the system located in the geographic location is different than a firmware configuration determined for the system located in a different geographic location.

### Claim 6 (depends on 1)

The apparatus of claim 1, wherein the system is configured with a system configuration corresponding to the geographic location, the firmware module further determining the firmware configuration for the system based on the system configuration for the geographic location where the system is located.

### Claim 7 (depends on 7)

The apparatus of claim 7, wherein the system is configured according to one or more regulations associated with the geographic location, the one or more regulations comprising one or more of network regulations, environmental regulations, power regulations, data security regulations, and user access regulations.

### Claim 8 (depends on 1)

The apparatus of claim 1, wherein the firmware module further determines one or more characteristics of an infrastructure of the geographic location, the firmware module determining the firmware configuration based on the one or more infrastructure characteristics.

### Claim 9 (depends on 1)

The apparatus of claim 1, wherein the geographic location associated with the system is determined from one or more of a system setting, a location service, a time zone, an internet protocol (“IP”) address, and a network latency between the system and the remote data store.

### Claim 10 (depends on 1)

The apparatus of claim 1, wherein the loading module does not access the firmware configuration associated with the geographic location from the remote data store in response to the firmware module determining that the firmware configuration associated with the geographic location is currently loaded on the system.

### Claim 11 (depends on 1)

The apparatus of claim 1, wherein the loading module updates one or more firmware pointers on the system, the one or more firmware pointers pointing to one or more storage locations for the firmware configuration on the remote data store.

### Claim 12 (depends on 1)

The apparatus of claim 1, wherein the firmware configuration comprises one or more files configured for the geographic location, the one or more files comprising one or more of device drivers, system settings, localization settings, access settings, and application settings.

### Claim 13

A method comprising:
determining, by use of a processor, a geographic location associated with a system;
determining a firmware configuration associated with the geographic location; and
dynamically accessing the firmware configuration associated with the geographic location from a remote data store, and loading the firmware configuration on the system.

### Claim 14 (depends on 13)

The method of claim 13, wherein the remote data store is one of a plurality of remote data stores, each remote data store being associated with a geographic location and storing firmware configurations intended for systems located at the geographic location.

### Claim 15 (depends on 13)

The method of claim 13, further comprising associating one or more firmware configurations with a combination of a geographic location and one or more systems.

### Claim 16 (depends on 13)

The method of claim 13, wherein a firmware configuration determined for the system located in the geographic location is different than a firmware configuration determined for the system located in a different geographic location.

### Claim 17 (depends on 13)

The method of claim 13, wherein the system is configured with a system configuration corresponding to the geographic location, the firmware configuration for the system being determined based on the system configuration for the geographic location where the system is located.

### Claim 18 (depends on 17)

The method of claim 17, wherein the system is configured according to one or more regulations associated with the geographic location, the one or more regulations comprising one or more of network regulations, environmental regulations, power regulations, data security regulations, and user access regulations.

### Claim 19 (depends on 13)

The method of claim 13, further comprising determining one or more characteristics of an infrastructure of the geographic location, the firmware configuration being determined based on the one or more infrastructure characteristics.

### Claim 20

A program product comprising a computer readable storage medium that stores code executable by a processor, the executable code comprising code to perform:
determining a geographic location associated with a system;
determining a firmware configuration associated with the geographic location; and
dynamically accessing the firmware configuration associated with the geographic location from a remote data store, and loading the firmware configuration on the system.
