JP6275895B2 - Management system, management server, management method and program - Google Patents

Description

  The present invention relates to a management system, a management server, a management method, and a program.

  In recent years, an increasing number of users use prepaid cards when purchasing goods and services. A prepaid card is a card that can be used in place of cash when purchasing goods or services at a store (including a purchase site on the Internet) by paying in advance for purchase.

  With the spread of prepaid cards, for example, opportunities to manage usage histories and balances on mobile devices are increasing. Providing useful information to users on mobile devices is important in promoting sales of products and services. It has come to assume a role (for example, refer to the following Patent Document 1).

JP 2003-331179 A

  On the other hand, conventionally, there is no big difference in the prepaid card itself sold by each prepaid card seller, and there is no big difference for a user when purchasing a prepaid card from any prepaid card seller. The same applies to management tools for managing information on usage status such as prepaid card usage histories and balances, and there is a problem that all management tools lack interest.

  On the other hand, for example, if there is a difference in interest when providing information on usage status such as usage history and balance depending on which prepaid card is purchased, it will lead to sales promotion for a specific prepaid card Expected. Furthermore, if there is a difference in interest depending on how much the purchased prepaid card is used, it is considered that the use of the prepaid card can be promoted, and sales of goods and services can be promoted.

  The present invention has been made in view of the above problems, and an object of the present invention is to improve the interest of a user in providing information related to the use status of a prepaid card.

The management server according to an embodiment of the present invention has the following configuration. That is,
A management server that manages data output via a user's terminal when an application is executed,
In response to a request from the application installed on the terminal of the user carrying the available cards when purchasing goods or services, a user identifier identifying the user and registered in association with the card registration Means,
And a transmission unit that transmits data associated with the card and output via the user's terminal when registered by the registration unit to the user's terminal.

  According to each embodiment of the present invention, it is possible to improve the interest of a user when providing information related to the usage status of a prepaid card.

It is a figure which shows the whole structure of a management system. It is a figure which shows the hardware constitutions of each server which comprises a management system. It is a figure which shows the hardware constitutions of each terminal which comprises a management system. It is a figure which shows an example of prepaid card management information. It is a figure which shows an example of skin management information. It is a figure which shows an example of the list information of acquisition skin. It is a figure which shows the function structure of a management server. It is a flowchart which shows the flow of a user registration process. It is a flowchart which shows the flow of a prepaid card information management process. It is a flowchart which shows the flow of a skin ID specific process. It is a flowchart which shows the flow of a terminal management process. It is a figure which shows the function structure of a portable terminal. It is a flowchart which shows the flow of a use state management process. It is a figure which shows an example of the display screen of a portable terminal. It is a figure which shows an example of the display screen of a portable terminal. It is a figure which shows an example of the display screen of a portable terminal. It is a sequence diagram which shows the flow of a process of the whole management system. It is a figure which shows the function structure of a management server. It is a figure which shows the provision timing of an advertisement. It is a flowchart which shows the flow of an advertisement display process. It is a figure which shows an example of the display screen of a portable terminal.

  Hereinafter, details of each embodiment of the present invention will be described with reference to the accompanying drawings. In the description of the specification and drawings according to each embodiment, components having substantially the same functional configuration are denoted by the same reference numerals, and redundant description is omitted.

[First Embodiment]
<1. Overall configuration of management system>
First, the overall configuration of the management system will be described. FIG. 1 is a diagram illustrating an overall configuration of a management system 100 according to the first embodiment. As shown in FIG. 1, the management system 100 includes a management server 110, a content providing server 120, a mobile terminal 130 such as a smartphone, and an information terminal 140 such as a notebook personal computer. In the management system 100, each server (management server 110, content providing server 120) and each terminal (mobile terminal 130, information terminal 140) are communicably connected via the Internet 150.

  The management server 110 is assumed to be owned by a prepaid card management company that issues and manages prepaid cards. Further, the content providing server 120 is owned by a content provider (provider) having ownership of all contents including image designs such as characters and fashion brands (image data, video data, music data, text data, etc.). Shall. Furthermore, it is assumed that the information terminal 140 is installed in a member store where a prepaid card can be used.

  The management server 110 includes a card management program 111, a terminal management program 112, a prepaid card management information database (hereinafter simply referred to as DB) 113, and a skin management DB 114.

  The card management program 111 manages the usage history by recording the usage information of the prepaid card 170 by the user 160 who purchased the prepaid card 170 in the prepaid card management information. In the present embodiment, it is assumed that the prepaid card 170 purchased by the user 160 has drawn contents including a design of a character, a fashion brand, etc. (in the example of FIG. 1, a star heptagon design). .

  The terminal management program 112 transmits the usage history of the prepaid card 170 to the mobile terminal 130 of the user 160 when the user 160 registers the purchased prepaid card 170 in the management server 110. Further, the usage history of the prepaid card 170 by the user 160 is totaled, and a skin corresponding to the totaling result is transmitted to the mobile terminal 130. A skin refers to a group of files that store information relating to the appearance of the application program, and refers to a group of files for changing the background, display color, font, and the like of the application program to specifications that are easy to use. In the present embodiment, the skin transmitted to the mobile terminal 130 is a character or fashion brand design (such as a star heptagon in the example of FIG. 1) included in the drawn content drawn on the prepaid card 170 purchased by the user 160. Design) skin. Note that the design included in the drawing content drawn on the prepaid card 170 and the similar design included in the skin are both based on the content provided by the content provider. In this embodiment, the skin is generated by a prepaid card manager.

  The prepaid card management information DB 113 stores prepaid card management information in which a prepaid card usage history is recorded for each user. The prepaid card management information of the prepaid card 170 purchased by the user 160 is stored in the prepaid card management information DB 113 in association with the user ID (user identifier) of the user 160.

  The skin management DB 114 stores skins transmitted to the mobile terminal 130 of the user 160. The transmitted skin is applied when the usage state management application 131 for browsing the usage history of the prepaid card 170 is executed on the mobile terminal 130 of the user 160. Note that the skin stored in the skin management DB 114 is generated and stored by the prepaid card management company based on the content provided by the content provider. Further, the skin management DB 114 defines the association between the stored skin and the prepaid card, and the skin management information for defining the conditions (conditions for the prepaid card usage history count result) for each skin to be usable. Store.

  The content providing server 120 includes a content management program 121 and a content DB 122. The content management program 121 manages the entire content that is the basis of the design of characters and fashion brands drawn on the prepaid card 170 and the same design included in the skin. The content management program 121 provides the content when the content provider contracts with the prepaid card management provider to grant the right to use the content in exchange for payment of the content usage fee. The content DB 122 stores content held by content providers and content list information.

  The mobile terminal 130 includes a usage state management application 131 and an acquisition skin DB 132. The usage state management application 131 accesses the management server 110 to acquire the usage history of the prepaid card 170 and displays it on the mobile terminal 130. Also, the skin that can be used in accordance with the result of counting the usage history of the prepaid card 170 is acquired from the management server 110.

  As a result, a skin including the design included in the drawing content drawn on the prepaid card 170 is set in the use state management application 131. As a result, the same design as the drawing content of the prepaid card 170 is displayed on the display screen when the usage state management application 131 is executed. In other words, since the user can purchase a favorite prepaid card to make the display screen of the usage status management application 131 a desired design, it is interesting to view information on usage status such as usage history and balance. Increases nature.

  The acquired skin DB 132 stores a plurality of skins acquired by the usage state management application 131 from the management server 110 and list information of acquired skins. Of the plurality of skins stored in the acquired skin DB 132, the user 160 can arbitrarily set which skin is to be applied when the usage state management application 131 is executed.

  The information terminal 140 is installed in a member store, and a card reader 141 that reads information on the prepaid card 170 when the user 160 purchases a product using the prepaid card 170 or receives a service at the member store. It is connected.

  The information terminal 140 transmits the information of the prepaid card 170 read by the card reader 141 to the management server 110 as usage information together with the usage fee and the store ID of the member store.

<2. Hardware configuration of each server>
Next, the hardware configuration of each server (management server 110 and content providing server 120) will be described. FIG. 2 is a diagram illustrating a hardware configuration of each server.

  As shown in FIG. 2, each server includes a CPU (Central Processing Unit) 201, a ROM (Read Only Memory) 202, a RAM (Random Access Memory) 203, and a storage unit 204. Each server further includes an input unit 205 and a communication unit 206. Each part of each server is connected to each other via a bus 207.

  The CPU 201 is a computer that executes various programs (the card management program 111, the terminal management program 112, the content management program 121, etc.) stored in the storage unit 204.

  The ROM 202 is a nonvolatile memory. The ROM 202 stores various programs, data, and the like necessary for the CPU 201 to execute various programs stored in the storage unit 204. Specifically, a boot program such as BIOS (Basic Input / Output System) or EFI (Extensible Firmware Interface) is stored.

  The RAM 203 is a main storage device such as a DRAM (Dynamic Random Access Memory) or an SRAM (Static Random Access Memory). The RAM 203 functions as a work area that is expanded when various programs stored in the storage unit 204 are executed by the CPU 201.

  The storage unit 204 stores various programs executed by the CPU 201 and various information used when the various programs are executed by the CPU 201. In the case of the management server 110, the various information stored in the storage unit 204 includes prepaid card management information, skins, skin management information, and the like. In the case of the content providing server 120, content, content list information, and the like are included.

  The input unit 205 is used when an administrator of each server inputs various instructions to each server. The communication unit 206 communicates with another server or each terminal (the mobile terminal 130 and the information terminal 140) via the Internet 150.

<3. Hardware configuration of each terminal>
Next, the hardware configuration of each terminal (mobile terminal 130, information terminal 140) will be described. FIG. 3 is a diagram illustrating a hardware configuration of each terminal constituting the management system 100.

  As illustrated in FIG. 3, each terminal includes a CPU 301, a ROM 302, a RAM 303, and a storage unit 304. Each terminal further includes an input unit 305, a display unit 306, and a communication unit 307. Each unit of each terminal is connected to each other via a bus 308.

  The CPU 301 is a computer that executes various programs (for example, the usage state management application 131) stored in the storage unit 304. The ROM 302 is a nonvolatile memory. The ROM 302 stores various programs and data necessary for the CPU 301 to execute various programs stored in the storage unit 304. Specifically, a boot program such as BIOS or EFI is stored.

  The RAM 303 is a main storage device such as DRAM or SRAM. The RAM 303 functions as a work area that is expanded when various programs stored in the storage unit 304 are executed by the CPU 301.

  The storage unit 304 stores various programs executed by the CPU 301 and various information (for example, skin, acquired skin list information, and the like) used when the various programs are executed by the CPU 301.

  The input unit 305 is used when a user of each terminal inputs various instructions to each terminal. Further, the display unit 306 displays various display screens acquired by each terminal accessing the management server 110 via the Internet 150, for example. The communication unit 307 communicates with the management server 110 via the Internet 150.

<4. Explanation of information stored in each DB>
Next, information stored in the DB (prepaid card management information DB 113, skin management DB 114, content DB 122, acquired skin DB 132) of each server and each terminal will be described. Specifically, among the information stored in the DB of each server and each terminal, details of prepaid card management information, skin management information, and acquired skin list information will be described.

(1) Prepaid Card Management Information First, the prepaid card management information 400 stored in the prepaid card management information DB 113 of the management server 110 will be described. FIG. 4 is a diagram showing an example of prepaid card management information 400.

  As shown in FIG. 4, the prepaid card management information 400 is managed separately for each prepaid card ID, and each prepaid card management information (in the example of FIG. 4, 400_1, 400_2...) Corresponds to a user ID. It is attached. For example, the prepaid card management information 400_1 records registration information, usage history, count results, and the like of the prepaid card 170 purchased by the user 160. In FIG. 4, the hatched portion is information already recorded in the prepaid card management information when the prepaid card is issued. In the example of FIG. 4, “C000001” (prepaid card ID of the prepaid card 170) and “UID-X” (user ID of the user 160) are registered as the prepaid card management information 400_1 (prepaid card ID, user ID). ) And are registered.

  Further, the prepaid card management information 400 includes “remaining money”, “action”, “usage fee or charge amount”, “date and time”, and “store (store ID)” as usage history items. Furthermore, the items of the usage history tabulation results include “cumulative usage fee”, “cumulative usage count”, “charge count”, “point count”, “skin ID”, “transmission information”, and the like. Hereinafter, details of each item will be described in the case of the prepaid card management information 400_1.

  In “Remaining amount”, the remaining amount of the prepaid card 170 is recorded. In the case of the prepaid card 170, since the user 160 has purchased for 3000 yen, “¥ 3000” is recorded in the balance before use.

  In “Action”, an action of the user 160 having the prepaid card 170 is recorded. “Purchase” is recorded in the first line of “Action”, and “Used” is recorded in the second and subsequent lines when the prepaid card 170 is used. When the prepaid card 170 is charged, “charge” is recorded.

  In “Usage Charge or Charge Amount”, an increase or decrease in the amount accompanying each action is recorded with a positive or negative sign. “+ ¥ 3000” is recorded in the first line of “Usage fee or charge amount”. From the second line onward, the usage fee is charged with a negative sign if the prepaid card 170 is used. Is recorded. On the other hand, when the prepaid card 170 is charged, the charge amount is recorded together with a positive sign.

  In “Date and time”, the date and time when each action was performed is recorded. In “Store (Store ID)”, a store name and a store ID where each action is performed are recorded. For example, in the example of FIG. 4, the prepaid card 170 is purchased at the Tokyo Shinjuku store (store ID = S001) and used or charged at the store. It is also used in Tokyo Shibuya store (store ID = S011) and Hokkaido store (store ID = S030).

  In the “cumulative usage fee”, a cumulative value of the usage fee for the user 160 using the prepaid card 170 is recorded. The accumulated usage fee is derived by adding the usage fee (amount with a negative sign) recorded in the “use fee or charge amount”. In the example of FIG. 4, as of April 2, 2014, the cumulative usage fee for the user 160 is “¥ 2850”. When “Action” is “Charge”, the corresponding “cumulative usage fee” records the cumulative usage fee at the previous use as it is.

  In “cumulative use count”, the number of times “use” is recorded as “action” is recorded. Each time it is used once, the “total number of times used” is incremented by one. In the case of an “action” other than “use”, “cumulative use count” is not incremented, and the cumulative use count at the previous use is recorded as it is.

  In “Charge Count”, the number of times “Charge” is recorded as “Action” is recorded. Each time the battery is charged once, the “number of charges” is incremented by one. In the case of “action” other than “charge”, “charge count” is not incremented, and the charge count at the previous charge is recorded as it is.

  In “Points”, the number of points to be added when the prepaid card 170 can be used at a specific store is recorded. For example, points are added when used at a content provider's store (so-called directly-managed store) having ownership of the entire content including designs such as characters and fashion brands drawn on the prepaid card 170. In the example of FIG. 4, since the Tokyo Shibuya store is a directly managed store of a content provider who has the ownership of the entire content including the design drawn on the prepaid card 170, each time it is used at the Tokyo Shibuya store, 10 points are added to the number.

  “Skin ID” includes a skin ID of a skin corresponding to a totaling result obtained by counting the usage history of the prepaid card 170 among various types of skins including designs drawn on the prepaid card 170. To be recorded. The management server 110 according to the present embodiment is configured such that a new skin can be used by the user 160 every time a totaling result obtained by counting the usage histories of the prepaid card 170 satisfies a predetermined usage condition. For this reason, “skin ID” of a skin that can be used in accordance with the result of counting the usage history of the prepaid card 170 is recorded in the prepaid card management information 400_1.

  In the example of FIG. 4, when the user 160 first purchases the prepaid card 170, a skin with skin ID = “A−001” is selected as a usable skin by the user 160. Therefore, “A-001” is recorded in “Skin ID”. Further, when the “cumulative usage fee” is “¥ 650” and the “cumulative usage count” is “3 times”, a skin whose skin ID = “A-002” can be newly used by the user 160 is available. Selected as. For this reason, “A-002” is recorded in “Skin ID”. Further, when used in the Hokkaido store, the skin with skin ID = “A−101” is selected by the user 160 as a new usable skin. Therefore, “A-101” is recorded in “Skin ID”. Furthermore, when the “cumulative usage amount” is “¥ 2850” and the “point count” is “20” points, the skin with the skin ID = “A-003” is a skin that can be newly used by the user 160. Selected. Therefore, “A-003” is recorded in “Skin ID”.

  In the “transmission information”, information indicating whether or not the usable skin is actually transmitted to the mobile terminal 130 of the user 160 is recorded. In the example of FIG. 4, the skins with skin ID = “A-001”, “A-002”, “A-101” have already been transmitted to the mobile terminal 130, and the skin with skin ID = “A-003” This indicates that it has not been transmitted to the mobile terminal 130 yet.

(2) Skin Management Information Next, the skin management information 500 stored in the skin management DB 114 of the management server 110 will be described. FIG. 5 is a diagram illustrating an example of the skin management information 500.

  As shown in FIG. 5, the skin management information 500 includes “prepaid card ID”, “content ID”, “skin ID”, “rank”, “condition”, and the like as information items.

  “Prepaid card ID” stores all identifiers of prepaid cards that are managed by the management server 110 (that is, issued and managed by a prepaid card manager). In this embodiment, a prepaid card management company issues four types of prepaid cards as prepaid cards on which designs such as characters and fashion brands are drawn. That is, the prepaid card manager contracts with four content providers and draws and issues a design based on the content provided by each content provider on the prepaid card.

  In the example of FIG. 5, a design based on the content of content ID = “AAAAA” is drawn on the prepaid card of prepaid card ID = “C000001 to C000100”. Also, a design based on the content with content ID = “BBBB” is drawn on the prepaid card with prepaid card ID = “C000101 to C000200”. A design based on the content with content ID = “CCCC” is drawn on the prepaid card with prepaid card ID = “C000201 to C000300”. Furthermore, a design based on the content of content ID = “DDDD” is drawn on the prepaid card of prepaid card ID = “C000301 to C000400”.

  In “content ID”, the content ID of the entire content including the design drawn on the prepaid card of each prepaid card ID is recorded.

  The “skin ID” is a skin including a design based on the content specified by the content ID, and a skin ID for specifying various types of skins generated by the prepaid card manager is recorded. For example, there are 21 types of skins that include a design based on the content of content ID = “AAAA”. Similarly, there are 15 types of skins that include designs based on content with content ID = “BBBB”, and there are 50 types of skins that include designs based on content with content ID = “CCCC”. . Furthermore, there are 32 types of skins that include designs based on the content of content ID = “DDDD”.

  Thus, the prepaid card ID and the skin ID are associated in the skin management information 500. In the example of FIG. 5, for convenience of explanation, 7-digit alphanumeric characters are used as the prepaid card ID. However, for example, the prepaid card ID is composed of 16-digit alphanumeric characters and the first 6 digits include a BIN code. In this case, the first 6 digits may be associated with the skin ID.

  In “Rank”, the rank of the skin specified by each skin ID is recorded. The conditions for enabling the user 160 to use the skin specified by each skin ID are set for each skin ID, and each time the condition is satisfied, the skin specified by the corresponding skin ID is used. It becomes possible to do.

  In “Condition”, a condition for enabling use of the skin specified by the skin ID corresponding to each “rank” (a condition for the total result of the prepaid card usage history) is recorded. The “condition” further includes “cumulative usage count”, “cumulative usage fee”, “charge count”, and “point count”. When the total result of these items included in the “condition” exceeds the threshold value, the skin specified by the corresponding skin ID is selected as a usable skin.

For example, in the case of a user 160 holding a prepaid card 170 with a prepaid card ID = “C000001”, the following condition must be satisfied in order for the skin with the skin ID = “A-002” to be usable.
・ Total usage count> th ₂₁
・ Cumulative usage fee> th ₂₂
・ Number of charges> th ₂₃
・ Number of points> th ₂₄
When the above condition is satisfied, it is determined that the total result of the usage history of the prepaid card 170 by the user 160 has reached rank = “2”, and the corresponding skin ID = “A-002” is selected as a usable skin. . Note that the skin of rank = “1” is a skin that can always be used by the user 160 when the prepaid card 170 is purchased, regardless of the result of counting the usage history.

  Further, as shown in FIG. 5, the items included in the “condition” are not limited to items related to the usage history tabulation results. When the prepaid card 170 is used in a specific store, conditions are set so that a specific skin corresponding to the use location can be used. By performing such a condition setting, the user 160 can use a skin including an area-specific design (so-called local character design), for example.

  In the example of FIG. 5, in the case of a prepaid card on which a design based on the content with content ID = “AAAA” is drawn, the skin with skin ID = “A−101” is used in store ID = “S030” (Hokkaido store). Is selected as an available skin. The skin with skin ID = “A−101” is a skin unique to the Hokkaido store.

  As shown in FIG. 5, “conditions” for enabling use are set to different threshold values for each content ID. Furthermore, the number of ranks is different for each content ID, and the number of times the skin changes is different for each content ID.

(3) Obtained Skin List Information Next, the obtained skin list information 600 stored in the obtained skin DB 132 of the mobile terminal 130 will be described. FIG. 6 is a diagram illustrating an example of acquired skin list information 600.

  As shown in FIG. 6, the acquired skin list information 600 includes “user ID”, “prepaid card ID”, “acquired skin ID”, and the like as information items.

  The “user ID” stores a user ID when the user 160 who owns the mobile terminal 130 registers as a user in the management server 110. In the “prepaid card ID”, the prepaid card ID of the prepaid card 170 registered by the user 160 in the management server 110 is stored. In the example of FIG. 6, the prepaid card ID = “C000001” is stored.

  “Acquired skin ID” stores the skin ID of the skin acquired by the user 160 for the prepaid card 170. In the example of FIG. 6, the user 160 has acquired three types of skins of the skin ID = “A-001”, “A-002”, and “A-101” for the prepaid card 170.

<5. Management Server Functional Configuration>
Next, functions realized in the management server 110 when the card management program 111 and the terminal management program 112 are executed by the CPU 201 will be described. FIG. 7 is a diagram illustrating a functional configuration of the management server 110. As illustrated in FIG. 7, the management server 110 includes a card information registration unit 711, a usage state recording unit 712, a usage state determination unit 721, and a skin transmission unit 722.

  The card information registration unit 711 receives a user registration request as a signal including a prepaid card ID (C000001) and a user ID (UID-X) from the user 160 who purchased the prepaid card 170. Also, the prepaid card management information 400_1 corresponding to the prepaid card ID (C000001) extracted from the accepted registration request is read, and the user ID (UID-X) extracted from the accepted registration request is registered in “User ID”. As described above, the card information registration unit 711 associates the user ID of the user who purchased the prepaid card with the prepaid card ID of the prepaid card purchased by the user.

  The usage state recording unit 712 records the user ID, the usage fee, the store ID of the member store, and the like included in the usage information transmitted from the information terminal 140 in the prepaid card management information 400_1. Specifically, the prepaid card management information 400_1 corresponding to the prepaid card ID (C000001) included in the usage information is read, and the usage fee included in the usage information, the store ID of the member store, etc. are read in the read prepaid card management information 400_1. Record.

  The usage state determination unit 721 is executed when the usage history of the prepaid card management information 400_1 is updated by the user 160 taking some action. Specifically, the usage history of the user 160 is totaled using the prepaid card management information 400_1, and the total result is recorded in the prepaid card management information 400_1. Further, by comparing the total result with the skin management information 500, it is determined whether or not a new skin is available. Further, when it is determined that a new skin can be used, the skin ID of the skin is recorded in the prepaid card management information 400_1.

  When the usage state management application 131 is activated on the mobile terminal 130, the skin transmission unit 722 transmits the skin selected as a usable skin to the mobile terminal 130. Specifically, first, it is recognized that the use state management application 131 is activated by receiving a transmission request as a signal for requesting transmission of prepaid card management information from the mobile terminal 130. Then, the prepaid card management information 400_1 of the prepaid card ID (= “C000001”) included in the transmission request is read. Further, it is determined whether or not there is a skin recorded as “not transmitted” in “transmission information” in the prepaid card management information 400_1. If it is determined that there is a skin recorded as “untransmitted” in the “transmission information”, the corresponding skin ID (= “A-003”) is extracted, and the skin specified by the extracted skin ID is transmitted. The request is transmitted to the requesting mobile terminal 130. As a result, the usable skin (skin with skin ID = “A-003”) is transmitted to the user 160.

  When an untransmitted skin is transmitted by the skin transmitting unit 722, the “transmission information” of the prepaid card management information 400_1 is rewritten from “untransmitted” to “transmitted”.

<6. Processing executed by the management server>
Next, various processes (user registration process, prepaid card information management process, skin ID specifying process, terminal management process) executed by the management server 110 will be described.

(1) User Registration Processing First, the flow of user registration processing by the card information registration unit 711 will be described. FIG. 8 is a flowchart showing the flow of user registration processing.

  In step S801, the card information registration unit 711 determines whether or not a user registration request has been received. The user 160 who has purchased the prepaid card 170 activates the usage state management application 131 to perform user registration. When the usage state management application 131 is activated in a state where user registration is not performed, a user registration screen is displayed on the display screen of the mobile terminal 130. Therefore, the user 160 inputs the prepaid card ID (= “C000001”) and the user ID (= “UID-X”) of the purchased prepaid card 170 on the user registration screen, and registers the user in the management server 110. Send a request. Thereby, the management server 110 receives a user registration request.

  If it is determined in step S801 that a user registration request has been received, the process advances to step S802. In step S802, the card information registration unit 711 extracts a prepaid card ID and a user ID included in the registration request.

  In step S803, the card information registration unit 711 reads the prepaid card management information 400_1 corresponding to the extracted prepaid card ID. In step S804, the card information registration unit 711 records the extracted user ID in the “user ID” of the read prepaid card management information 400_1.

  In step S805, the card information registration unit 711 records the date and time when the user's registration request is received in the “date and time” of the read prepaid card management information 400_1. In addition, when the store ID of the store where the user 160 purchased the prepaid card 170 is included in the user registration request, the registration is registered in the “store (store ID)” of the read prepaid card management information 400_1. Record the store ID included in the request.

  When the user registration process by the card information registration unit 711 is completed, the management server 110 transmits the skin (skin ID = “A-001” skin), the balance of the prepaid card management information 400_1, and the like. As a result, the mobile terminal 130 can set the received skin and display the initial screen of the usage state management application 131 to which the set skin is applied.

(2) Prepaid Card Information Management Processing Next, the flow of prepaid card information management processing by the usage status recording unit 712 and the usage status determination unit 721 will be described. FIG. 9 is a flowchart showing the flow of prepaid card information management processing.

  In step S901, the usage status recording unit 712 determines whether or not the user using the prepaid card has taken any action. Specifically, it is determined whether usage information has been received from a member store that can use a prepaid card. Alternatively, it is determined whether or not the prepaid card charge information has been received.

  If it is determined that neither the prepaid card usage information nor the charge information has been received, it is determined that there is no action by the user 160 and the apparatus waits until there is an action. On the other hand, if it is determined that either the prepaid card usage information or the charge information is received, it is determined that there is an action by the user 160, and the process proceeds to step S902.

  In step S902, the usage status recording unit 712 extracts a prepaid card ID (= “C000001”) included in usage information or charge information. In step S903, the prepaid card management information 400_1 corresponding to the extracted prepaid card ID is read.

  In step S904, the usage state recording unit 712 determines the content of the action. If the information received in step S901 is usage information, it is determined that “action” = “use”, and the process proceeds to step S905. On the other hand, if the information received in step S901 is charge information, it is determined that “action” = “charge”, and the process proceeds to step S910.

  In step S905, the usage state recording unit 712 records the usage fee, the date and time, and the store ID of the used store included in the usage information in the prepaid card management information 400_1.

  In step S906, the usage state determination unit 721 calculates the balance after the usage fee is newly recorded in step S905, and records the calculation result in the prepaid card management information 400_1.

  In step S907, the usage state determination unit 721 totals the accumulated usage fee after the usage fee and the like are newly recorded in step S905, and records the aggregation result in the prepaid card management information 400_1.

  In step S908, the usage status determination unit 721 increments the cumulative usage count and records it in the prepaid card management information 400_1. Furthermore, in step S909, the use state determination unit 721 determines whether or not the store ID extracted in step S905 is a store to which points are added. Specifically, by referring to the skin management information 500, it is determined whether or not the store is a point addition target. As a result of the determination, if it is determined that the store is the target of point addition, a predetermined number of points is added and recorded in the prepaid card management information.

  On the other hand, in step S910, the usage state determination unit 721 records the charge amount, date and time, and the store ID of the charged store included in the charge information in the prepaid card management information 400_1.

  In step S911, the use state determination unit 721 calculates the balance after the charge amount or the like is newly recorded in step S910, and records the calculation result in the prepaid card management information 400_1.

  In step S912, the use state determination unit 721 executes a skin ID specifying process. Details of the skin ID specifying process will be described later with reference to FIG. When the skin ID specifying process in step S912 is completed, the prepaid card information management process for the current action is terminated.

(3) Skin ID Specifying Process Next, details of the skin ID specifying process (step S912) by the use state determining unit 721 will be described. FIG. 10 is a flowchart showing the flow of the skin ID specifying process by the use state determining unit 721.

  In step S <b> 1001, the use state determination unit 721 reads the condition corresponding to the prepaid card ID (= “C000001”) from the skin management information 500.

  In step S1002, the usage state determination unit 721 reads the skin management information 500 and the prepaid card management information 400_1 "store ID", "cumulative usage fee", "cumulative usage count", "charge count", "point count". "Compare with.

  In step S1003, the use state determination unit 721 specifies the rank of the prepaid card 170 based on the comparison result in step S1002. In step S1004, the use state determination unit 721 specifies the skin ID associated with the rank specified in step S1003. If the specified skin ID is not yet recorded in the prepaid card management information 400_1, it is recorded in the prepaid card management information 400_1. At this time, “not transmitted” is recorded in “transmission information” of the prepaid card management information 400_1.

(4) Terminal Management Processing Next, the flow of terminal management processing by the skin transmission unit 722 will be described. FIG. 11 is a flowchart illustrating a flow of terminal management processing by the skin transmission unit 722.

  In step S <b> 1101, the skin transmission unit 722 determines whether the usage state management application 131 of the mobile terminal 130 is activated. Specifically, it is determined whether or not a request for transmitting prepaid card management information is received from portable terminal 130. If it is determined in step S1101 that the prepaid card management information transmission request has not been received, it is determined that the use state management application 131 is not activated in the mobile terminal 130, and the process waits until it is activated.

  On the other hand, if it is determined that the request for transmitting the prepaid card management information has been received, it is determined that the use state management application 131 has been activated in the mobile terminal 130, and the process proceeds to step S1102. In step S1102, the skin transmission unit 722 extracts the prepaid card ID (= “C000001”) included in the prepaid card management information transmission request.

  In step S1103, the skin transmission unit 722 reads the prepaid card management information 400_1 corresponding to the prepaid card ID extracted in step S1102. In step S1104, the skin transmitting unit 722 compares the prepaid card management information 400_1 read in the previous loop with the prepaid card management information 400_1 read in the current loop, and determines whether or not “action” has been updated. .

  If it is determined in step S1104 that the “action” has been updated, the process proceeds to step S1105. In the case of the first loop after the usage state management application 131 is activated, the process advances to step S1105 regardless of whether or not the “action” is updated.

  In step S <b> 1105, the skin transmission unit 722 transmits the current amount and other usage history recorded in the “balance” included in the prepaid card management information read in the current loop to the mobile terminal 130. Thereby, while the usage state management application 131 is running, changes in the usage history of the prepaid card can be transmitted to the mobile terminal 130 in real time.

  In step S1106, the skin transmission unit 722 determines whether there is an untransmitted skin based on the prepaid card management information 400_1. If it is determined in step S1106 that there is an untransmitted skin, the process proceeds to step S1107. In step S <b> 1107, the skin transmission unit 722 transmits an untransmitted skin to the mobile terminal 130.

  In step S1108, the skin transmission unit 722 rewrites “transmission information” corresponding to the skin ID of the skin transmitted this time from “untransmitted” to “transmitted” in the prepaid card management information 400_1.

  In step S <b> 1109, the skin transmission unit 722 determines whether or not the usage state management application 131 has ended in the mobile terminal 130. In the portable terminal 130, when the usage state management application 131 is terminated, the termination information is transmitted to the management server 110. Accordingly, the skin transmission unit 722 can determine whether or not the usage state management application 131 is terminated based on whether or not the termination information is transmitted from the mobile terminal 130.

  If it is determined in step S1109 that the usage state management application 131 has not ended, the process returns to step S1103, and the processes from step S1103 to step S1108 are repeated. Thereby, when the prepaid card 170 is used and the new skin is selected as a usable skin while the usage state management application 131 is running, the newly usable skin is displayed in real time on the mobile terminal 130. Can be sent to.

  If it is determined in step S1109 that the usage state management application 131 is terminated, the terminal management process is terminated.

<7. Functional configuration of mobile terminal>
Next, functions realized in the mobile terminal 130 when the usage state management application 131 is executed by the CPU 301 will be described. FIG. 12 is a diagram illustrating a functional configuration of the mobile terminal 130. As illustrated in FIG. 12, the mobile terminal 130 includes a user registration unit 1201, a skin acquisition unit 1202, a prepaid card management information acquisition unit 1203, and a display control unit 1204.

  The user registration unit 1201 registers the user ID of the user 160 who purchased the prepaid card 170 in the prepaid card management information 400_1. Specifically, an input of a prepaid card ID of the prepaid card 170 purchased by the user 160 and an input of the user ID of the user 160 are accepted, and a user registration request is transmitted to the management server 110.

  The skin acquisition unit 1202 acquires an unsent skin from the management server 110. When the usage status management application 131 is activated, the prepaid card management information acquisition unit 1203 transmits the prepaid card management information 400 including “current balance” of the prepaid card management information and other usage history to the management server 110. Make a request. The usage history includes “usage fee or charge amount”, “date and time”, and “store (store ID)” in addition to “remaining money”. Further, the prepaid card management information acquisition unit 1203 transmits the prepaid card management information transmission request including the prepaid card ID.

  The display control unit 1204 controls display of a display screen provided by the usage state management application 131. In the display control unit 1204, when the skin acquisition unit 1202 newly acquires a skin, or when the prepaid card management information acquisition unit 1203 acquires the updated prepaid card management information 400_1, these are displayed in real time. To control the display screen.

<8. Processing executed by portable terminal>
Next, usage state management processing executed by the usage state management application 131 of the mobile terminal 130 will be described.

  FIG. 13 is a flowchart showing the flow of usage status management processing by the usage status management application 131. When the usage state management application 131 is activated, the flowchart shown in FIG. 13 is executed. In the description of FIG. 13, it is assumed that the usage state management application 131 has already completed user registration and has set a skin (skin ID = “A-001”) acquired from the management server 110.

  In step S1301, the prepaid card management information acquisition unit 1203 identifies the prepaid card ID of the prepaid card that is to be managed by the usage state management application 131.

  In step S <b> 1302, the display control unit 1204 reads the skin currently set in the usage state management application 131.

  In step S <b> 1303, the prepaid card management information acquisition unit 1203 transmits a prepaid card management information transmission request to the management server 110. Further, in step S1304, the prepaid card management information acquisition unit 1203 acquires the prepaid card management information 400_1 transmitted from the management server 110. In step S <b> 1305, the skin acquisition unit 1202 acquires a skin if it is transmitted from the management server 110.

  In step S1306, the display control unit 1204 displays the display screen of the usage state management application 131 to which the skin read in step S1302 and the prepaid card management information acquired in step S1304 are applied. If a new skin is acquired in step S1305, a message indicating that a new skin has been acquired is displayed on the display screen.

  In step S <b> 1307, the display control unit 1204 determines whether a skin change instruction has been received from the user 160. If it is determined in step S1307 that a skin change instruction has been received, the skin instructed to change is set, and the process advances to step S1308. In step S1308, the display control unit 1204 reads the set skin and proceeds to step S1309 (the read skin is applied to the display screen in step S1306 of the next loop).

  On the other hand, if it is determined in step S1307 that no skin change instruction has been received, the process directly proceeds to step S1309.

  In step S <b> 1309, the display control unit 1204 determines whether an end instruction for the usage state management application 131 has been received. If it is determined in step S1309 that an instruction to end the usage state management application 131 has not been received, the process returns to step S1304. Then, the processing from step S1304 to S1308 is repeated.

  On the other hand, if it is determined in step S1309 that an instruction to end use state management application 131 has been received, the process advances to step S1310. In step S1310, the display control unit 1204 notifies the management server 110 that the usage state management application 131 has ended. Thereafter, the usage state management application 131 is terminated.

<9. Explanation of mobile terminal display screen>
Next, a display example of the display screen of the mobile terminal 130 will be described. 14-16 is a figure which shows the example of a display of the display screen of the portable terminal 130. FIG.

  FIG. 14 is a diagram for explaining a user registration screen displayed during the user registration process on the display screen 1410 of the mobile terminal 130. FIG. 14A shows a state in which the icon 1420 of the usage state management application 131 before the user registration process is displayed on the display screen 1410.

  When the icon 1420 is tapped in this state and the usage state management application 131 is activated, a user registration screen 1430 shown in FIG. 14B is displayed. As shown in FIG. 14B, the user registration screen 1430 is provided with an input field 1431 for inputting a prepaid card ID and an input field 1432 for inputting a user ID.

  The user 160 inputs the prepaid card ID described in the purchased prepaid card 170 in the input field 1431. In addition, the user 160 inputs his / her user ID in the input field 1432. Further, the user 160 presses the transmission button 1433. Accordingly, the user registration unit 1201 transmits a user registration request including the prepaid card ID and the user ID to the management server 110.

  FIG. 15 is a diagram for explaining the display screen 1410 of the mobile terminal 130 after the user registration is completed. FIG. 15A shows a state in which the icon 1520 of the usage state management application 131 after the user registration process is displayed on the display screen 1410. As shown in FIG. 15A, when the user registration process is completed, it is determined that the management target of the use state management application 131 is a prepaid card with a prepaid card ID = “C000001”. Therefore, information indicating that the prepaid card ID = “C0000001” is displayed on the icon 1520. It is assumed that the icon 1520 has a design similar to the design drawn on the prepaid card 170.

  When the icon 1520 is tapped in the state shown in FIG. 15A, the usage state management application 131 is activated, and the balance screen 1530 is displayed on the display screen 1410 as an initial screen as shown in FIG. 15B. Is displayed. On the balance screen 1530, the balance recorded in the prepaid card management information 400_1 is displayed. Further, by applying the set skin, a design 1532 similar to the design drawn on the prepaid card 170 is displayed. The balance screen 1530 is displayed not only as an initial screen when the usage state management application 131 is started but also when the “balance” button 1531 is pressed.

  When the “history” button 1541 is pressed in the state shown in FIG. 15B, a history screen 1540 is displayed on the display screen 1410 as shown in FIG. 15C. The history screen 1540 displays the usage history recorded in the prepaid card management information 400_1. Further, a design 1542 similar to the design drawn on the prepaid card 170 is displayed.

  FIG. 16A shows a state in which the notification screen 1610 is displayed when the “notification” button 1550 is tapped in the state shown in FIG. 15B or 15C. On the notification screen 1610, a message notifying that a new skin has been transmitted from the management server 110 is displayed. In addition, a skin ID for specifying the newly transmitted skin and a design included in the skin are displayed.

  FIG. 16B shows a state in which the skin setting screen 1620 is displayed when the “SETTING” button 1621 is tapped in the state shown in FIG. 15B, FIG. 15C, or FIG. ing. As shown in FIG. 16B, the skin setting screen 1620 displays a list of skin IDs stored in the list information 600 of acquired skins.

  The user 160 can set an arbitrary skin by selecting a desired skin ID on the skin setting screen 1620.

<10. Flow of processing in management system>
Next, the processing flow of the entire management system 100 will be described. FIG. 17 is a sequence diagram showing the flow of processing of the entire management system 100. In describing the flow of the processing illustrated in FIG. 17, it is assumed that the usage state management application 131 is installed in the mobile terminal 130 in advance.

  In step S1701, the user 160 pays a price to the prepaid card seller 1730, and in step S1702, obtains the prepaid card. In step S 1703, an instruction to start the usage state management application 131 is input to the mobile terminal 130. As a result, in step S1704, the usage state management application 131 is activated and a user registration screen is displayed.

  When the user 160 inputs registration information (user ID, prepaid card ID) with the user registration screen displayed (step S1705), the registration information is transmitted from the mobile terminal 130 to the management server 110 ( Step S1706).

  The management server 110 that has received the registration information reads the prepaid card management information corresponding to the prepaid card ID and records the user ID to complete the user registration (step S1707).

  When the user registration is completed, the management server 110 transmits skin and prepaid card management information to the mobile terminal 130 (step S1708). When the mobile terminal 130 receives the skin and prepaid card management information, the usage state management application 131 sets the received skin and displays an initial screen to which the set skin is applied (step S1709). Thereby, the user 160 can see the design included in the drawn content drawn on the purchased prepaid card on the display screen 1410 of the mobile terminal 130. The initial screen displays the balance immediately after purchase of the prepaid card as prepaid card management information. As a result, the user 160 can confirm the amount of the prepaid card purchased by the user 160.

  Upon confirming the completion of user registration, the user 160 inputs an end instruction for the usage state management application 131 (step S1710). As a result, the usage state management application 131 ends (step S1711).

  Thereafter, when the user 160 uses a prepaid card when purchasing merchandise at the member store (step S1712), usage information is transmitted from the information terminal 140 of the member store to the management server 110 (step S1713). The management server 110 that has received the usage information updates the prepaid card management information (step S1714).

  After that, the user 160 inputs an activation instruction for the usage state management application 131 in order to confirm the balance of the prepaid card and the like (step S1715). Thereby, in the portable terminal 130, the use state management application 131 is activated (step S1716).

  The usage state management application 131 transmits a request for transmitting prepaid card management information to the management server 110 (step S1717). The management server 110 that has received the transmission request reads the prepaid card management information corresponding to the prepaid card ID included in the transmission request and transmits it to the mobile terminal 130 (step S1718).

  Further, the management server 110 determines whether there is an unsent skin based on the read prepaid card management information. If it is determined that there is an untransmitted skin, the skin is transmitted to the mobile terminal 130 (step S1719).

  When the prepaid card management information is received, the usage state management application 131 displays an initial screen reflecting the received prepaid card management information (step S1720). When the initial screen is displayed, the use state management application 131 applies a skin that has already been set. If a new skin is received in step S1719, a message notifying that the skin has been received is displayed (step S1721).

  When the message 160 is received and the user 160 instructs to change the skin (step S1722), the use state management application 131 changes the setting of the skin (step S1723). As a result, the newly set skin is applied to the initial screen.

  Thereafter, when the user 160 inputs an instruction to end the usage state management application 131 (step S1724), the usage state management application 131 is ended (step S1725).

<11. Summary>
As is clear from the above description, in the management server 110 according to this embodiment,
-It is set as the structure which transmits the skin containing the design contained in the drawing content drawn on the prepaid card with respect to the user who completed user registration.
・ Prepaid card usage information is acquired and usage history is tabulated for each user.
-The configuration is such that the usage history is sent to the user while the usage status management application is running.
A plurality of skins including the design included in the drawing contents drawn on the prepaid card are prepared, and the skin corresponding to the usage history count result is transmitted to the user.

  As a result, when the user activates the use state management application, the design included in the drawn content drawn on the prepaid card purchased by the user can be displayed on the mobile terminal. As a result, the user purchases a favorite prepaid card, and sales of a specific prepaid card are promoted.

  Moreover, since various skins can be acquired according to the use history of a prepaid card, the user can increase the number of design variations to be displayed as the prepaid card is used. Furthermore, since points are added due to use at a specific store, the user can increase skin acquisition opportunities as the use at a specific store is increased. As a result, the use of the prepaid card by the user (especially, the use at a specific store) is promoted, and sales of products and services can be promoted.

  That is, by improving the interest of the user who uses the use state management application, it is possible to realize the sales promotion and usage promotion of a specific prepaid card and the sales promotion of products and services.

[Second Embodiment]
The management server according to the first embodiment is configured to transmit the prepaid card management information and the skin to the user's mobile terminal. However, the present invention is not limited to this, and may be configured to transmit advertisements for products and services handled by content providers that provide all content including designs included in skins.

  For users who have purchased prepaid cards on which specific drawing content is drawn, the products and services handled by content providers that provide all content including the designs included in the drawing content are products and services that stimulate purchase incentives. There is a high possibility. For this reason, the advertisement of the product and service for the user is effective in promoting the sale of the product and service. Details of this embodiment will be described below.

<1. Management Server Functional Configuration>
FIG. 18 is a diagram illustrating a functional configuration of the management server 1810 according to the second embodiment. Among the functional configurations shown in FIG. 18, the same reference numerals are given to the same components as those in the functional configuration described with reference to FIG. 7 in the first embodiment, and description thereof is omitted here.

  The difference from FIG. 7 is that an advertising unit 1801 is included. The advertisement unit 1801 transmits advertisements for products and services handled by the content provider. The advertisement unit 1801 transmits an advertisement to a user who has purchased a prepaid card on which a design based on content provided by a content provider is drawn.

  FIG. 19 is a diagram illustrating the timing at which the advertisement unit 1801 transmits an advertisement. Here, for the sake of simplicity of explanation, a case where an advertisement is transmitted to two users will be described. One user purchases a prepaid card having a user ID = “UID-X” and a prepaid card ID = “C000001” (a prepaid card on which a design based on the content of content ID = “AAAA” is drawn). It shall be. The other user purchases a prepaid card having a user ID = “UID-Y” and a prepaid card ID = “C000301” (a prepaid card on which a design based on the content of content ID = “DDDD” is drawn). Suppose you are.

  Here, as shown in FIG. 19A, it is assumed that a content provider that provides content with content ID = “AAAA” provides an advertisement period 1901 and requests a prepaid card manager to transmit an advertisement.

  Then, in the advertisement period 1901, it is assumed that the user with the user ID = “UID-X” starts the usage state management application 131 with the prepaid card ID = “C000001”. The advertisement unit 1801 recognizes that the prepaid card ID = “C000001” is associated with the content ID = “AAAAA” by referring to the skin management information 500. As a result, the advertisement unit 1801 transmits an advertisement requested by a content provider that provides content with content ID = “AAAA” to the mobile terminal 130 of the user with user ID = “UID-X”.

  In the advertisement period 1901, the user with the user ID = “UID-Y” also activates the usage status management application (here, the usage status management application 131 ′) with the prepaid card ID = “C000301”. . However, according to the skin management information 500, the prepaid card ID = “C000301” is associated with the content ID = “DDDD”. For this reason, even during the advertisement period 1901, the advertisement requested by the content provider that provides the content with the content ID = “AAAA” while the usage state management application 131 ′ with the prepaid card ID = “C000301” is activated. Will never be sent.

  On the other hand, as shown in FIG. 19B, the timing when the usage state management application 131 ′ with the prepaid card ID = “C000301” is activated is in the advertising period 1902. The advertisement period 1902 is a period in which the prepaid card manager is requested to transmit advertisements from a content provider that provides content with content ID = “DDDD”.

  Therefore, the advertisement unit 1801 provides a content provider that provides content with content ID = “DDDD” to the mobile terminal of the user with user ID = “UID-Y” (here, mobile terminal 130 ′). Send the requested advertisement.

  As described above, by using the skin management information 500 in which the user ID and the content ID are associated in advance, it is possible to transmit a useful advertisement to the user.

<2. Flow of advertisement display processing>
Next, the flow of advertisement display processing by the advertisement unit 1801 will be described. FIG. 20 is a flowchart showing the flow of advertisement display processing by the advertisement unit 1801. In step S2001, the use state determination unit 721 determines whether a transmission request for prepaid card management information has been received. If it is determined in step S2001 that the usage state determination unit 721 has not received a transmission request for prepaid card management information, the process waits until a transmission request is received.

  On the other hand, if it is determined in step S2001 that a prepaid card management information transmission request has been received, the process advances to step S2002. In step S2002, the usage state determination unit 721 determines that the usage state management application 131 has started. Further, the prepaid card ID and the user ID included in the transmission request are extracted and notified to the advertising unit 1801. Thereby, the advertising unit 1801 identifies the prepaid card ID notified from the usage state determination unit 721. In step S2003, the advertising unit 1801 refers to the skin management information 500 to identify the content ID associated with the identified prepaid card ID.

  In step S2004, the advertising unit 1801 determines whether or not the content provider that provides the content with the content ID specified in step S2003 is currently in the advertising period.

  If it is determined in step S2004 that the advertisement period is in progress, the process advances to step S2005 to transmit the advertisement of the content provider to the mobile terminal 130 of the user 160. Note that the advertisement unit 1801 transmits the advertisement of the content provider to the mobile terminal 130 specified by the user ID notified from the usage state determination unit 721 in step S2002.

  On the other hand, if it is determined in step S2004 that it is not during the advertisement period, the advertisement display process is terminated without transmitting the advertisement.

<3. Explanation of mobile terminal display screen>
Next, an example of the display screen of the mobile terminal 130 when an advertisement is displayed will be described. FIG. 21 is a diagram illustrating an example of a display screen of the mobile terminal 130 when an advertisement is displayed.

  As shown in FIG. 21, when the usage state management application 131 is activated and a balance screen 1530 is displayed as an initial screen on the display screen 1410, an advertisement display area 2101 is displayed and an advertisement of a content provider is displayed. .

  The advertisement display area 2101 is continuously displayed even when the “history” button 1541 is pressed and the history screen 1540 is displayed, or the “setting” button 1621 is pressed and the skin setting screen 1620 is displayed. Shall. However, it can be erased at an arbitrary timing by tapping the erase button 2111.

<4. Summary>
As is clear from the above description, in the management server 1810 according to this embodiment,
In the advertisement period of the content provider, when a corresponding usage state management application is activated on the mobile terminal, an advertisement of the content provider is transmitted to the mobile terminal.
-It is set as the structure determined by referring the skin management information with which the prepaid card ID and content ID are linked | related, whether it is a corresponding use state management application.

  Thereby, the user can browse advertisements of products and services handled by a content provider that provides all content including designs included in the drawn content drawn on the purchased prepaid card.

[Third Embodiment]
In the first and second embodiments, the case where the user purchases one prepaid card has been described. However, the number of prepaid cards purchased by the user is not limited to one. When a plurality of prepaid cards are purchased, user registration can be performed for each prepaid card. In this case, for each prepaid card, an icon of the usage state management application is displayed on the display screen 1410.

  Therefore, even if the same user, for example, when a prepaid card usage management application during the advertisement period is activated, an advertisement is transmitted, and when a prepaid card usage management application during the advertisement period is activated, the advertisement is transmitted. Never sent.

  In addition, the icon of a utilization state management application is not limited to when preparing for every prepaid card. For example, only one icon of the usage state management application may be displayed regardless of the number of prepaid cards purchased. In this case, it is assumed that the user can select which prepaid card the skin corresponding to is applied after the usage state management application is activated.

  A specific example will be described. For example, it is assumed that the user 160 has purchased two prepaid cards with prepaid card ID = “C000001” and “C000301”. In this case, the usage state management application 131 can selectively set a skin corresponding to each prepaid card.

  For this reason, when a skin corresponding to the prepaid card with the prepaid card ID = “C000001” is set, the skin based on the content ID = “AAAA” is applied when the usage state management application 131 is activated. It will be. Similarly, when the skin corresponding to the prepaid card with the prepaid card ID = “C000301” is set, the skin based on the content ID = “DDDD” is applied when the usage state management application 131 is activated. It will be.

  If the skin corresponding to the prepaid card with the prepaid card ID = “C000001” is set, when the usage state management application 131 is activated, an advertisement is transmitted from the content provider that provides the content with the content ID = “AAA”. Is done.

  On the other hand, when the skin corresponding to the prepaid card with the prepaid card ID = “C000301” is set, when the usage state management application 131 is activated, an advertisement is transmitted from the content provider that provides the content with the content ID = “DDDD”. Is done.

  That is, when the same user has purchased a plurality of prepaid cards, the transmitted advertisements differ depending on which prepaid card skin is set.

  Moreover, in the said 1st and 2nd embodiment, although it was set as the structure which totals a usage history for every prepaid card, it is good also as a structure which integrates and totals the usage history of several prepaid cards. Specifically, when the prepaid card IDs of a plurality of prepaid cards purchased by the user are all associated with the same content ID, the usage state determination unit 721 aggregates usage histories in the respective prepaid card management information. Results may be integrated. For example, when the prepaid card IDs of two prepaid cards are both associated with the same content ID, the rank is determined based on the total value of the usage amount of one prepaid card and the usage amount of the other prepaid card. You may comprise.

  Moreover, in the said 1st and 2nd embodiment, although it was set as the structure which displays the design contained in the drawing content drawn on the prepaid card on a portable terminal as a skin, this invention is not limited to this. For example, audio data, image data, moving image data, and text data related to the design included in the drawing content drawn on the prepaid card may be output on the mobile terminal separately from the skin. Specifically, when the usage state management application 131 is activated, music related to the design included in the drawn content drawn on the prepaid card flows or related moving images and characters are displayed. May be. Thus, the user's interest is further improved by adopting a configuration in which the data related to the design included in the drawn content drawn on the prepaid card is output on the mobile terminal.

  It should be noted that the present invention is not limited to the configuration shown here, such as a combination with other elements in the configuration described in the above embodiment. These points can be changed without departing from the spirit of the present invention, and can be appropriately determined according to the application form.

100: Management system 110: Management server 111: Card management program 112: Terminal management program 113: Prepaid card management information DB
114: Skin management DB
120: Content providing server 121: Content management program 122: Content DB
130: Portable terminal 131: Usage state management application 132: Acquisition skin DB
140: information terminal 141: card reader 400: prepaid card management information 500: skin management information 600: acquired skin list information 711: card information registration unit 712: usage state recording unit 721: usage state determination unit 722: skin transmission unit 1201 : User registration unit 1202: Skin acquisition unit 1203: Prepaid card management information acquisition unit 1204: Display control unit 1410: Display screen 1420: Icon 1430: User registration screen 1520: Icon 1530: Balance screen 1540: History screen 1610: Notification screen 1620 : Skin setting screen 1801: Advertising unit 1810: Management server 2101: Advertisement display area

Claims (12)

A management server that manages data output via a user's terminal when an application is executed,
In response to a request from the application installed on the terminal of the user carrying the available cards when purchasing goods or services, a user identifier identifying the user and registered in association with the card registration Means,
A management server comprising: a transmission unit configured to transmit, to the user terminal, data associated with the card and output via the user terminal when registered by the registration unit.   The management server according to claim 1, wherein the data output via the user terminal includes at least one of audio data, image data, moving image data, and text data. A counting means for acquiring and counting the use history of the user's card;
Selection means for selecting data corresponding to the tabulation result by the tabulation means from a plurality of the data associated with the card in response to a request from the application installed on the user terminal. And
The transmission means includes
The management server according to claim 1, wherein the data selected by the selection unit is transmitted to the terminal of the user. The selection means includes
The management server according to claim 3, wherein when the totaling result by the totaling unit satisfies a predetermined condition, data corresponding to the totaling result is selected. The transmission means includes
4. The management server according to claim 3, wherein data selected in accordance with a count result of card usage histories registered in association with the user identifier is transmitted to the terminal of the user. 5.   The management server according to claim 3, wherein the tabulation result includes at least one of a cumulative usage fee, a cumulative usage count, and a charging count of the card. The selecting means further includes:
4. The management server according to claim 3, wherein when the usage location included in the usage history of the card satisfies a predetermined condition, data corresponding to the usage location is selected. The transmission means further includes:
2. The management server according to claim 1, wherein information from a provider that provides content based on a drawing content drawn on the card is transmitted to the terminal of the user.   The transmission means is a provider that provides the content when the signal transmitted when the application is started in the user terminal includes information for specifying the predetermined content. The management server according to claim 8, wherein information from is transmitted to the terminal of the user. A management method in a management server that manages data output via a user's terminal when an application is executed,
Registration means, in response to a request from the installed the application to the terminal of the user carrying the available cards when purchasing goods or services, a user identifier identifying the user, the association with the card Registration process to register,
A transmission step of transmitting, to the user terminal, data associated with the card and output via the user terminal when registered in the registration step; Management method. When executing the application, the computer that manages the data output via the user's terminal ,
In response to a request from the application installed on the terminal of the user carrying the available cards when purchasing goods or services, a user identifier identifying the user and registered in association with the card registration Process,
A program for executing a transmission step of transmitting, to the user's terminal, data associated with the card and output via the user's terminal when registered in the registration step. An application running on the terminal;
A management server that manages data output via the terminal of the user when the application is executed ,
The management server
In response to a request from the application installed on the terminal of the user carrying the available cards when purchasing goods or services, a user identifier identifying the user and registered in association with the card registration Means,
Transmission means for transmitting data that is associated with the card and output via the user's terminal when registered by the registration means, to the user's terminal;
The application is stored in the terminal computer.
A receiving step of receiving data transmitted by the transmitting means;
And a setting step for setting data received in the receiving step.

Images