Patent Application
20140298487
The present invention relates generally to data storage devices, and more particularly to a multi-user Universal Serial Bus (USB) key with customizable file sharing permissions.
Data storage devices, such as a Universal Serial Bus (USB) flash drive (also referred to as a “USB key”), are becoming increasingly popular devices for storing, backing-up and transferring computer files. Currently, all the information on the USB key can be made available to any user upon providing the appropriate authentication, such as a password. As a result, multiple users cannot each securely store information on the same USB key with different authentication parameters (e.g., passwords). Furthermore, multiple users cannot securely store information on the same USB key that may be available to other designated users. For example, if user #1 desires to securely store information that may be made available to user #2 and user #3 and if user #4 desires to securely store information that may be made available to user #5 and user #6, then user #1 and user #4 would need to use their own USB keys.
Consequently, multiple users cannot currently share a single USB key securely whereby each user has their files uploaded to the USB key that will be securely available to that particular user and to other users designated by the user if the user so chooses. By not being able to allow multiple users to share a USB key securely, the usefulness of the USB key is lessened.
In one embodiment of the present invention, a method for having multiple users share a single data storage device securely comprises recognizing a first computing device in response to plugging the data storage device into the first computing device. The method further comprises creating a first account on the data storage device for a first user, where the first account is associated with the first user and the first computing device. Additionally, the method comprises receiving, by a controller, data from the first user to be associated with the first account. Furthermore, the method comprises recognizing a second computing device in response to plugging the data storage device into the second computing device. The method further comprises creating a second account on the data storage device for a second user, where the second account is associated with the second user and the second computing device. In addition, the method comprises receiving, by the controller, data from the second user to be associated with the second account. The first user has access to data associated with the first account in response to plugging the data storage device into the first computing device and the second user has access to data associated with the second account in response to plugging the data storage device into the second computing device.
Other forms of the embodiment of the method described above are in a data storage device and in a computer program product.
The foregoing has outlined rather generally the features and technical advantages of one or more embodiments of the present invention in order that the detailed description of the present invention that follows may be better understood. Additional features and advantages of the present invention will be described hereinafter which may form the subject of the claims of the present invention.
A better understanding of the present invention can be obtained when the following detailed description is considered in conjunction with the following drawings, in which:
The present invention comprises a method, data storage device and computer program product for having multiple users share a single data storage device securely. In one embodiment of the present invention, a data storage device, such as a Universal Serial Bus (USB) key, is plugged into a computing device. The USB controller of the USB key recognizes the computing device and creates an account (also referred to herein as the “USB virtual key”) for the user. The created account is associated with the user as well as associated with the computing device. The USB controller may then receive data, such as computer files, uploaded by the user of the USB key which is then associated with the created account. Only that user will be able to view that data on his/her computing device (computing device associated with the created account that is associated with the data to be viewed) unless the user indicates to share that data with other users. Such a process may be repeated each time the USB key is plugged into a different computing device thereby creating multiple accounts associated with multiple computing devices and users. In this manner, a single USB key may be used among multiple users securely.
In the following description, numerous specific details are set forth to provide a thorough understanding of the present invention. However, it will be apparent to those skilled in the art that the present invention may be practiced without such specific details. In other instances, well-known circuits have been shown in block diagram form in order not to obscure the present invention in unnecessary detail. For the most part, details considering timing considerations and the like have been omitted inasmuch as such details are not necessary to obtain a complete understanding of the present invention and are within the skills of persons of ordinary skill in the relevant art.
Referring now to the Figures in detail,
As stated in the Background section, data storage devices, such as a Universal Serial Bus (USB) flash drive (also referred to as a “USB key”), are becoming increasingly popular devices for storing, backing-up and transferring computer files. Currently, all the information on the USB key can be made available to any user upon providing the appropriate authentication, such as a password. As a result, multiple users cannot each securely store information on the same USB key with different authentication parameters (e.g., passwords). Furthermore, multiple users cannot securely store information on the same USB key that may be available to other designated users. For example, if user #1 desires to securely store information that may be made available to user #2 and user #3 and if user #4 desires to securely store information that may be made available to user #5 and user #6, then user #1 and user #4 would need to use their own USB keys. Consequently, multiple users cannot currently share a single USB key securely whereby each user has their files uploaded to the USB key that will be securely available to that particular user and to other users designated by the user if the user so chooses. By not being able to allow multiple users to share a USB key securely, the usefulness of the USB key is lessened.
The principles of the present invention provide a means for enabling a data storage device, such as a USB key, to be shared among multiple users securely thereby increasing the usefulness of the USB key as discussed below in connection with
Referring now to
In one embodiment, memory section 202 is configured to store a program(s) for allowing multiple users to share USB key 101 securely among each other, as discussed herein in connection with
As will be appreciated by one skilled in the art, aspects of the present invention may be embodied as a system, method or computer program product. Accordingly, aspects of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” ‘module” or “system.” Furthermore, aspects of the present invention may take the form of a computer program product embodied in one or more computer readable medium(s) having computer readable program code embodied thereon.
Any combination of one or more computer readable medium(s) may be utilized. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus or device.
Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the C programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
Aspects of the present invention are described below with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the present invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the function/acts specified in the flowchart and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer readable medium that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the computer readable medium produce an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.
The computer program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the function/acts specified in the flowchart and/or block diagram block or blocks.
As discussed above, USB key 101 can be shared among multiple users securely as discussed in connection with
Referring to
In step 302, USB controller 201 recognizes computing device 102 in response to plugging USB key 101 into computing device 102. In one embodiment, USB controller 201 recognizes the type of computing device 102 based on the properties (e.g., name, type, serial number) of computing device 102 available on USB interface 203 using the USB plug and play capabilities.
In step 303, USB controller 201 creates an account (also referred to herein as the “USB virtual key”) on USB key 101 for the user. In one embodiment, the created account is associated with the user as well as associated with computing device 102. As a result, the information stored on USB key 101 that is associated with the created account (discussed below) will only be accessible by the user associated with the created account when the user plugs USB key 101 into the associated computing device 102.
In step 304, USB controller 201 receives data (e.g., receives data, such as computer files, uploaded by the user of USB key 101) from the user to be associated with the created account.
The process of method 300 can be repeated each time USB key 101 is plugged into a different computing device 102 thereby allowing multiple users to share USB key 101 in a secure manner. For example, when USB key 101 is inserted in computing device 102, USB controller 201 recognizes the type of computing device 102 and creates an account or virtual USB key for the user that is associated with that computing device 102. From the perspective of the user, USB key 101 appears to be empty (i.e., does not contain any data, such as computer files) except for a configuration program associated with the created account as discussed further below. The user may upload data into USB key 101 that will be associated with the created account. Only that user will be able to view that data on his/her computing device 102 (computing device 102 associated with the created account that is associated with the data to be viewed) unless the user indicates to share that data with other users by configuring the account via the configuration program as discussed further below. When USB key 101 is removed from this computing device 102 and plugged into another computing device 102, such as by another user, USB controller 201 recognizes the type of computing device 102 and creates a new account for that user to be associated with that computing device 102. Similarly, that user may upload data into USB key 101 that will be associated with this created account. Furthermore, only that user will be able to view that data on his/her computing device 102 (computing device 102 associated with the created account that is associated with the data to be viewed) unless the user indicates to share that data with other users by configuring the account via the configuration program as discussed further below. In this manner, by creating multiple accounts associated with multiple computing devices 102 and users, a single USB key 101 may be used among multiple users securely.
In some implementations, method 300 may include other and/or additional steps that, for clarity, are not depicted. Further, in some implementations, method 300 may be executed in a different order presented and that the order presented in the discussion of
As discussed above, the created account or virtual USB key may be associated with a configuration application allowing the user to configure the account, such as to indicate which other user(s) may have access to the user's data stored in USB key 101. A method for configuring the created account (“virtual USB key”) on USB key 101 is discussed below in connection with
Referring to
In step 402, a determination is made by USB controller 201 as to whether it received any control access rights (e.g., creating, reading, writing and deleting permissions) to the data (e.g., files, folders) associated with the account from the user.
If USB controller 201 receives control access rights to the data associated with the account from the user, then, in step 403, USB controller 201 enables the data associated with the account to be accessed by other users according to the control access rights. For example, the user may select a file(s)/folder(s) and select one or more others users to be able to access the selected file(s)/folder(s) according to the designated control access rights. In one embodiment, when another user who has permission to view the shared resource uses USB key 101 on his/her computing device 102, the user may see an additional folder displayed on computing device 102 containing the shared resources, where such a folder includes an identification of the user who uploaded the shared resources (i.e., such a folder includes an identification of the user that granted permission to view the shared resources).
If, however, USB controller 201 does not receive control access rights to the data associated with the account from the user or upon enabling the data associated with the account to be accessed by other users according to the control access rights, then, in step 404, a determination is made by USB controller 201 as to whether it received any authentication parameter (e.g., password, biometric authentication, such as a fingerprint) for securing access to the data associated with the account from the user.
If USB controller 201 receives an authentication parameter for securing access to the data associated with the account from the user, then, in step 405, USB controller 201 presents the data associated with the account in response to receiving the authentication parameter. For example, if USB key 101 is plugged into another computing device 102, the authentication parameter, such as a password or fingerprint scan, may be required to be received by USB controller 201 in order for USB controller 201 to unlock the data (e.g., computer files) so as to be available to be viewed by the user.
If, however, USB controller 201 does not receive an authentication parameter for securing access to the data associated with the account from the user, then, in step 406, USB controller 201 does not require receipt of an authorization parameter for presenting the data associated with the account.
The principles of the present invention are not to be limited in scope to the configurations discussed above, but instead, the principles of the present invention include any type of configuration that would improve ease of use, functionality and security of the account (“virtual USB key”) and USB key 101. For example, the user may be able to link multiple accounts that were created based on plugging USB key 101 in multiple computing devices 102, where the user is the owner/main user of those computing devices 102. In another example, USB key 101 may be configured to grant owner/administrator access to all the accounts created on USB key 101 as discussed below in connection with
In some implementations, method 400 may include other and/or additional steps that, for clarity, are not depicted. Further, in some implementations, method 400 may be executed in a different order presented and that the order presented in the discussion of
As discussed above,
Referring to
If an initial set-up is not be to be performed by the owner/administrator, then USB controller 201 continues to determine whether an initial set-up is to be performed by the owner/administrator of USB key 101 in step 501.
If, however, an initial set-up is to be performed, a determination is made in step 502 by USB controller 201 as to whether the owner/administrator indicates to establish owner/administrator access to the accounts to be created on USB key 101.
If USB controller 201 receives an indication to establish owner/administrator access to the accounts to be created on USB key 101, then, in step 503, USB controller 201 establishes access to all accounts created on USB key 101 for the owner/administrator. In one embodiment, once the owner/administrator establishes owner/administrator access to the accounts to be created on USB key 101, the owner/administrator may grant other users full access to all the accounts created on USB key 101. In one embodiment, when an owner/administrator has established owner/administrator access to all accounts on USB key 101, the other users are notified, such as via the configuration application associated with the account or via the display of an owner/administrator file on the user's computing device 102, that an owner/administrator will have access to the user's uploaded data. An illustrative use case for an owner to have access to all the accounts on USB key 101 where each other user of USB key 101 only has access to his/her data uploaded to USB key 101 would be where an owner solicits data, such as a vote, on an issue from each user gathered together in a meeting. After each user has uploaded their vote on USB key 101, the user could pass USB key 101 to the next user in the meeting room to add their vote and so forth. After each user in the meeting has inputted their vote, the owner could then tally the vote without the other users (non-owners) being able to view the votes of the other users.
If, however, USB controller 201 does not receive an indication to establish owner/administrator access to the accounts to be created on USB key 101, then, in step 504, USB controller 201 does not establish access to all accounts created on USB key 101 for the owner/administrator.
In some implementations, method 500 may include other and/or additional steps that, for clarity, are not depicted. Further, in some implementations, method 500 may be executed in a different order presented and that the order presented in the discussion of
The descriptions of the various embodiments of the present invention have been presented for purposes of illustration, but are not intended to be exhaustive or limited to the embodiments disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terminology used herein was chosen to best explain the principles of the embodiments, the practical application or technical improvement over technologies found in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein.
