KR20060111354A - Method for setting disk information of storage device for upnp network - Google Patents

Abstract

A method for setting disk information of a storage device in a network is provided to easily perform setting for sharing data of an HNAS(Home Network Attached Storage) without using a complicated setting method that requires expert knowledge. A control application of a home network recognizes a home network storage device and registers it in a system. A user setting and a disk setting are performed according to a setting request action with respect to the home network storage device. The home network storage device is HNAS that can form a logical drive and a logical volume by grouping a plurality of hard disk drives in an array form.

Description

{METHOD FOR SETTING DISK INFORMATION OF STORAGE DEVICE FOR UPNP NETWORK}

1 is a diagram showing a configuration of a home network to which a disk information setting method of a storage device according to the present invention is applied;

2 illustrates a logical volume structure of an HNAS as a storage device;

3 shows a RAID level for a disk of a storage device;

4 illustrates a state variable for a storage service of a storage device;

5A-5G illustrate various GET actions for the configuration and configuration of a storage device in accordance with the present invention;

6 is a flowchart illustrating an operation of a method of setting disk information of a storage device in a network according to the present invention;

FIG. 7 is a flowchart illustrating a more detailed description of operations for a RAID configuration in the flowchart of FIG. 6;

FIG. 8 is a flowchart illustrating the user account registration and volume generation operations in detail in the flowchart of FIG. 6.

<Description of the symbols for the main parts of the drawings>

10: HNAS, 20: personal computer (PC),

30: Laptop computer, 40: PDA,

50: Wirelessless TV, 60: Control Point (CP).

The present invention relates to a method of setting disk information of a storage device on a network, and more particularly, to use HNAS (Network Attached Storage) as a storage space for sharing data files in a Universal Plug and Play (UPnP) home network. A disk information setting method of a storage device on a network for setting information.

In general, UPnP home networks are based on distributed and open networking architectures, enabling peer-to-peer inter-networking without requiring each home appliance or computer within the home network to be centrally managed. It was developed to make it possible.

In the UPnP network, a control point (CP) for controlling each device and a device for providing various services are provided. In the control point CP, various devices are found through a providing interface (Description). Control, and receive and process events.

The UPnP network also includes a media server that provides various media data and a media renderer that plays media data. The media server and the media renderer are control points. Media streaming from the media server is controlled based on various known transport protocols.

The media server enables the control point to view information about media files held by the server through a content directory service (CDS). Information such as the format, file size, presentation time, Uniform Resource Location (URL), file type, and the like.

The Content Directory Service (CDS) is designed to represent objects held by the media server in a tree structure. Each object has information about a container and a media file that may have information about other objects. It is classified as an item corresponding to.

On the other hand, in recent years, with the rapid advance of home network technology, there is a growing interest in storage devices for sharing various files such as multimedia data in the home. Attempts have been made to apply Network Attached Storage (NAS) as a Home Network Attached Storage (HNAS), which provides storage space for sharing.

Accordingly, in the present home network, HNAS is automatically recognized without the complicated setting operation of the user through a separate user interface (UI) device, and various setting operations of the network for the HNAS are arbitrarily selected. The new function to be applied by setting it is urgently required.

Accordingly, the present invention has been made in view of the above-described conventional situation, and an object thereof is to automatically recognize HNAS on a UPnP network and to easily perform various disk settings for use as a storage space for file sharing. A disk information setting method of a storage device is provided.

According to the present invention for achieving the above object, in the network setting method of the home network storage device that provides a file sharing service for each device in the home network, the home network storage device is recognized by the control application of the home network And registering the system with the system, and performing user setting and disk setting by a setting request action for the home network storage device.

Hereinafter, the present invention configured as described above will be described in detail with reference to the accompanying drawings.

1 is a diagram illustrating a configuration of a home network to which a disk information setting method of a storage device according to the present invention is applied.

As shown in FIG. 1, in the UPnP home network to which the method of the present invention is applied, an HNAS 10 for sharing user data or media data with peripheral media devices or computer devices in a network, and user data from the HNAS 10. Alternatively, as a plurality of network devices capable of receiving and processing various media data and presenting the data, a personal computer 20, a laptop computer 30, a PDA 40, a wireless television ( Wireless TV) 50.

The HNAS 10 provides a file sharing protocol of CIFS (Common Internet File System) method to provide an effective file sharing service for each device in a network, and prevents data loss due to an error condition of a disk where data is stored. Redundant Arrays of Inexpensive Disks (RAID) techniques are used.

In addition, the HNAS 10 preferably manages the storage space for each user or group in order to allocate access rights to the storage space on a user or group basis, and a situation in which the storage space is dynamically changed. It is preferable to consider and manage.

The HNAS 10 includes at least one hard disk to store data of a user, and forms a logical drive in an array form of physical drives that are independent of each other by using a plurality of hard disks. As illustrated in 2.

As illustrated in FIG. 2, the HNAS 10 may form physical drives 74 in which a plurality of hard disks 72 are configured in an array form as one logical drive. In addition, a logical volume 70 is formed for at least one logical drive A1 to An.

In addition, the plurality of disks can be classified and configured as RAID levels to protect and maintain user data even when an error occurs in each of the hard disks. The logical drives A1 to An are mutually different. It is possible to classify to the same RAID level, or even to different RAID levels.

As illustrated in FIG. 3, the RAID levels are divided into non-raid (NRAID), RAID 0, RAID 1, RAID 3, and RAID 5 according to the configuration, and the RAID levels are arranged in arrays. When data is read or written to a disk drive, the data can be divided into several blocks to improve the access speed of the disk.

The NRAID is the capacity of all the drives to be integrated into one logical drive, the capacity of the logical drive is the total capacity of the physical drive, and there is no data redundancy to protect data.

The RAID 0 is to distribute the data of the logical drive to multiple physical drives, and the performance is high, but the data is not protected due to lack of redundant functions, and the RAID 1 is executed only when there are only two hard drives. This can be done by copying data stored in one hard disk drive to another hard disk drive as it is, thereby preventing data loss in the event of a disk failure.

The RAID (0 + 1) is a combination of RAID 0 and RAID 1, and mirroring and stripping are possible, and RAID 3 distributes blocks using dedicated parity. The parity data is stored on a dedicated hard drive, and if a drive fails, data recovery can be performed by retrieving the lost data from the failed drive from the dedicated parity drive.

The RAID 5 may be executed when at least three hard disks are provided. An error occurs because the parity data is not stored in only one dedicated hard disk drive, but the parity information is distributed to an array of disks. In the event of multiple data recovery, data loss from other drives can be retrieved and used to increase the utilization of storage space.

In the HNAS 10, the RAID configuration may be changed according to the number of disks or the utilization rate of the disks, and may be configured as NRAID when the user does not want the RAID configuration or is composed of a single hard disk.

Meanwhile, the control point 60 allows the storage space of the HNAS 10 to be shared on a home network, and setting of a RAID level for a hard disk drive constituting the HNAS 10 includes knowledge of device configuration. Or default configuration is possible so that the basic configuration can be done automatically without the expert knowledge of the storage device.

In the present invention, a UPnP device service called "DiskUtility" is provided for setting a storage device. The storage service provides a setting service of a RAID configuration file system of a device, and this service type is defined as follows.

urn: schemas-upnp-org: service: diskutility: 1

In addition, the state variables of the device for such a disk storage service is shown in Figure 4, the state variables shown in Figure 4 are the number of disk arrays (NumArray), the number of disks (NumDisk), the capacity of the entire disk ( TotalDiskSize), Disk Index Value (DiskIndex), Number of Disk Partitions (Numpartition), Disk Capacity (DiskSize), Disk Remaining Capacity (RemainDiskSize), Disk Array Index Value (ArrayIndex), Number of Disk Array Devices ( ArrayNumDevice, RAID Level (RAIDLevel), Device Array (ArrayDevices), Disk Array Capacity (ArraySize), Disk Array Remaining Capacity (ArrayRemainSize), Disk Array Chunk Capacity (ArrayChunkSize), File System Type ( FSType), block size (BlcokSize), and result value (Result).

Next, FIGS. 5A to 5G are diagrams illustrating various GET actions for configuration and configuration of a storage device according to the present invention. In the control point 60, disk and RAID configuration information of the HNAS 10 through various GET actions. The various information of each disk, the setting state of each disk array, the size of the disk, the number of partitions, etc. can be checked.

First, in FIG. 5A, the GET action includes a system information action (GetSystemInfo), a disk information action (GetDiskInfo), a disk array information action (GetArrayInfo), a partition creation action (CreatePartition), a RAID creation action (CreateRAID), and a file system creation action ( CreateFileSystem), the system information action (GetSystemInfo) is shown in Figure 5b, the number of disk arrays (NumArray), the number of disks (NumDisk), the total disk capacity (TotalDiskSize), the resulting value (Result ) Has parameter information. The control point 60 can grasp the configuration information of the disk and RAID of the HNAS 10 and the overall disk capacity information through the parameter information of the system information action GetSystemInfo.

As shown in FIG. 5C, the disk information action GetDiskInfo may include a disk index value (DiskIndex), a number of partitions (Numpartition) of a disk, a disk size (DiskSize), a remaining capacity of a disk (RemainDiskSize), and a result value. (Result) has parameter information. If the control point 60 passes the index of the disk to which the information is to be obtained to the parameter of the disk index value (DiskIndex) through the disk information action (GetDiskInfo), the capacity of the corresponding disk. And the number of partitions currently configured and capacity information remaining.

As shown in FIG. 5D, the disk array information action GetArrayInfo may include an index value (ArrayIndex) of a disk array, a number of disk array devices (ArrayNumDevice), a RAID level (RAIDLevel), a device array (ArrayDevices), and a disk array. It contains the parameter information of capacity (ArraySize), remaining capacity of disk array (ArrayRemainSize), disk array chunk capacity (ArrayChunkSize), file system type (FSType) and result value (Result). At point 60, the disk array information action GetArrayInfo can be used to know the RAID level, the number of disks (partitions) constituting the disk array, and information on which partitions constitute the disk array.

As shown in FIG. 5E, the partition creation action (CreatePartition) has parameter information of a disk index value (DiskIndex), a partition size (PartitionSize) and a result value (Result), and the RAID creation action (CreateRAID) As shown in FIG. 5F, the index value (ArrayIndex) of the disk array, the number of disk array devices (ArrayNumDevice), the RAID level (RAIDLevel), the device array (ArrayDevices), and the capacity of the disk array (Chunk) capacity (ArrayChunkSize) It has parameter information of Result.

The file system create action CreateFileSystem has parameter information of a file system type (FSType), a block capacity (BlcokSize), and a result value (Result), as shown in FIG. 5G.

Next, FIG. 6 is a flowchart for explaining the operation of the disk information setting method of the storage device in the network according to the present invention, and FIG. 7 shows a more detailed description of the operation for the RAID configuration in the flowchart of FIG. 8 is a flowchart illustrating in more detail the user account registration and volume creation operations in the flowchart of FIG. 6.

Hereinafter, the flowchart according to the embodiment of the present invention shown in FIGS. 6 to 8 will be described in detail in parallel with the operation of the apparatus of FIG. 1.

First, when the HNAS 10 is driven, it periodically transmits a Simple Service Discovery Protocol (SSDP) Advertisement message indicating a file sharing service to the control point 60 according to the UPnP protocol (step S10), and the control point 60 In the SSDP message, the presence of the device of the HNAS 10 can be recognized (discovery) (step S11), and the HNAS 10 is registered in the system through the description of the HNAS service. The registration proceeds the setting work for the HNAS 10 (step S12).

However, the control point 60 enables service registration based on the recognition of the device through a search request command of the device without the periodic SSDP message from the HNAS 10.

Next, the control point 60 requests system configuration information of a device such as the total capacity size or number of hard disks installed in the HNAS 10 using the system information action GetSystemInfo as shown in FIG. 5B. (Step S13), the HNAS 10 provides the control point 60 with the system configuration information of the requested device (step S14).

Accordingly, the control point 60 obtains system configuration information of the device provided from the HNAS 10, that is, configuration information of disk and RAID, and capacity information of all disks (step S15).

Here, the control point 60 may request a RAID level to be configured according to the disk information, but if the disk is determined to be a single hard disk in the disk configuration information, or the user does not want to configure the RAID You may not request to configure the RAID level.

In addition, when the control point 60 requests the disk status information using the disk information action (GetDiskInfo) as shown in FIG. 5C (step S16), the HNAS 10 provides the requested disk status information. (Step S17).

Accordingly, the control point 10 can obtain the disk state information, that is, the capacity size of the disk, the number of partitions currently configured, and the remaining capacity information from the HNAS 60 (step S18). .

Then, when the control point 60 requests the information of the disk array using the disk array information action (GetArrayInfo) as shown in FIG. 5D (step S19), the HNAS 10 requests the disk array according to the request. Information on the RAID level, the number of disks (partitions) constituting the disk array, and the partitions constituting the array is provided (step S20).

Meanwhile, in the control point 60, after obtaining the disk configuration information from the HNAS 10 and determining the configuration of the device, it is necessary to perform the task of dividing each disk into logical partitions. As the partitioning operation is performed through the partition creation action (CreatePartition) as shown in FIG. 5E (step S21), the HNAS 10 divides each disk into one or a plurality of logical partitions (step S21). Step S22).

That is, the HNAS 10 divides each disk into partitions, but sets a disk index parameter value to an index of a desired disk, and calls a partition creation action (CreatePartition) to partition the desired disk. To be divided.

When the partitioning of the disk is completed, the control point 60 proceeds to configure RAID using a RAID creation action (CreateRAID) as shown in FIG. 5F (step S23), wherein the HNAS ( The desired RAID level is selected from the configurable RAID levels according to the hardware configuration information of the disk provided from 10).

The HNAS 10 can specify the size of the chunk required for RAID configuration (ie, the default value is generally 64 KB), and control the desired chunk size through the array chunk size parameter of the array. After passing to the pointer 60, when the RAID configuration is completed, the result is transferred to the control pointer 60 through the result parameter (Step S24).

When the RAID configuration is completed, the control point 60 performs a setting operation for building a file system on the device of the HNAS 10 using a file system create action (CreateFileSystem) as shown in FIG. 5G. (Step S25), the file system can be of various types such as " FAT16, FAT32, EXT2, EXT3, XFS ", etc., and can be predefined by the user or a default file system type can be defined at the control point 60.

The HNAS 10 receives the information of the selected file system through the file system create action (CreateFileSystem). The size information of the block required for the configuration of the file system is transmitted as a block size parameter, and the transferred file The file system configuration is performed using the type of system and the block size information, and the result of the execution is transmitted to the control point 60 through the result parameter (step S26).

Meanwhile, a detailed operation of the RAID configuration will be described in detail with reference to the flowchart of FIG. 5.

As illustrated in FIG. 5, the control point 60 determines whether a RAID configuration preset by the user exists (step S20). If it is determined that the RAID configuration preset by the user does not exist. It is determined whether the number of hard disks included in the HNAS 10 is two or more (step S21).

As a result of the determination, if it is determined that the number of hard disks included in the HNAS 10 is less than two, that is, one, the control point 60 proceeds with a request for configuring the corresponding RAID level as NRAID (step S60). S22).

However, if it is determined that the number of hard disks included in the HNAS 10 is two or more, it is determined whether the number of corresponding hard disks is three or more (step S23).

As a result of the determination, if it is determined that the number of hard disks included in the HNAS 10 is less than three, that is, two, the request for configuring the corresponding RAID level as RAID 1 is made (step S24). If it is determined that the number of hard disks is three or more, a request for configuring the RAID level to RAID 5 is made (step S25).

On the other hand, if it is determined in step S20 that the user-specified RAID exists, the control point 60 determines whether the user-set RAID is a RAID level suitable for the configuration of the hard disk currently provided in the HNAS 10. It is judged (step S26).

As a result of the determination, when the control point 60 determines that the user-configured RAID is not suitable for the current disk configuration, the control point 60 proceeds from step S21 to step S25 to determine the number of hard disks included in the corresponding HNAS 10. The appropriate RAID setup request will be performed.

On the other hand, if it is determined that the user-set RAID is suitable for the current disk configuration, a request is made to configure the RAID level with the setting value specified by the user (step S27).

Meanwhile, when the RAID level is set, an operation of setting a user account to be used for the storage space of the HNAS 10 and the amount of disk space to be allocated for each user is performed. It will be described in detail with reference to.

As illustrated in FIG. 6, the control point 60 determines whether a size of a user account and a disk volume to be allocated to each user is set in advance (step S30), which is assigned to the user account and the user. If it is determined that the size of the disk volume to be set is not set in advance, a default user is generated according to the basic user information predefined in the corresponding control point 60 (step S31), and the whole of the HNAS 10 is provided. By setting the hard disk as one volume (step S32), the operation of assigning the one volume to a default user is performed (step S33).

However, when it is determined in step S30 that the control point 60 determines that the size of the user account and the volume for each user is preset, the size of the volume allocated to the user is provided in the HNAS 10. It is judged whether or not it is properly set without exceeding the size of (step S34).

As a result of the determination, when it is determined that the size of the volume preset to the user does not exceed the size of the disk provided in the HNAS 10, the user setting is performed with the setting value of the preset volume size (S35), As the volume size is requested to the HNAS 10 (step S36), the user account and the volume are created (step S37).

On the other hand, the present invention is not limited to the above-described typical preferred embodiments, but can be carried out in various ways without departing from the gist of the present invention, various modifications, alterations, substitutions or additions are common in the art Those who have knowledge will easily understand. If the implementation by such improvement, change, replacement or addition falls within the scope of the appended claims, the technical idea should also be regarded as belonging to the present invention.

As described above, when using the HNAS for data sharing on the home network, the RAID level setting operation of the HNAS and the user without going through a complicated configuration process through a personal computer or a separate user interface device, By automatically assigning accounts and disk volumes, it is possible to easily set up HNAS data sharing without going through complicated configuration methods that require specialized knowledge.

Claims (12)

A method of network setting a home network storage device that provides a file sharing service for each device in a home network, the method comprising: A first step of recognizing and registering the home network storage device in a system in a control application of a home network; And a second step of performing user setting and disk setting by a setting request action for the home network storage device. The method of claim 1, In the first step, the home network storage device may combine a plurality of hard disk drives into an array to form a logical drive and a logical volume to form a home network attached storage (HNAS). The disk information setting method of the storage device on a network, characterized in that. The method according to claim 1 or 2, The second step may include requesting system information on an apparatus of the home network storage device and receiving corresponding system information. Requesting information of a disk provided in the home network storage device and receiving corresponding disk information; Requesting information of the disk array and receiving corresponding disk array information; Dividing a corresponding partition by requesting a partition configuration of the disk based on the system information, disk information, and disk array information; Requesting a configuration of a Redundant Arrays of Independent Disks (RAID) level based on the system information, disk information, and disk array information to set a corresponding RAID level; And setting a corresponding file system after requesting the construction of a file system for the home network storage device. The method of claim 3, wherein The system information of the home network storage device may be determined by a parameter of a GET action (GetSystemInfo) for identifying the disk and RAID configuration information of the device, the device information of each disk, and the setting status of the disk array. To set disk information of a storage device on a computer. The method of claim 3, wherein The disk information of the home network storage device may be determined by a parameter of a GET action (GetDiskInfo) for determining the size of the hard disk, the number of partitions configured on the disk, and remaining capacity information. How to Set Disk Information The method of claim 3, wherein The disk array information of the home network storage device may be checked by using a parameter of a GET action (GetArrayInfo) for identifying information about a RAID level, a disk constituting the array, the number of partitions, and information on a partition of the array. To set disk information of a storage device on a network. The method of claim 3, wherein The partitioning of the home network storage device may be performed by a parameter of a partition creation action (CreatePartition) for logically partitioning each disk partition. The method of claim 3, wherein The setting of the RAID level is performed by setting a chunk size required for RAID configuration and a parameter of a RAID create action (CreateRAID) for selecting a RAID level. Way. The method of claim 3, wherein The setting of the file system may include selecting a type of file system and performing a parameter of a file system create action (CreateFileSystem) for performing configuration through block size information. How to set up information. The method of claim 3, wherein The setting of the RAID level, the disk information setting method of the storage device on the network, characterized in that configured to default the RAID level according to the number of hard disks provided in the home network storage device. The method of claim 10, If the number of disks is one, the default RAID configuration is set to NRAID (Non-RAID). If the number of disks is two, the RAID configuration is set to RAID 1 by default. And setting the RAID configuration to RAID 5 by default if the number of disks is three or more. The method of claim 3, wherein In the setting of the RAID level, if a RAID configuration preset by a user exists, verifying whether the RAID configuration preset by the disk information is appropriate, and configured to set the RAID configuration to a predetermined setting value. To set disk information of a storage device on a network.

Images