JP2011523481A5

JP2011523481A5 -

Info

Publication number: JP2011523481A5
Application number: JP2011510489A
Authority: JP
Filing date: 2009-04-30
Publication date: 2012-06-14

Claims

A host device configured to communicate with a peripheral device,
A first software entity;
A plurality of code sets configured for the host device communicating with the peripheral device, wherein one code set of the plurality of code sets is customized to the first software entity When,
One or more processors,
Determining whether to validate the credentials for the first software entity as valid in response to a request by the first software entity communicating with the peripheral; and
If the credentials are valid, allow the first software entity to use at least a portion of the one code set, wherein at least a portion of the one code set is the first software entity One or more processors adapted to be used to communicate with the peripheral device and allow the peripheral device to verify itself;
A host device comprising:

The host device according to claim 1,
The request includes a task request from the first software entity,
The one or more processors may execute the task request on the first software entity when the one or more processors are programmed with at least a portion of the one code set. A host device configured to allow use of at least a portion thereof.

The host device according to claim 1,
The one or more processors are:
Providing one or more authentication options to the first software entity;
Receiving a response from the first software entity indicating any one of the one or more authentication options; and
A host device configured to determine whether to verify the credentials from the first software entity as valid by verifying the credentials based on the response.

The host device according to claim 1,
The host device, wherein the one or more processors are further configured to return an error to the first software entity if the credentials are not valid.

The host device according to claim 1,
The one or more processors include a software entity handler that provides access to the one code set using an identifier associated with the first software entity in a cryptographic function if the credentials are valid. A host device configured to allow the first software entity to use at least a portion of the one code set by generating.

The host device according to claim 5, wherein
The one or more processors may allow the first software entity to use at least a portion of the one code set by sending the software entity handler to the first software entity. Further configured host device.

The host device according to claim 5, wherein
The one or more processors are:
If the credentials are valid, register the first software entity in a table of authorized software entities; and
If the credentials are valid, further configured to register the software entity handler in the table;
The one or more processors are configured to determine whether to validate credentials from the first software entity as valid by reviewing the table of authorized software entities. Host device.

The host device according to claim 7, wherein
The one or more processors are configured to send an indication indicating that the first code set is presented to the first software entity if the first software entity is successfully registered. Configured host device.

The host device according to claim 7, wherein
If the one or more processors are programmed with at least a part of the one code set, the one or more processors may receive the software while the first software entity is registered in the table. A host device configured to allow the first software entity to perform a task related to the peripheral device using an entity handler.

The host device according to claim 7, wherein
The one or more processors are configured to register a permission related to the first software entity in the table, wherein the permission indicates the one code set accessible by the first software entity. .

The host device according to claim 7, wherein
The one or more processors are configured to deregister the first software entity if the first software entity has been registered in the table for a predetermined period indicated in the table. Host device being used.

The host device according to claim 7, wherein
The one or more processors are:
Receiving a task request from the first software entity;
If at least part of the code set is programmed into the one or more processors, the task request is executed; and
A host device configured to deregister the first software entity from the table after the task request is executed.

The host device according to claim 1,
The peripheral device is a host device which is a flash memory device.

The host device according to claim 1 ,
The one or more processors are:
Receiving a request to store content at a group of the peripheral devices, wherein the request is received from the first software entity; and
If the credentials are valid, configured to allow the first software entity to use at least part of the one code set by accessing an encryption key associated with the group. Host device.

The host device according to claim 1,
The request includes a request to access content at a group of the peripheral devices, the request is received from the first software entity,
The one or more processors use at least a portion of the one code set for the first software entity by accessing an encryption key associated with the group if the credentials are valid; A host device that is configured to allow

A method for providing access to a peripheral device, comprising:
In a host device having a plurality of code sets being used to communicate with the peripheral device,
Determining whether a first software entity seeks to communicate with the peripheral device;
In response to determining that the first software entity seeks to communicate with the peripheral device, determining whether to authenticate the first software entity on the host device;
In response to determining whether to authenticate the first software entity, the first of a plurality of code sets used to communicate with the peripheral device on the host device Allows the first software entity to access a code set that is customized to a software entity and is used to communicate with the peripheral device and allow the peripheral device to verify itself And steps to
A method comprising the steps of:

The method of claim 16, wherein
The one code set is dedicated to the first software entity communicating with the peripheral device;
The method of allowing the first software entity to access the one code set comprises allowing access to device driver code and application programming interface code.

The method of claim 16, wherein
Receiving a task request from the first software entity in the one code set;
Performing the task request using at least a portion of the one code set;
A method further comprising:

The method of claim 16, wherein
Determining whether to authenticate the first software entity comprises:
Receiving credentials from the first software entity;
Verifying the credentials performed by the one code set;
Including methods.

The method of claim 19, wherein
Providing one or more authentication options for the first software entity performed by the one code set;
Receiving from the first software entity a response indicating any one of the one or more authentication options;
The verifying includes verifying the credentials based on the response.

The method of claim 16, wherein
A method further comprising returning an error to the first software entity if the first software entity is not successfully authenticated.

The method of claim 16, wherein
If it is determined to authenticate the first software entity, generating a software entity handler that provides access to the one code set using an identifier associated with the first software entity in a cryptographic function Further comprising a method.

The method of claim 22, wherein
Transmitting the software entity handler configured to provide access to at least a portion of the one code set to the first software entity.

The method of claim 22, wherein
If the first software entity has been successfully authenticated, the method further comprises registering the first software entity using the one code set, the registering step comprising: Registering the software entity handler in a table.

25. The method of claim 24, wherein
Further comprising transmitting an indication to which the one code set is presented, wherein the transmitting step includes providing the indication to the first software entity if the first software entity has been successfully registered. A method comprising sending.

26. The method of claim 25, wherein
While the first software entity is registered, the method further includes permitting the first software entity to perform a task related to the peripheral device, and the permitting step is performed together with the one code set. Allowing the first software entity to perform the task using the software entity handler.

25. The method of claim 24, wherein
The registering step includes registering a permission associated with the first software entity, wherein the permission indicates one or more portions of the one code set accessible by the first software entity.

25. The method of claim 24, wherein
A method further comprising deregistering the first software entity if the first software entity has been registered in the table for a predetermined period indicated in the table.

25. The method of claim 24, wherein
Receiving a task request from the first software entity;
Performing the task request using at least a portion of the one code set;
Deregistering the first software entity from the table using the one code set after the task request is executed;
A method further comprising:

The method of claim 16, wherein
The method wherein the peripheral device is a flash memory device.

The method of claim 16, wherein
Receiving from the first software entity a request to store content in a group of the peripheral devices;
The step of determining whether the first software entity is seeking to communicate with the peripheral device is based on the request,
The step of determining whether to authenticate the first software entity on the host device is performed in a table of previous authenticated software entities to determine whether to authenticate the first software entity. Including access,
Accessing the encryption key associated with the group if the first software entity has been successfully authenticated;
Encrypting the content using the encryption key.

The method of claim 16, wherein
The one code set includes an API for a secure peripheral device,
Using at least a portion of the one code set by the first software entity to allow the first software entity to communicate with the peripheral device is protected content on the peripheral device. And using the secure peripheral device API so that the first software entity communicates with the peripheral device.