System, program and information processing device

Abstract

To provide a system, a program and an information processing device that improve usability of a user.SOLUTION: In a system 1, a control unit 10 of an information processing device 2 includes: an execution unit 106 which executes at least one of a first application and a second application different from the first application; a first determination unit 104a which determines whether a user agrees with common rules as use rules common to the first application and the second application; and a request control unit 110 which controls, based upon a determination result of the first determination unit, whether the user is requested to agree with the common rules when the execution unit executes the at least one of the first application and the second application.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present disclosure relates to a system, a program, and an information processing device. [Background technology]

[0002] Conventionally, there have been known techniques for requesting consent to terms of use before playing a game. For example, Patent Document 1 describes a technique for displaying a message indicating that consent to the content terms of use is required to start a game. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2017-140167 A Summary of the Invention [Problem to be solved by the invention]

[0004] However, there is room for improvement in terms of improving user convenience.

[0005] Therefore, an object of the present disclosure is to improve user convenience. [Means for solving the problem]

[0006] A first aspect is a system comprising: an execution unit that executes at least one of a first application and a second application different from the first application; a first judgment unit that judges whether user consent to common terms has been obtained, the common terms being terms of use common to the first application and the second application; and a request control unit that controls whether or not to request consent to the common terms from the user when the execution unit executes at least one of the first application and the second application based on a judgment result by the first judgment unit.

[0007] In the first aspect, when a user specifies a first application and agrees to the common terms, the request control unit may limit a request for agreement to the common terms when the execution unit executes a second application.

[0008] The system relating to the first aspect may further include a memory unit that associates and stores common identification information, which is identification information common to the first application and the second application, with each of a plurality of users, and the common identification information is associated with an indicator indicating whether or not the user has agreed to the common terms, and the determination unit may determine whether or not the user has agreed to the common terms by referring to the indicator.

[0009] In a first aspect, when a user agrees to a common agreement in association with common identification information without specifying a first application and a second application, the request control unit may be limited in requesting agreement to the common agreement when the execution unit executes the second application.

[0010] In a first aspect, the execution unit may be restricted from executing the second application during a first period and may be able to execute the second application during a second period, and if the user has agreed to the common terms in association with the common identification information during at least the first period, the request control unit may be restricted from requesting agreement to the common terms when the execution unit executes the second application during the second period.

[0011] The system relating to the first aspect may further include a second judgment unit that judges whether or not user consent to the individual terms has been obtained, where the individual terms are terms of use for a second application that differ at least in part from the common terms, and a display unit that displays the common terms and the individual terms in an identifiable manner when the second application is specified in association with common identification information, and the request control unit may further control whether or not to request consent to the individual terms from the user when the execution unit executes the second application based on the judgment result by the second judgment unit.

[0012] In a first aspect, the execution unit may be restricted from executing the second application during a first period and may be able to execute the second application during a second period, and the request control unit may be restricted from requesting consent to the individual terms when the execution unit executes the second application during the second period if the request control unit has agreed to the individual terms in association with the common identification information during at least the first period.

[0013] In a first aspect, requesting user consent to the common terms may include displaying the common terms to the user, and if the first determination unit determines that user consent has not been obtained, the request control unit may display the common terms when the execution unit executes at least one of the first application and the second application, and if the first determination unit determines that user consent has been obtained, the request control unit may restrict the display of the common terms when the execution unit executes at least one of the first application and the second application.

[0014] In a first aspect, the device may further include a reception unit that receives setting input from a user to display the common terms, and when the reception unit receives the setting input, the request control unit may display the common terms when the execution unit executes at least one of the first application and the second application, regardless of the determination result by the first determination unit.

[0015] In a first aspect, if the common terms are changed between a first point in time at which a user agrees to the common terms and a second point in time after the first point in time at which the execution unit executes the first application or the second application, the request control unit may display the common terms when the execution unit executes at least one of the first application and the second application, regardless of the determination result by the first determination unit.

[0016] A second aspect is a program that causes a computer to function as an execution means that executes at least one of a first application and a second application different from the first application, a first determination unit that determines whether user consent to common terms has been obtained, the common terms being terms of use common to the first application and the second application, and a request control means that controls whether or not to request consent to the common terms from the user when the execution means executes at least one of the first application and the second application based on a determination result by the first determination unit.

[0017] A third aspect is an information processing device comprising: an execution unit that executes at least one of a first application and a second application different from the first application; a first judgment unit that judges whether user consent to common terms has been obtained, the common terms being terms of use common to the first application and the second application; and a request control unit that controls whether or not to request consent to the common terms from the user when the execution unit executes at least one of the first application and the second application based on a judgment result by the first judgment unit. Effect of the Invention

[0018] According to the present disclosure, it is possible to improve user convenience. [Brief description of the drawings]

[0019] [Figure 1]FIG. 1 is a functional block diagram of the system 1. [Diagram 2] FIG. 4 is a diagram showing an example of information stored in a storage unit 14 according to the first embodiment. [Diagram 3] 4 is a flowchart for explaining the operation of the system 1 according to the first embodiment. [Figure 4] 3 is a diagram for explaining an example of a display screen of the terminal device 3 according to the first embodiment. FIG. [Diagram 5] 3 is a diagram for explaining an example of a display screen of the terminal device 3 according to the first embodiment. FIG. [Figure 6] FIG. 4 is a diagram showing an example of information stored in a storage unit 14 according to the first embodiment. [Figure 7] 3 is a diagram for explaining an example of a display screen of the terminal device 3 according to the first embodiment. FIG. [Figure 8] FIG. 4 is a diagram showing an example of information stored in a storage unit 14 according to the first embodiment. [Figure 9] 3 is a diagram for explaining an example of a display screen of the terminal device 3 according to the first embodiment. FIG. [Figure 10] 3 is a diagram for explaining an example of a display screen of the terminal device 3 according to the first embodiment. FIG. [Figure 11] 10 is a flowchart for explaining the operation of the system 1 according to the second embodiment. [Figure 12] FIG. 11 is a diagram for explaining an example of a display screen of the terminal device 3 according to the second embodiment. [Figure 13] FIG. 11 is a diagram for explaining an example of a display screen of the terminal device 3 according to the second embodiment. [Figure 14] FIG. 11 is a diagram for explaining an example of a display screen of the terminal device 3 according to the second embodiment. [Figure 15] FIG. 11 is a diagram showing an example of information stored in a storage unit 14 according to the second embodiment. [Figure 16] FIG. 11 is a diagram for explaining an example of a display screen of the terminal device 3 according to the second embodiment. [Figure 17] FIG. 11 is a diagram for explaining an example of a display screen of the terminal device 3 according to the second embodiment. [Figure 18]FIG. 2 is a hardware configuration diagram of a terminal device 3. [Figure 19] 13 is a diagram for explaining an example of a display screen of a terminal device 3 according to a modified example. FIG. [Figure 20] 13 is a diagram for explaining an example of a display screen of a terminal device 3 according to a modified example. FIG. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0020] A preferred embodiment of the present disclosure (hereinafter, referred to as the present embodiment) will be described with reference to the accompanying drawings. In each drawing, the same reference numerals denote the same or similar configurations.

[0021] In this disclosure, the terms "part", "means", "apparatus", and "system" do not simply mean physical means, but also include cases where the functions of the "part", "means", "apparatus", and "system" are realized by software. Furthermore, the functions of one "part", "means", "apparatus", or "system" may be realized by two or more physical means, devices, or software, and the functions of two or more "parts", "means", "apparatus", or "system" may be realized by one physical means, device, or software.

[0022] <1. Overview of System 1> The system 1 according to the present disclosure improves the convenience for a user to consent to the terms of use of an application (hereinafter, referred to as an "app").

[0023] Generally, when a user starts using an app, the user needs to agree to the terms of use of the app. However, even if at least a part of the terms of use is common between multiple apps, the user needs to individually check the entire terms of use when starting to use each app. In addition, even if the user is required to agree to the terms of use when attempting to start using the app, the user may be highly motivated to use the app at that time and may not read the terms of use thoroughly. One example of the effect of the system 1 according to the present disclosure is to solve these problems.

[0024] The application according to the present disclosure is software having functions corresponding to a specific business or purpose, and requiring consent to terms of use in order to be executed. Examples of the application according to the present disclosure include a game application, a text editor application, an illustration creation application, a music application, a video application, a map application, a payment application, a web browser application, and a messaging application.

[0025] In addition, in the system 1 of the present disclosure, the user can execute a first app and a second app different from the first app. Hereinafter, when there is no particular distinction between the first app and the second app, they are collectively referred to as "apps." In other words, below, "app" can be read as "first app" or "second app" to the extent that no contradiction occurs.

[0026] In addition, the first application and the second application in the present disclosure may be executed independently of each other. For example, the first application and the second application may be installed as separate software in at least one of the terminal device 3 and the information processing device 2.

[0027] <2. Functional configuration of System 1> The functional configuration of the system 1 will be described with reference to Fig. 1. The system 1 includes an information processing device 2, a cross-application management terminal device 3a, an application execution terminal device 3b, and a communication network 4. Hereinafter, when there is no particular distinction between the cross-application management terminal device 3a and the application execution terminal device 3b, they will be collectively referred to as the "terminal device 3."

[0028] [Information processing device 2] The information processing device 2 is a server device that provides various services to a terminal device 3 that is a client device.

[0029] In one embodiment, the information processing device 2 communicates with the application executing terminal device 3b, executes the application, and transmits the result to the application executing terminal device 3b. That is, it can be said that the information processing device 2 has a function as a game server device that provides game-related services to the application executing terminal device 3b.

[0030] In one embodiment, the information processing device 2 communicates with the cross-application management terminal device 3a and manages the state of user consent to the terms of use of each of a plurality of applications. That is, it can be said that the information processing device 2 has a function as a management server that manages the state of user consent to the terms of use.

[0031] The information processing device 2 includes a control unit 10, a storage unit 14, a network interface unit 18, and a bus 16. The control unit 10, the storage unit 14, and the network interface unit 18 are electrically connected via the bus 16.

[0032] (Storage unit 14) The storage unit 14 stores various programs executed by the control unit 10, which will be described later, as well as a consent information DB and a corresponding information DB.

[0033] -Consent information DB- The consent information DB stores information indicating whether or not each of a plurality of users has consented to the terms of use of each of a plurality of applications.

[0034] In one embodiment, the terms of use of an app are common terms shared with other apps. For example, if the terms of use of a first app and the terms of use of a second app are common terms, if a user agrees to the common terms when starting to use the first app, the user can start to use the second app without being asked to agree again. The common terms are, for example, a privacy policy.

[0035] The terms of use for the first app and the terms of use for the second app being common terms does not necessarily mean that the wording of the terms of use for the first app and the terms of use for the second app are the same. Specifically, the terms of use for the first app and the terms of use for the second app being common terms also mean that if a user agrees to the terms of use for the first app, the user can be deemed to have agreed to the terms of use for the second app. For example, if the terms of use for the first app include Articles 1 to 10 and the terms of use for the second app include Articles 1 to 5 (however, they have the same meaning as Articles 1 to 5 of the terms of use for the first app), then if a user agrees to the terms of use for the first app, the user can be deemed to have agreed to the terms of use for the second app.

[0036] In another embodiment, the terms of use of an app include common terms, which are parts that are common to the terms of use of other apps, and individual terms, which are parts that differ from the terms of use of other apps. For example, if the terms of use of a first app include the individual terms of the first app (hereinafter referred to as the "first individual terms") and the common terms, and the terms of use of a second app include the individual terms of the second app (hereinafter referred to as the "second individual terms") and the common terms, then if a user agrees to the first individual terms and the common terms when starting to use the first app, the user can start to use the second app by agreeing to the second individual terms (i.e., without being asked to agree again to the common terms). The individual terms are, for example, an EULA (End-User License Agreement) or the like.

[0037] The consent information DB stores a first individual agreement consent table t1 indicating whether or not each of a plurality of users has agreed to the first individual agreement, a second individual agreement consent table t2 indicating whether or not each of the users has agreed to the second individual agreement, and a common agreement consent table t3 indicating whether or not each of the users has agreed to the common agreement for the first application and the second application.

[0038] In one embodiment, the common agreement agreement table t3 associates a user's common identification information (hereinafter referred to as a "common ID") with an index indicating whether the user has agreed to the common agreement. The common ID is identification information commonly associated with a given user by the first application and the second application.

[0039] In addition, in one embodiment, the first individual terms and conditions agreement table t1 associates the user's identification information in the first application (hereinafter referred to as the "first user ID") with an indicator indicating whether the user has agreed to the first individual terms and conditions.

[0040] In addition, in one embodiment, the second individual terms and conditions agreement table t2 associates the user's identification information in the second application (hereinafter referred to as the "second user ID") with an indicator indicating whether the user has agreed to the second individual terms and conditions.

[0041] - Compatible Information DB - The correspondence information DB stores a first correspondence table t5 indicating the correspondence between the first user ID and the common ID, and a second correspondence table t6 indicating the correspondence between the first user ID and the common ID. In the present disclosure, the association of the common ID with the first user ID is referred to as "common ID federation in the first application." Also, the association of the common ID with the second user ID is referred to as "common ID federation in the second application."

[0042] The information processing device 2 can appropriately combine and use at least a portion of the first individual agreement table t1, the second individual agreement table t2, the common agreement table t3, the first correspondence relationship table t5, and the second correspondence relationship table t6.

[0043] In the following, unless there is a particular distinction between the Master Terms, the First Individual Terms, and the Second Individual Terms, they will be collectively referred to as the "Terms of Use." In other words, in the following, to the extent that no contradiction arises, the "Terms of Use" can be read as the "Master Terms," ​​the "First Individual Terms," ​​or the "Second Individual Terms."

[0044] In addition, hereinafter, when there is no particular distinction between the common ID, the first user ID, and the second user ID, they are collectively referred to as "identification information." In other words, hereinafter, "identification information" can be read as "common ID," "first user ID," or "second user ID" to the extent that no contradiction occurs.

[0045] (Control unit 10) The control unit 10 executes the programs stored in the storage unit 14 to function as a reception unit 100, an association unit 102, a determination unit 104, an execution unit 106, a display unit 108, and a request control unit 110.

[0046] --Reception Section 100-- The reception unit 100 receives consent of the user to the terms of use. In the present disclosure, receiving consent of the user to the terms of use includes receiving information indicating that the user has consented to the terms of use from the terminal device 3 of the user.

[0047] In one embodiment, when a user designates a first application, the reception unit 100 accepts consent to at least one of the first individual terms and the common terms. In another embodiment, when a user designates a second application, the reception unit 100 accepts consent to at least one of the second individual terms and the common terms. When a user does not designate either the first application or the second application, the reception unit 100 accepts consent to at least the common terms.

[0048] In one embodiment, the user's designation of an app includes displaying a screen on which the user can select whether or not to agree to the terms of use of the app. For example, if a title screen of a certain app requires consent to the terms of use, the user's designation of an app includes displaying the title screen of the certain app.

[0049] In one embodiment, the user's designation of an application includes displaying a screen on which the user can select whether or not to agree to the individual terms of the application, and cannot select whether or not to agree to the individual terms of other applications. Hereinafter, an example of a screen on which the user can select whether or not to agree to at least one of the first individual terms and the common terms, and cannot select whether or not to agree to the second individual terms, is referred to as a "first application management screen." In addition, an example of a screen on which the user can select whether or not to agree to at least one of the second individual terms and the common terms, and cannot select whether or not to agree to the first individual terms is referred to as a "second application management screen." That is, in the first application management screen, the user can select whether or not to agree to at least one of the first individual terms and the common terms, but cannot select whether or not to agree to the second individual terms. Similarly, in the second application management screen, the user can select whether or not to agree to at least one of the second individual terms and the common terms, but cannot select whether or not to agree to the first individual terms.

[0050] Furthermore, in one embodiment, when the user does not specify an app, it includes displaying a screen on which the user can select whether or not to agree to both the first individual terms and the second individual terms. When the user does not specify an app, it also includes displaying a screen on which the user cannot select whether or not to agree to both the first individual terms and the second individual terms. Hereinafter, the screen that is displayed when the user does not specify an app is referred to as a "cross-app management screen."

[0051] In one embodiment, the reception unit 100 receives consent to the terms of use in association with the common ID. Receiving consent to the terms of use in association with the common ID includes causing the association unit 102, described later, to associate an indicator indicating that consent has been accepted with the common ID in response to accepting consent. For example, when a user with a common ID of "001" agrees to the common terms in association with the common ID, "Done", which is an indicator indicating that consent to the common terms has been accepted, is associated with the common ID of "001".

[0052] In one embodiment, the reception unit 100 receives an input of a setting for displaying the terms of use from a user. For example, the reception unit 100 receives an input of a setting on a first application management screen as to whether or not the terms of use are to be displayed when an application is executed. Note that in the present disclosure, receiving an input of a setting from a user includes receiving information about the setting from the terminal device 3 of the user.

[0053] --Association section 102-- The associating unit 102 updates the consent information DB to associate an indicator indicating whether or not the user has agreed to the terms of use with the user's identification information. Specifically, the associating unit 102 associates an indicator indicating whether or not the user has agreed to the first individual terms with the first user ID. The associating unit 102 also indexes information indicating whether or not the user has agreed to the second individual terms with the second user ID. The associating unit 102 also associates an indicator indicating whether or not the user has agreed to the common terms with the common ID.

[0054] In one embodiment, the associating unit 102 associates an indicator with the user's identification information in response to the consent accepted by the accepting unit 100. For example, when the accepting unit 100 accepts the user's consent to the common terms, the associating unit 102 associates an indicator (for example, "Completed") indicating that the user has agreed to the common terms with the common ID.

[0055] -Judgment section 104- The determination unit 104 determines whether or not the user has consented to the terms of use. The determination unit 104 can also be said to include a first determination unit 104a that determines whether or not the user has consented to the common terms, and a second determination unit 104b that determines whether or not the user has consented to the individual terms (i.e., at least one of the first individual terms and the second individual terms).

[0056] In one embodiment, the determination unit 104 refers to the consent information DB to determine whether or not the user consent to the terms of use has been obtained. Specifically, the determination unit 104 refers to the common agreement consent table t3 to determine whether or not the user consent to the common agreement has been obtained. The determination unit 104 also refers to the first individual agreement consent table t1 to determine whether or not the user consent to the first individual agreement has been obtained. The determination unit 104 also refers to the second individual agreement consent table t2 to determine whether or not the user consent to the second individual agreement has been obtained. Specific examples of the common agreement table t3, the first individual agreement consent table t1, and the second individual agreement consent table t2 will be described later.

[0057] --Executive Division 106-- The execution unit 106 executes the application. In one embodiment, executing the application includes receiving information related to a user's operation from the application execution terminal device 3b, generating video and audio related to the application based on the information, and outputting the generated video and audio to the application execution terminal device 3b.

[0058] In one embodiment, executing an app means putting the app into a state where it can perform functions corresponding to a predetermined task or purpose. For example, if the app is a game app, executing the app includes putting the app into a state where it can play a quest (a game mode in which a user achieves a predetermined goal using game media such as characters and items owned by the user) or a gacha (a game mode in which a user pays a predetermined fee to select at least some game media from a plurality of game media). In other words, executing an app does not necessarily include displaying a title screen of the app or displaying metadata related to the app. Executing an app may also be putting the app into a state where it can perform functions that cannot be used unless the user agrees to the terms of use.

[0059] -Display section 108- The display unit 108 displays the terms of use. In one embodiment, when a specific application is designated in association with a common ID, the display unit 108 displays the common terms and the individual terms corresponding to the specific application in an identifiable manner.

[0060] In one embodiment, specifying an app in association with a common ID includes specifying the app in a state where the common ID is linked in the app.

[0061] In one embodiment, displaying the terms of use includes displaying the terms of use on the display device 710 included in the information processing device 2, as well as causing the terminal device 3 to display the terms of use.

[0062] -Request control unit 110- The request control unit 110 controls whether or not to request consent to the terms of use based on the determination result by the determination unit 104. In one embodiment, the request control unit 110 controls whether or not to request consent to the terms of use from the user when the execution unit 106 executes an app based on the determination result by the determination unit 104.

[0063] Note that "requesting the user to agree to the terms of use when the execution unit 106 executes an app" includes requesting the user to agree to the terms of use based on the user's designation of the app. In addition, "requesting the user to agree to the terms of use when the execution unit 106 executes an app" includes requesting the user to agree to the terms of use in order to satisfy the conditions for the execution unit 106 to execute (or become executable) the app.

[0064] In one embodiment, when the determination unit 104 determines that user consent to the terms of use has been obtained, the request control unit 110 is restricted from requesting the user to consent to the terms of use. In this case, the request control unit 110 typically does not request consent to the terms of use. Also, in one embodiment, when the determination unit 104 determines that user consent to the terms of use has not been obtained, the request control unit 110 requests consent to the terms of use.

[0065] In one embodiment, when a user specifies a first application and agrees to the common terms, the request control unit 110 limits the request for agreement to the common terms when the execution unit 106 executes a second application. For example, when a user agrees to the common terms when executing a first application, the request control unit 110 does not request agreement to the common terms when the user executes a second application.

[0066] Furthermore, in one embodiment, when the user agrees to the common terms in association with the common ID without specifying the first application and the second application, the request control unit 110 restricts the request for agreement to the common terms when the execution unit 106 executes at least one of the first application and the second application. For example, when the user agrees to the sharing terms on the cross-application management screen, the request control unit 110 does not request agreement to the common terms when the user executes the second application.

[0067] Furthermore, in one embodiment, the request control unit 110 requesting user consent to the terms of use includes displaying the terms of use to the user. If the determination unit 104 determines that user consent to the terms of use has not been obtained, the request control unit 110 displays the terms of use when the execution unit 106 executes the app. If the determination unit 104 determines that user consent to the terms of use has been obtained, the request control unit 110 restricts the display of the terms of use when the execution unit 106 executes the app.

[0068] Furthermore, in one embodiment, when the receiving unit 100 receives a setting input for displaying the terms of use from the user, the request control unit 110 may display the common terms when the execution unit 106 executes the application, regardless of the determination result by the determination unit 104. In other words, when the user expressly intends to display the terms of use when executing the application, the request control unit 110 displays the terms of use, regardless of whether the user has agreed to the terms of use in advance.

[0069] Furthermore, in one embodiment, if the terms of use are changed between a first point in time when the user agrees to the terms of use and a second point in time after the first point in time when the execution unit 106 executes the app, the request control unit 110 may display the common terms when the execution unit 106 executes the app, regardless of the determination result by the determination unit 104. In other words, if the terms of use are revised between the point in time when the user agrees to the terms of use and the point in time when the user actually executes the app, the request control unit 110 displays the terms of use regardless of whether the user has agreed to the terms of use in advance.

[0070] In one embodiment, the request for consent by the request control unit 110 includes setting the application so that it cannot be executed unless the user consents to the terms of use. In this case, restricting the request for consent by the request control unit 110 includes setting the application so that it can be executed without receiving an operation from the user to consent to the terms of use.

[0071] In one embodiment, the request for consent by the request control unit 110 includes setting the user to be unable to consent to the terms of use unless the terms of use are displayed. In this case, restricting the request for consent by the request control unit 110 includes setting the user to be able to consent to the terms of use without the terms of use being displayed.

[0072] (Network Interface Unit 18) The network interface unit 18 realizes communication with other devices via the communication network 4. The network interface unit 18 may realize communication based on, for example, the TCP / IP protocol.

[0073] [Terminal device 3] The terminal device 3 is a device used by a user. The terminal device 3 is, for example, an electronic device such as a game machine, a smartphone, a smart watch, a tablet terminal, or a personal computer. The terminal device 3 can access various information stored in the storage unit 14 by communicating with the information processing device 2.

[0074] The cross-application management terminal device 3a is a terminal device 3 that is used by a user to operate a cross-application management screen. The cross-application management terminal device 3a can also display a first application management screen and a second application management screen. Details will be described later.

[0075] The application execution terminal device 3b is a terminal device 3 used by a user to execute an application. Executing the application includes accepting an operation from a user, generating video and audio related to the game based on the operation accepted from the user, and outputting the generated video and audio. When the application execution terminal device 3b executes a game by communicating with the information processing device 2, the application execution terminal device 3b may transmit information related to the operation accepted from the user to the information processing device 2 and receive information related to the video and audio related to the game generated in the information processing device 2.

[0076] <3. Operation of System 1> [First embodiment] (Operation of the system 1 according to the first embodiment) An example of the operation of the system 1 according to the first embodiment will be described below with reference to Fig. 2 to Fig. 10. In the first embodiment, an example will be described in which a user agrees to the common terms on the first application management screen, and therefore there is no need to agree to the common terms again when executing the second application. Note that in the first embodiment, the first application and the second application will be described as being executable if both of them agree to the common terms.

[0077] 2 is a diagram for explaining information stored in the storage unit 14 at the initial point in time. FIG. 2(A) is a diagram showing an example of a first correspondence relationship table t5 at the initial point in time. In the first correspondence relationship table t5, a common ID of "001" is associated with a first user ID of "1001". That is, the user has already performed common ID federation in the first app at the initial point in time.

[0078] 2B is a diagram showing an example of the second correspondence table t6 at an initial point in time. In the second correspondence table t6, a common ID is not associated with the second user ID "2001". In other words, the user has not yet performed common ID federation in the second app.

[0079] 2C is a diagram showing an example of a common agreement table t3 at an initial point in time. In the common agreement table t3, a common ID "001" is associated with an index "not yet", which indicates that agreement to the common agreement has not been accepted.

[0080] 3 is a flowchart for explaining an example of the operation of the system 1. First, in response to a user's operation, the cross-application management terminal device 3a displays a cross-application management screen (S100). The cross-application management screen is an example of a screen that is displayed without the user specifying an application.

[0081] Fig. 4 is a diagram illustrating an example of a cross-application management screen displayed on the cross-application management terminal device 3a. The cross-application management screen in Fig. 4 displays a title d100, a common ID d102, an application designation area d104, and a terms of use confirmation area d110.

[0082] The title d100 indicates the title of the display screen. In this example, it says "Cross-application management."

[0083] The common ID d102 indicates the common ID of the user. In this example, "001" is displayed. In this example, it is assumed that the user can display the cross-application management screen on the cross-application management terminal device 3a by logging in to the cross-application management service using the common ID.

[0084] A first application designation button d106 and a second application designation button d108 are displayed in the application designation area d104. A user can designate a first application by pressing the first application designation button d106, and cause the display screen of the cross-application management terminal device 3a to transition to a first application management screen. A user can designate a second application by pressing the second application designation button d108, and cause the display screen of the cross-application management terminal device 3a to transition to a second application management screen.

[0085] The terms of use confirmation area d110 displays a common terms display button d112 and an agreement check box d114. The user can display the contents of the common terms on the cross-application management terminal device 3a by pressing the common terms display button d112. The user can also agree to the common terms in association with the common ID by pressing the agreement check box d114.

[0086] Returning to Fig. 3, next, the cross-application management terminal device 3a accepts designation of a first application from the user (S102). That is, the user presses the Designate First Application button d106 on the cross-application management screen in Fig. 4. In response to this, the information processing device 2 receives information indicating that the user has designated the first application from the cross-application management terminal device 3a.

[0087] Next, the cross-application management terminal device 3a displays the first application management screen (S104).

[0088] Fig. 5 is a diagram for explaining an example of a first application management screen displayed on the cross-application management terminal device 3a. The first application management screen in Fig. 5 displays a title d120, a user information display area d122, and a terms of use confirmation area d124.

[0089] The title d120 indicates the title of the display screen. In this example, it says "First application management."

[0090] In the user information display area d122, the first user ID ("1001"), the common ID ("Linked (001)"), the game record ("Win rate 56%), the billing history display button, and the friend display button are displayed. The common ID is typically displayed with reference to the first correspondence relationship table t5.

[0091] The terms of use confirmation area d124 displays a common terms display button d126 and an agreement check box d128. The user can display the contents of the common terms on the cross-application management terminal device 3a by pressing the common terms display button d126. The user can also agree to the common terms in association with the common ID by pressing the agreement check box d128.

[0092] Returning to Fig. 3, next, the cross-application management terminal device 3a accepts consent to the common agreement on the first application management screen (S105). That is, the user presses the consent checkbox d128 on the first application management screen in Fig. 5. In response to this, the information processing device 2 receives information indicating that the user has consented to the common agreement from the cross-application management terminal device 3a, and updates the common agreement table t3.

[0093] 6 is a diagram for explaining an example of information stored in the storage unit 14 when the user presses the consent checkbox d128 on the first application management screen (i.e., when the user consents to the common terms). Compared to FIG. 2, the indicator associated with the common ID "001" in the common terms consent table t3 has been updated from "Not yet" to an indicator "Completed", which indicates that consent to the common terms has been accepted.

[0094] 3, the application executing terminal device 3b then displays the title screen of the second application based on a user operation (S106). The user can display the title screen of the second application by, for example, specifying the second application on a home screen (not shown).

[0095] Fig. 7 is a diagram for explaining an example of a title screen of the second application. The title screen of the second application in Fig. 7 displays a title d140, a user ID display area d142, a common ID linkage display area d144, a terms of use confirmation area d146, a start button d152, and a message d154.

[0096] The title d140 indicates the title of the display screen. In this example, "Second App" is displayed. The user ID display area d142 displays the user's second user ID ("2001").

[0097] The common ID federation display area d144 indicates whether the user has performed common ID federation in the second app. In this example, the user has not yet performed common ID federation in the second app, so the federation button d145 displays "Not yet federated." The user can perform common ID federation in the second app by pressing the federation button d145.

[0098] The terms of use confirmation area d146 displays a common terms display button d148 and an agreement check box d150. The user can display the contents of the common terms on the application execution terminal device 3b by pressing the common terms display button d148. The user can also agree to the common terms in association with the common ID by pressing the agreement check box d150.

[0099] Although the user has agreed to the common terms using the cross-application management terminal device 3a (see the agreement checkbox d128 in FIG. 5), this is not reflected in the application execution terminal device 3b (see the agreement checkbox d150 in FIG. 7). This is because the user has not yet performed common ID federation in the second application.

[0100] The start button d152 is a button that allows the user to execute the second application by pressing it. Note that in Fig. 7, since it is assumed that the user has not yet agreed to the common terms, the second application cannot be executed even if the start button d152 is pressed. The message d154 is a message notifying the user of this fact.

[0101] Returning to FIG. 3, next, the application executing terminal device 3b accepts common ID federation for the second application by the user (S108). That is, the user presses the federation button d145 on the title screen of the second application in FIG. 7. For example, the user can perform common ID federation in the second application by inputting a common ID and a password corresponding to the common ID into the application executing terminal device 3b. In response to this, the information processing device 2 receives information to the effect that common ID federation will be performed from the application executing terminal device 3b, and updates the second correspondence relationship table t6.

[0102] 8 is a diagram for explaining an example of information stored in the storage unit 14 when the user performs common ID federation in the second application. Compared to FIG. 6, a common ID of "001" is newly associated with a common ID of "2001" in the second correspondence relationship table t6.

[0103] FIG. 9 is a diagram for explaining an example of a title screen of the second application after the user has performed common ID federation in the second application. In the display screen example of FIG. 7, the federation button d145 displays "Not federated", but in the display screen example of FIG. 9, it displays "Feedered (001)". In addition, the consent check box d150 was not checked in the display screen example of FIG. 7, but is automatically checked in the display screen example of FIG. 9. That is, the user can execute the application without performing an operation to agree to the common terms. In addition, in the display screen example of FIG. 7, the second application could not be executed even if the start button d152 was pressed, but in the display screen example of FIG. 9, the second application can be executed by the user by pressing the start button d152. In addition, the message d154 displayed in the display screen example of FIG. 7 is not displayed in the display screen example of FIG. 9.

[0104] Fig. 10 is a diagram for explaining another example of the title screen of the second application after the user has performed common ID federation in the second application. Compared to the display screen example of Fig. 9, the display screen example of Fig. 10 does not display the terms of use confirmation area d146. Restricting the request for consent to the common terms thus includes not displaying information related to the display or request of the terms of use.

[0105] (Effects of the system 1 according to the first embodiment) As described above, system 1 according to one embodiment of the present disclosure includes an execution unit 106 that executes at least one of a first application and a second application different from the first application, a first determination unit 104a that determines whether or not user consent to common terms has been obtained, where the common terms are terms of use common to the first application and the second application, and a request control unit 110 that controls whether or not to request consent to the common terms from the user when the execution unit 106 executes at least one of the first application and the second application, based on a determination result by the first determination unit 104a.

[0106] According to the system 1 of the first embodiment, it is possible to improve the convenience of the user agreeing to the terms of use of the app. Specifically, if the user of the system 1 agrees to the common terms, which are terms of use common to the first app and the second app, the user can execute the first app and the second app without being required to agree to the common terms when executing both the first app and the second app. Compared to the user having to agree to the terms of use for each of the first app and the second app individually, the system 1 reduces the user's effort.

[0107] In one embodiment, when a user specifies a first application and agrees to the common rules, the request control unit 110 is restricted from requesting agreement to the common rules when the execution unit 106 executes a second application.

[0108] This configuration can further improve user convenience. Specifically, by accepting consent to the common terms and conditions in a state where the first application is specified (for example, when the application execution terminal device 3b is displaying the title screen of the first application or when the cross-application management terminal device 3a is displaying the first application management screen), the user can consent to the terms and conditions for executing the second application while consenting to the terms and conditions for executing the first application.

[0109] In addition, the system 1 of one embodiment further includes a memory unit 14 that associates and stores common identification information, which is identification information common to the first application and the second application, with each of a plurality of users, and the common identification information is associated with an indicator indicating whether or not the user has agreed to the common terms, and the determination unit 104 determines whether or not the user has agreed to the common terms by referring to the indicator.

[0110] According to this configuration, the process of consenting to the common agreement can be simplified. For example, if a specific table stores a first user ID and an indicator indicating whether or not the user consents to the common agreement in association with each other, and another table stores a second user ID and an indicator indicating whether or not the user consents to the common agreement in association with each other, when the user consents to the common agreement, it is necessary to update both the specific table and the other table. In contrast, by storing a common ID in association with an indicator indicating whether or not the user consents to the common agreement (see common agreement agreement table t3), it is sufficient to update only one table.

[0111] In addition, in one embodiment, if a user agrees to the common rules in association with the common identification information without specifying the first application and the second application, the request control unit 110 is restricted from requesting agreement to the common rules when the execution unit 106 executes the second application.

[0112] A user may decide whether or not to agree to the common terms while overlooking a plurality of applications (i.e., without specifying any application) as in the cross-application management screen shown in Fig. 4. With this configuration, even if a user agrees to the common terms without specifying any application, the user can execute the application without being asked to agree again.

[0113] [Second embodiment] (Operation of the system 1 according to the second embodiment) An example of the operation of the system 1 according to the second embodiment will be described below with reference to Fig. 11 to Fig. 17. In the second embodiment, an example will be described in which the user selects whether or not to agree to the first individual terms, the second individual terms, and the common terms on each of the first application management screen, the second application management screen, and the cross-application management screen, and then executes the first application and the second application.

[0114] In the second embodiment, the first application can be executed if the user agrees to the first individual agreement and the common agreement, and the second application can be executed if the user agrees to the second individual agreement and the common agreement. In addition, the second embodiment is described assuming that the user has performed common ID federation for both the first application and the second application at an initial point in time.

[0115] 11 is a flowchart for explaining an example of the operation of the system 1 according to the second embodiment. First, the cross-application management terminal device 3a displays the contents of the first individual terms and accepts consent to the first individual terms (S200).

[0116] Fig. 12 is a diagram showing an example of a display screen of the cross-application management terminal device 3a in S200. The display screen example of Fig. 12 displays a title d200, a first individual agreement content d202, a scroll bar d204, an agreement checkbox d206, a non-display checkbox d208, and a back button d210.

[0117] The title d200 indicates the title of the display screen. In the example display screen of FIG. 12, "Terms of Use (First Application)" is displayed. The first individual agreement content d202 indicates the content of the first individual agreement. In the example display screen of FIG. 12, "Article 1 □□□... Article 2 XXX..." is displayed. The scroll bar d204 is an element for scrolling the display area of ​​the first individual agreement content d202. The agreement check box d206 is a check box that allows the user to agree to the first individual agreement by pressing it. The non-display check box d208 is a check box that allows the user to set not to display information about the first individual agreement when the first application is executed by pressing it. Note that the non-display check box d208 can typically be pressed only when the agreement check box d206 is checked (i.e., when the user agrees to the first individual agreement). In this example, since the agreement check box d206 is checked, the non-display check box d208 can be pressed. The back button d210 is a button that allows the user to return to the screen that was displayed immediately before by pressing it.

[0118] For example, the user can display a display screen such as that shown in FIG. 12 on the cross-application management terminal device 3a by pressing an individual terms display button (not shown) displayed on the first application management screen.

[0119] Returning to FIG. 11, next, the cross-application management terminal device 3a displays the contents of the second individual terms and receives consent to the second individual terms (S202).

[0120] Fig. 13 is a diagram showing an example of a display screen of the cross-application management terminal device 3a in S202. The display screen example of Fig. 13 displays a title d220, second individual agreement contents d222, a scroll bar d224, an agreement checkbox d226, a non-display checkbox d228, and a back button d230.

[0121] The title d220 indicates the title of the display screen. In the display screen example of FIG. 13, "Terms of Use (Second App)" is displayed. The second individual agreement content d222 indicates the content of the second individual agreement. In the display screen example of FIG. 13, "Article 1 XXX... Article 2 △△△..." is displayed. The scroll bar d224 is an element for scrolling the display area of ​​the second individual agreement content d222. The agreement check box d226 is a check box that allows the user to agree to the second individual agreement by pressing it. The non-display check box d228 is a check box that allows the user to set not to display information about the second individual agreement when the second app is executed by pressing it. Note that the non-display check box d228 can typically be pressed only when the agreement check box d226 is checked (i.e., the user agrees to the second individual agreement). In this example, the agreement check box d226 is not checked, so the non-display check box d228 cannot be pressed. The back button d230 is a button that allows the user to return to the screen that was displayed immediately before by pressing it.

[0122] For example, the user can display a display screen such as that shown in FIG. 13 on the cross-application management terminal device 3a by pressing an individual terms display button (not shown) displayed on the second application management screen.

[0123] Returning to FIG. 11, next, the cross-application management terminal device 3a displays the contents of the common agreement and receives consent to the common agreement (S204).

[0124] Fig. 14 is a diagram showing an example of a display screen of the cross-application management terminal device 3a in S204. The display screen example of Fig. 14 displays a title d240, common terms of use contents d242, a scroll bar d244, an agreement checkbox d246, a non-display checkbox d248, a message d250, and a back button d252.

[0125] The title d240 indicates the title of the display screen. In the example display screen of FIG. 14, "Common Terms" is displayed. The common terms content d242 indicates the contents of the common terms. In the example display screen of FIG. 14, "Article 1 ###... Article 2 ****..." is displayed. The scroll bar d244 is an element for scrolling the display area of ​​the common terms content d242. The agreement check box d246 is a check box that the user can press to agree to the common terms. The hidden check box d248 is a check box that the user can press to set not to display information about the common terms when the first application and the second application are executed. Note that the hidden check box d248 can typically be pressed only when the agreement check box d246 is checked (i.e., the user agrees to the common terms). In this example, since the agreement check box d246 is checked, the user can press the hidden check box d248, but does not press it. The message d250 indicates that the agreement to the common terms is reflected in multiple applications that have been linked with a common ID. The back button d252 is a button that allows the user to return to the previously displayed screen by pressing it.

[0126] For example, the user can display a display screen such as that shown in FIG. 14 on the cross-application management terminal device 3a by pressing a common rules display button d112 (see FIG. 4) displayed on the cross-application management screen.

[0127] FIG. 15 is a diagram for explaining an example of information stored in the storage unit 14 up to the point after S204.

[0128] 15(A) is a diagram showing an example of the first individual terms and conditions agreement table t1 at a point in time after S204. In the first individual terms and conditions agreement table t1, the first user ID "1001" is associated with an indicator "Done" indicating that the user's agreement to the first individual terms and conditions has been accepted (corresponding to the agreement checkbox d206 in FIG. 12), and a setting of "Do not display" indicating that the first individual terms and conditions will not be displayed when the first application is executed (corresponding to the non-display checkbox d208 in FIG. 12).

[0129] 15(B) is a diagram showing an example of the second individual terms and conditions agreement table t2 at a point in time after S204. In the second individual terms and conditions agreement table t2, the second user ID "2001" is associated with an indicator of "not yet" indicating that the user's agreement to the second individual terms and conditions has not been accepted (corresponding to the agreement checkbox d226 in FIG. 13), and a setting of "display" indicating that the second individual terms and conditions are to be displayed when the second application is executed (corresponding to the non-display checkbox d228 in FIG. 13).

[0130] 15(C) is a diagram showing an example of the common agreement agreement table t3 at a point in time after S204. In the common agreement agreement table t3, a common ID of "001" is associated with an indicator of "Done" indicating that the user's agreement to the common agreement has been accepted (corresponding to the agreement checkbox d246 in FIG. 14), and a setting of "Display" indicating that the common agreement is to be displayed when both the first application and the second application are executed (corresponding to the non-display checkbox d248 in FIG. 14).

[0131] Returning to FIG. 11, next, the application execution terminal device 3b displays the title screen of the first application based on the user's operation (S206).

[0132] Fig. 16 is a diagram for explaining an example of the title screen of the first application displayed in S206. The title screen of the first application in Fig. 16 displays a title d260, a user ID display area d262, a common ID linkage display area d264, a terms of use confirmation area d266, and a start button d276. Of these, the elements other than the terms of use confirmation area d266 are similar to those described in the first embodiment, and therefore will not be described below.

[0133] In the terms of use confirmation area d266, elements related to consent to the common terms (i.e., the common terms display button d272 and the consent checkbox d274) are displayed, but elements related to consent to the first individual terms are not displayed. This is because the first individual terms are set not to be displayed when the first application is executed (corresponding to the non-display checkbox d208 in FIG. 12), and the common terms are set to be displayed when the first application is executed (corresponding to the non-display checkbox d248 in FIG. 14).

[0134] Furthermore, in the terms of use confirmation area d266, the agreement checkbox d274 is automatically checked. This is because the user has agreed to the common terms in advance (corresponding to the agreement checkbox d246 in FIG. 14).

[0135] In this example, since the user has agreed to the common agreement and the first individual agreement in advance, the user can execute the first application by pressing the start button d276.

[0136] Returning to FIG. 11, next, the application execution terminal device 3b displays the title screen of the second application based on the user's operation (S208).

[0137] Fig. 17 is a diagram for explaining an example of the title screen of the second application displayed in S208. The title screen of the second application in Fig. 17 displays a title d280, a user ID display area d282, a common ID linkage display area d284, a terms of use confirmation area d286, a message d302, and a start button d300. Of these, the elements other than the terms of use confirmation area d286 are the same as those described in the first embodiment, and therefore will not be described below.

[0138] The terms of use confirmation area d286 displays elements related to consent to the common terms (i.e., the common terms display button d292 and the consent checkbox d294) and elements related to consent to the second individual terms (i.e., the second individual terms display button d296 and the consent checkbox d298). This is because the common terms and the second individual terms are set to be displayed when the second application is executed (corresponding to the non-display checkbox d228 in FIG. 13 and the non-display checkbox d248 in FIG. 14).

[0139] Additionally, in the terms of use confirmation area d286, the agreement checkbox d294 is automatically checked. This is because the user has agreed to the common terms in advance (corresponding to the agreement checkbox d246 in FIG. 14).

[0140] In this example, since the user has agreed to the common terms and conditions in advance, the user can execute the second application by pressing the start button d300 after agreeing to the second individual terms and conditions.

[0141] (Effects of the system 1 according to the second embodiment) In one embodiment, the system 1 further includes a second determination unit 104b that determines whether or not user consent to the individual terms has been obtained, where the individual terms are terms of use for the second application that differ at least in part from the common terms, and a display unit 108 that displays the common terms and the individual terms in an identifiable manner when the second application is specified in association with the common identification information, and the request control unit 110 further controls whether or not to request consent to the individual terms from the user when the execution unit 106 executes the second application, based on the determination result by the second determination unit 104b.

[0142] There may be differences between the terms of use for the first application and the terms of use for the second application. With this configuration, it is possible to distinguish between the common terms, which are the common parts between the terms of use for the first application and the terms of use for the second application, and the individual terms, which are the different parts. As a result, it is easy for the user to understand the similarities and differences between the terms of use for the first application and the terms of use for the second application.

[0143] In addition, in one embodiment, the system 1 further includes a reception unit 100 that receives setting input from a user to display the common terms, and when the reception unit 100 receives the setting input, the request control unit 110 displays the common terms when the execution unit 106 executes at least one of the first application and the second application, regardless of the determination result by the first determination unit 104a.

[0144] Even if a user has agreed to the terms of use once, there are cases where the user wants to check the terms of use again just before executing the application. With this configuration, it is possible to control the display according to the user's policy.

[0145] The effects of the system 1 described in the above embodiment are merely examples and do not limit the scope of application of the present disclosure.

[0146] <4. Hardware configuration> 18, an example of a hardware configuration in which each device including the above-mentioned information processing device 2 is realized by a computer 70 will be described. Note that the functions of each device can also be realized by dividing them into a plurality of devices.

[0147] As shown in FIG. 18, a computer 70 includes a processor 700, a storage device 702, an input I / F 704, a data I / F 706, a communication I / F 708, and a display device 710.

[0148] The processor 700 controls various processes in the computer 70 by executing programs stored in the storage device 702. For example, each functional unit included in the control unit 10 of the information processing device 2 can be realized by the processor 700 executing the programs stored in the storage device 702.

[0149] The storage device 702 is a storage medium such as a random access memory (RAM), etc. The RAM temporarily stores the program code of the program executed by the processor 700 and data required when the program is executed.

[0150] The storage device 702 may also be a non-volatile storage medium such as a hard disk drive (HDD) or a flash memory. The storage device 702 stores an operating system and various programs for implementing the above-mentioned configurations. The storage medium storing the various programs may be a non-transitory computer readable medium. In addition, the storage device 702 may store a table for registering various information and a DB for managing the table. Such programs and data are loaded into the storage device 702 as necessary and referred to by the processor 700.

[0151] The input I / F 704 is a device for receiving input from a user. Specific examples of the input I / F 704 include a camera, a button, a microphone, a keyboard, a mouse, a touch panel, various sensors, and a wearable device. The input I / F 704 may be connected to the computer 70 via an interface such as a Universal Serial Bus (USB).

[0152] The data I / F 706 is a device for inputting data from outside the computer 70. A specific example of the data I / F 706 is a drive device for reading data stored in various storage media. The data I / F 706 may be provided outside the computer 70. In that case, the data I / F 706 is connected to the computer 70 via an interface such as a USB.

[0153] The communication I / F 708 is a device for performing data communication via the communication network 4, either wired or wirelessly, with an external device of the computer 70. The communication I / F 708 may be provided outside the computer 70. In that case, the communication I / F 708 is connected to the computer 70 via an interface such as a USB.

[0154] The display device 710 is a device for displaying various types of information. Specific examples of the display device 710 include a liquid crystal display, an organic EL (Electro-Luminescence) display, and a display of a wearable device. The display device 710 may be provided outside the computer 70. In that case, the display device 710 is connected to the computer 70 via, for example, a display cable. In addition, when a touch panel is adopted as the input I / F 704, the display device 710 can be configured integrally with the input I / F 704.

[0155] The components of the terminal device 3 described in the above embodiment are assumed to realize a predetermined process in cooperation with other hardware by the processor 700 executing a program stored in the storage device 702. In other words, these components are assumed to be software or firmware, and also corresponding hardware, and in both concepts, they are also described as "functions," "means," "parts," "processing circuits," "units," or "modules," and can be interpreted as each of these.

[0156] <5. Modifications> In the above embodiment, the reception unit 100, the association unit 102, the determination unit 104, the execution unit 106, the display unit 108, and the request control unit 110 have been described as being one aspect of the functions of the control unit 10 of the information processing device 2, but are not limited to this. For example, at least some of these functions may be provided in the terminal device 3.

[0157] [Agreement to pre-release terms of use] In the above embodiment, the first application and the second application are described as being released applications, but this is not limiting. In one embodiment, the execution unit 106 is restricted from executing the second application during a first period (e.g., a period before release) and is allowed to execute the second application during a second period (e.g., a period after release), and if the user has agreed to the common terms in association with the common identification information at least during the first period, the request control unit 110 is restricted from requesting agreement to the common terms when the execution unit 106 executes the second application during the second period. That is, the system 1 may be configured to accept agreement to the terms of use during a period before the release of the second application, for example, and not to request agreement again after the release.

[0158] A more detailed description will be given with reference to Figs. 19 and 20. Fig. 19 is a diagram showing an example of a cross-application management screen. According to the cross-application management screen of Fig. 19, a user can cross-manage a released first application and a pre-released second application. The cross-application management screen of Fig. 19 displays a title d400, a common ID d402, a released application designation area d404, a pre-release application designation area d408, and a terms of use confirmation area d412. Of these, the title d400, the common ID d402, and the terms of use confirmation area d412 are similar to the title d100, the common ID d102, and the terms of use confirmation area d110 described with reference to Fig. 4, respectively, and therefore will not be described below.

[0159] A first application designation button d406 is displayed in the released application designation area d404. The user can transition the display screen of the cross-application management terminal 3a to a first application management screen (see FIG. 5) by pressing the first application designation button d406. As described in the first embodiment, the user can perform an operation related to consent to the terms of use on the first application management screen.

[0160] A second application designation button d410 is displayed in the pre-release application designation area d408. By pressing the second application designation button d410, the user can transition the display screen of the cross-application management terminal 3a to a second application management screen.

[0161] Fig. 20 is a diagram for explaining an example of a second application management screen displayed on the cross-application management terminal device 3a. The second application management screen in Fig. 20 displays a title d420, a user information display area d422, and a terms of use confirmation area d424.

[0162] The title d420 indicates the title of the display screen. In this example, it says "Second App Management."

[0163] In the user information display area d422, the second user ID, common ID, track record, billing history, and friends are displayed as item names. Note that since the second application is an application that has not yet been released, the actual values ​​corresponding to each item are not displayed at this point.

[0164] The terms of use confirmation area d424 displays a benefit display button d430, a terms of use display button d426, and an agreement check box d428. The user can display the contents of the terms of use on the cross-application management terminal device 3a by pressing the terms of use display button d426. The user can also agree to the terms of use in association with the second user ID or the common ID by pressing the agreement check box d428. In this way, if the user presses the agreement check box d428 before release, the user can execute the second application after release without being asked to agree to the terms of use (see the display screen example of FIG. 10).

[0165] Even if a user is requested to agree to the terms of use when he or she attempts to start using an app, the user may be highly motivated to use the app at that time and may not read the terms of use thoroughly. With this configuration, the user can agree to the terms of use in a first period (e.g., a period before the release of the app) and can run the app without being requested to agree to the terms of use again in a second period (e.g., a period after the release of the app). As a result, the user will be able to thoroughly read the terms of use and run the app smoothly immediately after the app is released.

[0166] The benefit display button d430 shown in FIG. 20 is a button that, when pressed by the user, can display a benefit for pre-registering an app on the cross-application management terminal 3a. Pre-registration includes a procedure in which a user indicates an intention to use an app before its release and can start using the app as soon as it is released. Note that, while FIG. 20 shows an example of a display screen after the user has already performed pre-registration, a pre-registration button may be displayed instead of the benefit display button d430 before the user performs pre-registration. The user may perform pre-registration of an app by pressing the pre-registration button.

[0167] In addition, in a mode in which consent to the terms of use of the application is accepted before the release, the first application and the second application may not have a common agreement. That is, a system 1 according to another mode of the present disclosure includes an execution unit 106 that executes a target application, a determination unit 104 that determines whether or not consent to the terms of use of the target application from the user has been obtained, and a request control unit 110 that controls whether or not to request consent to the terms of use from the user when the execution unit 106 executes the target application based on a determination result by the determination unit 104, and the execution unit 106 restricts execution of the target application in a first period and allows execution of the target application in a second period, and when the user agrees to the terms of use of the target application at least in the first period, the request control unit 110 restricts a request for consent to the terms of use when the execution unit 106 executes the target application in the second period.

[0168] Furthermore, if the terms of use are updated after the user initially consented to them during the first period, it is preferable that the system 1 requests the user to consent to the terms of use again before the user executes the target application. In this case, the content of the request may be determined according to the content of the update to the terms of use. For example, if the update to the terms of use is relatively minor, the system 1 may simply request the user to press a button to agree to the terms of use (without requesting the updated terms of use to be displayed). On the other hand, for example, if the terms of use are significantly updated, the system 1 may display the updated terms of use and then request the user to press a button to agree to the terms of use.

[0169] Furthermore, if the terms of use are updated after the user initially consented to the terms of use during the first period, the system 1 may display a request for consent again in association with the target application on a cross-application management screen (see FIG. 19). Alternatively, the system 1 may request consent again on a management screen for the target application (see FIG. 20). Alternatively, the system 1 may request consent again on a title screen (see FIG. 5-FIG. 6, etc.) that is displayed when the target application is executed.

[0170] [Display of Terms of Use] In the above embodiment, an example has been described in which the contents of the individual terms and conditions are displayed together (see Figs. 12 and 13), but this is not limiting. For example, if there is an item common to the first individual terms and conditions and the second individual terms and conditions, the item may be displayed separately from the other items. For example, if the terms of use include a EULA (an example of individual terms and conditions) and a privacy policy (an example of common terms and conditions), and there is an item common to the EULA of the first app and the EULA of the second app, the item may be displayed so as to be distinguishable from the other items.

[0171] In the above embodiment, an example in which the contents of the common rules are displayed together has been described (see FIG. 14), but this is not limiting. For example, if the information processing device 2 accepts the user's consent to the common rules at a first time point and there is a change to the common rules between the first time point and the second time point, the information processing device 2 may display the changed parts and the unchanged parts separately when displaying the common rules at the second time point.

[0172] [Consent by minors] In the above embodiment, the system 1 has been described as accepting consent to the terms of use from the user himself / herself, but this is not limited to the above. For example, if the user himself / herself is a minor, the system 1 may accept consent to the terms of use from the user's legal representative on behalf of the user himself / herself (or together with the user himself / herself). In this case, the system 1 may notify the user's legal representative of the acceptance of consent to the terms of use from the user himself / herself.

[0173] The content of the notification sent to the user's legal representative in response to receiving consent to the terms of use from the user may simply inform the user that he or she has agreed to the terms of use, or may request additional consent from the user's legal representative.

[0174] Furthermore, if the Terms of Use are updated between a first point in time when the user's legal representative initially consented to the Terms of Use and a second point in time thereafter, the content of the notification sent to the user's legal representative in response to accepting the user's consent to the Terms of Use may be determined according to the content of the update to the Terms of Use. For example, if the update to the Terms of Use is relatively minor, the system 1 may simply notify the user's legal representative that the user has consented to the Terms of Use. On the other hand, for example, if the Terms of Use are significantly updated, the system 1 may send a notification requesting additional consent from the user's legal representative.

[0175] [Other variations] In the above embodiment, one of the first and second apps may be an old version app and the other a new version app. Also, one of the first and second apps may be a full-price version app and the other a low-priced version app. Also, one of the first and second apps may be a regular version app and the other a trial version app.

[0176] In the above embodiment, it has been described that the "Terms of Use" can be read as the "Common Terms" or the "Individual Terms" (i.e., a lower concept) as long as no contradiction occurs, but this is not limited to the above. For example, the "Common Terms" and the "Individual Terms" can be read as the "Terms of Use" (i.e., a higher concept) as long as no contradiction occurs.

[0177] <6. Other embodiments> The following aspects are also included within the scope of the present disclosure.

[0178] [Appendix 1] A system 1 according to one embodiment of the present disclosure includes an execution unit 106 that executes at least one of a first application and a second application different from the first application, a first determination unit 104a that determines whether or not user consent to common terms has been obtained, the common terms being terms of use common to the first application and the second application, and a request control unit 110 that controls whether or not to request consent to the common terms from the user when the execution unit 106 executes at least one of the first application and the second application, based on a determination result by the first determination unit 104a.

[0179] [Appendix 2] In the system 1 described in Appendix 1, when a user specifies a first application and agrees to the common terms, the request control unit 110 may limit the request for agreement to the common terms when the execution unit 106 executes a second application.

[0180] [Appendix 3] The system 1 described in Supplementary Note 1 or Supplementary Note 2 may further include a memory unit 14 that stores common identification information, which is identification information common to the first application and the second application, in association with each of a plurality of users, and the common identification information is associated with an indicator indicating whether or not the user has agreed to the common terms, and the determination unit 104 may determine whether or not the user has agreed to the common terms by referring to the indicator.

[0181] [Appendix 4] In the system 1 described in Appendix 3, if a user agrees to the common terms in association with common identification information without specifying the first application and the second application, the request control unit 110 may limit the request for agreement to the common terms when the execution unit 106 executes the second application.

[0182] [Appendix 5] In the system 1 described in Supplementary Note 3 or Supplementary Note 4, the execution unit 106 may be restricted from executing the second application in a first period and may be able to execute the second application in a second period, and if the user has agreed to the common terms in association with the common identification information at least in the first period, the request control unit 110 may be restricted from requesting agreement to the common terms when the execution unit 106 executes the second application in the second period.

[0183] [Appendix 6] The system 1 described in any one of Supplementary Notes 3 to 5 may further include a second determination unit 104b that determines whether or not user consent to the individual terms has been obtained, where the individual terms are terms of use for a second application that differ at least in part from the common terms, and a display unit 108 that displays the common terms and the individual terms in an identifiable manner when the second application is specified in association with common identification information, and the request control unit 110 may further control whether or not to request consent to the individual terms from the user when the execution unit 106 executes the second application based on the determination result by the second determination unit 104b.

[0184] [Appendix 7] In the system 1 described in Appendix 6, the execution unit 106 may be restricted from executing the second application during the first period and may be able to execute the second application during the second period, and if the request control unit 110 has agreed to the individual terms in association with the common identification information during at least the first period, the request for agreement to the individual terms when the execution unit 106 executes the second application during the second period may be restricted.

[0185] [Appendix 8] In the system 1 described in any one of Supplementary Notes 1 to 7, requesting user consent to the common terms includes displaying the common terms to the user, and if the first determination unit 104a determines that user consent has not been obtained, the request control unit 110 displays the common terms when the execution unit 106 executes at least one of the first application and the second application, and if the first determination unit 104a determines that user consent has been obtained, the request control unit 110 may restrict the display of the common terms when the execution unit 106 executes at least one of the first application and the second application.

[0186] [Appendix 9] The system 1 described in Appendix 8 may further include a reception unit 100 that receives setting input from a user to display the common terms, and when the reception unit 100 receives the setting input, the request control unit 110 may display the common terms regardless of the determination result by the first determination unit 104a when the execution unit 106 executes at least one of the first application and the second application.

[0187] [Appendix 10] In the system 1 described in Appendix 8 or Appendix 9, if the common terms are changed between a first point in time when the user agrees to the common terms and a second point in time after the first point in time when the execution unit 106 executes the first application or the second application, the request control unit 110 may display the common terms regardless of the determination result by the first determination unit 104a when the execution unit 106 executes at least one of the first application and the second application.

[0188] [Appendix 11] A program according to another embodiment of the present disclosure causes a computer 70 to function as an execution means for executing at least one of a first application and a second application different from the first application, a first determination unit 104a for determining whether or not user consent to common terms has been obtained, the common terms being terms of use common to the first application and the second application, and a request control means for controlling whether or not to request consent to the common terms from the user when the execution means executes at least one of the first application and the second application based on a determination result by the first determination unit 104a.

[0189] [Appendix 12] An information processing device 2 according to another embodiment of the present disclosure includes an execution unit 106 that executes at least one of a first application and a second application different from the first application, a first determination unit 104a that determines whether or not user consent to a common agreement has been obtained, the common agreement being a term of use common to the first application and the second application, and a request control unit 110 that controls whether or not to request consent to the common agreement from the user when the execution unit 106 executes at least one of the first application and the second application, based on a determination result by the first determination unit 104a. [Explanation of symbols]

[0190] 1 System 2. Information processing equipment 3 Terminal Equipment 3a Cross-application management terminal device 3b Terminal device for executing applications 4. Communication Network 10 Control section 14 Storage section 70 Computer 100 Reception 102 Association section 104 Judgment section 104a 1st judgment part 104b Second judgment part 106 Executive Department 108 Display section 110 Request control section

Claims

1. an execution unit that executes at least one of a first application and a second application different from the first application; a first determination unit that determines whether or not consent to a common agreement has been obtained from a user, the common agreement being a term of use common to the first application and the second application; a request control unit that controls whether or not to request consent to the common protocol from a user when the execution unit executes at least one of the first application and the second application, based on a determination result by the first determination unit; A system comprising:

2. The system according to claim 1 , wherein when a user specifies the first application and agrees to the common agreement, the request control unit is restricted from requesting agreement to the common agreement when the execution unit executes the second application.

3. a storage unit that stores common identification information, which is identification information common to the first application and the second application, in association with each of a plurality of users, and the common identification information is associated with an indicator indicating whether or not the user has agreed to the common agreement; The system according to claim 1 , wherein the first determination unit determines whether or not consent to the common agreement from the user has been obtained by referring to the indicator.

4. The system of claim 3, wherein when a user agrees to the common agreement in association with the common identification information without specifying the first application and the second application, the request control unit is restricted from requesting agreement to the common agreement when the execution unit executes the second application.

5. the execution unit is configured to restrict execution of the second application during a first period and to be able to execute the second application during a second period; The system described in claim 3, wherein if a user agrees to the common terms in association with the common identification information during at least the first period, the request control unit is limited in requesting agreement to the common terms when the execution unit executes the second application during the second period.

6. a second determination unit that determines whether or not consent to an individual agreement has been obtained from a user, the individual agreement being a term of use for the second application that is at least partially different from the common agreement; a display unit that displays the common agreement and the individual agreement in a distinguishable manner when the second application is designated in association with the common identification information; Further equipped with The system according to claim 3 , wherein the request control unit further controls whether or not to request the user to agree to the individual terms when the execution unit executes the second application based on a determination result by the second determination unit.

7. the execution unit is configured to restrict execution of the second application during a first period and to be able to execute the second application during a second period; The system described in claim 6, wherein when the request control unit agrees to the individual terms and conditions in association with the common identification information during at least the first period, the request for agreement to the individual terms and conditions when the execution unit executes the second application during the second period is restricted.

8. Requiring user agreement to the common agreement includes displaying the common agreement to the user; When the first determination unit determines that the consent of the user has not been obtained, the request control unit displays the common agreement when the execution unit executes at least one of the first application and the second application; The system described in claim 1 , wherein when the first determination unit determines that user consent has been obtained, the request control unit restricts the display of the common terms and conditions when the execution unit executes at least one of the first application and the second application.

9. a reception unit that receives an input of a setting for displaying the common rules from a user, 9. The system of claim 8, wherein when the reception unit receives the setting input, the request control unit displays the common rules when the execution unit executes at least one of the first application and the second application, regardless of the judgment result by the first judgment unit.

10. 9. The system of claim 8, wherein if the common rules are changed between a first point in time at which a user agrees to the common rules and a second point in time after the first point in time at which the execution unit executes at least one of the first application and the second application, the request control unit displays the common rules when the execution unit executes at least one of the first application and the second application, regardless of the determination result by the first determination unit.

11. Computer, an execution means for executing at least one of a first application and a second application different from the first application; a first determination unit that determines whether or not a user's consent to a common agreement has been obtained, the common agreement being a term of use common to the first application and the second application; a request control means for controlling, based on a result of the determination by the first determination unit, whether or not to request consent to the common protocol from a user when the execution means executes at least one of the first application and the second application; A program that functions as a

12. an execution unit that executes at least one of a first application and a second application different from the first application; a first determination unit that determines whether or not consent to a common agreement has been obtained from a user, the common agreement being a term of use common to the first application and the second application; a request control unit that controls whether or not to request consent to the common protocol from a user when the execution unit executes at least one of the first application and the second application, based on a determination result by the first determination unit; An information processing device comprising:

Images