Server

A server system manages digital ticket lending and borrowing, providing financial benefits to all stakeholders by adjusting fees based on demand and usage patterns, optimizing revenue distribution among lenders, borrowers, and issuers.

JP2024165519AActive Publication Date: 2024-11-28TOYOTA JIDOSHA KK
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
JP2023081781
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-05-17
Publication Date
2024-11-28
Estimated Expiration
2043-05-17

AI Technical Summary

Technical Problem

Existing systems do not effectively provide benefits to all stakeholders involved in the lending and borrowing of digital tickets, including the user who lends, borrows, and issues the tickets.

Method used

A server system that manages digital ticket lending and borrowing, allowing users to register and lend digital tickets, sets usage fees, and distributes these fees among the lender, borrower, and issuer, with fee adjustments based on demand, congestion, and time.

Benefits of technology

The system provides financial benefits to all stakeholders by allowing users to lend and borrow digital tickets efficiently, while adjusting fees to manage demand and usage patterns, thereby optimizing revenue distribution.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024165519000001_ABST
    Figure 2024165519000001_ABST
Patent Text Reader

Abstract

To provide a server capable of benefitting all of a lender of a digital ticket, a borrower of the digital ticket, and an issuer of the digital ticket.SOLUTION: A processor 101 of a server 100 receives processing of registering a digital ticket 420 in a database 104 by a user 210 (a first user) who owns the digital ticket 420. Further, the processor 101 requests a user 310 (a second user) who wants to borrow the digital ticket 420 registered in the database 104, to pay a usage fee of the digital ticket 420. Further, when the user 310 pays the usage fee, the processor 101 lends the digital ticket 420 from the user 210 to the user 310. Furthermore, the processor 101 distributes a part of the usage fee to the user 210, and distributes another part of the usage fee to a company 410 (an issuer).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 server. [Background technology]

[0002] In the commuter pass processing method disclosed in JP 2008-084346 A (Patent Document 1), a company that has concluded a contract with a railway company lends contactless commuter passes to its employees. [Prior art documents] [Patent documents]

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

[0004] It is conceivable that a user may purchase a digital ticket (such as a digital commuter pass or digital coupon ticket) that can be used multiple times and then share part of it with other users (lending it to other users). In such a case, it is desirable for there to be benefits for the user who lends the digital ticket (ticket lender), the user who borrows the digital ticket (ticket borrower), and the ticket issuer (transportation company or other operator).

[0005] The present disclosure has been made to solve the above-mentioned problems, and its purpose is to provide a server that can provide benefits to all parties: the digital ticket lender, the digital ticket borrower, and the digital ticket issuer. [Means for solving the problem]

[0006] A server according to one aspect of the present disclosure includes a database in which digital tickets issued by an issuer are registered, and a processor that manages lending and borrowing of digital tickets among multiple users. The processor accepts a process for registering the digital ticket in the database by a first user who owns the digital ticket, requests a second user who wishes to borrow the digital ticket registered in the database to pay a usage fee for the digital ticket, and, when the second user pays the usage fee, lends the digital ticket from the first user to the second user, distributes a portion of the usage fee to the first user, and distributes the other portion of the usage fee to the issuer.

[0007] In a server according to one aspect of the present disclosure, as described above, when a second user borrows a digital ticket registered in the server's database, a usage fee is paid to each of the first user and the issuer. This allows the second user to use the digital ticket by borrowing it from the first user. Furthermore, each of the first user and the issuer can obtain a financial benefit by lending the digital ticket to the second user. Therefore, benefits can be provided to all of the lender of the digital ticket (first user), the borrower of the digital ticket (second user), and the issuer of the digital ticket.

[0008] In the server according to the above aspect, the processor preferably determines the usage fee according to at least one of the following: the supply and demand balance of the digital ticket, the degree of congestion at the facility that can be used with the digital ticket, the time period during which the digital ticket is used, and the weather. With this configuration, the usage fee for the digital ticket can be appropriately changed based on each of the above conditions. As a result, the usage fee can be set to an appropriate amount.

[0009] In this case, preferably, the processor sets a higher usage fee the greater the demand for digital ticket supply or the more crowded the facility that can be used with the digital ticket is. By configuring in this manner, the demand for digital tickets can be reduced by setting the usage fee higher when the demand for digital tickets is high. Also, by setting the usage fee higher when the facility is crowded, the store can be prevented from becoming even more crowded.

[0010] In the server according to the above aspect, the processor preferably invites second users by publishing the digital ticket registered in the database on application software or a bulletin board. With this configuration, second users can be invited efficiently.

[0011] In this case, the processor preferably limits the range of disclosure of the digital ticket for recruiting second users to a range specified by the first user. In this configuration, the digital ticket can be shared among a limited community such as the first user's family and colleagues. The digital ticket can also be used for employee benefits.

[0012] According to the present disclosure, it is possible to provide benefits to the digital ticket lender, the digital ticket borrower, and the digital ticket issuer. [Brief description of the drawings]

[0013] [Figure 1] FIG. 1 is a diagram illustrating a configuration of a ticket management system according to an embodiment. [Diagram 2] FIG. 11 is a sequence diagram illustrating control of a ticket management system according to an embodiment. [Diagram 3] FIG. 13 is a diagram showing the scope of disclosure of information for inviting rental of a digital ticket according to one embodiment. [Figure 4]FIG. 2 illustrates a relationship between demand for digital tickets and fees for using digital tickets according to one embodiment. [Diagram 5] FIG. 13 is a diagram showing the relationship between the degree of congestion of a store where a digital ticket can be used and the usage fee for the digital ticket according to a modified example of an embodiment. [Figure 6] FIG. 13 is a diagram showing the relationship between time and the usage fee of a digital ticket according to a modified example of an embodiment. [Figure 7] FIG. 13 is a diagram showing the relationship between weather (probability of precipitation) and the usage fee for a digital ticket according to a modified example of an embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0014] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings. In the drawings, the same or corresponding parts are denoted by the same reference characters, and the description thereof will not be repeated.

[0015] <Ticket management system configuration> 1 is a diagram illustrating an overall configuration of a ticket management system 1 according to an embodiment of the present disclosure. The ticket management system 1 includes a management server 100, a communication terminal 200 of a user 210, a communication terminal 300 of a user 310, and a server 400. The management server 100 is an example of a "server" in the present disclosure.

[0016] The management server 100 includes, for example, a processor 101, a memory 102, a communication unit 103, and a database 104.

[0017] The processor 101 is, for example, a microprocessor such as a CPU, an MPU, etc. The processor 101 manages the lending and borrowing of a digital ticket 420, which will be described later, between a plurality of users (for example, the user 210 and the user 310).

[0018] The memory 102 is a volatile memory such as a RAM. The processor 101 loads system programs and control programs read from a storage (not shown) of the management server 100 into the memory 102 and executes the programs to realize various processes.

[0019] The communication unit 103 includes a communication interface with a network such as the Internet. The communication unit 103 is configured to enable two-way communication with external devices of the management server 100 (for example, the communication terminal 200, the communication terminal 300, and the server 400).

[0020] The database 104 manages various data (such as a digital ticket 420 described below) handled in the ticket management system 1. The database 104 will be described in detail later.

[0021] The communication terminal 200 and the communication terminal 300 are terminals carried by the user 210 and the user 310, respectively. For example, each of the communication terminal 200 and the communication terminal 300 is a smartphone, a tablet, a smart watch, or the like. Note that each of the communication terminal 200 and the communication terminal 300 may be a non-portable communication terminal such as a PC (Personal Computer).

[0022] The server 400 is a server managed by a business operator 410 (e.g., a railroad company) that sells the digital ticket 420. The server 400 manages the sale of the digital ticket 420. Note that the digital ticket 420 may be sold by a sales platform that handles various types of tickets.

[0023] The user 210 purchases a digital ticket 420 from the business operator 410 using the communication terminal 200. For example, the user 210 purchases a digital ticket 420 that can be used multiple times (three times in FIG. 1). For convenience, FIG. 1 shows three digital tickets 420, which indicate that the digital ticket 420 can be used three times. Note that in the following explanation, an example is shown in which the digital ticket 420 is a digital coupon ticket with a limited number of uses, but the digital ticket 420 may also be a digital commuter pass with a limited period of use.

[0024] It is also assumed that the user 210 has used the communication terminal 200 to register the digital tickets 420 for the above three times in the database 104.

[0025] When the management server 100 receives a request to register the digital ticket 420 in the database 104, the management server 100 makes the information public so that the digital ticket 420 registered in the database 104 can be lent to other users. The disclosure of information will be described in detail later.

[0026] Here, it is assumed that the user 310 wishes to borrow the digital ticket 420 registered in the database 104 using the communication terminal 300. Specifically, the user 310 uses the communication terminal 300 to transmit information indicating that he / she wishes to borrow the digital ticket 420 to the management server 100. For example, it is assumed that the user 310 wishes to borrow one of the three digital tickets 420 registered in the database 104.

[0027] In this case, the processor 101 requests the user 310 to pay the usage fee for the digital ticket 420 through the communication unit 103. For example, the processor 101 may determine the usage fee to be a fee (1800 yen in FIG. 1) that is lower than the fee (e.g., 2000 yen) for purchasing only one digital ticket 420 and higher than the fee per use (e.g., 5000 yen / 3=1667 yen) for purchasing three digital tickets 420 (a coupon ticket). Doing so provides a financial benefit to the user 310. Details of how the processor 101 determines the usage fee will be described later.

[0028] When the user 310 pays the usage fee for the digital ticket 420, the processor 101 lends the digital ticket 420 registered in the database 104 to the user 310. In other words, the digital ticket 420 is lent from the user 210 to the user 310.

[0029] Here, it is desirable that there be benefits for the user 210 who lends out the digital ticket 420, the user 310 who borrows the digital ticket 420, and the business entity 410 that issues the ticket.

[0030] Therefore, in this embodiment, the processor 101 distributes a part of the usage fee to the user 210 and distributes another part of the usage fee to the business operator 410. This provides a financial benefit to each of the user 210 and the business operator 410. Furthermore, the user 310 benefits in that he or she can enjoy the digital ticket 420 only to the extent that he or she wishes to use it. Furthermore, when the digital ticket 420 is out of stock, the user 310 can use the digital ticket 420 by borrowing it from the user 210. This also provides a benefit to the user 310.

[0031] The amount paid to user 210 may be, for example, 90% of the fee paid by user 310. The amount paid to business operator 410 may be, for example, 10% of the fee paid by user 310. The ratio of distribution of the usage fee is not limited to the above example.

[0032] <Ticket management system sequence> Next, a control sequence regarding lending and borrowing of the digital ticket 420 by the ticket management system 1 will be described with reference to FIGS.

[0033] In step S 1 , a user 210 who is to be the lender of a digital ticket 420 uses a communication terminal 200 to carry out a process for purchasing the digital ticket 420 from a server 400 of a business entity 410 that is the issuer of the digital ticket 420 .

[0034] In step S2, the server 400 of the business operator 410 grants (transmits) the digital ticket 420 to the communication terminal 200 of the user 210 in response to the process in step S1.

[0035] In step S 3 , the user 210 uses the communication terminal 200 to perform a process for registering the purchased digital ticket 420 in the database 104 of the management server 100 .

[0036] In step S4, the management server 100 (processor 101) accepts registration of the digital ticket 420 in the database 104 in response to the process in step S3.

[0037] In step S5, the user 210 uses the communication terminal 200 to specify the disclosure range for soliciting rentals of the digital ticket 420 registered in the database 104. For example, the user 210 uses the communication terminal 200 to specify the above disclosure range by specifying the identification number (telephone number, email address, etc.) of the communication terminal 300 that publishes the above recruitment information and the attributes (place of employment, place of study, address, gender, age, etc.) of the user 310 that publishes the above recruitment information.

[0038] In step S6, the processor 101 publishes information indicating that the digital ticket 420 registered in the database 104 is being solicited for rental to the publication range specified in step S5. Specifically, the processor 101 publishes the digital ticket 420 registered in the database 104 on application software or a bulletin board available on the communication terminal 300 of the user 310 corresponding to the above publication range. In the example shown in Fig. 3, an image 320 indicating that the digital ticket 420 is being solicited for rental is displayed on the display of the communication terminal 300 within the publication range (in the example shown in Fig. 3, "Ticket for rental" is displayed).

[0039] For example, the processor 101 may transmit, via the communication unit 103, a password for accessing the application software or the bulletin board (or a password for obtaining a digital ticket 420 in the application software or the bulletin board) only to the communication terminal 300 of the user 310 corresponding to the above-mentioned disclosure range.

[0040] In step S7, the user 310 uses the communication terminal 300 to transmit information indicating that he / she wishes to borrow the digital tickets 420 registered in the database 104 to the management server 100. At this time, the user 310 specifies the range of the digital tickets 420 registered in the database 104 that he / she wishes to borrow. For example, the user 310 may wish to borrow one digital ticket 420 out of the three digital tickets 420 registered in the database. In other words, the user 310 may wish to borrow only a portion of the digital tickets 420 registered in the database.

[0041] Furthermore, as described above, the digital ticket 420 may be a free pass or a commuter pass that can be used any number of times within a certain period. In this case, the user 310 may transmit to the management server 100 information indicating the period, number of days, or time period during which the user wishes to borrow the digital ticket 420, within the validity period of the digital ticket 420. Furthermore, when the user 210 registers the digital ticket 420 in the database 104, the user 210 may be able to specify the period during which the digital ticket 420 can be lent, etc.

[0042] In step S8, processor 101 determines the usage fee according to the supply and demand balance of digital ticket 420. Specifically, processor 101 sets a higher usage fee as the demand for the supply of digital ticket 420 increases. Processor 101 may determine the usage fee for digital ticket 420 before it is published in the application software or on the bulletin board. In this case, processor 101 may determine the usage fee according to the current or past supply and demand balance of the same or similar digital ticket.

[0043] Fig. 4 is a graph showing the usage fee against the demand for digital ticket 420. Fig. 4 illustrates an example in which the usage fee increases in steps as the demand for digital ticket 420 increases. Note that the usage fee may increase linearly as the demand for digital ticket 420 increases.

[0044] Here, the processor 101 may set an upper limit for the usage fee (see the dashed line in FIG. 4). For example, the processor 101 may set an upper limit so that the usage fee is less than the fee paid when the digital ticket 420 is purchased in a normal manner (for example, when the digital ticket 420 is purchased for one use through the server 400).

[0045] Furthermore, the processor 101 may determine the magnitude of demand based on the number of people who applied to use the digital ticket 420 relative to the number of people who are able to use the digital ticket 420 registered in the database 104. Note that the number of people who are able to use the digital ticket 420 is three people when, for example, three digital tickets 420 are registered in the database 104. Also, the number of people who are able to use the digital ticket 420 is one person when the digital ticket 420 is a commuter pass or a free pass.

[0046] Referring back to FIG. 2, in step S9, the processor 101 requests the user 310 through the communication unit 103 to pay the usage fee determined in step S8.

[0047] In step S10, the user 310 pays the usage fee requested in step S9 to the management server 100.

[0048] In step S11, the processor 101 distributes a portion of the usage fee paid in step S10 to the user 210. The processor 101 also distributes a remaining portion of the usage fee paid to the business operator 410 (server 400). The ratio between the amount distributed to the user 210 and the amount distributed to the business operator 410 may be changed appropriately according to a predetermined condition (for example, the supply and demand balance of the digital ticket 420) or may be a fixed value. The amount distributed to the business operator 410 may also be a fixed amount.

[0049] As described above, in this embodiment, when the user 310 who wishes to borrow the digital ticket 420 registered in the database 104 pays the usage fee, the processor 101 lends the digital ticket 420 from the user 210 to the user 310. In addition, the processor 101 distributes a part of the usage fee to the user 210, and distributes another part of the usage fee to the business operator 410. This allows the user 310 who wishes to use the digital ticket 420 temporarily to feel an advantage in that he or she can use the digital ticket 420 without purchasing it. This also allows financial benefits to be given to both the user 210 and the business operator 410.

[0050] In the above embodiment, an example has been shown in which the usage fee for the digital ticket 420 is determined according to the supply and demand balance of the digital ticket 420, but the present disclosure is not limited thereto. For example, as shown in Fig. 5, the usage fee may be determined according to the degree of congestion of a facility that can be used with the digital ticket 420. In the example shown in Fig. 5, an example is shown in which the usage fee increases in a stepwise manner as the degree of congestion increases. Note that the usage fee may increase linearly according to the degree of congestion.

[0051] The degree of congestion may be determined based on the time period when the digital ticket 420 is scheduled to be used by the user 310. The degree of congestion may also be determined based on events held around the facility. The degree of congestion may also be determined based on the weather. The degree of congestion may also be determined by combining these pieces of information.

[0052] The usage fee may also be determined based on the time period during which the digital ticket 420 is scheduled to be used by the user 310. In the example shown in Fig. 6, the usage fee is set higher during the morning work hours (e.g., 6:00 to 9:00) and the evening work hours (e.g., 17:00 to 21:00) than during other time periods. This allows the usage fee to be set relatively high during rush hour periods when many people use public transportation. The usage fee may also be set to change, for example, every hour.

[0053] The usage fee may also be determined based on the weather during the period when the digital ticket 420 is used by the user 310. In the example shown in FIG. 7, the usage fee decreases linearly as the probability of precipitation increases. This allows the usage fee to be relatively low when the weather is bad and few people go out. The usage fee may decrease in steps according to the probability of precipitation. The usage fee may also be determined according to changes in temperature. For example, the usage fee may be low when the temperature is high (e.g., above 30° C.) or when the temperature is low (e.g., below 5° C.).

[0054] In the above embodiment, an example has been shown in which the range in which information for inviting users to borrow digital tickets 420 is made public is limited, but the present disclosure is not limited to this. The range does not have to be limited. For example, the information may be made public to all users 310, while only users 310 within a specified range may be able to obtain digital tickets. Also, all users 310 may be able to obtain digital tickets.

[0055] In the above embodiment, the digital ticket 420 that can be used in transportation facilities managed by a railway company or the like is shown as an example, but the present disclosure is not limited to this. For example, the lending and borrowing of digital tickets that can be used in entertainment facilities such as amusement parks and live music venues may be managed.

[0056] In the above embodiment, the user 310 borrows a part of the digital ticket 420 registered in the database 104 (a part of the number of times that can be used), but the present disclosure is not limited to this. For example, the user 310 may borrow all of the digital tickets 420 registered in the database 104.

[0057] In the above embodiment, an example has been described in which the digital ticket 420 that can be used multiple times is registered in the database 104, but the present disclosure is not limited to this. The digital ticket 420 that can be used only once may also be registered in the database 104.

[0058] The configurations (processing) of the above embodiment and the above modified examples may be combined with each other.

[0059] The embodiments disclosed herein should be considered to be illustrative and not restrictive in all respects. The scope of the present disclosure is defined by the claims, not by the description of the embodiments described above, and is intended to include all modifications within the meaning and scope of the claims. [Explanation of symbols]

[0060] 100 server (management server), 101 processor, 104 database, 210 user (first user), 310 user (second user), 410 business operator (issuer).

Claims

1. A database in which digital tickets issued by an issuer are registered; a processor for managing the lending and borrowing of the digital ticket among a plurality of users; The processor, accepting a transaction by a first user who owns the digital ticket to register the digital ticket in the database; requesting a second user who wishes to rent the digital ticket registered in the database to pay a usage fee for the digital ticket; lending the digital ticket from the first user to the second user when the second user has paid the usage fee; A server that distributes a portion of the usage fee to the first user and distributes another portion of the usage fee to the publisher.

2. The server of claim 1 , wherein the processor determines the usage fee based on at least one of the supply and demand balance of the digital ticket, the degree of congestion of the facility that can be used with the digital ticket, the time of day when the digital ticket is used, and the weather.

3. The server of claim 2 , wherein the processor increases the usage fee the greater the demand for the supply of the digital ticket or the more crowded a facility available with the digital ticket is.

4. The server according to any one of claims 1 to 3, wherein the processor recruits the second users by publishing the digital ticket registered in the database on application software or a bulletin board.

5. The server according to claim 4 , wherein the processor limits a range of disclosure of the digital ticket for recruiting the second user to a range designated by the first user.

Citation Information

Patent Citations

  • Information management device, information management system, information management method, and information management program

    JP2017049703A

  • Information processing apparatus, information processing method, and program

    JP2020013383A

  • Fee calculation device, fee calculation method and computer program

    JP2021107968A

  • Commuter pass processing method, commuter pass processing system, and non-contact type commuter pass

    JP2008084346A