JP2011076478A - Sns server, property information management method and program for the same - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To facilitate management of property information, in a server providing a plurality of SNSs. <P>SOLUTION: In this SNS (Social Networking Service) server 10 providing the plurality of SNSs, the property information 131 of users of the respective SNSs is configured by a common table 132 comprising items common to the respective SNSs and original tables 133 each comprising items original to each SNS. When the SNS server 10 updates an item value of the property information of each user, the SNS server 10 updates an item value of the common table 132 about the common item 210, and updates an item value of the original table 133 about the original item 211. When the SNS server 10 refers to the item value of the property information of each user, the SNS server 10 refers to the item value of the common table 132 about the common item 210, and refers to the item value of the original table 133 about the original item 211. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  It is a technology related to the management of a social database of a social networking service (SNS).

  Currently, various SNSs such as mixi (registered trademark) and GREE (registered trademark) exist, and social information of users is managed for each SNS. This social information is user information used for SNS, and includes, for example, property information (see Non-Patent Document 1) such as the user's name, nickname, current location, and hobbies. This social information includes friends (friend information) and activities (activity information) in addition to property information. The friend information is information indicating the user's personal relationship such as the user's friend, colleague, and family. The activity information is information indicating user behavior such as writing a blog, listening to music, taking a picture, etc., and this activity information is notified to the user's friends. The notification here is performed, for example, by displaying the activity information as a character image or the like on the Web browser of the terminal device of the user's friend.

Open Social, [online], [Search September 16, 2009], Internet, <URL: http://code.google.com/apis/opensocial/>

  Here, the same user may use a plurality of SNSs. That is, when a certain server provides two SNSs SNS1 and SNS2, the user A may use both SNSs. In such a case, the property information of SNS1 and the property information of SNS2 are managed separately, but this takes time and effort for management. That is, the property information includes items commonly used in each SNS (common items. For example, name, date of birth, address, e-mail address, etc.), and if these are managed for each SNS property information, double It will be a hassle. For example, when there is a change in the contents of the user's mail address among the common items, the information on the mail address of the property information of each SNS must be changed.

  Accordingly, an object of the present invention is to solve the above-described problems and facilitate management of property information in a server that provides a plurality of SNSs.

  In order to solve the above-described problem, the invention described in claim 1 is an SNS server that provides a plurality of SNSs and manages property information of the plurality of SNSs, from a terminal device of a SNS user via a network. An input unit that receives input of various types of information, (1) a common table indicating property items of each SNS for each user ID of the SNS, a common table indicating item values of the common items, and (2) each SNS For each user ID of a user who uses the SNS, among the items of the property information of the SNS, a unique item that is an item other than the common item and a unique table indicating the item value of the unique item are stored. And a storage unit that performs SNS data processing based on a processing request from the terminal device that is input via the input unit, and returns an execution result to the terminal device. When a user property information reference request is received from the terminal device via the data processing unit and the SNS data processing unit, the item values of the common items are read from the common table among the item values subject to the reference request. The item value of the unique item is read from the unique table, the read item value is output to the SNS data processing unit, and the processing result by the SNS data processing unit and the database reference unit is output to the terminal device. Part.

  The invention described in claim 6 is an SNS server that provides a plurality of SNSs and manages property information of the plurality of SNSs. (1) Property information of each SNS for each user ID of the SNS user Common item of the item, a common table indicating the item value of the common item, and (2) for each SNS, for each user ID of the user who uses the SNS, among the items of the property information of the SNS A storage unit that stores a unique item that is an item other than the item and a unique table that indicates the item value of the unique item, and executes SNS data processing based on a processing request from the user's terminal device. When an SNS server including an SNS data processing unit that returns a result to the terminal device receives a reference request for user property information from the terminal device, the reference request Among the target item values, the item value of the common item is read from the common table, the item value of the unique item is read from the unique table, and the read item value is output to the terminal device that is the source of the reference request. The property information management method is characterized by this.

  By doing in this way, the SNS server records the item value of the common item in the common table among the property information of the plurality of SNSs, and records the item unique to the SNS in the unique table. When referring to the property information of a certain SNS in response to a request from the terminal device, the item value of the common item is read from the common table, and the item value of the unique item of the SNS is read from the unique table. Read from. As described above, by managing common items using the common table, it is not necessary to prepare property information for each SNS. Therefore, management of property information becomes easy. For example, if it is desired to update the item value of the common item among the property information of each SNS, the item value of the common table may be updated.

  In the invention according to claim 2, when the SNS server according to claim 1 receives an update request for property information including a user ID, an item name, and an item value from the terminal device via the SNS data processing unit, Based on the update request, update the item value of the user's item name of the user ID in the common table and the unique table, and update the item value updated item and the item ID indicating the user ID to the SNS data processing unit And the storage unit includes item information in which the item ID and the updated item value are associated with each other, and the database update unit (1) updates when the received update request does not include the item ID. The user ID and item ID indicating the item name included in the request are issued, and the item value included in the update request is used for the common table and the original table. The item value of the item relating to the user is updated, the issued item ID is associated with the updated item value, stored in the item information, and the issued item ID is output to the SNS data processing unit (2 ) When an item ID is included in the received update request, (a) when the item value included in the update request is different from the item value associated with the item ID in the item information, Update the item value related to the item to the item value included in the update request, update the common table and the unique table using the item value, and (b) the item value included in the update request corresponds to the item in the item information When the value is the same as the item value associated with the ID, the common table and the unique table are not updated, and the SNS data processing unit does not correspond to the item ID output from the database updating unit. The item update request to, when outputting the re database update unit, configured to output the update request including the item ID which is the output.

  In the property information management method according to claim 6, when an update request for property information including a user ID, an item name, and an item value is received from a terminal device, the update request is received. The database update of the SNS server including the database update unit that updates the item value of the item name of the user of the user ID in the common table and the unique table, and outputs the item and the item ID indicating the user ID to the SNS data processing unit (1) If the received update request does not include an item ID, the department issues an item ID indicating the user ID and item name included in the update request, and uses the item value included in the update request. Update the field value of the field for the user in the table and the original table, and the issued field D is associated with the updated item value and stored in the item information, and the step of outputting the issued item ID to the SNS data processing unit is executed. (2) The item ID is included in the received update request. If the item value included in the update request is different from the item value associated with the item ID in the item information, the item value related to the item in the item information is updated. And updating the common table and the original table using the item value, and (b) the item value included in the update request corresponds to the item ID in the item information. When it is the same as the assigned item value, the common table and the unique table are not updated, and the SNS data processing unit does not correspond to the item ID output from the database updating unit. The item update request to, when outputting the re database update unit, and the property information management method for outputting an update request including the item ID which is the output.

  According to such an SNS server, the database update unit issues an item ID for the user who has received the update of the item value of the property information for the first time, and the item for which the same user has received the update for the first time, and outputs it to the SNS data processing unit To do. The issued item ID is stored as item information. And when a database update part receives the update request containing this item ID from a SNS data processing part, it turns out that it is update of the item value of the same item as the item updated last time among the property information of the said user. And if the item value of the item of this item ID is the same, each table is not updated, and if the item value is different, each table is updated. That is, when receiving an update request for property information, the SNS server does not access each table if there is no need for updating, so the update processing load on each table can be reduced. Therefore, it is possible to reduce the load of updating processing of item values of items that are frequently updated in the property information (for example, information indicating the current position of the user measured by GPS or the like). In addition, by configuring the property information with the common table and the unique table in this way, for example, when newly creating SNS property information, if the item value of the common item recorded in the common table is used, Therefore, the creation of property information is easy and accurate.

  In the invention according to claim 3, when the SNS server according to claim 1 receives a property information update request including a user ID, an item name, and an item value from the terminal device via the SNS data processing unit, A database update unit that updates the item value of the user's item name of the user ID in the common table and the unique table based on the update request, and the storage unit stores the user ID, the item name, and the item value of the item name item value The database update unit includes the associated item information, and (1) when the combination of the user ID, the item name, and the item value included in the update request is not stored in the item information, Update the item value of the item with the item value included in the update request, and use the user ID, item name, and item value to share the common table and unique text. Update the table, (2) the user ID included in the update request, a combination of the item name and item values, when stored in the item information, characterized in that it does not update the common table and its own table.

  Even in this way, when the SNS server accepts an update request, it does not access each table if there is no need for updating, so that the update processing load on each table can be reduced.

  In the invention according to claim 4, the database update unit of the SNS server according to claim 2 or claim 3 uses the latest item value stored in the item information of the storage unit for each predetermined period. And the unique table is updated.

  By doing in this way, item values of items with high update frequency in the property information are updated on the item information and reflected in each table every predetermined period. It is no longer necessary to perform update, and the update processing load on each table can be further reduced.

  As for invention of Claim 5, the memory | storage part of the SNS server of any one of Claim 1 thru | or 4 shows the user ID of the user who is a user's friend, and the attribute of the user who is the friend. And when the SNS data processing unit accepts the data processing request for the first user, the second information of the terminal device that is the transmission source of the processing request is referred to by referring to the friend information for the first user. When it is determined that the user is a friend of the first user and a user having a predetermined attribute, data processing relating to the first user is executed in response to a processing request from the terminal device of the second user It is characterized by doing.

  By doing in this way, the SNS server can perform the process which considered the attribute of the user of the terminal device of the transmission source of this data processing request about the various data processing regarding SNS. For example, in the friend information, when the information that the attribute of the user B of the terminal device that requested the data processing is “family” with respect to “user A” is recorded, Data processing is performed within the permitted range. For example, in the service provided by the SNS server, if the addition of a comment on the blog of user A is permitted, a comment is added in response to a comment addition request from the terminal device of user B. .

  The invention according to claim 8 is a program for causing an SNS server, which is a computer, to execute the property information management method according to claim 6 or claim 7.

  By doing so, the property information management method according to claim 6 or claim 7 can be executed by a general computer.

  ADVANTAGE OF THE INVENTION According to this invention, in the server which provides several SNS, management of the property information of each SNS can be made easy.

It is a block diagram of the system containing the SNS server of this Embodiment. It is the figure which illustrated the common table and original table of FIG. (A) is a sequence diagram showing a procedure when a new common table is created, and (b) is a sequence diagram showing a procedure when a new unique table is created. (A) is a sequence diagram showing a procedure when creating a new item in the common table, and (b) is a sequence diagram showing a procedure when creating a new item in the unique table. (A) is a sequence diagram which shows the reference processing procedure of the item value of a common table, (b) is a sequence diagram which shows the reference processing procedure of an original table item value. (A) is a sequence diagram which shows the update process procedure of the item value of a common table, (b) is a sequence diagram which shows the update process procedure of an original table item value. It is a sequence diagram which shows the detail of the update process of a common table and an original table. It is a block diagram of the system containing the SNS server of 2nd Embodiment. It is the sequence diagram which showed the process sequence of the SNS data processing part of FIG. 8, a database processing part, and a module management part.

  Hereinafter, modes for carrying out the present invention (hereinafter referred to as embodiments) will be described.

<Configuration>
First, the overall configuration of a system including an SNS (social network service) server according to the present embodiment will be described with reference to FIG. The system includes an SNS server 10 that provides a plurality of SNSs, and a terminal device 20 that transmits and receives data to and from the SNS server 10. The SNS server 10 and the terminal device 20 are connected by a network 30 such as an IP (Internet Protocol) network. When the SNS server 10 receives a reference request for property information and the like, an update request, and various data processing requests related to SNS from the terminal device 20 via the network 30, the SNS server 10 returns a reference result, an update result, and various data processing results.

  Such an SNS server 10 is realized by a computer including an input / output unit (input unit and output unit) 11, a processing unit 12, and a storage unit 13. The input / output unit 11 is responsible for receiving various data processing requests related to the SNS, transmitting various data processing results, and the like. The processing unit 12 controls the SNS server 10 as a whole, and here provides the SNS to the user terminal device 20 mainly through various application execution processes related to the SNS. Further, the property information 131 (described later) stored in the storage unit 13 is referred to and updated. The SNS is provided by application execution processing by the SNS data processing unit 121, and the SNS data processing unit 121 provides one or more SNSs. The storage unit 13 stores various information necessary for the processing unit 12 to execute processing, applications (application programs), and the like. Further, the property information of each user regarding each SNS is composed of a common table 132 that shows items common to each SNS and their item values, and a unique table 133 that shows items unique to each SNS and their item values. The This will be conceptually described with reference to FIG.

  For example, the property information used in each SNS includes common items (name, date of birth, etc.) of property information of each SNS as indicated by reference numeral 210 in FIG. 2 and property information of each SNS as indicated by reference numeral 211. It consists of original items (hobbies, current location, etc.). Here, when referring to the item value of the common item in the profile information of SNSID = A1 of the user ID = XX, the item value of the item of the user ID = XX in the common table 132 is read. When referring to the item value of the unique item of the profile information of SNSID = A1, the item value of the item of the user ID = XX is read from the table of SNSID = A1 in the unique table 133. Note that if it is a reference request for the entire profile information of SNSID = A1 of user ID = XX, the item values of the common item and the unique item are read and output. That is, since the item values of the common table 132 are used for the common items in the profile information, it is not necessary to manage the profile information of each user for each SNS.

  The input / output unit 11 of the SNS server 10 in FIG. 1 includes a communication interface and an input / output interface for performing data communication over the network 30. The processing unit 12 is realized by a program execution process by a CPU (Central Processing Unit) included in the SNS server 10, a dedicated circuit, or the like. Further, the storage unit 13 includes a storage medium such as a random access memory (RAM), a read only memory (ROM), a hard disk drive (HDD), and a flash memory. The storage unit 13 stores an application program for realizing the function of the SNS data processing unit 121. The item information 134 (described later) is stored on the RAM (main memory) of the storage unit 13. This is because the information of the item information 134 is likely to be updated frequently.

  Next, the configuration of the processing unit 12 will be described. The processing unit 12 includes an SNS data processing unit 121 and a database processing unit 122.

  The SNS data processing unit 121 executes data processing of each SNS based on the request from the terminal device 20 input by the input / output unit 11 and returns the processing result to the terminal device 20. That is, various services related to SNS are provided. For example, when a blog update processing request is received from the terminal device 20, the blog data (not shown) is updated accordingly, and the update result is returned to the terminal device 20. When the SNS data processing unit 121 receives a request for property information reference or an update request from the terminal device 20, the SNS data processing unit 121 instructs the database processing unit 122 to refer to or update the property information. When the result is received, the data is returned to the terminal device 20.

  The database processing unit 122 refers to or updates various information such as property information 131 and friend information 135 (described later) stored in the storage unit 13 based on an instruction from the SNS data processing unit 121. Then, the reference result and the update result are output to the SNS data processing unit 121. Such a database processing unit 122 includes a database reference unit 123, a database update unit 124, a friend reference unit 125, and a friend update unit 126.

  Upon receiving a user property information reference request, the database reference unit 123 determines whether the item that is the target of the reference request is an item in the common table 132 or an item in the unique table 133. Then, the item value of the item related to the user who is the target of the property information reference request is read from the table including the reference target item, and is output to the SNS data processing unit 121. For example, referring to FIG. 2, when the database reference unit 123 receives a reference request for the name of the user ID = XX via the SNS data processing unit 121, this item is a common item. The item value relating to the name of this user ID = XX is read out. When a reference request for the current location of the user ID = XX is received, the item value of the current location of the SNSID = A1 of the user ID = XX is read from the unique table 133. Then, the read item value is returned to the SNS data processing unit 121.

  When the database update unit 124 receives an update request for the property information 131, the database update unit 124 updates the information of the user of the SNS that is the target of the update request, among the information in the common table 132 or the unique table 133. Specifically, first, when the database update unit 124 receives an input of an update request for the property information 131 via the SNS data processing unit 121, the database update unit 124 sets an item name and a user ID to be updated in the update request. It is determined whether or not the item ID shown is included. Here, if the item ID is not included, the database update unit 124 issues an item ID indicating the item name and user ID that are the targets of the update request. This item ID issues a unique value (or random value) every time. And the item value of the said item regarding the said user in the common table 132 and the original table 133 is updated using the item value contained in the input update request. Further, the database update unit 124 stores the issued item ID and the item value in association with each other in the item information 134. The issued item ID is output to the SNS data processing unit 121. That is, if the item value of an item that has not been updated in the user property information 131 is updated, the item ID and the item value of the item are stored in the item information 134. Also, the issued item ID is notified to the SNS data processing unit 121 (and the update request terminal device 20), and the SNS data processing unit 121 updates the same item when an update request for the same item is output again. This item ID is included in the request and output. Therefore, the database update unit 124 determines whether the update request includes an item ID, whether the update request is an item value update request from a new user, and whether a new item is received from the same user. It can be determined whether or not it is an update request.

  In addition, when the input update request includes an item ID indicating an item name and a user ID, the database update unit 124 corresponds to the item value in the item information 134 with the item value included in the update request. It is determined whether or not the item value is the same. That is, it is determined whether or not this update request is an update request for updating the same item with the same value for the profile information of the same user. Here, when it is determined that the request is not an update request for updating the same user and the same item with the same value, the item value related to the item in the item information 134 is updated to the item value included in the update request. Also, the item value of the item in the common table 132 or the unique table 133 is updated using this item value. On the other hand, the database update unit 124, when the item value included in the update request is the same as the item value associated with the item ID in the item information 134, that is, here, the same value for the same user and the same item. When it is determined that the update request is for updating, the common table 132 and the unique table 133 are not updated. Thereby, when the update request of the same item value about the same item is received from the same user, it becomes unnecessary to perform the update process of various tables.

  When the friend reference unit 125 receives a friend reference request including the user ID via the SNS data processing unit 121, the friend information 135 displays the friend user ID (friend ID) of the friend of the user ID and the attribute of the friend in the friend information 135. Read and output to the SNS data processing unit 121. The friend attribute read out here is referred to when the SNS data processing unit 121 performs processing based on the friend attribute. That is, when the SNS data processing unit 121 receives a processing request for data related to the first user, the SNS data processing unit 121 refers to the friend information 135 and the second user of the terminal device 20 that is the transmission source of the processing request When it is determined that the user is a user and a user having a predetermined attribute, data processing related to the first user is executed in response to a processing request from the terminal device 20 of the second user. For example, let us consider a case in which data processing related to the user A is received in the friend information 135 and the data processing request source is the terminal device 20 of the user B. Here, in the friend information 135, when the attribute of the user B is “family” with respect to the “user A”, the SNS data processing unit 121 has data in a range permitted for the “family” of the user A. Process.

  When the friend update unit 126 receives an update request for the friend information 135 via the SNS data processing unit 121, the friend update unit 126 updates the friend of the friend information 135 and the attribute of the friend based on the update request. For example, if the attribute of the friend already registered in the friend information 135 is changed, the attribute of the friend to be changed is changed. If a friend is added, the friend ID of the user is added, and the attribute of the friend is added.

  Next, the storage unit 13 will be described. The storage unit 13 stores property information 131, item information 134, friend information 135, and user ID information 136.

  The property information 131 includes a common table 132 and a unique table 133. Among these, the common table 132 is a table showing item values of items (common items) common to each SNS among the items of the property information 131. For example, as illustrated in FIG. 2, for each user ID, information indicating an ID of an SNS (SNSID) in which the user participates, a common item, and a value of a common item related to the user. For example, the common table 132 of FIG. 2 indicates that the SNSID of the user with the user ID “XX” is “A1, A2”, the name is “aa”, and the date of birth is “bb”.

  In addition, as illustrated in FIG. 2, the unique table 133 is a table showing, for each SNS, a user ID participating in the SNS and item values of the unique items of the SNS regarding the user. The table on the foremost side of the unique table 133 in FIG. 2 is a table showing the item value of the unique item whose SNSID is “A1”, and the current location of the user with the user ID “XX” is “cc”. The hobby is “dd”.

  Returning to the description of FIG. The item information 134 is information indicating the item ID of the item whose item value is updated in the property information 131 by the database updating unit 124 and the item value of the item in association with each other. The item information 134 is stored on the RAM of the storage unit 13, for example. The item ID and the item value indicated in the item information 134 are referred to when the database update unit 124 determines whether or not the item value of each table needs to be updated.

  The friend information 135 is information indicating, for each SNS, a user ID (friend ID) of a user who is a friend of each user of the SNS and an attribute of the user who is the friend. For example, when the SNS data processing unit 121 receives a data processing request from the terminal device 20 of a predetermined user, the friend information 135 is processed according to the data processing request based on the attribute of the user. It is referred to when determining whether or not to execute.

  The user ID information 136 is information indicating a user ID of a user who subscribes to the SNS for each SNS. This user ID information 136 is referred to when a new common table 132 or unique table 133 is newly created. It is assumed that the information of the user ID information 136 is input in advance via the input / output unit 11.

  According to the SNS server 10 described above, since it is not necessary to manage the property information of each SNS individually, the management effort can be reduced. Further, when an item value update request for the property information 131 is received and the item value included in the update request is the same item value for the same user and the same item, the item value is reflected in each table. Can be omitted. Thereby, the load of the update process of each table can be reduced. Furthermore, the friend information 135 includes not only the user ID (friend ID) of each user's friend but also the attribute of the friend. Therefore, the SNS data processing unit 121 can execute data processing based on the friend attribute.

<Processing procedure>
Next, the processing procedure of the SNS server 10 will be described with reference to FIG. First, the creation procedure for newly creating the common table 132 and the unique table 133 will be described with reference to FIGS.

<New creation process>
When the SNS data processing unit 121 in FIG. 1 receives a new common table creation request including an item name list provided in the common table 132 via the input / output unit 11, the SNS data processing unit 121 outputs the creation request to the database processing unit 122 (FIG. 3). (A) S11). In response to this, the database update unit 124 of the database processing unit 122 registers this item name list in a predetermined area of the storage unit 13 (S12). Then, the database update unit 124 acquires a list of all user IDs from the user ID information 136 (S13), lists the item names registered in the storage unit 13 in S12, and the list of all user IDs acquired in S13. And create a new common table 132 (S14). The created common table 132 is stored in a predetermined area of the storage unit 13. The database update unit 124 of the database processing unit 122 notifies the SNS data processing unit 121 that a new common table 132 has been created (S15).

  When the SNS data processing unit 121 in FIG. 1 receives a request for creating a new unique table including an item name list provided in the unique table 133 and the SNS ID via the input / output unit 11, the SNS data processing unit 121 outputs the request to the database processing unit 122 ( S21 in FIG. In response to this, the database update unit 124 of the database processing unit 122 registers this item name list in a predetermined area of the storage unit 13 as in S12 (S22). Then, the database updating unit 124 acquires a list of user IDs of the SNSID accepted in S22 from the user ID information 136 (S23), and acquires the item name list registered in the storage unit 13 in S22 and acquired in S23. A unique table 133 is newly created using the list of user IDs that have been created (S24). The created unique table 133 is stored in a predetermined area of the storage unit 13. The database update unit 124 of the database processing unit 122 notifies the SNS data processing unit 121 that a unique table 133 has been newly created (S25). As described above, the database update unit 124 newly creates the common table 132 and the unique table 133.

<New item addition processing>
Next, a procedure for adding a new item to the common table 132 and the unique table 133 will be described with reference to FIGS. First, when the SNS data processing unit 121 receives a creation request including an item name of a new item related to a common item via the input / output unit 11, the SNS data processing unit 121 outputs the creation request to the database processing unit 122 (FIG. 4A). S31). In response to this, the database updating unit 124 of the database processing unit 122 registers the item name of the new item in a predetermined area of the storage unit 13 (S32), and uses this registered item name to add a new item to the common table 132. Create (S33). Then, the common table 132 in which the new item is created is stored in a predetermined area of the storage unit 13. Next, the database processing unit 122 notifies the SNS data processing unit 121 that a new item has been created in the common table 132 (S34).

  When the SNS data processing unit 121 receives a request for creating a new item including the item name of the new item related to the unique table 133 and the SNS ID via the input / output unit 11, the SNS data processing unit 121 outputs the creation request to the database processing unit 122. (S41 in FIG. 4B). In response to this, the database update unit 124 of the database processing unit 122 registers the item name of the new item in a predetermined area of the storage unit 13 (S42), and uses this registered item name to register the SNSID, as in S32. A new item is created in the original table 133 (S43). Then, the unique table 133 in which the new item is created is stored in a predetermined area of the storage unit 13. Next, the database processing unit 122 notifies the SNS data processing unit 121 that a new item has been created in the unique table 133 (S44). As described above, the database update unit 124 newly creates the common table 132 and the unique table 133.

<Reference processing of item value>
Next, a procedure when referring to the item values of the common table 132 and the unique table 133 will be described with reference to FIGS. First, when the SNS data processing unit 121 receives a reference request for an item value including the user ID and the item name of the item to be referred to via the input / output unit 11, the SNS data processing unit 121 outputs the reference request to the database processing unit 122 ( S51 in FIG. In response to this, the database reference unit 123 of the database processing unit 122 searches the item name of the reference request from the item names of the common table 132 and the unique table 133 (S52). When it is determined that the item name of the reference request is an item of the common table 132, the item value of the item name of the user ID is referred (read) from the common table 132 (S53). Then, the item value read from the common table 132 (S54) is output to the SNS data processing unit 121 (S55).

  When the SNS data processing unit 121 receives a reference request for an item value including the user ID, the item name of the item to be referred to, and the SNS ID via the input / output unit 11 (S61 in FIG. 5B). ) And output to the database processing unit 122. In response to this, the database reference unit 123 of the database processing unit 122 searches for the item name from the item names of the common table 132 and the unique table 133 (S62). If it is determined that the item name is an item of the unique table 133, the item value of the item name of the user ID is referred to (read) from the unique table 133 of the SNSID (S63). Then, the item value is read from the unique table 133 (S64) and output to the SNS data processing unit 121 (S65). As described above, the database update unit 124 performs reference processing of the item values of the common table 132 and the unique table 133.

<Item value update processing>
Next, a procedure for updating item values in the common table 132 and the unique table 133 will be described with reference to FIGS. First, when the SNS data processing unit 121 receives an update request for an item value including a user ID, an item name of an item to be updated, and an item value via the input / output unit 11, the SNS data processing unit 121 outputs the request to the database processing unit 122. (S71 in FIG. 6A). In response to this, the database update unit 124 of the database processing unit 122 searches for the item name from the item names of the common table 132 and the unique table 133 (S72). When the database update unit 124 determines that the item name is an item of the common table 132, the database update unit 124 updates the item value of the item name of the user ID in the common table 132 (S73). The SNS data processing unit 121 is notified (S74).

  When the SNS data processing unit 121 receives an update request for an item value including the user ID, the item name of the item to be updated, and the SNS ID via the input / output unit 11 (S81 in FIG. 6B). ) And output to the database processing unit 122. In response to this, the database update unit 124 of the database processing unit 122 searches for the item name from the item names of the common table 132 and the unique table 133 (S82). When the database update unit 124 confirms that the item name is an item of the unique table 133, the database update unit 124 updates the item value of the item name of the user ID in the unique table 133 of the SNSID (S83). The SNS data processing unit 121 is notified of the update (S84).

  Here, details of the update processing of the item values of the common table 132 and the unique table 133 by the database processing unit 122 will be described with reference to FIG.

  First, when the SNS data processing unit 121 receives an update request for an item value including the user ID, the item name, and the item value that are the target of the update request via the input / output unit 11, the SNS data processing unit 121 processes the update request as a database process. (S91, corresponding to S71 in FIG. 6A). Then, the database update unit 124 of the database processing unit 122 determines whether or not the item ID is included in this update request (S92). If the item ID is not included in the update request (No in S92), a new item ID is issued (S94). Then, the common table 132 or the unique table 133 is searched using the user ID and item name included in the update request as keys, and the item value of which item name in which table should be updated is specified. Then, the database update unit 124 of the database processing unit 122 updates the item value of the user and the item name of the specified table (S96). Further, the database update unit 124 stores the issued item ID and the item value included in the update request in association with the item information 134. Then, the database update unit 124 of the database processing unit 122 outputs the issued item ID to the SNS data processing unit 121 (S97). Thereafter, when receiving an update request for the same item from the same user, the SNS data processing unit 121 outputs an update request including this item ID to the database processing unit 122.

  On the other hand, if the item ID is included in the update request output from the SNS data processing unit 121 in S92 (Yes in S92), the database updating unit 124 of the database processing unit 122 indicates that this item ID is included in the item information 134. It is determined whether it is stored (S93). If this item ID is stored in the item information 134 (Yes in S93), the item value corresponding to the item ID in the item information 134 is the current item value (the item included in the update request). Value) is determined (S95). On the other hand, if the item ID is not stored in the item information 134 (No in S93), the process proceeds to S96.

  In S95, if the item value corresponding to the item ID in the item information 134 is the same as the current item value (the item value included in the update request) (Yes in S95), the database updating unit of the database processing unit 123 124 returns “OK” to the SNS data processing unit 121 (S97). At this time, the database update unit 124 does not update the item value in the item information 134 nor update the item value in each table. That is, when an update request with the same item value is received for the same item from the same user as the previous time, the database update unit 124 does not perform update processing on each table. This eliminates the need for the database update unit 124 to perform unnecessary update processing on the item values in each table. If the item value corresponding to the item ID in the item information 134 is different from the current item value (item value included in the update request) (No in S95), the database updating unit 124 proceeds to S96. move on. That is, the database update unit 124 executes update processing for each table and update processing for the item information 134 using the user ID, item name, and item value indicated in the update request.

  According to the database updating unit 124 of the database processing unit 122 described above, when a new item value update request is received from the user, the item ID is issued and the item ID is output to the SNS data processing unit 121. And when this SNS data processing part 121 receives again the update request of the item value of the same item about the profile information of the same user, it will output the update request containing the item ID. In other words, the database update unit 124 can search the item information 134 using the item ID as a key to determine whether or not an update request for the same item has been received from the same user in the past, and what the item value of the item is. The database update unit 124 can quickly determine whether an update request with the same item value for the same item from the same user has been accepted.

  Although not described here, the SNS data processing unit 121 receives the update request for the friend including the user ID, the friend ID of the user (friend ID), and a label indicating the attribute of the user. The request is output to the friend update unit 126. In response to this, the friend update unit 126 updates or adds a friend and its attribute to the friend information 135. When the SNS data processing unit 121 receives a friend reference request including a user ID, a label indicating the friend attribute, and the like, the SNS data processing unit 121 outputs the reference request to the friend reference unit 125. In response to this, the friend reference unit 125 returns, from the friend information 135, a list of friends of the user and friends having attributes indicated in the reference request among the friends, to the SNS data processing unit 121.

<Second Embodiment>
Next, the SNS server 10A according to the second embodiment of this invention will be described with reference to FIG. The SNS server 10 </ b> A according to the second embodiment generates activity information 139 indicating a processing result by the SNS data processing unit 121. Constituent elements similar to those of the above-described embodiment are denoted by the same reference numerals and description thereof is omitted.

<Configuration>
The storage unit 13 of the SNS server 10A in FIG. 8 stores a module group 137 and a module table 138. In addition, the storage unit 13 includes an area for storing activity information 139. Furthermore, the processing unit 12 of the SNS server 10A further includes a module management unit 127.

  The module group 137 is a module group of programs executed in accordance with the application program execution process of the SNS data processing unit 121.

  The module table 138 is information indicating a program module to be executed in accordance with the execution process of each application program (see Table 1).

  The activity information 139 is information indicating the processing contents executed by the SNS data processing unit 121. For example, when the SNS data processing unit 121 publishes user A's blog, the activity information 139 has the content that “user A has published the blog”. Further, when the SNS data processing unit 121 provides a music distribution service to the user B, the activity information 139 has the content “User B has listened to music”, and the SNS data processing unit 121 is the terminal of the user C. When uploading a photo image from the apparatus 20 is received, the activity information 139 has the content “User C uploaded a photo image”.

  Note that the SNS data processing unit 121 and the database processing unit 122 perform the following processing in addition to the processing described in the first embodiment. When the application program is executed, the SNS data processing unit 121 further performs a process of outputting an activity information registration request regarding the execution of the program to the database processing unit 122. When the database processing unit 122 receives the activity information registration request, the database processing unit 122 further performs a process of calling a module (target module) to be executed along with the execution of the application with respect to the module management unit 127.

  Based on the module call instruction from the database processing unit 122, the module management unit 127 refers to the module table 138 and selects a module of a program to be executed along with the execution of the application program from the module group 137. Then, the scenario execution unit 128 included in the module management unit 127 performs an execution process of the selected module.

  For example, when the SNS data processing unit 121 publishes the user A's blog, this is notified to the database processing unit 122. Upon receiving this notification, the database processing unit 122 outputs a target module call instruction to the module management unit 127. Further, upon receiving the instruction to call the target module, the module management unit 127 selects a module and activates the selected module. Then, the scenario execution unit 128 requests the database processing unit 122 to search for the friend of the user A indicated in the activity information registration request, and generates the activity information to be notified to the searched friend. For example, based on this module, the scenario execution unit 128 requests the database processing unit 122 to search for the friend of the user indicated in the activity information registration request, and obtains a search result that the friend of the user A is the users B and C. Consider the case of getting it. In this case, the scenario execution unit 128 generates activity information 139 indicating that the user A has published the blog, and notifies the generated activity information 139 to the terminal devices 20 of the users B and C.

<Processing procedure>
Next, the processing procedure of the SNS server 10A will be described with reference to FIG. First, when executing the execution process of the application program, the database processing unit 122 outputs a registration request (activity information registration request) for activity information 139 associated with the execution process to the database processing unit 122 (S101). This registration request includes the user ID of the terminal device 20 that is the transmission source of the application program execution request, XML (Extensible Markup Language) data (XML) indicating the processing contents of the application program, and the ID (APLID) of the executed application program. Including. Upon receiving such an activity information registration request, the database processing unit 122 outputs, to the module management unit 127, an instruction to call the target module to be executed in accordance with the execution of the application program (S102). This call instruction includes the above-described user ID, XML, and APLID.

  Upon receiving such a call instruction, the module management unit 127 refers to the module table 138 using the APLID included in the call instruction as a key, and selects a module to be activated when the application is executed from the module group 137. To do. Then, activation processing of the selected module is performed (S103). Then, the scenario execution unit 128 analyzes the XML included in the call request (S104), and executes the module based on the analyzed XML. Here, the friend search request indicating the user ID included in the instruction to call the target module is output to the friend reference unit 125 of the database processing unit 122, and the friend is called (S105). And the friend reference part 125 performs the friend search process of the said user from the friend information 135 by using a user ID as a key (S106). Next, the searched friend is returned to the module management unit 127 as a friend ID list. Then, the scenario execution unit 128 of the module management unit 127 generates activity information 139 indicating the execution result of the application (S107), and the generated activity information 139 is sent to the friend shown in the friend ID list searched in S106. Notification is made (S108).

  For example, the scenario executing unit 128 notifies the activity information 139 that the user A has published the blog to the browser of the terminal devices 20 of the users B and C who are the friends of the user A. Thereby, the users B and C can know that the user A who is his friend has published the blog.

  Note that the module of the program to be executed in accordance with the execution of the application program described in the module table 138 can be changed based on an instruction input from the input / output unit 11. For example, based on an instruction from the user A, it is possible to change a program module to be executed from execution of the application program XX from b, c to d, e. By doing in this way, the module of the program which should be executed in conjunction with the execution of the application program can be changed to what the user desires, and various services can be provided to the user.

  1 and 8, when the SNS data processing unit 121 receives an update request including a new item value, the database update unit 124 updates (1) the item value of the item included in the update request in the item information 134. (2) The item values of the items in each table are updated, but the update timings of (1) and (2) may not be the same. That is, every time a new item value is received by an update request, the database update unit 124 updates the item value on the item information 134, and the item value stored in the item information 134 is reflected in each table. It may be executed every predetermined period. That is, the database update unit 124 updates the item value on the item information 134 within a predetermined period, and updates each table with the item value (latest item value) on the item information 134 after the predetermined period. You may make it perform. By doing in this way, for example, even if the item value transmitted from each terminal device 20 is an item value that frequently changes, such as user position information measured by GPS (Global Positioning System), The database update unit 124 does not need to update each table each time this item value is received. Therefore, the load of update processing for each table can be reduced.

  Further, the database update unit 124 in FIGS. 1 and 8 determines whether or not the update request is related to the same item of the same user by using the item ID included in the received update request, but is included in the update request. You may make it judge using a user ID and an item name. That is, the item information 134 stores information in which the user ID and item name of the update request received in the past are associated with the item value of the item, and the database update unit 124 stores the received update request in the received update request. If the combination of the included user ID, item name, and item value is stored in the item information 134, it is determined that an update request with the same item value for the same item has been received from the same user, and update processing for each table is performed. Not performed. On the other hand, if the combination of the user ID, the item name, and the item value included in the received update request is not stored in the item information 134, the database update unit 124 (1) an update request from a different user, (2) Even if the same user is an update request regarding different items, or (3) an update request regarding the same item from the same user, it is determined that the update request is based on different update values, and an update process is performed on each table. By doing in this way, the database update part 124 can judge whether it is the update request regarding the same item of the same user, without using item ID.

  Further, the database update unit 124 may delete the information of the item information 134 every predetermined period. In this way, the resources secured in the item information 134 of the storage unit 13 can be used effectively.

10, 10A SNS server 11 Input / output unit 12 Processing unit 13 Storage unit 20 Terminal device 30 Network 121 SNS data processing unit 122 Database processing unit 123 Database reference unit 124 Database update unit 125 Friend reference unit 126 Friend update unit 127 Module management unit 128 Scenario execution unit 131 Property information 132 Common table 133 Unique table 134 Item information 135 Friend information 136 User ID information 137 Module group 138 Module table 139 Activity information

Claims (8)

An SNS server that provides a plurality of SNSs and manages property information of the plurality of SNSs,
An input unit for receiving input of various information from the terminal device of the SNS user via a network;
(1) For each user ID of the user, a common item of the property information items of the SNS, a common table indicating the item values of the common items, and (2) using the SNS for each SNS A storage unit that stores, for each user ID of the user, a unique table that is an item other than the common item among items of the property information of the SNS, and a unique table that indicates item values of the unique item;
An SNS data processing unit that executes SNS data processing based on a processing request from the terminal device input via the input unit, and returns an execution result to the terminal device;
When a reference request for the property information of the user is received from the terminal device via the SNS data processing unit, the item value of the common item among the item values subject to the reference request is the common table. A database reference unit that reads out the item value of the unique item from the unique table and outputs the read item value to the SNS data processing unit;
An SNS server, comprising: an output unit that outputs processing results obtained by the SNS data processing unit and the database reference unit to the terminal device. The SNS server is
When an update request for the property information including the user ID, item name, and item value is received from the terminal device via the SNS data processing unit, the user in the common table and the unique table is based on the update request. A database update unit that updates the item value of the item name of the user of the ID, and outputs the item that updated the item value and the item ID indicating the user ID to the SNS data processing unit;
The storage unit
Item information that associates the item ID with the updated item value,
The database update unit
(1) If the item ID is not included in the received update request, an item ID indicating a user ID and an item name included in the update request is issued, and an item value included in the update request is used. The item value of the item related to the user in the common table and the unique table is updated, the issued item ID is associated with the updated item value, stored in the item information, and the issued item ID is Output to the SNS data processing unit,
(2) When the item ID is included in the received update request, (a) the item value included in the update request is different from the item value associated with the item ID in the item information. When the item value related to the item in the item information is updated to the item value included in the update request, the common table and the unique table are updated using the item value, and (b) included in the update request. When the item value is the same as the item value associated with the item ID in the item information, the common table and the unique table are not updated,
The SNS data processing unit
2. The update request including the output item ID is output when an update request for an item corresponding to the item ID output from the database update unit is output to the database update unit again. The SNS server as described in. The SNS server is
When an update request for the property information including the user ID, item name, and item value is received from the terminal device via the SNS data processing unit, the user in the common table and the unique table is based on the update request. A database update unit for updating the item value of the item name of the user of ID,
The storage unit includes item information in which the user ID, the item name, and the item value of the item of the item name are associated with each other,
The database update unit
(1) When the combination of the user ID, item name, and item value included in the update request is not stored in the item information, the item value of the item of the user in the item information is included in the update request Updating the common table and the original table using the user ID, the item name, and the item value,
(2) The common table and the unique table are not updated when a combination of a user ID, an item name, and an item value included in the update request is stored in the item information. SNS server. The database update unit
4. The SNS server according to claim 2, wherein the common table and the unique table are updated using a latest item value stored in the item information of the storage unit for each predetermined period. The storage unit
Comprising friend information indicating a user ID of a user who is the friend of the user and an attribute of the user who is the friend;
The SNS data processing unit
When a processing request for data related to the first user is received, the second user of the terminal device that is the transmission source of the processing request refers to the friend information related to the first user, and the friend of the first user When it is determined that the user has a predetermined attribute, data processing relating to the first user is executed in response to a processing request from the terminal device of the second user. The SNS server according to any one of claims 1 to 4. An SNS server that provides a plurality of SNSs and manages property information of the plurality of SNSs, (1) for each user ID of the SNS user, common items of the property information items of the SNSs, A common table indicating item values of common items, and (2) for each SNS, for each user ID of the user using the SNS, among items of property information of the SNS, items other than the common items A storage unit that stores a unique item and a unique table that indicates an item value of the unique item, and performs SNS data processing based on a processing request from the terminal device of the user, and the execution result is transmitted to the terminal An SNS server including an SNS data processing unit to be returned to the device
When the reference request for the property information of the user is received from the terminal device, the item value of the common item is read from the common table among the item values subject to the reference request, and the item of the unique item A property information management method, wherein values are read from the unique table, and the read item values are output to the terminal device that is the source of the reference request. When receiving an update request for the property information including the user ID, item name and item value from the terminal device, based on the update request, the item name of the user of the user ID in the common table and the unique table The database update unit in the SNS server includes a database update unit that updates an item value and outputs an item ID indicating the item and the user ID to the SNS data processing unit,
(1) If the item ID is not included in the accepted update request,
Issuing an item ID indicating a user ID and an item name included in the update request, and updating an item value of the item related to the user in the common table and the unique table using an item value included in the update request; ,
Associating the issued item ID with the updated item value and storing it in item information;
Outputting the issued item ID to the SNS data processing unit;
(2) In the case where the item ID is included in the received update request,
(A) When the item value included in the update request is different from the item value associated with the item ID in the item information,
Updating an item value related to the item in the item information to an item value included in the update request;
Executing the step of updating the common table and the unique table using the item value;
(B) When the item value included in the update request is the same as the item value associated with the item ID in the item information,
Without updating the common table and the original table,
The SNS data processing unit
7. When an item update request corresponding to an item ID output from the database update unit is output again to the database update unit, an update request including the output item ID is output. Property information management method described in 1.   The program for making the SNS server which is a computer perform the property information management method of Claim 6 or Claim 7.

Images