Abstract:
An information processing apparatus includes: an record information obtaining mechanism which obtains record information representing a provision destination of one predetermined electronic information property by a terminal device relating to a provider of the electronic information property; a weighting mechanism which extracts the provision destination included in the obtained actual achievement information and performs weighting on the extracted provision destination based on a reference predetermined in accordance with the attribute of the provision destination; and an evaluation value calculating mechanism which calculates an evaluation value of the provider based on the weighted value.

Description:
CROSS-REFERENCE TO RELATED APPLICATION 
     The present application claims priority from Japanese Patent Application No. JP 2011-018633 filed in the Japanese Patent Office on Jan. 31, 2011, the entire content of which is incorporated herein by reference. 
     BACKGROUND 
     The present disclosure relates to an information processing apparatus, a method, and a program, and particularly to an information processing apparatus, a method, and a program which make it possible to enhance the added value of content distribution services. 
     Content distribution services based on a download scheme via a network have actively been used in the related art. According to such content distribution services, there is a case in which content is transmitted and received between mobile terminals of users in addition to a case in which content is downloaded from a server with the use of a user&#39;s mobile phone or the like, for example. 
     In addition, information which is called word-of-mouth information is exchanged on message boards and the like on the Internet. This word-of-mouth information is evaluation information regarding the services of shops, the qualities of products, the appeal of content, or the like, for example. 
     The word-of-mouth information is helpful as it is the opinions of persons who actually went to the shops, persons who bought the products, persons who viewed the content, and the like unlike the evaluation information described by magazine writers or experts, and is often referred to for the purchase of the products or services. 
     In addition, a technique has also been proposed in which viewing effects are measured by collecting the attributes of viewers (user information) from the wireless terminals of the viewers (see Japanese Unexamined Patent Application Publication No. 2010-41194, for example). With such a technique, it has become possible to more easily collect evaluation information. 
     SUMMARY 
     Incidentally, content including advertisements has been distributed for free, for example, as content distribution services have become widespread. 
     As the states of content distribution services have become diversified as described above, it is necessary to differentiate these services from the content distribution services in the related art in which a user simply pays for the desired content to be downloaded. 
     It is possible to enhance the added value of content distribution services if content is distributed with priority to users who have contributed to the improvement of the evaluation information in the market of content to be distributed, for example. 
     For example, viral marketing has attracted attention in recent years as a method of marketing with the use of so-called word-of-mouth information. 
     In viral marketing, existing users are encouraged to introduce original content or services to acquaintances to indirectly promote the original content or services via existing users. For this reason, the information regarding which users are to be encouraged is extremely important information for viral marketing. 
     It has been difficult to appropriately analyze which users efficiently introduce the provided contents or services to be promoted by a company, according to the word-of-mouth information in a message board on the Internet in the related art. 
     It is desirable to obtain useful information easily for viral marketing. 
     According to an embodiment of the present disclosure, there is provided an information processing apparatus including: a record information obtaining mechanism which obtains record information indicating a provision destination of one predetermined electronic information property by a terminal device relating to a provider of the electronic information property; a weighting mechanism which extracts the provision destination included in the obtained record information and performs weighting on the extracted provision destination based on a reference predetermined in accordance with the attribute of the provision destination; and an evaluation value calculating mechanism which calculates an evaluation value of the provider based on the weighted value. 
     According to the embodiment, a first terminal device as a terminal device relating to a provider of the electronic information property may include a device information receiving mechanism which receives identification information of a second terminal device relating to a provision destination of the electronic information property and information including an address of second communication from the second terminal device via first communication, and an electronic information property transmitting mechanism which transmits the electronic information property to the second terminal device via the second communication, wherein the record information may include identification information and attribute information of a user of the second terminal device included in information received via the first communication. 
     According to the embodiment, the weighting mechanism may perform weighting on the provision destination based on evaluation information with respect to the electronic information property which has been received by the second terminal device with the use of the second communication. 
     According to the embodiment, the weighting mechanism may perform the weighting on the provision destination based on at least one of a type of the electronic information property provided to the provision destination and the time point at which the electronic information property was provided. 
     According to the embodiment, the information processing apparatus may further include: an assigned group specifying mechanism which specifies an assigned group, to which a provider belongs, by specifying a user of the terminal device as a target of computation of the evaluation value based on a plurality of pieces of record information; and a provision destination group specifying mechanism which specifies a provision destination group by specifying a user of the terminal device to which the provider as the target of the computation of the evaluation value has newly provided the electronic information property based on the plurality of pieces of record information, wherein the assigned group specifying mechanism may specify first to n-th providing users while regarding the provider as the target of the computation of the evaluation value as a first providing user, regarding the specified user as a second providing user, and regarding a user who provided the electronic information property to the second providing user in the past as a third providing user, and wherein the provision destination group specifying mechanism may specify first to n-th provided users while regarding the specified user as a first provided user and regarding the user to which the first provided user provided the electronic information property in the past as a second provided user. 
     According to the embodiment, the evaluation value calculating mechanism may calculate the evaluation value based on the number of users who are not duplicated among users belonging to the specified assigned group and the provision destination group. 
     According to the embodiment, the record information may further include information relating to a user authentication scheme of the second terminal included in the information received via the first communication and the user authentication result of the second terminal. 
     According to the embodiment, the information processing apparatus may further include: a class specifying mechanism which specifies a reliability class indicating the reliability of a provider of a product or a service, a security class of the first terminal device, and a security class of the second terminal device based on the identification information of the first terminal device and the identification information of the second terminal device; and a link authentication mechanism which specifies a link authentication scheme in which it is confirmed that second communication is being continuously performed between the first terminal device and the second terminal device based on the specification result and executing processing relating to the link authentication based on the scheme, wherein the information relating to the user authentication result of the second terminal may include the result of the link authentication. 
     According to the embodiment, the link authentication mechanism may periodically function according to the specification result evaluator identity confirmation processing in which the identity of the second terminal device is confirmed by receiving information, which indicates whether or not information transmitted to the second terminal device with the use of the third communication has been transmitted to the first terminal device with the use of the second communication, from the first terminal device with the use of the third communication, and provider identity confirmation processing in which the identity of the first terminal device is confirmed by receiving information, which indicates whether or not the information transmitted to the first terminal device with the use of the third communication has been transmitted to the second terminal device with the use of the second communication, from the second terminal device with the use of the third communication. 
     According to the embodiment, the link authentication mechanism may specify the link authentication scheme by determining whether or not the provider identity confirmation processing is executed based on the reliability class. 
     According to the embodiment the link authentication mechanism may specify the link authentication scheme by determining whether a unique key stored in advance in the first terminal device or the second terminal device is used in the evaluator identity confirmation processing or the provider identity confirmation processing or whether a temporary key which is not stored in advance in the first terminal device or the second terminal device is used, based on the security class. 
     According to another embodiment of the present disclosure, there is provided an information processing method including: obtaining by a record information obtaining mechanism actual achievement information indicating a provision destination of one predetermined electronic information property by a terminal device relating to a provider of the electronic information property; extracting the provision destination included in the obtained record information and performing weighting on the extracted provision destination based on a reference predetermined in accordance with the attribute of the provision destination by a weighting mechanism; and calculating an evaluation value of the provider based on the weighted value by an evaluation calculating mechanism. 
     According to still another embodiment of the present disclosure, there is provided a program which causes a computer to function as an information processing apparatus including: a record information obtaining mechanism which obtains record information indicating a provision destination of one predetermined electronic information property by a terminal device relating to a provider of the electronic information property; a weighting mechanism which extracts the provision destination included in the obtained record information and performs weighting on the extracted provision destination based on a reference predetermined in accordance with the attribute of the provision destination; and an evaluation value computing mechanism which calculates an evaluation value of the provider based on the weighted value. 
     According to the embodiment, record information indicating a provision destination of one predetermined electronic information property by a terminal device relating to a provider of the electronic information property is obtained, the provision destination included in the obtained record information is extracted, the weighting is performed on the extracted provision destination in accordance with the attribute of the provision destination based on a predetermined reference, and an evaluation value of the provider is calculated based on the weighted value. 
     According to the present disclosure it is possible to further enhance the added value of the content distribution services. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         FIG. 1  is a diagram showing a configuration example of an evaluation information collecting system according to an embodiment of the present disclosure; 
         FIG. 2  is a diagram showing another configuration example of an evaluation information collecting system according to an embodiment of the present disclosure; 
         FIG. 3  is a block diagram showing a configuration example of a mobile terminal; 
         FIG. 4  is a block diagram showing a configuration example of a server; 
         FIG. 5  is a diagram showing an example of terminal device information; 
         FIG. 6  is a diagram illustrating an example of a scheme in which link authentication is performed to collect evaluation information; 
         FIG. 7  is an arrow chart illustrating a flow of processing based on the scheme of  FIG. 6 ; 
         FIG. 8  is a diagram illustrating another example of a scheme in which link authentication is performed to collect evaluation information; 
         FIG. 9  is an arrow chart illustrating a flow of processing based on the scheme of  FIG. 8 ; 
         FIG. 10  is a diagram illustrating still another example of a scheme in which link authentication is performed to collect evaluation information; 
         FIG. 11  is an arrow chart illustrating a flow of processing based on the scheme of  FIG. 10 ; 
         FIG. 12  is a diagram illustrating still another example of a scheme in which link authentication is performed to collect evaluation information; 
         FIG. 13  is a diagram illustrating still another example of a scheme in which link authentication is performed to collect evaluation information; 
         FIG. 14  is a diagram illustrating a handover message; 
         FIG. 15  is a diagram illustrating information for specifying a scheme for link authentication; 
         FIG. 16  is a flow chart illustrating an example of evaluation information collecting processing; 
         FIG. 17  is a flow chart illustrating an example of processing of Case  1 ; 
         FIG. 18  is a flow chart illustrating an example of processing of Case  2 ; 
         FIG. 19  is a flow chart illustrating an example of processing of Case  3 ; 
         FIG. 20  is a flow chart illustrating an example of processing of Case  3 ; 
         FIG. 21  is a flow chart illustrating an example of processing of Case  4 ; 
         FIG. 22  is a flow chart illustrating an example of processing of Case  4 ; 
         FIG. 23  is a flow chart illustrating an example of processing of Case  5 ; 
         FIG. 24  is a flow chart illustrating an example of processing of Case  5 ; 
         FIG. 25  is a flow chart illustrating an example of processing by a terminal device on the side of a provider; 
         FIG. 26  is a flow chart illustrating an example of content provision processing; 
         FIG. 27  is a flow chart illustrating an example of link authentication processing; 
         FIG. 28  is a flow chart illustrating another example of processing by a terminal device on the side of a provider; 
         FIG. 29  is a flow chart illustrating another example of link authentication processing; 
         FIG. 30  is a flow chart illustrating an example of processing by a terminal device on the side of an evaluator; 
         FIG. 31  is a flow chart illustrating an example of first link authentication processing; 
         FIG. 32  is a flow chart illustrating an example of second link authentication processing; 
         FIG. 33  is a flow chart illustrating an example of content evaluation processing; 
         FIG. 34  is a flow chart illustrating another example of processing by a terminal device on the side of an evaluator; 
         FIG. 35  is a flow chart illustrating an example of third link authentication processing; 
         FIG. 36  is a flow chart illustrating an example of fourth link authentication processing; 
         FIG. 37  is a diagram showing a configuration example of a content distribution system according to an embodiment of the present disclosure; 
         FIG. 38  is a diagram showing an example of record information; 
         FIG. 39  is a diagram showing another example of a handover message; 
         FIG. 40  is a diagram showing another configuration example of a content distribution system according to an embodiment of the present disclosure; 
         FIG. 41  is a diagram showing an example of a network map created by regarding respective mobile terminals in the record information as nodes; 
         FIG. 42  is a diagram illustrating a scheme for specifying a user as a connector; 
         FIG. 43  is a flow chart illustrating an example of server processing according to the embodiment of  FIG. 37 ; and 
         FIG. 44  is a flow chart illustrating an example of server processing according to the embodiment of  FIG. 40 . 
     
    
    
     DETAILED DESCRIPTION OF EMBODIMENTS 
     Hereinafter, description will be given of embodiments of the present disclosure with reference to the drawings. 
     According to the present disclosure, evaluation information is collected with the use of a handover function of a mobile terminal, for example. 
     For example, a mobile terminal configured as a mobile phone has a near-field wireless communication mechanism such as Bluetooth (registered trademark), WiFi (registered trademark), or the like in some cases. In such cases, the mobile phones can directly (locally) communicate with each other. Moreover, when mobile phones are provided with non-contact communication (NFC: Near Field Communication) devices, connection authentication is performed by the non-contact communication devices by the users causing the mobile phones to approach (or contact) each other, whereby the near-field wireless communication becomes available. The function by which the connection authentication is performed by the non-contact communication devices to make the near-field wireless communication possible is referred to as handover. 
     With the use of such a handover function, the user can receive provided service or purchase a product simply by touching the mobile phones. When the user purchases content as a product, the user can download the data of the content onto the mobile terminal through the near-field wireless communication simply by touching the mobile phones. 
       FIG. 1  is a diagram showing a configuration example of an evaluation information collecting system according to an embodiment of the present disclosure. In the example of the drawing, an evaluation information collecting system  10  includes a server  21 , information collecting terminals  31  to  33 , and mobile terminals  41  to  43 . 
     The server  21  is installed at a data center of a business operator of collecting evaluation information, obtains the evaluation information transmitted from the information collecting terminals  31  to  33 , and performs processing such as storage, modification, and the like of the obtained evaluation information. The server  21  performs processing such as the sorting of the obtained information into each type of a product or a service as the target of evaluation and the provision of the classified information to a user who accesses via the network. 
     The information collecting terminals  31  to  33  are terminals which respectively communicate by the handover functions of the mobile terminals  41  to  43 , and are configured to include near-field wireless communication mechanisms and non-contact communication devices. 
     For example, the information collecting terminal  31  is configured as a device which provides trial-listening services of music content. When the user causes a mobile terminal  41  to touch a predetermined region, for example, the information collecting terminal  31  transmits a part of data of the content via the near-field wireless communication after the non-contact communication and causes the mobile terminal  41  to perform streaming reproduction of the content. In so doing, the user can listen to the content as a trial by putting on a headset connected to the mobile terminal  41 . 
     In addition, the information collecting terminal  32  is configured as a device such as a POS terminal used in a restaurant, for example. When the user causes the mobile terminal  42  to touch a predetermined region, the information collecting terminal  32  transmits GUI data such as a menu, an order format, or the like via the near-field wireless communication after the non-contact communication, and causes the mobile terminal  42  to display the GUI data. In so doing, the user can order a desired menu or answer questionnaire and get bonus points by the mobile terminal  42 . 
     The information collecting terminal  33  is configured as a device such as a wireless communication hub installed at a predetermined area such as a shopping mall, an entertainment park, or the like. When the user causes the mobile terminal  43  to touch a predetermined region, the information collecting terminal  33  transmits data of game content via the near-field wireless communication after the non-contact communication. In so doing, the user can enjoy the game by the mobile terminal  43 . 
     Each of the information collecting terminals  31  to is provided with a broad area communication mechanism, which is for communicating with the server  21 , as well as the near-field wireless communication mechanism and the non-contact communication device. As the broad area communication mechanism, a wireless communication device can be exemplified which performs wireless communication with the nearest wires base station to perform communication via the mobile communication network. Alternatively, another configuration is also applicable in which connection with the server  21  can be made via a dedicated line. 
     The mobile terminals  41  and  42  are configured as mobile phones, for example. The mobile terminal  43  is configured as a game device, for example. The mobile terminals  41  to  43  are terminals which respectively communicate by the handover function, and are configured to include the near-field wireless communication mechanisms and the non-contact communication devices. In addition to them, the mobile terminals  41  to  43  include wireless communication devices which perform wireless communication with the nearest wireless base station to perform communication via the mobile communication network. 
     In the example of  FIG. 1 , the information accumulated in the information collecting terminal  31  such as the number of times of the reproduction orders of the content, the attribute information of the user of the mobile terminal  41 , which is obtained via the non-contact communication, or the like is transmitted to the server  21  as the evaluation information. 
     For example, the information accumulated in the information collecting terminal  32  such as the number of times of the orders for each menu, the answer to the questionnaire, or the like is transmitted to the server  21  as the evaluation information. 
     Moreover, the information accumulated in the information collecting terminal  33  such as the operation information in the game or the like is transmitted to the server  21  as the evaluation information, for example. 
     As described above, the evaluation information is transmitted from the information collecting terminals  31  to  33  to the server  21  with the use of the broad area communication mechanisms. 
       FIG. 2  is a diagram showing another configuration example of an evaluation information collecting system according to an embodiment of the present disclosure. In the example of the drawing, the evaluation information collecting system  10  includes a server  21  and mobile terminals  44  to  47 . 
     The mobile terminals  44  to  47  are respectively configured as mobile phones in the same manner as the mobile terminals  41  and  42  in  FIG. 1 . In the case of  FIG. 2 , the users of the mobile terminals  45  and  47  are providers of the content, respectively, and the users of the mobile terminals  44  and  46  are the evaluators of the content, respectively. 
     In the example of  FIG. 2 , the server  21  is installed at a data center of a business operator of collecting evaluation information in the same manner, obtains the evaluation information transmitted from the mobile terminals  45  and  47 , and performs processing such as the storage, the modification, and the like of the obtained evaluation information. 
     For example, it is assumed that the user of the mobile terminal  45  downloads to the mobile terminal  45  the data of music content that the user desires to introduce to friends. When the mobile terminals  44  are brought to be in contact with the mobile terminal  45 , the data of the content from the mobile terminal  45  is transmitted via the near-field wireless communication after the non-contact communication, and the mobile terminal  44  is caused to perform streaming reproduction of the content. In so doing, the user of the mobile terminal  44  can listen to the content as a trial by putting on a headset or the like. Then, the user of the mobile terminal  44  transmits the evaluation of the music (Brief comment or the like, for example) to the mobile terminal  45  via the near-field wireless communication. 
     For example, it is assumed that the user of the mobile terminal  47  enjoys a network game and desires that a friend who is the user of the mobile terminal  46  also join this network game. When the mobile terminals  46  and  47  are brought to be in contact, the data of the game is transmitted from the mobile terminal  47  via the near-field wireless communication after the non-contact communication, and the mobile terminal  46  is caused to display the screen and the like of the game. 
     In so doing, the user of the mobile terminal  46  can join the network game that the user of the mobile terminal  47  enjoys. In addition, information such as the profile of the user, the operation information of the game, and the like are transmitted from the mobile terminal  46  to the mobile terminal  47  via the near-field wireless communication. 
     In the case of  FIG. 2 , the information accumulated in the mobile terminal  45  such as the comment for music or the like is transmitted to the server  21  as the evaluation information, for example. 
     In addition, the information accumulated in the mobile terminal  47  such as the operation information of a game or the like is transmitted to the server  21  as the evaluation information, for example. 
     The evaluation information from the mobile terminals  45  and  47  to the server  21  is transmitted with the use of the broad area communication mechanisms. 
     As described above, the evaluation information collecting system  10  according to the present disclosure does not place weight on collected evaluation information based on the user comment, and it is also possible to collect the information such as the user&#39;s record of trial listening for the content, for example, as the evaluation information. 
       FIG. 3  is a block diagram showing a configuration example of a mobile terminal in  FIG. 1 or 2 . Although the drawing shows the configuration of the mobile terminal  41 , it is also possible to apply the configuration of the drawing to the mobile terminals  42  to  47 . 
     In  FIG. 3 , the CPU (Central Processing Unit)  111  of the mobile terminal  41  executes various kinds of processing based on the program stored on the ROM (Read Only Memory)  112  or the program loaded on the RAM (Random Access Memory)  113  from the storage unit  123 . The RAM  113  appropriately stores data which is necessary for the CPU  111  to execute various kinds of processing. 
     The CPU  111 , the ROM  112 , and the RAM  113  are connected to each other via the bus  114 . The input and output interface  120  is also connected to the bus  114 . 
     To the input and output interface  120 , an input unit  121  including a keyboard, a mouth, and the like, a display including an LCD (Liquid Crystal Display) and the like, an output unit  122  including a speaker and the like, and a storage unit  123  configured by a hard disk, a flash memory, or the like are connected. 
     A drive  125  is also connected to the input and output interface  120 , if necessary, a removable medium  126  such as a magnetic disk, an optical disc, a magneto-optical disc, or a semiconductor memory is appropriately mounted thereon, and a computer program read from the removable medium  126  is installed on the storage unit  123 , if necessary. 
     A mobile communication wireless communication unit  131 , a near field communication unit  132 , and a non-contact communication unit  133  are further connected to the input and output interface  120 . 
     The mobile communication wireless communication unit  131  is a wireless communication device which performs wireless communication with a wireless base station which is not shown in the drawing and performs communication via the mobile communication network. The mobile communication wireless communication unit  131  uses a frequency band of 2 GHz, for example, and is used not only for the telephone call application but also for various communication applications such as the Internet connection and the like with the use of the data communication of 2 Mbps at a maximum. For example, the wireless communication by the mobile communication wireless communication unit  131  is used for downloading the content data, for the communication with the server  21 , and the like. In addition, the mobile communication wireless communication unit  131  is assumed to be configured as a device or the like capable of communicating based on a communication scheme of a so-called third generation mobile phone. 
     The near field communication unit  132  is a near-field wireless communication device such as Bluetooth (registered trademark, referred to as a BT) or IEEE (Institute of Electrical and Electronic Engineers) 802.11x. Here, the near-field wireless communication means local (narrow area) wireless communication in which the communicable maximum distance is about several meters to several tens of meters. An arbitrary communication standard can be used. For example, when the near field communication unit  132  performs communication of BT, the communication at the maximum communication rate 3 Mbit/second (Version 2.0+EDR or later versions) is performed in the band of 2.4 GHz via an antenna. 
     The non-contact communication unit  133  is an NFC (Near Field Communication) device. Hear, the non-contact communication means local (narrow area) wireless communication in which the communicable maximum distance is about several tens of cm. An arbitrary communication standard can be used. For example, the non-contact communication unit  133  uses a frequency in the band of 13.56 MHz via an antenna and performs communication at a communication rate of 424 Kbit/second at a maximum in the extremely short distance of about 10 cm. 
     The non-contact communication by the non-contact communication unit  133  is used for sending and receiving the information which is necessary for establishing the near-field wireless communication connection by the near field communication unit  132  and the message in which a list or the like of the transmittable content to and from the mobile terminal whose case body is brought to be in contact or placed nearby. 
     Each part of the mobile terminal  41  is controlled by the CPU  111 . The execution binary code of the control program is stored on the ROM  112  or the storage unit  123 , and the stack and the heap regions for various kinds of computation processing are expanded on the RAM  113 . 
     In addition, since the information collecting terminals  31  to  33  are configured in the same manner as in the example of  FIG. 3 , the detailed description thereof will be omitted. 
       FIG. 4  is a block diagram showing a configuration example of a server in  FIG. 1 or 2 . 
     As shown in the drawing, the server  21  includes a CPU  201 , a ROM  202 , and a RAM  203  which are connected to each other via the bus  204 , in the same manner as in the case of the mobile terminal  41 . In addition, an input and output interface  210  is connected to the bus  204 . 
     To the input and output interface  210 , an input unit  211 , an output unit  212 , a storage unit  213 , a driver  215  for a removable medium  216  are connected in the same manner as in the case of the mobile terminal  41 . 
     The CPU  201 , the ROM  202 , the RAM  203 , the bus  204 , the input and output interface  210 , the input unit  211 , the output unit  212 , the storage unit  213 , the drive  215 , and the removable medium  216  in  FIG. 4  correspond to the CPU  111 , the ROM  112 , the RAM  113 , the bus  114 , the input and output interface  120 , the input unit  121 , the output unit  122 , the storage unit  123 , the drive  125 , and the removable medium  126  in  FIG. 2 , respectively. 
     The server  21  also includes a communication unit  214  connected to the input and output interface  210 . The communication unit  214  is a communication device which performs communication with other devices via the network. For example, the communication unit  214  is connected to the mobile communication network via the wired network and used for the communication with a mobile terminal or an information collecting terminal. 
     To the input and output interface  210 , an evaluation information database  221  and the terminal device database  222  are further connected. 
     The evaluation information database  221  stores the evaluation information transmitted from a mobile terminal or an information collecting terminal. The evaluation information database  221  classifies the evaluation information into the types of products or services as the targets of the evaluation and organizes the information as the database such that it is possible to search for the identification information of the products, the identification information of the evaluators, the evaluation date, and the like as keys, if necessary. 
     The terminal device database  222  store the information (terminal device information) relating to a communication function of a mobile terminal or an information collecting terminal (appropriately referred to as a terminal device) for each terminal. 
       FIG. 5  is a diagram showing an example of information stored on the terminal device database  222 . The drawing shows an example of the terminal device information of the mobile terminal with a predetermined identification number, for example. 
     The “type of broad area communication” shown in  FIG. 5  is the information for specifying the type of the broad area communication mechanism of the mobile terminal, in which the information such as 3G (IMT-2000), WiMAX (Worldwide Interoperability for Microwave Access), or the like are described, for example. 
     In the “broad area communication address”, the information for specifying the address for communicating with the user of the aforementioned broad area communication mechanism is described. 
     The “near-field wireless communication type” is the information for specifying the type of the near-field wireless communication mechanism of the mobile terminal, in which the information such as Bluetooth (registered trademark), Wi-Fi, or the like is described. 
     In the “near-field wireless communication address”, the information for specifying the address for communicating with the use of the aforementioned near-field wireless communication mechanism is described. 
     The “non-contact communication scheme” is the information for specifying the communication scheme available by the non-contact communication by the mobile terminal, and the information such as “only data response”, “only data obtaining”, or “data communication available” is described. 
     The “unique key” is the information representing a secret key stored in advance on the mobile terminal. When the mobile terminal includes a security module, the information of the key which is necessary for the access to the security module is described. 
     The “provider sorting” is the information for specifying whether or not the mobile terminal is the mobile terminal of the provider of the products or the services or the information for specifying the scheme of the provision of the products or the services, and the information representing it is described. 
     As described above, the terminal device information of the information collecting terminal  31 , the terminal device information of the information collecting terminal  32 , . . . the terminal device information of the mobile terminal  41 , the terminal device information of the mobile terminal  42 , . . . are stored on the mobile device database  222  of the server  21 . That is, the terminal device database  222  stores the terminal device information of the terminal devices which can join the valuation information collecting system  10  so as to correspond to the respective identification information. 
     As described above, according to the evaluation information collecting system  10  of the present disclosure, the evaluation information is collected with the use of the handover functions of the mobile terminals. The evaluation information collected with the use of the handover functions is the evaluation information obtained in the state in which the provider of the products or the services is in the extremely close relationship with the evaluator. This is because the connection authentication is performed by the non-contact communication devices of the mobile terminals placed nearby to perform the near-field wireless communication according to the handover functions. 
     The thus collected evaluation information is helpful as opinions of persons who actually receive the products or the services, and it is considered that the evaluation information can be referred to for the purpose of the products or the services. This is because the evaluation information collected with the use of the handover functions is considered to be the evaluation of the users, who actually receive the products or the services, as it is unlike the articles in the magazine which introduce the products or the services. In addition, the evaluation information collected with the use of the handover functions is not collected from the persons who do not actually receive the products or the services unlike the information written in message boards on the Internet. 
     When the evaluation information is collected with the use of the handover functions, however, it is difficult to prove that the evaluation information is really the information which has been collected with the use of the handover functions when the evaluation information is collected with the use of the handover functions. That is, it is understood that the evaluation information collected with the use of the handover functions is helpful just because the evaluation information has been collected immediately after the reception of the products or the services via the near-field wireless communication as described above. For example, when the evaluation information is collected from mobile terminals or the information collecting terminals by the server  21  based on the batch scheme, it is difficult to remove a doubt that only the evaluation information which is advantageous for the provider of the products or the services is transmitted or a doubt that the evaluation information is fake. 
     Of course, it is considered that business operators of collecting evaluation information try to honestly collect information; however, a person who refers to the evaluation information may think that some impropriety has occurred when the evaluation of a specific product is extremely good as compared with that of other products. Moreover, if the transmission of the evaluation information is failed or the evaluation information which has already been transmitted is repeatedly transmitted due to the trouble of the software or the like even when the provider of the products or the services does not meant to do so, incorrect evaluation is formed as a result. If such a situation occurs, the evaluation relating to the reliability of the evaluation information supplied by the server  21  is significantly lowered thereafter. 
     Thus, the present disclosure makes it possible to confirm that the near-field wireless communication is continuously performed between the mobile terminal or the information collecting terminal of the provider and the mobile terminal of the evaluator when the server  21  collects the evaluation information. In so doing, it is possible to prove that the evaluation information has been collected immediately after receiving the products or the services. 
     According to the present disclosure, the server  21  is immediately notified of the handover between the mobile terminal or the information collecting terminal of the provider and the mobile terminal of the evaluator although the detail thereof will be described later. In addition, the server  21  accesses the mobile terminal or the information collecting terminal of the provider with the use of the broad area communication mechanism, for example, to confirm that the near-field wireless communication with the mobile terminal of the same evaluator is continuously performed. 
     For example, it is possible to confirm that the near-field wireless communication with the mobile terminal of the same evaluator is continuously performed as follows. When the notification of the handover is made, predetermined authentication information is transmitted from the server  21  to the mobile terminal of the evaluator, and it is confirmed that the authentication information has been transmitted from the mobile terminal of the evaluator in the near-field wireless communication after the handover. In addition, the confirmation of the fact that the near-field wireless communication with the mobile terminal of the same evaluator is continuously performed will be referred to as link authentication. 
       FIG. 6  is a diagram illustrating an example of a scheme in which link authentication is performed to collect evaluation information in the evaluation information collecting system  10 . The drawing shows an example in which the handover is performed between the information collecting terminal  31  and the mobile terminal  41 , a part of the content data is transmitted via the near-field wireless communication (BT) after the non-contact communication (NFC communication), and the streaming reproduction is performed. 
     In the example of the drawing, the information collecting terminal  31  notifies the server  21  of the handover between the information collecting terminal  31  and the mobile terminal  41  with the use of the broad area communication. At this time, the identification number of the information collecting terminal  31  and the identification number of the mobile terminal  41  are also transmitted to the server  21 . Then, the server  21  generates random number and encrypts the random number using a unique key of the mobile terminal  41 . In addition, it is possible to obtain the unique key of the mobile terminal  41  by searching for the terminal device database  222  with the use of the identification number of the mobile terminal  41 . 
     The server  21  transmits the random number which has been encrypted (referred to as encrypted random number) to the broad area communication address of the information collecting terminal  31 . In addition, it is possible to obtain the broad area communication address of the information collecting terminal  31  by searching for the terminal device database  222  using the identification number of the information collecting terminal  31 . 
     The information collecting terminal  31  transmits the encrypted random number transmitted from the server  21  to the mobile terminal  41  via the near-field wireless communication. 
     The mobile terminal  41  decodes the encrypted random number with the own unique key to obtain the random number. Then, the mobile terminal  41  transmits the random number to the information collecting terminal  31  via the near-field wireless communication. 
     The information collecting terminal  31  transmits the random number transmitted from the mobile terminal  41  to the server  21  via the broad area communication. 
     The server  21  compares the random number transmitted from the information collecting terminal  31  with the random number generated by the server  21  and confirms that the near-field wireless communication with the evaluator at the time of the handover is being performed when both random numbers are coincident with each other. That is, it is possible to confirm the identity of the evaluator. 
     Thereafter, a part of the content data is transmitted from the information collecting terminal  31  via the near-field wireless communication, and the streaming reproduction of the content is performed by the mobile terminal  41 . The mobile terminal  41  transmits the evaluation information to the information collecting terminal  31  at this time. 
     While the content data and the evaluation information are transmitted via the near-field wireless communication between the information collecting terminal  31  and the mobile terminal  41 , the server  21  continuously (periodically) confirms the identity of the evaluator as described above at a constant cycle, for example. 
     Then, the evaluation information accumulated in the information collecting terminal  31  is transmitted to the server  21  via the broad area communication. 
     In so doing, the link authentication is performed in the evaluation information collecting system  10  to collect the evaluation information. 
       FIG. 7  is an arrow chart illustrating a flow of processing of performing the aforementioned link authentication with reference to  FIG. 6  to collect the evaluation information. 
     In the drawing, the mobile communication wireless communication unit  131  of the information collecting terminal  31  of the mobile communication wireless communication unit  131  is described as 3G131-1 while the mobile communication wireless communication unit  131  of the mobile terminal  41  is described as 3G131-2. In addition, the near field communication unit  132  of the information collecting terminal  31  is described as BT132-1 while the near field communication unit  132  of the mobile terminal  41  is described as BT132-2. Moreover, the non-contact communication unit  133  of the information collecting terminal  31  is described as NFC133-1 while the non-contact communication unit  133  of the mobile terminal  41  is described as NFC133-2. 
     In addition, the 3G here is based on a communication scheme of a digital mobile phone such as a W-CDMA scheme, a CDMA2000 scheme, or the like and means a so-called third generation mobile phone (3G). 
     The NFC133-1 of the information collecting terminal  31  transmits the handover message in Step S 11 , and the NFC133-2 of the mobile terminal  41  receives the handover message in Step S 101 . 
     The NFC133-2 transmits the handover message in Step S 102 , and the NFC133-1 receives the handover message in Step S 12 . 
     By the above processing, the other device information is exchanged by the information collecting terminal  31  and the mobile terminal  41 . In addition, the other device information includes the identification number of the device as the counterpart of the handover, the near-field wireless communication address, and the like. 
     The NFC133-1 notifies the BT132-1 of the other device information in Step S 13 , and the BT132-1 receives the other device information in Step S 31 . In addition, the NFC133-2 notifies the BT132-2 of the other device information in Step S 103 , and the BT132-2 receives the other device information in Step S 121 . In practice, the other device information and other information are notified via the CPU  111 . The same is true in the following process. 
     The NFC133-1 notifies the 3G131-1 of the other device information in Step S 14 , and the 3G131-1 receives the other device information in Step S 51 . 
     The 3G131-1 performs the notification of the handover by transmitting the information including the other device information to the server  21  in Step S 52 , and the server  21  obtains the notification in Step S 71 . When the server  21  is notified of the handover, not only the other device information of the counterpart of the handover but also the other device information of its own (in this case, the information collecting terminal  31 ) is transmitted. 
     The BT132-1 transmits a BT connection request to the BT132-2 in Step S 32 , and the BT132-2 receives the BT connection request in Step S 122 . 
     The server  21  generates a random number in Step S 72  and encrypts the random number in Step S 73 . The server  21  transmits the encrypted random number obtained in the processing of Step S 73  as a confirmation request in Step S 74 , and the 3G131-1 receives the encrypted random number in Step S 53 . 
     The 3G131-1 notifies the BT132-1 of the confirmation request, which has been received in Step S 53 , in Step S 54  and the BT132-1 receives the confirmation request in Step S 33 . 
     The BT132-1 transmits the confirmation request, which has been received in Step S 33 , in Step S 34 , and the BT132-2 receives the confirmation request in Step S 123 . 
     The BT132-2 decodes the encrypted random number of the confirmation request, which has been received in Step S 123 , in Step S 124  to obtain the random number. In addition, the encrypted random number is decoded by the CPU  111  in practice. 
     The BT132-2 transmits the random number obtained in the processing of Step S 124  as the confirmation request in Step S 125 , and the BT132-1 receives the random number in Step S 35 . 
     The BT132-1 notifies the 3G131-1 of the confirmation request, which has been received in Step S 35 , in Step S 36 , and the 3G131-1 obtains the confirmation request in Step S 55 . 
     The 3G131-1 transmits the confirmation request, which has been obtained in Step S 55 , in Step S 56 , and the server  21  receives the confirmation request in Step S 75 . 
     The content data is transmitted and received in Step S 37  and Step S 126 , and the operation information as the evaluation information is transmitted and received in Step S 127  and Step S 38 . 
     The BT132-1 notifies the 3G131-1 of the evaluation information in Step S 39  and the 3G131-1 receives the evaluation information in Step S 57 . 
     The 3G131-1 transmits the evaluation information, which has been obtained in Step S 57 , in Step S 58 , and the server  21  receives the evaluation information in Step S 76 . 
     The processing of the part surrounded by the dotted line in the drawing is periodically executed as the processing for confirming the identity of the evaluator. 
     As described above, the link authentication is performed, and the processing of collecting the evaluation information is executed. 
     Although the subjects which execute each step in the arrow chart were expressed as the 3G131-1, the BT132-1, . . . and the like in this example as appropriately described in the explanation of  FIG. 7 , the expressions were given only for the purpose of convenience. That is, such expressions were given to facilitate understanding of on which communication scheme the information transmitted or received in each step is based since three types of communication schemes including the non-contact communication, the near-field wireless communication, and the broad area communication are used in the present disclosure. Accordingly, the processing relating to each step is executed by the CPU  111  or the like in practice. The same is true in the following arrow charts. 
     Although the description was made of a case in which the mobile terminal  41  holds the unique key in the example described above with reference to  FIG. 6 , there is also a case in which the mobile terminal  41  does not hold a unique key. In such a case, it is possible to confirm the identity of the evaluator as shown in  FIG. 8 , for example. 
       FIG. 8  is a diagram illustrating another example of a scheme in which the link authentication is performed to collect the evaluation information in the evaluation information collecting system  10 . The drawing shows a case in which the handover is performed between the information collecting terminal  31  and the mobile terminal  41 , a part of the content data is transmitted via the near-field wireless communication (BT) after the non-contact communication (NFC communication), and the streaming reproduction is performed. In the case of the example of  FIG. 8 , the mobile terminal  41  does not hold a unique key unlike the case of  FIG. 6 . 
     In the case of the example of  FIG. 8 , the information collecting terminal  31  notifies the server  21  of the handover between the information collecting terminal  31  and the mobile terminal  41  via the broad area communication. At this time, the identification number of the information collecting terminal  31  and the identification number of the mobile terminal  41  are also transmitted to the server  21 . Then, the server  21  generates random number and confirms that the mobile terminal  41  does not hold a unique key. It is possible to confirm that the mobile terminal  41  does not hold a unique key, by searching for the terminal device database  222  with the use of the identification number of the mobile terminal  41 . 
     The server  21  transmits the random number to the broad area communication address of the mobile terminal  41  as a temporary key. In addition, it is possible to obtain the broad area communication address of the mobile terminal by searching for the mobile device database  222  with the use of the identification number of the mobile terminal  41 . 
     The server  21  transmits the confirmation request to the broad area address of the information collecting terminal  31 , and the information collecting terminal  31  delivers the confirmation request to the mobile terminal  41  via the near-field wireless communication. 
     The mobile terminal  41  transmits the temporary key as the response to the confirmation request to the information collecting terminal  31  via the near-field wireless communication, and the information collecting terminal  31  delivers the response to the server  21  via the broad band communication. 
     The server  21  compares the temporary key transmitted from the information collecting terminal  31  with the random number generated by the information collecting terminal  31  and confirms that the near-field wireless communication with the evaluator at the time of the handover is being performed when both are coincident. That is, it is possible to confirm the identity of the evaluator. 
     Thereafter, a part of the content data is transmitted from the information collecting terminal  31  via the near-field wireless communication, and the mobile terminal  41  performs the streaming reproduction of the content. At this time, the mobile terminal  41  transmits the evaluation information to the information collecting terminal  31 . 
     While the content data and the evaluation information are transmitted via the near-field wireless communication between the information collecting terminal  31  and the mobile terminal  41  as described above, the server continuously (periodically) confirms the identity of the evaluator as described above at a constant cycle, for example. 
     Then, the evaluation information accumulated in the information collecting terminal  31  is transmitted to the server  21  via the broad area communication. 
     In so doing, the link authentication is performed, and the evaluation information is collected in the evaluation information collecting system  10  even when the mobile terminal  41  does not hold the unique key. 
       FIG. 9  is an arrow chart illustrating a flow of processing of performing the aforementioned link authentication with reference to  FIG. 8  to collect the evaluation information. 
     The NFC133-1 of the information collecting terminal  31  transmits the handover message in Step S 11 , and the NFC133-2 of the mobile terminal  41  receives the handover message in Step S 101 . 
     The NFC133-2 transmits the handover message in Step S 102 , and the NFC133-1 receives the handover message in Step S 12 . 
     By the above processing, the other device information is exchanged between the information collecting terminal  31  and the mobile terminal  41 . In addition, the other device information is the information such as the identification number of the device as the counterpart of the handover, the near-field wireless communication address, and the like. In addition, the other device information includes the broad area communication address of the server  21 , if necessary. 
     The NFC133-1 notifies the BT132-1 of the other device information in Step S 13 , and the BT132-1 receives the other device information in Step S 31 . In addition, the NFC133-2 notifies the BT132-2 of the other device information in Step S 103 , and the BT132-2 receives the other device information in Step S 121 . 
     The BT132-2 notifies the 3G131-2 of the other device information, which has been obtained in Step S 121 , in Step S 122 , and the 3G131-2 receives the other device information in Step S 141 . In addition, the processing of Steps S 122  and S 141  may be omitted. 
     The NFC133-1 notifies the 3G131-1 of the other device information in Step S 14 , and the 3G131-1 receives the other device information in Step S 51 . 
     The 3G131-1 notifies the server  21  of the handover by transmitting the information including the other device information to the server  21  in Step S 52 , and the server  21  obtains the handover in Step S 71 . When the server  21  is notified of the handover, not only the other device information of the counterpart of the handover but also the other device information of its own (in this case, the information collecting terminal  31 ) is transmitted. 
     The BT132-1 transmits the BT connection request to the BT132-2 in Step S 32 , and the BT132-2 receives the BT connection request in Step S 123 . 
     The server  21  generates a random number in Steps S 72  and S 73  as a temporary key. The server  21  transmits the temporary key obtained in the processing of Step S 73  in Step S 74 , and the 3G131-2 receives the temporary key in Step S 142 . 
     The 3G131-2 notifies the BT312-2 of the temporary key, which has been received in Step S 142 , in Step S 143 , and the BT312-2 receives the temporary key in Step S 124 . 
     The server  21  transmits the confirmation request in Step S 75 , and the 3G131-1 receives the confirmation request in Step S 53 . 
     The 3G131-1 notifies the BT132-1 of the confirmation request, which has been received in Step S 53 , in Step S 54 , and the BT132-1 obtains the confirmation request in Step S 33 . 
     The BT132-1 transmits the confirmation request, which has been obtained in Step S 33 , in Step S 34 , and the BT132-2 receives the confirmation request in Step S 125 . 
     The BT132-2 transmits the temporary key, which has been obtained in Step S 124 , as the response to the confirmation request, which has been received in Step S 125 , in Step S 126 , and the BT132-1 receives the temporary key in Step S 35 . 
     The BT132-1 notifies the 3G131-1 of the confirmation response, which has been received in Step S 35 , in Step S 36 , and the 3G131-1 obtains the confirmation response in Step S 55 . 
     The 3G131-1 transmits the confirmation response, which has been obtained in Step S 55 , in Step S 56 , and the server  21  receives the confirmation response in Step S 76 . 
     Although the content data and the operation information as the evaluation are transmitted or received thereafter, such processing is the same as that in the case described above with reference to  FIG. 7 , and therefore, the detailed description thereof will be omitted. 
     The processing in the part surrounded by a dotted line in the drawing is periodically executed as the processing for confirming the identity of the evaluator. 
     As described above, the processing of performing the link authentication to collect the evaluation information is executed. 
     Incidentally, in the example described above with reference to  FIG. 6  and the example described above with reference to  FIG. 8 , the link authentication is performed based on the information obtained only from the information collecting terminal  31 . However, such scheme does not effectively function in some cases when there is no sufficiently confidential relationship between the business operator of collecting evaluation information or the like who administers the server  21  and the content provider which administers the information collecting terminal  31 . In order to represent that the content provider which administers the information collecting terminal  31  is worthy of trust, the description of “Trusted” is added to the information collecting terminal  31  in  FIGS. 6 and 8 . 
     For example, when the content provider is not worthy of trust, it is not possible to believe that the random number decoded and obtained by the mobile terminal  41  and the temporary key received by the mobile terminal  41  via the broad area communication have been transmitted as they are to the server  21 . That is, it is difficult to deny the possibility that the information collecting terminal  31  has faked the confirmation response transmitted in Step S 56  of  FIG. 7  and in Step S 56  of  FIG. 9 . 
     For this reason, the confirmation of the identity of the evaluator based on the information transmitted from the provider side is not enough, and it is necessary to further confirm the identity of the provider based on the information transmitted from the evaluator side when there is no sufficiently confidential relationship between the business operator of collecting evaluation information or the like and the content provider. That is, it is difficult to deny the possibility that the provider pretends to be the evaluator, for example, and therefore, it is necessary to confirm that the provider and the evaluator are continuously performing the near-field wireless communication at the time of the handover from both the provider side and the evaluator side. 
       FIG. 10  is a diagram illustrating still another example of a scheme in which link authentication is performed to collect evaluation information in the evaluation information collecting system  10 . The drawing shows an example in which the handover is performed between the mobile terminal  47  and the mobile terminal  46  and the content (a game, for example) data is transmitted via the near-field wireless communication (BT) after the non-contact communication (NFC communication). 
     In the case of the example in  FIG. 10 , the description of “Trusted” is not added to the mobile terminal  47  as a content provider unlike the case of  FIG. 6 or 8 . That is, there is no sufficiently confidential relationship between the business operator of collecting evaluation information or the like and the content provider in the case of the example in  FIG. 10 . In the example of the drawing, both the mobile terminal  46  and the mobile terminal  47  hold unique keys. 
     In the example of  FIG. 10 , the mobile terminal  47  notifies the server  21  of the handover between the mobile terminal  47  and the mobile terminal  46  via the broad area communication. At this time, the identification numbers of the mobile terminal  47  and the mobile terminals  46  are also transmitted to the server  21 . Then, the server  21  generates a random number and encrypts the random number using the unique key of the mobile terminal  46 . In addition, the unique key of the mobile terminal  46  can be obtained by searching for the terminal device database  222  with the use of the identification number of the mobile terminal  46 . 
     The server  21  transmits the random number which has been encrypted (referred to as an encrypted random number) to the broad area communication address of the mobile terminal  47 . The broad area communication address of the mobile terminal  47  can be obtained by searching for the terminal device database  222  using the identification number of the mobile terminal  47 . 
     The mobile terminal  47  transmits the encrypted random number, which has been transmitted from the server  21 , to the mobile terminal  46  via the near-field wireless communication. 
     The mobile terminal  46  decodes the encrypted random number with its own unique key to obtain the random number. Then, the mobile terminal  46  transmits the random number to the mobile terminal  47  via the near-field wireless communication. 
     The mobile terminal  46  transmits the random number, which has been transmitted from the mobile terminal  46 , to the server  21  via the broad area communication. 
     The server  21  compares the random number transmitted from the mobile terminal  47  with the random number generated by its own and confirms that the near-field wireless communication with the evaluator at the time of the handover is being performed when both are coincident. That is, it is possible to confirm the identity of the evaluator based on the information transmitted from the side of the provider. 
     The server  21  generates another random number and encrypts the random number with the use of the unique key of the mobile terminal  47 . In addition, it is possible to obtain the unique key of the mobile terminal by searching for the terminal device database  222  with the use of the identification number of the mobile terminal  47 . 
     The server  21  transmits the random number which has been encrypted (referred to as an encrypted random number) to the broad area communication address of the mobile terminal  46 . In addition, it is possible to obtain the broad area communication address of the mobile terminal  46  by searching for the terminal device database  222  with the use of the identification number of the mobile terminal  46 . 
     The mobile terminal  46  transmits the encrypted random number, which has been transmitted from the server  21 , to the mobile terminal  47  via the near-field wireless communication. 
     The mobile terminal  46  decodes the encrypted random number with its own unique key to obtain the random number. Then, the mobile terminal  47  transmits the random number to the mobile terminal  46  via the near-field wireless communication. 
     The mobile terminal  47  transmits the random number, which has been transmitted from the mobile terminal  47 , to the server  21  via the broad area communication. 
     The server  21  compares the random number transmitted from the mobile terminal  46  with the random number generated by its own and confirm that the near-field wireless communication with the provider at the time of the handover is being performed when both are coincident. That is, it is possible to confirm the identity of the evaluator based on the information transmitted from the side of the evaluator. 
     Thereafter, the content data is transmitted from the mobile terminal  47  via the near-field wireless communication, and a game screen or the like is displayed by the mobile terminal  46 . The mobile terminal  46  transmits the evaluation information to the mobile terminal  47  at this time. 
     While the content data and the evaluation information are transmitted via the near-field wireless communication between the mobile terminal  47  and the mobile terminal  46  as described above, the server  21  continuously (periodically) confirms the identity of the evaluator and the identity of the provider at a constant cycle as described above. 
     Then, the evaluation information accumulated in the mobile terminal  47  is transmitted to the server  21  via the broad area communication. 
     In so doing, the link authentication is performed to collect the evaluation information in the evaluation information collecting system  10  even in the case where there is no sufficiently confidential relationship between the business operator of collecting evaluation information or the like and the provider of the content. 
       FIG. 11  is an arrow chart illustrating a flow of processing of performing the aforementioned link authentication to collect the evaluation information with reference to  FIG. 10 . 
     In the drawing, the mobile communication wireless communication unit  131  of the mobile terminal  47  is expressed as 3G131-3, and the mobile communication wireless communication unit  131  of the mobile terminal  46  is expressed as 3G131-4. In addition, the near field communication unit  132  of the mobile terminal  47  is expressed as BT132-3, and the near field communication unit  132  of the mobile terminal  46  is expressed as BT132-4. Furthermore, the non-contact communication unit  133  of the mobile terminal  47  is expressed as NFC133-3, and the non-contact communication unit  133  of the mobile terminal  46  is expressed as NFC133-4. 
     The NFC133-3 of the mobile terminal  47  transmits the handover message in Step S 211 , and the NFC133-4 of the mobile terminal  46  receives the handover message. 
     The NFC133-4 transmits the handover message in Step S 302 , and the NFC133-3 receives the handover message in Step S 212 . 
     By the above processing, the other device information is exchanged between the mobile terminal  47  and the mobile terminal  46 . In addition, the other device information is the information such as the identification number of the device as the counterpart of the handover, the near-field wireless communication address, and the like. In addition, the other device information includes the broad area communication address of the server  21 , if necessary. 
     The NFC133-3 notifies the BT132-3 of the other device information in Step S 213 , and the BT132-3 receives the other device information in Step S 231 . In addition, the NFC133-4 notifies the BT132-4 of the other device information in Step S 303 , and the BT132-4 receives the other device information in Step S 321 . The BT132-4 notifies the 3G131-4 of the other device information, which has been obtained in Step S 321 , in Step S 322 , and the 3G131-4 receives the other device information in Step S 341 . In practice, the notification of the other device information and other information is performed via the CPU  111 . The same is true in the following description. 
     The 3G131-4 performs the notification of the handover by transmitting the information including the other device information to the server  21  in Step S 342 , and the server  21  receives the notification in Step S 271 . In addition, the processing of Step S 321 , Step S 341 , and Step S 342  may be omitted. 
     The NFC133-3 notifies the 3G131-3 of the other device information in Step S 214 , and the 3G131-3 receives the other device information in Step S 251 . 
     The 3G131-3 performs the notification of the handover by transmitting the information including the other device information to the server  21  in Step S 252 , and the server  21  receives the notification in Step S 272 . In addition, when the server  21  is notified of the handover, not only the other device information of the counterpart of the handover but also the other device information of its own (in this case, the mobile terminal  37 ) is transmitted. 
     The BT132-3 transmits a BT connection request to the BT132-4 in Step S 232 , and the BT132-4 receives the BT connection request in Step S 323 . 
     The server  21  generates a random number in Step S 273  and encrypts the random number in Step S 274 . The server transmits the encrypted random number obtained in the processing of Step S 274  as a confirmation request in Step S 275 , and the 3G131-3 receives the encrypted random number in Step S 253 . 
     The 3G131-3 notifies the BT132-3 of the confirmation request, which has been received in Step S 253 , in Step S 254 , and the BT132-3 receives this confirmation request in Step S 233 . 
     The BT132-3 transmits the confirmation request, which has been obtained in Step S 233 , in Step S 234 , and the BT132-4 receives the confirmation request in Step S 234 . 
     The BT132-4 decodes the encrypted random number as the confirmation request, which has been obtained in Step S 324 , to obtain the random number in Step S 325 . In addition, the CPU  111  decodes the encrypted random number in practice. 
     The BT132-4 transmits the random number, which has been obtained in the processing of Step S 325 , as the confirmation response in Step S 326 , and the BT132-3 receives the random number in Step S 235 . 
     The BT132-3 notifies the 3G131-3 of the confirmation response, which has been received in Step S 35 , in Step S 236 , and the 3G131-3 receives the confirmation response in Step S 255 . 
     The 3G131-3 transmits the confirmation response, which has been obtained in Step S 255 , in Step S 256 , and the server  21  receives the confirmation response in Step S 276 . 
     In addition, the server  21  generates another random number in Step S 277  and encrypts the random number in Step S 278 . The server  21  transmits the encrypted random number, which has been obtained in the processing of Step S 278 , in Step S 279 , and the 3G131-4 receives the encrypted random number in Step S 343 . 
     The 3G131-4 notifies the BT132-4 of the confirmation request, which has been received in Step S 343 , in Step S 344 , and the BT132-4 receives the confirmation request in Step S 328 . 
     The BT132-4 transmits the confirmation request, which has been obtained in Step S 328 , in Step S 329 , and the BT132-3 receives the confirmation request in Step S 237 . 
     The BT132-3 decodes the encrypted random number of the confirmation request, which has been received in Step S 237 , to obtain the random number in Step S 238 . 
     The BT132-3 transmits the random number, which has been obtained in the processing of Step S 238 , as the confirmation response in Step S 239 , and the BT132-4 receives the random number in Step S 330 . 
     The BT132-4 notifies the 3G131-3 of the confirmation response, which has been received in Step S 330 , in Step S 331 , and the 3G131-3 receives the confirmation response in Step S 345 . 
     The 3G131-4 transmits the confirmation response, which has been obtained in Step S 345 , in Step S 346 , and the server  21  receives the confirmation response in Step S 280 . 
     Thereafter, the content data and the operation information as the evaluation information will be transmitted and received. Since such processing is the same as that in the case described above with reference to  FIG. 7 , the detailed description thereof will be omitted. 
     The processing in the part surrounded by the dotted line in the drawing is periodically executed as the processing for confirming the identity of the evaluator and the identity of the provider. 
     As described above, the processing of performing the link authentication to collect the evaluation information is executed. 
     In the example described above with reference to  FIG. 10 , the description was given of a case in which the mobile terminal  46  holds a unique key. However, the mobile terminal  46  may not hold a unique key in some cases. In such a case, it is possible to confirm the identity of the evaluator and the identity of the provider as shown in  FIG. 12 , for example. 
       FIG. 12  is a diagram illustrating still another example of a scheme in which link authentication is performed to collect evaluation information in the evaluation information collecting system  10 . The example in the drawing shows a case in which the handover is performed between the mobile terminal  47  and the mobile terminal  46  and the content (for example, a game) data is transmitted via the near-field wireless communication (BT) after the non-contact communication (NFC communication). 
     In the case of the example in  FIG. 12 , the expression “Trusted” is not added to the mobile terminal  47  as the content provider in the same manner as in the case of  FIG. 10 , and there is no sufficiently confidential relationship between the business operator of collecting evaluation information or the like and the content provider. In addition, the example shown in the drawing is different from the case of  FIG. 10  in that the mobile terminal  47  holds a unique key while the mobile terminal  46  does not hold a unique key. 
     In  FIG. 12 , the mobile terminal  47  notifies the server  21  of the handover between the mobile terminal  47  and the mobile terminal  46  via the broad area communication. At this time, the identification numbers of the mobile terminal and the mobile terminal  46  are also transmitted to the server  21 . Then, the server  21  generates a random number and confirms that the mobile terminal  46  does not hold a unique key. In addition, it is possible to confirm that the mobile terminal  46  does not hold a unique key by searching for the terminal device database  222  with the use of the identification number of the mobile terminal  46 . 
     The server  21  transmits the random number as a temporary key to the broad area communication address of the mobile terminal  46 . In addition, the broad area communication address of the mobile terminal  46  can be obtained by searching for the terminal device database  222  with the use of the identification number of the mobile terminal  46 . 
     The server  21  transmits a confirmation request to the broad area address of the mobile terminal  47 , and the mobile terminal  47  delivers the confirmation request to the mobile terminal  46  via the near-field wireless communication. In addition, the broad area communication address of the mobile terminal  47  can be obtained by searching for the terminal device database  222  with the use of the identification number of the mobile terminal  47 . 
     The mobile terminal  46  transmits the temporary key as a response to the confirmation request to the mobile terminal  47  via the near-field wireless communication, and the mobile terminal  47  delivers the response to the server  21  via the broad area communication. 
     The server  21  compares the temporary key transmitted from the mobile terminal  47  with the random number generated by its own and confirms that the near-field wireless communication with the evaluator at the time of the handover is being performed when both are coincident. That is, it is possible to confirm the identity of the evaluator based on the information transmitted from the side of the provider. 
     The server  21  generates another random number and encrypts the random number with the use of the unique key of the mobile terminal  47 . In addition, the unique key of the mobile terminal  47  can be obtained by searching for the terminal device database  222  with the use of the identification number of the mobile terminal  47 . 
     The server  21  transmits the random number which has been encrypted (referred to as an encrypted random number) to the broad area communication address of the mobile terminal  46 . The broad area communication address of the mobile terminal  46  can be obtained by searching for the terminal device database  222  with the use of the identification number of the mobile terminal  46 . 
     The mobile terminal  46  transmits the encrypted random number, which has been transmitted from the server  21 , to the mobile terminal  47  via the near-field wireless communication. 
     The mobile terminal  47  decodes the encrypted random number with its own unique key to obtain the random number. Then, the mobile terminal  47  transmits the random number to the mobile terminal  46  via the near-field wireless communication. 
     The mobile terminal  46  transmits the random number, which has been transmitted from the mobile terminal  47 , to the server  21  via the broad area communication. 
     The server  21  compares the random number transmitted from the mobile terminal  46  with the random number generated by its own and confirms that the near-field wireless communication with the provider at the time of the handover is being performed when both are coincident. That is, it is possible to confirm the identity of the provider based on the information transmitted from the side of the evaluator. 
     Thereafter, the mobile terminal  47  transmits the content data via the near-field wireless communication, and the game screen or the like is displayed by the mobile terminal  46 . The mobile terminal  46  transmits the evaluation information to the mobile terminal  47  at this time. 
     While the content data and the evaluation information are transmitted via the near-field wireless communication between the mobile terminal  47  and the mobile terminal  46  as described above, the server  21  continuously (periodically) confirms the identity of the evaluator and the identity of the provider at a constant cycle, for example, as described above. 
     Then, the evaluation information accumulated in the mobile terminal  47  is transmitted to the server  21  via the broad area communication. 
     As described above, the link authentication is performed to collect the evaluation information in the evaluation information collecting system  10  even when there is no sufficiently confidential relationship between the business operator of collecting evaluation information or the like and the content provider and the evaluator side does not have a unique key. 
     The processing described above with reference to  FIG. 12  is the combination of the processing described above with reference to  FIG. 10  and the processing described above with reference to  FIG. 8 . Therefore, the detailed description with reference to the arrow chart will be omitted. 
     Moreover, both the mobile terminal  46  and the mobile terminal  47  do not hold unique keys in some cases. In such a case, it is possible to confirm the identity of the evaluator and the identity of the provider as shown in  FIG. 13 , for example. 
       FIG. 13  is a diagram illustrating still another example of a scheme in which link authentication is performed to collect evaluation information in the evaluation information collecting system  10 . The example of the drawing shows a case in which the handover between the mobile terminal  47  and the mobile terminal  46  is performed and the content (for example, a game) data is transmitted via the near-field wireless communication (BT) after the non-contact communication (NFC communication). 
     In the case of the example in  FIG. 13 , the expression of “Trusted” is not added to the mobile terminal  47  as the content provider in the same manner as in the case of  FIG. 10 , and there is no sufficiently confidential relationship between the business operator of collecting evaluation information or the like and the content provider. In the example of the drawing, both the mobile terminal  47  and the mobile terminal  46  do not hold unique keys unlike the case of  FIG. 12 . 
     In  FIG. 13 , the mobile terminal  47  notifies the server  21  of the handover between the mobile terminal  47  and the mobile terminal  46  via the broad area communication. At this time, the identification numbers of the mobile terminals  47  and  46  are also transmitted to the server  21 . Then, the server  21  generates a random number and confirms that the mobile terminal  46  does not hold a unique key. It is possible to confirm that the mobile terminal  46  does not hold a unique key by searching for the terminal device database  22  with the use of the identification number of the mobile terminal  46 . 
     The server  21  transmits the random number as a temporary key to the broad area communication address of the mobile terminal  46 . The broad area communication address of the mobile terminal  46  can be obtained by searching for the terminal device database  222  with the use of the identification number of the mobile terminal  46 . 
     The server  21  transmits a confirmation request to the broad area address of the mobile terminal  47 , and the mobile terminal  47  delivers the confirmation request to the mobile terminal  46  via the near-field wireless communication. In addition, the broad area communication address of the mobile terminal  47  can be obtained by searching for the terminal device database  222  with the use of the identification number of the mobile terminal  47 . 
     The mobile terminal  46  transmits a temporary key as a response to the confirmation request to the mobile terminal  47  via the near-field wireless communication, and the mobile terminal  47  delivers the response to the server  21  via the broad area communication. 
     The server  21  compares the temporary key transmitted from the mobile terminal  47  with the random number generated by its own and confirms that the near-field wireless communication with the evaluator at the time of the handover is being performed when both are coincident. That is, it is possible to confirm the identity of the evaluator based on the information transmitted from the provider side. 
     In addition, the server  21  generates another random number and confirms that the mobile terminal  47  does not hold a unique key. It is possible to confirm that the mobile terminal  47  does not hold a unique key by searching for the terminal device database  222  with the use of the identification number of the mobile terminal  47 . 
     The server  21  transmits the random number as a temporary key to the broad area communication address of the mobile terminal  47 . 
     The server  21  transmits a confirmation request to the broad area address of the mobile terminal  46 , and the mobile terminal  46  delivers the confirmation request to the mobile terminal  47  via the near-field wireless communication. 
     The mobile terminal  47  transmits the temporary key as a response to the confirmation request to the mobile terminal  46  via the near-field wireless communication, and the mobile terminal  46  delivers the response to the server  21  via the broad area communication. 
     The server  21  compares the temporary key transmitted from the mobile terminal  46  with the random number generated by its own and confirms that the near-field wireless communication with the provider at the time of the handover is being performed when both are coincident. That is, it is possible to confirm the identity of the provider based on the information transmitted from the evaluator side. 
     Thereafter, the mobile terminal  47  transmits the content data via the near-field wireless communication, and a game screen or the like is displayed by the mobile terminal  46 . The mobile terminal  46  transmits the evaluation information to the mobile terminal  47  at this time. 
     While the content data and the evaluation information are transmitted via the near-field wireless communication between the mobile terminal  47  and the mobile terminal  46  as described above, the server  21  continuously (periodically) confirms the identity of the evaluator and the identity of the provider at a constant cycle, for example, as described above. 
     Then, the evaluation information accumulated in the mobile terminal  47  is transmitted to the server  21  via the broad area communication. 
     In so doing, the link authentication is performed to collect the evaluation information in the evaluation information collecting system  10  even when there is no sufficiently confidential relationship between the business operator of collecting evaluation information or the like and the content provider. 
     Since the processing described above with reference to  FIG. 13  is also the combination of the aforementioned processing, the detailed description thereof with reference to the arrow chart will be omitted. 
     According to the present disclosure, it is possible to perform the link authentication and collect the evaluation information as described above, and it is also possible to obtain the evaluation information on a P2P network in which the content provider and the evaluator are dynamically changed, for example. 
     According to the present disclosure, it is possible to shorten the time from the showing of a product, content, or the like as the evaluation target to the collecting of the evaluation information as compared with the case in the related art, and it is also possible to provide timely evaluation information. 
     Moreover, it is not necessary to install a dedicated device such as a camera or the like to confirm that an evaluator is actually present, for example, and it is possible to realize an evaluation information collecting system with high reliability with a simple configuration. 
     As the conclusion of the examples described above with reference to  FIGS. 6 to 13 , it is considered that the following two points are to be taken into consideration when the link authentication is performed to collect the evaluation information in the evaluation information collecting system  10 . The first point is whether or not there is a sufficiently confidential relationship between the business operator of collecting evaluation information or the like and the content provider, and the second point is whether or not the evaluator side and the provider side hold unique keys. 
     That is, when there is a sufficiently confidential relationship between the business operator of collecting evaluation information or the like and the content provider, it is possible to realize the link authentication by periodically confirming the identity of the evaluator based on the information transmitted from the provider side. On the other hand, when there is no sufficiently confidential relationship between the business operator of collecting evaluation information or the like and the content provider, it is possible to realize the link authentication by periodically confirming the identity of the evaluator based on the information transmitted from the provider side and by confirming the identity of the provider based on the information transmitted from the evaluator side. 
     When the mobile terminal of the evaluator holds a unique key, it is possible to confirm the identity of the evaluator based on the information transmitted from the provider side by transmitting a random number encrypted with the use of the unique key to the mobile terminal of the provider side. On the other hand, when the mobile terminal of the evaluator does not hold a unique key, it is possible to confirm the identity of the evaluator based on the information transmitted from the provider side by transmitting a temporary key to the mobile terminal or the like of the evaluator side and then transmitting a confirmation request to the mobile terminal or the like of the provider. 
     Similarly, when the mobile terminal or the like of the provider holds a unique key, it is possible to confirm the identity of the provider based on the information transmitted from the evaluator side by transmitting a random number encrypted with the use of the unique key to the mobile terminal of the evaluator side. On the other hand, when the mobile terminal or the like of the provider does not hold a unique key, it is possible to confirm the identity of the provider based on the information transmitted from the evaluator side by transmitting a temporary key to the mobile terminal or the like of the provider side and then transmitting a confirmation request to the mobile terminal or the like of the evaluator. 
     As described above, the collection of the evaluation information by performing the link authentication is realized based on the total of five types of schemes. 
     The present disclosure is for making it possible to collect the evaluation information by performing the link authentication regardless of the confidential relationship between the business operator of collecting evaluation information or the like and the content provider and regardless of the presence of the unique keys on the sides of the evaluator and the provider. For this reason, the handover message is made to include the following information. 
       FIG. 14  is a diagram illustrating a format of a handover message. The handover message is the information transmitted and received when the mobile terminal or the information collecting terminal performs the non-contact communication (NFC), for example. The format of the handover message is standardized by NFC Forum, and the format shown in the drawing is defined by a standard of the NFC forum. 
     As shown in the drawing, the handover message is configured by a plurality of (four in this example) divided records. 
     The “Record  1 ” is a record in which information such as a handover request, selection, or the like is stored. The “Record  2 ” is a record in which second carrier candidates are stored, where the “ac (Alternative Carrier)” is stored as the Record Type at the header part and a pointer of each second carrier (identifier of the “Record  3 ”) is stored in the payload part. 
     The “Record  3 ” is a record in which information relating to the near-field wireless communication mechanism is stored. As shown in the drawing, the storage of a packet including a header and a payload in the “Record  3 ” is defined by the standard of Bluetooth SIG. In addition, the packet shown in the drawing as the packet of the “Record  3 ” is the packet in the case where the near-field wireless communication mechanism performs the communication based on Bluetooth. 
     The “Record  4 ” is a record in which information defined by a manufacturer of the mobile terminal or the like is stored. In the present disclosure, the packet information shown in the drawing is defined as the information included in the “Record  4 ”. 
     As shown in the drawing, a packet including a header and a payload is stored on the “Record  4 ”. 
     The information regarding the “Record Type” is described in the header, and the information representing that the record  4  in this case is the record in which information used for collecting the evaluation information is stored is described. 
     The payload includes “server approval sorting”, a “link authentication scheme”, and a “broad area communication address”. 
     In the “server approval sorting”, the information representing whether or not the terminal device is the terminal device approved by the server  21  (Yes/No, for example) is described. The fact that the terminal device is the terminal device approved by the server  21  means that there is a sufficiently confidential relationship with the business operator of collecting evaluation information or the like. 
     In the “link authentication scheme”, the information representing a scheme based on which the aforementioned confirmation of the identity of the evaluator or the confirmation of the identity of the provider is performed is described. Specifically, the information representing a scheme in which a random number is encrypted with the use of a unique key or a scheme in which a temporary key is transmitted in advance from the server  21  is described. 
     In the “broad area communication address”, the broad area communication address of the device and the broad area communication address of the server  21  are described, if necessary. 
     According to the evaluation information collecting system  10  of the present disclosure, the handover message as shown in  FIG. 14  is transmitted and received at the time of the handover. The information shown in  FIG. 14  is transmitted as the other device information to the server  21  as well with the notification of the handover. 
     When the server  21  is notified of the handover from the information collecting terminal or the mobile terminal, the server  21  analyzes the information included in the “Record  4 ” in  FIG. 14  and performs the link authentication. As described above, the collection of the evaluation information by performing the link authentication is realized based on the total of five types of schemes in the evaluation information collecting system  10  of the present disclosure. 
     The first scheme is employed when there is a sufficiently confidential relationship between the business operator of collecting evaluation information or the like and the provider and when the mobile terminal of the evaluator holds a unique key as described above with reference to  FIG. 6 . This is referred to as Case  1 . 
     The second scheme is employed when there is a sufficiently confidential relationship between the business operator of collecting evaluation information or the like and the provider and when the mobile terminal of the evaluator does not hold a unique key as described above with reference to  FIG. 8 . This is referred to as Case  2 . 
     The third scheme is employed when there is no sufficiently confidential relationship between the business operator of collecting evaluation information or the like and the provider and when both the mobile terminal of the evaluator and the mobile terminal of the provider hold unique keys as described above with reference to  FIG. 10 . This is referred to as Case  3 . 
     The fourth scheme is employed when there is no sufficiently confidential relationship between the business operator of collecting evaluation information or the like and the provider and when the mobile terminal of the evaluator does not hold a unique key while the mobile terminal of the provider holds a unique key as described above with reference to  FIG. 12 . This is referred to as Case  4 . 
     The fifth scheme is employed when there is no sufficiently confidential relationship between the business operator collecting evaluation information or the like and the provider and when both the mobile terminal of the evaluator and the mobile terminal of the provider do not hold unique keys as described above with reference to  FIG. 13 . This is referred to as Case  5 . 
     When the server  21  is notified of the handover from the information collecting terminal or the mobile terminal, the server  21  analyzes the information included in the “Record  4 ” in  FIG. 14 , specifies the attribute of the provider side and the attribute of the evaluator side, and specifies the scheme of the link authentication as shown in  FIG. 15 . 
     That is, it is determined whether or not there is a sufficiently confidential relationship with the business operator of collecting evaluation information or the like based on the “server approval sorting” of the handover messages on the sides of the provider and the evaluator as shown in  FIG. 15 . In this example, the expression “Trusted” is added to the mobile terminal which has a sufficiently confidential relationship with the business operator of collecting evaluation information or the like (Yes in the “server approval sorting”) while the expression of “Not Trusted” is added to the mobile terminal which does not have a confidential relationship (No in the “server approval sorting”). 
     In addition, a scheme for confirming the identity of the evaluator and the identity of the provider based on the “server approval sorting” of the handover messages on the sides of the provider and the evaluator is specified. In this example, the scheme in which a random number is encrypted with the use of the unique key is described as the “unique key”, and the scheme in which a temporary key is transmitted in advance from the server  21  is described as the “temporary key”. 
     As described above, the server  21  specifies the scheme of the link authentication and performs the link authentication to collect the evaluation information. 
     Next, description will be given of an example of the evaluation information collecting processing executed by the server  21  with reference to the flow chart in  FIG. 16 . 
     The CPU  201  of the server  21  determines whether or not the notification of the handover has been received from the information collecting terminal or the mobile terminal in Step S 701  and waits for the determination that the notification of the handover has been received. 
     When it is determined that the notification of the handover has been received in Step S 701 , the processing proceeds to Step S 702 . 
     The CPU  201  obtains and analyzes the device information on the provider side, which has been transmitted with the notification of the handover, to specify the attribute of the provider side in Step S 702 . At this time, the information included in the “Record  4 ” in  FIG. 14 , for example, is analyzed, and the attribute of the provider side (the information collecting terminal  31 , the mobile terminal  47 , or the like, for example) is specified. That is, whether or not there is a sufficiently confidential relationship with the business operator of collecting evaluation information or the like and whether the scheme is a scheme in which a random number is encrypted with the use of a unique key or a scheme in which a temporary key is transmitted in advance from the server  21  are specified. 
     The CPU  201  obtains and analyzes the device information of the evaluator side, which has been transmitted from the notification of the handover, in Step S 703  in the same manner as in the processing of Step S 702  to specify the attribute of the evaluator side. 
     The CPU  201  specifies the scheme of the link authentication based on the attribute, which has been specified in Step S 702  and Step S 703 , in Step S 704 . That is, the schemes of Case  1  to Case  5  are specified as described above with reference to  FIG. 15 . 
     The CPU  201  executes the link authentication processing depending on the scheme based on the link authentication scheme, which has been specified in Step S 704 , in Step S 705 . In so doing, the link authentication corresponding to each of Case  1  to Case  5  is performed. 
       FIG. 17  is a flow chart illustrating an example of processing of Case  1  executed as the processing of Step S 705  when the link authentication scheme corresponds to Case  1  in Step S 704 . 
     The CPU  201  creates (generates) a random number in Step S 721 . 
     The CPU  201  obtains the unique key of the evaluator side by searching for the terminal device database  222  with the use of the identification number of the evaluator side (the mobile terminal  41 , for example) in Step S 722 . 
     The CPU  201  encrypts the random number created in Step S 721  with the use of the unique key, which has been obtained in Step S 722 , in Step S 723 . 
     The CPU  201  obtains the broad area communication address of the provider side by searching for the terminal device database  222  with the use of the identification number of the provider side (the information collecting terminal  31 , for example) in Step S 724 . 
     The CPU  201  transmits the encrypted random number created in Step S 723  as a confirmation request to the broad area address, which has been obtained in Step S 724 , in Step S 725 . 
     The CPU  201  determines whether or not an appropriate confirmation response, which is the response to the confirmation request transmitted in Step S 725 , has been received in Step S 726 . At this time, it is determined that the random number created in Step S 721  is included in the confirmation request, and that an appropriate response has been received when the random number is included. 
     When it is determined in Step S 726  that the appropriate confirmation response has been received, the processing proceeds to Step S 727 . On the other hand, when it is determined that the appropriate confirmation response has not been received, the processing proceeds to Step S 730  to execute the error processing. 
     The CPU  201  records the time point at which the appropriate confirmation response was received as the authentication time of the link authentication in Step S 727 . 
     The CPU  201  determines in Step S 728  whether or not the evaluation information has been transmitted from the provider side and moves on to Step S 729  when it is determined that the evaluation information has not yet been transmitted. 
     The CPU  201  determines in Step S 729  whether or not a predetermined time period has passed since the authentication time was recorded in Step S 727  and waits for the determination that the predetermined time period has passed. When it is determined in Step S 729  that the predetermined time period has passed, the processing returns to Step S 721 . In so doing, the identity of the evaluator is continuously (periodically) confirmed at a constant cycle. 
     On the other hand, when it is determined in Step S 728  that the evaluation information has been transmitted from the provider side, the processing of Case  1  is completed. 
     As described above, the link authentication processing depending on the scheme in the case of Case  1  is executed. 
       FIG. 18  is a flow chart illustrating an example of processing of Case  2  executed as the processing of Step S 705  when the link authentication scheme is specified to be Case  2  in Step S 704 . 
     The CPU  201  creates a temporary key in Step S 751 . 
     The CPU  201  obtains the broad area communication address of the evaluation side by searching for the terminal device database  222  with the use of the identification of the evaluation side (the mobile terminal  41 , for example) in Step S 752 . 
     The CPU  201  transmits the temporary key created in Step S 751  to the broad area address, which has been obtained in Step S 752 , in Step S 753 . 
     The CPU  201  obtains the broad area communication address of the provider side by searching for the terminal device database  222  with the use of the identification number of the provider side (the information collecting terminal  31 , for example) in Step S 754 . 
     The CPU  201  transmits a confirmation request to the broad area address, which has been obtained in Step S 754 , in Step S 755 . 
     The CPU  201  determines whether or not an appropriate confirmation response, which is the response to the confirmation request transmitted in Step S 755 , has been received in Step S 756 . At this time, it is determined that the temporary key created in Step S 751  is included in the confirmation response, and that the appropriate confirmation response has been received when the temporary key is included. 
     When it is determined in Step S 756  that the appropriate confirmation response has been received, the processing proceeds to Step S 757 . On the other hand, when it is determined that the appropriate confirmation response has not been received, the processing proceeds to Step S 760  to execute the error processing. 
     The CPU  201  records the time at which the appropriate confirmation response was received as the authentication time of the link authentication in Step S 757 . 
     The CPU  201  determines in Step S 758  whether or not the evaluation information has been transmitted from the provider side and moves on to Step S 759  when it is determined that the evaluation information has not yet been transmitted. 
     The CPU  201  determines in Step S 759  whether or not a predetermined time period has passed since the authentication time was recorded in Step S 757  and waits for the determination that the predetermined time has passed. When it is determined in Step S 759  that the predetermined time has passed, the processing returns to Step S 751 . In so doing, the identity of the evaluator is continuously (periodically) confirmed at a constant cycle. 
     On the other hand, when it is determined in Step S 758  that the evaluation information has been transmitted from the provider side, the processing of Case  2  is completed. 
     As described above, the link authentication processing depending on the scheme in the case of Case  2  is executed. 
       FIGS. 19 and 20  are flow charts illustrating an example of the processing of Case  3  executed as the processing of Step S 705  when the link authentication scheme corresponds to Case  3  in Step S 704 . 
     Since the processing form Step S 781  to Step S 788  is the same as that from Step S 721  to Step S 727  and Step S 730  in  FIG. 17 , the detailed description thereof will be omitted. 
     The CPU  201  creates (generates) a random number in Step S 789 . 
     The CPU  201  obtains the unique key of the provider side by searching the terminal device database  222  with the use of the identification number of the provider side (the mobile terminal  47 , for example) in Step S 790 . 
     The CPU  201  encrypts the random number created in Step S 789  with the use of the unique key, which has been obtained in Step S 790 , in Step S 791 . 
     The CPU  201  obtains the broad area communication address of the evaluator side by searching for the terminal device database  222  with the use of the identification number of the evaluator side (the mobile terminal  46 , for example) in Step S 792 . 
     The CPU  201  transmits the encrypted random number generated in Step S 791  as a confirmation request to the broad area address, which has been obtained in Step S 792 , in Step S 793 . 
     The CPU  201  determines whether or not an appropriate confirmation response, which is the response to the confirmation request transmitted in Step S 793 , has been received in Step S 794 . At this time, it is determined whether or not the random number created in Step S 789  is included in the confirmation response, and that the appropriate confirmation response has been received when the random number is included. 
     When it is determined that the appropriate confirmation response has been received in Step S 794 , the processing proceeds to Step S 795 . On the other hand, when it is determined that the appropriate confirmation response has not been received, the processing proceeds to Step S 798  to execute the error processing. 
     The CPU  201  records the time at which the appropriate confirmation response was received as the authentication time of the link authentication in Step S 795 . 
     The CPU  201  determines in Step S 796  whether or not the evaluation information has been transmitted from the provider side and moves on to Step S 797  when it is determined that the evaluation information has not yet been transmitted. 
     The CPU  201  determines in Step S 797  whether or not a predetermined time period has passed after recording the authentication time in Step S 795  and waits for the determination that the predetermined time period has passed. When it is determined in Step S 795  that the predetermined time period has passed, the processing returns to Step S 781 . In so doing, the identity of the evaluator and the identity of the provider are periodically confirmed. 
     On the other hand, when it is determined in Step S 796  that the evaluation information has been transmitted from the provider side, the processing of Case  3  is completed. 
     As described above, the link authentication processing depending on each scheme in the case of Case  3  is executed. 
       FIGS. 21 and 22  are flow charts illustrating an example of the processing of Case  4  executed as the processing of Step S 705  when the link authentication scheme is specified to be Case  4  in Step S 704 . 
     Since the processing from Step S 811  to Step S 818  is the same as the processing from Step S 751  to Step S 757  and Step S 760  in  FIG. 18 , the detail description thereof will be omitted. 
     Since the processing from Step S 819  to Step S 828  is the same as the processing from Step S 789  to Step S 798  in  FIG. 20 , the detailed description thereof will be omitted. 
     The link authentication processing depending on the scheme in the case of Case  4  is executed in this manner. 
       FIGS. 23 and 24  are flow charts illustrating an example of the processing of Case  5  executed as the processing in Step S 705  when the link authentication scheme is specified to be Case  5  in Step S 704 . 
     Since the processing from Step S 831  to Step S 838  is the same as the processing from Step S 811  to Step S 818  in  FIG. 21 , the detailed description will be omitted. 
     The CPU  201  creates a temporary key in Step S 839 . 
     The CPU  201  obtains the broad area communication address of the provider side by searching for the terminal device database  222  with the use of the identification number of the provider side (the mobile terminal  47 , for example) in Step S 840 . 
     The CPU  201  transmits the temporary key created in Step S 839  to the broad area address, which has been obtained in Step S 840 , in Step S 841 . 
     The CPU  201  obtains the broad area communication address of the evaluation side by searching for the terminal device database  222  with the use of the identification number of the evaluator side (the mobile terminal  46 , for example) in Step S 842 . 
     The CPU  201  transmits a confirmation request to the broad area address, which has been obtained in Step S 842 , in Step S 843 . 
     The CPU  201  determined in Step S 844  whether or not an appropriate confirmation response, which is the response to the confirmation request transmitted in Step S 843 , has been received. At this time, it is determined whether or not the temporary key created in Step S 839  is included in the confirmation response, and that the appropriate confirmation response has been received when the temporary key is included. 
     When it is determined in Step S 844  that the appropriate confirmation response has been received, the processing proceeds to Step S 845 . On the other hand, when it is determined that the appropriate confirmation response has not been received, the processing proceeds to Step S 848  to execute the error processing. 
     The CPU  201  records the time at which the appropriate confirmation response was received as the authentication time of the link authentication in Step S 845 . 
     The CPU  201  determines in Step S 846  whether or not the evaluation information has been transmitted from the provider side and moves on to Step S 847  when it is determined that the evaluation information has not yet been transmitted. 
     The CPU  201  determines in Step S 847  whether or not a predetermined time period has passed since the recording of the authentication time in Step S 845  and waits for the determination that the predetermined time period has passed. When it is determined in Step S 847  that the predetermined time period has passed, the processing returns to Step S 831 . In so doing, the identity of the evaluator and the identity of the provider are periodically confirmed. 
     On the other hand, when it is determined in Step S 846  that the evaluation information has been transmitted from the provider side, the processing of Case  5  is completed. 
     As described above, the link authentication processing depending on the scheme in the case of Case  5  is executed. 
     The evaluation information collecting processing including such link authentication processing depending on the scheme is executed. 
     Next, description will be given of an example of the processing by the terminal device (the information collecting terminal  31 , the mobile terminal  47 , or the like, for example) on the provider side with reference to the flow chart in  FIG. 25 . The processing is executed in the terminal device on the provider side which holds a unique key, and the terminal device on the provider side provides music content or the like in this example. 
     The CPU  111  of the information collecting terminal or the mobile terminal determines in Step S 901  whether or not the handover has been performed and waits for the determination that the handover has been performed. 
     The CPU  111  notifies the server  21  of the handover via the broad area communication in Step S 902 . At this time, the other device information is transmitted along with the notification of the handover. 
     The CPU  111  determines in Step S 903  whether or not a confirmation request via the broad area communication has been received. When it is determined in Step S 903  that the confirmation request has been received, the processing proceeds to Step S 905 . When it is determined that the confirmation request has not been received, the processing proceeds to Step S 904 . 
     Here, description will be given of an example of the content provision processing in Step S 904  in  FIG. 25  with reference to the flow chart in  FIG. 26 . 
     The CPU  111  transmits the content data to the evaluator side via the near-field wireless communication in Step S 921 . 
     The CPU  111  receives the evaluation information from the evaluator side via the near-field wireless communication in Step S 922 . 
     The CPU  111  determines in Step S 923  whether or not a predetermined amount of data has been transmitted in the processing of Step S 921 , and the processing returns to Step S 921  when it is determined that the predetermined amount of data has not yet been transmitted. On the other hand, when it is determined that the predetermined amount of data has been transmitted, the processing proceeds to Step S 906  in  FIG. 25 . 
     Here, description will be given of an example of the link authentication confirmation processing in Step S 905  in  FIG. 25  with reference to the flow chart in  FIG. 27 . 
     The CPU  111  transmits the confirmation request which has been determined to be received in Step S 903  to the evaluator side via the near-field wireless communication in Step S 941 . 
     The CPU  111  determines in Step S 942  whether or not the confirmation response to the confirmation request transmitted in Step S 941  has been received via the near-field wireless communication and waits for the determination that the confirmation response has been received. When it is determined in Step S 942  that the confirmation response has been received, the processing proceeds to Step S 943 . 
     The CPU  111  transmits the confirmation response which has been determined to be received in Step S 942  to the server  21  via the broad area communication in Step S 943 . 
     The CPU  111  determines in Step S 944  whether or not the confirmation request has been received via the near-field wireless communication and waits for the determination that the confirmation request has been received. When it is determined in Step S 944  that the confirmation request has been received, the processing proceeds to Step S 945 . 
     The CPU  111  decodes an encrypted random number included in the confirmation request, which has been determined to be received in Step S 944 , with the use of its own unique key in Step S 945 . 
     The CPU  111  transmits the random number obtained by decoding in Step S 945  as the confirmation response to the evaluator side via the near-field wireless communication in Step S 946 . 
     As described above, the link confirmation processing is executed. 
     Referring back to  FIG. 25 , the processing proceeds to Step S 906  after the processing of Step S 904  or Step S 905 , and the CPU  111  determines whether or not the content provision has been completed. For example, when the evaluator instructs the stop of the content reproduction, it is determined in Step S 906  that the content provision has been completed. When it is determined that the content provision has not yet been completed in Step S 906 , the processing returns to Step S 903 . 
     When it is determined in Step S 906  that the content provision has been completed, the processing proceeds to Step S 907 . 
     The CPU  111  transmits the evaluation information received in the processing of Step S 904  to the server  21  via the broad area communication in Step S 907 . 
     As described above, the processing by the terminal device on the provider side is executed. 
     Next, description will be given of another example of the processing by the terminal device on the provider side with reference to the flow chart in  FIG. 28 . The processing is executed in the terminal device on the provider side which does not hold a unique key, and the terminal device on the provider side provides music content or the like in this example. 
     The CPU  111  of the information collecting terminal or the mobile terminal determines in Step S 961  whether or not the handover has been performed and waits for the determination that the handover has been performed. 
     The CPU  111  notifies the server  21  of the handover via the broad area communication in Step S 962 . At this time, the other device information is transmitted along with the notification of the handover. 
     The CPU  111  determines in Step S 963  whether or not a confirmation request or a temporary key via the broad area communication has been received. When it is determined in Step S 963  that the confirmation request or the temporary key has been received, the processing proceeds to Step S 965 . When it is determined that the confirmation request has not been received, the processing proceeds to Step S 964 . 
     Here, description will be given of an example of the link authentication confirmation processing in Step S 965  in  FIG. 28  with reference to the flow chart in  FIG. 29 . 
     The CPU  111  determines in Step S 981  whether or not what the CPU  111  has determined to receive in Step S 963  is the confirmation request. When it is determined that the confirmation request has been received, the processing proceeds to Step S 982 . 
     The CPU  111  transmits the confirmation request which has been determined to receive in Step S 963  to the evaluator side via the near-field wireless communication in Step S 982 . 
     The CPU  111  determines whether or not the confirmation response to the confirmation request transmitted in Step S 982  has been received via the near-field wireless communication in Step S 983  and waits for the determination that the confirmation response has been received. When it is determined in Step S 983  that the confirmation response has been received, the processing proceeds to Step S 984 . 
     The CPU  111  transmits the confirmation response which has been determined to be received in Step S 983  to the server  21  via the broad area communication in Step S 984 . 
     On the other hand, when it is determined in Step S 981  that what the CPU  111  has determined to receive in Step S 963  is not the confirmation request, the processing proceeds to Step S 988 . This means that the temporary key has been received. 
     The CPU  111  stores the temporary key, which has been determined to be received in Step S 963 , in Step S 988 . 
     After the processing of Step S 984  or Step S 988 , the processing proceeds to Step S 985 . 
     The CPU  111  determines in Step S 985  whether or not the confirmation request has been received via the near field wireless communication and waits for the determination that the confirmation request has been received. When it is determined that the confirmation request has been received in Step S 985 , the processing proceeds to Step S 986 . 
     The CPU  111  reads the temporary, which has been stored in Step S 988 , in Step S 986 . 
     The CPU  111  transmits the temporary key read in Step S 986  as a confirmation response to the evaluator side via the near field wireless communication in Step S 987 . 
     As described above, the link authentication confirmation processing is executed. 
     Since the content provision processing of Step S 964  in  FIG. 28  is the same as the processing described above with reference to  FIG. 26 , the detailed description thereof will be omitted. Moreover, since the processing of Step S 966  and Step S 967  in  FIG. 28  is the same as the processing of Step S 906  and Step S 907  in  FIG. 25 , respectively, the detailed description thereof will be omitted. 
     As described above, the processing by the terminal device on the provide side is executed. 
     Next, description will be given of an example of the processing by the terminal device (the mobile terminal  41 , the mobile terminal  46 , or the like, for example) on the evaluator side with reference to the flow chart in  FIG. 30 . The processing is executed by the terminal device on the evaluator side which holds a unique key, and music content or the like is provided by the terminal device on the provider side and the content is evaluated in this example. 
     The CPU  111  of the mobile terminal determines in Step S 1001  whether or not the handover has been performed and waits for the determination that the handover has been performed. 
     The CPU  111  notifies the server of the handover via the broad area communication in Step S 1002 . At this time, the other device information is transmitted along with the notification of the handover. The processing of Step S 1002  may be omitted. 
     The CPU  111  determines in Step S 1003  whether or not the confirmation request via the broad area communication has been received. When it is determined that the confirmation request has been received in Step S 1003 , the processing proceeds to Step S 1004 . 
     Here, description will be given of an example of the first link authentication processing of Step S 1004  in  FIG. 30  with reference to the flow chart in  FIG. 31 . 
     The CPU  111  transmits the confirmation request which has been determined to be received in Step S 1003  to the provider side via the near field wireless communication in Step S 1021 . 
     The CPU  111  determines in Step S 1022  whether or not the confirmation response to the confirmation request transmitted in Step S 1021  has been received and waits for the determination that the confirmation response has been received. When it is determined in Step S 1022  that the confirmation response has been received, the processing proceeds to Step S 1023 . 
     The CPU  111  transmits the confirmation response which has been determined to be received in Step S 1022  to the server  21  via the broad area communication in Step S 1023 . 
     As described above, the first link authentication processing is executed. 
     Referring back to  FIG. 30 , after the processing of Step S 1004 , or when it is determined in Step S 1003  that the confirmation request has not been received, the processing proceeds to Step S 1005 . 
     The CPU  111  determines in Step S 1005  whether or not the confirmation request via the near field wireless communication has been received. When it is determined in Step S 1005  that the confirmation request has been received, the processing proceeds to Step S 1007 . 
     Here, description will be given of an example of the second link authentication processing of Step S 1007  in  FIG. 30  with reference to the flow chart in  FIG. 32 . 
     The CPU  111  decodes the encrypted random number included in the confirmation request which has been determined to be received in Step S 1005  with its own unique key in Step S 1041 . 
     The CPU  111  transmits the random number obtained by decoding in Step S 1041  as a confirmation response to the provider side via the near field wireless communication in Step S 1042 . 
     As described above, the second link confirmation processing is executed. 
     Referring back to  FIG. 30 , when it is determined in Step S 1005  that the confirmation request has not been received, the processing proceeds to Step S 1006 . 
     Here, Description will be given of an example of the content evaluation processing of Step S 1006  in  FIG. 30  with reference to the flow chart in  FIG. 33 . 
     The CPU  111  receives the data from the provider side via the near field wireless communication in Step S 1061 . 
     The CPU  111  transmits the evaluation information to the provider side via the near field wireless communication in Step S 1062 . 
     The CPU  111  determines in Step S 1063  whether or not a predetermined amount of data has been transmitted in the processing of Step S 1061 , and the processing returns to Step S 1061  when it is determined that the predetermined amount of data has not yet been transmitted. On the other hand, when it is determined that the predetermined amount of data has been transmitted, the processing proceeds to Step S 1008  in  FIG. 30 . 
     As described above, the content evaluation processing is executed. 
     Referring back to  FIG. 30 , after the processing of Step S 1006  or Step S 1007 , the processing proceeds to Step S 1008 . 
     The CPU  111  determines in Step S 1008  whether or not the evaluation of the content received from the provider side has been completed, and the processing returns to Step S 1003  when it is determined that the evaluation has not yet been completed. 
     On the other hand, when it is determined in Step S 1008  that the content evaluation has been completed, the processing is completed. 
     As described above, the processing by the terminal device on the evaluator side is executed. 
     Next, description will be given of another example of the processing by the terminal device on the evaluator side with reference to the flow chart in  FIG. 34 . The processing is executed by the terminal device on the evaluator side which does not hold a unique key, and music content or the like is provided by a terminal device on the provider side and the content is evaluated in this example. 
     The CPU  111  of the mobile terminal determines in Step S 1081  whether or not the handover has been performed and waits for the determination that the handover has been performed. 
     The CPU  111  notifies the server  21  of the handover via the broad area communication in Step S 1082 . At this time, the other device information is transmitted along with the notification of the handover. The processing of Step S 1082  may be omitted. 
     The CPU  111  determines in Step S 1083  whether or not the confirmation request via the broad area communication has been received. When it is determined in Step S 1083  that the confirmation request has been received, the processing proceeds to Step S 1084 . 
     Here, description will be given of an example of the third link authentication processing of Step S 1084  in  FIG. 34  with reference to the flow chart in  FIG. 35 . 
     The CPU  111  determines in Step S 2001  what has been determined to be received in Step S 1083  is the confirmation request. When it is determined that the confirmation request has been received, the processing proceeds to Step S 2002 . 
     The CPU  111  transmits the confirmation request which has been determined to be received in Step S 1083  to the provider side via the near field wireless communication in Step S 2002 . 
     The CPU  111  determines in Step S 2003  whether or not the confirmation response to the confirmation request transmitted in Step S 2002  has been received via the near field wireless communication and waits for the determination that the confirmation response has been received. When it is determined in Step S 2003  that the confirmation response has been received, the processing proceeds to Step S 2004 . 
     The CPU  111  transmits the confirmation response which has been determined to be received in Step S 2003  to the server  21  via the broad area communication in Step S 2004 . 
     On the other hand, when it is determined in Step S 2001  that what has been determined to be received in Step S 1083  is not the confirmation request, the processing proceeds to Step S 2005 . This means that the temporary key has been received. 
     The CPU  111  records the temporary key, which has been determined to be received in Step S 1083 , in Step S 2005 . 
     As described above, the third link authentication processing is executed. 
     Referring back to  FIG. 34 , after the processing of Step S 1084 , or when it is determined in Step S 1083  that the confirmation request via the broad area communication has not been received, the processing proceeds to Step S 1085 . 
     The CPU  111  determines in Step S 1085  whether or not the confirmation request via the near field wireless communication has been received. When it is determined in Step S 1085  that the confirmation request has been received, the processing proceeds to Step S 1087 . 
     Here, description will be given of an example of the fourth link authentication processing of Step S 1087  in  FIG. 34  with reference to the flow chart in  FIG. 36 . 
     The CPU  111  reads the temporary key, which has been stored in Step S 2005 , in Step S 2021 . 
     The CPU  111  transmits the temporary key read in Step S 2021  as the confirmation response to the evaluator side via the near field wireless communication in Step S 2022 . 
     As described above, the fourth link authentication confirmation processing is executed. 
     Referring back to  FIG. 34 , on the other hand, in Step S 1085 , when it is determined that the confirmation request has not been received, the processing proceeds to Step S 1086 . Since the content evaluation processing of Step S 1086  is the same as the processing described above with reference to the flow chart in  FIG. 33 , the detailed description thereof will be omitted. 
     After the processing of Step S 1086  or Step S 1087 , the processing proceeds to Step S 1088 . 
     The CPU  111  determines in Step S 1088  whether or not the evaluation of the content provided from the provider side has been completed, and the processing returns to Step S 1083  when it is determined that the evaluation has not yet been completed. 
     On the other hand, when it is determined in Step S 1088  that the content evaluation has been completed, the processing is completed. 
     As described above, the processing by the terminal device on the evaluator side is executed. 
     Incidentally, the above description was mainly given of the examples in which the evaluation information is collected as the information to be referred to for purchasing products or services, such as so-called word-of-mouth information. However, the information may be collected from a different view point. 
       FIG. 37  is a diagram illustrating another embodiment of the present disclosure. The drawing shows a configuration example of the content distribution system  11  which distributes content based on the record relating to the content provision of each terminal device. 
     In this example, the content distribution system  11  includes a server  22 , mobile terminals  51  to  53 , and mobile terminals  55  to  57 . In this example content is transmitted (distributed) to the mobile terminal  51  and mobile terminal  55 . 
     The content is provided from the mobile terminal  51  to the mobile terminals  52  and  53 . In addition, the content is provided from the mobile terminal  55  to the mobile terminals  56  and  57 . The content is provided to each of the mobile terminals  52 ,  53 ,  56 , and  57  by the mobile terminals  52 ,  53 ,  56 , and  57  respectively performing the streaming reproduction of the music content or the like. 
     The server  22  is installed at the data center of a business operator collecting record information, for example, to obtain the record information transmitted from the mobile terminal  51  or  55  and perform processing such as storage, modification, and the like of the obtained record information. The server  22  distributes the content to the mobile terminal or the mobile terminal  55  based on the obtained record information. 
     The configuration described above with reference to  FIG. 4  is applied to the server  22 . 
     Here, a scheme is assumed in which content is sequentially with the use of the handover of the mobile phone. For example, a case is assumed in which a new song of a musician immediately after the release is distributed to the mobile phones of the members of the fan club for promotion. 
     The content of the new song immediately after the release is distributed to the use of the mobile terminal  51  and the user of the mobile terminal  55  who are members of the fan club. At this time, the mobile terminals  51  and  55  download the content data from the server  22  and store the content data in the storage unit  123 , respectively. 
     Then, the user of the mobile terminal  51  performs the handover between the mobile terminal  51  and the mobile terminal  52  of a friend to cause the mobile terminal  52  to perform the streaming reproduction of the content with the use of the near field wireless communication. In addition, the user of the mobile terminal  51  performs the handover between the mobile terminal  51  and the mobile terminal  53  of another friend to cause the mobile terminal  53  to perform the streaming reproduction of the content with the use of the near field wireless communication. 
     The user of the mobile terminal  55  causes the mobile terminals  56  and  57  of friends to perform the streaming reproduction of the content in the same manner. 
     Although another configuration is also applicable in which the mobile terminal  52  or  53  downloads the content from the mobile terminal  51 , it is assumed here that only the streaming reproduction of the content is performed. 
     Although only the mobile terminals  51  and  55  are described herein as the mobile terminals of the users who are the members of the fan club, more members respectively have the mobile terminals in practice. Moreover, although the example was described herein in which each member provides the content to two friends, the number of persons to which the content is provided is different depending on each member. 
     As described above, the content is sequentially provided from the members of the fan club according to the content distribution system  11 . Some of the users who have received the content as described above actually purchase and download the music content or newly join the fan club. 
     In the content distribution system  11 , the mobile terminals  51  and  55  transmit record information. The record information is the information representing to whom the mobile terminals  51  and  55  respectively have provided the content, for example. 
       FIG. 38  is a diagram showing an example of the record information. The drawing shows the record information transmitted from the mobile terminal  51  to the server  21 , for example, and the record information includes the information relating to the “content provision destination” and the information relating to the “detail” in this example. 
     The information relating to the “content provision destination” includes the “user ID” and the “user attribute”. The “user ID” is the identification information which specifies the user. In this example, “A010001” and “B020003” are described, and they are the identification information of the users of the mobile terminals  52  and  53 . In addition, the user ID is allotted to each user based on a predetermined numbering rule in order to uniquely specify each user in the content distribution system  11 . 
     The “user attribute” in  FIG. 38  includes “age”, “sex”, “address” and “taste”, and the “age”, the information representing the “age, the “sex”, the “address” and the “taste” of the user specified by the “user ID” is described. As the “taste”, information representing the hobby of the user such as the “watching sports”, “reading books”, and the like may be described, or information representing the preference specified to music content such as “rock”, “jazz”, and the like may be described, for example. 
     The information described as the “user ID” and the “user attribute” in the record information is included in the handover message as will be described later, and is obtained when the handover is performed between the mobile terminal  51  and the mobile terminal  52  or  53 , for example. 
     The information relating to the “detail” includes “provision start time”, “provision completion time”, “content ID”, and “certificate”. The “provision start time” and the “provision completion time” are information representing the time point at which the content provision to the user specified by the “user ID” is started and the information representing the time point at which the content provision is completed, respectively. 
     The “content ID” is the information which specifies the provided content. 
     The “certificate” is issued as a result of the authentication of the users with the user ID “A010001” and the user ID “B020003” by the application program mounted to the mobile terminal  52  or  53 . In addition, the result of the link authentication may be included in the “certificate” as will be described later. 
     For performing the streaming reproduction of the content in the mobile terminal  52  or  53 , it is necessary to log on in advance to the application program for reproducing the content, and the user is authenticated by inputting a password at the time of the log-on, for example. For example, a software company which has developed the application program holds a secret key and an opened key, and the secret key is mounted on the mobile terminal with the application program. 
     The application for reproducing the content creates a certificate obtained by encrypting a value, which is obtained by performing predetermined computation on the user ID of the user, with its own secret key when a password which is coincident with the password registered in advance is input. 
     When the record information is transmitted from the mobile terminal  51 , the server  22  can authenticate the user as a result by decoding the certificate with the use of the opened key in the server  22 . For example, when content of a new song of a musician immediately after the release is distributed for promotion, content provision” means allowing the users to listen via the mobile terminals. For this reason, it is possible to create more reliable record information by adding the user authentication result in each mobile terminal as a certificate. 
     The above creation of the certificate is just one example, and the certificate may be created based on another scheme. In addition, it is not necessary to provide the certificate for the record information, and the information representing that the user has not been authenticated may be described in the “certificate” for the record information when the user is not authenticated by the mobile terminal  52  or  53 , for example. 
     The information which specifies the type of the certificate is stored in the “certificate” for the record information with the information including the numerical values constituting the certificate. Accordingly, the server which has received the record information recognizes whether or not the result of the user authentication by the application program is included in the record information or whether or not the result of the link authentication is included in the record information as will be described later. 
     The server  22  receives the record information configured as described above from the mobile terminals  51  and  55 . Then, the server  22  analyzes the record information, specifies when and to whom the mobile terminals  51  and  55  have provided the content, and specifies the mobile terminal which has provided the content to more users in unit time, for example. 
     As described above, the server  22  analyzes the record information and specifies the mobile terminals with the best record in the content provision, for example. The fact that the record in the provision is good may mean that the mobile terminals have provided the content to more users in a unit of time or that the mobile terminals have provided the content to the users of the ages, sexes, addresses, tastes of the promotion target, for example. When the goal of the promotion is to increase fans in the young generation, the record information is filtered with the “age” in the information relating to the “content provision destination”, and the record in the provision by the mobile terminals which have provided the content to more users of the ages less than a threshold value is considered to be good. 
     Moreover, in the analysis of the record information, the effectiveness of the certificate may be determined as well as the determination of whether or not the user authentication result by the application program is included in the “certificate” for the record information or whether or not the link authentication result is included in the “certificate”. Here, the effectiveness of the certificate is obtained such that effectiveness is determined when the link authentication result is included along with the user authentication result or when the certificate creation date satisfies a predetermined reference, for example. 
     The record information may be filtered based on the content of the information (the user authentication result, the link authentication result, or both) included in the certificate and the effectiveness thereof. In so doing, it is possible to specify the mobile terminals with good record in the content provision in consideration of the extent to which the reliability is necessary for the record information. 
     The server  22  distributes the content of the subsequent new song, for example, to the mobile terminals with good record in the provision, which have been specified as described above, with priority. For example, when the server  22  determines that the record in the provision by the mobile terminal  51  is good, the server  22  allows the mobile terminal to download the content of the subsequent new song for free. Alternatively, the server  22  may allow a plurality of mobile terminals for which the better record in the provision than a preset reference has been confirmed to download the content of the subsequent new song for free, or the server  22  may allow the mobile terminals to download the content of the new song for free in order from the mobile terminal with the best record in the provision with time differences. 
     Alternatively, a bonus advantage such as a ticket of a concert or the like may be given to the mobile terminal with the best record in the provision. 
     In so doing, it is possible to promote the selling of the content, for example, and thereby it is possible for a record company or the like which provide the content to realize more effective content distribution. 
     The content distribution system  11  of the present disclosure makes it possible to perform the aforementioned collection of the record information. Thus, the following information is included in the handover message. 
       FIG. 39  is a diagram illustrating a format of the handover message. As described above with reference to  FIG. 14 , the handover message is the information transmitted and received when the mobile terminal or the information collecting terminal performs the non-contact communication (NFC communication). The format of the handover message is standardized by NFC Forum, and the format in the drawing is defined by the standard of the NFC Forum. 
     The “Record  1 ” to the “Record  4 ” in the drawing are the same as those described above with reference to  FIG. 14 . Therefore, the detailed description thereof will be omitted. 
     The “Record  5 ” is the information in which the information defined by the manufacturer of the mobile terminal or the like is stored in the same manner as in the “Record  4 ”. According to the present disclosure, the packet information as shown in the drawing is defined as the information included in the “Record  5 ”. 
     As shown in the drawing, the packet including the header and the payload is stored in the “Record  5 ”. 
     The information of the “Record Type” is described in the header, and the information representing that the Record  5  is the record in which the information to be used for collecting the record information is stored is described in this case. 
     The payload includes the “user ID”, the “user attribute”, the “user authentication scheme”, and the “user authentication information”. 
     The “user ID” and the “user attribute” are the same as those in the record information described above with reference to  FIG. 38 . 
     The “user authentication scheme” is the information which specifies the authentication scheme relating to the “user authentication information”. 
     A case will be considered in which the user authentication is performed in the mobile terminal  52  or  53  as described above. For example, when the mobile terminal  52  or the like performs the streaming reproduction of the content, it is necessary to log on in advance to the application program for the content reproduction, and the user is authenticated by inputting a password at the time of the log-on. In such a case, a certificate is created by encrypting a value obtained by performing predetermined computation on the user ID with a secret key of a software company which has developed the application program. 
     In such a case, the information representing the aforementioned predetermined computation performed on the user ID, the information which specifies the software company, and the like are stored in the “user authentication information”, for example, and the aforementioned certificate is stored. 
     For example, when the user is not authenticated by the mobile terminal  52  or  53 , the information representing that the user has not been authenticated is stored in the “user authentication scheme”, and null value is stored in the “user authentication information”. 
     The mobile terminal  51  creates the aforementioned record information based on the information described in the “Record  5 ” in the handover message as described above and transmits the record information to the server  22 . 
     Here, in order to further enhance the reliability of the record information, it is possible to perform the aforementioned link authentication and allow the link authentication result to be included in the certificate. That is, it is possible to add the link authentication result as the information which proves that the record information is not fake. 
     For example, when the server  22  in  FIG. 37  can perform the link authentication in the same manner as the server  21  in  FIG. 1 , the server  22  creates the certificate of the link authentication. In such a case, the server  22  performs the link authentication on the communication between the provider side (the mobile terminal  51 , for example) and the user (the mobile terminal  52  or  53 , for example) in the same manner as the processing described above with reference to  FIG. 16 . 
     Then, the server  22  creates the certificate by encrypting the information representing that the link authentication is performed until the content provision from the mobile terminal  51  to the mobile terminal  52  or  53  is completed, for example. The information obtained by encrypting a value obtained in combination between the user ID of the user of the mobile terminal  52  or  53  and the time point of the link authentication with the unique key of the server  22  is regarded as the certificate. The server  22  transmits the encrypted certificate to the mobile terminal  51  when the content provision is completed. 
     The server  22  decodes the information stored in the “certificate” of the record information transmitted from the mobile terminal  51  with its own unique key. In so doing, the sever  22  obtains the user ID of the user of the mobile terminal  52  or  53  and the time point of the link authentication, and compares the user ID and the time point with the content of the record information to confirm that the record information is not the fake. 
     Alternatively, when the server  22  in  FIG. 37  is not capable of performing the link authentication in the same manner as the server  21  in  FIG. 1 , the server  21  creates the certificate of the link authentication as described above. At this time, the server  21  holds a secret key and an opened key. 
     In this case, the information obtained by encrypting a value obtained in combination between the user ID of the user of the mobile terminal  52  or  53  and the time point of the link authentication with the secret key of the server  21  is regarded as the certificate, for example. The server  21  transmits the encrypted certificate to the mobile terminal  51  at the time of the completion of the content provision. 
     The server  22  decodes the information stored in the “certificate” of the record information transmitted from the mobile terminal  51  with the opened key of the server  21 . In so doing, the server  22  obtains the user ID of the user of the mobile terminal  52  or  53  and the time point of the link authentication, compares the user ID and the time point with the content of the record information to confirm that the record information is not the fake. 
     Another method can also be selected in which a content text and a secret key (or a unique key) is input to a hash function and the output value is added to the certificate as a digital sign as well as the above method in which the certificate itself is encrypted. In such a case, the server can detect the fake in the certificate by verifying the sign with the use of the opened key (or the unique key) corresponding to the mobile terminal or the like. 
     It is possible to further enhance the reliability of the record information by allowing the link authentication result to be included in the certificate as described above. 
     In addition, the record information obtained as described above is used not only for the effective distribution of content but also for various purposes. 
     For example, a content distribution system  12  is assumed in which content is sequentially downloaded from a mobile terminal of a user to a mobile terminal of another user as shown in  FIG. 40 . In the example of  FIG. 40 , the mobile terminals  61  and  65  download the content data from the server  23 . 
     In addition, the configuration described above with reference to  FIG. 4  is applied to the server  23  as well. 
     The mobile terminals  62  and  66  download the content from the mobile terminals  61  and  65 , respectively. Moreover, the mobile terminals  63  and  67  download the content from the mobile terminals  62  and  66 , respectively. 
     Then, the mobile terminals  61 ,  62 ,  65 , and  66  transmit the record information to the server  23 . 
     In such a content distribution system  12 , it is possible to specify the user as a core for the content provision based on the record information. 
     The server  23  can recognize to which mobile terminal each mobile terminal has provided the content based on the record information.  FIG. 41  is a diagram showing an example of a network map created by regarding respective mobile terminals in the record information as nodes. The circle in the drawing represents the node, and the node which is connected to more nodes is represented as a bigger circle. 
     It is considered that the mobile terminal which has provided the contents to more mobile terminals is the mobile terminal with high importance in the content distribution system  12  and the content evaluation by the user of the mobile terminal greatly affects the selling of the content. Thus, the server  23  specifies the user as a core based on the record information. 
     Although the server  23  may simply determine the user of the mobile terminal, who has provided the content to the largest number of the mobile terminals, it is also possible to specify the user who effectively becomes the core, based on the record information. 
     For example, the server  23  specifies the user as a core by computing an evaluation value corresponding to the number of the users to which the user has provided the content and comparing the evaluation values. At this time, the evaluation value is computed by performing the weighting as will be described later. 
     For example, the server  23  obtains the information representing the number of users to which the individual mobile terminals have provided the content based on the “user IDs” in the record information, for example. Then, the server  23  specifies the type and the category of the provided content based on the “content ID” in the record information, for example, and performs the weighting of the users who have provided the content based on the specification result. 
     In so doing, it is possible to specify the user as a core for music content or game content, for example. 
     In addition, the server  23  performs the weighting of the users who have provided the content based on the “provision start time” or the “provision completion time” in the record information, for example. The users who have recently provided the content are weighted more heavily, for example. 
     In so doing, it is possible to specify the user as a core in consideration of the timeliness of the record information. 
     The server  23  may further perform the weighting of the users after receiving the evaluation information from the server  21 , for example. For example, the server  23  can obtain the identification information of the mobile terminal of the user based on the user ID of the record information. The server  23  obtains the evaluation information from the server based on the identification information of the mobile terminal. Then, the users of the mobile terminal from which evaluation information including longer comments was obtained are weighted more heavily. 
     As described above, it is possible to specify the users as cores in consideration of whether or not the content has been provided to the users who are interested in the content, for example. 
     The server  23  calculates the evaluation value of the user of each mobile terminal as described above, for example. When the evaluation value of the n-th User n  is represented as V (User n ), the evaluation value of the user is computed based on the equation (1). 
     
       
         
           
             
               
                 
                   
                     V 
                     ⁡ 
                     
                       ( 
                       
                         User 
                         n 
                       
                       ) 
                     
                   
                   = 
                   
                     
                       ∑ 
                       
                         i 
                         = 
                         0 
                       
                       M 
                     
                     ⁢ 
                     
                       
                         Cat 
                         i 
                       
                       · 
                       
                         Time 
                         i 
                       
                       · 
                       
                         Eval 
                         i 
                       
                     
                   
                 
               
               
                 
                   ( 
                   1 
                   ) 
                 
               
             
           
         
       
     
     In Equation (1), the variable i is a variable indicating the user ID included in the record information transmitted from the mobile terminal of the n-th user (referred to as a target user) as the target of the evaluation, and M user IDs are included here. That is, the n-th target user provided the content to M users. In addition, the user to whom the target user has provided the content will be referred to as a provision destination user here. 
     In addition, Cat i  in the equation (1) indicates the weight of the provision destination user calculated based on the “content ID” in the record information. Time i  indicates the weight of the provision destination user calculated based on the “provision start time” or the “provision completion time” in the record information. Eval i  indicates the weight of the provision destination user calculated based on the evaluation information. 
     In addition to this, the weighting based on the age and the sex of the provision target user may be performed. 
     The user specified by the evaluation value described above with reference to the equation (1) can be considered to be a user as a start point for the content provision, namely a so-called hub user. However, it is also possible to specify the user with high importance in the content provision from another view point. 
     For example, when users form a group, the content provision is performed within the group in many cases. For example, a case will be considered in which the content is sequentially downloaded between the users who are students. In such a case, the content is relatively easily downloaded between the users who belong to a same club. However, the content is downloaded by the users belonging to another club in less cases. 
     In such a case, it is considered that the view point of whether or not the user has provided the content to the users in another club becomes more important than the view point of how many users the user has provided to the content, in order to specify the user as a core. That is, since it is considered that the content is easily downloaded within individual clubs, the user as a connector who connects a club and another club is important. 
     For example, the server  23  can obtain the history of the past content provision for each user of each mobile terminal by analyzing the record information. For example, it is possible to create a list of users who provided the content in the past three month as a history of the past content provision for each of the user of each mobile terminal. 
     The server  23  can specify the user as a connector based on such content provision history.  FIG. 42  is a diagram illustrating a scheme which specifies the user as a connector. In the drawing, each user is shown as a node represented by a circle with the corresponding reference numerals of U 1 , U 2 , or the like. Now, it is determined whether or not the user as the node shown by U 1  in the drawing is the user as a connector. 
     The server  23  creates a list of the users to whom the user U 1  provided the content in the past three months based on the already accumulated record information. In this case, the user U 1  provided the content to the users U 9  and U 10  in the past. 
     The server  23  creates a list of the users to whom the users U 9  and U 10  provided the content in the past three months based on the already accumulated record information. In this case, the user U 9  provided the content to the users U 11 , U 5 , and U 12 . In addition, the user U 10  provided the content to the users U 8  and U 13 . 
     As described above, the assigned group of the user U 1  is specified. 
     The server  23  determines that the user U 1  provided the content to the user U 2  based on the record information newly transmitted from the mobile terminal of the user U 1 . The server  23  specifies the assigned group of the user U 2  (referred to as a provision destination group) based on the already accumulated record information in the same manner as in the aforementioned case. 
     Then, the server  23  counts the number of the users duplicated between the assigned group and the provision destination group. In this example, the users U 5  and U 8  are duplicated, the number of duplicated users is two. In addition, the server  23  counts the number of the users (referred to as unique users) who are not duplicated between the assigned group and the provision destination group. In this example, the number of unique users is five in each of the assigned group and the provision destination group. 
     The server  23  sums up the number of unique users in the assigned group and the number of unique users in the provision destination group, for example, to calculate the evaluation value of the user as a connector. Then, the user as a connector is specified based on the calculated evaluation value. 
     The description was made of the example of  FIG. 42  in which the group depths of the assigned group and the provision destination group were three. That is, the assigned group and the provision destination group were formed based on the content provision history of three levels from the user U 1  and the user U 2  as the start points. The group depth for specifying the user as a connector in practice may arbitrarily be set. 
     As described above, the server  23  can specify a user as a hub or a user as a connector. Such user information is important for viral marketing, for example. The operator of the server  23  can provide a service such as providing the information relating to the user as a hub or a connector specified as described above to the content business operator such as a game software manufacturer or the like. 
     Next, description will be given of the processing by the server  22  with reference to the flow chart in  FIG. 43 . This processing is executed when the content distribution based on the record information is ordered, for example. 
     The server  22  receives the record information in Step S 3011 . At this time, the record information transmitted from the mobile terminals  51  and  55  in  FIG. 37  is received, for example. 
     The server  21  analyzes the record information, which has been received in Step S 3011 , in Step S 3012 . At this time, the analysis is performed for specifying the mobile terminal with the best record in the content provision, for example. The fact that the record in the provision is good may mean that the mobile terminals have provided the content to more users in unit time or that the mobile terminals have provided the content to the users of the ages, sexes, addresses, and tastes of the promotion target, for example. When the goal of the promotion is to increase fans in the young generation, the record information is filtered with the “age” in the information relating to the “content provision destination”, and the record in the provision by the mobile terminals which have provided the content to more users of the ages less than a threshold value is considered to be good. 
     The record information may be filtered based on the content of the information (the user authentication result, the link authentication result, or both) included in the certificate and the effectiveness thereof. 
     In Step S 3013 , the server  22  quantifies the level of the record in the provision by each mobile terminal based on the result of the processing of Step S 3012 . 
     In Step S 3014 , the server  22  distributes the content of the subsequent new song with priority based on the result of the processing of Step S 3013 . 
     At this time, the mobile terminal with the good record in the provision is specified by mutually comparing the numerical values of the mobile terminals obtained as the result of the processing of Step S 3013  or by comparing the numerical values with a preset threshold value, for example. Then, when the server  22  determines that the record in the provision by the mobile terminal  51  is good, the server  22  allows the mobile terminal  51  to download the content of the subsequent new song for free. Alternatively, the server  22  may allow a plurality of mobile terminals for which the better record in the provision than a preset reference has been conformed to download the content of the subsequent new song for free, or the server  22  may allow the mobile terminals to download the content of the new song for free in order from the mobile terminal with the best record in the provision with time differences. 
     Alternatively, a bonus advantage such as a ticket for a concert or the like may be given to the mobile terminal with the best record in the provision. 
     As described above, the processing by the server  22  is executed. 
     Next, description will be given of the processing by the server  23  with reference to the flow chart in  FIG. 44 . This processing is executed when the specification of a hub user or a connector user based on the record information is ordered, for example. 
     The server  23  receives the record information in Step S 3031 . At this time, the record information transmitted from the mobile terminals  62  and  67  in  FIG. 40  is received, for example. 
     The server  23  analyzes the record information, which has been received in Step S 3032 , in Step S 3032 . 
     At this time, the server  23  obtains the information representing to how many users the individual mobile terminals have provided the content based on the user IDs in the record information, for example. Then, the server  23  specifies the type, the category, and the like of the provided content based on the “content ID” in the record information and performs weighting of the users who have provided the content based on the specification result. 
     Alternatively, the server  23  may perform the weighting of the users who have provided the content based on the “provision start time” or the “provision completion time” of the record information, for example. Furthermore, the server  23  obtains the evaluation information from the server based on the identification information of the mobile terminal. Then, the users of the mobile terminal from which evaluation information including longer comments was obtained are weighted more heavily. 
     The analysis result is used in the hub user specification processing which will be described later. 
     In addition, the server  23  creates a list of the users who provided the content in the past three months for each user of each mobile terminal at this time, for example, to create the history of the past content provision. 
     Such an analysis result is used in the connector user specification processing which will be described later. 
     The server  23  executes the hub user specification processing in Step S 3033 . Here, the evaluation value of the user of each mobile terminal is calculated based on the result of the processing of Step S 3032 , for example. The user evaluation value is computed based on the aforementioned equation (1). 
     As described above, a hub user is specified. 
     The server  23  executes the connector user specification processing in Step S 3034 . Here, the number of the users duplicated between the assigned group and the provision destination group is counted as described above with reference to  FIG. 42  based on the result of the processing of Step S 3032 , for example. The number of the unique users who are not duplicated between the assigned group and the provision destination group is counted, and then number of the unique users in the assigned group and the number of the unique users in the provision destination group are summed up to calculate the evaluation values of the users as connectors. 
     As described above, the connector user is specified. 
     In Step S 3035 , the server  23  outputs the user ID of the hub user specified in the processing of Step S 3033  or the user ID of the connector user specified in the processing of Step S 3034 . 
     As described above, the processing by the server  23  is executed. 
     The description was given of the embodiments described above with reference to  FIGS. 37 to 44  as examples in which the server  22  more effectively distribute the content based on the record information relating to the content provision by the mobile terminal with the handover function or in which the server  23  specifies the hub user or the connector user. However, the record information processed by the server  22  or  23  is not limited to the record information relating to the content provision by the mobile terminal with the handover function. For example, the record information relating to the content provision by a terminal which provides content via wired communication may be processed, for example. 
     In addition, the description was given of the embodiments described above with reference to  FIGS. 37 to 44  as an example in which the record information relating to the content provision is handled. However, the present disclosure can be applied to the case in which the record information relating to the provision of electronic information properties other than content is handled, for example. 
     Although the above description was made of a case in which the non-contact communication is performed at the time of the handover and the near field wireless communication is then performed, the embodiments to which the present disclosure can be applied are not limited thereto. For example, contact type communication in which a terminal is brought to be in contact may be used instead of the non-contact communication such as the NFC or the like, or the ordinary wired LAN may be used instead of the near field wireless communication. 
     Although the above description was given of a case in which the wireless communication for the mobile communication network was used for the broad area communication performed between the server and the mobile terminal or the like, the embodiments to which the present disclosure can be applied are not limited thereto. For example, communication with the use of fixed communication network communication or the unique network may be used instead of the wireless communication for the mobile communication network. 
     The aforementioned series of processes can be executed by hardware or software. When the aforementioned series of processes is executed by the software, the program configuring the software is installed on a computer embedded in the dedicated hardware from the network or a recording medium. Alternatively, the various programs are installed on a general personal computer capable of performing various functions from the network or the recording medium. 
     When the aforementioned series of processes is executed by the software, the program constituting the software is installed from the network such as the Internet or the like or a recording medium such as a removable medium or the like. 
     It is matter of course that the series of processes described above in this specification is not necessarily performed in the time series manner but may include the processes executed in parallel or individually executed. 
     The embodiments of the present disclosure are not limited to the aforementioned embodiments, and various modifications can be made within the range of the scope of the present disclosure.