JP5844877B1 - Rights management system and program - Google Patents

Abstract

Provided is a rights management system in which a transferor does not need to designate an assignee in a right transfer procedure. A right management system receives a transferable display data to a transferee terminal, receives a transfer application data from the transferee terminal, and receives status inquiry data from the transferee terminal. A function to transmit the transfer presentation data to the assignee terminal 30 in accordance with the transfer application data and the status inquiry data, a function to receive transfer request data from the transferee terminal 30, and the transfer application data and transfer request data. And a function for establishing transfer in response. [Selection] Figure 1

Description

  The present invention relates to a rights management system and program.

  A system that performs processing related to the transfer of rights between an assignor and an assignee is known. An example of such a system is described in US Pat.

JP 2009-9181 A

  However, in the prior art, the assignor needs to designate the assignee, which is inconvenient for both the assignor and the assignee. That is, the transferor must search for the transfer partner before applying for the transfer, and the transferee cannot request the transfer of rights unless specified by the transferor.

  The present invention has been made to solve such a problem, and an object of the present invention is to provide a rights management system that makes it unnecessary for a transferor to designate a transferee in a transfer procedure.

To solve the problems described above, the rights management system according to the present invention, to support the assignment of the right between the Yuzuru Watarihito and assignee, a rights management system,
The rights management system is communicable with an assignee terminal used by the assignee and an assignee terminal used by the assignee,
The rights management system includes:
A function of transmitting transferable display data relating to a right owned by the transferor to the transferor terminal;
A function of receiving transfer application data relating to the right from the transferor terminal;
A function of receiving status inquiry data related to the right from a terminal;
A function for determining a purchase deadline related to the right, and when the purchase deadline has passed, the terminal as the transferee terminal, in response to the transfer application data and the status inquiry data, to the transferee terminal , A function of transmitting transfer presentation data relating to the right;
When the purchase deadline has passed, the terminal as the transferee terminal, and from the transferee terminal, the function of receiving transfer request data related to the right;
A function for establishing the transfer of the right from the transferor to the transferee according to the transfer application data and the transfer request data when the purchase deadline has passed;
A function of transmitting purchase presentation data relating to the right to the transferor terminal when the purchase deadline has not elapsed, and using the terminal as the transferor terminal;
Is provided.

The transfer presentation data is
An indication identifying the right;
An assignment request indication indicating that it is possible to request the assignment of the right;
It may also include a display indicating a transfer request operation object to be operated at the transferee terminal in order to transmit the transfer request data.
The transferable display data is
An indication identifying the right;
A transfer request indication indicating that it is possible to apply for the transfer of the right;
And a display indicating a transfer application operation object to be operated in the transferor terminal to transmit the transfer application data .
It is capable of receiving the transfer request data from a plurality of transfer people according to the same rights,
The function for establishing transfer may be a function for establishing transfer in order from the previously received transfer application data when there are a plurality of transfer application data.
The right may be a right to run in a long distance running tournament.

  The program according to the present invention causes a computer to function as the above-described rights management system.

  According to the rights management system and program according to the present invention, the transferor can transmit the transfer application data without designating the transferee, and the transferee voluntarily transmits the status inquiry data to present the transfer. Since data can be received, there is no need for the transferor to designate the transferee, and the convenience of both parties is improved.

It is a figure which shows the structure containing the rights management system which concerns on Embodiment 1 of this invention. It is a figure which shows the outline | summary of transfer of the right which the rights management system of FIG. 1 handles. It is a figure which shows the example of a structure of the transfer presenter list | wrist contained in the convention data of FIG. It is a figure which shows the example of the period when the purchase of a right and the request for transfer are possible respectively. 2 is a flowchart illustrating an example of a flow of processing for acquiring a right in the right management system of FIG. 1. It is a figure which shows the example of normal entry presentation data. 2 is a flowchart showing an example of a flow of processing for applying for assignment of rights in the rights management system of FIG. 1. It is a figure which shows the example of the entry log | history data containing transferable display data. It is a figure which shows the example of the entry history data which does not contain transferable display data. It is a figure which shows the example of the entry history data which does not contain transferable display data. It is a figure which shows the example of exchange of the charge which generate | occur | produces with purchase and transfer of a right.

Embodiments of the present invention will be described below with reference to the accompanying drawings.
Embodiment 1 FIG.
FIG. 1 shows a configuration including a rights management system 10 according to Embodiment 1 of the present invention. The rights management system 10 is a system that supports the transfer of rights among a plurality of rights entities. In the present embodiment, the right subject is a participant or a candidate who wants to participate in the long-distance running competition, and the right is a right to start in the long-distance running competition.

  The transferor terminal 20 is a computer used by a person who desires to transfer the right among the right owners. The transferee terminal 30 is a computer used by a person who desires transfer of rights.

  FIG. 2 shows an outline of the transfer of the rights (running rights) handled by the rights management system 10. First, Mr. A wishes to participate in a specific event of a specific competition, and purchases rights as a participant. This purchase is a procedure called entry, for example, and is not necessarily limited to a paid procedure.

  Then, for some reason, it is assumed that Mr. A no longer needs the right before the right is exercised (that is, before the convention is held). In this case, if Mr. B wants to participate in the same event of the same tournament, Mr. A may transfer his right to Mr. B. The rights management system 10 according to the present invention supports such assignment by managing rights.

  Returning to FIG. The rights management system 10, the transferee terminal 20, and the transferee terminal 30 are connected via a communication network N so that they can communicate with each other. That is, the rights management system 10 can communicate with other computers (for example, the assignee terminal 20 and the assignee terminal 30) via the communication network N.

  The rights management system 10 includes a configuration as a well-known computer, and includes a calculation unit 11 that performs calculation and a storage unit 12 that stores information. The calculation means 11 includes a CPU (Central Processing Unit), and the storage means 12 includes a storage medium such as a semiconductor memory and an HDD (Hard Disk Drive).

  Although not particularly illustrated, the right management system 10 includes an input unit, an output unit, and a network interface. The input means is means used by the user to input information, and is, for example, a mouse or a keyboard. The output means is means for outputting information to the user, such as a liquid crystal display or a printer.

  The configurations of the transferee terminal 20 and the transferee terminal 30 are not particularly illustrated, but include a configuration as a well-known computer in the same manner as the right management system 10.

  The storage means 12 of the right management system 10 can store the tournament data 40 and the participant data 50. The storage unit 12 stores a rights management program (not shown). The rights management program is executed by a computer (particularly computing means), thereby causing the computer to function as the rights management system 10 according to the present invention.

  The tournament data 40 includes information related to the rights to be transferred (in this embodiment, the right to start), information for identifying the rights (for example, tournament ID and event ID), and information related to the rights, Associate.

  Information related to the rights includes, for example, the date of the tournament, information indicating the owner of the rights (for example, an entry list including one or more participant IDs), information indicating the purchase deadline of the rights (for example, entry deadline), And information (for example, a transfer presenter list including one or more participant IDs) indicating a person who desires to transfer the right.

  Participant data 50 includes information regarding the owner of the right. In this embodiment, the right owner is a participant in a long distance running tournament. In this specification, “participants” include those who wish to participate and those who have wished to participate in the past. Participant data 50 associates information for identifying a participant (for example, a participant ID) with information related to the participant.

  The information related to the participant includes, for example, the participant name, information for identifying the right (for example, tournament ID and event ID), entry state, and payment state. The entry status represents the relationship between the participant and the rights. For example, participation is planned (a state in which the participant owns the right), a transfer application is in progress (the participant assigns the right he / she owns to another person). Desired but has not yet been transferred), transferred (participant has already transferred the rights he had previously) to another person, and failed to transfer (filed for transfer) The transfer deadline has passed without the transfer request appearing and the transfer has not been established. A person who has transferred the right to another person is not a “participant” after the transfer is established, but may be referred to as a participant in the present specification, including a person who has been a participant in the past.

  FIG. 3 shows an example of the configuration of the transfer presenter list 41 among the information included in the tournament data 40. The transfer presenter list 41 is configured as an ordered list, for example. The order is, for example, the order in which an application for assignment of rights (indication of desire to transfer the possessed rights to another person) has occurred.

  In the example of FIG. 3, a transfer presenter list 41 is defined for each of two events of a certain tournament. In the full marathon, Mr. A applied for the transfer first, followed by Mr. C, then D. In the half marathon, Mr. X applied for the transfer first, and then Mr. A applied for the transfer.

  In the present embodiment, when the transfer of rights is established, the transfer application relating to the transfer is deleted from the transfer presenter list 41. In other words, the transfer presenter list 41 includes only transfer applications that have not yet been transferred.

FIG. 4 shows an example of a period in which a normal entry (purchase of rights) to the tournament and a transfer request are possible. This period can be arbitrarily determined by the organizer of the event, for example.
FIG. 4 shows a normal entry start (purchase start) point, a normal entry deadline (purchase deadline) point, and a transfer deadline point. There is an upper limit on the number of participants that can participate in a tournament (or a specific event in the tournament). 4A is an example in the case where the participant has not reached the upper limit by the deadline of the normal entry, and FIG. 4B is an example in the case where the participant has reached the upper limit by the deadline of the normal entry. It is.

  Normally, right after the start of entry, the right can be purchased, but no transfer request is possible. In addition, if the deadline for regular entry is passed or the number of participants reaches the limit, the purchase deadline will be reached at that time, and on the contrary, the purchase of rights becomes impossible and the transfer of rights can be requested. It becomes. As described above, in the present embodiment, at any time, as a procedure for obtaining a right, at most one of purchase and assignment requests is possible.

The operation of the rights management system 10 configured as described above will be described below.
FIG. 5 is a flowchart illustrating an example of a processing flow for acquiring a right in the right management system 10. In the present embodiment, acquisition of a right is realized by purchase or assignment of the right. The process shown in FIG. 5 is started in response to the right management system 10 receiving state inquiry data from another computer (for example, the assignee terminal 20 or the assignee terminal 30) (step S1).

  The status inquiry data is, for example, data for inquiring whether or not normal entry is possible or right transfer is possible for a specific event (s) of a specific event (s). It can be configured as an HTTP request containing a specific URL. The flowchart of FIG. 5 can be executed in parallel for each item, for example.

  The rights management system 10 determines whether the participant of the event has reached the capacity (step S2) and whether the normal entry deadline for the event has elapsed (step S3). This determination can be said to be a determination for determining a purchase deadline. As shown in FIG. 4, the purchase deadline is the normal entry deadline (purchase deadline) or when the participant reaches the capacity, whichever comes first.

  If the participant has not reached the capacity and is before the normal entry deadline, the right management system 10 is able to enter normally because the purchase deadline has not yet passed, and there is no desire to transfer. It is determined that it is possible (step S4, but specific processing need not be executed in this step). In this case, the right management system 10 transmits normal entry presentation data related to the right (step S5). Here, the terminal that is the destination of the normal entry presentation data corresponds to the transferor terminal 20, for example.

  FIG. 6 shows an example of normal entry presentation data. The normal entry presentation data can be configured to be included in an HTTP response including HTML data for displaying a screen as shown in FIG. 6, for example. That is, if the state inquiry data in step S 1 is transmitted from the assignor terminal 20, the rights management system 10 transmits normal entry presentation data to the assignor terminal 20. On the other hand, if the status inquiry data in step S <b> 1 is transmitted from the assignee terminal 30, the right management system 10 transmits normal entry presentation data to the assignee terminal 30. The assignor terminal 20 or the assignee terminal 30 performs display in accordance with the received data, so that the participant (assigner or assignee) can see a screen as shown in FIG.

  It can be said that the normal entry presentation data is purchase presentation data indicating that the right can be purchased. A display for specifying the right (distance item and participation qualification in the example of FIG. 6) and a normal entry are displayed. Normal entry request display indicating that it can be desired ("Entry" button in the "Entry" column), and a normal entry request operation object ("Entry") to be operated on the computer to request a normal entry "Entry" button in the column). In the example of FIG. 6, a single button serves as both a normal entry desired display and a normal entry desired operation object.

  In the example of FIG. It is shown that regular entry is possible for 3 events. That is, no. For the third event, a button labeled “Entry” is displayed in the “Entry” column, so that the participant can know that a normal entry is possible for this event.

  In the example of FIG. It is shown that it is impossible to request transfer for the third event. That is, no. For the third event, a minus sign is displayed in the “transfer” column, so that the participant can know that it is impossible (at least at that time) to transfer this event.

  After step S5, although not specifically shown, the participant is no. I hope to participate in the 3rd event. Assume that the “Entry” button in the “Entry” column is operated for the third event. In response to this, the transferee terminal 20 transmits the normal entry request data relating to the right, and the right management system 10 receives this (step S6). The normal entry request data is, for example, data indicating that the button has been operated, and can be configured as an HTTP request including a specific URL, for example.

  After step S6, the rights management system 10 establishes the purchase of rights by the participant (step S7), and ends the process shown in FIG. A specific process for establishing a purchase can be appropriately designed by those skilled in the art. For example, it is realized by outputting purchase completion data indicating that the participant has purchased the right. The purchase completion data includes, for example, data for additionally associating the participant ID of the participant with the event of the tournament data 40 and information related to the participant in the participant data 50, and setting the entry status. Data for “participation schedule”. The participant ID can be appropriately specified by a known technique. For example, the rights management system 10 may request a login operation or the like before step S7.

  In steps S2 and S3, if the participant has reached the capacity or is after the normal entry deadline, the right management system 10 cannot normally enter because the purchase deadline has already passed. Yes, it is determined that the transfer request is possible (step S8, but it is not necessary to execute a specific process in this step).

  In this case, the right management system 10 determines whether there is transfer application data relating to the right (step S9). The transfer application data is data indicating that a certain participant (transferer) has applied for the transfer of the right, and is represented by, for example, a participant ID included in the transfer presenter list of the tournament data 40. In this case, if the transfer presenter list of the tournament data 40 corresponding to the right is not empty, it is determined that transfer application data exists.

  If the transfer application data does not exist, the right management system 10 ends the process of FIG. This is a situation where all participants who own the rights plan to participate on their own, there are no participants willing to transfer the rights to others, and therefore there is no room to accept new participants in that event. Corresponding to

  If transfer application data exists in step S9, the rights management system 10 transmits transfer presentation data relating to the rights (step S10). Here, the terminal that is the destination of the transfer presentation data corresponds to the transferee terminal 30, for example. Here, considering steps S1 and S9, it can be said that the rights management system 10 transmits the transfer presentation data relating to the right to the transferee terminal 30 in accordance with the transfer application data and the state inquiry data.

  FIG. 6 also shows an example of transfer presentation data. It can be said that the transfer presentation data is data indicating that it is possible to request the transfer of the right, an indication for specifying the right (distance item and participation qualification in the example of FIG. 6), and the right of the right A transfer request availability display (an “entry” button in the “transfer” column) that indicates that it is possible to request transfer, and a transfer operation object that should be operated on the computer to request transfer (“transfer” column) "Entry" button). In the example of FIG. 6, a single button serves as both an assignment requestable display and an assignment request operation object. Further, as will be described later, in the present embodiment, “the transferee desires transfer” is represented by the process “the transferee terminal 30 transmits transfer request data”.

  In the example of FIG. 1 and No. 1 It is shown that it is possible to request transfer for four events. That is, for these events, a button labeled “Entry” is displayed in the “Assignment” column, which allows participants to know that they can request the transfer of rights for this event. Can do.

  In the example of FIG. 1 and No. 1 It is shown that it is impossible to enter normally for 4 events. In other words, the word “Deadline” is displayed in the “Entry” column for these events, which means that the participant cannot (at least at that point) make a normal entry for this event. Can know.

  After step S10, although not shown in particular, the assignee, for example, No. I hope to participate in the 4th event. Assume that the “entry” button in the “transfer” column is operated for the fourth event. In response to this, the assignee terminal 30 transmits the transfer request data related to the right, and the right management system 10 receives it (step S11). The transfer request data is, for example, data indicating that the button has been operated, and can be configured as an HTTP request including a specific URL, for example.

  After step S11, the rights management system 10 establishes the transfer (step S12) and ends the process shown in FIG. A specific process for establishing the transfer can be appropriately designed by those skilled in the art. For example, it is realized by outputting transfer completion data indicating that the transfer has been completed. Here, considering steps S9 and S11, it can be said that the rights management system 10 establishes the transfer in accordance with the transfer application data and the transfer request data.

  The transfer completion data includes, for example, data for deleting the transferee's participant ID associated with the event of the tournament data 40 and the transferee's participant ID for the event of the tournament data 40. Data, data for deleting the first participant ID (that is, the assignee) in the transfer presenter list of the tournament data 40, and the entry state regarding the participant ID of the assignor in the participant data 50 is “assigned”. And data for adding information related to the participant ID of the assignee to the participant data 50 to make the entry state “scheduled to participate”. In the example of FIG. 3, Mr. A's right recorded at the top is transferred, and Mr. A's participant ID is deleted from the transfer presenter list 41.

  Note that the participant ID of the assignee can be appropriately specified by a known technique. For example, the rights management system 10 may request a login operation or the like before step S12. The establishment of transfer (for example, output of transfer completion data) may be performed by transmission via the communication network N instead of or in addition to the operation to the storage unit 12 of the right management system 10.

  FIG. 7 is a flowchart illustrating an example of a flow of processing for the transferor to apply for transfer of rights in the right management system 10. The process shown in FIG. 7 is started in response to the right management system 10 receiving an entry history data request from another computer (for example, the assignee terminal 20) (step S21). The flowchart of FIG. 7 can be executed in parallel for each item, for example. Prior to step S21, a login operation or the like for specifying the participant ID of the transfer person may be requested.

  The entry history data request is, for example, data for instructing the rights management system 10 to transmit information related to the rights owned by the transfer person, and is configured as an HTTP request including a specific URL, for example. be able to.

  The rights management system 10 determines whether or not it is possible to apply for the transfer of the rights of the item (step S22). For example, if the transferor owns the right, has not applied for transfer, and the transfer deadline has not yet passed, it is determined that the transfer can be applied. In this case, in response to the entry history data request, the right management system 10 transmits entry history data including transferable display data (step S23).

  FIG. 8 shows an example of entry history data including transferable display data. The entry history data can be configured to be included in an HTTP response including HTML data for displaying a screen as shown in FIG. 8, for example. That is, if the entry history data request in step S 21 is transmitted from the assignor terminal 20, the right management system 10 transmits entry history data to the assignor terminal 20. The transferor terminal 20 performs display according to the received data, whereby the participant (transferr) can see a screen as shown in FIG.

  The entry history data is data representing a purchase, transfer, or transfer history regarding the right that the transferor currently owns or previously owned. For example, for each right, “Currently owned by purchase or transfer”, “Currently owned and can apply for transfer to others”, “Currently owned but transferred to others” "It is impossible to apply", "Currently owned but has been applied for transfer to another person and is waiting to be transferred from another person", "Currently owned because the transfer was successful Does not own ”,“ data has been transferred, but the transfer deadline has passed without the transfer being established, and as a result it is still owned ”.

  The entry history data transmitted in step S23 includes transferable display data. The transferable display data is data indicating that the transferor currently owns the right and can apply for transfer to another person. The transferable display data includes, for example, a display for specifying rights (in the example of FIG. 8, the date of the event, the name of the event, the distance / commendation item, the reception date / inquiry number, and the entry type) and the application for the transfer of rights. A transfer application availability display (“transfer application” button in the “application status” column) indicating that it is possible, and a transfer application operation object (“application status”) to be operated on the transferor terminal 20 to apply for transfer "Indication of transfer" button in the column). In the example of FIG. 8, a single button serves as both a transfer request availability display and a transfer request operation object. Further, as will be described later, in the present embodiment, “the assigner applies for assignment” is represented by the process “the assignee terminal 20 transmits assignment application data”.

  In the example of FIG. 1 and No. 1 It is shown that an application for transfer can be made for the second event. In other words, for these events, a button labeled “Application for transfer” is displayed in the “Application status” column, which allows the transferor to apply for the transfer of rights for these items. I can know that. In this example, No. 1 in FIG. For example, No. 1 in FIG. This is the same event as the fourth event.

  After step S23, although not shown in particular, the transferor has no. In order to apply for the transfer of the rights of the first event, no. It is assumed that the “transfer application” button in the “application status” column is operated for the first event. In response to this, the transferor terminal 20 transmits the transfer application data relating to the right, and the right management system 10 receives it (step S24). The transfer application data is, for example, data indicating that the button has been operated, and can be configured as an HTTP request including a specific URL, for example.

  After step S24, the rights management system 10 stores assignment application data indicating that the assigner has applied for the assignment of the right (step S25), and ends the processing shown in FIG. The transfer application data includes, for example, data for additionally associating a transferee participant ID to the end of the transfer presenter list of the event of the tournament data 40, and the transferer entry status in the participant data 50 as “transfer application”. Data for changing to “medium”. In the example of FIG. 3, the transferee's participant ID is added as the fourth participant ID next to Mr. D recorded third.

  In step S22, if the transferor does not own the right, or has already applied for the transfer, or if the transfer deadline has already passed, apply for the transfer Is determined to be impossible. In this case, in response to the entry history data request, the right management system 10 transmits entry history data not including the transferable display data of the right (step S26). When entry history data relating to another right is transmitted together with this, transferable display data relating to the other right may be included.

  FIG. 9 and FIG. 10 show examples of entry history data not including transferable display data. These figures are No. This is an example that does not include the transferable display data relating to the first item (however, the transfer of the No.2 item includes transferable display data as in FIG. 8). It is indicated that an application for transfer is impossible for one event.

  9 and FIG. This indicates that the application for the transfer of the rights of the first item has already been completed (that is, steps S24 and S25 have been performed in the past), so that the transferor can transfer the rights of these items. You can know that it is impossible to apply (again).

  The example of FIG. 9 is an example showing a state where the application for transfer has been completed but the transfer itself has not yet been established. In other words, the transferor still has the right and can participate in the event if the transfer deadline has passed without the transfer being established. In the example of FIG. For the first event, “Entry completed” is written in the “Application status” column. You can see that you still have the rights to the first event. In the example of FIG. 9, “transfer application completed” is written in the “application status” column, and the transfer application availability display (“transfer application” button) is not displayed. This allows the transferor to know that it is impossible to apply (again) for the transfer of the right.

  The example of FIG. 10 is an example showing a state where transfer has already been established. That is, the transferor no longer has the right and cannot participate in the event. In the example of FIG. For the first event, “invalid” is written in the “application status” column. You can see that you no longer have the right to the first event. In the example of FIG. 10, “assignment completed” is written in the “application status” column, and the transfer application availability display (“transfer application” button) is not displayed. This allows the transferor to know that it is impossible to apply (again) for the transfer of the right.

  As described above, since the rights management system 10 according to the first embodiment records the transfer application data from the transferor terminal 20 in the transfer presenter list and establishes transfer sequentially from the top of the transfer presenter list. There is no need for the transferor to designate the transferee in the transfer procedure. For this reason, the transferor does not need to search for a transfer partner before applying for transfer, and the transferee can positively request the transfer of rights (even if not specified by the transferor). Thus, convenience is improved for both the transferor and the transferee.

  The rights management system 10 can process a large number of assignment application data in parallel. In other words, it is possible to receive multiple transfer application data related to the same right, and if there are multiple transfer application data, transfer is established in order from the first received in response to the reception of the transfer request data. The transfer completion data is output. For this reason, even when there are a plurality of assignors and assignees, the assignor can easily associate with the assignee.

In the first embodiment, the following modifications can be made.
In FIG. 1, the assignee terminal 20 and the assignee terminal 30 are shown as different hardware, but they may be the same hardware. For example, when a participant acquires a certain right by assignment and then assigns it to another participant, the computer operated by the participant first functions as the assignee terminal 30, and then assigns it. It functions as the human terminal 20.

  In the first embodiment, it is not possible to make a request for assignment for a right that has not been applied for transfer, but it may be configured so that a request for transfer can also be made for a right that has not been applied for transfer. . This can be realized, for example, by including in the tournament data 40 a transfer applicant list having the same configuration as the transfer presenter list 41 of the first embodiment. For example, this transferee list is configured as an ordered list, and the order is the order in which a request for transfer of rights occurs. In this case, the transfer is established according to the transfer application.

  In the first embodiment, a normal entry desired operation object (an “entry” button in the “entry” column in FIG. 6), an assignment desired operation object (an “entry” button in the “transfer” column in FIG. 6), and a transfer application operation object ( 8 to 10 are all expressed as buttons, but the display format of each object is not limited to this. For example, an image other than a button may be used, and a format normally used when a known web browser represents a hyperlink may be used.

  These objects may be displayed on various screens. For example, it may be displayed not only on a list screen of a plurality of events as shown in FIG. 6, but also on a screen displaying details of a single event or a single event. Such transition between screens may be designed appropriately by those skilled in the art based on known techniques.

  In the first embodiment, the right is a right to start for each event in the long distance running tournament, but can also be applied to other rights.

  In the first embodiment, as shown in FIG. 4, at most one of the purchase and transfer requests can be made at any time. As a variation, it may be possible to both purchase and transfer at least at some point in time or period.

  As shown in steps S4 to S7, the rights management system 10 according to the first embodiment can transmit purchase presentation data and cannot transmit transfer presentation data before the purchase deadline. As a modification, an exception may be provided. For example, even before the purchase deadline, an arbitrary limitation condition regarding the tournament ID, the participant ID, and the like may be provided, and the purchase presentation data may not be transmitted if the conditions are not met. Further, another limitation condition may be provided, and the transfer presentation data may be transmitted when the condition is met.

  Further, as shown in steps S8 to S12, the rights management system 10 according to the first embodiment cannot transmit the purchase presentation data and can transmit the transfer presentation data after the purchase expiration date. . As a modification, an exception may be provided. For example, even after the purchase deadline, an arbitrary limitation condition regarding the tournament ID, the participant ID, and the like may be provided, and purchase presentation data may be transmitted when the condition is met. Further, another limitation condition may be provided, and the transfer presentation data may not be transmitted when the condition is met.

  In the first embodiment, communication between the rights management system 10 and the assignor terminal 20 and the assignee terminal 30 is performed based on the HTTP protocol, but this may be based on another protocol. For example, part or all of the data may be transmitted / received by e-mail.

  In connection with the transmission and reception of data relating to the transfer and transfer of rights, additional data may be transmitted and received for the presentation and confirmation of necessary information. For example, the rights management system 10 may transmit data for displaying a screen for confirming the contents of rights and conditions for transfer to the transferor terminal 20 before and after receiving the transfer application data (step S24). Good. This screen shows, for example, the name of the participant, the name of the tournament, the date of the event, the entry type, the transferable period, the price of the right to be transferred (for example, the entry fee for that item), the amount of other necessary fees, and the amount to be refunded ( For example, the amount paid for the purchase of the right), the amount of the commission for the transfer application, the refund equivalent amount (the total deduction paid to the transferor when the transfer is established), the amount of user points for the use of any service, This includes a warning that the transfer application cannot be cancelled, selection of a payment method (for example, settlement by credit card), and the like.

  In addition, for example, the rights management system 10 receives normal entry request data (purchase request data), receives transfer application data, receives transfer request data, and transfers are established (for example, transfer completion data). Or the like may be sent. Moreover, you may perform notification which shows that the transfer time limit passed without transfer being materialized. These notifications may be made by electronic mail.

  After the normal entry deadline has passed, additional adjustment of participants may be performed. In the first embodiment, the “entry” button in the “entry” column in FIG. 6 is an example of a normal entry desired operation object, and the “entry” button in the “transfer” column in FIG. 6 is an example of a desired transfer operation object. . As a modification, the “entry” button in the “transfer” column of FIG. 6 may function as a normal entry desired operation object. For example, after the normal entry deadline has passed, if the participant who entered has lost his / her rights due to cancellation or delay in payment, etc., the “transfer” in FIG. 6 for additional participant recruitment (so-called “late entry”). An “entry” button in the column may be used.

  In such a configuration, when the “entry” button in the “transfer” column of FIG. 6 is operated, whether it is processed as a normal entry request or a transfer request is based on an arbitrary criterion. Can be determined. For example, if there is transfer application data for the right, it is processed as a transfer request (step S11 and subsequent steps are executed), and if there is no transfer application data, it is processed as a normal entry request (from step S6 onward). Executed). In this way, the transfer application frame is processed with priority over the late entry frame.

  With the purchase and transfer of rights as in the first embodiment, fee exchange may occur. Further, the right management system 10 may further include a function of executing processing related to fee exchange. For example, it may be provided with a function for generating exchange of charges by communicating with a computer of a financial institution such as a credit card company or a bank.

  FIG. 11 shows an example of exchange of fees that accompany the purchase and transfer of rights. The “+” symbol attached to the fee item name in the figure indicates that the fee is received, and the “−” symbol indicates that the fee is paid.

  As shown in FIG. 11, it is assumed that Mr. A purchases the right by performing the normal entry procedure after the normal entry starts and before the deadline. Along with this, as shown in (1), a tournament participation fee (consideration of the right) and an entry fee (a fee for acquiring the right) are paid from Mr. A to the operator of the rights management system 10. After that, when the normal entry deadline has passed, the tournament participation fee is paid from the manager to the tournament organizer as shown in (2).

  Assume that Mr. A made a transfer application as shown in (3) after the normal entry deadline and before the transfer deadline. At this point, there is no request for transfer, but after that, Mr. B wants to transfer. Along with this, as shown in (4), the participation fee (consideration of rights), entry fee (fee related to acquisition of rights) and transfer fee (fee related to transfer of rights) will be transferred from Mr. B to the operator. Paid. In addition, since transfer is established between Mr. A and Mr. B in response to this transfer request, the competition fee will be returned to Mr. A by the operator as shown in (5), and the transfer fee will be paid accordingly. Is paid to the operator by Mr. A.

  In this way, after the regular entry deadline, the total tournament fee does not change. Therefore, from the viewpoint of the tournament organizer, the tournament participation fee received when the deadline for normal entry has passed does not need to be refunded even if the transfer of rights thereafter occurs.

  A person skilled in the art can appropriately design the configuration and operation of the charging stand 10 for generating the exchange of the charges as described above.

  In the first embodiment, when there are a plurality of assignment application data, the rights management system 10 establishes assignment in order from the one received earlier and outputs assignment completion data. As a modification, the order may be determined based on other criteria. For example, classify participants into multiple groups, and transfer application data from participants belonging to one group (for example, paid members) takes precedence over transfer application data from participants belonging to another group (for example, free members). You may make it process.

  In the first embodiment, the right is a right to start in a long distance running tournament, but this may be related to other events. For example, the right may be a right to participate in a competition related to running without being limited to a long distance running competition. Alternatively, the right may be a right to participate in a tournament related to a bicycle. The right may be a right to participate in other sports-related competitions and events.

  10 rights management system (computer), 11 calculation means, 12 storage means, 20 assignee terminal, 30 assignee terminal, 40 event data, 41 transfer presenter list, 50 participant data, N communication network.

Claims (5)

A rights management system that supports the transfer of rights between a transferor and a transferee,
The rights management system is communicable with an assignee terminal used by the assignee and an assignee terminal used by the assignee,
The rights management system includes:
A function of transmitting transferable display data relating to a right owned by the transferor to the transferor terminal;
A function of receiving transfer application data relating to the right from the transferor terminal;
A function of receiving status inquiry data related to the right from a terminal;
A function for determining a purchase deadline related to the right, and when the purchase deadline has passed, the terminal as the transferee terminal, in response to the transfer application data and the status inquiry data, to the transferee terminal , A function of transmitting transfer presentation data relating to the right;
When the purchase deadline has passed, the terminal as the transferee terminal, and from the transferee terminal, the function of receiving transfer request data related to the right;
A function for establishing the transfer of the right from the transferor to the transferee according to the transfer application data and the transfer request data when the purchase deadline has passed;
A function of transmitting purchase presentation data relating to the right to the transferor terminal when the purchase deadline has not elapsed, and using the terminal as the transferor terminal;
A rights management system comprising: The transfer presentation data is
An indication identifying the right;
An assignment request indication indicating that it is possible to request the assignment of the right;
The right management system according to claim 1 , further comprising: a display indicating a transfer request operation object to be operated in the transferee terminal in order to transmit the transfer request data. The transferable display data is
An indication identifying the right;
A transfer request indication indicating that it is possible to apply for the transfer of the right;
The transferor and a display showing the transfer application operation object to be operated in the terminal, the rights management system of claim 1 or 2 for the transmission of the transfer application data. The right management system according to any one of claims 1 to 3 , wherein the right is a right to start in a long-distance running tournament. A program that causes a computer to function as the rights management system according to any one of claims 1 to 4 .

Images