JP5914375B2 - Data providing method and service system - Google Patents

Description

  The present invention relates to a user data providing method and a service system for providing data registered by a user in response to a request from another person.

  Congestion of the telephone network is a state where it is difficult to connect the telephones, and this is caused by the concentration of telephones exceeding the capacity that can be processed within a certain time in the exchange. For example, when a disaster occurs, the number of telephone calls for confirmation of safety may increase and congestion may occur. If the call cannot be confirmed due to congestion and the safety cannot be confirmed, the call is repeated until the other party is connected, and congestion may increase. In addition, not only a telephone but also communication on the Internet, congestion occurs when data exceeding the communication line capacity is transmitted.

  As a safety confirmation method that can be used when a disaster occurs, there are a disaster message dial, a disaster message board, and the like in addition to a method of directly calling the other party. When using the disaster message dial, the user calls a specific telephone number for the disaster message dial and registers a voice data message in association with the telephone number to which he / she subscribes. Also, other users who confirm the safety of the user can call a specific telephone number and listen to the message using the user's telephone number as a key.

  The disaster message board is a service that uses the Internet, and in the event of a disaster, the user accesses a specific server for the disaster message board and registers a message such as character data in association with the telephone number to which the user subscribes. . Also, other users who confirm the user's safety can access a specific server and view the message using the user's telephone number or the like as a key.

  In general, it is difficult to share data between systems that collect data in different formats (see, for example, Patent Document 1). The disaster message dial and the disaster message board both have safety data, but the disaster message dial system uses voice data and the disaster message board system uses text format data. doing. Therefore, data is not shared by each system.

JP-A-8-256176

  As described above, conventionally, even if a plurality of systems have necessary data, they are independent of each other. For this reason, the user needs to access each system separately, and when a disaster occurs, a telephone call or request transmission from the user is sent to each system, which may easily cause congestion in the telephone network or communication line.

  In view of the above problems, the present invention prevents the occurrence of congestion in the telephone network and the Internet communication network even in a situation where congestion is likely to occur in the telephone network, and enables user information to be quickly confirmed. With the goal.

In order to achieve the above object, the present invention stores voice data input from a user terminal, and the first service system provided to another user terminal stores text data input from the user terminal. A data providing method for providing data to a second service system provided to a terminal, wherein the first service system receives the voice data including the safety information of the user from the user terminal, and storing the voice data storage device to the identifier in correspondence, in the audio data stored in the sound data storage device timing, converts the audio data into text data, the converted text data, the audio data Is stored in the text data storage device in association with the text data relating to the attribute of the user who entered When receiving a request including a user attribute and requesting provision of text data of the user from the second service system, the text data requested by the request is read from the text data storage device, 2 and transmitting to the service system, and the text data storage device stores the telephone number and other user attributes encrypted .
The present invention is a service system for storing voice data input from a user terminal and providing it to other user terminals. When voice data including user safety information is received from a user terminal, the voice data is received from the user terminal. When receiving a request for receiving provision of voice data including an identifier from the user terminal and a reception unit that stores the voice data in association with the identifier, the voice data corresponding to the identifier is read from the voice data storage device. a first providing means for transmitting to the user terminal, in the audio data stored in the sound data storage device timing, converts the audio data into text data, the converted text data, and inputs the voice data Conversion stored in a text data storage device in association with text data relating to user attributes When a request for providing text data including user attributes is received from another service system that stores text data input from the user terminal and provides it to other user terminals, the requested text data is Second providing means for reading from the text data storage device and transmitting it to the other service system, wherein the text data storage device stores the telephone number and other user attributes encrypted . .

  According to the present invention, even in a situation where congestion is likely to occur in the telephone network, congestion can be prevented from occurring in the telephone network or the Internet communication network, and user information can be quickly confirmed.

FIG. 1 is a schematic diagram illustrating a user data providing system according to an embodiment. FIG. 2 is a block diagram showing the configuration of the first service system. FIG. 3 is a schematic diagram illustrating the configuration of contractor data used in the first service system. FIG. 4 is a schematic diagram illustrating a configuration of reception data used in the first service system. FIG. 5 is a schematic diagram illustrating the configuration of text data used in the first service system. FIG. 6 is an example of text data. FIG. 7 is a block diagram showing the configuration of the second service system. FIG. 8 is a flowchart for explaining processing of the first service system that has received the voice data. FIG. 9 is a flowchart for explaining processing of the first service system that has received the authentication data. FIG. 10 is a flowchart for explaining processing of the first service system that has received a request from a terminal. FIG. 11 is a flowchart for explaining processing of the first service system that has received a request from the second service system.

  Hereinafter, a user data providing method and a service system used in the user data providing method according to the present invention will be described with reference to the drawings. In the following description, the same configuration and the same process are denoted by the same reference numerals, and the description thereof is omitted.

  As shown in FIG. 1, a user data providing system 1 that implements a user data providing method according to the present invention includes a first service system 10 that is a “disaster message dial system” and a “disaster message board system” or “ And a second service system 20 which is a “safety confirmation system that can be used at the time of a similar disaster”. In the user data providing system 1, the first service system 10 and the second service system 20 are connected via a network 30. The network 30 is a communication network that can transmit and receive data between the service systems 10 and 20 by packet communication.

  The first service system 10 is connected to the terminals 40 a and 40 b via the telephone network 31. The terminals 40a and 40b are wired telephones, mobile phones, and the like. Alternatively, it may be an information processing apparatus such as a personal computer having a voice input / output device and capable of transmitting and receiving voice via the telephone network 31. Here, the telephone network 31 may be wired or wireless. Alternatively, the telephone network 31 may be a telephone network that uses an Internet line such as an IP telephone network. Hereinafter, an example using the terminal 40a will be described, but the same applies even if the terminal 40a is replaced with the terminal 40b. In FIG. 1, the number of telephones connected to the first service system 10 is two, but the number of telephones connected is not limited.

  The first service system 10 is connected to the terminals 40 c and 40 d via the network 32. The network 32 is a communication network such as an NGN line or an Internet line that can realize packet communication. The terminals 40c and 40d are information processing apparatuses such as a personal computer, a mobile phone, a tablet terminal, and a smartphone. Hereinafter, an example using the terminal 40c will be described, but the same applies even if the terminal 40c is replaced with the terminal 40d. In FIG. 1, the number of information processing apparatuses connected to the first service system 10 is two, but the number of information processing apparatuses connected is not limited.

  The second service system 20 is connected to terminals 50 a and 50 b that are information processing apparatuses via a network 33. The network 33 is a communication network that can transmit and receive data between the second service system 20 and the terminal 50a by packet communication. Hereinafter, an example using the terminal 50a will be described, but the same applies even if the terminal 50a is replaced with the terminal 50b. In FIG. 1, the number of information processing devices connected to the second service system 20 is two, but the number of information processing devices connected is not limited.

  In FIG. 1, the network 32 to which the terminal 40c is connected and the network 33 to which the terminal 50a is connected are different, but may be the same. In addition to the networks 32 and 33, the network 30 may be the same. In addition, when importance is attached to the security of data transmitted and received between the service systems 10 and 20, the network 30 may use a dedicated line. 1 illustrates an example of the user data providing system 1 in which one first service system 10 and one second service system 20 are connected. However, the first service system 10 to be connected is described. The number of second service systems 20 is not limited.

<First service system>
As shown in FIG. 2, the first service system 10 includes a receiving unit 11a that receives voice data, a conversion unit 11b that converts voice data into text data, a first providing unit 11c that provides voice data to the terminal 40a, and authentication. A registration unit 11d for registering the data, a determination unit 11e for determining whether to provide data, and a second provision unit 11f for providing data to the second service system 20.

  For example, the first service system 10 is an information processing device such as a server including the CPU 11 and the storage device 12, and the CPU 11 receives the reception unit 11 a, the conversion unit 11 b, and the like by executing the service program P 1 stored in the storage device 12. The processing of the first providing unit 11c, the registering unit 11d, the determining unit 11e, and the second providing unit 11f is executed. In addition to the service program P1, the storage device 12 includes contractor data D1 related to a user who subscribes to a telephone service provided by the first service system 10, received data D2 including received voice data, and text converted from the voice data. Text data D3 in a format and authentication data D4 used for determining whether access is possible are stored.

  The contractor data D1 is data including the “name” of the user who contracts the telephone service provided by the first service system 10, the “phone number” assigned to the user, and the like. In the contractor data D1, for example, as shown in FIG. 3, “name” and “telephone number” are associated with the “contractor ID” determined by the user as a key. The storage device 12 can store contractor data D1 of a plurality of users.

  When the reception means 11a inputs voice data from the terminal 40a via the telephone network 31, as shown in FIG. 4, for example, the reception means 11a associates the input voice data with the metadata obtained when the voice data is input. And stored in the storage device 12 as reception data D2.

  Specifically, the voice data is data relating to the user and includes data such as the user's “name”, “age”, “address”, “message”, and the like. Here, the “address” does not have to include the entire address, and may be specified by the prefecture or city. Further, the content of the “message” can be freely input by the user, and is, for example, details on safety and information on the destination.

  For example, the reception unit 11a guides the user by voice announcement when receiving the voice data, and the user inputs the voice data according to the guidance. Thereby, the reception means 11a can distinguish (store) the contents of items such as “name”, “age”, “address” or “message”. In addition, when the reception unit 11a can perform voice recognition processing, the reception unit 11a may generate reception data D2 by distinguishing the contents of each item from the input voice data by voice recognition.

  Further, for example, the metadata is data including “acceptance time” when the audio data is received, the “phone number” of the user input to the user as the user identifier, and the like. That is, the first service system 10 uses the user's “phone number” as a key in each process.

  In addition, the metadata may include user position information. When the terminal used by the user for inputting voice data is a fixed telephone (wired telephone), the “location information” where the user exists is specified from the area code included in the telephone number. Further, when the terminal used by the user for inputting voice data is a mobile phone, “location information” where the user exists is specified from the base station to which the mobile phone is connected. Therefore, the metadata can include “location information” specified in this way.

  The storage device 12 can store a plurality of received data D2. That is, the storage device 12 can store reception data D2 of a plurality of users.

  The conversion unit 11b converts the contents of each item of the audio data included in the reception data D2 into a text format. Moreover, the conversion means 11b produces | generates text data from the converted data and a user's attribute. Specifically, the conversion means 11b displays the contents of “the contents of each converted item”, “the contents of necessary items included in the metadata of the received data D2”, “the items included in the contractor data D1”, and the like. The included data is stored in the storage device 12 as text data D3. At this time, the conversion means 11b is not included in the contractor data D1 and the reception data D2, but can include the content input from the terminal 40a in the text data D3. Here, the conversion unit 11b can select the contractor data D1 corresponding to the reception data D2 using the identifier “telephone number” as a key.

  FIG. 5 is a conceptual diagram illustrating an example of data included in the text data D3. For example, “name (kanji)” and “e-mail address” are extracted from the contractor data D1. Further, “name (kana)”, “age”, “address”, and “message” are extracted from the voice data of the reception data D2 and converted. Further, the “telephone number” and “reception time” are extracted from the metadata of the reception data D2.

  In addition, the “encrypted phone number” of the text data D3 is encrypted by, for example, the “phone number” included in the metadata of the reception data D2 by the conversion unit 11b. If it is not desirable to publish “telephone numbers” that are one of the personal information and have a one-to-one correspondence with users in a wide range, it is possible to use this “encrypted phone number” to leak personal information. Can be prevented. That is, if the “telephone number” which is personal information is leaked, it may be misused. If the encryption method is unified in the user data providing system 1, the user can be specified using the “encrypted telephone number” as a key.

  Various schemes for encrypting the telephone number are conceivable. For example, a “phone number hash value” can be used as the “encrypted telephone number”. Hashing is a “method in which a character string is uniquely converted into another character string and is not easily converted in the reverse direction”. Therefore, for example, the telephone number is converted (encrypted) using such a “method that can be uniquely converted and is not easily converted in the reverse direction”. Specifically, it can be used as a telephone number encrypted by a cryptographic hash function such as SHA-1 or SHA-2. As a result, if the original phone number is to be kept secret, it is difficult to reverse convert, so this encrypted phone number is a character generated based on the phone number without being known to others. Since it is a column, it is possible to uniquely specify an individual.

  More specifically, when the telephone number is hashed (encrypted) among the name “Ishida” and the telephone number “XXXXXXXXXX”, the name “Ishida” and the telephone number “badjoifafdaxcp” can be obtained. On the other hand, when the telephone number of the name “Ishida” and the telephone number “YYYYYYYYYY” is hashed, the name “Ishida” and the telephone number “bfsriklnfsbmq” can be obtained. Therefore, when the hashed phone number is used, it is possible to distinguish between Ishida of the phone number “XXXXXXXXXX” and Ishida of the phone number “YYYYYYYYYY”.

  In addition, although the example which encrypts a telephone number among a user's attribute (personal information) is demonstrated here, the object of encryption is not restricted to a telephone number. For example, when information leakage is not preferable, the contents of other attributes such as an e-mail address may be encrypted.

  The “deletion time” is a time input from the terminal 40a or the terminal 40c, or a time after a predetermined time has elapsed (eg, one month later) from the “reception time”. In this case, the value (time) input from the terminal 40a or the terminal 40c can also be used as the “predetermined time”. The first service system 10 includes, for example, an updating unit (not shown), and when the text data D3 includes “deletion time”, the text data D3 and the corresponding reception by the updating unit after the deletion time has elapsed. The data D2 is deleted from the storage device 12.

  Furthermore, in addition to the information included in FIG. 5, “an identifier (ID) used in another WEB service”, “blood type”, and the like may be included. These may be extracted from the contractor data D1 and the reception data D2, or may be input from the terminal 40a via the telephone network 31 or input from the terminal 40c via the network 32 and included in the text data D3. .

  In addition, each item of the text data D3 can be associated with a “flag” indicating whether or not to be disclosed. Further, a plurality of flags may be associated with different disclosure ranges. The example shown in FIG. 5 includes a “flag relating to items that can be disclosed to the whole” and a “flag relating to items that can be disclosed only to authenticated users”. For example, in the example illustrated in FIG. 5, “name (kanji)” is not disclosed to “whole” but only to “authenticated users”. On the other hand, “name (kana)” is disclosed to “whole” and “authenticated user”. Note that FIG. 5 shows only the contents related to one user, but the text data D3 can have data of a plurality of users.

  For example, the value of each flag can be input as voice data from the terminal 40a via the telephone network 31 and included in the text data D3. Alternatively, flag setting means (not shown) may be input from the terminal 40c via the network 32 and included in the text data D3.

  The text data D3 is data including the contents of the items described above with reference to FIG. 5 in FIG. Regardless of the type of text format, the text data D3 may use, for example, XML as shown in FIG. The format of the text data D3 may be other formats such as JSON (JavaScript Object Notation) and YAML (YAML Ain't Markup Language) as long as it is structured in addition to XML (Extensible Markup Language). <Privacy_flag> in FIG. 6A indicates the value of the flag corresponding to each item of text data, and the value following A of <privacy_flag> corresponds to each item. Whether or not there is ". Moreover, the value following B of <privacy_flag> corresponds to each item, and these represent “whether or not it can be disclosed only to authenticated users”.

  In addition, although omitted in FIGS. 5 and 6, <privacy_flag> may further include a character “C” and a character C followed by “value corresponding to each item”. Specifically, when there are a plurality of authentication methods, it is necessary to limit the scope of disclosure according to the authentication method. Therefore, it shall be specified that “when authenticated by authentication method 1” is disclosed using the value following B, and “when authenticated by authentication method 2” is disclosed using the value following C. Can do.

  For example, “authentication method 1” is “when authenticated using a telephone number”, and “authentication method 2” is “authentication using name and address (prefecture or city). When it is done ". The telephone number identifies the user almost on a one-to-one basis. However, since the name may be the same name, it is difficult to identify the user on a one-to-one basis. Therefore, the number of pieces of information (information to be disclosed) obtained when authenticated by “authentication method 2” is defined to be smaller than when authenticated by “authentication method 1”. For example, when authenticated by “authentication method 1”, information on the items of “name (kanji), name (kana), age, address (prefecture), address (city), telephone number, message” is disclosed. In addition, when authentication is performed by “authentication method 2”, it can be specified that information of items of “name (kana), age, address (prefecture), encrypted telephone number” is disclosed. Note that the authentication method is not limited to this, and “authentication using a white list”, which will be described later, may be considered, and the number of authentication methods specified by <privacy_flag> of the text data D3 is not limited.

  When the first providing unit 11 c receives a request for providing a voice data message from the terminal 40 a via the telephone network 31, the first providing unit 11 c extracts the corresponding voice data from the storage device 12. The first providing unit 11c transmits and provides the extracted data to the terminal 40a via the telephone network 31. For example, when receiving a request including the identifier “telephone number”, the first providing unit 11 c searches and extracts the reception data D2 associated with the “telephone number” from the storage device 12.

  When the registration unit 11d inputs authentication data from the terminal 40a or the terminal 40c, the registration unit 11d stores the input data in the storage device 12 as the authentication data D4. The registration unit 11d can also change the authentication data stored in the storage device 12 in accordance with an operation from the terminal 40a or the terminal 40c.

  For example, the registration unit 11 d inputs authentication data from the terminal 40 a via the telephone network 31. Further, for example, the registration unit 11 d inputs authentication data from the terminal 40 c via the network 32. The authentication data is, for example, a white list including an identifier (for example, a telephone number or an e-mail address) of another person who can provide the data. The “white list” is data including an identifier of another person to be disclosed so as not to be disclosed (provided) except for a predetermined specific person. Alternatively, the authentication data may be a password that is entered by another person who requests the provision of data.

  In addition, the authentication data may be a part of user attributes (personal information) included in the contractor data D1 and the text data D3. Specifically, it is determined in advance which of the user's attributes is the data for authentication, and this user's attribute is given to others who know all of the attributes defined for authentication. You may make it permit provision of data. For example, “name”, “telephone number”, “e-mail address”, and “address” as user attributes can be used as authentication data.

  The authentication data D4 is data that associates the above-described “white list”, “password”, “user attribute (personal information)”, and the like with a “telephone number” that is a user identifier. The storage device 12 can store authentication data D4 for a plurality of users.

  When the determination unit 11e receives a request for providing text data from the second service system 20 via the network 33, the determination unit 11e searches the storage device 12 for the corresponding text data D3. This request includes at least an identifier of another person who requests provision of data and an identifier of a user who is requested to provide data.

  For example, the identifier is a “telephone number” or “e-mail address” that identifies the user on a one-to-one basis. The request can include authentication data for providing data. In this case, “name” and “address” can be used as user identifiers.

  For example, when searching for data related to a plurality of users, the request may include an identifier for identifying the plurality of users. Specifically, when a public institution transmits a request with an “address” as an identifier for the purpose of confirming safety, it is possible to retrieve data on all residents in a specific area. Furthermore, when a school or a company sends a request including a plurality of “phone numbers” for the purpose of confirming the safety of a plurality of persons such as students and employees, the data of the plurality of persons can be searched.

  When the text data D3 is searched, the determination unit 11e determines whether the request is permitted by the authentication data D4. At this time, the determination unit 11e uses the authentication data D4 for the user who is requested to provide the data.

  For example, when the authentication data D4 is a “white list” including an identifier of a user (other person) who can provide data, the determination unit 11e determines whether or not the identifier of the other person is included in the request. When the authentication data D4 is “password”, the determination unit 11e determines whether or not the user password included in the authentication data D4 is included in the request. Further, when the authentication data D4 is “user attribute”, the determination unit 11e determines whether or not the attribute included in the authentication data D4 is included in the request.

  The second providing unit 11f generates text data for transmission including the content of the item to be transmitted from the corresponding text data D3 according to the determination result of the determination unit 11e. That is, the second providing unit 11f generates text data including data of an item selected according to <privacy_flag>. The second providing unit 11 f transmits the generated text data to the second service system 20 via the network 30. When the corresponding text data D3 is not retrieved by the determination unit 11e, the second providing unit 11f transmits a response indicating that the user text data D3 requested by the request does not exist to the second service system 20 via the network 30. To do.

  The second providing means 11f can be easily realized by using an API (Application Programming Interface). As a result, data sharing with other systems using data transmission / reception can be realized. Further, the second providing means 11f may be set so as to provide an upper limit of requests per hour in order to exclude those who maliciously access through the API.

  For example, it is assumed that text data D3 shown in FIG. 6A is extracted and it is determined that the request is from a user who is not authenticated by the determination unit 11e. In this case, as shown in FIG. 6B, for example, “name (kana)”, “age”, “encrypted phone number”, “address”, “acceptance time”, “ Text data including only “deletion time” is generated.

  The first service system 10 does not have to be realized by a single device, and may be realized by a plurality of devices. For example, any of the plurality of processing units 11a to 11f may be realized by an external device, or any of the plurality of data D1 to D4 may be stored by the external device.

<Second service system>
As shown in FIG. 7, the second service system 20 includes a receiving unit 21a, a providing unit 21b, and an acquiring unit 21c. For example, the second service system 20 is an information processing apparatus such as a server including the CPU 21 and the storage device 22, and the CPU 21 receives the reception unit 21 a, the provision unit 21 b, and the provision unit 21 b by executing the service program P 2 stored in the storage device 22. The processing of the acquisition unit 21c is executed. In addition to the service program P2, the storage device 22 stores received data D6 related to the received data.

  When the receiving means 21a inputs text data including user attributes and safety information from the terminal 50a via the network 33, the receiving means 21a associates the input text data with the metadata obtained when the text is input, and receives the received data. The data is stored in the storage device 22 as D6.

  The reception data D6 is data in which a user attribute and safety information are associated with a user identifier. The user identifier is, for example, a user name, a telephone number, or an e-mail address.

  When the providing unit 21b receives a request for providing text data from the terminal 50a via the network 33, the providing unit 21b extracts the corresponding reception data D6 from the storage device 22 and provides the data to the terminal 50a via the network 33. .

  The providing unit 21b outputs the received request to the obtaining unit 21c when the corresponding data is not extracted from the reception data D2. The providing unit 21b provides the text data input from the obtaining unit 21c to the terminal 50a in response to the request.

  When the acquisition unit 21c inputs a request, the acquisition unit 21c transmits the request to the first service system 10. When the text data is received in response to the transmitted request, the received text data is output to the providing means 21b.

  If the second service network 20 is connected to a plurality of first service networks, the acquisition unit 21c may transmit requests to all the connected first service networks at the same time, or in a predetermined order. You may send a request at When transmitting in a predetermined order, upon receiving a response indicating that the user's text data does not exist in response to a request transmitted to one device, the process of transmitting the request to other devices is repeated.

  Next, various processes in the first service system 10 will be described.

<Audio data addition processing>
First, a process of receiving voice data from the terminal 40a and storing new voice data in the storage device 12 will be described using the flowchart of FIG.

  The accepting unit 11a inputs voice data transmitted from the terminal 40a via the telephone network 31 (S01). Here, the voice data includes voices relating to items such as the user's “name”, “age”, “address”, or “message”, being distinguished for each item.

  The accepting unit 11a stores the input voice data and metadata related to the voice data in the storage device 12 as acceptance data D2 together with a telephone number that is a user identifier (S02).

  Further, the conversion unit 11b converts the voice data of the reception data D2 into a text format (S03). Here, the conversion unit 11b converts the audio data of the reception data D2 into the text format at a regular timing (for example, every 5 minutes), or new reception data D2 is stored in the storage device 12. Is the timing. For example, when the conversion process is performed at regular timing, the conversion unit 11b converts all the reception data D2 newly stored in the storage device 12 into the text format after converting the previous voice data into the text format. On the other hand, when the conversion process is performed at the timing when the new reception data D2 is stored in the storage device 12, the conversion unit 11b converts only the reception data D2 newly stored in the storage device 12 into a text format.

  Thereafter, the conversion unit 11b generates text data D3 by associating the data converted into the text format in step S03 with the related data, and stores the data in the storage device 12 (S04).

<Authentication data registration process>
A process of receiving authentication data from the terminals 40a and 40c and storing new authentication data D4 in the storage device 12 will be described using the flowchart of FIG.

  The registration unit 11d inputs authentication data from the terminal 40a via the telephone network 31 or from the terminal 40c via the network 32 (S11). When the authentication data is personal information such as the user's “name” and “phone number”, the user's personal information used for authentication is input.

  Thereafter, the registration unit 11d stores the data input in step S11 in the storage device 12 as the authentication data D4 (S12).

<Audio data provision processing>
The process of providing audio data to the terminal 40a in response to a request will be described using the flowchart of FIG.

  The first providing means 11c inputs a request for providing voice data from the terminal 40a via the telephone network 31 (S21).

  Subsequently, the first providing unit 11c extracts the reception data D2 including the “telephone number” included in the request from the storage device 12 (S22). The reception data D2 includes audio data as described above with reference to FIG.

  When the corresponding reception data is extracted in step S23, the voice data of the extracted reception data D2 is transmitted to the terminal 40a requested by the request (S23).

<Text data provision processing>
A process of providing text data to the second service system 20 will be described with reference to the flowchart of FIG.

  The determination unit 11e inputs a request for requesting provision of text data from the second service system 20 via the network 30 (S31).

  Subsequently, the determination unit 11e extracts the text data D3 including the identifier included in the request from the storage device 12 (S32).

  Further, when the target authentication data D4 is extracted from the storage device 12, the determination unit 11e authenticates this request (S33).

  The second providing unit 11f generates text data for transmission from the data of items that are transmission targets (publication targets) in the text data D3 extracted in step S32, according to the authentication result of step S33. (S34).

  Thereafter, the second providing unit 11f transmits the text data for transmission generated in step S34 to the second service system 20 (S35).

  In the second service system 20 that has received this text data, the text data is output from the obtaining means 21c to the providing means 21b. After that, the providing unit 21 b transmits text data to the terminal 50 a via the network 33.

  Here, the first service system 10 has been described as inputting voice data, providing voice data to the terminal 40a, and providing text format data to the second service system 20. May be executable. For example, although explanation using illustration is omitted, the first service system 10 may be able to input text format data and provide the text format data to the terminal 40c as in the second service system 20. .

  In the user data providing system 1 described above, the data received by the first service system 10 by voice can also be converted into text format data and provided to the second service system 20 which is another device. Therefore, if the user's safety information can be obtained in this way, the terminal using each service system does not attempt to access the service system multiple times, and acquires information possessed by other service systems in one access. can do. Accordingly, congestion of the telephone network and the network can be prevented.

  Further, the user data providing system 1 can provide data as data in a format that can be used by other devices by using the API. Therefore, provision (sharing) of data can be easily realized.

  Furthermore, in the user data providing system 1, the content of data that is not desirable for disclosure can be encrypted and transmitted. It is also possible to freely select the contents of data that the user has determined to be unsuitable for disclosure and keep it private. Therefore, it is possible to prevent the leakage and diffusion of personal information. In other words, prompt confirmation of safety and personal information leakage and diffusion are two sides of the same coin, and it was difficult to establish both at the same time, but by limiting the scope of encryption and disclosure, personal information leakage and Diffusion can be prevented.

  As mentioned above, although this invention was demonstrated in detail using embodiment, this invention is not limited to embodiment described in this specification. The scope of the present invention is determined by the description of the claims and the scope equivalent to the description of the claims.

DESCRIPTION OF SYMBOLS 1 ... User data provision system P1, P2 ... Service program 10 ... 1st service system 11 ... CPU
11a ... Accepting means 11b ... Conversion means 11c ... First providing means 11d ... Registration means 11e ... Determination means 11f ... Second providing means 12 ... Storage device
D4 ... Authentication data D1 ... Contractor data D2 ... Reception data D3 ... Text data D4 ... Authentication data 20 ... Second service system 21 ... CPU
21a ... Accepting means 21b ... Providing means 21c ... Acquiring means 22 ... Storage device D6 ... Accepted data 30, 32, 33 ... Network 31 ... Telephone network 40a-40d, 50a, 50b ... Terminal

Claims (6)

The first service system that stores voice data input from the user terminal and provides it to other user terminals stores the text data input from the user terminal and supplies the data to the second service system provided to other user terminals. A data providing method to provide,
The first service system includes:
Receiving voice data including the safety information of the user from the user terminal, storing the voice data in the voice data storage device in association with the identifier of the user;
In the audio data stored in the sound data storage device timing, converts the audio data into text data, the converted text data, the text data stored in association with the text data about attributes of the user who inputs the speech data Storing in the device;
Upon receiving from the second service system a request including user attributes and requesting provision of the user's text data, the text data requested by the request is read from the text data storage device, and the second service system And sending to
The text data storage device stores a telephone number and other user attributes in encrypted form . A service system that stores voice data input from a user terminal and provides it to other user terminals,
When receiving voice data including the safety information of the user from the user terminal, receiving means for storing the voice data in the voice data storage device in association with the identifier of the user;
Receiving a request for providing audio data including an identifier from a user terminal, first providing means for reading out audio data corresponding to the identifier from the audio data storage device and transmitting the audio data to the user terminal;
In the audio data stored in the sound data storage device timing, converts the audio data into text data, the converted text data, the text data stored in association with the text data about attributes of the user who inputs the speech data Conversion means stored in the device;
When a request for requesting provision of text data including user attributes is received from another service system that stores text data input from the user terminal and provides the text data to other user terminals, the requested text data is converted into the text data. Second providing means for reading from the storage device and transmitting to the other service system,
In the text data storage device, a telephone number and other user attributes are encrypted and stored. Each item of data included in the text data is associated with a flag that specifies whether the data can be disclosed,
3. The service system according to claim 2, wherein, when transmitting data in response to a request, the second providing unit transmits only data of items that can be disclosed by a flag in the text data. 4. When receiving a request for requesting provision of text data, a determination unit that determines whether or not the content of a specific item included in the request is included in the authentication data stored in the authentication data storage device,
4. The service system according to claim 2, wherein the second providing unit transmits requested data according to a determination result of the determining unit. 5. 5. The service system according to claim 4, wherein the authentication data is any one of an identifier of another person who requests provision of data, a predetermined password, or a part of a user attribute. The service system according to claim 4 or 5, further comprising: a registration unit that registers the authentication data in the authentication data storage device when the authentication data is newly input.

Images