# US 10,372,461 B2 · Device driver registration device and device driver registration method using same

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

- Number: US 10,372,461 B2
- Document ID: US10372461B2
- Status: Granted
- Kind: B2
- Application number: 15/512,810
- Filed: 2015-08-31
- Published: 2017-10-05
- Granted: 2019-08-06
- Earliest claimed: 2014-09-19
- Assignees: Alab Inc.
- Applicants: Alab Inc.; Konami Digital Entertainment Co., Ltd.
- Inventors: Masayuki Araki; Hajime Takahama
- Web page: https://patentgrep.com/patent/US10372461B2

## CPC

- G06F 9/4406: {Loading of operating system}
- G06F 9/4411: {Configuring for operating with peripheral devices; Loading of device drivers}
- G06F 9/44521: {Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

[Problem to be Solved] To register a device driver in the kernel of an operating system by means of a method simpler than conventional methods. [Solution] The device driver is registered in an operating system kernel using a notification driver, which is provided with a driver interface for notifying the operating system kernel of device setting information, and a scenario sequence file, in which device setting information is described which includes device parameters, including configuration structure information about the device, and an execution script for determining the operations of the device. By loading the scenario sequence file into the notification driver, the device driver is registered in the operating system kernel by means of the device interface.

## Claims

### Claim 1

A device-driver registration device comprising:
a notification driver, wherein the notification driver is provided with a driver-interface for notifying an OS kernel of device setting-information, the notification driver not including any device configuration information; and
a scenario sequence file, in which only device setting-information not depending on an operating system is described,
wherein the device setting-information is registered into the kernel via the driver-interface by reading the scenario sequence file into the notification driver.

### Claim 2 (depends on 1)

The device-driver registration device according to claim 1, wherein the notification driver is compiled according to the OS kernel.

### Claim 3

A device driver registration method comprising:
preparing a notification driver and a scenario sequence file, wherein the notification driver comprises a driver-interface for notifying an OS kernel of device setting-information, wherein the notification driver does not include any device configuration information, and wherein the scenario sequence file describes only device setting-information not depending on an operating system, and
registering the device setting-information into the kernel via the driver-interface by reading the scenario sequence file into the notification driver.

### Claim 4 (depends on 3)

The registration method of the device-driver according to claim 3,
wherein the notification driver only functions as an interface to notify the OS of the device setting-information.

### Claim 5 (depends on 3)

The device driver registration method according to claim 3, wherein preparing the notification driver comprises compiling the notification driver according to the OS kernel.

### Claim 6

A registration method of a device-driver comprising:
loading a notification driver into an OS kernel,
wherein the notification driver comprises a driver-interface for notifying the OS kernel of device setting-information, the notification driver not including any device configuration information;
starting initializing a device and reading a scenario sequence file where the device setting-information is described;
executing a main thread to generate a handler based on the scenario sequence file; and
registering a device-driver into the kernel by registering the handler, thereby allowing the scenario sequence file to not depend on the OS kernel.

### Claim 7 (depends on 6)

The registration method according to claim 6,
wherein initializing the device and reading the scenario sequence file where the device setting-information is described comprises:
setting default values of a register; and
clearing a work memory.

### Claim 8 (depends on 6)

The registration method according to claim 6,
wherein executing the main thread to generate the handler based on the scenario sequence file comprises respectively associating a device parameter and an execution script that determines a device operation to every handler according to a table.

### Claim 9 (depends on 6)

The registration method of the device-driver according to claim 6, wherein loading the notification driver into the OS kernel comprises compiling the notification driver according to the OS kernel and loading the compiled notification driver into the OS kernel.