The present invention relates to a data sharing system, a shared data management apparatus, and a control method of the shared data management apparatus.
At present, in a service for allowing users to acquire data stored on a network, the user access a server with a communication terminal and requests a data acquisition. An example of such a service is disclosed in Patent Document 1. In the invention disclosed in Patent Document 1, monitoring data acquired by a monitoring device is transmitted to a supervisory computer. IDs are given to the monitoring device such as a monitoring camera and users beforehand. The supervisory computer decides the correspondence between the user ID and the monitoring device ID in accordance with the user's access. When they match, the monitoring data is provided to the user over the Internet.
In such a conventional technique, however, each user has to make an access and request data stored in the supervisory computer. For this reason, when the data is delivered to lots of users, lots of users access a server apparatus of the supervisory computer. Lots of accesses cause a problem in that the traffic volume of radio communication is increased and simultaneously the load applied onto the server apparatus is increased.
The present invention has been made in view of the above circumstances, and an object of the present invention is to provide a data sharing system, a shared data management apparatus, and a control method of the shared data management apparatus, whereby in a case where multiple users share data, the traffic amount of radio communication is reduced to alleviate the load applied onto the management side of the system, and in addition, only a prescribed user is allowed to share data in an efficient manner.
In order to solve the above problem, there is provided a data sharing system as recited in claim 1 of the present invention comprising: a plurality of data storage units (for example, DBs 104a to 104d illustrated in
a group processing unit (for example, a group processing unit 202 illustrated in
A shared data management apparatus, as recited in claim 2, for managing data sharing stored in a plurality of data storage units connected to each other via a radio access network, the shared data management apparatus comprising: an attribute information management unit for managing attribute information on a user who can make a request of the sharing of the data; a group processing unit for creating a user group including a plurality of users based upon the attribute information managed by the attribute information management unit; an authority information management unit for managing authority information on an authority for permitting a user included in the user group to share the data stored in the plurality of data storage units; a user group identifying unit for identifying the user group permitted to share the data stored in any of the plurality of data storage units based upon the authority information; and a data sharing process unit for storing the data stored in a data storage unit owned by the user belonging to the user group identified by the user group identifying unit. With such an invention, it is possible to share the data on the radio access network in the plurality of data storage units owned by the respective users belonging to the user group. Additionally, in this situation, the data can be delivered to multiple users from the shared data management apparatus, whereby the traffic amount of the radio communication can be reduced and the load on the system administration side can be reduced more than a case where each of multiple users accesses the shared data management apparatus to request the data sharing. Furthermore, such a delivery is made according to the authority information, whereby it is possible to provide a data sharing system of permitting only a prescribed user to share the data in an effective manner.
In the shared data management apparatus, as recited in claim 3, according to the invention of claim 2, when the user belongs to a plurality of user groups, the user group identifying unit may identify one user group, to which the data sharing is permitted, from the plurality of user groups, and the data sharing process unit may store the data on a data storage unit owned by said one user group identified by the user identifying unit. With such an invention, even in a case where a single user belongs to multiple user groups, the authority of the data sharing by the user group is made clear to prevent unintended data sharing.
In the shared data management apparatus, as recited in claim 4, according to the invention of claim 2 or claim 3, the sharing authority management unit may manage the authority relating to at least one of a data type permitted to share and a period while the sharing of the data is permitted, for each of the users and the user groups. With such a configuration, the authority for sharing the data can be set by the type of data such as sound or image or the period. Accordingly, it is possible to set more detailed conditions to permit or deny the data sharing.
In the shared data management apparatus, as recited in claim 5, according to the invention of any one of claim 2 to claim 4, the group processing unit may create the user group based upon at least one of attribute information on the individual user, current location information, and a data content shared in the past. With such a configuration, it is made possible to deliver to multiple users who have the same attribute the data suited to the attribute. Additionally, it is made possible to deliver to multiple users who are in a prescribed range the data necessary for staying in the prescribed range.
Furthermore, it is made possible to deliver to multiple users who have the same preference the data in accordance with the preference.
A control method of a shared data management apparatus, as recited in claim 6, for managing sharing of data stored in a plurality of data storage units connected to each other via a radio access network, the control method comprising: an attribute information acquiring step of acquiring attribute information on a user who can make a request of the sharing of the data; a grouping process step of creating a user group including a plurality of the users based upon the attribute information acquired by the attribute information acquiring step; an authority information acquiring step of acquiring authority information on an authority for permitting the user included in the user group to share the data stored in the plurality of data storage units; a user group identifying step of identifying the user group permitted to share the data stored in any of the plurality of data storage units based upon the authority information; and a data sharing process step of storing the data stored in a data storage unit owned by the user belonging to the user group identified by the user group identifying step. With such an invention, it is possible to share the data on the radio access network in the plurality of data storage units owned by the respective users belonging to the user group. Additionally, in this situation, the data can be delivered to multiple users from the shared data management apparatus, whereby the traffic amount of the radio communication can be reduced and the load on the system administration side can be reduced more than a case where each of multiple users accesses the shared data management apparatus to request the data sharing. Furthermore, such a delivery is made according to the authority information, whereby it is possible to provide a data sharing system of permitting only a prescribed user to share the data in an effective manner.
According to the present invention, it is possible to share a recorded message of a voice mail, melody data, video data, or text data informing an incoming call of a mobile telephone or the like between multiple data storing units owned by respective users belonging to a user group. In addition, in this process, it is possible for the shared data management unit to deliver data to multiple users.
This makes it possible to reduce the traffic amount on the radio communication and alleviate the load applied onto the system management side more than a case where each of multiple users accesses the shared data management apparatus to request the data sharing. Moreover, authority information is managed and the data sharing is limited by the authority information. It is therefore possible to allow only the users who have the proper right to share the data in an efficient manner.
Hereinafter, a description will be given of a data sharing system, a shared data management apparatus included in this system, and a control method of the shared data management apparatus.
(Outline of System)
As illustrated, the data sharing system according to the present embodiment includes: multiple databases (hereinafter, referred to as DBs) 104a, 104b, and 104c; a shared data management server 100 for managing users who share data stored in the DBs 104a to 104c and transmitting data to a user who is to share the data; and communication terminal devices each for transmitting the data to the shared data management server 100 to store the data in the DBs 104a to 104c, and receiving the delivered data that have been stored.
As the communication terminal devices, for instance, mobile telephones 103a, 103b, 103c, and 103d are used. The mobile telephones 103a to 103d are connected to a network NW through mobile telephone networks, not illustrated, or base stations 101. Specifically, the network NW is a network with an extended function of enabling both of Personal Computers (PCs) and the mobile telephones 103a to 103d to receive identical services.
Moreover, in an embodiment of the present invention, the communication terminal devices are not limited to mobile telephones and may be applicable to a case where PCs are used as the communication terminal devices.
The DBs 104a to 104d are owned by any of the users, respectively. Data is stored in the DBs 104a to 104d by corresponding users, respectively. The data to be stored include image data, sound data, text data, and program data.
The shared data management server 100 sets users who share the data beforehand, and makes the data stored in the DB shared in accordance with the setting. In addition, “sharing” means that the shared data management server 100 stores the data requested to be shared the data requested to be shared in the DB of a user who requested the data sharing. Furthermore, herein, such a process is referred to as sharing process.
Moreover, for example, coping the data requested to be shared and distributing the data in Push distribution or the like, to the DB of the user who requested the sharing, whereby the shared data management server 100 stores the data.
In addition, in the present embodiment, it is assumed that users create a group. In the description hereinafter, this group will be referred to as “user group”. In the user group, the data sharing is permitted. Specifically, the data sharing may be permitted only when each of users who belong to a user group makes an approval, or may be permitted automatically to all of the users who can share the data (in other words, without approval).
(Configuration of Data Management Server)
1 Profile Group Management Unit
In addition, in the data sharing system according to the present embodiment, the profile information includes user groups to which the users belong.
A user is not limited to belong to a single user group, and may belong to multiple user groups.
In
Furthermore, the DB owned by the user A stores text data 303, video data 304, audio data 305, and program data 306.
Moreover, the profile information further includes personal information such as a user's name, age, address, or profession, and attribute information such as an International Mobile Subscriber Identity (IMSI) or telephone number.
In the data sharing system according to the present embodiment, location information of a user may be detected by use of Global Positioning System (GPS) or the like and the detected location may be stored as the profile information. Additionally, By applying information that the user likes to acquire or preference at the time of making a contract of the data sharing system, the information that the user desires to acquire or the like is included in the profile information. Such information can be used for automatic grouping to be described later.
Furthermore, although not illustrated, the profile information is assumed to include information identifying the DB owned by a user and names of data stored in the IDE. The information identifying the DB owned by a user and names of data stored in the DB are opened to another user as necessary. Another user requests the data sharing by use of such information.
2 Sharing Policy Management Unit
In the illustrated example, the user B permits a user group Gb to share melody data and video data, but does not permit the user group Gb to share voice mail data. In addition, as to the data permitted to share, since the shared method is set to “manual”, only the data manually selected by a user who belongs to the user group Gb is shared out of the data that can be shared. Furthermore, since the period of time for sharing is set from August 9 to October 7, the melody data and the image data are permitted to be shared with the user group Gb from August 9 to October 7.
Moreover, in the present embodiment, not only the user group but also an individual user can be permitted to share the data. In the illustrated example, this user permits a user E to share the melody data only, but does not permit the voice mail data or the video data. The period of time for sharing the melody data is unlimited from August 11, so the sharing is permitted from August 11 or later with no time limit. Specifically, since the sharing method is set to “manual/automatic”, the melody data that can be shared may be acquired either manually or automatically.
The user A clicks a button of “information registration” from the operation screen illustrated in
As described above, a user is able to belong to multiple user groups. On the operation screen illustrated in
After the above information is input, the permission of the data sharing that has been requested is notified to the communication terminal device such as a mobile telephone of the user B. By this notification, the user B inputs the permission of sharing (Yes) or denial (No) for every piece of data to which the sharing is requested, from the communication screen of the communication terminal device illustrated in
That is, as to the data that the user A desires to share, when the user B gives permission of the data sharing, the corresponding data is permitted to be shared with the user A or with the user group input by the user A on the policy illustrated in
Moreover, as to the data sharing with a user group, for example, a notification may be given to the user B that there is a request, only when a user with a given authority who belongs to the user group requests the data sharing. Alternatively, only when the permission of the data sharing is requested from a predetermined communication terminal device, a notification may be given to the user B that there is a request.
3 Group Processing Unit
When the user A manually encourages the user B to participate in the user group managed by the user A, the user A requests the user B to participate in the user group via the operation screen of the communication terminal device. The request is notified to the user B through a general WEB server 604 included in a network. When the user B desires to participate in the user group of the user A, the desire to participate in the group is notified from the WEB server 604 to the group processing unit 202. When the desire of participation is notified, the group registration unit 606 registers the user B as a member of the user group of the user A.
Additionally, the group processing unit 202 is provided with an automatic grouping unit 607. The automatic grouping unit 607 is provided with: a group mapping analysis engine 601; a user preference analysis engine 602; and a user profile association analysis engine 603. The automatic grouping unit 607 is a component of grouping users automatically by use of a user's current location, a history of data to which the sharing is requested, or information included in profile information.
The user preference analysis engine 602 is a component of analyzing data with which the user requested to share or a history of data with which the user requested to share to extract user's preferences. The user profile association analysis engine 603 analyzes the user profiles of multiple users to extract common points or the like. The group mapping analysis engine 601 creates a group of users based upon the extracted user's preferences, the common points of the user profile, or the like.
Grouping Process by Preference
The user preference analysis engine 602 analyzes the history of data shared by users registered in the data sharing system. In this process, as to the text data, a key word common to multiple shared text data is extracted as information on the preference. Additionally, when the sound data or video data relating to music is shared, the title key word of music or image is extracted as the information on the preference.
The group mapping analysis engine 601 creates a user group so that multiple users who have common information on the preference belong to an identical user group. Specifically, in this process, the group mapping analysis engine 601 inquires the user whether or not the user desires to belong to the user group. Only when the user desires it, such a user may be registered in the user group.
Grouping Process by Attribute (Profile Information)
The user profile association analysis engine 603 extracts common elements such as address, work place, department, gender, hobby, and the like, from the user profile stored in the user profile master DB. The group mapping analysis engine 601 creates a user group so that multiple users who have common information on the address, department or the like belong to an identical user group. With such grouping, for example, information can be delivered to given community residents from a local ward office, the police office, or the like.
In this case, the group mapping analysis engine 601 creates a user group so that multiple users who have the common elements belong to an identical user group.
In this process, whether or not the user desires to belong to the user group may be inquired to register only the user who desires it in the user group.
Grouping Process by Current Position
Moreover, as described above, when the users' location information is acquired as the user profile by use of GPS or the like, the user profile association analysis engine 603 extracts the users' current locations within a given range as a common element between users.
As a concrete example of a case where the user group is created based upon the location information, conceivable is a case where user's participation in a concert or event is automatically encouraged. In such an example, an organizer of an event creates a user group beforehand, and inquires the users within a given range from the event site set as a center about the participation in the user group. When a user desires to participate in the user group, the user is registered in the event organizer's group. The event organizer stores the information on the event in the DB of the event organizer, thereby allowing the users included in the user group to share the stored information.
In another situation, when a traffic jam or the like occurs, a manager of transportation creates a user group, so that whether or not there is a desire to participate in the user group can be inquired for the users within a range affected by the traffic jam. With such a process, the manager stores information on the situation of the traffic jam, schedule of recovery, detour, or the like in the DB, thereby allowing the users who belong to the user group to share the information.
4 Data Sharing Process Unit
When a user C makes a call to the user B, when the sound data of a voice mail (voice mail message) is generated, the sound data is stored in the DB 604b. As illustrated in
In addition, when the user B downloads the melody data, such downloaded melody data is stored in the DB 604b. As illustrated in
Moreover, the data sharing process is performed manually or automatically, as described above. When performed manually, the sharing process unit requests determination of whether or not the data should be shared to the user A, the user X, and the user Y. Only when the user A or the like desires to share the data, the data sharing is achieved. When performing automatically, since the sound data or the melody data of the answering machine is newly stored, the sharing process unit automatically copies the sound data or the melody data from the DB 604a to the DBs of the user A, the user X, and the user Y.
(Operation)
Next, the operation of the data sharing system according to the present embodiment will be described.
1 Registration of Profile Information
As illustrated in
The profile group management unit 201 registers the profile information in the user profile master DB in response to the registration request (step 806). Then, the registration result is notified to the mobile telephone 103a (step 804). After the registration is confirmed on the mobile telephone 103a, the registration process of the profile information is completed.
In the above process, the user makes a connection to the site as illustrated in
Moreover, according to the present embodiment, the user's current location can be stored as the profile information. The current location may be input in the form of address, telephone number, or the like from the operation screen, or may be acquired by use of the GPS function or the like of the mobile telephone 103a.
2 Process of Policy Setting
The user A requests a connection to a policy setting screen provided by the site of the data sharing system, from the mobile telephone 103a (step 111). The sharing policy management unit 203 provides the policy setting screen illustrated in, for example,
The user B confirms the transmitted information on the mobile telephone 103b, and determines whether the data sharing with the user A or the user group to which the user A belongs is permitted or denied (step 119). The determination result is transmitted to the sharing policy management unit 203 as information of the policy setting confirmation (step 115). The sharing policy management unit 203 sets the policy of the user B, when the user A permits the data sharing (step 120), and registers as illustrated in, for example,
3.1 Grouping Process (Manual)
In such a case, the user A requests the sharing policy management unit 203 for a group setting screen provided by the data sharing system, by use of the mobile telephone 103a (step 171). The sharing policy management unit 203 provides the group setting screen to the mobile telephone 103a of the user A (step 172). The user A transmits the participation request of the user B participating in the user group, by use of the mobile telephone 103a, to the sharing policy management unit 203 (step 173). The sharing policy management unit 203 requests the mobile telephone 103b of the user B for a participation confirmation in the user group (step 174).
The user B transmits the information on permission or denial of the participation in the user group in response to a participation confirmation request of the sharing policy management unit 203 (step 175). The sharing policy management unit 203 performs the grouping process in accordance with the will of the user B, which is permission or denial (step 180). Then, the grouping result is transmitted to the mobile telephone 103a and the mobile telephone 103b (step 176, step 177). When the user A participates in the user group of the user B, the participation of the user A in the user group of the user B is registered in the profile group management unit 201.
Specifically, when the user B desires to cancel the membership of the user group of the user A, the user B has only to transmit the information indicative of an intention of cancelling the membership to the sharing policy management unit 203 from the group setting screen.
3.2 Grouping Process (Automatic)
The group processing unit 202 requests the profile group management unit 201 for transmission of the profile information (step 181). The profile group management unit 201 transmits the profile information in response to the request (step 182). The group processing unit 202 extracts the user's current location from the profile information, and requests multiple users whose current locations are included in a prescribed range for transmission of information indicative of whether or not to participate in the user group (step 183, step 185). The users (examples are the user A and the user B) transmit the requested information from their mobile telephones (step 184, step 186).
The group processing unit 202 performs the grouping process of creating a group with users who desire to participate in the user group (step 189). Information indicative of which user belongs to which group is managed by the profile group management unit 201. The result of the grouping process is transmitted to the users who participate in the user group (step 187, step 188).
Specifically, the present embodiment is not limited to the configuration of automatically performing the grouping process based upon the current location. For example, the user's address or department and the sharing are requested, so that the grouping process can be performed based upon the contents stored in the user's own DB.
The grouping process based upon the address allows users who live in a specified area to share data for rules of waste disposal, use of public accommodations, business hours of stores, and the like. In addition, the grouping based upon the department allows users who belong to this department to share the sound data of incoming calls at the department of the work place, and the like. Furthermore, the grouping process based upon the content stored in the DB allows a proposal to another user who likes the same content to acquire the data and encourage the data acquisition (sales).
4.1 Sharing Process (Sound Data of Answering Machine, Image Data)
For example, as illustrated in
In a case where the policy of the designated group is set for performing the data sharing manually, the sharing policy management unit 203 issues a sharing process confirmation request to the user (only the user B is illustrated in the drawing for simplification) included in the user group (step 123).
The user B transmits an instruction of whether the data sharing is to be performed (OK) or not (NG) to the sharing policy management unit 203 (step 124). When performing of the data sharing is instructed, the sharing policy management unit 203 notifies an instruction of performing the data sharing to the mobile telephone 103a, and in addition, requests the data sharing process unit 204 to share the sound data (step 126). Moreover, the sound data is shared with another user who has instructed the data sharing, among the other users who belong to the designated user group.
The data sharing process unit 204 makes the sound data shared between the DB 104a and the DB 104b in response to the request (step 128). The data sharing is achieved by the data sharing process unit 204 by copying the sound data in the DB 104a and transmitting by Push distribution or the like from the data sharing process unit 204 to the DB 104b. After the data sharing is achieved, a sharing completion notification is given to the data sharing process unit 204 from the mobile telephone 103a, the mobile telephone 103b, and a communication terminal device of another user (step 129).
The data sharing process unit 204 notifies the sharing policy management unit 203 of the result of the sharing process (step 130). The sharing policy management unit 203 also notifies the mobile telephone 103a, the mobile telephone 103b, and the communication terminal device, of another user, with which the data is shared of the result of the sharing process (step 131, step 132).
In the above operation, the sharing policy management unit operates as illustrated in
If it is requested (step S141: Yes), the sharing policy management unit confirms the policy requested (step S142). Then, whether or not the data sharing is desired is sequentially determined for the user or the user group who are permitted to share the data as to the corresponding data type and who desire the manual sharing (step S143). Specifically, as to the user or the user group who desire the automatic sharing, the data sharing is instructed to the data sharing process unit without the determination at step S143. The user or the user group determined to desire the data sharing is recorded for the subsequent Push distribution (step S146).
Then, as to the user or all in the user group with whom the data sharing is possible, whether or not they desire the sharing is determined (step S414). When the determination is not completed for all the users (step S144: No), the desire of the sharing process of an unprocessed user or user group is determined and the sharing is achieved. When the determination is completed for all the users (step S144: Yes), an instruction for sharing is issued to the data sharing process unit for all the users who desire the data sharing (step S145).
4.2 Sharing Process (Melody Data)
When the mobile telephone 1502 downloads the melody data, the downloaded melody data is stored in the DB 104a. The melody data is transmitted to the user group to which the sharing is permitted by the policy (step 151). The timing when the melody data is transmitted to the user group can be set at, for example, the timing when a user belonging to the user group makes a call to the user A.
On the communication terminal device (only the mobile telephone 103a is illustrated in the drawing for simplification) of the user included in the user group, the data of the transmitted melody data is reproduced to play the melody (step 161). In addition, after the melody is played, the operation guidance for acquiring the melody data may be played. The user of the mobile telephone 103a listens to the played melody, and determines whether or not to desire the acquisition of the melody data in accordance with the guidance (step 162).
The operation is, for example, to push a given button once to instruct the start of sharing in the DB, when desiring the acquisition of the melody data. Alternatively, when the data sharing is not desired, a given button is pushed twice to cancel the data sharing.
By the operation on the mobile telephone 103a, the confirmation request of the sharing policy of the user who owns the mobile telephone 103a is transmitted from the mobile telephone 103a to the sharing policy management unit 203 (step 152). The sharing policy management unit 203 determines the policy of the user group including the mobile telephone 103a (step 160).
As a determination result, when the user group including the mobile telephone 103a is permitted to share the melody data of the user A and the current time is included in a sharing period range, the sharing policy management unit 203 requests the data sharing process unit 204 for the sharing process of the data of the user group (step 154). Specifically, the policy determination result of the sharing policy management unit 203 is transmitted to all the users who desire the sharing of the melody data from the sharing policy management unit 203.
The data sharing process unit 204 shares the melody data in the DB 104a with all the users who desire to share the melody data, in response to the request from the sharing policy management unit 203 (step 156). Subsequent to the sharing, the sharing process completion is notified to the data sharing process unit 204 from the communication terminal device of the user to which the sharing process of the melody data is performed (step 157). The data sharing process unit 204 notifies the result of the sharing process to the communication terminal device of the user belonging to the user group (step 158, step 159).
In the above sequence, the process illustrated in
The user operates the buttons of the mobile telephone in accordance with the guidance. On the mobile telephone, whether or not the user desires to share the melody data is determined by the button operation (step S163). When the acquisition is desired (step S163: Yes), the mobile telephone notifies the sharing policy management unit of the desire to acquire the melody data (step S164). When the acquisition is not desired (step S163: No), the process is terminated without notification to the sharing policy management unit.
Moreover, the sharing policy management unit determines whether or not the information indicative of the desire to acquire the melody data is transmitted from the mobile telephone, as illustrated in
When the user of the mobile telephone is able to acquire the melody data (step S166: Yes), the sharing policy management unit instructs the sharing of the melody data to the data sharing management unit (step S167). When the acquisition of the melody data by the user group is not permitted (step S166: No), the process is terminated without issuing an instruction for sharing. Specifically, in such a case, information indicative of the fact that the data sharing is not permitted may be transmitted to the mobile telephone in form of sound or text.
In the present embodiment described heretofore, in a case where the sound data of the voice mail is shared, for example, the user A makes a call to the user B to make another user other than the user B share the recorded message of the voice mail. Accordingly, this allows the user B to talk about the content of the message recorded in the answering machine or the reaction therefor. Moreover, in a case where multiple vehicles moves toward the same destination, the GPS information of one vehicle can be shared with mobile telephones of passengers in another vehicle.
The present invention applies to “Voice Mail Service” of NTT Docomo, whereby a recorded message of the voice mail can be shared with multiple users. In addition, when the present invention applies to “i-Motion®”, the video data can be delivered in an efficient manner.
Number | Date | Country | Kind |
---|---|---|---|
2009-084983 | Mar 2009 | JP | national |
Filing Document | Filing Date | Country | Kind | 371c Date |
---|---|---|---|---|
PCT/JP2010/002326 | 3/30/2010 | WO | 00 | 12/6/2011 |