Contradiction determination device, communication control device, and contradiction determination method

Abstract

This contradiction determination device comprises: a first acquisition unit that acquires metadata indicating at least a situation when content is generated by a terminal of a user, among data associated with the content; a second acquisition unit that acquires action data indicating a history of actions of the user using the terminal, among data managed by a service provider; and a metadata determination unit that determines whether or not the metadata is contradictory on the basis of a relationship between the situation indicated by the metadata and the history of actions of the user indicated by the action data.

Description

Conflict determination device, communication control device, and conflict determination method

[0001] The present disclosure relates to a technique for determining whether metadata conflicts.

[0002] Patent Document 1 discloses a forgery detection device that detects forgery of metadata attached to image data. The metadata indicates a script that is a hash function and a hash value of the program string of the script. The forgery detection device calculates the hash value of the program string of the script using the script. The forgery detection device compares the calculated hash value with the hash value indicated in the metadata. The forgery detection device determines whether the metadata has been forged based on the result of the comparison.

[0003] Japanese Unexamined Patent Application Publication No. 2019-41192

[0004] The forgery detection device described in Patent Document 1 cannot determine whether the metadata has been forged when the metadata does not indicate a script. That is, the forgery detection device described in Patent Document 1 cannot determine whether the metadata conflicts when the metadata does not indicate a script.

[0005] An object of the present disclosure is to provide a technique capable of determining whether metadata conflicts even when the metadata does not indicate a script.

[0006] A conflict determination device according to an aspect of the present disclosure includes a first acquisition unit that acquires metadata that at least indicates a situation when the content is generated by a user's terminal among data attached to the content, a second acquisition unit that acquires behavior data indicating a history of the user's behavior using the terminal among data managed by a service provider, and a metadata determination unit that determines whether the metadata conflicts based on a relationship between the situation indicated by the metadata and the history of the user's behavior indicated by the behavior data.

[0007] A communication control device according to another aspect of the present disclosure includes the inconsistency determination device and a communication control unit that prohibits the transmission of the content based on the determination that the metadata is inconsistent.

[0008] A method for determining inconsistencies relating to yet another aspect of this disclosure includes: obtaining metadata from data associated with the content that at least indicates the circumstances under which the content was generated by the user's terminal; obtaining behavioral data from data managed by the service provider that indicates the history of the user's actions using the terminal; and determining whether the metadata is inconsistent based on the relationship between the circumstances indicated by the metadata and the history of the user's actions indicated by the behavioral data.

[0009] According to this disclosure, a technology is provided that can determine whether metadata is inconsistent or not, even if the metadata does not indicate a script.

[0010] This is a diagram showing an example of a content management system CS. This is a diagram showing an example of metadata M1. This is a diagram showing an example of a service provision server 40. This is a diagram showing an example of service history data D1. This is a diagram showing an example of a terminal 20. This is a diagram showing an example of judgment data D3. This is a diagram showing an example of metadata M1. This is a diagram showing record R2 determined as the corresponding record. This is a diagram for explaining the operation of terminal 20. This is a diagram for explaining the operation of terminal 20 in the first modified example. This is a diagram showing an example of terminal 20a. This is a diagram for explaining the operation of terminal 20a. This is a diagram showing an example of camera operation data D1a.

[0011] 1: Embodiment 1-1: Content Management System CS Figure 1 is a diagram showing an example of a content management system CS.

[0012] The content management system CS manages content. The content management system CS includes a content distribution server 10, terminal 20, and terminal 30. The content management system CS may also include other terminals.

[0013] The content distribution server 10 manages the distribution of content. For example, the content distribution server 10 stores content provided by terminal 20. The content distribution server 10 provides the content provided by terminal 20 to terminal 30 in response to a request from terminal 30.

[0014] Content is accompanied by metadata. For example, content provided by terminal 20 is accompanied by metadata M1.

[0015] Figure 2 shows an example of metadata M1. Metadata M1 includes location data G1 and date / time data G2. Metadata M1 may also include other data.

[0016] Location data G1 indicates the location of terminal 20 when the content was generated by terminal 20. If the content is image data generated by the camera 22 of terminal 20, location data G1 indicates the location of the region represented by the image data.

[0017] The date and time data G2 indicates the date and time when the content was generated by terminal 20. If the content is image data generated by the camera 22 of terminal 20, the date and time data indicates the date and time when the camera 22 performed the image capture. The date and time indicated by the date and time data G2 is set to the date and time that terminal 20 is counting when the content was generated by terminal 20.

[0018] Metadata M1 indicates at least the circumstances under which the content was generated by user U1's terminal 20. Hereinafter, the circumstances under which the content was generated by user U1's terminal 20 will be referred to as the "content generation circumstances." The content generation circumstances are, for example, a combination of the location of terminal 20 when the content was generated by user U1's terminal 20 and the date and time when the content was generated by user U1's terminal 20. The location of terminal 20 when the content was generated by user U1's terminal 20 is indicated by the location data G1 of metadata M1. The date and time when the content was generated by user U1's terminal 20 is indicated by the date and time data G2 of metadata M1.

[0019] Metadata M1 can be tampered with. If the location data G1 of metadata M1 is tampered with, the tampered location data G1 will indicate a different location from the location of the region represented by the image data, which is an example of the content. Therefore, metadata M1 becomes contradictory. Consequently, the reliability of the content decreases. If the date and time data G2 of metadata M1 is tampered with, the tampered date and time data G2 will indicate a different date and time from the date and time the content was created. Therefore, metadata M1 becomes contradictory. Consequently, the reliability of the content decreases.

[0020] Furthermore, metadata M1 containing incorrect information may be generated. For example, if content is generated by terminal 20 while terminal 20 is counting an incorrect date and time, metadata M1 containing date and time data G2 indicating an incorrect date and time will be generated. Metadata M1 containing date and time data G2 indicating an incorrect date and time is contradictory. Therefore, the reliability of the content is reduced. Note that the situation in which terminal 20 is counting an incorrect date and time can occur, for example, by manipulating terminal 20 to count an incorrect date and time.

[0021] In Figure 1, terminal 20 determines whether metadata M1 is inconsistent using data managed by the service provider SP operating the service server 40. For example, terminal 20 uses behavioral data, which shows the history of user U1's actions using terminal 20, from the data managed by the service provider SP, to determine whether metadata M1 is inconsistent. Details of the determination will be described later. Note that the service provider SP is, for example, the company operating the service server 40.

[0022] Terminal 20 may determine whether metadata M1 is inconsistent using behavioral data managed by service provider SP and behavioral data managed by a service provider different from service provider SP.

[0023] Terminal 20 may determine whether the metadata M1 is inconsistent using behavioral data managed by the service provider SP and behavioral data managed by each of several service providers different from the service provider SP.

[0024] If terminal 20 determines that metadata M1 is inconsistent, it will prohibit the provision of content to the content distribution server 10. This prevents a decline in the reliability of the content distributed by the content distribution server 10.

[0025] 1-2: Service Provider Server 40 Figure 3 shows an example of a service provider server 40. The service provider server 40 is an example of a device managed by a service provider SP. The service provider server 40 is a server composed of multiple computers. The service provider server 40 may be composed of a single computer. The service provider server 40 can communicate with the terminal 20 via a communication network NW. The service provider server 40 may also be able to communicate with the terminal 20 without using a communication network NW. The service provider server 40 may also be able to communicate with the terminal 30.

[0026] The service provider server 40 provides service B1 to user U1 of terminal 20. Service B1 is a service that is used by terminal 20. Service B1 is, for example, a QR code (registered trademark) payment service. In the QR code payment service, payment is made using the QR code displayed on terminal 20.

[0027] A QR code payment service is one example of a payment service that uses terminal 20. However, payment services that use terminal 20 are not limited to QR code payment services. For example, a payment service that uses terminal 20 may be a credit card payment service that uses terminal 20, or a points payment service that uses terminal 20.

[0028] A payment service using terminal 20 is an example of service B1. Service B1 is not limited to a payment service using terminal 20. For example, service B1 may be a ticket gate service using terminal 20, an unlocking service using terminal 20, or an access control service using terminal 20.

[0029] In the following explanation, for the sake of simplicity, we will describe an example where service B1 is a payment service using terminal 20.

[0030] The service provider server 40 includes a communication device 41, a storage device 42, a processing device 43, and a bus 44.

[0031] Bus 44 is a wiring configuration for transmitting information. Bus 44 connects the communication device 41, the storage device 42, and the processing device 43. Bus 44 may consist of a single bus, or it may consist of various buses provided between the devices.

[0032] The communication device 41 can communicate with the terminal 20 via the communication network NW. The communication device 41 may also communicate with the terminal 20 without using the communication network NW.

[0033] The storage device 42 is a recording medium that can be read by the processing device 43. The storage device 42 includes at least one memory. The storage device 42 includes, for example, non-volatile memory and volatile memory. Non-volatile memory is, for example, ROM (Read Only Memory), EPROM (Erasable Programmable Read Only Memory), and EEPROM (Electrically Erasable Programmable Read Only Memory). Volatile memory is, for example, RAM (Random Access Memory) and VRAM (Video Random Access Memory). The storage device 42 stores program PG1 and service history data D1. Program PG1 includes a plurality of instructions.

[0034] Service history data D1 shows the history of services B1 provided to user U1 using terminal 20. The history of services B1 provided to user U1 using terminal 20 represents the history of user U1's actions using terminal 20. Therefore, service history data D1 shows the history of user U1's actions using terminal 20. As mentioned above, an example of service B1 is a payment service using terminal 20.

[0035] Figure 4 shows an example of service history data D1. Service history data D1 shows multiple records. Each of the multiple records represents a payment. Each of the multiple records is identified by a payment number E0. Each of the multiple records shows date and time E1, location E2, and amount E3. Date and time E1 is the date and time when the payment was made using terminal 20. Location E2 is indicated by the name of the store where the payment was made using terminal 20. Amount E3 is the amount of the payment made using terminal 20.

[0036] Service history data D1 shows the date and time E1 and location E2 for each transaction. Therefore, record R1 shown in service history data D1 indicates that user U1 used terminal 20 at "AAA Store Tokyo Branch" at "18:05 on November 28, 2024". Record R2 shown in service history data D1 indicates that user U1 used terminal 20 at "BBB Store Tokyo Branch" at "15:10 on November 28, 2024". In this way, service history data D1 shows the history of user U1's actions using terminal 20. Service history data D1 is an example of action data showing the history of user U1's actions using terminal 20.

[0037] Service history data D1 is managed by the service provider SP. Therefore, it is difficult to tamper with service history data D1. For example, it is difficult for user U1 to tamper with service history data D1.

[0038] In Figure 3, the processing unit 43 includes at least one CPU (Central Processing Unit). The at least one CPU is an example of at least one processor. The at least one processor is an example of at least one computer. The processing unit 43 reads program PG1 from the storage device 42. The processing unit 43 functions as an operation control unit 431 by executing program PG1.

[0039] The operation control unit 431 controls the operation of the service provision server 40. For example, the operation control unit 431 provides service B1 to user U1 using terminal 20. Each time service B1 is provided to user U1 using terminal 20, the operation control unit 431 adds data indicating the record of the provision of service B1 to user U1 using terminal 20 to the service history data D1. The operation control unit 431 provides the service history data D1 to terminal 20. For example, the operation control unit 431 provides the service history data D1 to terminal 20 in response to a request from terminal 20. The operation control unit 431 may be composed of circuits such as a DSP (Digital Signal Processor), ASIC (Application Specific Integrated Circuit), or FPGA (Field Programmable Gate Array).

[0040] 1-3: Terminal 20 Figure 5 shows an example of terminal 20. Terminal 20 is an example of a contradiction detection device. Terminal 20 is also an example of a communication control device. Terminal 20 is, for example, a smartphone. Terminal 20 is not limited to a smartphone. For example, terminal 20 may be a tablet or a laptop computer. Terminal 20 is used by user U1.

[0041] The terminal 20 includes an input device 21, a camera 22, a display device 23, a GPS (Global Positioning System) module 24, a communication device 25, a storage device 26, a processing device 27, and a bus 28.

[0042] Bus 28 is a wiring for communicating information. Bus 28 connects an input device 21, a camera 22, a display device 23, a GPS module 24, a communication device 25, a storage device 26, and a processing device 27 to each other. Bus 28 may be constituted by a single bus, or may be constituted by various buses provided for each device.

[0043] Input device 21 is the user interface of terminal 20. Input device 21 includes a touch panel. Input device 21 may include a plurality of operation keys in addition to the touch panel. Input device 21 may include a plurality of operation keys without including the touch panel. Input device 21 may include a voice input device such as a microphone. Input device 21 receives various inputs from user U1. For example, input device 21 receives an instruction to start a payment application AP1 described later. Also, input device 21 receives an instruction to start a determination application AP2 described later.

[0044] [[ID=**6**]]Camera 22 generates content C1 by executing imaging. Content C1 is, for example, image data showing a still image. Content C1 is not limited to image data showing a still image. For example, content C1 may be image data showing a moving image. Camera **22** is an example of a content generation device that generates content. The content generation device is not limited to camera 22 as long as it is a device mounted on terminal 20 that generates content. For example, the content generation device may be a microphone mounted on terminal 20. The microphone mounted on terminal 20 generates sound data indicating sound as content C1.

[0045] Display device 23 displays various information. For example, display device 23 displays content C1 generated by camera 22.

[0046] Note: There was a typo in the original Japanese text where the same variable "Camera 22" was used twice in the English translation for the Chinese translation of "カメラ22". I've corrected it to make the translation more accurate.The GPS module 24 generates position data F1 indicating the position of the terminal 20. The GPS module 24 generates the position data F1 based on satellite signals from GPS satellites. The GPS module 24 generates the position data F1 in response to the camera 22 generating the content C1. Therefore, the position data F1 indicates the position of the terminal 20 when the content C1 is generated by the user U1's terminal 20.

[0047] The communication device 25 can communicate with the service providing server 40 via the communication network NW. The communication device 25 may be able to communicate with the service providing server 40 without going through the communication network NW. Also, the communication device 25 can communicate with the content distribution server 10 via the communication network NW. The communication device 25 may be able to communicate with the content distribution server 10 without going through the communication network NW. The communication device 25 may be able to communicate with the terminal 30 via the communication network NW. The communication device 25 may be able to communicate with the terminal 30 without going through the communication network NW.

[0048] The storage device 26 is a recording medium readable by the processing device 27. The storage device 26 includes at least one memory. The storage device 26 includes, for example, a non-volatile memory and a volatile memory. The storage device 26 stores the program PG2, the payment application AP1, the determination application AP2, the map data D2, and the determination data D3.

[0049] The program PG2 includes a plurality of instructions. The program PG2 defines a plurality of operations of the terminal 20. The plurality of operations of the terminal 20 includes an operation of counting the current date and time. The plurality of operations of the terminal 20 further includes an operation of generating metadata M1 associated with the content C1 in response to the camera 22 generating the content C1. The plurality of operations of the terminal 20 may include other operations.

[0050] The payment application AP1 is an application program that defines an operation of receiving the service B1 from the service providing server 40. The payment application AP1 includes a plurality of instructions. The payment application AP1 is managed by the service provider SP.

[0051] The judgment application AP2 is an application program that defines the operation to determine whether or not metadata M1 is inconsistent. Furthermore, the judgment application AP2 defines the operation to determine whether or not to send content C1, which contains metadata M1, to the content distribution server 10. The judgment application AP2 includes multiple instructions.

[0052] Map data D2 indicates the locations of objects such as buildings. For example, map data D2 indicates the locations of various shops. Map data D2 may be included in the judgment application AP2. Map data D2 does not have to be stored in the storage device 26. For example, map data D2 may be stored in a map server that can communicate with terminal 20. In this case, terminal 20 refers to map data D2 stored in the map server by communicating with the map server.

[0053] The judgment data D3 indicates the travel time required to move between two locations. The judgment data D3 indicates the travel time for each pair of locations.

[0054] Figure 6 shows an example of judgment data D3. The judgment data D3 shown in Figure 6 indicates, for example, that a movement time J1 is required for movement between position "XXX" and position "YYY".

[0055] The judgment data D3 may be included in the judgment application AP2. The judgment data D3 does not have to be stored in the storage device 26. For example, the judgment data D3 may be stored in a server that can communicate with the terminal 20. In this case, the terminal 20 refers to the judgment data D3 stored in the server by communicating with the server.

[0056] In Figure 5, the processing unit 27 is another example of a contradiction determination device. The processing unit 27 is also another example of a communication control device. The processing unit 27 includes at least one CPU.

[0057] The processing unit 27 reads the program PG2 from the storage device 26. By executing the program PG2, the processing unit 27 functions as a date and time counter 271 and a metadata generation unit 272. The date and time counter 271 and the metadata generation unit 272 may each be configured by circuits such as a DSP, ASIC, or FPGA.

[0058] The processing unit 27 reads the payment application AP1 from the storage device 26 in response to an instruction to start the payment application AP1. By executing the payment application AP1, the processing unit 27 functions as a payment control unit 273. The payment control unit 273 may be composed of circuits such as a DSP, ASIC, or FPGA.

[0059] The processing unit 27 reads the judgment application AP2 from the storage device 26 in response to an instruction to start the judgment application AP2. By executing the judgment application AP2, the processing unit 27 functions as a contradiction determination unit 274 and a communication control unit 275. The contradiction determination unit 274 and the communication control unit 275 may each be composed of circuits such as a DSP, ASIC, or FPGA.

[0060] The date and time counter 271 counts the current date and time. The date and time counter 271 outputs date and time data F2 indicating the current date and time. A real-time clock may be used instead of the date and time counter 271.

[0061] The metadata generation unit 272 generates metadata M1. For example, the metadata generation unit 272 acquires location data F1 generated by the GPS module 24 in response to the camera 22 generating content C1 as location data G1. The metadata generation unit 272 also acquires date and time data F2 output by the date and time counter 271 when the camera 22 generates content C1 as date and time data G2. The metadata generation unit 272 generates metadata M1 which includes at least the location data G1 and the date and time data G2. The metadata generation unit 272 adds the metadata M1 to the content C1. Therefore, the metadata M1 is associated with the content C1.

[0062] The payment control unit 273 performs the operation of receiving service B1 from the service provider server 40. For example, the payment control unit 273 performs a payment using terminal 20 by communicating with the service provider server 40. The payment control unit 273 operates when payment application AP1 is active. For example, the payment control unit 273 operates when payment application AP1 is in the foreground.

[0063] The inconsistency determination unit 274 determines whether the metadata M1 is inconsistent or not. The inconsistency determination unit 274 operates when the determination application AP2 is active. For example, the inconsistency determination unit 274 operates when the determination application AP2 is in the foreground. The inconsistency determination unit 274 includes a first acquisition unit 274a, a second acquisition unit 274b, and a metadata determination unit 274c.

[0064] The first acquisition unit 274a acquires metadata M1 from the data associated with content C1. For example, the first acquisition unit 274a acquires metadata M1 when the judgment application AP2 is active.

[0065] The second acquisition unit 274b acquires service history data D1 from the data managed by the service provider SP. As described above, service history data D1 is an example of behavioral data showing the history of user U1's actions using terminal 20. For example, the second acquisition unit 274b acquires service history data D1 when the judgment application AP2 is active.

[0066] For example, in a situation where payment application AP1 and judgment application AP2 are logged in with the same account, the second acquisition unit 274b of judgment application AP2 uses that account to acquire service history data D1 from the service provision server 40.

[0067] Furthermore, if the payment application AP1 is permitted to access the judgment application AP2, the second acquisition unit 274b of the judgment application AP2 may acquire the service history data D1 from the service provision server 40 via the payment application AP1.

[0068] If the payment application AP1 is authorized to receive service history data D1 from the judgment application AP2, and the service history data D1 is stored in the payment application AP1, the second acquisition unit 274b of the judgment application AP2 acquires the service history data D1 from the payment application AP1.

[0069] If the service history data D1 is stored in the storage device 26 of the terminal 20, the second acquisition unit 274b acquires the service history data D1 from the storage device 26.

[0070] The metadata determination unit 274c determines whether the metadata M1 is inconsistent or not. The metadata determination unit 274c operates when the determination application AP2 is active. For example, the metadata determination unit 274c operates when the determination application AP2 is in the foreground.

[0071] The metadata determination unit 274c determines whether the metadata M1 is inconsistent based on the relationship between the content generation status indicated by the metadata M1 and the history of user U1's actions indicated by the service history data D1.

[0072] For example, if the relationship between the content generation status indicated by metadata M1 and the history of user U1's actions is contradictory, the metadata determination unit 274c determines that metadata M1 is contradictory.

[0073] On the other hand, if the relationship between the content generation status indicated by metadata M1 and the history of user U1's actions is not contradictory, the metadata determination unit 274c determines that metadata M1 is not contradictory.

[0074] For example, the metadata determination unit 274c determines, from among the multiple records shown in the service history data D1, the record showing the date and time E1 that is closest to the date and time indicated by the date and time data G2 of the metadata M1, as the corresponding record.

[0075] The metadata determination unit 274c identifies the location of place E2 shown in the corresponding record by referring to the map data D2.

[0076] The metadata determination unit 274c calculates the difference between the date and time indicated by the date and time data G2 of the metadata M1 and the date and time E1 indicated in the corresponding record as the estimated travel time.

[0077] The metadata determination unit 274c determines a pair of locations, specifically the location E2 shown in the corresponding record and the location data G1 in the metadata M1, as a corresponding pair.

[0078] The metadata determination unit 274c determines the travel time H3 for the corresponding pair by referring to the determination data D3.

[0079] If the estimated travel time is shorter than the travel time H3 for the corresponding pair, the metadata determination unit 274c determines that the relationship between the content generation status indicated by metadata M1 and the history of user U1's actions is contradictory. In other words, if the estimated travel time is shorter than the travel time H3 for the corresponding pair, the metadata determination unit 274c determines that metadata M1 is contradictory.

[0080] If the estimated travel time is equal to or greater than the travel time H3 for the corresponding pair, the metadata determination unit 274c determines that there is no contradictory relationship between the content generation status indicated by metadata M1 and the history of user U1's actions. In other words, if the estimated travel time is equal to or greater than the travel time H3 for the corresponding pair, the metadata determination unit 274c determines that metadata M1 is not contradictory.

[0081] Here, we will explain the operation of the metadata determination unit 274c in a situation where metadata M1 indicates that "terminal 20 generated content in Kita-ku, Osaka City, Osaka Prefecture at 15:20 on November 28, 2024," as shown in Figure 7.

[0082] In this case, the metadata determination unit 274c determines record R2, shown in Figure 4, as the corresponding record. Figure 8 shows record R2, which has been determined as the corresponding record.

[0083] Next, the metadata determination unit 274c identifies the location of place E2, which is shown in the corresponding record, record R2, by referring to the map data D2. In the following, we assume that the location of place E2 shown in the corresponding record is "Minato-ku, Tokyo".

[0084] In this case, the corresponding record, record R2, indicates that "user U1 used terminal 20 in Minato-ku, Tokyo at 15:10 on November 28, 2024." Meanwhile, metadata M1, as described above, indicates that "terminal 20 generated content in Kita-ku, Osaka City, Osaka Prefecture at 15:20 on November 28, 2024."

[0085] Next, the metadata determination unit 274c calculates the difference between the date and time indicated by the date and time data G2 of metadata M1, "15:20 on November 28, 2024," and the date and time E1 indicated in the corresponding record, "15:10 on November 28, 2024," as the estimated travel time. In this case, the estimated travel time is "10 minutes."

[0086] Next, the metadata determination unit 274c determines that the location E2 "Minato-ku, Tokyo" shown in the corresponding record and the location G1 "Kita-ku, Osaka City, Osaka Prefecture" shown in the metadata M1 are a corresponding pair.

[0087] Next, the metadata determination unit 274c identifies the travel time H3 for the corresponding pair by referring to the determination data D3. In the following, we assume that the travel time H3 for the corresponding pair of "Minato-ku, Tokyo" and "Kita-ku, Osaka-shi, Osaka-sen" is "3 hours".

[0088] Since the estimated travel time of "10 minutes" is shorter than the travel time H3 of "3 hours" for the corresponding pair, the metadata determination unit 274c determines that there is a contradictory relationship between the content generation status indicated by metadata M1 and the history of user U1's actions. In other words, the metadata determination unit 274c determines that metadata M1 is contradictory.

[0089] Such inconsistent metadata M1 can result, for example, from the terminal 20 being manipulated to count an incorrect date and time before the content C1 is generated. Alternatively, inconsistent metadata M1 can result from the tampering of consistent metadata M1.

[0090] In Figure 5, the communication control unit 275 controls the transmission of content C1 to which metadata M1 has been added.

[0091] For example, the communication control unit 275 prohibits the transmission of content C1 based on the metadata determination unit 274c's determination that metadata M1 is inconsistent. The communication control unit 275 transmits content C1 with metadata M1 attached to the content distribution server 10 based on the metadata determination unit 274c's determination that metadata M1 is not inconsistent. The content distribution server 10 receives content C1 with metadata M1 attached. The content distribution server 10 stores content C1 with metadata M1 attached.

[0092] 1-4: Operation Diagram 9 is a diagram illustrating the operation of terminal 20. The operation shown in Figure 9 is initiated when the input device 21 of terminal 20 receives an imaging instruction while the judgment application AP2 is active. In the following, access from the judgment application AP2 is permitted to the payment application AP1.

[0093] In step S101, the camera 22 generates content C1 by performing image capture. In response to the camera 22 generating content C1, the GPS module 24 generates location data F1. The location data F1 indicates the location of the terminal 20 when content C1 was generated by the terminal 20.

[0094] Next, in step S102, the metadata generation unit 272 generates metadata M1. For example, the metadata generation unit 272 acquires location data F1 generated by the GPS module 24 as location data G1. The metadata generation unit 272 also acquires date and time data F2 output by the date and time counter 271 when the camera 22 generates content C1 as date and time data G2. The metadata generation unit 272 generates metadata M1 which includes at least the location data G1 and date and time data G2 as shown in Figure 2. The metadata generation unit 272 adds the metadata M1 to content C1.

[0095] Next, in step S103, the first acquisition unit 274a acquires metadata M1 from the data associated with content C1.

[0096] Next, in step S104, the second acquisition unit 274b acquires the service history data D1.

[0097] For example, the second acquisition unit 274b acquires service history data D1 from the service provision server 40 via the payment application AP1.

[0098] If the service history data D1 is stored in the payment application AP1, the second acquisition unit 274b acquires the service history data D1 from the payment application AP1.

[0099] If the service history data D1 is stored in the storage device 26 of the terminal 20, the second acquisition unit 274b acquires the service history data D1 from the storage device 26.

[0100] Step S104 may be executed during the period between the completion of step S102 and the start of step S103.

[0101] Next, in step S105, the metadata determination unit 274c determines whether or not the metadata M1 is inconsistent.

[0102] For example, the metadata determination unit 274c determines, from among the multiple records shown in the service history data D1, the record showing the date and time E1 that is closest to the date and time indicated by the date and time data G2 of the metadata M1, as the corresponding record.

[0103] The metadata determination unit 274c identifies the location of place E2 shown in the corresponding record by referring to the map data D2.

[0104] The metadata determination unit 274c calculates the difference between the date and time indicated by the date and time data G2 of the metadata M1 and the date and time E1 indicated in the corresponding record as the estimated travel time.

[0105] The metadata determination unit 274c determines a pair of locations, specifically the location E2 shown in the corresponding record and the location data G1 in the metadata M1, as a corresponding pair.

[0106] The metadata determination unit 274c determines the travel time H3 for the corresponding pair by referring to the determination data D3.

[0107] If the estimated travel time is shorter than the travel time H3 for the corresponding pair, the metadata determination unit 274c determines that the relationship between the content generation status indicated by metadata M1 and the history of user U1's actions is contradictory. In other words, if the estimated travel time is shorter than the travel time H3 for the corresponding pair, the metadata determination unit 274c determines that metadata M1 is contradictory.

[0108] If the estimated travel time is equal to or greater than the travel time H3 for the corresponding pair, the metadata determination unit 274c determines that there is no contradictory relationship between the content generation status indicated by metadata M1 and the history of user U1's actions. In other words, if the estimated travel time is equal to or greater than the travel time H3 for the corresponding pair, the metadata determination unit 274c determines that metadata M1 is not contradictory.

[0109] If the metadata determination unit 274c determines in step S105 that the metadata M1 is inconsistent, the communication control unit 275 prohibits the transmission of content C1 in step S106.

[0110] If the metadata determination unit 274c determines in step S105 that the metadata M1 is not contradictory, then in step S107, the communication control unit 275 transmits the content C1 with the metadata M1 attached to the content distribution server 10. The content distribution server 10 stores the content C1 with the metadata M1 attached.

[0111] In the operation shown in Figure 9, the generation of content C1 triggers a determination of whether metadata M1 is inconsistent or not. Therefore, it is possible to prevent tampering with metadata M1 during the period from the time metadata M1 is generated until the time the determination of whether metadata M1 is inconsistent or not is performed. Furthermore, it is possible to prevent tampering with content C1 during the period from the time content C1 is generated until content C1 is transmitted to the content distribution server 10. In addition, even if terminal 20 is operated to count an incorrect date and time before content C1 is generated, it is possible to determine that metadata M1 is inconsistent.

[0112] 1-5: Summary of Embodiments The terminal 20 includes a contradiction determination unit 274. The contradiction determination unit 274 includes a first acquisition unit 274a, a second acquisition unit 274b, and a metadata determination unit 274c.

[0113] The first acquisition unit 274a acquires metadata M1 from the data associated with content C1. Metadata M1 indicates at least the content generation status. The content generation status is the situation when content C1 was generated by user U1's terminal 20. The second acquisition unit 274b acquires service history data D1 from the data managed by the service provider SP. Service history data D1 is an example of behavior data that shows the history of user U1's actions using terminal 20. The metadata determination unit 274c determines whether metadata M1 is inconsistent based on the relationship between the content generation status indicated by metadata M1 and the history of user U1's actions indicated by service history data D1.

[0114] Therefore, even if metadata M1 does not indicate a script, it is possible to determine whether metadata M1 is inconsistent or not.

[0115] The service history data D1 is managed by the service provider SP. Therefore, it is difficult to tamper with the service history data D1. The metadata determination unit 274c uses the service history data D1, which is difficult to tamper with, to determine whether the metadata M1 is inconsistent. Therefore, the metadata determination unit 274c can accurately confirm whether the truthfulness of the metadata M1 is guaranteed.

[0116] If the service history data D1 is stored in the payment application AP1, it is possible to determine whether the metadata M1 is inconsistent using only the data stored in the terminal 20. Even if the service history data D1 is not stored in the payment application AP1 but is stored in the storage device 26, it is possible to determine whether the metadata M1 is inconsistent using only the data stored in the terminal 20.

[0117] The content generation status indicated by metadata M1 may be a combination of the location of terminal 20 when content C1 was generated by user U1's terminal 20 and the date and time when content C1 was generated by user U1's terminal 20. In this case, it is possible to determine whether metadata M1 is inconsistent based on the combination of the location of terminal 20 when content C1 was generated by user U1's terminal 20 and the date and time when content C1 was generated by user U1's terminal 20.

[0118] The second acquisition unit 274b may acquire service history data D1 from the service server 40 managed by the service provider SP. In this case, it is possible to determine whether the metadata M1 is inconsistent by using data that is not stored in the terminal 20.

[0119] The terminal 20 may include a contradiction determination unit 274 and a communication control unit 275. The communication control unit 275 prohibits the transmission of content C1 based on its determination that the metadata M1 is contradictory. Therefore, the transmission of content C1 with contradictory metadata M1 can be prohibited. Thus, the possibility of content C1 with contradictory metadata M1 being distributed can be reduced.

[0120] The communication control unit 275 may transmit content C1 based on its determination that the metadata M1 is consistent. In this case, content C1 with consistent metadata M1 can be distributed.

[0121] 2: Modifications The following are examples of modifications to the above-described embodiments. Two or more modifications can be arbitrarily selected from the following examples and combined as appropriate, within the bounds of mutual non-contradictory relationships.

[0122] 2-1: In the first modified embodiment, the operation to determine whether the metadata M1 is inconsistent is initiated when the input device 21 of the terminal 20 receives an imaging instruction while the determination application AP2 is active.

[0123] However, the operation to determine whether the metadata M1 is inconsistent does not necessarily have to be initiated when the input device 21 of the terminal 20 receives an imaging instruction while the determination application AP2 is active.

[0124] For example, the operation to determine whether metadata M1 is inconsistent may be initiated when the input device 21 of terminal 20 receives a content selection instruction while the determination application AP2 is active. The content selection instruction is an instruction to select content to be sent to the content distribution server 10.

[0125] Figure 10 is a diagram illustrating the operation of terminal 20 in the first modified example. The operation shown in Figure 10 is initiated when the input device 21 of terminal 20 receives a content selection instruction while the judgment application AP2 is active. Of the multiple steps shown in Figure 10, steps that perform the same processing as the steps shown in Figure 9 are denoted by the same reference numerals as those used for the steps shown in Figure 9. For the sake of simplicity, only the steps in Figure 10 that differ from those shown in Figure 9 will be described. In the following, content C1 with metadata M1 is stored in the storage device 26 of terminal 20. Furthermore, it is assumed that the content selection instruction is an instruction to select content C1 with metadata M1 as the content to be sent to the content distribution server 10.

[0126] In step S201, the first acquisition unit 274a selects content C1 accompanied by metadata M1 based on the content selection instruction. Subsequently, step S103 described above is executed.

[0127] In the operation shown in Figure 10, a determination is made as soon as a content selection instruction is received to determine whether the metadata M1 is inconsistent. Therefore, the already generated content C1 can be selected as the content to be sent to the content distribution server 10. Furthermore, even if the metadata M1 is tampered with during the period from when the metadata M1 is generated until when the content selection instruction is received, it can still be determined that the metadata M1 is inconsistent. Also, even if the terminal 20 is operated to count an incorrect date and time before the content C1 is generated, it can still be determined that the metadata M1 is inconsistent.

[0128] According to the first modified example, similar to the embodiment, it is possible to determine whether metadata M1 is inconsistent even if metadata M1 does not indicate a script. Furthermore, the metadata determination unit 274c uses service history data D1, which is difficult to tamper with, to determine whether metadata M1 is inconsistent. Therefore, the metadata determination unit 274c can accurately confirm whether the truthfulness of metadata M1 is guaranteed.

[0129] 2-2: Second Modification In the first modification, there is a possibility that content C1 may be tampered with during the period from when content C1 is generated until the start of the operation shown in Figure 10. The second modification includes the operation of the first modification and an operation to determine whether or not content C1 has been tampered with. In the second modification, terminal 20a is used instead of terminal 20.

[0130] Figure 11 shows an example of terminal 20a. Terminal 20a differs from terminal 20 in three main ways. First, judgment application AP2a is used instead of judgment application AP2. Second, communication control unit 275a is used instead of communication control unit 275. Third, content determination unit 276 is included. The following will explain terminal 20a, focusing on the differences from terminal 20.

[0131] The judgment application AP2a is an application program that defines the operation to determine whether metadata M1 is inconsistent or not. The judgment application AP2a further defines the operation to determine whether content C1 is inconsistent or not. The judgment application AP2a further defines the operation to determine whether to send content C1, along with metadata M1, to the content distribution server 10. The judgment application AP2a includes multiple instructions.

[0132] The processing unit 27 reads the judgment application AP2a from the storage device 26. By executing the judgment application AP2a, the processing unit 27 functions as a contradiction determination unit 274, a content determination unit 276, and a communication control unit 275a. The content determination unit 276 and the communication control unit 275a may each be configured by circuits such as a DSP, ASIC, or FPGA.

[0133] The content determination unit 276 determines whether or not the content C1 is contradictory.

[0134] For example, the content determination unit 276 generates a hash value for content C1 in response to the generation of content C1. The content determination unit 276 adds the hash value of content C1 to metadata M1.

[0135] The content determination unit 276 selects content C1 accompanied by metadata M1 based on the content selection instruction. The content determination unit 276 generates a hash value for the content C1 selected based on the content selection instruction.

[0136] If the hash value of the generated content C1 is different from the hash value of the content C1 added to the metadata M1, the content determination unit 276 determines that the content C1 is inconsistent.

[0137] If the hash value of the generated content C1 matches the hash value of the content C1 added to the metadata M1, the content determination unit 276 determines that the content C1 is not contradictory.

[0138] Furthermore, the method for determining whether content C1 is contradictory is not limited to the method described above and can be changed as appropriate.

[0139] The communication control unit 275 transmits content C1 based on the determination that metadata M1 is not inconsistent and the determination that content C1 is not inconsistent.

[0140] The communication control unit 275 prohibits the transmission of content C1 based on its determination that metadata M1 is inconsistent.

[0141] The communication control unit 275 prohibits the transmission of content C1 based on its determination that content C1 is inconsistent.

[0142] Figure 12 is a diagram illustrating the operation of terminal 20a. Among the multiple steps shown in Figure 12, steps that perform the same processing as the steps shown in Figure 10 are denoted by the same reference numerals as those used for the steps shown in Figure 10. For the sake of simplicity, we will describe the steps in Figure 12 that differ from the steps shown in Figure 10.

[0143] If the metadata determination unit 274c determines in step S105 that metadata M1 is inconsistent, then in step S301 the content determination unit 276 determines whether or not content C1 is inconsistent.

[0144] If the content determination unit 276 determines in step S301 that content C1 is inconsistent, then step S106 is executed.

[0145] If the content determination unit 276 determines in step S301 that the content C1 is not contradictory, then step S107 is executed.

[0146] Steps S105 and S301 may be interchanged.

[0147] According to the second modification, in addition to the effects achieved by the first modification, it is possible to determine whether or not content C1 has been tampered with. Furthermore, the possibility of tampered content C1 being distributed can be reduced.

[0148] 2-3: In the third modified embodiment, the first modified embodiment, or the second modified embodiment, the content generation status indicated by metadata M1 is not limited to a combination of the location of terminal 20 when content C1 was generated by user U1's terminal 20 and the date and time when content C1 was generated by user U1's terminal 20.

[0149] For example, if the service provider server 40 provides camera operation data D1a indicating the date and time E1a of the camera 22's operation, the content generation status indicated by metadata M1 may be the date and time when content C1 was generated by user U1's terminal 20. The date and time when content C1 was generated by user U1's terminal 20 is indicated by the date and time data G2 of metadata M1.

[0150] Figure 13 shows an example of camera operation data D1a. The date and time E1a of the camera 22 operation indicated by the camera operation data D1a is based, for example, on a date and time counted by the service provision server 40.

[0151] Camera operation data D1a is another example of behavioral data showing the history of user U1's actions using terminal 20. Camera operation data D1a is managed by service provider SP. Camera operation data D1a is stored on service provider server 40. Camera operation data D1a indicates multiple operation records Ra. Each of the multiple operation records Ra is generated each time camera 22 performs imaging. Each of the multiple operation records Ra indicates the date and time E1a of the camera 22's operation.

[0152] In the third modification, the second acquisition unit 274b acquires camera operation data D1a. The metadata determination unit 274c determines whether the plurality of operation records Ra indicated by the camera operation data D1a include a corresponding operation record that shows the same date and time as the date and time data G2 of the metadata M1.

[0153] The metadata determination unit 274c determines that metadata M1 is not contradictory if multiple operation records Ra include corresponding operation records.

[0154] The metadata determination unit 274c determines that metadata M1 is inconsistent if multiple operation records Ra do not include a corresponding operation record.

[0155] Furthermore, the corresponding operation record is not limited to an operation record that shows the same date and time as the date and time indicated by the date and time data G2 of metadata M1. For example, the corresponding operation record may also be an operation record that shows a date and time where the difference from the date and time indicated by the date and time data G2 of metadata M1 is less than a threshold. The threshold is, for example, one minute. However, the threshold is not limited to one minute. For example, the threshold may be shorter or longer than one minute. In a configuration in which a threshold is used, even if the date and time counted by the date and time counter 271 of terminal 20a differs from the date and time counted by the service provision server 40, multiple operation records Ra can include the corresponding operation record.

[0156] According to the third modified example, it is possible to determine whether metadata M1 is inconsistent or not without using the location data G1 of metadata M1.

[0157] 2-4: In the fourth modified embodiment, the first modified embodiment, the second modified embodiment, or the third modified embodiment, content C1 may be transmitted to a device other than the content distribution server 10. For example, content C1 may be transmitted from terminal 20 to terminal 30.

[0158] 2-5: In the fifth modified embodiment, the first modified embodiment, the second modified embodiment, the third modified embodiment, or the fourth modified embodiment, content C1 and first data may be transmitted based on the determination that metadata M1 is not inconsistent, and content C1 and second data that is indistinguishable from the first data may be transmitted based on the determination that metadata M1 is inconsistent.

[0159] For example, the communication control unit 275 shown in Figure 5 transmits content C1 and first data to the content distribution server 10 based on the determination that metadata M1 is not contradictory. The first data is, for example, metadata M1. The first data is not limited to metadata M1. For example, the first data may include metadata M1 and first determination data indicating the determination that metadata M1 is not contradictory. The first determination data may also be data indicating a symbol that represents that metadata M1 is not contradictory.

[0160] The communication control unit 275 transmits content C1 and second data to the content distribution server 10 based on its determination that metadata M1 is inconsistent. The second data includes metadata M1 and second determination data indicating that metadata M1 is inconsistent. If the first data includes metadata M1 and first determination data, and the second determination data is different from the first determination data, the second determination data does not need to indicate that metadata M1 is inconsistent. The second determination data may also be data indicating a symbol that metadata M1 is inconsistent.

[0161] According to the fifth modification, the content distribution server 10 can identify content C1 with inconsistent metadata M1 based on the second data. Therefore, the content distribution server 10 can, for example, prohibit the distribution of content C1 with inconsistent metadata M1. Alternatively, when providing content C1 with inconsistent metadata M1, the content distribution server 10 can also provide data indicating that content C1 may have been tampered with.

[0162] 3. Other (1) Each function illustrated in Figure 3, Figure 5, or Figure 11 can be implemented by any combination of hardware and software. The method of implementing each function is not particularly limited. Each function may be implemented using one physically or logically coupled device, or it may be implemented using a device configured by directly or indirectly connecting two or more physically or logically separated devices (for example, using wired, wireless, etc.). Each function may be implemented by combining the above one device or the above multiple devices with software.

[0163] (2) In this disclosure, the term “apparatus” may be replaced with other terms such as circuit, device or unit.

[0164] (3) In each of the embodiments and the first to fifth modifications, the storage device 42 and the storage device 26 may consist of at least one of the following: an optical disc such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., compact disc, digital multipurpose disc, Blu-ray® disc), a smart card, flash memory (e.g., card, stick, key drive), a floppy® disk, a magnetic strip, etc. The program may also be transmitted from a network via a telecommunications line.

[0165] (4) Each of the embodiments and the first to fifth modified examples is LTE (Long Term Evolution), LTE-A (LTA-Advanced), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (where x is, for example, an integer or decimal), FRA (Future Radio Access), NR (new Radio), New radio access (NX), Future generation radio access (FX), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20 may apply to at least one system utilizing UWB (Ultra-WideBand), Bluetooth®, or other appropriate systems, and to next-generation systems extended, modified, created, or defined based thereon. Alternatively, multiple systems may be applied in combination (e.g., a combination of at least one of LTE and LTE-A with 5G).

[0166] (5) The processing procedures, sequences, or flowcharts illustrated in each of the embodiments and the first to fifth modifications may be in any order, as long as they do not contradict each other. For example, the methods described in this disclosure present various step elements in an illustrative order and are not limited to the specific order presented.

[0167] (6) In each of the embodiments and the first to fifth modifications, the input and output information may be stored in a specific location (e.g., memory) or managed using a management table. The input and output information may be overwritten, updated, or appended to. The output information may be deleted. The input information may be transmitted to other devices.

[0168] (7) In each of the embodiments and the first to fifth modifications, the determination may be based on a value represented by one bit (0 or 1), on a Boolean value (true or false), or on a numerical comparison (for example, a comparison with a predetermined value).

[0169] (8) The programs illustrated in each of the embodiments and the first to fifth modifications should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, or functions, whether they are called software, firmware, middleware, microcode, or hardware description languages ​​or by other names. Furthermore, software, or instructions, etc., may be transmitted or received via a transmission medium. For example, if software is transmitted from a website, server, or other remote source using at least one of wired technology (such as coaxial cable, fiber optic cable, twisted pair, and digital subscriber line (DSL)) and wireless technology (such as infrared, microwave, etc.), at least one of these wired and wireless technologies is included in the definition of a transmission medium.

[0170] (9) The information described in each of the embodiments and the first to fifth modifications may be represented using any of the following different technologies. For example, the data and information that may be referred to throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields, magnetic particles, optical fields, photons, or any combination thereof. Notwithstanding the terms described herein and the terms necessary for understanding this disclosure, terms may be replaced with terms having the same or similar meanings.

[0171] (10) In each of the embodiments and the first to fifth modifications, the terms “system” and “network” are used interchangeably.

[0172] (11) In each of the embodiments and the first to fifth modifications, each of terminals 20 and 20a is, for example, a mobile station. A mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or several other appropriate terms.

[0173] (12) A mobile station may also be called a transmitting device, receiving device, or communication device. A mobile station may also be a device mounted on a mobile body, or the mobile body itself. A mobile body means a movable object. The speed of movement of a mobile body is arbitrary. A mobile body can be stopped. A mobile body includes, but is not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones (registered trademark), multicopters, quadcopters, balloons, and things mounted on them. A mobile body may be a mobile body that moves autonomously based on operational commands. A mobile body may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile body (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). A mobile station also includes devices that do not necessarily move during communication operations. For example, the mobile station could be an IoT (Internet of Things) device such as a sensor.

[0174] (13) In each of the embodiments and the first to fifth modifications, the term “decision” may encompass a wide variety of actions. “Decision” may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiry (e.g., searching in a table, database or another data structure), and ascertaining. “Decision” may also include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, and accessing (e.g., accessing data in memory), and ascertaining. “Decision” may also include resolving, selecting, choosing, establishing, and comparing. In other words, "decision" can include considering that some action has been "decided." Furthermore, "decision" can be reinterpreted as "assuming," "expecting," or "considering."

[0175] (14) In each of the embodiments and the first to fifth modifications, the term “connected,” or any variation thereof, means any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are “connected” or “coupled” to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, “connection” may be read as “access.” As used in the present disclosure, two elements may be considered to be “connected” or “coupled” to each other using at least one of one or more wires, cables, and printed electrical connections, and, in some non-limiting and non-exclusive examples, electromagnetic energy having wavelengths in the radio frequency domain, microwave domain, and optical (both visible and invisible) domain.

[0176] (15) In each of the first embodiment and the first to fifth modifications, the phrase "based on" does not mean "based solely on" unless otherwise specified. In other words, the phrase "based on" means both "based solely on" and "based at least on".

[0177] (16) Any reference to elements using the designations “first” and “second” as used in this disclosure does not limit the quantity or order of those elements in general. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Accordingly, references to the first and second elements do not imply that only two elements may be adopted or that the first element must precede the second element in any way.

[0178] (17) Where “include,” “including,” and variations thereof are used in each of the embodiments and the first to fifth modifications in this disclosure or in the claims, these terms are intended to be inclusive, as is the term “comprising.” Furthermore, where the term “or” is used in this disclosure or in the claims, it is intended not to be an exclusive OR.

[0179] (18) Where articles are added in the translation, for example, a, an, and the in English, the disclosure may include the fact that the noun following these articles is plural.

[0180] (19) The information, parameters, etc. described in this disclosure may be expressed using absolute values, relative values ​​from a given value, or other corresponding information.

[0181] (20) In this disclosure, the term “A and B are different” may mean “A and B are different from each other.” The term may also mean “A and B are each different from C.” Terms such as “separate” and “combined” may be interpreted in the same way as “different.”

[0182] (21) Each aspect / embodiment described herein may be used individually, in combination, or switched between as needed during implementation. Furthermore, notification of certain information (e.g., notification that "it is X") is not limited to explicit notification, but may also be implicit (e.g., by not providing such notification).

[0183] (22) It will be obvious to those skilled in the art that the present invention is not limited to the embodiments described herein. The present invention can be implemented in modified and altered forms without departing from the spirit and scope of the invention as defined by the claims. Accordingly, the descriptions herein are for illustrative purposes only and are not intended to be restrictive in any way to the present invention. Furthermore, multiple embodiments selected from those illustrated herein may be combined.

[0184] 4. Aspects that can be understood from the above-described forms or modifications The following aspects can be understood from at least one of the above-described forms or modifications.

[0185] 4-1: First Embodiment The inconsistency determination device according to the first embodiment includes a first acquisition unit, a second acquisition unit, and a metadata determination unit. The first acquisition unit acquires metadata from among the data associated with the content, which indicates at least the circumstances under which the content was generated by the user's terminal. The second acquisition unit acquires behavioral data from among the data managed by the service provider, which indicates the history of the user's actions using the terminal. The metadata determination unit determines whether the metadata is inconsistent based on the relationship between the circumstances indicated by the metadata and the history of the user's actions indicated by the behavioral data.

[0186] According to this embodiment, it is possible to determine whether metadata is inconsistent even if the metadata does not indicate a script.

[0187] Behavioral data is managed by the service provider. Therefore, it is difficult to tamper with behavioral data. The metadata determination unit uses behavioral data that is difficult to tamper with to determine whether the metadata is inconsistent. Therefore, the metadata determination unit can accurately verify whether the truthfulness of the metadata is guaranteed.

[0188] 4-2: Second Embodiment In the example of the first embodiment (second embodiment), the situation is a combination of the location of the user's terminal when the content was generated by the user's terminal and the date and time when the content was generated by the user's terminal. According to this embodiment, it is possible to determine whether the metadata is inconsistent based on the combination of the location of the terminal when the content was generated by the user's terminal and the date and time when the content was generated by the user's terminal.

[0189] 4-3: Third Embodiment In an example of the first or second embodiment (third embodiment), the second acquisition unit acquires the behavioral data from a device managed by the service provider. According to this embodiment, it is possible to determine whether the metadata is inconsistent by using data not stored in the inconsistency determination device.

[0190] 4-4: The fourth embodiment of the communication control device includes a contradiction determination device according to any of the first to third embodiments, and a communication control unit that prohibits the transmission of the content based on the determination that the metadata is contradictory. According to this embodiment, the transmission of content with contradictory metadata can be prohibited. Therefore, the possibility of content with contradictory metadata being distributed can be reduced.

[0191] 4-5: Fifth Embodiment In the example of the fourth embodiment (fifth embodiment), the communication control unit transmits the content based on the determination that the metadata is not contradictory. According to this embodiment, content with consistent metadata can be distributed.

[0192] 4-6: Sixth Embodiment In the example of the fourth embodiment (sixth embodiment), the communication control device further includes a content determination unit that determines whether the content is inconsistent, and the communication control unit transmits the content based on the determination that the metadata is not inconsistent and the determination that the content is not inconsistent. According to this embodiment, the possibility of tampered content being distributed can be reduced.

[0193] 4-7: The seventh embodiment of the communication control device includes a contradiction determination device according to any of the first to third embodiments, and a communication control unit that transmits the content and first data based on a determination that the metadata is not contradictory, and transmits the content and second data that is distinguishable from the first data based on a determination that the metadata is contradictory. According to this embodiment, content with contradictory metadata can be identified based on the second data.

[0194] 4-8: The eighth aspect of the contradiction determination method includes: obtaining metadata from data associated with the content that at least indicates the circumstances under which the content was generated by the user's terminal; obtaining behavioral data from data managed by the service provider that indicates the history of the user's actions using the terminal; and determining whether the metadata is contradictory based on the relationship between the circumstances indicated by the metadata and the history of the user's actions indicated by the behavioral data. This aspect can achieve the same effects as the first aspect.

[0195] CS...Content Management System, SP...Service Provider, U1...User, 10...Content Distribution Server, 20...Terminal, 20a...Terminal, 21...Input Device, 22...Camera, 23...Display Device, 24...GPS Module, 25...Communication Device, 26...Storage Device, 27...Processing Device, 271...Date and Time Counter, 272...Metadata Generation Unit, 273...Settlement Control Unit, 274...Inconsistency Determination Unit, 274a...First Acquisition Unit, 274b...Second Acquisition Unit, 274c...Metadata Determination Unit, 275...Communication Control Unit, 275a...Communication Control Unit, 276...Content Determination Unit, 30...Terminal, 40...Service Provider Server, 41...Communication Device, 42...Storage Device, 43...Processing Device, 431...Operation Control Unit, 44...Bus.

Claims

1. A contradiction determination device comprising: a first acquisition unit that acquires metadata from data associated with content that at least indicates the circumstances under which the content was generated by the user's terminal; a second acquisition unit that acquires behavioral data from data managed by the service provider that indicates the history of the user's actions using the terminal; and a metadata determination unit that determines whether the metadata is contradictory based on the relationship between the circumstances indicated by the metadata and the history of the user's actions indicated by the behavioral data.

2. The inconsistency determination device according to claim 1, wherein the situation is a combination of the location of the terminal when the content was generated by the user's terminal and the date and time when the content was generated by the user's terminal.

3. The contradiction determination device according to claim 1, wherein the second acquisition unit acquires the behavioral data from a device managed by the service provider.

4. A communication control device comprising: a contradiction determination device according to claim 1; and a communication control unit that prohibits the transmission of the content based on the determination that the metadata is contradictory.

5. The communication control device according to claim 4, wherein the communication control unit transmits the content based on the determination that the metadata is not inconsistent.

6. The communication control device according to claim 4, further comprising a content determination unit that determines whether the content is inconsistent, wherein the communication control unit transmits the content based on the determination that the metadata is not inconsistent and the determination that the content is not inconsistent.

7. A communication control device comprising: a contradiction determination device according to claim 1; a communication control unit that transmits the content and first data based on a determination that the metadata is not contradictory, and transmits the content and second data distinguishable from the first data based on a determination that the metadata is contradictory.

8. A method for determining inconsistencies, comprising: obtaining metadata from data associated with the content that at least indicates the circumstances under which the content was generated by the user's terminal; obtaining behavioral data from data managed by the service provider that indicates the history of the user's actions using the terminal; and determining whether the metadata is inconsistent based on the relationship between the circumstances indicated by the metadata and the history of the user's actions indicated by the behavioral data.

Images