Patent Grant
9158780
1. Field of the Invention
The present invention relates to an information storage device and an information service system.
2. Description of the Related Art
With the popularization of high-performance digital cameras, even individuals have possessed a large amount of shot image data. Moreover, a service for storing information files of a customer in a server on the Internet with or without charge has been widely rendered owing to speed-up of an information network.
In the meantime, also a service for offering a storage area of a certain capacity in a server on the Internet to a customer who purchased a commodity such as a camera, an IC recorder or the like and made a user registration has been emerged. Especially, in a case where a camera, an IC recorder or the like is provided with a wireless communication function, shot image data or recorded voice data can be recorded without limitation on a storage capacity of an included memory by directly transmitting the image data or the voice data to the server. Moreover, it becomes easy to also use the image data or the voice data for various types of services prepared in the server. Accordingly, a technique of transmitting information generated by a portable device to an information storage server via a communication, and of managing the information is proposed.
For example, Patent Document 1 describes a server device that includes storage means where first and second storage areas are set, stores a shot image transferred from an electronic camera in the first storage area before a user registration, and moves the image stored in the first area to the second storage area and stores the image in the second storage area after the user registration. Moreover, the second storage area of the server device described in Patent Document 1 is allocated according to the number of cameras.
[Patent Document 1] Japanese Laid-open Patent Publication No. 2008-204068
A first aspect of the present invention provides an information storage device for storing an information file of a registered member. The information storage device includes: a first storage unit configured to store an arbitrary information file transmitted from the registered member via a wide area information network; a second storage unit configured to store an information file in a predetermined form, which is derived from the information file stored in the first storage unit; an information file determination unit configured to determine whether or not the information file is the information file in the predetermined form; a file conversion unit configured to convert the information file into the information file in the predetermined form; and a storage management unit configured to manage the information file stored in the first storage unit, and the information file stored in the second storage unit, wherein the storage management unit converts a copy of the file stored in the first storage unit into the information file in the predetermined with the file conversion unit and stores the copy in the second storage unit if the information file determination unit determines that the copy is not in the predetermined form when the copy is stored in the second storage unit.
A second aspect of the present invention provides an information service system where an information storage device and an external device operated by a registered member are connected to a wide area information network, wherein: the information storage device includes a first storage unit configured to store an arbitrary information file transmitted from the external device via the wide area information network, a second storage unit configured to store an information file in a predetermined form, which is derived from the information file stored in the first storage unit, an information file determination unit configured to determine whether or not the information file is the information file in the predetermined form, a file conversion unit configured to convert the information file into the information file in the predetermined form, and a storage management unit configured to manage the information file stored in the first storage unit, and the information file stored in the second storage unit; the external device includes a storage medium for storing the information file, an information file selection unit configured to select the information file stored on the storage medium, and an information file transmission unit configured to transmit the information file selected by the information file selection unit to the information storage device via the wide area information network, wherein the storage management unit converts a copy of the information file stored in the first storage unit into the information file in the predetermined form with the file conversion unit and stores the copy in the second storage unit if the information file determination unit determines that the copy is not in the predetermined form when the copy is stored in the second storage unit.
According to an embodiment, two types of information storage servers are provided in an information storage device. The first server that offers a storage area with a charge to a member accepts an information file in an arbitrary form transmitted from the member, whereas the second server that offers a storage area with no charge accepts an information file in a predetermined form.
The information file stored in the second server is locally backed up, for example, in a local backup system within the same LAN, and the information file stored in the second server is locally backed up and also backed up in a geographically remote backup system via a wide area information network.
The information file stored in the second server can be edited by a person that possesses the information file, and can be shared with a third party. The information file stored in the first server cannot be shared with a third party, and is protected from being edited even by the person who possesses the information file.
When information data is transmitted from a terminal device and stored in the first server as an information file, the first server transmits deletion permission information for the information data to the terminal device side, so that the terminal device is enabled to delete the information data permitted to be deleted.
Additionally, if the information file stored in the first server is deleted by the terminal, information indicating that the file has been deleted is transmitted to the first server, and the information file stored in the second server is protected from being deleted with a normal deletion procedure.
Furthermore, a server at a storage destination of an information file can be set in advance for each terminal device.
Embodiments according to the present invention are described in detail below with reference to the drawings.
In the following description, identification information, a database, and an interface are respectively abbreviated to ID, DB, and I/F.
The information service system S1 according to this embodiment includes an information storage device 100 that accepts an access made from a network terminal 50 (external device) and a terminal device 300 (external device), which will be described later, via an information network.
The information storage device 100 according to this embodiment includes an information service server 103, and a first storage device 101 (first storage unit) and a second storage device 102 (second storage unit), which are connected to the information service server 103.
To the information storage device 100, a local backup system 200 (first backup storage device) is connected via a LAN (Local Area Network) 10.
The LAN 10 (local area information network) to which the information storage device 100 and the local backup system 200 are connected is connected to an upper-level Internet 30 (wide area information network) via a gateway 20.
To the Internet 30, a remote backup system 500 (second backup storage device) accessed by the information storage device 100, and a charging server 40 are connected.
To the Internet 30, also a network terminal 50 and a terminal device 300, which are possessed by a person who uses the information storage device 100, are connected.
The information service system S1 according to this embodiment renders a service for storing an information file transmitted by the network terminal 50 or the terminal device 300, which is possessed by a user, in the information storage device, or for releasing the information file.
In the case of this embodiment, a size of a storage area with no charge of an information file in the information storage device 100 is allocated, for example, according to a type or an attribute of the terminal device 300 or an accessory 400 registered by the user.
In the case of this embodiment, the terminal device 300 is, for example, a camera, and the accessory 400 is, for example, a replacement lens, a strobe or another accessory, which is attached/detached to/from the camera.
For a storage area with a charge in the information storage device 100, a size desired by a user is allocated according to a contract with the user.
The information storage device 100 according to this embodiment includes an information service server 103, and a first storage device 101 and a second storage device 102, which are connected to the information service server 103.
In the case of this embodiment, the first storage device 101 is a storage area for safely storing an information file possessed by a user, and offered to the user with a charge. For the storage area of the first storage device 101, a storage duration according to a charge is set.
The second storage device 102 is a utilization area used to store, share, or release an information file, and offered to a user with no charge.
The information service server 103 includes a processing unit 110 (storage management means), an external storage I/F 120, a network I/F 130 (communication means), a device information DB 140, a member management DB 150, a storage area management DB 160, and a sharing management DB 170.
The processing unit 110 is configured with a computer or the like, and implements various types of control functions illustrated in
The external storage I/F 120 controls an information input/output to/from the first storage device 101 and the second storage device 102.
The network I/F 130 controls an information input/output to/from the LAN 10.
In the case of this embodiment, the processing unit 110 includes a member registration function 110a, a member authentication function 110b, a file type determination function 110c, a charging processing function 110d, a file operation function 110e, a storage area setting function 110f, an image processing function 110g, a WEB page generation function 110h, a file backup function 110j, a device determination function 110k, and an electronic mail function 110m.
The member registration function 110a executes a process for registering a user who uses the information storage device 100 as a member as will be described later.
Additionally, the member registration function 110a in this embodiment extracts a storage area that has reached an expiry date within a storage area with a charge in the first storage device 101, makes a setting for extending the expiry date of the extracted storage area by a predetermined duration, and requests the charging processing function 110d to cause the charging server 40 for managing a settlement account of a member to whom the area that has reached the expiry date is allocated to charge a cost for extending the expiry date by the predetermined duration.
The member authentication function 110b executes a process for authenticating a member who uses the information storage device 100 as will be described later.
The file type determination function 110c executes a process for determining various types of attributes of an information file as will be described later.
The charging processing function 110d executes a process for charging a member in cooperation with the charging server 40 when a service with a charge is rendered as will be described later.
The file operation function 110e executes a process for implementing various types of operations for a file that is stored in the information storage device 100 as an information file as will be described later.
The storage area setting function 110f processes a control for allocating a storage area of an information file in the information storage device 100 as will be described later.
The image processing function 110g executes processes such as a process for reducing a size of an image file as will be described later.
The WEB page generation function 110h executes a process for releasing an information file stored in the information storage device 100, or for generating a home page intended to share the information file with another member.
The file backup function 110j executes a process for storing a copy of an information file stored in the information storage device 100 in the local backup system 200 or the remote backup system 500 as will be described later.
The device determination function 110k executes a process for determining a device type or an attribute of the terminal device 300 or the accessory 400.
The electronic mail function 110m transmits/receives e-mail to/from the network terminal 50 or the terminal device 300, which is possessed by a user, as will be described later.
The member management DB 150 is used to manage a user who is registered as a member.
The member management DB 150 according to this embodiment is configured to manage a member ID 151, personal information 152, a storage area ID 153, a utilization area ID 154, a storage area expiry 155, the number of registered devices 156, and a device serial number 157 by using the member ID 151 as a key.
The storage area ID 153 is information for identifying an area of the first storage device 101 allocated to the member.
The utilization area 154 is information for identifying an area of the second storage device 102 allocated to the member.
The storage area expiry 155 is information indicating a storage limit of an area identified with the storage area ID 153.
The number of registered devices 156 is information indicating the number of terminal devices 300 or accessories that the member registered as a user.
The device serial number 157 is information for identifying the terminal device 300 or the accessory 400, which is registered as a user.
The personal information 152 is composed of an e-mail address 152a, a name 152b, an address 152c, a telephone number 152d, a member registration date 152e, a charged account 152f, and a login password 152g.
As illustrated in
As illustrated in
The area ID 161 is information for identifying an allocated area in the second storage device 102.
The member ID 162 is information for identifying a member who possesses a storage area identified with the area ID 161.
The time limit 163 is information indicating an expiry date of the storage area identified with the area ID 161.
The area size 164 is information indicating a size of the storage area identified with the area ID 161.
The number of files 165 is information indicating the number of information files stored in the storage area identified with the area ID 161.
The file ID 166 is information for identifying individual information files stored in the storage area identified with the area ID 161.
The storage address 167 is information for identifying a storage position of an information file having the file ID 166 in the storage area identified with the area ID 161.
The file name 168 is a name of the information file identified with the file ID 166.
The file type 169 is information indicating a type (TIFF, JPEG, WAVE or the like) of the information file identified with the file ID 166.
The backup address 169a is information for identifying a position where a copy of the information file identified with the file ID 166 is stored. In this case, the copy of the information file in the second storage device 102 is stored in the local backup system 200. Therefore, the backup address 169a indicates a storage position in the local backup system 200.
In contrast, as illustrated in
Accordingly, the storage area management DB 160B in this embodiment is different from the utilization area management DB 160A in that backup addresses 2 to 3 (169b) indicating storage positions of copies of the information file respectively in the remote backup systems 500 at two sites are included in addition to the backup address 1 indicating the storage position of the copy of the information file in the local backup system 200, and a lock flag 166a is added. The lock flag 116a is a flag for controlling whether or not to prohibit a deletion operation of an information file identified with the file ID 166. For example, an information file is prohibited from being deleted if the lock flag 166a is set to “1”, or the information file is released from being deleted if the lock flag 166a is set to “0”.
The backup address 2 indicates a storage position of the copy of the information file in the remote backup system 500, and the backup address 3 indicates a storage position of the copy in another remote backup system not illustrated.
In the case of this embodiment, part of a storage area in the second storage device 102, which is allocated to a member (administrator), is set as a shared area so that members other than the member to whom the storage area is allocated can reference an information file. Therefore, an information file of the administrator, which is located in the shared area, can be referenced also by a member permitted by the administrator. The sharing management DB 170 is used to manage a shared area.
As illustrated in
The sharing management ID 171 is information for identifying each shared area in the second storage device 102.
The administrator ID 172 is information for identifying a member, who is an administrator of a shared area identified with the sharing management ID 171.
The shared area address 173 is information indicating a position in the shared area in the second storage device 102.
The sharing start date 174 and the sharing end date 175 are information respectively indicating sharing start date and time and sharing end date and time of the shared area.
The guest ID 176 is information for identifying a guest who is permitted to access the shared area identified with the shared area address 173. If the guest is a member, the guest ID 176 is a member ID 151 registered to the member management DB 150. If the guest is not a member, the guest ID 176 is an e-mail address that a user (administrator) inputs in step 757 of
The device information DB 140 is used to stipulate and manage an allocation amount of a storage area in the second storage device 102, which is allocated to a member, according to a type of a device such as the terminal device 300, the accessory 400 or the like possessed by the member.
As illustrated in
The device type ID 141 is information for identifying a device type of the terminal device 300 such as a camera or the like, and that of the accessory 400.
The device ID 142 is information indicating a range of identification numbers allocated to devices of a type identified with the device type ID 141.
The allocation size 143 is information indicating a size of a storage area in the second storage device 102, which is allocated with no charge, for each device identified with the device type ID 141 and the device ID 142.
The allocation start date 144 and the allocation end date 145 are information respectively indicating a date when a storage area starts to be allocated, and a date when the storage area ends to be allocated.
Configuration examples of the local backup system 200 and the remote backup system 500 for storing a copy of an information file stored in the information storage device 100 according to this embodiment are described next.
The local backup system 200 is provided within the same network as the information storage device 100, and connected to a shared LAN 10.
In the case of this embodiment, a copy of an information file stored with a charge in the first storage device 101 of the information storage device 100, and a copy of the information file stored with no charge in the second storage device 102 are stored in the local backup system 200.
In the meantime, the remote backup system 500 is installed in an area that is geographically remote from the information storage device 100, and connected to the information storage device 100 via the Internet 30, the gateway 20, and the LAN 10.
As illustrated in
The backup server 201 includes a processing unit 210, an external storage I/F 220, a network I/F 230, and a file backup management DB 240.
The processing unit 210 is configured with a computer or the like for controlling the whole of the backup server 201.
The external storage I/F 220 controls an information input/output to/from a subordinate storage device 202.
The network I/F 230 controls an information input/output to/from an information network such as the LAN 10 or the Internet 30.
The remote backup system 500 is the same as the local backup system 200 except that a database backup management DB 250 is provided in addition to the file backup management DB 240.
The file backup management DB 240 included in the local backup system 200 and the remote backup system 500 stores information such as a file ID 241, a file name 242, a member ID 243, an original storage address 244, a backup storage address 245, backup date and time 246, and the like.
The file ID 241 is information for identifying a stored information file, and corresponds to the above described file ID 166.
The file name 242 is the name of the information file, and corresponds to the file name 168 of the information file at a copy source.
The member ID 243 is information indicating a person who possesses the copy of the information file, and corresponds to the above described member ID 162.
The original storage address 244 is information indicating a storage position of the information file at the copy source in the first storage device 101.
The backup storage address 245 is information indicating a storage position of the copy of the information file in the local backup system 200 or the remote backup system 500.
The backup date and time 246 indicates date and time when the information file is copied from the first storage device 101 or the second storage device 102 and stored.
The database backup management DB 250 included in the remote backup system 500 stores a database ID 251, a file name 252, an original address 253, a backup address 254, and backup date and time.
The database ID 251 is information for identifying a copy of an archive of a database provided in the information storage device 100 where original information of an information file and the like are stored.
The file name 252 is information indicating a name of a copy of the database, the original address 253 is information indicating a position where a database at a copy source is located, the backup address 254 is information indicating a storage position of the copy of the database, and the backup date and time 255 is information indicating date and time when the database is copied and stored.
The original database of the information storage device 100 is identified with the database ID 251, and the storage position of the database in the information storage device 100 is identified with the original address 253.
Configuration examples of the network terminal 50, the terminal device 300, and the accessory 400 of a user who uses the information storage device 100 according to this embodiment are described next.
The network terminal 50 in this embodiment is configured, for example, with a personal computer.
Namely, in the network terminal 50, for example, a processing unit 51, a working memory 52, a hard disk 53, a communication I/F 54, a display unit 55, an operation unit 56, and a network I/F 57 are connected via an information transmission path 58, and mutually exchange information.
The processing unit 51 is, for example, a microprocessor. The working memory 52 is a main storage for storing a program executed by the processing unit 51, and data.
The hard disk 53 offers a nonvolatile storage area such as a program memory 53a, an image memory 53b, an information memory 53c, and the like.
The communication I/F 54 offers a connection function of communicating information with a terminal device 300 to be described later. Specifically, the communication I/F 54 is configured with a universal wired connection interface such as USB or the like, a near field wireless communication interface, an infrared communication interface or the like.
The display unit 55 is configured with a display for visualizing and displaying an information file.
The operation unit 56 offers a user input function such as a keyboard, a pointing device or the like.
The network I/F 57 offers a function of connecting to the LAN 10 or the Internet 30.
Namely, the network terminal 50 according to this embodiment can execute a process for extracting an information file such as an image file or the like from the terminal device 300 such as a camera or the like connected via the communication I/F 54, for storing the information file in the image memory 53b or the information memory 53c, and for transmitting the file to the information storage device 100 and making the information storage device 100 store the file as a replacement for the terminal device 300.
The terminal device 300 according to this embodiment is configured, for example, with a camera such as a digital camera, a video camera or the like, and generates an image file such as a still image, a voiced moving image, or the like as an information file.
Namely, as illustrated in
The image capturing unit 320 is composed of an image capturing element for shooting a still image or a moving image, and an optics system. The image processing unit 310 controls the image capturing unit 320, processes the still image or the moving image shot by the image capturing unit 320, and stores the image in the image memory 340 as an image file in a desired format.
The display unit 330 is a display for displaying an image of a subject shot by the image capturing unit 320 in real time, for displaying an index image of image data included in an image file stored in the image memory, and for further displaying various types of selection menus and operation information.
The controller 350 is configured with a microprocessor or the like that controls the whole of the terminal device 300. The controller 350 implements various types of controls to be described later by executing a program stored in the program memory 351.
The device ID memory 360 stores information such as a manufacturing number unique to the terminal device 300, a device type code and the like. Specifically, the above described device ID 142 and device type ID 141 are stored.
The accessory I/F 370 offers a function of connecting and communicating with the accessory 400.
The network I/F 380 offers a function of connecting to the Internet 30 wiredly or wirelessly. The communication I/F 390 offers a function of connecting to the communication I/F 54 of the network terminal 50 wiredly or wirelessly.
Namely, the terminal device 300 according to this embodiment is enabled to be used not only by being indirectly connected to the Internet 30 via the network terminal 50 but by being directly connected to the Internet 30 not via the network terminal 50. The image memory 340 stores an information file received via the network I/F 380 or the communication I/F 390 in addition to an image file. Moreover, the terminal device 300 has a WEB browser function in order to use a service rendered by the information service server 103 by accessing the information service server 103 via the Internet. A WEB page received via the communication I/F 390 is displayed on the display unit 330.
The accessory 400 in this embodiment is an accessory such as a replacement lens, a strobe or the like connected to a camera as the terminal device 300.
In the case of this embodiment, for example, if a service rendered by the information service server 103 is used by the terminal device 300 to which the accessory 400 is connected, the terminal device 300 transmits information for identifying the accessory 400 to the information service server 103 along with information for identifying the local terminal device 300.
If the service rendered by the information service server is a member registration, a storage area of an information file is offered with no charge in the second storage device 102 of the information storage device 100 according to the information for identifying the terminal device 300 or the information for identifying the accessory 400, which has been received by the information service server 103 simultaneously with the member registration. In the meantime, if the service rendered by the information service server is a service for a member, and if it is determined that the terminal device 300 or the accessory 400 is not registered as a user according to the information for identifying the terminal device 300 or the information for identifying the accessory 400, which has been received by the information service server 103, a user registration is made, and the storage area with no charge of the information file is expanded in the second storage device 102 of the information storage device 100 according to information for identifying the registered device.
A configuration example in a case where the accessory 400 is, for example, a strobe externally attached to the camera is described with reference to
The accessory 400 includes a controller 410, a light emission unit 420, a display unit 430, an operation unit 440, an accessory ID memory 450, a program memory 460, and an accessory I/F 470.
The controller 410 is configured, for example, with a microcomputer or the like, and controls the whole of the accessory 400. The light emission unit 420 is composed of components such as a lamp that emits light at timing and for a duration as instructed from the controller 410, and a capacitor for supplying an electric current to the lamp.
The display unit 430 is a display for visualizing and presenting an operation state of the accessory 400 to a user.
The operation unit 440 is configured with an information input mechanism, such as a switch, a dial, a button, a dip switch or the like, with which a user inputs control information to the controller 410.
The accessory ID memory 450 stores information such as a device type number, a manufacturing number, or the like, which is intended to identify the accessory 400. Specifically, information such as the above described device type ID 141, device ID 142, and the like are stored.
The program memory 460 stores information such as a control program to be executed by the controller 410.
The accessory I/F 470 offers a function of connecting to the accessory I/F 370 of the terminal device 300, and of communicating information.
One example of actions of the information storage device and the information service system according to this embodiment is described in detail below with reference to flowcharts. In the flowcharts described below, symbols A, B and C enclosed with a circle represent a connection relationship of the flowcharts separated into two figures.
The size of the utilization area allocated to a registered member differs depending on the device type ID or the device ID of the terminal device 300 or the accessory 400 identified by the information service server 103.
Once the member registration is started, the terminal device 300 initially accepts a selection of the member registration from a menu displayed on the display unit 55 (step 701).
Then, the terminal device 300 reads the device type ID 141 and the device ID 142 from the device ID memory 360 (step 702), and determines whether or not the accessory 400 is connected (step 703).
If the accessory 400 is connected, the terminal device 300 obtains the device type ID 141 and the device ID 142 of the accessory 400 (step 704).
Next, the terminal device 300 transmits a member registration request including the device type ID 141 and the device ID 142 of the local terminal device 300 and those of the accessory 400 to the information service server 103 of the information storage device 100 (step 705).
The information service server 103 receives the member registration request from the terminal device 300, and extracts the device type IDs 141 and the device IDs 142 (step 901).
Additionally, the information service server 103 determines whether or not any of the pairs of the extracted device type ID 141 and device ID 142 has been already registered to the member management DB 150 (step 902). If the pairs are not registered, the information service server 103 generates a member registration WEB page (step 903), and transmits the generated member registration WEB page to the terminal device 300 (step 904). Alternatively, if the determination in step 902 results in “YES”, the information service server 103 transmits, to the terminal device 300, information (member registration verification) for verifying that the member registration has been already made (step 904).
Upon receipt of the member registration WEB page or the member registration verification (step 706), the terminal device 300 determines whether or not the received data is a member registration verification (step 707). If the received data is not the member registration verification, the terminal device 300 displays the received member registration WEB page (step 708), accepts an input of personal information 152 from the user, and transmits the information to the information service server 103 (step 709). Alternatively, if the determination in step 707 results in “YES”, the terminal device 300 displays that the member registration has been already made. Here, the member registration process is completed.
The information service server 103 registers the received personal information to the member management DB 150 (step 905).
Additionally, the information service server 103 determines whether or not the terminal device 300 or the accessory 400 identified with the pair of the device type ID 141 and the device ID 142 is a device to which an area is to be allocated by referencing the device information DB 140 (step 906). If the terminal device 300 or the accessory 400 is a device to which an area is to be allocated, a utilization area of a size identified with the pair of the device type ID 141 and the device ID 142 is secured in the second storage device 102, and information for managing the secured utilization area is registered to the utilization area management DB 160A and the member management DB 150 (step 907).
The processes in the above described steps 906 to 907 are repeated for all pairs of the device type ID 141 and the device ID 142, which are extracted in step 901 (step 908), until registrations or area expansions are completed. If the utilization area has been already secured, it is expanded by the size identified with the pair of the device type ID 141 and the device ID 142, and information registered to the member management DB 150 and the utilization area management DB 160A is updated.
Thereafter, the information service server 103 generates a member ID 151, registers the ID to the member management DB 150 (step 909), and transmits the member ID to the terminal device 300 (step 910).
The terminal device 300 receives the member ID 151 from the information service server 103, and stores the member ID 151 in the device ID memory 360 of the terminal device 300 (step 710). Here, the member registration is completed.
If the terminal device 300 makes a connection to the information service server 103 via the Internet 30 after the member registration, it reads the member ID from the device ID memory 360 along with the device type ID and the device ID, includes the ID in a connection request, and transmits the request to the information service server 103.
In the flow of the member registration illustrated in
Additionally, the member registration may be made not by directly connecting the terminal device 300 to the Internet 30 but by using dedicated software that is installed in the network terminal 50 such as a personal computer or the like connected to the Internet 30. In this case, upon activation of the software dedicated to a member registration, whether or not the terminal device 300 is connected to the network terminal 50 is determined, and a device type ID and a device ID are read from the device ID memory of the terminal device 300 if the terminal device 300 is connected. If the accessory 400 is connected to the terminal device 300, a device type ID and a device ID of the accessory 400 are read from the accessory ID memory 450. Then, a member registration request including the device type ID and the device ID is transmitted to the information service server 103 similarly to step 705 of
The example represented by the flowchart illustrated in
Once the terminal device 300 starts to make a connection to the information service server 103 via the Internet 30, it initially reads the member ID 151 from the device ID memory (step 711), and transmits a connection request including the member ID 151 to the information service server 103 (step 712).
Upon receipt of the connection request (step 912), the information service server 103 determines whether or not the member ID 151 has been authenticated (step 913). The information service server 103 transmits, to the terminal device 300, a connection verification for verifying that a connection is permitted if the member ID 151 has been authenticated, or the information service server 103 transmits a non-connection verification to the terminal device 300 if the member ID 151 has not been authenticated (step 914).
Upon receipt of the connection verification or the non-connection verification (step 713), the terminal device 300 determines whether or not the member ID 151 has been successfully authenticated and the connection has been made (step 714).
If the connection has been successfully made, the terminal device 300 reads the device ID 142 of the local terminal device 300 (step 715). Moreover, if the accessory 400 is connected (step 716), the terminal device 300 obtains the device ID 142 of the accessory 400 (step 717), and transmits the obtained ID to the information service server 103 (step 718). The example of
The information service server 103 receives the device ID 142 from the terminal device 300 (step 915).
Then, the information service server 103 determines whether or not the device has been already registered to the member management DB 150 for each received device ID 142 (step 916). If the device has not been registered yet, the information service server 103 further determines whether or not the terminal device 300 or the accessory 400 identified with the device ID 142 is a target to which an area is to be allocated by referencing the device information DB 140 (step 917). If the determination results in “YES”, the area size 164 of the utilization area management DB 160A is updated to expand the utilization area of the member identified with the member ID by an allocation size 143 set by the device ID 142 (step 918), and registers the device ID 142 to the member management DB 150 (step 919). If the determination in step 917 results in “NO”, the information service server 103 executes step 919.
Alternatively, if the determination in step 916 results in “YES”, the device ID has been already registered. Therefore, the flow skips to step 920.
With the processes in steps 917 to 919, the information service server 103 registers all received device IDs 142, and determines whether or not a necessary expansion of a utilization area has been made (step 920). If the expansion of the utilization area has been made, the information service server 103 transmits a service acceptance start verification including a listing of services rendered by the information service server 103 to the terminal device 300 (step 921).
The terminal device 300 that has received the verification displays a service selection screen (step 719). Here, the device registration is completed.
As described above, each time the terminal device 300 directly makes a connection to the information service server 103 via the Internet 30 to use a service, the process illustrated in
In this case, the terminal device 300 obtains a condition for uploading the information file from the information service server 103 into a utilization area, converts the information file on the side of the terminal device 300 so that the condition is satisfied, and stores the file in a form of the information file, which satisfies the condition, in the information storage device 100.
The form of an information file in this embodiment indicates an attribute of information of the information file (a size, a format or the like of a file), and an attribute of information (a type, a compression method or the like of information) included in the information file.
The process example is described by assuming that the member ID authentication and the device registration process, which are described with reference to
When the terminal device 300 displays a service selection screen on the display unit 330 and accepts a selection of uploading the image (step 720), it displays a listing of index images of shot images included in image files stored in the image memory (step 721).
Then, the terminal device 300 accepts a selection of an index image (step 722), and a selection of an area at an uploading destination (step 723).
Next, the terminal device 300 determines whether the area at the uploading destination is either a storage area of the first storage device 101 or a utilization area of the second storage device 102 (step 724).
If the utilization area is selected, the terminal device 300 transmits an information file acceptance condition request to the information service server 103 (step 725).
Upon receipt of the information file acceptance condition request from the terminal device 300 (step 922), the information service server 103 returns an information file acceptance condition (step 923).
The terminal device 300 reads an image file corresponding to the index image (step 727) after it receives the information file acceptance condition from the information service server 103 (step 726).
Then, the terminal device 300 determines whether or not the image file satisfies the information file acceptance condition (step 728). If the image file does not satisfy the information file acceptance condition, the terminal device 300 converts the read image file into a form that satisfies the information file acceptance condition (step 729).
Additionally, if the uploading destination is the storage area in the above described step 724, or if the image file satisfies the acceptance condition in step 728, the terminal device 300 does not convert the file.
Thereafter, the terminal device 300 transmits area specification information and the image file to the information service server 103 (step 729a).
Upon receipt of the area specification information and the image file from the terminal device 300 (step 924), the information service server 103 generates a file ID for management (step 925), and stores the image file in the specified area (step 930).
Thereafter, the information service server 103 transmits the file ID to the terminal device 300 (step 941).
Upon receipt of the file ID (step 730), the terminal device 300 stores the file ID in the image memory 340 in association with the image file (step 731).
After all selected image files have been uploaded with the processes in the above described steps 724 to 731 (step 732), the image uploading is completed. If the determination in step 732 results in “NO”, the processes in steps 724 to 731 are repeated for an image file that has been not been updated despite being selected.
The process of
Namely, this backup operation is an operation performed when the remote backup system 500 is installed geographically remote from the information storage device 100 and the local backup system 200.
After the information service server 103 has received area specification information and an image file (step 924) and generates a file ID for management (step 925), it initially determines whether or not the specified area is a storage area (step 931).
If the specified area is a storage area, the information service server 103 stores the image file and the file ID in an area identified with the member ID 151 of the first storage device 101 (step 932).
Additionally, the information service server 103 stores a copy of the image file and that of the file ID also in the local backup system 200 installed within the same site as the information service server 103 (step 933).
Furthermore, the information service server 103 stores a copy of the image file and that of the file ID in the remote backup system 500 installed at a remote site different from the information service server 103 (step 934).
In contrast, if the information service server 103 determines that the specified area is not a storage area (utilization area) in step 931, it stores the image file and the file ID in an area identified with the member ID 151 in the second storage device 102 (step 935), and further stores a copy of the image file and that of the file ID in the local backup system 200 installed within the same site as the information service server 103 (step 936).
Thereafter, the information service server 103 transmits the file ID to the terminal device 300 (step 941).
In the local backup system, not only copies of information files but those of information of various types of databases of the information service system according to this embodiment are stored. Also a copy of information of the member management DB 150 and that of information of the storage area management DB 160B for managing an information file stored in the first storage device are stored in the remote backup system 500 at predetermined time intervals.
As described above, if a specified destination of an information file is a storage area, a copy of an information file is stored in a local backup server that is installed at a close distance, and also a copy of the information file is stored in a remote backup server installed at a remote distance (for example, in another continent). As a result, the remote backup server is not affected even if a large-scale disaster occurs, and the information file deposited by a member can be safely stored.
Namely, the example where an information file on the side of the terminal device 300 is deleted in synchronization with the storage of the information file by the terminal device 300 in the information storage device 100 in the information service system according to this embodiment is described.
In this case, a storage destination is set by the information service server 103, the image file of the image shot by the camera is stored in the image memory 340 when the image is shot, and the image file is transmitted to the information service server 103 and stored at a storage destination specified with the setting of the storage destination.
If the storage destination is a utilization area of the second storage device 102, the image file is converted so that a storable file condition is satisfied, and the converted file is stored. If the storage destination is a storage area of the first storage device 101, the image file is stored unchanged. When it is verified on the side of the camera (the terminal device 300) that the image file has been stored in the storage area of the first storage device 101, the shot image within the image memory 340 is deleted, and an index image corresponding to the deleted shot image, and the file ID for identifying the image file stored in the storage area are stored.
After the series of processes in
When a user selects a server setting, the terminal device 300 transmits a server setting request to the information service server 103 (step 734).
Upon receipt of the server setting request from the terminal device 300 (step 942), the information service server 103 returns a WEB page for the server setting (step 943).
The terminal device 300 displays the server setting WEB page received from the information service server 103 on the monitor, and makes a user select a server (step 735).
Additionally, the terminal device 300 transmits information of a file storage destination area specified by the user to the information service server 103 (step 736).
The information service server 103 registers the received specified destination area as a storage destination area to the member management DB 150 in association with a device ID for identifying the camera (step 944). A character A in the last digit of the device serial number in
After step 736, the terminal device 300 shoots an image (step 737), generates an image file including the shot image (step 738), stores the image file in the image memory 340, and transmits the image file and a device ID to the information service server 103 (step 739).
Upon receipt of the image file and the device ID (step 945), the information service server 103 determines whether or not the storage destination is a utilization area by referencing the member management DB 150 (step 946).
If the information service server 103 determines that the storage destination is a utilization area, it further determines whether or not the image file satisfies a file storage condition (step 947). If the image file does not satisfy the file storage condition, the information service server 103 converts the image file into a form that satisfies the file storage condition (step 948).
Thereafter, the information service server 103 generates a file ID for management (step 949), stores the converted image file in the specified area (step 950), and transmits the file ID and storage destination area information to the terminal device 300 (step 951). In contrast, if the determination in step 946 results in “NO” and if the determination in step 947 results in “YES”, the flow skips to step 949, in which the information service server 103 generates a file ID for management, and stores the image file received in step 950 in the specified area.
Upon receipt of the file ID and the storage destination area information (step 740), the terminal device 300 determines whether or not the storage destination is a storage area (step 741).
If the terminal device 300 determines that the storage destination is a storage area, it generates an index image from the shot image of the image file stored in the image memory 340 (step 742), stores an image file of the index image in the image memory 340 in association with the file ID (step 743), and deletes the image file including the shot image from the image memory 340 (step 744).
If the terminal device 300 determines that the storage destination is not a storage area (utilization are) in step 741, the terminal device 300 stores the image file in the image memory in association with the file ID (step 745).
Thereafter, the terminal device 300 determines whether or not to continue shooting (step 746). If the terminal device 300 determines that the shooting is to be continued, it repeats the above described processes in and after step 737. If the terminal device 300 determines that the shooting is to be terminated, the image uploading is completed.
In the above description, the terminal device 300 is identified with the device ID. However, the terminal device 300 may be identified with a pair of a device type ID and a device ID. In this case, also a device type name is registered to the member management DB 150.
An example where a process for applying a prohibition lock to a deletion operation of an information file uploaded into a storage area (second storage device 102) is added in the process, illustrated in
In
After the terminal device 300 has received a file ID 166 of image data stored in the storage area (the first storage device 101) and area information (storage address 167) of a storage destination from the information service server 103, and has deleted an image file including a corresponding shot image from the image memory 340 (steps 740 to 744), it transmits the file ID 166 and the storage address 167 of the deleted image file to the information service server 103 (step 744a).
Upon receipt of the file ID 166 and the storage address 167 (step 951a), the information service server 103 applies a deletion prohibition lock to the image file by setting a lock flag 166a of the image file corresponding to the file ID 166 in the storage area management DB 160B to “1” (step 951b), and transmits a lock verification to the terminal device 300 (step 951c).
The deletion prohibition applied in step 951b in the information service server 103 means that even a member who possesses an information file cannot delete the information file, for example, with a normal procedure in this embodiment illustrated in
Upon receipt of the lock verification of the image file deleted from the image memory 340 in step 744 from the information service server 103 (step 744b), the terminal device 300 determines whether or not to continue the shooting (step 746). If the terminal device 300 determines that the shooting is to be continued, the flow returns to step 737 of
As described above, in the case of this embodiment, an information file such as an image file or the like that is shot on the side of the terminal device 300 and stored in the first storage device 101, which is the storage area of the information storage device, is locked to be not deleted with the normal procedure at timing when the information file is deleted on the side of the terminal device 300. As a result, the information file of a user, which is stored in the first storage device 101, can be more securely protected.
In the information service system according to this embodiment, an information file safely stored in the first storage device 101 of the information storage device 100 cannot be directly used for a service rendered by the information service server 103. To use the information file safely stored in the first storage device 101 for the service rendered by the information service server 103, the information file stored in the first storage device 101 needs to be copied to the second storage device 102.
If an image file is copied from the first storage device 101 to the second storage device 102 in the information storage device 100, the terminal device 300 transmits an image file copy request to the information service server 103 (step 748) upon acceptance of an image file copy service selected by a user (step 747) on a service selection screen displayed on the display unit 330 after the series of processes illustrated in
Upon receipt of the image file copy request, the information service server 103 transmits a listing of index images of images included in image files stored in the storage area (the first storage device 101) to the terminal device 300 (step 953).
The terminal device 300 displays the received listing of index images on the display unit 330, makes a user select any of the index images (step 749), and transmits information for specifying the index image selected by the user to the information service server 103 (step 750).
Upon receipt of the information for specifying the index image (step 954), the information service server 103 identifies the image file stored in the storage area with the information for specifying the index image (step 955), and makes a copy of the identified image file (step 956).
Next, the information service server 103 determines whether or not the generated copy of the image file satisfies a file storage condition of a utilization area (the first storage device 101) (step 957).
If the copy does not satisfy the condition, the information service server 103 converts the copied image file into a form that satisfies the file storage condition of the utilization area, and stores the image file in the utilization area (step 958). If the copy satisfies the condition, the information service server 103 stores the copy of the image file in the utilization area unchanged (step 959).
Upon completion of copying image files corresponding all specified index images (step 960), the information service server 103 transmits a copy completion to the terminal device 300 (step 961).
The terminal device 300 that has received the copy completion displays that the image files have been copied (step 751), and terminates the copies of the image files.
One example of a method for sharing an information file among members of an information sharing group that can include a non-member in addition to members registered to the information service system according to this embodiment is described next with reference to
After the series of processes illustrated in
Upon receipt of the image sharing request (step 962), the information service server 103 transmits, to the terminal device 300, a listing of index images of images included in image files stored in a utilization area (the second storage device 102) (step 963).
The terminal device 300 makes a user select an index image by displaying the received listing of index images on the display unit 330 (step 754), and transmits information for specifying the index image selected by the user to the information service server 103 (step 755).
Upon receipt of the information for specifying the index image (step 964), the information service server 103 generates a WEB page for sharing (step 965).
Thereafter, the information service server 103 identifies the image file to be shared based on the received information for specifying the index image (step 966), generates a reduced image of the image included in the identified image file, arranges the generated image on the WEB page for sharing, and places a link from the reduced image to the image file (step 967).
Then, the information service server 103 verifies whether or not links have been placed from reduced images arranged on the WEB page to all specified image files (step 968), and repeats steps 966 and 967 until links have been placed to all the specified image files. Upon completion of placing the links to all the specified image files, the information service server 103 generates a WEB page for inputting a member of the information sharing group, and transmits the WEB page to the terminal device 300 (step 969).
The terminal device 300 receives the WEB page for inputting a member of the information sharing group, displays the WEB page on the display unit 330 (step 756), and accepts an input of an e-mail address or a member ID 151 of a member of the information sharing group (step 757).
The terminal device 300 transmits information (member ID 151 and e-mail address) for specifying the input information sharing group member to the information service server 103 (step 758).
Upon receipt of the information for specifying the information sharing group member from the terminal device 300 (step 970), the information service server 103 determines whether or not the information for specifying the member is a member ID 151 (step 971). If the information for specifying the member is the member ID 151, the information service server 103 obtains an e-mail address by referencing the member management DB 150 (step 972), creates e-mail for notifying the member of the sharing, and transmits the e-mail to the member of the information sharing group (step 973). Alternatively, if the determination in step 971 results in “NO”, namely, if the information for specifying the member is an e-mail address, the information service server 103 creates e-mail for notifying the member of the sharing after it registers the e-mail address to the sharing management DB 170, and transmits the e-mail to the member of the information sharing group (step 973).
The processes in steps 971 to 973 are repeated for all the members of the information sharing group specified by the information received from the terminal device 300 (step 974).
Thereafter, the information service server 103 releases the WEB page for sharing via the Internet 30 (step 975), and transmits, to the terminal device 300, information for verifying that the WEB page for sharing has been released (step 976).
The terminal device 300 receives the information for verifying that the WEB page for sharing has been released from the information service server 103, and displays the WEB page on the display unit 330 (step 759). Here, the information file sharing process is completed.
One example of an operation for deleting an information file stored in the information storage device 100 by the terminal device 300 in the information service system according to this embodiment is described next.
The network terminal 50 activates a WEB browser when an image file (information file) starts to be deleted (step 760), reads a member ID 151 from the terminal device 300 connected to the network terminal 50 (step 761), and transmits a connection request including the read member ID 151 to the information service server 103 (step 762).
The information service server 103 generates a WEB page for displaying a listing of services rendered by the information service server 103, and transmits the listing to the network terminal 50 (step 979) after it has received the connection request and authenticated the member ID 151 (step 978).
The network terminal 50 displays the WEB page received from the information service server 103 on the display unit 330 (step 763), detects that an image file deletion has been selected by a user on the WEB page (step 764), and transmits a service request command including information for specifying the image file deletion to the information service server 103 (step 764a).
The information service server 103 receives the service request command including the information for specifying the image file deletion (step 980), generates a deletion target listing WEB page on which a listing of index images of images included in image files stored in the storage area (the first storage device 101) and the utilization area (the second storage device 102) are displayed, and transmits the WEB page to the network terminal 50 (step 981).
The network terminal 50 displays the deletion target listing WEB page received from the information service server 103 on the display unit 330 (step 764b), and accepts a selection of an index image displayed on the WEB page by the user (step 764c).
Then, the network terminal 50 transmits a deletion command including information for specifying the index image selected by the user to the information service server 103 (step 764d).
Upon receipt of the deletion command from the network terminal 50 (step 982), the information service server 103 determines whether or not the received information for specifying the index image corresponds to an image file stored in the storage area (step 983). If the information corresponds to the image file stored in the storage area, the information service server 103 further determines whether or not the image file is locked (namely, whether or not the lock flag 166a is set) (step 984).
If the image file is locked, the information service server 103 generates a WEB page for notifying that the image file desired to be deleted is locked, and transmits the WEB page to the network terminal 50 (step 985).
Alternatively, if the information service server 103 determines that the information does not correspond to the image file stored in the storage area in step 983, or if the information service server 103 determines that the file is not locked in step 984, it deletes the image file specified by the network terminal 50 (step 986).
Then, the information service server 103 determines whether or not the processes in steps 983 to 986 have been completed for all image files identified with the information for specifying an index image, which is included in the deletion command received from the network terminal 50 (step 986a).
If the processes have not been completed, the information service server 103 repeats the processes in steps 983 to 986a. If the processes have been completed, the information service server 103 generates a WEB page for verifying that the image files have been deleted, and transmits the WEB page to the network terminal 50 (step 986b).
The network terminal 50 displays the WEB page received from the information service server 103 in the above described step 985 or 986b (step 764e). Here, the deletions of the image files are completed.
As described above, in this embodiment, if the lock flag 166a is set for an information file such as an image file stored in the storage area (the first storage device 101), even a person who possesses the information file cannot delete the file. Therefore, the information file is securely protected.
One example of a process for downloading an information file stored in the information storage device 100 into the terminal device 300 of a user is described next.
When the image file starts to be downloaded, the terminal device 300 transmits a connection request including a member ID 151 to the information service server 103 of the information storage device 100 (step 766).
After the information service server 103 has received the connection request and authenticated the member ID 151 (step 987), it generates a WEB page on which a listing of index images of image files stored in the storage area (the first storage device 101) and a utilization area (the second storage device 102) is displayed, and transmits the WEB page to the terminal device 300 (step 988).
The terminal device 300 displays the WEB page received from the information service server 103 on the display unit 330 (step 767), makes a user select an index image on the WEB page, and accepts downloading of a selected index image (step 768).
The terminal device 300 transmits a downloading request including information for specifying the selected index image to the information service server 103 (step 769).
Upon receipt of the downloading request from the terminal device 300 (step 989), the information service server 103 transmits an image file identified with the information for specifying the index image to the terminal device 300 (step 990).
Thereafter, the information service server 103 determines whether or not the image file transmitted to the terminal device 300 in step 990 is a file that is stored in the storage area (the first storage device 101) and locked to be prohibited from being deleted (step 991).
If the image file is a locked file, the information service server 103 sets the lock flag 166a to “0”, and releases the lock of the file prohibited from being deleted (step 992).
Thereafter, the information service server 103 determines whether or not all image files specified by the deletion request received from the terminal device 300 have been downloaded (step 993), and repeats steps 990 to 992 until all the image files have been downloaded.
If the information service server 103 determines that all the specified files have been downloaded in step 993, it generates a page for verifying that the image files have been downloaded, and transmits the page to the terminal device 300 (step 994).
The terminal device 300 receives the image file from the information service server 103 in the above described step 990 (step 770), and stores the received image file in the image memory (step 771).
Additionally, the terminal device 300 receives the WEB page transmitted from the information service server 103 in step 994, and displays the WEB page on the display unit 330 (step 772). Here, the downloading of the image files is completed.
As described above, in the case of this embodiment, the information service server 103 of the information storage device 100 enables an information file such as an image file or the like stored in the storage area (the first storage device 101) to be deleted by releasing the lock flag 166a after the information file has been downloaded into the terminal device 300. Therefore, even if the information file on the side of the information storage device 100 is deleted, a copy of the deleted information file is present on the side of the terminal device 300. Therefore, the information file can be securely prevented from being lost, for example, with an erroneous deletion operation or the like.
Namely, the reliability of storage of an information file in the terminal device 300 is improved.
In the information service system S2 illustrated in
In the case of this embodiment illustrated in
The information storage device 100A, the local backup system 200A, the gateway 20A, and the LAN 10A respectively have configurations equivalent to the information storage device 100, the local backup system 200, the gateway 20, and the LAN 10.
In the case of the embodiment illustrated in
Similarly, the local backup system 200A of the information storage device 100A includes both the above described file backup management DB 240 and database backup management DB 250, and also functions as a remote backup system 500 of the information storage device 100.
Namely, in the case of this embodiment illustrated in
In the case of this embodiment illustrated in
Accordingly, the network terminal 50 and the terminal device 300 according to this embodiment are provided with a function of making a user select either of the information storage device 100 and the information storage device 100A.
This embodiment illustrated in
The embodiments of the present invention can provide a technique of safely storing an information file of original image data or the like deposited from a user, and of making diverse services using an information file easily available.
The present invention is not limited to the configurations referred to in the above described embodiments, and can be diversely modified within a scope that does not depart from the gist of the invention as a matter of course.
This is a Continuation application of PCT Application No. PCT/JP2010/59980, filed on Jun. 11, 2010, which was not published under PCT Article 21(2) in English.
| Number | Name | Date | Kind |
|---|---|---|---|
| 20020035576 | Kishimoto et al. | Mar 2002 | A1 |
| 20030149731 | Ohwa | Aug 2003 | A1 |
| 20090025086 | Fujita et al. | Jan 2009 | A1 |
| 20100049810 | Maeda | Feb 2010 | A1 |
| Number | Date | Country |
|---|---|---|
| 2001197473 | Jul 2001 | JP |
| 2002082887 | Mar 2002 | JP |
| 2002116988 | Apr 2002 | JP |
| 2003216557 | Jul 2003 | JP |
| 2003242080 | Aug 2003 | JP |
| 2005148796 | Jun 2005 | JP |
| 2006202012 | Aug 2006 | JP |
| 2008204068 | Sep 2008 | JP |
| 2008102770 | Aug 2008 | WO |
| Entry |
|---|
| International Search Report of International Application No. PCT/JP2010/059980 dated Jul. 20, 2010 consisting of 2 pages. |
| Notice of Rejection Grounds issued on Aug. 6, 2013 in corresponding Japanese Patent Application No. 2012-519197 consisting of 7 pages including partial English translation. |
| Notice of Rejection issued in corresponding Chinese Patent Application No. 201080067266.8 on Oct. 21, 2014, consisting of 23 pp. (English translation provided). |
| Number | Date | Country | |
|---|---|---|---|
| 20130097072 A1 | Apr 2013 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | PCT/JP2010/059980 | Jun 2010 | US |
| Child | 13693546 | US |
