Service management apparatus, service management method, and program

The service management system addresses user and revenue fluctuations by matching users with different usage timings and generating service provision data, enhancing service usage and revenue stability.

JP2026025262APending Publication Date: 2026-02-16NEC CORP
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
JP2024127945
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2024-08-02
Publication Date
2026-02-16

AI Technical Summary

Technical Problem

Service providers face challenges in maintaining consistent user numbers and revenue due to fluctuations in service usage, particularly exacerbated by the COVID-19 pandemic and remote work trends.

Method used

A service management system that matches users with different usage timings based on specified conditions, calculates usage fees, and generates service provision proof data to enable users to use services according to these conditions, thereby stabilizing user numbers and increasing revenue.

Benefits of technology

The system effectively equalizes user distribution across different days of the week and increases service usage by allowing users to purchase commuter passes at discounted fees, thus stabilizing revenue for service providers.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2026025262000001_ABST
    Figure 2026025262000001_ABST
Patent Text Reader

Abstract

To provide a service management device capable of leveling the number of users of a service on each day and increasing the number of users of the service.SOLUTION: Designation of service use conditions including at least service use timing is received from a plurality of users. To specify a user group including a plurality of matched users by matching the plurality of users different in use timing on the basis of use conditions. To calculate a service use price of each of a plurality of users included in a user group on the basis of use conditions. To generate service provision certification data for enabling each of a plurality of users to use a service corresponding to use conditions on the basis of the payment of the use price of each of the plurality of users.SELECTED DRAWING: Figure 1
Need to check novelty before this filing date? Find Prior Art

Description

[Technical Field]

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

[0002] Patent Document 1 discloses a technology that provides a platform that enables users to enjoy convenient services.

[0003] Specifically, Patent Document 1 discloses a technology that enables efficient management or use of information about individuals and things, and that uses the information about individuals and things to efficiently process business at vendors, stores, etc., thereby providing a foundation that enables users to enjoy convenient services. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2002-334162 Summary of the Invention [Problem to be solved by the invention]

[0005] Meanwhile, service providers need to equalize the number of users of their services on each day and increase the number of users of their services.

[0006] An object of the present disclosure is to provide a service management device, a service management method, and a program that solve the above-mentioned problems. [Means for solving the problem]

[0007] A service management device according to one aspect of the present disclosure includes a receiving means for receiving, from a plurality of users, specification of service usage conditions including at least the timing of service usage; a group identification means for matching a plurality of users with different usage timings based on the usage conditions and identifying a user group including the matched plurality of users; a usage fee calculation means for calculating a usage fee for the service for each of a plurality of users included in the user group based on the usage conditions; and a data generation means for generating service provision proof data that enables each of the plurality of users to use the service in accordance with the usage conditions based on payment of the usage fee for each of the plurality of users.

[0008] A service management method according to one aspect of the present disclosure receives, from multiple users, specification of service usage conditions including at least the timing of service usage, matches multiple users with different usage timings based on the usage conditions, identifies a user group including the matched multiple users, calculates a usage fee for the service for each of the multiple users included in the user group based on the usage conditions, and generates service provision proof data that enables each of the multiple users to use the service in accordance with the usage conditions based on payment of the usage fee for each of the multiple users.

[0009] A program according to one aspect of the present disclosure causes a computer of a service management device to function as: a receiving means for receiving, from multiple users, specification of service usage conditions including at least the timing of service usage; a group identification means for matching multiple users with different usage timings based on the usage conditions and identifying a user group including the matched multiple users; a usage fee calculation means for calculating a usage fee for the service for each of multiple users included in the user group based on the usage conditions; and a data generation means for generating service provision proof data that enables each of the multiple users to use the service in accordance with the usage conditions based on payment of a usage fee for each of the multiple users. [Effects of the Invention]

[0010] According to the above aspect, it is possible to equalize the number of users using the service each day and increase the number of users of the service. [Brief explanation of the drawings]

[0011] [Figure 1] 1 is a schematic configuration diagram of a service management system according to an embodiment of the present disclosure. [Figure 2] 1 is a system configuration diagram of a service management system according to an embodiment of the present disclosure. [Figure 3] FIG. 2 is a hardware configuration diagram of a service management device according to an embodiment of the present disclosure. [Figure 4] FIG. 2 is a functional block diagram of a service management device according to an embodiment of the present disclosure. [Figure 5] FIG. 10 is a diagram illustrating an example of a user management table according to an embodiment of the present disclosure. [Figure 6] FIG. 10 is a diagram illustrating a processing flow of a service management device according to an embodiment of the present disclosure. [Figure 7] FIG. 10 is a diagram illustrating another configuration of a service management device according to an embodiment of the present disclosure. [Figure 8] FIG. 10 is a diagram illustrating a processing flow of another configuration of the service management device according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0012] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings.

[0013] With the recent spread of the COVID-19 pandemic as a catalyst, many companies have adopted systems that allow employees to work remotely. In this environment, fewer companies are requiring 100% of their employees to come to the office, as was the case before the COVID-19 pandemic, and many companies are now allowing employees to work at a certain percentage (20-50%) of their offices. Under these circumstances, there are concerns about a decrease in the number of users of transportation services such as railway and bus companies. Furthermore, if people's social activities decrease due to the COVID-19 pandemic, there are concerns about a decrease in users of other services as well. The present disclosure provides a service management device, a service management method, and a program that prevent a decrease in revenue for service providers due to a decrease in the number of users of each service.

[0014] FIG. 1 is a schematic configuration diagram of a service management system according to an embodiment of the present disclosure. The service management system 100 of the present disclosure includes at least a service management device 1. The service management device 1 is connected to and communicates with terminals 2 owned by multiple users, such as users A, B, and C. The service management device 1 performs user management, sharing management, usage fee management, and the like.

[0015] More specifically, the service management device 1 accepts specification of service usage conditions from the terminals 2 of multiple users, matches the multiple users who will use the service based on the usage conditions, and identifies a user group including the matched multiple users. The service management device 1 calculates a usage fee for the service for each of the multiple users included in the user group based on the usage conditions. Then, based on the payment of the usage fee for each of the multiple users, the service management device 1 generates service provision proof data that enables each of the multiple users to use the service according to the usage conditions.

[0016] More specifically, the service management device 1 receives from a plurality of users the use conditions for which the service is rail travel, the use conditions including at least the section of travel, the period of travel, and the day of the week of travel. Furthermore, the service management device 1 matches a plurality of users who have specified usage conditions in which the usage section and usage period match but the days of the week for usage are different, and identifies a user group including the matched plurality of users. Furthermore, the service management device 1 calculates the usage fee for each of the multiple users based on the usage conditions of each user. Furthermore, the service management device 1 generates commuter pass data for railroad use according to the service usage fees for each of the multiple users.

[0017] FIG. 2 is a system configuration diagram of a service management system according to an embodiment of the present disclosure. As an example, the service management system 100 may be configured by a communication connection between a service management device 1, a fee server 3, and a database 4. The service management device 1, fee server 3, and database 4 may be built inside a cloud server that provides cloud services. The terminal 2 may be, for example, a smartphone or PC owned by a user, and may be communication connected to a cloud service such as the service management device 1 via a 4G (4th Generation) / 5G (5th Generation) network.

[0018] FIG. 3 is a hardware configuration diagram of a service management device according to an embodiment of the present disclosure. 3, the service management device 1 is a computer equipped with hardware such as a CPU (Central Processing Unit) 101, a ROM (Read Only Memory) 102, a RAM (Random Access Memory) 103, a storage device 104, a communication module 105, and an input device 106. The terminal 2 and the fee server 3 are also computers equipped with similar hardware.

[0019] FIG. 4 is a functional block diagram of a service management device according to an embodiment of the present disclosure. The CPU 101 of the service management device 1 executes the service management program, which causes the service management device 1 to perform functions such as a reception unit 11, a group identification unit 12, a usage fee calculation unit 13, a data generation unit 14, a download control unit 15, and a service management unit 16.

[0020] The reception unit 11 receives, from a plurality of users, specification of service conditions. In the present disclosure, the reception unit 11 receives, from the terminals 2 of the plurality of users, specification of service conditions for the plurality of users for whom the service is rail travel, the service conditions including at least a section of travel, a period of travel, and a day of the week for travel.

[0021] The group identification unit 12 matches multiple users who use the service based on the usage conditions and identifies a user group including the matched multiple users. In the present disclosure, the group identification unit 12 matches multiple users who have specified usage conditions in which the usage section and usage period match but the days of the week for use are different, and identifies a user group including the matched multiple users.

[0022] The usage fee calculation unit 13 calculates the usage fee for each of the multiple users included in the user group based on the usage conditions. In the present disclosure, the usage fee calculation unit 13 calculates the usage fee for each of the multiple users based on the usage conditions for each of the multiple users.

[0023] The data generation unit 14 generates service provision proof data that enables each of the multiple users to use a service according to the usage conditions based on payment of the usage fee for each of the multiple users. In the present disclosure, the data generation unit 14 generates commuter pass data for railway use according to the usage fee for the service for each of the multiple users as the service provision proof data.

[0024] The download control unit 15 controls so that the commuter pass data can be downloaded to each user's terminal 2. In the present disclosure, the download control unit 15 transmits to the terminal 2 the commuter pass data, which is an example of service provision proof data.

[0025] The service management unit 16 performs various processes when a user uses a service. In the present disclosure, the service management unit 16 acquires commuter pass data from the terminal 2 when using a train, and determines whether or not the service can be used.

[0026] FIG. 5 is a diagram illustrating an example of a user management table according to an embodiment of the present disclosure. The service management device 1 acquires the terms of use for railway services from the terminals 2 of multiple users, such as users A, B, C, D, E, F, and G. The terms of use include the section of use (boarding section), the day of use, and the period of use. The day of use is an example of the timing of use. The service management device 1 matches multiple users who have specified terms of use that match the section of use and the period of use but different days of use, identifies a user group including the matched multiple users, and assigns a group ID (group identifier). The service management device 1 calculates the usage fee for all users included in the group (group fee) and the usage fee for each user (user fee). It also generates commuter pass data for each user and stores this data in the user management table.

[0027] FIG. 6 is a diagram illustrating a processing flow of the service management device according to an embodiment of the present disclosure. Next, the processing flow of the service management device will be explained step by step.

[0028] <Action 1: Recruiting commuter pass sharing service users> A user who wishes to use the commuter pass sharing service installs a service app on their own terminal 2, which includes authentication functions for using the service, commuter pass functions, and usage fee payment functions. The user uses the service app to operate the service management device 1 on the cloud service via the 4G / 5G network to send a commuter pass sharing service registration request, which includes usage conditions such as the desired usage section, day of use, and usage period. Terminal 2 sends the sharing service registration request to service management device 1. The sharing service registration request may include identifiers of the user and terminal 2.

[0029] <Action 2: Registering in the database> The reception unit 11 of the service management device 1 receives sharing service registration requests from multiple users' terminals 2 (step S101). The reception unit 11 receives identifiers of the users and terminals 2 and usage conditions (usage section, usage day, usage period) included in the sharing service registration requests, and registers them in the database 4 (step S102).

[0030] <Action 3: Forming a group by matching> The group identification unit 12 of the service management device 1 matches multiple users who use the railway sharing service based on the usage conditions contained in the database 4, and identifies a user group including the matched multiple users (step S103). Specifically, the group identification unit 12 matches users who specify the same usage section, the same usage period, and different usage days as usage conditions based on the usage conditions, and identifies one group. The number of people included in a group may be limited to a predetermined number. For example, as shown in FIG. 5, the group identification unit 12 matches users A, B, and C who use the same usage section (Yokohama Station to Tokyo Station), the same usage period (the month of April), and different usage days, and identifies them as a group to which an identifier of group 1 is assigned. The group identification unit 12 registers the identifier of group 1 by linking it to the identifiers of users A, B, and C registered in the database 4. The group identification unit 12 instructs the usage fee calculation unit 13 to calculate the usage fee for each user (user A, user B, and user C) using the sharing service.

[0031] <Step 4: Calculating the fee> The usage fee calculation unit 13 calculates the usage fee for each user (user A, user B, user C) based on the usage conditions of each user in response to the usage fee calculation instruction (step S104). For example, the usage fee calculation unit 13 determines the usage fee for each user through a predetermined calculation process based on the monthly commuter pass fare and the usage conditions of each user in the group. The determined usage fee is registered in the database 4. More specifically, the usage fee calculation unit 13 queries the fare server 3 for the commuter pass fare for the usage period (one month) for the section of use indicated by the usage conditions (e.g., Yokohama Station to Tokyo Station) and obtains the commuter pass fare (14,640 yen) from the fare server 3. The usage fee calculation unit 13 associates the commuter pass fare with the identifier of group 1 and registers it as the group fare (the usage fee for all users in the group). In the present disclosure, because each user in the group uses the train on a different day of the week, the usage fee for all users in the group is the commuter pass fare for one user. However, this is not limited to this example. For example, the group fare may be calculated by multiplying the commuter pass fare for one user by a predetermined percentage. The usage fee calculation unit 13 then divides the group fee by the number of users in the group and determines the resulting value as the user fee for each user in the sharing service. That is, as shown in FIG. 6, the user fee for each user in Group 1 (usage area: Yokohama to Tokyo / usage period: 1 month) may be set at 4,880 yen. If the number of days per week used by each user in Group 1 differs, a fee proportional to the number of days per week may be set. For example, User A uses the service two days per week (Monday and Wednesday), User B uses the service two days per week (Tuesday and Thursday), and User C uses the service three days per week (Friday, Saturday, and Sunday). In this case, the user fees for Users A and B may be calculated as 2 / 7 of the group fee, and User C's user fee may be calculated as 3 / 7 of the group fee.

[0032] The fee server 3 may have the function of the usage fee calculation unit 13 that calculates the user fee described above, and the fee server 3 may calculate the user fee for each user in the same way. In this case, the fee server 3 may register the user fee for each user in the database 4. The usage fee calculation unit 13 instructs the fee server 3 to perform a payment process including the user's identifier and the user fee for that user's usage period. Based on the payment process instruction, the fee server 3 performs a payment process based on the user fee for each user's usage period (step S105). The payment process may use known technology. The usage fee calculation unit 13 records a payment completion flag in the database 4, linking it to the identifier of the user for whom the payment process by the fee server 3 has been completed.

[0033] <Action 5: Issuing a commuter pass> The data generation unit 14 of the service management device 1 checks whether or not a payment completion identifier for each user is recorded in the database 4, and generates commuter pass data for the user to whom the payment completion identifier has been assigned (step S106). The commuter pass data may include information such as the commuter pass identifier, issuance date and time, user identifier (such as name and date of birth), usage conditions (usage section, usage period, and day of week for use), and usage fee. After detecting that payment completion identifiers have been assigned to all users in a group, the data generation unit 14 may generate commuter pass data for each user in the group. This processing by the data generation unit 14 is an example of processing for generating commuter pass data for railway use according to the usage conditions of each service for multiple users.

[0034] The data generation unit 14 instructs the download control unit 15 to start downloading the commuter pass data for the user for which it generated the data. The download control unit 15 controls the commuter pass data so that it can be downloaded to each user's terminal (step S107). For example, the download control unit 15 may send the commuter pass data to each user's terminal 2. Alternatively, the download control unit 15 may store the commuter pass data in a download data storage area in the database 4 so that the commuter pass data can be downloaded based on access from the terminal 2, or perform setting processing to enable various downloads. Each terminal 2 then downloads the commuter pass data based on user operations, etc. As a result, the terminal 2 stores the commuter pass data.

[0035] When a user travels by train in accordance with the terms of use, the user holds terminal 2 over the ticket gate device installed at the ticket gate. Terminal 2 is equipped with an RFID (Radio Frequency Identification) function, which is activated based on a radio signal transmitted from the ticket gate device. Terminal 2 uses the RFID function to transmit commuter pass data to the ticket gate device. The ticket gate device transmits a passage determination request to service management device 1, which includes information such as the commuter pass data, the ticket gate device identifier, and the date and time. Service management device 1 acquires the passage determination request from the ticket gate device. Service management unit 16 determines whether or not to allow passage through the ticket gate based on the terms of use included in the commuter pass data in the passage determination request. For example, based on the usage section and ticket gate device identification information included in the terms of use, if the usage section is to be used, the date and time are within the usage period, and the day of use matches today's day of the week, service management unit 16 determines that passage is permitted. Service management unit 16 then transmits a passage determination result indicating whether or not passage is permitted to the ticket gate device. If the result of the pass-through determination indicates that the ticket gate is permitted to pass through, the ticket gate performs an action to permit the ticket gate to pass through (such as outputting a sound indicating that the ticket gate is permitted to pass through).If the result of the pass-through determination indicates that the ticket gate is not permitted to pass through, the ticket gate performs an action to permit the ticket gate to pass through (such as closing the gate flap).

[0036] The processing of the service management unit 16 may be performed by the ticket gate device. That is, based on the usage conditions received by the ticket gate device from the terminal 2, if the usage section is used based on the usage section and the identification information of the ticket gate device, the date and time is within the usage period, and the day of use matches the current day of the week, it may be determined that passage is permitted.

[0037] According to the processing of the service management device 1 described above, each user can purchase commuter pass data at a discounted usage fee based on the terms of use, which will increase the use of commuter pass sharing services that group together users who use the service on different days of the week. This will enable the leveling of users who use the train on each day of the week. Furthermore, according to the processing of the service management device 1 described above, each user can purchase commuter pass data at a discounted usage fee based on the terms of use, which will allow each user to use the train using a commuter pass at a reasonable fare, which will increase the number of people using the train.

[0038] In the above process, the group identification unit 12 matches multiple users who have the same usage section, the same usage period, and different usage days as the usage conditions based on the usage conditions, and identifies one group. However, the group identification unit 12 may also match users who have the same usage section, the same usage period, and different usage times as the usage conditions based on the usage conditions, and identify one group. Alternatively, the group identification unit 12 may match multiple users who have the same usage section, the same usage period, and different usage days and different usage times as the usage conditions based on the usage conditions, and identify one group. This will increase the use of commuter pass sharing services, which group users who use the service at different times and on different days of the week into one group. This will enable the distribution of train users on each day of the week to be more evenly distributed.

[0039] In the above process, the service management device 1 receives from multiple users specification of usage conditions, including at least the timing of use for trains, matches multiple users with different usage timings based on the usage conditions, identifies a user group including the matched multiple users, calculates the railway usage fee for each of the multiple users included in the user group based on the usage conditions, and generates commuter pass data that allows each of the multiple users to use the railway in accordance with the usage conditions based on the payment of the usage fee for each of the multiple users. However, the service management device 1 may target services other than railway use. For example, to implement a commuter pass sharing service for other public transportation such as buses, the service management device 1 may match multiple users based on the bus usage conditions to identify a group, and similarly generate and issue commuter pass data based on the usage conditions.

[0040] FIG. 7 is a diagram illustrating another configuration of the service management device according to an embodiment of the present disclosure. FIG. 8 is a diagram showing a processing flow in another configuration of the service management device according to an embodiment of the present disclosure. The service management device 1 includes a reception unit 71, a group identification unit 72, a usage fee calculation unit 73, and a data generation unit 74. The accepting means accepts from a plurality of users the specification of the conditions for using the service, including at least the timing of using the service (step S701). The group identification means matches a plurality of users who have different usage timings based on the usage conditions, and identifies a user group including the matched plurality of users (step S702). The usage fee calculation means calculates the usage fee for the service for each of the multiple users included in the user group based on the usage conditions (step S703). The data generating means generates service provision proof data that enables each of the plurality of users to use the service according to the usage conditions, based on payment of the usage fee by each of the plurality of users (step S704).

[0041] Although the present disclosure has been described above with reference to the embodiments, the present disclosure is not limited to the above-described embodiments. Various modifications that can be understood by those skilled in the art can be made to the configuration and details of the present disclosure within the scope of the present disclosure. Furthermore, each embodiment can be combined with other embodiments as appropriate.

[0042] Some or all of the above-described embodiments can be described as, but are not limited to, the following supplementary notes.

[0043] (Appendix 1) a receiving means for receiving, from a plurality of users, designations of service use conditions including at least the timing of use of the service; a group specifying means for matching a plurality of users who have different usage timings based on the usage conditions and specifying a user group including the matched plurality of users; a usage fee calculation means for calculating a usage fee for the service for each of the plurality of users included in the user group based on the usage conditions; a data generating means for generating service provision proof data that enables each of the plurality of users to use the service according to the usage conditions, based on payment of a usage fee by each of the plurality of users; A service management device comprising:

[0044] (Appendix 2) The receiving means receives, from the plurality of users, specification of the use conditions for the plurality of users for which the service is rail use, the use conditions including at least a section to be used, a period of use, and a day of the week to be used. 2. The service management device of claim 1.

[0045] (Appendix 3) The group identification means matches the plurality of users who have specified usage conditions in which the usage section and the usage period match and the days of the week in which the usage indicates the usage timing are different, and identifies a user group including the matched plurality of users. 3. The service management device according to claim 2.

[0046] (Appendix 4) The usage fee calculation means calculates a usage fee for each of the plurality of users based on the usage conditions of each of the users. 4. The service management device of claim 3.

[0047] (Appendix 5) The data generation means generates commuter pass data for use of the railway in accordance with the terms of use of the service for each of the plurality of users. 5. The service management device of claim 4.

[0048] (Appendix 6) download control means for controlling downloading of the commuter pass data to the terminal device of each of the users; 6. The service management device according to claim 5, comprising:

[0049] (Appendix 7) The receiving means receives, from the plurality of users, specification of the use conditions for the plurality of users for which the service is rail use, the use conditions including at least a section to be used, a period of use, and a time of use. 2. The service management device of claim 1.

[0050] (Appendix 8) The group identification means matches the plurality of users who have specified use conditions in which the use section and the use period match and the use time indicating the use timing is different, and identifies a user group including the matched plurality of users. 8. The service management device of claim 7.

[0051] (Appendix 9) Accepting specifications of terms of use of the service, including at least the timing of use of the service, from a plurality of users; matching a plurality of users who have different usage timings based on the usage conditions, and identifying a user group including the matched plurality of users; calculating a fee for using the service for each of the plurality of users included in the user group based on the terms of use; Based on payment of a usage fee by each of the plurality of users, service provision proof data is generated that allows each of the plurality of users to use the service according to the usage conditions. Service management methods.

[0052] (Appendix 10) The use conditions of the plurality of users for which the use of railways is the service are accepted from the plurality of users, and the use conditions include at least a section of use, a period of use, and a day of use. 9. A service management method as set forth in claim 9.

[0053] (Appendix 11) Matching the plurality of users who have specified usage conditions in which the usage section and the usage period match and the days of the week that indicate the usage timing are different, and identifying a user group including the matched plurality of users. 11. A service management method as set forth in claim 10.

[0054] (Appendix 12) Calculating a usage fee for each of the plurality of users based on the usage conditions for each of the users 12. The service management method according to claim 11.

[0055] (Appendix 13) Generate commuter pass data for use of the railway in accordance with the use conditions of the service for each of the plurality of users 13. The service management method of claim 12.

[0056] (Appendix 14) Controlling the commuter pass data so that it can be downloaded to the terminal device of each of the users. 14. The service management method of claim 13.

[0057] (Appendix 15) The use conditions of the plurality of users for which the service is rail use are accepted from the plurality of users, and the use conditions include at least a section of use, a period of use, and a time of use. 9. A service management method as set forth in claim 9.

[0058] (Appendix 16) Matching the plurality of users who have specified usage conditions in which the usage section and the usage period match and the usage time indicating the usage timing are different, and identifying a user group including the matched plurality of users. 16. The service management method of claim 15.

[0059] (Appendix 17) A computer of the service management device, a receiving means for receiving, from a plurality of users, designations of service use conditions including at least the timing of use of the service; a group identification means for matching a plurality of users who have different usage timings based on the usage conditions and identifying a user group including the matched plurality of users; a usage fee calculation means for calculating a usage fee for the service for each of the plurality of users included in the user group based on the usage conditions; a data generating means for generating service provision proof data that enables each of the plurality of users to use the service according to the usage conditions, based on payment of a usage fee by each of the plurality of users; A program that functions as a

[0060] (Appendix 18) The receiving means receives, from the plurality of users, specification of the use conditions for the plurality of users for which the service is rail use, the use conditions including at least a section to be used, a period of use, and a day of the week to be used. 17. The program described in Appendix 17.

[0061] (Appendix 19) The group identification means matches the plurality of users who have specified usage conditions in which the usage section and the usage period match and the days of the week in which the usage indicates the usage timing are different, and identifies a user group including the matched plurality of users. 18. The program described in Appendix 18.

[0062] (Appendix 20) The usage fee calculation means calculates a usage fee for each of the plurality of users based on the usage conditions of each of the users. 19. The program described in Appendix 19.

[0063] (Appendix 21) The data generation means generates commuter pass data for use of the railway in accordance with the terms of use of the service for each of the plurality of users. 20. The program described in Appendix 20.

[0064] (Appendix 22) download control means for controlling downloading of the commuter pass data to the terminal device of each of the users; 22. The program of claim 21, comprising:

[0065] (Appendix 23) The receiving means receives, from the plurality of users, specification of the use conditions for the plurality of users for which the service is rail use, the use conditions including at least a section to be used, a period of use, and a time of use. 17. The program described in Appendix 17.

[0066] (Appendix 24) The group identification means matches the plurality of users who have specified use conditions in which the use section and the use period match and the use time indicating the use timing is different, and identifies a user group including the matched plurality of users. 23. The program described in Appendix 23. [Explanation of symbols]

[0067] 1. Service management device 2. Terminal 3. Fee Server 4. Database 11. Reception 12. Group Specific Section 13. Usage fee calculation section 14. Data generation section 15 Download control section 16. Service Management Department

Claims

1. a receiving means for receiving, from a plurality of users, designations of service use conditions including at least the timing of use of the service; a group specifying means for matching a plurality of users who have different usage timings based on the usage conditions and specifying a user group including the matched plurality of users; a usage fee calculation means for calculating a usage fee for the service for each of the plurality of users included in the user group based on the usage conditions; a data generating means for generating service provision proof data that enables each of the plurality of users to use the service according to the usage conditions, based on payment of a usage fee by each of the plurality of users; A service management device comprising:

2. The receiving means receives, from the plurality of users, specification of the use conditions for the plurality of users for which the service is rail use, the use conditions including at least a section to be used, a period of use, and a day of the week to be used. The service management device according to claim 1 .

3. The group identification means matches the plurality of users who have specified usage conditions in which the usage section and the usage period match and the days of the week in which the usage indicates the usage timing are different, and identifies a user group including the matched plurality of users. The service management device according to claim 2 .

4. The usage fee calculation means calculates a usage fee for each of the plurality of users based on the usage conditions of each of the users. The service management device according to claim 3 .

5. The data generation means generates commuter pass data for use of the railway in accordance with the terms of use of the service for each of the plurality of users. The service management device according to claim 4 .

6. download control means for controlling downloading of the commuter pass data to the terminal device of each of the users; The service management device according to claim 5 , comprising:

7. The receiving means receives, from the plurality of users, specification of the use conditions for the plurality of users for which the service is rail use, the use conditions including at least a section to be used, a period of use, and a time of use. The service management device according to claim 1 .

8. The group identification means matches the plurality of users who have specified use conditions in which the use section and the use period match and the use time indicating the use timing is different, and identifies a user group including the matched plurality of users. The service management device according to claim 7.

9. Accepting specifications of terms of use of the service, including at least the timing of use of the service, from a plurality of users; matching a plurality of users who have different usage timings based on the usage conditions, and identifying a user group including the matched plurality of users; calculating a fee for using the service for each of the plurality of users included in the user group based on the terms of use; Based on payment of a usage fee by each of the plurality of users, service provision proof data is generated that allows each of the plurality of users to use the service according to the usage conditions. Service management methods.

10. A computer of the service management device, a receiving means for receiving, from a plurality of users, designations of service use conditions including at least the timing of use of the service; a group identification means for matching a plurality of users who have different usage timings based on the usage conditions and identifying a user group including the matched plurality of users; a usage fee calculation means for calculating a usage fee for the service for each of the plurality of users included in the user group based on the usage conditions; a data generating means for generating service provision proof data that enables each of the plurality of users to use the service according to the usage conditions, based on payment of a usage fee by each of the plurality of users; A program that functions as a

Citation Information

Patent Citations

  • System for managing person and object information

    JP2002334162A