JP7400375B2 - Management systems and programs - Google Patents

Description

The present invention relates to a management system and program.

Traditionally, applications used on smartphones such as the iPhone (registered trademark) and Android (registered trademark) use a so-called in-app billing system to expand the app's functionality and purchase additional content. It is common to do so. For example, as a billing method using such an in-app billing system, an item billing method has been proposed in which billing and settlement for purchasing multiple types of items in a game app are performed by calling a phone number (for example, (See Patent Document 1).

JP 2018-32363 Publication

In the item charging method disclosed in Patent Document 1, charging is performed using the iOS (registered trademark) in-app charging system for iPhone (registered trademark), while charging is performed using the in-app charging system for Android (registered trademark). Billing is performed using the Android OS (registered trademark) in-app billing system, and each billing status is managed by a separate billing management server. Therefore, when checking a customer's billing status, it is necessary to make an inquiry to each billing management server, which is troublesome.

The present invention has been made in view of such problems, and an object of the present invention is to grant more appropriate usage rights to users depending on the charging status.

In order to solve the above problems, the management system according to the present invention,
A receipt that is issued in association with a predetermined login user ID when a charge is made with a predetermined login user ID via a first application running on a first OS; acquisition means for acquiring a receipt issued from a corresponding store server to the first application from the first application at a predetermined timing;
a management unit that manages billing status by the login user ID based on the receipt acquired by the acquisition unit from the first application;
a setting means for setting a usage permission range of functions of the first application for the login user ID in accordance with a billing situation managed by the management means;
The login user ID is used to log into an application that is an application that operates on a second OS whose corresponding store server is different from the first OS and is registered in advance as a second application corresponding to the first application. When logged in, the login user ID is allowed to use the functions of the second application within the same usage permission range set for the functions of the first application by the setting means. a means of authorization; and
It is characterized by having the following.

According to the present invention, it is possible to grant more appropriate usage authority to the user depending on the billing status.

FIG. 1 is a schematic configuration diagram showing an in-app billing system according to the present embodiment. FIG. 2 is a block diagram showing the functional configuration of a terminal device. FIG. 2 is a block diagram showing the functional configuration of a cloud server. FIG. 2 is a block diagram showing the functional configuration of a billing management server. (a) is a data table showing the state before the user whose "login ID" is "abcde" purchases a chargeable item, and (b) is a data table showing the state after the user purchases the chargeable item. . 12 is a flowchart illustrating an example of the operation of the in-app billing system when a billing item corresponding to Company A's OS is purchased. 12 is a flowchart illustrating an example of the operation of the in-app billing system when a billing item compatible with Company A's OS is purchased through a predetermined website. 12 is a flowchart illustrating an example of the operation of the in-app billing system when one user logs into the mobile application via a terminal device equipped with a company A OS. 12 is a flowchart illustrating an example of the operation of the in-app billing system when one user logs into the mobile application via a terminal device equipped with Company B's OS. FIG. 2 is a diagram showing an overall view of operations performed by the in-app billing system of the present embodiment.

Below, specific aspects of the present invention will be explained using the drawings.

≪Configuration of in-app billing system 1≫
First, the configuration of this embodiment will be explained with reference to FIG. FIG. 1 is a schematic configuration diagram showing an in-app billing system 1 of this embodiment.

As shown in FIG. 1, an in-app billing system (management system) 1 is equipped with an OS (e.g., iOS) from company A (e.g., Apple (registered trademark)) as a first OS (operation system). A terminal device 10A equipped with company A's OS, a terminal device 10B equipped with company B's OS (for example, Google (registered trademark)) as a second OS (Android OS), and a store server for company A's OS. 20, a store server 30 for Company B's OS, a cloud server 40, a billing management server 50, an original server 60, and the like. The terminal device 10A equipped with company A OS, the terminal device 10B equipped with company B OS, the store server 20 for company A OS, the store server 30 for company B OS, the cloud server 40, the billing management server 50, and the original server 60 are connected to a communication network. are connected to enable information communication via N.

The A-company OS-equipped terminal device 10A and the B-company OS-equipped terminal device 10B are, for example, smartphones or tablet terminals used by users. Specifically, the terminal device 10A equipped with company A's OS is an iPhone (registered trademark) or iPad (registered trademark) provided by Apple (registered trademark), and the terminal device 10B equipped with company B's OS is an iPhone (registered trademark) or an iPad (registered trademark) provided by Apple (registered trademark). ) is an Android (registered trademark) version of smartphones and tablets provided by the company.

When a billing item 42a (described later) is purchased in a mobile application 12a (described later) launched on a terminal device 10A equipped with a company A's OS, the store server 20 for company A's OS receives a receipt from the purchase of the billing item 42a. This is the issuing server. The receipt here indicates electronic purchase information when the user purchased the billing item 42a via the store server 20 for Company A's OS. Furthermore, when a billing management server 50 (described later) requests verification of a receipt (a receipt issued by the store server 20 for Company A's OS), the store server 20 for Company A's OS determines whether the receipt is legitimate. This is a server that verifies whether or not it is true.

When a billing item 42a (described later) is purchased within the mobile application 12a (described later) launched on the terminal device 10B equipped with the company B's OS, the store server 30 for company B's OS receives the receipt for the purchase of the billing item 42a. This is the issuing server. The receipt here indicates electronic purchase information when the user purchased the billing item 42a via the store server 30 for company B's OS. In addition, similarly to the store server 20 for Company A's OS, the store server 30 for Company B's OS receives a request to verify a receipt (a receipt issued by the store server 30 for Company B's OS) by the billing management server 50, which will be described later. In this case, it is a server that verifies whether the receipt in question is legitimate.

The cloud server 40 is a server that provides cloud services (for example, use of billing items 42a, etc.) when using the mobile application 12a started on the terminal device 10A equipped with company A's OS or the terminal device 10B equipped with company B's OS.

The billing management server 50 stores billing items 42a that can be purchased within the mobile application 12a launched on the terminal device 10A equipped with company A's OS or the terminal device 10B equipped with company B's OS, and a predetermined web service via the cloud server 40. This is a server that manages the billing status of billing items 42a that can be purchased from a site (not shown).

The original server 60 accepts purchases of chargeable items 42a from a predetermined website (not shown) in addition to the route for accepting purchases of chargeable items 42a within the mobile application 12a launched on the terminal device 10A equipped with Company A's OS or the terminal device 10B equipped with Company B's OS. This is a server for accepting and managing purchases of the billing item 42a.

<Configuration of company A OS-equipped terminal device 10A>
Next, with reference to FIG. 2, the configuration of the company A OS-equipped terminal device 10A will be described. FIG. 2 is a block diagram showing the functional configuration of the company A OS-equipped terminal device 10A. Note that the OS-equipped terminal device 10B from Company B has the same configuration as the OS-equipped terminal device 10A from Company A, except for the difference in the installed OS, so a description thereof will be omitted.

As shown in FIG. 2, the Company A OS-equipped terminal device 10A includes a control section 11, a storage section 12, an operation section 13, a display section 14, a communication section 15, and the like.

The control unit 11 includes a CPU that executes various programs stored in the storage unit 12 to perform predetermined calculations and control each unit, and a memory that serves as a work area during program execution (both are not shown). ). The control unit 11 executes various processes in cooperation with programs stored in the storage unit 12.

The storage unit 12 is composed of a nonvolatile semiconductor memory or the like. The storage unit 12 stores system programs and application programs executed by the control unit 11, data necessary for executing these programs, and the like. Further, the storage unit 12 stores, for example, a certain mobile application 12a downloaded from the first store server 20 or the original server 60 via the communication network N.

The mobile application 12a incorporates a so-called in-app billing API (Application Programming Interface), and by using the API, a billing item 42a (described later) can be purchased.

The operation unit 13 includes various function keys, receives press input of each key by the user, and outputs the operation information to the control unit 11. Further, the operation unit 13 has a touch panel or the like in which transparent electrodes are arranged in a grid pattern so as to cover the surface of the display unit 14, and detects the position pressed with a finger or touch pen, etc., and uses the position information as operation information. It is output to the control section 11.

The display section 14 is composed of an LCD (Liquid Crystal Display) or the like, and performs various displays on the screen according to display control signals from the control section 11.

The communication unit 15 wirelessly connects to the communication network N and performs communication with external devices connected to the communication network N.

<Configuration of cloud server 40>
Next, the configuration of the cloud server 40 will be described with reference to FIG. 3. FIG. 3 is a block diagram showing the functional configuration of the cloud server 40.

As shown in FIG. 3, the cloud server (obtaining means, setting means, permission means) 40 includes a control section 41, a storage section 42, a communication section 43, and the like.

The control unit 41 includes a CPU that executes various programs stored in the storage unit 42 to perform predetermined calculations and control each unit, and a memory that serves as a work area during program execution (both are not shown). ). The control unit 41 executes various processes in cooperation with programs stored in the storage unit 42.

The storage unit 42 is composed of a nonvolatile semiconductor memory or the like. The storage unit 42 stores system programs and application programs executed by the control unit 41, data necessary for executing these programs, and the like.

Furthermore, the storage unit 42 stores charging items 42a that can be used within the mobile application 12a described above. The control unit 41 controls the purchase of the charge item 42a by one user (for example, the purchase of the charge item 42a within the mobile application 12a (first application) into which the one user has logged in via the company A OS-equipped terminal device 10A). When the purchase) is completed, even within the mobile application 12a (first application) that the one user logged in to via the terminal device 10A equipped with company A's OS, for example, the mobile application 12a (first application) logged in via the terminal device 10B equipped with company B's OS Even within the application 12a (second application), the billing item 42a (a function possessed by each of the first application and the second application) is made available.

The communication unit 43 includes a modem, a router, a network card, and the like. The communication unit 43 transmits and receives data to and from external devices connected via the communication network N.

<Configuration of billing management server 50>
Next, the configuration of the billing management server 50 will be explained with reference to FIG. 4. FIG. 4 is a block diagram showing the functional configuration of the billing management server 50.

As shown in FIG. 4, the billing management server (management means) 50 includes a control section 51, a storage section 52, a communication section 53, and the like.

The control unit 51 includes a CPU that executes various programs stored in the storage unit 52 to perform predetermined calculations and control each unit, and a memory that serves as a work area during program execution (both are not shown). ). The control unit 51 executes various processes in cooperation with programs stored in the storage unit 52.

The storage unit 52 is composed of a nonvolatile semiconductor memory or the like. The storage unit 52 stores system programs and application programs executed by the control unit 51, data necessary for executing these programs, and the like.

Furthermore, the storage unit 52 is provided with an accounting management DB 52a. The billing management DB 52a stores data tables for managing the billing status of billing items 42a for each user using the mobile application 12a.

FIG. 5 is a data table regarding the user whose "login ID (login user ID)" is "abcde". Specifically, FIG. 5(a) is a data table showing the state before the user purchases the charging item 42a, and FIG. 5(b) is a data table showing the state after the user purchases the charging item 42a. This is a data table showing. Here, the information in each item of "login ID" and "password" is information used when each user logs in to the mobile application 12a.

As shown in FIG. 5(a), when a user whose "login ID" is "abcde" is in a state before purchasing the billing item 42a, each item in the "vendor" item of the data table for the user is The information in the "purchase history" and "expiration date" items corresponding to the vendor are both in an unregistered state (indicated by a "-" symbol in the figure). Further, the "billing status" information corresponding to each vendor is all in an unpurchased status. Note that among the vendors, "Company A store" means the sale of billing items 42a compatible with the OS (eg, iOS) of Company A (eg, Apple (registered trademark)). Further, "Company B store" refers to the sale of billing items 42a compatible with the OS (eg, Android OS) of Company B (eg, Google (registered trademark)). "Company C store" refers to the sale of chargeable items 42a through a predetermined website operated by Company C.
For example, if the user purchases a billing item 42a that is compatible with Company A's OS, and the receipt issued at the time of the purchase is determined to be a legitimate receipt by Company A's OS store server 20, as shown in FIG. As shown in (b), the control unit 51 uses the "purchase history" information corresponding to "Company A Store" in the "Vendor" item of the data table for the user based on the information on the receipt. , for example, update to “2019/10/10”. Further, the control unit 51 updates the "expiration date" information corresponding to "Company A store" in the "vendor" item to, for example, "2019/11/10" based on the information on the receipt. Further, the control unit 51 updates the "billing status" information corresponding to each vendor in the "vendor" item from the unpurchased state to the purchased state. Although not shown, the user purchases the billing item 42a that is compatible with Company B's OS, and the receipt issued at the time of the purchase is determined to be a legitimate receipt by Company B's OS store server 30. or when the billing item 42a is purchased through the above-mentioned predetermined website, the control unit 51 changes the "billing status" information corresponding to each vendor in the "vendor" item from the unpurchased state. Update to purchased status.

The communication unit 53 is composed of a modem, a router, a network card, and the like. The communication unit 53 transmits and receives data to and from external devices connected via the communication network N.

≪Operation of in-app billing system 1≫
Next, the operation of the in-app billing system 1 in each phase will be explained using FIGS. 6 to 9.

<Operation of in-app billing system 1 when billing item 42a compatible with Company A's OS is purchased>
FIG. 6 is a flowchart showing an example of the operation of the in-app charging system 1 when the charging item 42a corresponding to the OS of company A is purchased.

As shown in FIG. 6, first, the company A OS-equipped terminal device 10A selects the charge item 42a when a purchase acceptance screen (not shown) for the charge item 42a is displayed within the mobile application 12a running on the own device. 42a is performed via the operation unit 13, the charge item 42a is purchased and a payment request is made to the company A OS store server 20 (step S1).

Next, the A company OS store server 20 that has received the payment request issues a receipt for the purchase of the billing item 42a, and transmits the receipt to the A company OS installed terminal device 10A (step S2).

Next, the company A OS-equipped terminal device 10A that received the receipt transfers the receipt and the login ID of the user who has logged in to the mobile application 12a from the own device to the cloud server 40 (step S3).

Next, the cloud server 40 transfers the transferred receipt and login ID to the billing management server 50 (step S4).

Next, upon receiving the receipt and the login ID, the billing management server 50 requests the company A OS store server 20 to verify whether the receipt is a valid receipt (step S5).

Next, the store server 20 for Company A's OS verifies the receipt based on the receipt verification request from the billing management server 50, and transmits the verification result to the billing management server 50 (step S6). Then, the processing by the store server 20 for company A's OS ends.

Next, the billing management server 50 reports the received verification result to the cloud server 40 (step S7). Furthermore, the billing management server 50 updates the information in the billing management DB 52a based on the received verification result (step S8). Specifically, as shown in FIG. 5(b), the billing management server 50 checks the user who is logged in to the mobile application 12a (for example, the user whose "login ID" is "abcde") and who is stored in the billing management DB 52a. The "purchase history" information corresponding to "Company A store" in the "vendor" item of the data table of a certain user is updated to, for example, "2019/10/10" based on the information on the receipt. Additionally, the billing management server 50 updates the "expiration date" information corresponding to "Company A Store" in the "Vendor" item to, for example, "2019/11/10" based on the information on the receipt. Additionally, the billing management server 50 updates the "billing status" information corresponding to each vendor in the "vendor" item from the unpurchased state to the purchased state. Then, the processing by the billing management server 50 ends.
Note that regarding the processing in steps S7 and S8, the processing in step S8 may be executed before the processing in step S7.

Next, when the cloud server 40 receives the report of the verification result, if the report is a valid receipt (step S9; YES), the cloud server 40 updates the mobile application running on the terminal device 10A equipped with company A's OS. Display switching control processing (step S10) is performed to switch the display screen of 12a, and a display switching signal is transmitted to the company A OS-equipped terminal device 10A. Then, the processing by the cloud server 40 ends.
On the other hand, if the above report is not a valid receipt (step S9; NO), the cloud server 40 issues an error notification to the company A OS-equipped terminal device 10A (step S11). Then, the processing by the cloud server 40 ends.

Next, the company A OS-equipped terminal device 10A determines whether a display switching signal has been received from the cloud server 40 (step S12).

In step S12, if it is determined that the display switching signal has been received (step S12; YES), the company A OS-equipped terminal device 10A stops accepting purchases of the billing item 42a, and displays a screen where the billing item 42a can be used ( (not shown) (step S13). Then, the processing by the company A OS-equipped terminal device 10A ends.
On the other hand, if it is determined in step S12 that the display switching signal has not been received (an error notification has been received) (step S12; NO), the company A OS-equipped terminal device 10A accepts the purchase of the billing item 42a. A screen (not shown) is continuously displayed (step S14). Then, the processing by the company A OS-equipped terminal device 10A ends.

Regarding the operation of the in-app billing system 1 when the billing item 42a corresponding to the OS of Company B is purchased, the terminal device 10A equipped with the OS of Company A is changed to the terminal device 10B equipped with the OS of Company B in the flowchart shown in FIG. The operation of the in-app billing system 1 is generally the same as when the billing item 42a corresponding to the OS of the company A described above is purchased, except that the store server 20 for the OS of the company A is replaced with the store server 30 for the OS of the company B. Since they are similar, their explanation will be omitted.

<Operation of in-app billing system 1 when billing item 42a is purchased through a predetermined website>
FIG. 7 is a flowchart showing an example of the operation of the in-app charging system 1 when the charging item 42a corresponding to the OS of company A is purchased through a predetermined website.

As shown in FIG. 7, first, when a purchase acceptance screen (not shown) for the charge item 42a is displayed on a predetermined website, the company A OS-equipped terminal device 10A displays a screen for purchasing the charge item 42a. When the procedure operation is performed via the operation unit 13, a purchase process is performed for the billing item 42a, and a payment request is made to the original server 60 (step S21).

Next, the original server 60 that received the payment request transfers the purchase information (receipt) when the purchase process was performed to the cloud server 40 (step S22).

Next, the cloud server 40 that has received the purchase information transmits to the billing management server 50 the login ID used when the user who has performed the procedure for purchasing the billing item 42a logs into the predetermined website, along with the purchase information. (step S23).

Next, upon receiving the purchase information and the login ID, the billing management server 50 requests the original server 60 to verify whether the purchase information is valid purchase information (step S24).

Next, the original server 60 verifies the purchase information based on the purchase information verification request from the billing management server 50, and transmits the verification result to the billing management server 50 (step S25). Then, the processing by the original server 60 ends.

Next, the billing management server 50 reports the received verification result to the cloud server 40 (step S26). Furthermore, the billing management server 50 updates the information in the billing management DB 52a based on the received login ID and purchase information (step S27). Specifically, the billing management server 50, although not shown, is a user who is logged in to a predetermined website (for example, a user whose "login ID" is "abcde") stored in the billing management DB 52a. The "purchase history" information corresponding to "Company C store" in the "vendor" item of the data table is updated to, for example, "2019/10/10" based on the purchase information. Additionally, the billing management server 50 updates the "expiration date" information corresponding to "Company C store" in the "vendor" item to, for example, "2019/11/10" based on the purchase information. Additionally, the billing management server 50 updates the "billing status" information corresponding to each vendor in the "vendor" item from the unpurchased state to the purchased state. Then, the processing by the billing management server 50 ends.
Note that regarding the processing in steps S26 and S27, the processing in step S27 may be executed before the processing in step S26.

Next, when the cloud server 40 receives the report of the verification result, if the report is a report that the purchase information is valid (step S28; YES), the cloud server 40 updates the web page currently logged in on the terminal device 10A equipped with Company A's OS. Display switching control processing (step S29) for switching the display screen of the site is performed, and a display switching signal is transmitted to the company A OS-equipped terminal device 10A. Then, the processing by the cloud server 40 ends.
On the other hand, if the above report is not valid purchase information (step S28; NO), the cloud server 40 notifies the company A OS-equipped terminal device 10A of an error (step S30). Then, the processing by the cloud server 40 ends.

Next, the company A OS-equipped terminal device 10A determines whether a display switching signal has been received from the cloud server 40 (step S31).

In step S31, if it is determined that the display switching signal has been received (step S31; YES), the company A OS-equipped terminal device 10A stops accepting purchases of the billing item 42a, and displays a screen where the billing item 42a can be used ( (not shown) (step S32). Then, the processing by the company A OS-equipped terminal device 10A ends.
On the other hand, if it is determined in step S31 that the display switching signal has not been received (an error notification has been received) (step S31; NO), the company A OS-equipped terminal device 10A accepts the purchase of the billing item 42a. A screen (not shown) is continuously displayed (step S33). Then, the processing by the company A OS-equipped terminal device 10A ends.
Regarding the operation of the in-app billing system 1 when the billing item 42a corresponding to the OS of company B is purchased through a predetermined website, the terminal device 10A equipped with the OS of company A in the flowchart shown in FIG. Except for being replaced with the installed terminal device 10B, the operation is generally the same as the operation of the in-app billing system 1 when the billing item 42a corresponding to the OS of Company A is purchased through the above-mentioned predetermined website, so a description thereof will be omitted. do.

<Operation of the in-app billing system 1 when logging into the mobile application 12a>
FIG. 8 is a flowchart showing an example of the operation of the in-app billing system 1 when one user logs in to the mobile application 12a (first application) via the company A OS-equipped terminal device 10A.

As shown in FIG. 8, first, when an operation for logging into the mobile application 12a is performed via the operation unit 13, the company A OS-equipped terminal device 10A performs a login process to the mobile application 12a. The login ID input via the operation unit 13 is then transmitted to the cloud server 40 (step S41).

Next, the cloud server 40 that received the login ID transfers the login ID to the billing management server 50 (step S42).

Next, the billing management server 50 that has received the login ID verifies the login ID using the billing management DB 52a (step S43), and refers to the data table corresponding to the login ID stored in the billing management DB 52a. Check the billing status and expiration date. Then, the billing management server 50 reports the verification result regarding the login ID (whether or not the billing status is a purchased state and whether or not the expiration date has expired) to the cloud server 40 (step S44). Then, the processing by the billing management server 50 ends.

Next, the cloud server 40 performs a display control process for a screen (for example, a home screen or a menu screen) displayed on the company A OS-equipped terminal device 10A that has logged into the mobile application 12a according to the verification result received from the billing management server 50. (Step S45) and transmits a display control signal to the company A OS-equipped terminal device 10A. Then, the processing by the cloud server 40 ends.

Next, if the display control signal received from the cloud server 40 is a signal corresponding to the verification result that the billing item 42a has been purchased and is within the expiration date (step S46; YES), the company A OS-equipped terminal device 10A displays the corresponding display control signal. Based on the signal, a screen (not shown) in which the billing item 42a can be used is displayed, for example, on the home screen or menu screen in the mobile application 12a (step S47). Then, the processing by the company A OS-equipped terminal device 10A ends.
On the other hand, if the display control signal received from the cloud server 40 is a signal corresponding to the verification result that the billing item 42a has been purchased and is not within the expiration date, the Company A OS-equipped terminal device 10A (step S46; NO). Based on the signal, for example, a screen (not shown) introducing the billing item 42a is displayed on the home screen or menu screen in the mobile application 12a (step S48). Then, the processing by the company A OS-equipped terminal device 10A ends.

Next, the operation of the in-app billing system 1 when one user logs in to the mobile application 12a (second application) via the company B OS-equipped terminal device 10B will be described using FIG.

As shown in FIG. 9, first, when an operation for logging into the mobile application 12a is performed via the operation unit 13, the company B OS-equipped terminal device 10B performs a login process to the mobile application 12a, and The login ID input via the operation unit 13 is then transmitted to the cloud server 40 (step S51).

Next, the cloud server 40 that has received the login ID transfers the login ID to the billing management server 50 (step S52).

Next, the billing management server 50 that has received the login ID verifies the login ID using the billing management DB 52a (step S53), and refers to the data table corresponding to the login ID stored in the billing management DB 52a. Check the billing status and expiration date. Then, the billing management server 50 reports the verification result regarding the login ID (whether or not the billing status is a purchased state and whether or not the expiration date has expired) to the cloud server 40 (step S54). Then, the processing by the billing management server 50 ends.

Next, the cloud server 40 performs display control processing for a screen (for example, a home screen or a menu screen) displayed on the company B OS-equipped terminal device 10B that has logged into the mobile application 12a according to the verification result received from the billing management server 50. (Step S55) and transmits a display control signal to the company B OS-equipped terminal device 10B. Then, the processing by the cloud server 40 ends.

Next, if the display control signal received from the cloud server 40 is a signal corresponding to the verification result that the billing item 42a has been purchased and is within the expiration date (step S56; YES), the company B OS-equipped terminal device 10B displays the corresponding display control signal. Based on the signal, a screen (not shown) in which the billing item 42a can be used is displayed, for example, on the home screen or menu screen in the mobile application 12a (step S57). Then, the processing by the company B OS-equipped terminal device 10B ends.
On the other hand, if the display control signal received from the cloud server 40 is a signal corresponding to the verification result that the billing item 42a has been purchased and is not within the expiration date, the company B OS-equipped terminal device 10B (step S56; NO) Based on the signal, for example, a screen (not shown) introducing the billing item 42a is displayed on the home screen or menu screen in the mobile application 12a (step S58). Then, the processing by the company B OS-equipped terminal device 10B ends.

Note that the operation of the in-app billing system 1 when one user logs in to a predetermined website via the terminal device 10A equipped with company A's OS or the terminal device 10B equipped with company B's OS is performed according to the steps of the flowchart shown in FIG. The operation of the in-app billing system 1 is generally the same as when logging into the mobile application 12a described above, except that "login to the mobile application" in step S41 and step S51 of the flowchart shown in FIG. 9 is replaced with "login to the website". Therefore, its explanation will be omitted.

<Overview of operations performed by in-app billing system 1>
Next, an overview of the operations performed by the in-app billing system 1 will be described. FIG. 10 is a diagram showing the overall operation performed by the in-app billing system 1.

As shown in FIG. 10, when a purchase process for a billing item 42a is performed within the mobile application 12a running on the terminal device 10A equipped with company A's OS or the terminal device 10B equipped with company B's OS, the terminal device 10A equipped with company A's OS Alternatively, the terminal device 10B equipped with company B's OS makes a payment request to the corresponding store server (store server 20 for company A's OS or store server 30 for company B's OS) (A-1).

Next, the store server that received the payment request (store server 20 for company A's OS or store server 30 for company B's OS) issues a receipt for the purchase of the billing item 42a, and sends the receipt to A, who made the payment request. The information is sent to the terminal device 10A equipped with Company OS or the terminal device 10B equipped with Company B OS (A-2).

Next, the A-company OS-equipped terminal device 10A or the B-company OS-equipped terminal device 10B that received the receipt transfers the receipt and the login ID of the user who has logged in to the mobile application 12a from the own device to the cloud server 40. (A-3).

Next, the cloud server 40 transfers the transferred receipt and login ID to the billing management server 50 (A-4).

Next, upon receiving the receipt and the login ID, the billing management server 50 verifies whether the receipt is a valid receipt or not using the corresponding store server (store server 20 for company A's OS or store server for company B's OS). server 30) (A-5).

Next, the store server verifies the receipt based on the receipt verification request from the billing management server 50, and transmits the verification result to the billing management server 50 (A-6).

Next, the billing management server 50 reports the received verification result to the cloud server 40 (A-7). Also, here, the billing management server 50 updates (manages) the information (billing status) in the billing management DB 52a based on the received verification result.

Next, the cloud server 40 that has received the report of the verification result sets whether or not the charge item 42a can be used based on the content of the report (whether or not it is a valid receipt) (A-8).

Further, when the purchase process for the billing item 42a is performed on a predetermined website, the terminal device 10A equipped with company A's OS or the terminal device 10B equipped with company B's OS makes a payment request to the original server 60 (B-1). .

Next, the original server 60 that received the payment request transfers the purchase information (receipt) when the purchase process was performed to the cloud server 40 (B-2).

Next, the cloud server 40 that has received the purchase information transmits to the billing management server 50 the login ID used when the user who has performed the procedure for purchasing the billing item 42a logs into the predetermined website, along with the purchase information. (B-3).

Next, upon receiving the purchase information and the login ID, the billing management server 50 requests the original server 60 to verify whether the purchase information is valid purchase information (B-4).

Next, the original server 60 verifies the purchase information based on the purchase information verification request from the billing management server 50, and transmits the verification result to the billing management server 50 (B-5).

Next, the billing management server 50 reports the received verification result to the cloud server 40 (B-6). Also, here, the billing management server 50 updates (manages) the information (billing status) in the billing management DB 52a based on the received verification result.

Next, the cloud server 40 that has received the report of the verification result sets whether or not the charge item 42a can be used based on the content of the report (whether or not it is legitimate purchase information) (B-7).

As described above, the in-app billing system 1 of the present embodiment allows users to use a predetermined login ID (login user ID) via the mobile application 12a running on the OS of company A (first OS), for example. When a charge is made, the receipt associated with the login ID and issued from the store server 20 for company A's OS that is compatible with company A's OS to the mobile application 12a is sent to the mobile application. 12a at a predetermined timing, and manage the billing status of the login ID based on the receipt acquired from the mobile app 12a, and manage the functions of the mobile app 12a with the login ID in accordance with the managed billing status. When the usage permission range is set and the user logs into the mobile application 12a running on Company B's OS (second OS) whose corresponding store server is different from Company A's OS using the above-mentioned predetermined login ID, The login ID is allowed to use the functions of the mobile application 12a running on Company B's OS within the same scope as the usage permission set for the functions of the mobile application 12a running on Company A's OS. To give permission.
Therefore, according to the in-app billing system 1 of the present embodiment, when a user logs in with a predetermined login ID to the mobile application 12a running on the OS of company B whose corresponding store server is different from the OS of company A, The use of the functions of the mobile application 12a running on Company B's OS with the login ID is within the same scope as the usage permission range set for the functions of the mobile application 12a running on Company A's OS. This allows users to be granted more appropriate usage rights depending on their billing status.

Further, according to the in-app billing system 1 of the present embodiment, for example, a predetermined login to the mobile application 12a running on a predetermined website whose corresponding store server is different from the OS of company A (first OS) is performed. When logged in with an ID, the use of the functions of the mobile application 12a that runs on a predetermined website with the login ID is set to target the functions of the mobile application 12a that runs on Company A's OS. Since the usage permission range is the same as the usage permission range given above, it is possible to grant more appropriate usage authority to the user depending on the billing status.

Further, the in-app billing system 1 of the present embodiment is a receipt that is issued in association with a predetermined login ID when a charge is made using a predetermined login ID via the mobile application 12a running on the OS. , a receipt issued to the mobile application 12a from a store server compatible with the above OS is obtained from the mobile application 12a at a predetermined timing, and the billing status by the login ID is determined based on the receipt obtained from the mobile application 12a. and set the usage permission range of a predetermined function with a login ID in accordance with the managed billing situation, and when a user logs into the mobile application 12a with a predetermined login ID, The functions of the mobile application 12a are permitted to be used within the set usage permission range. In addition, the in-app billing system 1 centrally manages billing status for each login ID, regardless of the store server that issues the receipt, and allows the mobile app 12a to control the scope of use of the above functions for each login ID. Set commonly regardless of the operating OS.
Therefore, according to the in-app billing system 1 of the present embodiment, when a user purchases the billing item 42a that is compatible with one OS, the user can then purchase a terminal device that is compatible with any OS (installed with the OS of company A). This billing item 42a can be used even when logging in to the mobile application 12a via the terminal device 10A or the terminal device 10B equipped with company B's OS. User rights can be granted.

Although the present invention has been specifically explained based on the embodiments above, the present invention is not limited to the above embodiments, and can be modified without departing from the gist thereof.
For example, in the above embodiment, the in-app billing system 1 is divided into the cloud server 40 and the billing management server 50 from a security perspective, but the cloud server 40 and the billing management server 50 may be integrated as one server. .

Further, in the embodiment described above, the charging method for the charging item 42a may be any method such as package sales, monthly charging, pay-as-you-go charging, or the like. Note that in the case where the billing method of the billing item 42a is monthly billing, for example, when one user misses the payment deadline for the billing item 42a, the control unit 51 of the billing management server 50 performs the above-mentioned The "billing status" information corresponding to each vendor in the "vendor" item of the data table (see FIG. 5(b)) is updated from the purchased status to the unpurchased status. Further, the control unit 51 sets a grace period when the payment deadline for the billing item 42a has passed, and if payment is not made during this grace period, the “Vendor” item in the data table is The "billing status" information corresponding to each vendor may be updated from the purchased status to the unpurchased status.

Further, in the embodiments described above, an example is disclosed in which a nonvolatile semiconductor memory or the like is used as a computer-readable medium for the program according to the present invention, but the present invention is not limited to this example. As other computer-readable media, it is possible to apply a portable recording medium such as a CD-ROM. Further, a carrier wave is also applied as a medium for providing data of the program according to the present invention via a communication line.

Although the embodiments of the present invention have been described, the scope of the present invention is not limited to the above-described embodiments, but includes the scope of the invention described in the claims and equivalent ranges thereof.
Below, the invention described in the claims first attached to the application of this application will be added. The claim numbers listed in the supplementary notes are as in the claims originally attached to the request for this application.
[Additional note]
<Claim 1>
A receipt that is issued in association with a predetermined login user ID when a charge is made with a predetermined login user ID via a first application running on a first OS; acquisition means for acquiring a receipt issued from a corresponding store server to the first application from the first application at a predetermined timing;
a management unit that manages billing status by the login user ID based on the receipt acquired by the acquisition unit from the first application;
a setting means for setting a usage permission range of functions of the first application for the login user ID in accordance with a billing situation managed by the management means;
The login user ID is used to log into an application that is an application that operates on a second OS whose corresponding store server is different from the first OS and is registered in advance as a second application corresponding to the first application. When logged in, the login user ID is allowed to use the functions of the second application within the same usage permission range set for the functions of the first application by the setting means. a means of authorization; and
A management system characterized by:
<Claim 2>
The permission means is an application that operates on a predetermined website whose corresponding store server is different from that of the first OS, and which is registered in advance as a third application corresponding to the first application. When the user logs in with the login user ID, the user is allowed to use the functions of the third application with the login user ID in a usage permission range set by the setting means for the functions of the first application. permitted to the same extent as
The management system according to claim 1, characterized in that:
<Claim 3>
A receipt that is issued in association with a predetermined login user ID when a charge is made with a predetermined login user ID via a first application running on a first OS; acquisition means for acquiring a receipt issued from a corresponding store server to the first application from the first application at a predetermined timing;
a management unit that manages billing status by the login user ID based on the receipt acquired by the acquisition unit from the first application;
a setting means for setting a usage restriction range of functions of the first application for the login user ID in accordance with a billing situation managed by the management means;
The login user ID is used to log into an application that is an application that operates on a second OS whose corresponding store server is different from the first OS and is registered in advance as a second application corresponding to the first application. When logged in, the use of the functions of the second application by the login user ID is restricted to the same range as the usage restriction range set for the functions of the first application by the setting means. a restricting means for restricting;
A management system characterized by:
<Claim 4>
The restriction means is an application that is registered in advance as a third application corresponding to the first application and that is an application that operates on a predetermined website whose corresponding store server is different from that of the first OS. When the user logs in with the login user ID, the use of the function of the third application with the login user ID is limited to a usage restriction range set by the setting means for the function of the first application. limit within the same range as
The management system according to claim 3, characterized in that:
<Claim 5>
A receipt that is issued in association with the login user ID when a charge is made with a predetermined login user ID via an application running on the OS, and is sent from a store server compatible with the OS to the application. an acquisition means for acquiring an issued receipt from the application at a predetermined timing;
a management unit that manages billing status by the login user ID based on the receipt acquired by the acquisition unit from the application;
a setting means for setting a usage permission range of a predetermined function for the login user ID in accordance with the billing situation managed by the management means;
a permission means that, when the application is logged in with the login user ID, allows the use of the function of the application with the login user ID within a usage permission range set by the setting means;
Equipped with
The management means centrally manages the billing status for each login user ID regardless of the difference in the store server as the issuer of the receipt,
The setting means commonly sets a usage permission range of the function for the login user ID regardless of the difference in the OS on which the application runs.
A management system characterized by:
<Claim 6>
A receipt that is issued in association with the login user ID when a charge is made with a predetermined login user ID via an application running on the OS, and is sent from a store server compatible with the OS to the application. an acquisition means for acquiring an issued receipt from the application at a predetermined timing;
a management unit that manages billing status by the login user ID based on the receipt acquired by the acquisition unit from the application;
a setting means for setting a usage restriction range of a predetermined function for the login user ID in accordance with the billing situation managed by the management means;
Restricting means for restricting the use of the function of the application by the login user ID within a usage restriction range set by the setting means when the login user ID logs into the application;
Equipped with
The management means centrally manages the billing status for each login user ID regardless of the difference in the store server as the issuer of the receipt,
The setting means commonly sets a usage permission range of the function for the login user ID regardless of the difference in the OS on which the application runs.
A management system characterized by:
<Claim 7>
management system computer,
A receipt that is issued in association with a predetermined login user ID when a charge is made with a predetermined login user ID via a first application running on a first OS; acquisition means for acquiring a receipt issued from a corresponding store server to the first application from the first application at a predetermined timing;
management means for managing billing status by the login user ID based on the receipt acquired by the acquisition means from the first application;
a setting means for setting a usage permission range of the functions of the first application for the login user ID in accordance with the billing situation managed by the management means;
The login user ID is used to log into an application that is an application that operates on a second OS whose corresponding store server is different from the first OS and is registered in advance as a second application corresponding to the first application. When logged in, the login user ID is allowed to use the functions of the second application within the same usage permission range set for the functions of the first application by the setting means. authorization means to authorize;
A program characterized by functioning as
<Claim 8>
management system computer,
A receipt that is issued in association with a predetermined login user ID when a charge is made with a predetermined login user ID via a first application running on a first OS; acquisition means for acquiring a receipt issued from a corresponding store server to the first application from the first application at a predetermined timing;
management means for managing billing status by the login user ID based on the receipt acquired by the acquisition means from the first application;
a setting means for setting a usage restriction range of functions of the first application for the login user ID in accordance with the billing situation managed by the management means;
The login user ID is used to log into an application that is an application that operates on a second OS whose corresponding store server is different from the first OS and is registered in advance as a second application corresponding to the first application. When logged in, the use of the functions of the second application by the login user ID is restricted to the same range as the usage restriction range set for the functions of the first application by the setting means. restrictive means of restricting;
A program characterized by functioning as
<Claim 9>
management system computer,
A receipt that is issued in association with the login user ID when a charge is made with a predetermined login user ID via an application running on the OS, and is sent from a store server compatible with the OS to the application. acquisition means for acquiring issued receipts from the application at a predetermined timing;
management means for managing billing status by the login user ID based on the receipt acquired by the acquisition means from the application;
a setting means for setting a usage permission range of a predetermined function for the login user ID in accordance with the billing situation managed by the management means;
permission means for permitting use of the function of the application with the login user ID within a usage permission range set by the setting means when the user logs into the application with the login user ID;
function as
The management means centrally manages the billing status for each login user ID regardless of the difference in the store server as the issuer of the receipt,
The setting means commonly sets a usage permission range of the function for the login user ID regardless of the difference in the OS on which the application runs.
A program characterized by:
<Claim 10>
management system computer,
A receipt that is issued in association with the login user ID when a charge is made with a predetermined login user ID via an application running on the OS, and is sent from a store server compatible with the OS to the application. acquisition means for acquiring issued receipts from the application at a predetermined timing;
management means for managing billing status by the login user ID based on the receipt acquired by the acquisition means from the application;
a setting means for setting a usage restriction range of a predetermined function for the login user ID in accordance with the billing situation managed by the management means;
Restricting means for restricting the use of the functions of the application with the login user ID within a usage restriction range set by the setting means when the user logs into the application with the login user ID;
function as
The management means centrally manages the billing status for each login user ID regardless of the difference in the store server as the issuer of the receipt,
The setting means commonly sets a usage permission range of the function for the login user ID regardless of the difference in the OS on which the application runs.
A program characterized by:

1 In-app billing system (management system)
10A Terminal device with company A's OS 10B Terminal device with company B's OS 12a Mobile application 20 Store server for company A's OS 30 Store server for company B's OS 40 Cloud server (acquisition means, setting means, permission means)
41 Control unit 42a Billing item 50 Billing management server (management means)
51 Control unit 60 Original server

Claims (10)

A receipt that is issued in association with a predetermined login user ID when a charge is made with a predetermined login user ID via a first application running on a first OS; acquisition means for acquiring a receipt issued from a corresponding store server to the first application from the first application at a predetermined timing;
a management unit that manages billing status by the login user ID based on the receipt acquired by the acquisition unit from the first application;
a setting means for setting a usage permission range of functions of the first application for the login user ID in accordance with a billing situation managed by the management means;
The login user ID is used to log into an application that is an application that operates on a second OS whose corresponding store server is different from the first OS and is registered in advance as a second application corresponding to the first application. When logged in, the login user ID is allowed to use the functions of the second application within the same usage permission range set for the functions of the first application by the setting means. a means of authorization; and
A management system characterized by: The permission means is an application that operates on a predetermined website whose corresponding store server is different from that of the first OS, and which is registered in advance as a third application corresponding to the first application. When the user logs in with the login user ID, the user is allowed to use the functions of the third application with the login user ID in a usage permission range set by the setting means for the functions of the first application. permitted to the same extent as
The management system according to claim 1, characterized in that: A receipt that is issued in association with a predetermined login user ID when a charge is made with a predetermined login user ID via a first application running on a first OS; acquisition means for acquiring a receipt issued from a corresponding store server to the first application from the first application at a predetermined timing;
a management unit that manages billing status by the login user ID based on the receipt acquired by the acquisition unit from the first application;
a setting means for setting a usage restriction range of functions of the first application for the login user ID in accordance with a billing situation managed by the management means;
The login user ID is used to log into an application that is an application that operates on a second OS whose corresponding store server is different from the first OS and is registered in advance as a second application corresponding to the first application. When logged in, the use of the functions of the second application by the login user ID is restricted to the same range as the usage restriction range set for the functions of the first application by the setting means. a restricting means for restricting;
A management system characterized by: The restriction means is an application that is registered in advance as a third application corresponding to the first application and that is an application that operates on a predetermined website whose corresponding store server is different from that of the first OS. When the user logs in with the login user ID, the use of the function of the third application with the login user ID is limited to a usage restriction range set by the setting means for the function of the first application. limit within the same range as
The management system according to claim 3, characterized in that: A receipt that is issued in association with the login user ID when a charge is made with a predetermined login user ID via an application running on the OS, and is sent from a store server compatible with the OS to the application. an acquisition means for acquiring an issued receipt from the application at a predetermined timing;
a management unit that manages billing status by the login user ID based on the receipt acquired by the acquisition unit from the application;
a setting means for setting a usage permission range of a predetermined function for the login user ID in accordance with the billing situation managed by the management means;
a permission means that, when the application is logged in with the login user ID, allows the use of the function of the application with the login user ID within a usage permission range set by the setting means;
Equipped with
The management means centrally manages the billing status for each login user ID regardless of the difference in the store server as the issuer of the receipt,
The setting means commonly sets a usage permission range of the function for the login user ID regardless of the difference in the OS on which the application runs.
A management system characterized by: A receipt that is issued in association with the login user ID when a charge is made with a predetermined login user ID via an application running on the OS, and is sent from a store server compatible with the OS to the application. an acquisition means for acquiring an issued receipt from the application at a predetermined timing;
a management unit that manages billing status by the login user ID based on the receipt acquired by the acquisition unit from the application;
a setting means for setting a usage restriction range of a predetermined function for the login user ID in accordance with the billing situation managed by the management means;
Restricting means for restricting the use of the function of the application by the login user ID within a usage restriction range set by the setting means when the login user ID logs into the application;
Equipped with
The management means centrally manages the billing status for each login user ID regardless of the difference in the store server as the issuer of the receipt,
The setting means commonly sets a usage permission range of the function for the login user ID regardless of the difference in the OS on which the application runs.
A management system characterized by: management system computer,
A receipt that is issued in association with a predetermined login user ID when a charge is made with a predetermined login user ID via a first application running on a first OS; acquisition means for acquiring a receipt issued from a corresponding store server to the first application from the first application at a predetermined timing;
management means for managing billing status by the login user ID based on the receipt acquired by the acquisition means from the first application;
a setting means for setting a usage permission range of the functions of the first application for the login user ID in accordance with the billing situation managed by the management means;
The login user ID is used to log into an application that is an application that operates on a second OS whose corresponding store server is different from the first OS and is registered in advance as a second application corresponding to the first application. When logged in, the login user ID is allowed to use the functions of the second application within the same usage permission range set for the functions of the first application by the setting means. authorization means to authorize;
A program characterized by functioning as management system computer,
A receipt that is issued in association with a predetermined login user ID when a charge is made with a predetermined login user ID via a first application running on a first OS; acquisition means for acquiring a receipt issued from a corresponding store server to the first application from the first application at a predetermined timing;
management means for managing billing status by the login user ID based on the receipt acquired by the acquisition means from the first application;
a setting means for setting a usage restriction range of functions of the first application for the login user ID in accordance with the billing situation managed by the management means;
The login user ID is used to log into an application that is an application that operates on a second OS whose corresponding store server is different from the first OS and is registered in advance as a second application corresponding to the first application. When logged in, the use of the functions of the second application by the login user ID is restricted to the same range as the usage restriction range set for the functions of the first application by the setting means. restrictive means of restricting;
A program characterized by functioning as management system computer,
A receipt that is issued in association with the login user ID when a charge is made with a predetermined login user ID via an application running on the OS, and is sent from a store server compatible with the OS to the application. acquisition means for acquiring issued receipts from the application at a predetermined timing;
management means for managing billing status by the login user ID based on the receipt acquired by the acquisition means from the application;
a setting means for setting a usage permission range of a predetermined function for the login user ID in accordance with the billing situation managed by the management means;
permission means for permitting use of the function of the application with the login user ID within a usage permission range set by the setting means when the user logs into the application with the login user ID;
function as
The management means centrally manages the billing status for each login user ID regardless of the difference in the store server as the issuer of the receipt,
The setting means commonly sets a usage permission range of the function for the login user ID regardless of the difference in the OS on which the application runs.
A program characterized by: management system computer,
A receipt that is issued in association with the login user ID when a charge is made with a predetermined login user ID via an application running on the OS, and is sent from a store server compatible with the OS to the application. acquisition means for acquiring issued receipts from the application at a predetermined timing;
management means for managing billing status by the login user ID based on the receipt acquired by the acquisition means from the application;
a setting means for setting a usage restriction range of a predetermined function for the login user ID in accordance with the billing situation managed by the management means;
Restricting means for restricting the use of the functions of the application with the login user ID within a usage restriction range set by the setting means when the user logs into the application with the login user ID;
function as
The management means centrally manages the billing status for each login user ID regardless of the difference in the store server as the issuer of the receipt,
The setting means commonly sets a usage permission range of the function for the login user ID regardless of the difference in the OS on which the application runs.
A program characterized by:

Images