DEVICES AND METHODS FOR DEVICE-MAPPING CONNECTIVITY HUB

Abstract

The present invention discloses devices and methods for a connectivity hub, for connecting a plurality of storage devices to a host system, including: a plurality of ports, each port operative to electrically engage with a storage device; electrical paths joining the plurality of ports to a common point operationally connected to the host system; and a controller operative to associate a relative physical location with a logical identity for each port. Preferably, the controller is configured to perform the association by correlating an insertion time of the storage device in a respective port with a detection time of the logical identity. A connectivity hub, for connecting a plurality of storage devices to a host system, including: at least 23 ports, each port operative to electrically engage with a corresponding storage device; and electrical paths joining at least 23 ports to a common point operationally connected to the host system.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is herein described, by way of example only, with reference to the accompanying drawings, wherein:

FIG. 1 is a simplified schematic block diagram of a device-mapping connectivity hub, according to preferred embodiments of the present invention;

FIG. 2 is a high-level schematic block diagram of the connectivity hub of FIG. 1;

FIG. 3 is a simplified schematic block diagram of a device-mapping connectivity hub in which a port sensor is used to identify the physical ports of newly-mounted storage devices, according to preferred embodiments of the present invention;

FIG. 4 is a simplified flowchart of the device-mapping procedure associated with the connectivity hub of FIG. 1, according to preferred embodiments of the present invention.

DESCRIPTION OF THE PREFERRED EMBODIMENTS

The present invention relates to devices and methods for providing user-specific connectivity, to a plurality of storage devices, for a plurality of end-users in a room. The principles and operation for providing user-specific connectivity for a plurality of end-users in a room, according to the present invention, may be better understood with reference to the accompanying description and the drawings.

Referring now to the drawings, FIG. 1 is a simplified schematic block diagram of a device-mapping connectivity hub, according to preferred embodiments of the present invention. A device-mapping connectivity hub 10 is shown in FIG. 1 having multiple ports 12 for connecting a plurality of PSDs. As an example, hub device 10 is configured with a total of 30 ports 12 in rows A, B, C, D, and E and columns I, II, III, IV, V, and VI, according to the layout of seats in a classroom.

A user entering the classroom connects his/her PSD into a respective port 12 in connectivity hub 10 according to the location of the user's seat in the classroom. For example, a student planning to sit in the right-most seat of the first row in the classroom connects his/her PSD to a respective port 12 located in connectivity hub 10 positioned in row A, column VI; whereas a student planning to sit in the left-most seat of the last row in the classroom connects his/her PSD to a respective port 12 located in connectivity hub 10 positioned in row E, column I.

FIG. 2 is a high-level schematic block diagram of the connectivity hub of FIG. 1. A controller 20 monitors ID data passing through connectivity hub 10 from ports 12 via respectively-mounted PSDs. ID data from each storage device is transferred to a host system 22 (e.g. a teacher's computer). As an example, the ID data is displayed on host system 22 according to the layout of ports 12 in connectivity hub 10.

A locking mechanism 24 is optionally provided for locking a PSD in its position in connectivity hub 10 such that that removal of the PSD from its respective port 12 is possible only upon providing an authorized key. Locking mechanism 24 is provided to prevent an unauthorized user from removing a PSD that does not belong to him/her from connectivity hub 10.

Locking mechanism 24 can be implemented using an electrically-actuated latch, to secure and release the PSD in its position in connectivity hub 10, in conjunction with an authorizing device, for validating the user, such as a fingerprint-recognition device (e.g. Security Key Fingerprint Mini Flash Drive, available from ACP-EP Memory, Irvine, Calif.). Alternatively, locking mechanism 24 can be implemented using a physical key (as described in detail in US Patent Publication No. 20070016965, assigned to the assignee of the present invention, and hereby incorporated by reference as if fully set forth herein), or by entering a password (e.g. via a keypad 26) for unlocking the PSD from its respective port 12, enabling only an authorized user to disconnect the PSD.

Locking mechanism 24 is shown in FIG. 2 connected to only one port 12; however, it should be understood that a respective locking mechanism 24 can be connected to each port 12 as a token communication point (e.g. a USB port, a keypad, an electronic-sensor mechanism, and an optical-sensor mechanism). Implementing a biometric sensor, such as a fingerprint reader, within locking mechanism 24 for authenticating the user is optional. A display 28 is optionally provided for displaying the location of the seats in a room (e.g. for viewing by a user connecting his/her PSD to connectivity hub 10).

A power source 30, optionally residing within connectivity hub 10, is provided as a means for supplying power to each PSD connected to connectivity hub 10. Power source 30 is provided only in order to overcome the limitations of existing UFD technology known in the art, which have a strict limit on the total power consumption (and as a result, on the total number of devices) that can be used for power drawn from a host system.

Optionally, controllable port switches 32 (e.g. mechanical or electronic) can be connected to the VCC lines of each port 12. When host system 22 needs to identify the volumes mounted into connectivity hub 10 and link the volumes to physical ports 12, host system 22 disconnects the VCC to all the PSDs using switches 32, and then turns the VCC to each port 12 on again one by one. Each port 12 that is powered up will initiate the mounting process of the volume that is engaged into the respective port 12. This enables host system 22 to identify the volumes as the volumes appear in host system 22. Port switches 32 are shown in FIG. 2 connected to only two ports 12; however, it should be understood that a respective port switches 32 can be connected to each port 12.

FIG. 3 is a simplified schematic block diagram of a device-mapping connectivity hub in which a port sensor is used to identify the physical ports of newly-mounted storage devices, according to preferred embodiments of the present invention. A connectivity hub 40 includes a USB port sensor 42 that is connected to host system 22 via controller 20, and has hard-wired connections 44 to each physical port 12. By monitoring the electrical current through controller wires 46 to ports 12, port sensor 42 can identify, for example, the insertion of PSDs 48 and 50 into ports CI and DII (using the exemplary layout in FIG. 1 as an example), and report such an event to host system 22 via a USB protocol. While host system 22 will not get a direct indication from port sensor 42 about the identity of the PSD that is inserted into connectivity hub 32, the time correlation between the detection of an engaged port 12 and the mounting of a new volume clearly indicates to host system 22 the correlation between the engaged port 12 and the new volume.

It should be noted that the present invention relates to implementing a connectivity hub with a plurality of ports configured, in correspondence to the location of users in a classroom, to allow connection to a plurality of PSDs. However, it is understood that other implementations are possible within the scope of the invention, relating to a connectivity hub, of any design, implemented to provide a connection port to a plurality of external peripheral devices.

FIG. 4 is a simplified flowchart of the device-mapping procedure associated with the connectivity hub of FIG. 1, according to preferred embodiments of the present invention. First, a user inserts a device into into a port of the device-mapping connectivity hub (Step 60). The system determines whether the device is a PSD (Step 62). If the device is not a PSD, the device is designated as a peripheral device (Step 64). If the device is a PSD, a drive letter is assigned to the PSD (Step 66). The PSD is dismounted, removing the allocation of the drive letter (Step 68).

The system then determines whether a secondary directory name exists in a pre-defined drive (Step 70). If a secondary directory name does not exist, a secondary directory name is created (Step 72), and the PSD is mounted as a sub-directory in the secondary directory (Step 74). If a secondary directory name exists, the PSD is mounted as a sub-directory in the secondary directory (Step 74). The system then adds a respective sub-directory name for the PSD to be mounted from the secondary directory (Step 76).

Optionally, the system can determine the mapping of the logical volume to the relative position of the PSD in the hub by correlating the insertion time of the PSD with the mounting of the volume (Step 78). Optionally and alternatively, the system can use a port sensor, port switches, or identifying information on the PSD to determine the mapping of the logical volume to the relative position of the PSD in the hub (Step 80).

Upon removal of the PSD from the connectivity hub, the directory name allocated for the PSI) is removed (Step 82). If there are no remaining PSDs in the hub, the secondary directory is removed (Step 84).

In a more general way, the present invention can be used as a business method for providing a moderator (e.g. teacher, event coordinator, venue supervisor) with a venue layout. In such an embodiment, the venue (e.g. classroom, auditorium, campus, stadium) has objects (e.g. student belongings, desks, seats, and work stations) located in the venue. A panel (e.g. a device-mapping connectivity hub) having ports located in the panel is used to identify a relative physical location of storage devices engaged in respective ports with corresponding objects. A representation of the storage devices associated with the corresponding objects is displayed on a moderator display.

While the invention has been described with respect to a limited number of embodiments, it will be appreciated that many variations, modifications, and other applications of the invention may be made.

APPENDIX
The Visual Basic Code
Attribute VB_Name = “General”
Public Const FO_DELETE = &H3
Public Const FOF_ALLOWUNDO = &H40
Public Const FOF_NOCONFIRMATION = &H10
Public Type SHFILEOPSTRUCT
hWnd As Long
wFunc As Long
pFrom As String
pTo As String
fFlags As Integer
fAborted As Boolean
hNameMaps As Long
sProgress As String
End Type
Public Type SECURITY_ATTRIBUTES
nLength As Long
lpSecurityDescriptor As Long
bInheritHandle As Long
End Type
Public Declare Function SHFileOperation Lib “shell32.dll” Alias —
“SHFileOperationA” (lpFileOp As SHFILEOPSTRUCT) As Long
Public Declare Function CreateDirectory Lib “kernel32”
Alias
“CreateDirectoryA” —
(ByVal lpPathName As String,
lpSecurityAttributes As
SECURITY_ATTRIBUTES) As Long
Public Declare Function GetVolumeInformation Lib “kernel32” —
Alias “GetVolumeInformationA” (ByVal
lpRootPathName As String, —
ByVal lpVolumeNameBuffer As String, ByVal
nVolumeNameSize As Long, —
lpVolumeSerialNumber As Long,
lpMaximumComponentLength As
Long, —
lpFileSystemFlags As Long, ByVal
lpFileSystemNameBuffer As String, —
ByVal nFileSystemNameSize As Long) As Long
Public Declare Function GetDriveType Lib “kernel32” —
Alias “GetDriveTypeA” —
(ByVal lpRootPathName As String) As Long
Public Declare Function FindVolumeClose Lib “kernel32” —
(ByVal hFindVolume As Long) As Long
Public Declare Function FindFirstVolume Lib “kernel32” —
Alias “FindFirstVolumeA” —
(ByVal lpszVolumeName As String, —
ByVal cchBufferLength As Long) As Long
Public Declare Function FindNextVolume Lib “kernel32” —
Alias “FindNextVolumeA” —
(ByVal hFindVolume As Long, —
ByVal lpszVolumeName As String, —
ByVal cchBufferLength As Long) As Long
Public Declare Function FindVolumeMountPointClose Lib
“kernel32” —
(ByVal hFindVolume As Long) As Long
Public Declare Function FindFirstVolumeMountPoint Lib “kernel32” —
Alias “FindFirstVolumeMountPointA” —
(ByVal lpszRootPathName As String, —
ByVal lpszVolumeMountPoint As String, —
ByVal cchBufferLength As Long) As Long
Public Declare Function FindNextVolumeMountPoint Lib “kernel32” —
Alias “FindNextVolumeMountPointA” —
(ByVal hFindVolume As Long, —
ByVal lpszVolumeName As String, —
ByVal cchBufferLength As Long) As Long
Public Declare Function lstrlen Lib “kernel32” —
Alias “lstrlenW” (ByVal lpString As Long) As Long
Public Declare Function GetVolumeNameForVolumeMountPoint
Lib “kernel32” —
Alias “GetVolumeNameForVolumeMountPointA” —
(ByVal lpszVolumeMountPoint As String, —
ByVal lpszVolumeName As String, —
ByVal cchBufferLength As Long) As Long
Public Declare Function SetVolumeMountPoint Lib “kernel32” —
Alias “SetVolumeMountPointA” —
(ByVal lpszVolumeMountPoint As String, —
ByVal lpszVolumeName As String) As Boolean
Public Declare Function DeleteVolumeMountPoint Lib “kernel32” —
Alias “DeleteVolumeMountPointA” —
(ByVal lpszVolumeMountPoint As String) As Boolean
Alias “GetVolumePathNamesForVolumeNameA” —
(ByVal lpszVolumeName As String, —
ByVal lpszVolumePathNames As String, —
ByVal cchBufferLength As Long, —
ByVal lpcchReturnLength As Long) As Long
Public Declare Function GetUserName Lib “advapi32.dll”
Alias “GetUserNameA” —
(ByVal lpBuffer As String, nSize As Long) As Long
Public Declare Function IsUserAnAdmin Lib “shell32” ( ) As Long

The API functions used for the above set of operations are kept in Window's “Volume Management Functions”. Among the functions used are:

• • SetVolumeMountPoint: Make the directory mount point to the volume name. Thus, when mounted the volume name is associated with the specified directory.
  • DeleteVolumeMountPoint: Release the drive letter that was created by the UFD's insertion.
  • GetVolumeNameForVolumeMountPoint: Return the volume name for the drive letter.

The attached source code include 3 ‘BAS’ files. The code is written in Visual Basic. The following provide some insight to each of these files:

• 1. ‘General.BAS’: This file includes the type definitions and function declarations of the code.
• 2. ‘Start.BAS’: This is the file that includes the “main( )” function. This function only activates the ‘Bgen_Class’ module. The purpose of this module is to detect ‘device insertion’ or ‘device removed’. If the device is a USB removable disk (e.g. a UFD), the module activates the event ‘DeviceDetect’, and provides the information whether the device received a drive letter, and if it was inserted or ejected.
• 3. ‘Fgen_main.FRM’: This file includes the implementation of all functions that also handle the different events. The file contains 12 functions that are briefly described below:
  • 3.1. Form_Load( ): Start the detection of UFDs inserted or removed. Create the directory ‘c:\USB_ports’, if required. Ask to delete the directory: “c:\USB_ports” (if it exists) upon loading such that the directory is empty when used.
• 3.2. Form_Unload( ): Upon UFD removal, checks whether the directory ‘C:\USB_ports’ is empty. In this case, it means that the last UFD was removed, and then this function deletes the directory ‘C:\USB_ports’.
  • 3.3. boGen_Class_DeviceDetectNoDriveLetter( ): Activate the event ‘evicebetectNoDriveLetter’. Checks whether a PSD (e.g. UFD) was either inserted or removed such that the UFD has no drive letter assigned to it. In case, the UFD was inserted, create directory that will be mounted for the inserted UFD. If the UFD is removed, then delete the directory of the removed UFD.
  • 3.4. boGen_Class_DeviceDetectWithDriveLetter( ): Acts in a similar manner to ‘boGen_Class_DeviceDetectNoDriveLetter( )’, but since a drive letter is assigned to the UFD, this function also releases the drive letter that was created by the UFD's insertion.
  • 3.5. Deltree( ): Delete a directory and all its sub-directories using API functions. This function is called by the above functions except ‘boCen_Class_DeviceDetectWithDriveLetter( )’, since in this case a drive letter is assigned and not a directory.
  • 3.6. CreateDir( ): Creates a directory using API functions. This function is called with the required directory name from ‘Form_Load( )’ to create the directory ‘C:\USB_ports’, and from the functions ‘boGen_Class_DeviceDetectNoDriveLetter( )’ and ‘boGen_Class_DeviceDetectWithDriveLetter( )’ to create the directories for the corresponding UFD upon insertion.
  • 3.7. GetVolumeFromDrive( ): Returns the volume name for drive letter. For example f:=>\\?Volume{cc6f0f25-23ba-11db-8212-806d6172696f}\.
  • 3.8. GetPathNamesFromVolumeName( ) Returns the directory that is mount pointed to the volume name. For example: ‘\\?\Volume{cc6f0f25-23ba-11db-8212-806d6172696f}\’ returns ‘c:\USB_ports\UFD1’.
  • 3.9. FillVolumeNamesArray( ): Fills the ‘msVolumeNameArr’ array with the current volume's mount point. The ‘msVolumeNameArr’ array holds the current volume's mount point (e.g. when the function “mounivol” is run in command line.
  • 3.10. GetFreeDirNum( ): Returns the current free number of directory that will be mounted for the last inserted UFD.
  • 3.11. CompareVolumeArrays( ): Compares the new list of volumes mount pointed to the old list, and returns the volume name of the volumes added or removed.

Dismounting a volume, in Windows XP as a drive, and instead allocating a directory for it:

• 1. Right Click on “My Computer” icon.
• 2. Click “Manage”, a window appears with “Computer Management” in its banner area (top of the window).
• 3. Select “Disk Management” on the lower-left side of the window. Then, on the right side of the window, all volumes appear.
• 4. Select the volume that corresponds to the UFD already inserted.
• 5. Right-click the selected volume, and click “Change Drive Letter and Paths for . . . ”. The “ . . . ” here stands for the name of the volume and drive letter already allocated. A window will appear with three buttons “Add . . . ”; “Change . . . ” “Remove”.
• 6. Click on the drive letter, and then clock on “Remove”. Then, confirm the operation in the message window opened. The window is closed, and the “Computer Management” window reappears.
• 7. Again, right-click on the desired volume in the right side of the “Computer Management”, the click again “Change Drive Letter and Paths for . . . ”. Here, the ‘ . . . ’ stands for the volume name only.
• 8. Click ‘Add . . . ’. A window opens. Click the radio button “Mount in the following empty NTFS folder”. Insert the empty directory name directly, or browse for an empty directory in an existing NTFS drive. When browsing, one can also create a new directory for the designated volume.
• 9. Click “OK”. Close the “Computer Management” window.

The device can now be approached as a directory in the selected NTFS drive.

Claims

1. A connectivity hub for connecting a plurality of storage devices to a host system, the connectivity hub comprising: (a) a plurality of ports, each said port operative to electrically engage with a storage device;(b) electrical paths joining said plurality of ports to a common point operationally connected to the host system; and(c) a controller operative to associate a relative physical location with a logical identity for said each port.

2. The hub of claim 1, wherein data, stored in said storage device, is configured to be displayed on a display at a display location that corresponds to a physical identity of a corresponding said port.

3. The hub of claim 1, wherein said ports are arranged in the hub in a layout corresponding to physical entities in a pre-defined space.

4. The hub of claim 3, wherein said layout corresponds to at least one location selected from the group consisting of: a location of users in a room and a location of seats in a room.

5. The hub of claim 3, wherein said layout includes a grid of any shape.

6. The hub of claim 1, wherein at least one said port includes an operational connection point to another hub.

7. The hub of claim 1, wherein said each port is adapted to engage with a port component selected from the group consisting of: a USB device. a multi-media card, and a secured digital card.

8. The hub of claim 1, the hub further comprising: (d) a locking mechanism for securing said storage device to a corresponding said port, said locking mechanism configured to allow said storage device to be extracted from said corresponding port only upon said locking mechanism receiving an authorization provided by an authorized key.

9. The hub of claim 8, wherein said locking mechanism includes at least one locking component selected from the group consisting of: a mechanical lock, a keypad, an electronic sensor, an optical sensor, an acoustic sensor, a magnetic sensor, and a biometric sensor.

10. The hub of claim 8, wherein said authorized key is configured to operate said locking mechanism via at least one link selected from the group consisting of: a wired link and a wireless link.

11. The hub of claim 10, wherein said keypad is operative to be activated by said authorized key.

12. The hub of claim 1, wherein said controller is configured to associate said relative physical location with said logical identity by: (i) activating switches to said plurality of ports, and(ii) correlating a current flow, enabled by activating said switches, between an engaged said storage device and said controller.

13. The hub of claim 1, the hub further comprising: (d) a port sensor for detecting said relative physical location of an engaged said port with said storage device.

14. The hub of claim 1, wherein said controller is configured to associate said relative physical location with said logical identity by correlating an insertion time of said storage device in a respective said port with a detection time of said logical identity.

15. A connectivity-hub system for connecting a plurality of storage devices to a host system, the connectivity-hub system comprising: (a) a connectivity hub including: (i) a plurality of ports, each said port operative to electrically engage with a storage device;(ii) electrical paths joining said plurality of ports to a common point operationally connected to the host system; and(iii) a controller operative to associate a relative physical location with a logical identity of said each port; and(b) a display module operative to display data stored in said storage device at a display location, of said display module, that corresponds to a device physical identity of a corresponding said port in said hub.

16. The connectivity-hub system of claim 15, wherein said ports are arranged in said hub in a layout corresponding to physical entities in a pre-defined space.

17. The connectivity-hub system of claim 16, wherein said layout corresponds to at least one location selected from the group consisting of: a location of users in a room and a location of seats in a room.

18. The connectivity-hub system of claim 16, wherein said layout includes a grid of any shape.

19. The connectivity-hub system of claim 15, wherein at least one said port includes an operational connection point to another said hub.

20. The connectivity-hub system of claim 15, wherein said each port is adapted to engage with a port component selected from the group consisting of: a USB device. a multi-media card, and a secured digital card.

21. The connectivity-hub system of claim 15, the connectivity-hub system further comprising: (c) a locking mechanism for securing said storage device to a corresponding said port, said locking mechanism configured to allow said storage device to be extracted from said corresponding port only upon said locking mechanism receiving an authorization provided by an authorized key.

22. The connectivity-hub system of claim 15, wherein said controller is configured to associate said relative physical location with said logical identity by: (i) activating switches to said plurality of ports, and(ii) correlating a current flow, enabled by activating said switches, between an engaged said storage device and said controller.

23. The connectivity-hub system of claim 15, the connectivity-hub system further comprising: (d) a port sensor for detecting said relative physical location of an engaged said port with said storage device.

24. The connectivity-hub system of claim 15, wherein said controller is configured to associate said relative physical location with said logical identity by correlating an insertion time of said storage device in a respective said port with a detection time of said logical identity.

25. A connectivity hub for connecting a plurality of storage devices to a host system, the connectivity hub comprising: (a) at least 23 ports, each said port operative to electrically engage with a corresponding storage device; and(b) electrical paths joining said at least 23 ports to a common point operationally connected to the host system.

26. The hub of claim 25, wherein said corresponding storage device is a Windows-based storage device.

27. A business method for providing a visual representation of a venue, the business method comprising the steps of: (a) providing a panel with a plurality of ports, wherein each said port corresponds to a relative venue position in the venue, said panel configured: (i) to accommodate a respective storage device engaged in said each port;(ii) to report a physical identity of each engaged said storage device to a host system, wherein said physical identity is associated with said relative venue position; and(iii) to allow data to be exchanged between said each engaged storage device and said host system; and(b) offering said panel for sale.

28. A method for connecting a plurality of storage devices to a host system, the method comprising the steps of: (a) configuring a plurality of ports on a connectivity hub to provide a common point operationally connectable to the host system; and(b) associating, via said hub, a relative physical location with a logical identity to each said port.

29. The method of claim 28, the method further comprising the step of: (c) configuring at least one said port to provide said common point with another said hub.

30. The method of claim 28, the method further comprising the step of: (c) electrically engaging a storage device to a corresponding said port.

31. The method of claim 30, the method further comprising the step of: (d) displaying data, stored in said storage device, at a display location that corresponds to a physical identity of said corresponding port.

32. The method of claim 30, the method further comprising the step of: (d) securing said storage device to said corresponding port, wherein said storage device can be extracted from said corresponding port only upon said hub receiving an authorization provided by an authorized key.

33. The method of claim 28, wherein said step of associating includes: (i) activating switches to said plurality of ports, and(ii) correlating a current flow, enabled by activating said switches, between an engaged said storage device and said controller.

34. The method of claim 28, the method further comprising the step of: (c) detecting, via a port sensor, said relative physical location of an engaged said port with said storage device.

35. The method of claim 28, wherein said step of associating includes correlating an insertion time of said storage device in a respective said port with a detection time of said logical identity.

36. A method for connecting a plurality of storage devices to a host system, the method comprising the steps of: (a) configuring a plurality of at least 23 ports, each said port operative to electrically engage with a corresponding storage device; and(b) operationally connecting said at least 23 ports to the host system.

37. The method of claim 33, wherein said corresponding storage device is a Windows-based storage device.

38. A computer-readable storage medium having computer-readable code embodied on the computer-readable storage medium, the computer-readable code comprising: (a) program code for configuring a plurality of at least 23 ports, each said port operative to electrically engage with a corresponding storage device; and(b) program code for operationally connecting said at least 23 ports to the host system.