Service management device, service management method, and program

Abstract

A service management device (100) includes: a node for storing a rule (220) that associates a usage history (210) of services provided by a respective plurality of business entities with available incentive services; and a service processing unit (102) for identifying, when acquiring a user's usage history (210) of services of the respective business entities, an incentive service available to the user using the rule (220) and performing a process related to the identified incentive service.

Description

[Technical field]

[0001] The present invention relates to a service management device, a service management method, and a program. [Background technology]

[0002] An example of a technology for promoting the use of a service is described in Patent Document 1. Device The system includes an acquisition unit that acquires a user's usage history for a specified service, the usage history being for a specified aggregation period and the usage history for a transaction period at least a portion of which overlaps with the aggregation period, and a determination unit that determines, as a benefit to be provided to the user, a benefit based on the service usage history in the transaction period, which differs depending on the usage history in the aggregation period.

[0003] Furthermore, Patent Document 2 describes a system that enables the management of service information and services for customer acquisition and sales promotion by providing available service information based on the card usage history using the customer's mobile information terminal.

[0004] Furthermore, Patent Document 3 describes an information providing device that displays coupons that can be used when purchasing a product or service on a mobile terminal in order to promote sales of the product or service. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] JP 2021-120843 A [Patent Document 2] JP 2004-227417 A [Patent Document 3] JP 2016-71649 A Summary of the Invention [Problem to be solved by the invention]

[0006] The technologies described in the above patent documents are related to the provision of a certain service and are intended to promote the use of that service. None of the documents describe the idea of ​​freely combining services provided by multiple different business entities and providing incentives to users according to the terms of use to promote the use of each service.

[0007] The present invention has been made in consideration of the above circumstances, and has as its object to promote service utilization by users by freely combining services provided by a plurality of different business entities. [Means for solving the problem]

[0008] In order to solve the above-mentioned problems, each aspect of the present invention employs the following configuration.

[0009] The first aspect relates to a service management device. A service management device according to a first aspect of the present invention comprises: A storage means for storing rules for linking a usage history of a service provided by each of a plurality of business entities with an incentive service that can be provided; The system has a service processing means that, when it acquires the user's usage history of the services of each of the multiple business entities, identifies incentive services that can be provided to the user using the rules, and executes processing related to the identified incentive service.

[0010] A second aspect relates to a service management method performed by at least one computer. A service management method according to a second aspect includes: A service management device storing in a storage means rules for linking the usage history of services provided by each of a plurality of business entities with incentive services that can be provided; When the user's usage history of the services of each of the multiple business entities is obtained, the rules are used to identify incentive services that can be provided to the user, and processing related to the identified incentive services is executed.

[0011] Another aspect of the present invention may be a program for causing at least one computer to execute the method of the second aspect, or a computer-readable recording medium having such a program recorded thereon. This recording medium includes a non-transitory tangible medium. The computer program comprises computer program code which, when executed by a computer, causes the computer to perform the service management method on the service management device.

[0012] Any combination of the above components, and any transformation of the present invention into a method, device, system, recording medium, computer program, etc., are also effective as aspects of the present invention.

[0013] Furthermore, the various components of the present invention do not necessarily have to be independent entities, but may be formed as a single member by multiple components, one component may be formed from multiple components, one component may be a part of another component, or part of one component may overlap with part of another component, etc.

[0014] In addition, although the method and computer program of the present invention describe a number of steps in a sequential order, the order does not limit the order in which the steps are executed. Therefore, when implementing the method and computer program of the present invention, the order of the steps can be changed as long as it does not affect the content.

[0015] Furthermore, the steps of the method and computer program of the present invention are not limited to being executed at different timings, and therefore a step may occur while another step is being executed, or the execution timing of a step may overlap partially or entirely with the execution timing of another step, etc. Effect of the Invention

[0016] According to each of the above aspects, services provided by a plurality of different business entities can be freely combined to promote service utilization by users. [Brief description of the drawings]

[0017] [Figure 1] 1 is a diagram conceptually illustrating a system configuration of a service management system according to an embodiment of the present invention. [Diagram 2] 2 is a block diagram illustrating an example of a hardware configuration of each computer constituting the service management system shown in FIG. 1. [Diagram 3] FIG. 2 is a functional block diagram illustrating a logical configuration of a service management device according to an embodiment. [Figure 4] 10 is a flowchart illustrating an example of the operation of the service management device according to the embodiment. [Diagram 5] 1 is a diagram conceptually illustrating a system configuration of a service management system according to an embodiment. [Figure 6] FIG. 2 is a functional block diagram illustrating a logical configuration of a service management device according to an embodiment. [Figure 7] FIG. 13 illustrates an example of a data structure of a token. [Figure 8] FIG. 13 is a diagram for explaining token usage history information of tokens recorded in multiple nodes. [Figure 9] 10 is a flowchart illustrating an example of the operation of a token processing unit of the service management device according to the embodiment. [Figure 10] 10 is a flowchart illustrating an example of an operation of a settlement process by a service processing unit of the service management device of the embodiment. [Figure 11]FIG. 2 is a functional block diagram logically illustrating a configuration of a service management device according to an embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0018] Hereinafter, the embodiments of the present invention will be described with reference to the drawings. In all the drawings, the same components are given the same reference numerals, and the description will be omitted as appropriate. In addition, in the following drawings, the configuration of the parts that are not related to the essence of the present invention is omitted and is not shown.

[0019] In the embodiment, "acquisition" includes at least one of the following: a device goes to retrieve data or information stored in another device or storage medium (active acquisition), and inputs data or information output from another device to the device (passive acquisition). Examples of active acquisition include making a request or inquiry to another device and receiving a reply, and accessing and reading information from another device or storage medium. Examples of passive acquisition include receiving information that is distributed (or transmitted, push notification, etc.). Furthermore, "acquisition" may mean selecting and acquiring data or information from received data or information, or selecting and receiving distributed data or information.

[0020] (First embodiment) <System Overview> FIG. 1 is a diagram conceptually showing a system configuration of a service management system 1 according to an embodiment of the present invention. The service management system 1 manages the provision of services provided by multiple different business entities to users. The service management system 1 includes a storage device that stores service usage history 210 of services provided by multiple business entities (indicated as businesses 50 in the figure), and a service management device 100 that manages the service usage history 210 of the multiple businesses 50.

[0021] The function of the service management device 100 is realized, for example, by decentralized applications (dApps: Decentralized Applications) that operate on a distributed network. However, the service management device 100 is not limited to this, and the function may be realized by at least one server that operates on a cloud. Furthermore, the service management device 100 may be a computer managed by an organization such as a so-called optimizer or aggregator.

[0022] A menu can be created to be provided to users by freely combining the services provided by multiple different businesses 50, and rules 220 can be created to give incentives to users on the condition that they use multiple services included in the menu. These rules 220 may be created by business entities (agency, local government, event planning company, etc.) other than the businesses 50 providing the individual services.

[0023] The rules 220 may be created on an operation terminal (computer 1000 described later) of the business entity.

[0024] Although details will be described in an embodiment below, the service usage history 210 and the rules 220 are stored in a node 20 (not shown in FIG. 1) on the blockchain network 10. The service management device 100 refers to the service usage history 210 stored in each node 20 on the blockchain network 10.

[0025] <Hardware configuration example> Each of the multiple nodes 20 constituting the service management system 1 and the service management device 100 is realized by at least one computer. The user terminal 30 of the user is a smartphone, tablet terminal, wearable terminal, or the like, which is also realized by a computer. As described above, the operating terminal of the business entity is a personal computer, smartphone, tablet terminal, or the like, which is also realized by a computer.

[0026] FIG. 2 is a block diagram illustrating an example of the hardware configuration of each computer 1000 constituting the service management system 1 shown in FIG.

[0027] The computer 1000 has a bus 1010, a processor 1020, a memory 1030, a storage device 1040, an input / output interface 1050, and a network interface 1060.

[0028] The bus 1010 is a data transmission path for transmitting and receiving data among the processor 1020, memory 1030, storage device 1040, input / output interface 1050, and network interface 1060. However, the method of connecting the processor 1020 and the like to each other is not limited to a bus connection.

[0029] The processor 1020 is implemented by a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), or the like.

[0030] The memory 1030 is a main storage device realized by a RAM (Random Access Memory) or the like.

[0031] The storage device 1040 is an auxiliary storage device realized by a hard disk drive (HDD), a solid state drive (SSD), a memory card, a read only memory (ROM), or the like. The storage device 1040 stores program modules that realize each function of the service management device 100 of the service management system 1 (for example, the service processing unit 102 in FIG. 3, the token processing unit 110 in FIG. 6, and the selection unit 120 in FIG. 11, which will be described later). The processor 1020 reads each of these program modules into the memory 1030 and executes them, thereby realizing each function corresponding to the program module. The storage device 1040 also functions as a storage unit (not shown) that stores various information used by the service management device 100. The storage means of the node 20 may also be realized by the storage device 1040.

[0032] The program module may be recorded in a recording medium. The recording medium for recording the program module may include a non-transitory tangible medium usable by the computer 1000, and the program code readable by the computer 1000 (processor 1020) may be embedded in the medium.

[0033] The input / output interface 1050 is an interface for connecting the computer 1000 to various input / output devices.

[0034] The network interface 1060 is an interface for connecting the computer 1000 to a communication network. This communication network is, for example, a LAN (Local Area Network) or a WAN (Wide Area Network). The method for connecting the network interface 1060 to the communication network may be a wireless connection or a wired connection. However, the network interface 1060 may not be used in some cases.

[0035] The computer 1000 is connected to necessary devices (not shown, for example, a camera, a display, an operation unit, a touch panel, etc.) via the input / output interface 1050 or the network interface 1060. Alternatively, the computer 1000 communicates with any device (not shown, for example, an automatic ticket gate, an IC card reader, etc.) via the input / output interface 1050 or the network interface 1060.

[0036] The service management system 1 may be realized by a plurality of computers 1000 constituting the service management device 100 .

[0037] Each component of the service management device 100 of each embodiment shown in Figures 3, 6, and 11 described below is realized by any combination of hardware and software of the computer 1000 of Figure 2. Those skilled in the art will understand that there are various modifications to the realization methods and devices. The functional block diagrams showing the service management device 100 of each embodiment show blocks of logical function units, rather than a configuration in hardware units.

[0038] <Example of functional configuration> FIG. 3 is a functional block diagram showing a logical configuration of the service management device 100 of the present embodiment. The service management device 100 includes a service processing unit 102 . First, the rules 220 linking the service usage history 210 provided by each of a plurality of business entities with the incentive services that can be provided are stored in the node 20. The service usage history 210 is recorded in the node 20 every time a user uses a service provided by each business entity 50. In addition, in the rules 220, the business entity 50 or the like defines conditions for granting an incentive according to the service usage conditions. As described above, the rules 220 may be defined by a business entity 50 other than the business entity 50 providing the service.

[0039] In this embodiment, the service usage history 210 and the rule 220 are each stored in a plurality of nodes 20 on the blockchain network 10. Therefore, a person other than the business operator 50 providing the service may define the rule 220 and store it in the node 20 using an external operation terminal (realized by the computer 1000 in FIG. 2).

[0040] For example, the rule 220 can be defined by being written in a predetermined programming language using an operation terminal of the business entity 50. For example, the rule 220 includes discount logic and incentive logic. An application for setting the rule 220 may be provided. The application is started on an operation terminal of the business entity 50, and a service for setting the service as a condition of use is provided. of The operator may be able to create the rules 220 by operating a screen including various user interfaces that accept selections, specification of terms of use, specification of the type of incentive and the means of granting, and the like.

[0041] The created rule 220 is stored in the node 20 on the blockchain network 10. A plurality of rules 220 may be presented to users by publishing them as a service list, for example, on a website. Details will be described in the third embodiment below.

[0042] The service usage history 210 includes at least identification information (user ID) for identifying a user, identification information (service ID) for identifying a used service, and date and time information when the service was used.

[0043] The service processing unit 102 acquires at least one rule 220 stored in the multiple nodes 20. Furthermore, the service processing unit 102 extracts and acquires the service usage history 210 related to a user from the service usage history 210 stored in the multiple nodes 20, for example, by using the user ID of the user as a search key.

[0044] The rule 220 can be created by combining at least two services among, for example, use of transportation, purchase of goods, and use of accommodation facilities. The rule 220 includes a service ID of a target service and a discount logic or an incentive logic. The rule 220 may also include, as a condition, a period during which the rule 220 applies. Alternatively, the rule 220 may also include, as a condition, attributes of users to which the rule 220 applies (for example, students, seniors, families with children, gender, etc.). Specific examples of the rule 220 will be described later in the examples.

[0045] When the service processing unit 102 acquires the user's usage history 210 of the services of each of the multiple businesses 50, the service processing unit 102 uses the rule 220 to identify incentive services that can be provided to the user, and executes processing related to the identified incentive service.

[0046] The process related to the incentive service is the granting of a predetermined value to a user, such as a process of electronically performing a fee discount, a cash back, a point grant, a coupon distribution, etc. The service processing unit 102 executes the granting of value to a user. For example, in the case of coupon distribution, the service processing unit 102 registers a digital coupon in the wallet 40 of the user terminal 30 of the user. Other processes will be described in detail in the second embodiment described later.

[0047] <Example of operation> FIG. 4 is a flowchart showing an example of the operation of the service management device 100 of the present embodiment. First, the service processing unit 102 acquires a rule a that defines that a coupon worth 1000 yen is to be given on the condition that a train A is boarded, a hotel B is stayed, and a purchase is made at a store C during a specific period of use (step S101). The acquisition of the rule 220 will be described in detail in the third embodiment described later.

[0048] The service processing unit 102 refers to the service usage history 210 for the specific usage period of the user, and judges whether or not each condition defined in the rule a is satisfied. Specifically, the service processing unit 102 first refers to the service usage history 210 for the specific usage period of the user, and if boarding on train A is confirmed (YES in step S103), proceeds to step S105. If boarding on train A is not confirmed (NO in step S103), this process ends.

[0049] Next, the service processing unit 102 refers to the service usage history 210 for the user's specific usage period, and if a stay at Hotel B can be confirmed (YES in step S105), proceeds to step S107. If a stay at Hotel B cannot be confirmed (NO in step S105), this process ends. Next, the service processing unit 102 refers to the service usage history 210 for the user's specific usage period, and if a purchase at Store C can be confirmed (YES in step S107), proceeds to step S109. If a purchase at Store C cannot be confirmed (NO in step S107), this process ends.

[0050] However, the order of execution of steps S103 to S107 is not limited to this. For example, the determination process of each step may be performed in parallel, the logical product of the determination results is calculated, and step S109 may be executed if all the determination results are YES.

[0051] In step S109, the service processing unit 102 grants an incentive defined in the rule a, in this case, distributes a coupon worth 1000 yen. Specifically, for example, a digital coupon worth 1000 yen is registered in the wallet 40 of the user terminal 30 of the user.

[0052] As described above, in this embodiment, the rule 220 linking the usage history of the services provided by each of the multiple business entities with the available incentive services is stored in the node 20, and when the service processing unit 102 acquires the service usage history 210 of the user for each of the multiple business entities, it identifies the incentive services available to the user using the rule 220 and executes processing related to the identified incentive service. Thus, according to this embodiment, services provided by different multiple business entities can be freely combined and presented to the user as the rule 220 together with incentive grant information, thereby encouraging the user to use the services.

[0053] This is efficient because the multiple service providers 50 do not need to manage the user's usage history regarding the granting of incentives or execute processes related to the granting of incentives. On the other hand, the multiple service providers 50 can obtain the service usage history 210 regarding the user's use of the service, and can use the information in planning and selling future services.

[0054] Second embodiment 5 is a diagram conceptually showing the system configuration of the service management system 1 of this embodiment. This embodiment is similar to the above-described embodiment except that it has a configuration in which tokens are used to manage the use of services.

[0055] At least one token 80 is issued for each service provided to a user. For example, an application (e.g., wallet 40) for registering the token 80 of the service to be used is pre-installed in the user terminal 30. A predetermined value to be used for payments related to the service is pre-registered and available for use in the wallet 40. The predetermined value is defined as a virtual currency. The virtual currency is not particularly limited, but examples include virtual currencies such as Bitcoin and Ethereum.

[0056] A user deposits an asset value in advance in virtual currency into the deposit pool 230 using a wallet 40. The deposited virtual currency is used in the settlement process for the fee to be paid when using a service.

[0057] The token 80 is, for example, a non-fungible token (NFT). A usage history of the token 80 corresponding to a service is recorded in the node 20 on the blockchain network 10 each time a service is used.

[0058] 6 is a functional block diagram showing a logical configuration of the service management device 100 of this embodiment. The service management device 100 further includes a token processing unit 110 in addition to the configuration of the service management device 100 of FIG. The token processing unit 110 issues a token 80 for a service and allocates it to a user, and when the provision of the service is completed, releases the allocation of the token 80 issued to the user. The service processing unit 102 uses the usage history of the token 80 to identify the usage history of the service for each user.

[0059] The token 80 issued to the user is registered in the wallet 40 of the user's user terminal 30. The token 80 is issued for each service and is registered in the wallet 40 as, for example, a train ticket or a hotel accommodation ticket. In addition, for the use of a service for purchasing goods at a store, a token 80 may be issued for the service using virtual currency payment that has been deposited in advance and registered in the wallet 40.

[0060] The token processing unit 110 records, each time a service corresponding to a token 80 issued to a user is used, the identification information (token ID) of the used token 80 and the date and time of use of the service in the node 20. For example, date and time information such as when boarding a train, when disembarking from a train, when checking in to a hotel, when checking out from a hotel, and when virtual currency payment is used to purchase a product at a store are each recorded in the node 20 as the usage history of the token 80.

[0061] 7 is a diagram showing an example of the data structure of the token 80. It is an example of token usage history information 240 recorded for each use of the token 80. The token usage history information 240 includes at least a token ID, a user ID, and a usage date and time in association with each other. In FIG. 7(a), date and time information when a user boarded a train is linked to a token ID and a user ID and stored in node 20. In FIG. 7(b), date and time information when a user disembarked from a train is linked to a token ID and a user ID and stored in node 20. In FIG. 7(c), date and time information when a user checked into a hotel where he / she is staying is linked to a token ID and a user ID and stored in node 20. In FIG. 7(d), date and time information when a user purchased a product at a store is linked to a token ID and a user ID and stored in node 20.

[0062] When the token processing unit 110 issues the token 80, the token ID of the token 80 is linked to the user ID of the user who issued the token 80 and the service ID of the service usable with the token 80, and these are stored in the service usage history 210. Therefore, the token processing unit 110 can identify the service used with the token 80 by searching the service usage history 210 recorded in the node 20 for the corresponding service ID using the token ID of the token 80 as a key.

[0063] 7, the token ID of the token 80 is recorded in the token usage history information 240 each time the token 80 is used, but in other examples, the token processing unit 110 may record a service ID of a service available with the token 80 in the token usage history information 240. That is, the token processing unit 110 records at least one of the token ID of the token 80 and the service ID of the service provided by the token 80 in the token usage history information 240 in association with the user ID and the date and time of use.

[0064] There are various possible methods for acquiring the token ID of the token 80 when using the token 80 registered in the wallet 40. For example, when the token 80 registered in the wallet 40 is used, the token usage history information 240 is recorded in the node 20 by the wallet 40 by the user terminal 30 communicating with an automatic ticket gate at a station and a contactless IC card reader at a lodging facility or store through short-range wireless communication such as NFC (Near Field Communication).

[0065] As another method of obtaining the token ID of the token 80, for example, a two-dimensional code (e.g., a QR (Quick Response) code (registered trademark)) containing information about the service provided by the token 80 (token ID or service ID) and a user ID may be displayed on the display of the user terminal 30 and read by a barcode reader or the like at a lodging facility or store, thereby allowing the token 80 registered in the wallet 40 to be used.

[0066] The user ID may be, for example, user identification information registered for use of the wallet 40 or user identification information registered for use of virtual currency, and is not particularly limited. However, the acquisition of the user ID is subject to the prior consent of the user.

[0067] Since the token usage history information 240 includes the user ID of the user, the service processing unit 102 can obtain the service usage history 210 of the user by extracting the user ID as a key. In addition, since the token usage history information 240 includes the usage date and time of the service, the service processing unit 102 can specify the service usage history 210 of the user during the usage period defined in the rule 220.

[0068] Furthermore, since the token usage history information 240 includes a token ID corresponding to the service, the service usage history 210 of each business operator 50 can extract information regarding the usage of the service defined in the rule 220 using the service ID as a key.

[0069] In addition, in FIG. 5, by extracting token usage history information 240 indicating the usage status of tokens 80 recorded in a distributed manner across multiple nodes 20 using the service ID as a key, a service usage history 210 for each service provided by the operator 50 can be obtained.

[0070] FIG. 8 shows how multiple nodes 20 record information about tokens 80 assigned to each user.

[0071] As described above, the token ID, user ID, and usage date and time of the token 80 assigned to the user are recorded and accumulated in each node 20 of the blockchain network 10. The records of each service usage of a certain user, such as getting on and off a train, checking in and out of a hotel, and paying for a product purchase at a store, may be recorded separately in different nodes 20. The usage records of the tokens 80 recorded in a distributed manner in multiple nodes 20, that is, the usage records of various services, are managed in an integrated manner by the service management device 100. Therefore, the service processing unit 102 can identify the usage history of each token 80, that is, the usage history of the service.

[0072] In this embodiment, since the history of the token 80 can be recorded on the blockchain network 10, for example, even if the usage records of services provided by different businesses 50 are recorded, the service management system 1 can be collectively managed by the service management system 1 by introducing the mechanism of the service management system 1. For example, it becomes possible to manage the usage status of services across different businesses 50. Therefore, in a tie-up campaign planned between different businesses 50, it is possible to define in the rule 220 the granting of incentives such as a discount on the fee for using the service on the condition of using a specific means of transportation, using an accommodation facility, and making a purchase at a specific store.

[0073] Note that information linked to the token 80 and recorded may be other than the example shown in FIG. 7. For example, in addition to the boarding date and time and disembarking date and time of the train ticket, information indicating the boarding station and disembarking station may be linked to the token 80 and recorded. Alternatively, in addition to the product purchase date and time, when a specific product is purchased, information indicating the product code and purchase amount of the product may be linked to the token 80 and recorded. Alternatively, location information of the user when using a service may be acquired using the location acquisition function of the user terminal 30, and the usage location information may be linked to the token 80 and recorded. In other words, the token usage history information 240 may include at least one of the boarding and disembarking station, purchased product code, purchase amount, and service usage location information in addition to the token ID, user ID, and usage date and time.

[0074] <Example of operation> FIG. 9 is a flowchart showing an example of the operation of the token processing unit 110 of the service management device 100 of this embodiment. First, when the token processing unit 110 accepts the selection of a service to be used by a user, it issues a token 80 for the use of the service and registers it in the wallet 40 of the user terminal 30 of the user (step S201).

[0075] The token processing unit 110 associates the token ID of the token 80 issued to the user, the service ID of the service, the user ID of the user, and the issuance date and time of the token 80, and stores them in the token usage history information 240.

[0076] Then, when detecting that the user has used the service (YES in step S203), the token processing unit 110 records information regarding the use of the token 80 stored in the node 20 on the blockchain network 10 (step S205).

[0077] The use of a service by a user can be detected, for example, by a record of entry or exit at an automatic ticket gate using the wallet 40 of the user terminal 30. Alternatively, it can be detected by the acceptance of a check-in operation at an airline ticket check-in machine at an airport using the wallet 40 of the user terminal 30. Alternatively, it can be detected by the use of the token 80 using the wallet 40 (such as reading a two-dimensional barcode) when checking in or checking out at an accommodation facility. Alternatively, it can be detected by electronic payment processing when purchasing a product at a store using the wallet 40.

[0078] Specifically, at least the token ID of the token 80, the user ID of the user, and the date and time of use are recorded as token usage history information 240 in the node 20 on the blockchain network 10.

[0079] Then, when the end of the service usage is detected (YES in step S207), the token processing unit 110 releases the token 80 assigned to the user (step S209). The method of detecting the end of the service usage may differ for each service. For example, in the case of a token 80 corresponding to a train ticket, the end of the usage of the token 80 may be detected when the user boards the train and then receives an exit record at the automatic ticket gate when disembarking using the wallet 40 of the user terminal 30.

[0080] In the case of a token 80 for a service provided by an accommodation facility, the end of use may be detected by accepting the end of use using the wallet 40 (such as by reading a two-dimensional barcode) when checking out of the accommodation facility. Alternatively, in the case of a token 80 for purchasing a product at a store, the end of use of the service may be detected by, for example, setting a usage limit for the token 80 and detecting the expiration of the usage limit. Alternatively, the end of use of the token 80 may be detected by the user himself deleting the token 80 by operating the wallet 40.

[0081] The token 80 that has been released from allocation to the user is deleted from the wallet 40 of the user terminal 30 of that user. Alternatively, the token 80 may be recorded in the wallet 40 as a used token 80.

[0082] The service usage history is recorded in the node 20 each time the token 80 is used. The service management device 100 can aggregate the records of the token 80 for each service recorded in a distributed manner in the multiple nodes 20, and extract and manage them as token usage history information 240 for each user or service usage history 210 for each service. In other words, the service usage history 210 and the token usage history information 240 are extracted by service provided by each business operator 50 and by user, respectively, from the usage records of the token 80 recorded in a distributed manner in the multiple nodes 20 each time.

[0083] The flowchart in Fig. 9 includes three processes, namely, a process for issuing a token 80 (step S201), a process at the time of using a service (steps S203 to S205), and a process at the time of ending the use of a service (steps S207 to S209). For the sake of explanation, Fig. 9 shows the three processes executed in order, but each process can be executed individually and does not necessarily have to be executed in the order shown in the flowchart in Fig. 9.

[0084] Next, using the service usage history 210 (token usage history information 240) recorded in this manner, the service processing unit 102 performs a settlement process for the value related to the payment for the use of the service used by the user and a settlement process for the value associated with the granting of incentives.

[0085] FIG. 10 is a flowchart showing an example of the operation of the settlement process by the service processing unit 102 of the service management device 100 of this embodiment. First, the service processing unit 102 accepts a deposit of virtual currency from the user to the wallet 40 of the user terminal 30 of the user (step S231). The accepted virtual currency is stored in the deposit pool 230.

[0086] When the use of a service using the wallet 40 is detected, the service processing unit 102 identifies the fee for the use of the service (step S233). The fee for the use of each service may be the fee presented by the business 50 providing the service, or when the service use is accepted, the business 50 providing the service may be inquired about the usage fee to obtain information on the value of the service at that time.

[0087] next, The service processing unit 102 The service usage history 210 of the user is referenced, and an incentive to be given to the user is identified according to the usage conditions defined in the rule 220 (step S235). For example, if a 10% discount on the usage fee is defined when the usage conditions of the rule 220 are met, the service processing unit 102 applies the discount identified in step S235, and performs settlement processing at the amount obtained by discounting 10% from the usage fee identified in step S233. Specifically, The service processing unit 102 In step S231, the value equivalent to the usage fee is calculated from the virtual currency deposited by the user, and distributed to each of the businesses 50 providing the services.

[0088] According to this embodiment, the token processing unit 110 issues a token 80 for a service and allocates it to a user, and when the provision of the service is completed, the token 80 issued to the user is released, and the service processing unit 102 identifies the service usage history for each user using the usage history of the token 80. In this way, by managing the usage of the service with the token 80, the usage status by users of services provided by multiple different business entities can be efficiently indicated and centrally managed by the service management device 100.

[0089] The process of granting incentives based on the condition of using the service will also be carried out using virtual currency. R Service Fee of The settlement process can be carried out more efficiently.

[0090] Third embodiment 11 is a functional block diagram logically showing the configuration of the service management device 100 of this embodiment. The service management device 100 of this embodiment is similar to any of the above-mentioned embodiments, except that it has a configuration for selecting a rule 220 to be applied to a user.

[0091] This embodiment further includes a selection section 120 in addition to the configuration of the second embodiment in Fig. 6. However, the selection section 120 of this embodiment may be combined with the configuration of the first embodiment in Fig. 3. The selection unit 120 selects at least one rule 220 from among a plurality of rules 220. The service processing unit 102 uses the selected rule 220.

[0092] There are various possible methods for the selection unit 120 to select a rule to be applied to a user, including, but not limited to, the following examples. A combination of the following methods may also be used. (1) When a service category (travel, sports, theater, etc.) is selected, a list of rules 220 registered in that category is presented (displayed on the display of the user terminal 30) and the user's selection is accepted. (2) Based on the attributes of the user (gender, age, occupation, residential area, hobbies, etc.), the rules 220 that are optimal for the user are created and proposed to the user. The rules 220 may be created by an administrator of the business entity, or may be created automatically by a predetermined logic (application, etc.). (3) At least one of the following is learned through machine learning: the user's attributes, the history of services the user has used in the past, and information about services that have been registered in advance as services in which the user is more interested; and rules 220 that are optimal for the user are created and proposed to the user. (4) A business entity proposes the service to a specific user or to the public. For example, the business entity notifies the user terminal 30 of a user who has used the service in the past, or notifies the public through general advertisements or direct mail. Here, the business entity may be either a business entity 50 that provides a service or a business entity that does not provide a service.

[0093] The timing of the selection of rule 220 by the selection unit 120 may be before the settlement process after using the service, before using the service, during the use of the service, or during a specific period (for example, during a campaign period), and is not particularly limited.

[0094] According to this embodiment, the selection unit 120 selects at least one rule 220 from among the multiple rules 220, and the service processing unit 102 uses the selected rule 220. This configuration makes it possible to freely combine services provided by various business entities and appropriately provide the user with a service suited to the user from an incentive service menu that provides incentives to the user on condition that the user uses the combined services. This makes it possible to further promote the use of services.

[0095] Although the embodiments of the present invention have been described above with reference to the drawings, these are merely examples of the present invention, and various configurations other than those described above can also be adopted. For example, the use of each service provided by the service management system 1 may be subject to a condition of the remaining balance of the user's assets deposited in the deposit pool 230 or past performance. For example, the service processing unit 102 performs processing such as displaying a screen on the wallet 40 prompting the user to deposit asset value before registering for use of the service, and judging whether the balance of the asset value of the user meets a criterion. The balance criterion may be, for example, that a value equal to or greater than the value required for using the service is deposited in the deposit pool 230.

[0096] According to this configuration, the value required as the consideration for using the service can be deposited in advance, so that the value as the consideration for using the service can be reliably collected. EXAMPLES

[0097] An embodiment showing an example of a combination of services provided by a plurality of different business entities will be described below. Example 1 <Regional promotion or travel campaign> Incentive service rules are defined that allow discounts or cash back when using transportation in a specific area, purchasing products at a trade fair, or using accommodation facilities. Specifically, the following rule 220 is defined: (a1) If a passenger rides a particular bus a certain number of times or more, a fixed fare will be charged (for example, by giving a cash back on the difference in fare) (similar to a one-day pass). (a2) If you stay at a specific lodging facility, you will receive 80 tokens equivalent to a certain amount when purchasing goods at a nearby trade fair (acting like a regional coupon). (a3) A 30% discount on long-distance flight and accommodation charges for a specified period.

[0098] Example 2 <Traveling campaigns / events such as stamp rallies> Define incentive service rules that allow users to enjoy incentives (NFTs, fungible tokens, etc.) and discounts when visiting specific facilities. Specifically, the following rule 220 is defined: (b1) An incentive is given if one visits all stations on a specified railway line within a certain period of time. (b2) An incentive is awarded if one visits all of the designated tourist attractions (hot spring facilities, shrines, temples, etc.) in a particular area.

[0099] Example 3 <Discount service across transportation operators> Specific routes, multiple operators, certain conditions Use to meet For example, an incentive service rule is defined such that if the service is used a certain number of times within a certain period, a cashback is given to cover the difference. Specifically, the following rule 220 is defined: (c1) If a person uses trains and taxis together more than a certain number of times, the fare difference will be refunded in one lump sum, making the fare a fixed amount (similar to a commuter pass). (c2) Where a long-distance train journey is involved, the fare for the outbound bus journey from the destination station will be discounted.

[0100] Although the present invention has been described above with reference to the embodiments and examples, the present invention is not limited to the above-mentioned embodiments and examples. Various modifications that can be understood by those skilled in the art can be made to the configuration and details of the present invention within the scope of the present invention. In the present invention, when information about a user is acquired and used, this shall be done lawfully.

[0101] A part or all of the above-described embodiments can be described as, but are not limited to, the following supplementary notes. 1. A storage means for storing rules for linking the usage history of services provided by each of a plurality of business entities with incentive services that can be provided; a service processing means for acquiring a usage history of the service of each of the plurality of business entities by the user, specifying an incentive service that can be provided to the user by using the rule, and executing a process related to the specified incentive service; A service management device comprising: 2. In the service management device according to 1., The service management device, wherein the service includes at least two of use of transportation, purchase of goods, and use of accommodation facilities. 3. In the service management device according to 1. or 2., The incentive service is the provision of a predetermined value to the user, The service processing means executes the provision of the value to the user. 4. In the service management device according to 3., A service management device, wherein the predetermined value is defined in virtual currency. 5. In the service management device according to any one of 1. to 4., The token is set for the service, A token processing means is further provided for issuing a token for the service and allocating it to a user, and canceling the allocation of the token issued to the user when the provision of the service is terminated; The service processing means identifies the usage history of the service for each user by using the usage history of the token. 6. In the service management device according to 5., The token is a non-fungible token (NFT). 7. In the service management device according to any one of 1. to 6., A selection means for selecting at least one rule from among the plurality of rules, The service processing means uses the selected rule.

[0102] 8. The service management device: storing in a storage means rules for linking the usage history of services provided by each of a plurality of business entities with incentive services that can be provided; A service management method that, when it obtains a user's usage history of the services of each of the multiple business entities, identifies incentive services that can be provided to the user using the rules, and executes processing related to the identified incentive service. 9. In the service management method according to 8., The service management method, wherein the service includes at least two of use of transportation, purchase of goods, and use of accommodation facilities. 10. In the service management method according to 8. or 9., The incentive service is the provision of a predetermined value to the user, The service management device, The service management method further comprises: providing the value to the user. 11. In the service management method according to 10., A service management method, wherein the predetermined value is defined in virtual currency. 12. In the service management method according to any one of 8. to 11., The token is set for the service, The service management device further comprises: issue a token for the service and assign it to a user, and when the provision of the service is terminated, release the assignment of the token issued to the user; A service management method, comprising: identifying a usage history of the service for each user by using the usage history of the token. 13. In the service management method according to 12., A service management method, wherein the token is a Non-Fungible Token (NFT). 14. In the service management method according to any one of 8. to 13., The service management device further comprises: Selecting at least one rule from among the plurality of rules; The service management method includes identifying the incentive service that can be provided to the user using the selected rule, and executing a process related to the identified incentive service.

[0103] 15. On the computer: A step of storing in a storage means a rule for linking a usage history of a service provided by each of a plurality of business entities with an available incentive service; A program for executing a procedure in which, when a user's usage history of the services of each of the multiple business entities is obtained, the program uses the rules to identify incentive services that can be provided to the user, and executes processing related to the identified incentive services. 16. In the program according to 15., The program, wherein the services include at least two of use of transportation, purchase of goods, and use of accommodation. 17. In the program according to 15. or 16., The incentive service is the provision of a predetermined value to the user, A program for causing a computer to execute a procedure for granting the value to the user. 18. In the program according to 17., The program, wherein the predetermined value is defined in virtual currency. 19. In the program according to any one of 15. to 18., The token is set for the service, a step of issuing a token for the service and allocating it to a user, and cancelling the allocation of the token issued to the user when the provision of the service is terminated; A program for causing a computer to execute a procedure for identifying the usage history of the service for each user using the usage history of the token. 20. In the program according to paragraph 19, The token is a Non-Fungible Token (NFT). 21. In the program according to any one of 15. to 20., selecting at least one rule from among the plurality of rules; A program for causing a computer to execute a procedure of identifying the incentive service that can be provided to the user using the selected rule, and executing a process related to the identified incentive service. [Explanation of symbols]

[0104] 1 Service Management System 10. Blockchain Network 20 nodes 30 User terminals 40 Wallet 50 businesses 80 Tokens 100 Service management device 102 Service Processing Unit 110 Token Processing Unit 120 Selection section 210 Service usage history 220 Rules 230 Deposit Pool 240 Token usage history information 1000 Computers 1010 Bus 1020 Processor 1030 Memory 1040 Storage Device 1050 Input / Output Interface 1060 Network Interface

Claims

1. A storage means for storing rules for linking a usage history of a service provided by each of a plurality of business entities with an incentive service that can be provided; a service processing means for acquiring a usage history of the service of each of the plurality of business entities by the user, specifying an incentive service that can be provided to the user by using the rule, and executing a process related to the specified incentive service; Equipped with The token is set for the service, A token processing means is further provided for issuing a token for the service and allocating it to a user, and canceling the allocation of the token issued to the user when the provision of the service is terminated; The token processing means associates the identification information of the token issued to the user, the identification information of the service, the identification information of the user, and the issuance date and time of the token, and stores them in a storage device as token usage history information; The service processing means identifies the usage history of the service for each user by using the token usage history information stored in the storage device.

2. In the service management device according to claim 1, The storage devices are a plurality of nodes on a blockchain network; The token processing means stores the token usage history information in any one of the plurality of nodes, The service processing means is a service management device that aggregates the token usage history information stored in the multiple nodes and identifies the service usage history for each user.

3. In the service management device according to claim 1 or 2, The token usage history information further includes at least one of the boarding and alighting stations of a transportation facility, the product code of a purchased item, the purchase amount, and location information where the service was used.

4. 4. The service management device according to claim 1, The service management device, wherein the service includes at least two of use of transportation, purchase of goods, and use of accommodation facilities.

5. 5. The service management device according to claim 1, The incentive service is the provision of a predetermined value to the user, The service processing means executes the provision of the value to the user.

6. 6. The service management device according to claim 5, A service management device, wherein the predetermined value is defined in virtual currency.

7. 7. The service management device according to claim 6, The service management device, wherein the token is a non-fungible token (NFT).

8. 8. The service management device according to claim 1, A selection means for selecting at least one rule from among the plurality of rules, The service processing means uses the selected rule.

9. A service management device storing in a storage means rules for linking the usage history of services provided by each of a plurality of business entities with incentive services that can be provided; When the user's usage history of the services of each of the plurality of business entities is acquired, the system identifies an incentive service that can be provided to the user using the rule, and executes a process related to the identified incentive service; The token is set for the service, The service management device further comprises: issue a token for the service and assign it to a user, and when the provision of the service is terminated, release the assignment of the token issued to the user; The identification information of the token issued to the user, the identification information of the service, the identification information of the user, and the issuance date and time of the token are linked together and stored in a storage device as token usage history information; A service management method, wherein when executing the process, the token usage history information stored in the storage device is used to identify the usage history of the service for each user.

10. On the computer, A step of storing in a storage means a rule for linking a usage history of a service provided by each of a plurality of business entities with an available incentive service; acquiring a usage history of the service of each of the plurality of business entities by the user, identifying an incentive service that can be provided to the user using the rule, and executing a process related to the identified incentive service; The token is set for the service, The computer further comprises: A procedure is executed to issue a token for the service, allocate it to a user, and release the allocation of the token issued to the user when the provision of the service is terminated; In the step of releasing, the identification information of the token issued to the user, the identification information of the service, the identification information of the user, and the issuance date and time of the token are linked together and stored in a storage device as token usage history information; A program that, in the step of executing the processing, identifies the usage history of the service for each user using the token usage history information stored in the storage device.

Images