Golf booking server

Abstract

The present disclosure presents a golf booking server which: is communicatively connected to a plurality of golfer terminals; generates booking by making golfers join on the basis of join conditions of the golfers who request join-in booking; enables a request for replacing a booking team during a round through the join-in booking; induces preference evaluation of a joined booking team when the golf round is completed; and causes the evaluated golf team and the preference evaluation result to be linked and stored.

Description

Golf Booking Server

[0001] The present invention relates to a golf booking server, and more particularly, to a technology for supporting general booking and join booking for use of a golf course.

[0002] Golf course users (hereinafter referred to as "golfers") form teams of four and reserve tee times to play a round of golf. Golfers who are not part of a team can use the course through "join" (recruitment) bookings.

[0003] Typically, golfers make a reservation through the golf course website, then post a join booking post including the booking date, booking time, gender, number of participants, etc., and then form a team through comments from other golfers who wish to join or direct contact, and proceed with the booked golf round.

[0004] Recently, golf courses have been providing a join booking service that recruits golfers who have not formed a team to form a team so that they can use the golf course.

[0005] Golf courses launch a join booking service at specific times. Golfers apply for a join booking, specifying conditions such as date, time, gender, and number of participants. The golf course manually forms teams using these conditions and then notifies golfers who have completed their join bookings through a website announcement or personal contact. These golfers then proceed to play their scheduled rounds.

[0006] However, the conventional join booking service only considers the tee time and number of people to join golfers, so there are differences in the golfers' skills and round tendencies, which causes a problem in that the satisfaction with the round through join booking is lowered.

[0007] The matters described in the background art above are intended to help understand the background of the invention and may include matters that are not publicly disclosed prior art.

[0008] The present invention has been proposed to solve the problem, and its purpose is to provide a golf booking server that joins booking teams based on join conditions, allows a request for replacement of booking teams during a round through join booking, and induces a preference evaluation of the booking team that has made the join booking.

[0009] In order to achieve the above object, a golf booking server according to an embodiment of the present invention includes a communication circuit configured to communicate with a plurality of golfer terminals and to exchange data with the plurality of golfer terminals, a memory, and one or more processors configured to load commands stored in the memory and perform one or more operations according to execution of the commands, and the one or more processors control the golf booking server to communicate with the plurality of golfer terminals, and create a first booking by joining a first golfer team and a second golfer team in response to a join booking request transmitted from the plurality of golfer terminals, and when a golf round of the first booking is completed, request an evaluation of a preference for an opposing team from the first golfer team and the second golfer team, and store the golf team that evaluated the preference for the booking team and the result of the preference evaluation in association with each other.

[0010] One or more processors may replace the booking team of the first golfer team for a subsequent round of golf by joining the first golfer team to a second booking in response to a booking team replacement request transmitted from a golfer terminal of the first golfer team in a previous round of golf of the first booking.

[0011] One or more processors can detect a booking that is in progress on a previous round of golf among one or more bookings having a tee time after the tee time of the first booking as a second booking.

[0012] One or more processors may request a preference evaluation for the first golfer team from the golfer terminal of the second golfer team when the golf round of the first booking is completed, request a preference evaluation for the third golfer team and the second golfer team from the golfer terminal of the first golfer team when the golf round of the second booking is completed, request a preference evaluation for the first golfer team from the golfer terminal of the third golfer team, and receive one of a preference and a non-preference as a preference evaluation result for the booking team from the golfer terminals of the first golfer team to the third golfer team.

[0013] One or more processors may transmit to the golfer terminal a join booking list including one or more join booking information in response to a join request received from the golfer terminal, but may transmit to the golfer terminal a join booking list that does not include join booking information of a golfer team that the golfer team of the golfer terminal has evaluated as unfavorable in a previous golf round.

[0014] One or more processors may transmit to the golfer terminal a join booking list including one or more join booking information in response to a join request received from the golfer terminal, and may transmit to the golfer terminal a join booking list that displays the join booking information of a golfer team that the golfer team of the golfer terminal has evaluated as preferred in a previous golf round, distinguishing it from other join booking information.

[0015] One or more processors may transmit a join booking creation alarm to a golfer terminal, and may transmit a join booking creation alarm to the golfer terminal when a join booking is created for a golfer team that the golfer terminal has evaluated as preferred in a previous golf round.

[0016] One or more processors may enable priority reservation of golfer terminals that have received a set number of preference ratings from other golfers.

[0017] One or more processors may offer each golfer in a five-person booking a lower round of golf cost than each golfer in a four-person booking.

[0018] One or more processors may differentiate and present golf round costs based on join conditions transmitted from a golfer terminal at the time of join booking, and may present golf round costs differently depending on the join conditions set by the golfer terminal.

[0019] One or more processors may offer higher golf round rates if they set join conditions that make it difficult to join with other golf teams.

[0020] One or more processors may differentiate and present golf round costs based on join conditions transmitted from a golfer terminal at the time of join booking, and may present different golf round costs depending on the number of join conditions.

[0021] One or more processors may offer a higher round of golf cost to golfers on a larger golf team than to golfers on other golf teams when making a join booking.

[0022] One or more processors may offer a higher price for a round of golf to a team of golfers whose tee times are set to a specific time than to a team of golfers whose tee times are set to a time zone.

[0023] According to the present invention, the golf booking server has the effect of increasing the satisfaction of the experience of a join golf round while relieving the inconvenience of a join golf round through services such as changing the booking team, evaluating preferences, and providing benefits based on the results of the preference evaluation.

[0024] In addition, the golf booking server can differentiate the cost of a golf round for each golfer based on the composition of the booking team, thereby reducing the cost of a golf round for each golfer while increasing the cost of the golf course, thereby increasing the cost satisfaction of golfers and golf course operators.

[0025] In addition, the golf booking server joins golfers through join conditions, but if golfers feel difficulty or discomfort in playing golf together due to other golfers' bad manners, nagging, slow progress, etc., it can change the booking team through a booking team change request, thereby solving the inconvenience of join booking and increasing the satisfaction of join booking, which can have the effect of encouraging many golfers to play golf rounds through join booking.

[0026] In addition, the golf booking server can evaluate the preference of the booking team after a golf round is played through join booking, and by reflecting the preference evaluation in the join booking, it can prevent behavior that may cause difficulties or discomfort to the booking team, such as bad manners, nagging, or slow progress, when playing join booking, thereby solving the inconvenience of join booking and increasing the satisfaction of join booking, which can have the effect of encouraging many golfers to play golf rounds through join booking.

[0027] In addition, the golf booking server can prevent a decline in the golf course's profits by reducing the round costs of golfers who enjoy rounds under various conditions by suggesting costs based on various joining conditions such as joining conditions, time, and number of people.

[0028] Additionally, the golf booking server has the effect of making it easier for golfers to access join bookings by omitting the cost of the rest area by presenting it to each joining team, thereby eliminating the need for golfers to present the cost among themselves.

[0029] FIG. 1 is a block diagram illustrating a golf booking system including a golf booking server according to an embodiment of the present invention.

[0030] Figure 2 is a drawing for explaining an example of the golfer database of Figure 1.

[0031] Figure 3 is a drawing for explaining an example of the join database of Figure 1.

[0032] Figure 4 is a drawing for explaining an example of the booking database of Figure 1.

[0033] Figure 5 is a drawing for explaining the booking function of the golf booking server of Figure 1.

[0034] FIG. 6 is a drawing for explaining the booking team replacement function provided by the golf booking server of FIG. 1.

[0035] Fig. 7 is a drawing for explaining the booking team evaluation function provided by the golf booking server of Fig. 1.

[0036] FIG. 8 is a drawing illustrating an example of benefits provided to a golfer who has completed a booking team evaluation provided by the golf booking server of FIG. 1.

[0037] FIG. 9 and FIG. 10 are drawings for explaining the configuration of the golf booking server of FIG. 1.

[0038] Hereinafter, a preferred embodiment of the present invention will be described in detail with reference to the attached drawings.

[0039] These examples are provided to more fully illustrate the present invention to those skilled in the art. The following examples may be modified in various ways, and the scope of the present invention is not limited to the examples described below. Rather, these examples are provided to further faithfully and completely convey the spirit of the present invention.

[0040] Those skilled in the art will appreciate that the various exemplary blocks, devices, or operations described in connection with the configurations disclosed herein may be implemented as electronic hardware, computer software, or a combination of both. Such blocks, devices, or operations may be implemented or performed using a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC) or application-specific standard product (ASSP), a field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to produce a configuration as disclosed herein. A processor may be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other configuration. Computer software or programs may reside in nonvolatile RAM such as random access memory (RAM), read-only memory (ROM), flash RAM, erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), registers, hard disks, removable disks, CD-ROMs, or any other form of storage medium known in the art, and may include machine-readable instructions that are executable by an array of logic elements, such as a processor or a DSP. An exemplary storage medium may be coupled to the processor, and the processor can read information from, and write information to, the storage medium. Alternatively, the storage medium may be integral to the processor. The processor and the storage medium may reside within an application-specific integrated circuit (ASIC). The ASIC may reside within a terminal.Alternatively, the processor and the storage medium may reside as separate components within the reading-enabled device.

[0041] Referring to FIG. 1, a golf booking system according to an embodiment of the present invention comprises a golfer terminal (100), a database (200), and a golf booking server (300). Here, in FIG. 1, the database (200) and the golf booking server (300) are illustrated as separate terminals for easy explanation of the embodiment of the present invention, but are not limited thereto, and the database (200) may be configured as a single terminal and a storage medium such as a memory, SSD, or HDD built into the terminal.

[0042] A golfer terminal (100) is a terminal used by a user to book a golf round. The golfer terminal (100) is configured as a terminal capable of transmitting and receiving data with a golf booking server (300) via a network. Examples of the golfer terminal (100) include terminals capable of transmitting and receiving data with the golf booking server (300) via a network, such as a smartphone, tablet, desktop, laptop, or kiosk.

[0043] The database (200) stores information related to golf booking. For example, the database (200) stores golfer information, join information, join condition information, booking information, payment information, etc. used for golf booking.

[0044] For this purpose, the database (200) may be configured to include a golfer database (220), a join database (240), and a booking database (260).

[0045] The golfer database (220) stores golfer information, which is personal information about golfers using the golf booking system. The golfer database (220) may additionally store evaluation information to provide additional services during join booking.

[0046] For example, referring to FIG. 2, the golfer database (220) stores golfer information including golfer identifier, ID, password, name, contact information, etc. The golfer database (220) may further store evaluation information including the number of golfer evaluations, preferred teams, and non-preferred teams to provide additional services.

[0047] Here, in FIG. 2, the golfer database (220) is illustrated and described as storing golfer information and evaluation information, but it is not limited thereto, and the database (200) may further include an evaluation database (200) separate from the golfer database (220), and the evaluation database (200) may be configured to store golfer identifiers and evaluation information in conjunction with each other.

[0048] The join database (240) stores join booking information, which is information entered by a golfer for join booking. The join database (240) may also store join condition information entered by the golfer for join booking. Here, the join booking information is booking information in a tentative reservation state where the booking has not been confirmed, and the join condition information may be information entered by the golfer who applied for join booking to limit the golfers who join during join booking.

[0049] For example, referring to FIG. 3, the join database (240) stores join information including a join code, a golfer identifier, a date, a tee time, a number of holes, a course, a number of people, etc. The join database (240) further stores join condition information for join booking between users, and may further store join condition information including companion relationships, member composition, age, gender, handicap, etc. for joins between users.

[0050] The booking database (260) stores booking information for which reservations have been completed. The booking database (260) may further store payment information for settling golf round costs.

[0051] For example, referring to FIG. 4, the booking database (260) stores booking information including a booking code, golfer identifier, date, tee time, hole, course, number of people, etc. In this case, the booking database (260) further stores payment information for costs incurred during a golf round, and further stores payment information including golf round costs and other costs, as an example.

[0052] The golf booking server (300) can be configured to perform a booking function, a booking team replacement function, a booking team evaluation function, and a settlement function.

[0053] The golf booking server (300) is configured to provide a booking function that creates a booking for a golf round through join booking, booking join, and general booking.

[0054] Referring to FIG. 5, the golf booking server (300) is configured to support join bookings with various team combinations, such as join bookings / general bookings consisting of 5 people without caddies, 1:1:1:1, 2:2, 3:1, and 4:1, in order to provide a flexible booking service. The golf booking server (300) is configured to perform join bookings based on join condition information, including personnel composition, companion relationships, age groups, gender, and handicap, in order to eliminate inconveniences of join bookings and increase satisfaction.

[0055] Join booking allows golfers to join through join conditions, but there are problems such as difficulty or discomfort in playing a round of golf together due to other golfers' bad manners, nagging, and slow progress.

[0056] Accordingly, the golf booking server (300) is configured to provide a booking team change function that allows a golfer to request a booking team change so that the golfer can play a golf round with another team if the golfer wishes to change the booking team. The golf booking server (300) is configured so that a golfer can request a booking team change between the first and second halves (or between the first and middle, or between the middle and the second halves) of a golf round. The golf booking server (300) allows the golfer who requested the booking team change to join another team and play a golf round if there is an empty spot in the team after the time at which the golfer's booking team change request is entered.

[0057] For example, referring to FIG. 6, if a first golfer team of two and a second golfer team of two constitute a first joint booking team, and a third golfer team of two constitute a second joint booking team, and the first golfer team requests a change of booking teams during the first half (holes 1 to 9) of a golf round, the golf booking server (300) forms a first golfer team of two and a third golfer team of two as a joint booking team and forms a second golfer team as another joint booking team to form the second half (holes 10 to 18) of the golf round.

[0058] The golf booking server (300) operates as a booking team evaluation function to evaluate the preference of the opposing team (or opposing golfer) with whom the golfer played a round of golf through a join booking after the golfer's golf round is completed. The golf booking server (300) operates as a booking team evaluation function after the join golf round is completed. When the golf booking server (300) operates as a booking team evaluation function, it receives an input of a preference evaluation for the opposing team (or accompanying team, opposing golfer) that the golfer has joined from the golfer's terminal (100). The golf booking server (300) receives one of a preference and a non-preference as an input of a preference evaluation.

[0059] For example, referring to FIGS. 6 and 7, if the first and second golfer teams join and book the first half of a golf round, and the first and third golfer teams join and book the second half of a golf round, the golf booking server (300) receives preference evaluations for the second and third golfer teams from the first golfer team, and receives preference evaluations for the first golfer team from the second and third golfer teams.

[0060] The golf booking server (300) can be configured to provide various services to golfers using the preference evaluation results.

[0061] The golf booking server (300) may be configured to provide a preference evaluation function for joining teams (joining golfers) to enhance the experience satisfaction of joining golf rounds through joining bookings. The golf booking server (300) may be configured to provide various benefits to golfers who have completed a preference evaluation to facilitate the activation of preference evaluation. In this case, the golf booking server (300) may be configured to provide various benefits to golfers who have completed a preference evaluation a set number of times or more.

[0062] For example, the golf booking server (300) can be configured so that a join booking that includes a golfer evaluated as unpreferred in the booking function is not exposed in the join booking list.

[0063] Referring to FIG. 8, the golf booking server (300) provides a join booking list that removes the join bookings of golfers evaluated as unpreferred by the golfer at the time of joining, thereby providing a different join booking list for each golfer (team).

[0064] As another example, the golf booking server (300) may be configured to send a notification to the golfer terminal (100) when a golfer evaluated as preferred in the booking function joins (creates) a join booking.

[0065] As another example, the golf booking server (300) may be configured to display multiple join bookings that can be joined in a join booking list when a golfer joins, but to display join bookings that include a golfer evaluated as preferred so as to be distinguished from other join bookings.

[0066] The golf booking server (300) may be configured to provide benefits to golfers who have received many favorable evaluations from other golfers.

[0067] For example, the golf booking server (300) is configured to generate a join booking list including join information and the number of preferred evaluations. The golf booking server (300) is configured to generate a join booking list including a plurality of visible booking information, and further includes the number of preferred evaluations of the golfer who generated the join information.

[0068] As another example, the golf booking server (300) is configured to generate a join booking list sorted based on the number of preferred evaluations. Accordingly, the join booking list is arranged with the join booking with the highest number of preferred evaluations at the top.

[0069] As another example, the golf booking server (300) is configured to provide reservation priority to golfers whose preference ratings exceed a preset number. Specifically, the golf booking server (300) may set the join booking time for golfers without reservation priority to 8:00 AM, and for golfers with reservation priority to approximately 7:00 AM. In other words, the golf booking server (300) allows golfers with preference ratings exceeding a preset number to reserve join bookings earlier than other golfers.

[0070] In this way, the golf booking server (300) increases the satisfaction of the experience of a join golf round while relieving the inconvenience of a join golf round through exchanging booking teams, evaluating preferences, and providing benefits based on the results of the preference evaluation.

[0071] The golf booking server (300) is configured to provide a settlement function that presents booking conditions and costs incurred during a golf round.

[0072] For example, a golf booking server (300) may be configured to differentiate the cost of a golf round depending on the number of people in the booking.

[0073] Golf booking servers (300) generally present a standard golf round cost based on a booking for 4 people.

[0074] The golf booking server (300) offers a golf round fee that is higher than the fee for a four-person golf round when booking (join booking, general booking) for a team of five, but lower than the fee for a five-person golf round. The golf booking server (300) offers a discounted golf round fee to each golfer included in a five-person booking, and is configured to offer a total golf round fee that is higher than the fee for a four-person booking.

[0075] Accordingly, the golf booking server (300) can increase the cost satisfaction of both golfers and golf course operators by reducing the cost of each golf round while increasing the cost of the golf course. Specifically, when booking for five people, golfers can use the golf course at a lower cost than when booking for four people. Furthermore, the golf course can offer a relatively higher profit per booking because the higher cost of a golf round is normalized compared to a four-person booking.

[0076] As another example, the golf booking server (300) can be configured to differentiate golf round fees based on join conditions during join booking. The more stringent the join conditions (i.e., the more conditions), the more difficult it is to join with other teams. Accordingly, the golf booking server (300) is configured to offer a relatively higher golf round fee when strict join conditions are set.

[0077] The golf booking server (300) may be configured to set a set number of join conditions as a standard golf round cost, and to present a golf round cost that sequentially increases from the standard golf round each time a join condition is added when the number of join conditions exceeds the set number.

[0078] As another example, the golf booking server (300) may be configured to differentiate and present a golf round fee based on the number of members in each team that constitutes a join booking. That is, the golf booking server (300) maintains the overall golf round fee of the join booking the same, and sets a higher golf round fee for golfers belonging to a majority team than for golfers belonging to a minority team. If the number of members in the first golfer team is 3, and the number of members in the second golfer team that joined the first golfer team is 1, the golf booking server (300) may set a golf round fee based on 4 members, but may set a higher golf round fee for golfers in the first golfer team than for golfers in the second golfer team.

[0079] As another example, the golf booking server (300) may be configured to offer a golf round fee based on whether a tee-up time (i.e., tee-off) has been confirmed at the time of a join booking. The golf booking server (300) may offer a higher golf round fee to a team that joins by setting the tee-up time to a specific time during a join booking than to a team that joins by setting the tee-up time to a specific time.

[0080] In this way, the golf booking server (300) can prevent a decrease in the golf course's profits by reducing the round costs of golfers who enjoy rounds under various conditions by suggesting costs according to various joining conditions such as joining conditions, time, and number of people.

[0081] As another example, the golf booking server (300) may be configured to present, by team, the costs incurred by golfers who have made joint bookings at rest areas (e.g., shade houses) during their golf rounds. In the case where the first and second golfer teams have made joint bookings, the golf booking server (300) is configured to present the food and beverage costs incurred at the shade house during their golf rounds separately as the first golfer team costs and the second golfer team costs.

[0082] Typically, golf courses list the cost of a rest area per booking, requiring golfers who have made a joint booking to submit the cost again. In contrast, the golf booking server (300) according to an embodiment of the present invention lists the cost of a rest area per team, thereby eliminating the need for golfers who have made a joint booking to submit the cost, making joint bookings more accessible to golfers.

[0083] Hereinafter, a golf booking server (300) according to an embodiment of the present invention is described as being separated from a database (200) and composed of a plurality of modules, but includes a communication circuit configured to exchange data with a golfer terminal, a memory, and one or more processors configured to load commands stored in the memory and perform one or more operations according to the execution of the commands, and the one or more processors can be configured to control the golf booking server (300) to communicate with the golfer terminal and perform a booking function, a booking team replacement function, a booking team evaluation function, and a settlement function.

[0084] Referring to FIG. 9, the golf booking server (300) is configured to include a control module (310), a booking module (320), a join module (330), a replacement module (340), an evaluation module (350), and a settlement module (360).

[0085] The control module (310) is a module that controls each module of the golf booking server (300) to perform booking functions, booking team replacement functions, booking team evaluation functions, and settlement functions according to the request of the golfer terminal (100). Although the control module (310) is described below as exchanging data with the golfer terminal (100), it may be configured to communicate with the golfer terminal via a communication module (not shown, or a communication circuit).

[0086] The control module (310) responds to a booking request from a golfer terminal and transmits a booking creation request to the booking creation module. The control module (310) detects booking-related information, including a golfer identifier, date, tee-up time, odd number, course, and number of participants, from the booking request from the golfer terminal. The control module (310) generates a booking creation request including the detected booking-related information. The control module (310) transmits the booking creation request to the booking module (320).

[0087] The control module (310) responds to a join booking request from a golfer terminal by transmitting a join booking creation request to the join creation module. The control module (310) detects join booking-related information, including a golfer identifier, date, tee time, hole, course, number of participants, etc., from the join booking request from the golfer terminal. The control module (310) generates a join booking creation request including the detected join booking-related information. The control module (310) transmits the join booking creation request to the join module (330).

[0088] The control module (310) can further detect join condition information, including one or more of companion relationship, personnel composition, age, gender, and handicap, from the join booking request of the golfer terminal. The control module (310) generates a join booking creation request including join booking-related information and join condition information. The control module (310) transmits the join booking creation request to the join module (330).

[0089] The control module (310) responds to a join request from a golfer terminal by transmitting a join booking request to the join module (330).

[0090] The control module (310) may detect a golfer identifier from a join request of a golfer terminal, generate a join booking request including the golfer identifier, and transmit the request to the join module (330).

[0091] The control module (310) may also transmit a join booking request including a join condition to the join module (330). The control module (310) detects a join condition from a join request from a golfer terminal. The module detects a join condition including at least one of date, tee time, hole, course, number of participants, companion relationship, age, gender, and handicap. The control module (310) generates a join booking request including the detected join condition and transmits it to the join module (330).

[0092] The control module (310) responds to a booking team replacement request from a golfer terminal (100) that conducts a golf round through booking and join booking and transmits the booking team replacement request to the replacement module (340). The control module (310) detects a golfer identifier and / or a booking identifier from the booking team replacement request of the golfer terminal (100). The control module (310) generates a booking team replacement request including one of the detected golfer identifier and booking identifier and transmits the request to the replacement module (340).

[0093] When the control module (310) receives a booking team replacement list in response to a booking team replacement request, it transmits the booking team replacement list to the golfer terminal (100). The control module (310) receives a booking team replacement confirmation request including one booking information from the booking team replacement list from the golfer terminal (100). The control module (310) updates the booking information by combining the golfer (or team including the golfer) who requested the booking team replacement with the booking information included in the booking team replacement confirmation request.

[0094] After updating the booking information, the control module (310) transmits a booking update alarm to the golfer terminal (100) of the golfer included in the booking information. Upon receiving the booking update alarm, the golfer waits until the replacement booked team arrives at the shade house and then proceeds with the second half (or middle and second half) of the round with the replacement booked team.

[0095] When the golf round of a team that has participated in a joint booking is completed, the control module (310) transmits a request for evaluation of the joint booking team to the evaluation module (350). When the golf round of a team that has participated in a joint booking is completed, the control module (310) transmits a request for presentation of costs to the settlement module (360).

[0096] The booking module (320) generates booking information in response to a booking creation request from the control module (310). The booking module (320) detects booking-related information from the booking creation request from the control module (310). The booking module (320) generates a booking code. The booking module (320) generates booking information including the booking code and booking-related information. The booking module (320) stores the booking information in the booking database (260).

[0097] The join module (330) responds to a join booking creation request from the control module (310) to determine whether join booking is possible.

[0098] The join module (330) detects a golfer identifier from the join booking creation request if the time at which the join booking creation request is received is after the first set time and before the second set time. The join module (330) detects evaluation information linked to the golfer identifier from the golfer database (220). The join module (330) determines that join booking is possible if the number of preferred evaluations of the evaluation information is greater than or equal to the set number. Here, the second set time is the time after the first set time, and the second set time is the time set for starting the join booking service at the golf course.

[0099] The join module (330) determines that join booking is not possible if the time at which a join booking creation request is received is before the first set time. The join booking module (320) determines that join booking is not possible if the time is after the first set time but before the second set time and the number of preferred evaluations of the golfer is less than the set number.

[0100] The join module (330) determines that join booking creation is possible if the time at which a join booking creation request is received is after the first set time.

[0101] The join module (330) determines that join booking is possible and generates join booking information. The join module (330) detects join booking-related information from the join booking creation request. The join module (330) generates a join code. The join module (330) generates join booking information including the join code and join booking-related information, and stores the join booking information in the join database (240).

[0102] The join module (330) can further detect join condition information from a join booking creation request. The join module (330) generates join booking information including a join code, join booking-related information, and join condition information, and stores the join booking information in the join database (240).

[0103] After creating join booking information, the join module (330) can send a preferred team join booking alarm to a golfer who has evaluated the golfer who requested the creation of the join booking as a preferred team.

[0104] The join module (330) detects a golfer identifier from a join booking request. The join module (330) detects golfer information stored in the golfer database (220) that includes the golfer identifier detected from the join booking request and is stored as a preferred team. The join module (330) detects contact information from the detected golfer information. The join module (330) sends a preferred team join booking alarm containing join booking information to the detected contact information.

[0105] The join module (330) may be configured to detect one (or some) golfers by filtering based on the preference evaluation result when multiple golfers are detected as notification targets, and to transmit a preferred team join booking alarm to the golfer terminal (10) of the detected golfer.

[0106] The join module (330) may be configured to, when multiple golfers are detected as notification targets, sort them based on preference evaluation results and send a preferred team join booking alarm to the golfer with the highest preference evaluation. In this case, the join module (330) may sequentially send preferred team join booking alarms based on the preference evaluation results. In other words, the join module (330) may enable golfers with a high preference evaluation rate to quickly receive preferred team join booking alarms.

[0107] The join module (330) can transmit a preferred team join booking alarm only to golfers who have evaluated the opposing team (join team) a certain number of times after a round through join booking. The join module (330) first detects golfer information whose golfer identifier is detected from the join booking request and is stored as a preferred team. The join module (330) secondarily detects golfer information whose evaluation count is greater than or equal to a preset number among the golfer information detected in the first round. The join module (330) transmits a preferred team join booking alarm including join booking information to the contact information included in the secondarily detected golfer information.

[0108] The join module (330) detects join information from the join database (240) in response to a join booking request from the control module (310). The join module (330) generates a join list including the detected join information. The join module (330) transmits the join list to the control module (310). Here, for the purpose of easily explaining the embodiment of the present invention, the join module (330) is described as generating a join list including join information. However, an actual server may generate a join list mixed with join information, booking information, and empty booking time zones, and it should be understood that such a join list is also included in the rights.

[0109] The join module (330) can transmit a join list with filtered join information based on the join conditions of the golfer requesting the join to the control module (310).

[0110] The join module (330) detects join conditions from the join booking request of the control module (310). The join module (330) first detects join information from the join database (240). The join module (330) secondarily detects join information corresponding to the join conditions among the firstly detected join information. The join module (330) generates a join list including the secondarily detected join information and transmits it to the golfer terminal (100).

[0111] The join module (330) can transmit a join list filtered with join information based on the golfer's evaluation results to the control module (310). At this time, the join module (330) can be configured to provide a join list filtered using the evaluation results (i.e., preferred team, non-preferred team) only to golfers who have evaluated the opposing team (join team) a certain number of times after a round through join booking.

[0112] The join module (330) can detect a join booking requested by a golfer who has registered as a preferred team by a golfer who has requested a join and transmit the same to the control module (310). The join module (330) detects a golfer identifier from the booking request of the control module (310). The join module (330) detects evaluation information corresponding to the golfer identifier. The join module (330) detects join information corresponding to the preferred team of the evaluation information from the join database (240). The join module (330) generates a join list including the detected join information and transmits the same to the control module (310).

[0113] The join module (330) can detect join bookings requested by golfers who have registered as non-preferred teams, excluding join bookings requested by golfers who have requested joins, and transmit the results to the golfer terminal (100). The join module (330) detects join information, excluding join information corresponding to non-preferred teams, from the join database (240) among the detected evaluation information. The join module (330) generates a join list including the detected join information and transmits the list to the control module (310).

[0114] The join module (330) can transmit a join list filtered with join information based on the golfer's join conditions and evaluation results to the control module (310). The join module (330) can be configured to provide a join list filtered using the join conditions and evaluation results only to golfers who have evaluated the opposing team (join team) a certain number of times after a round through join booking.

[0115] The join module (330) detects a join condition from a join booking request from the control module (310). The join module (330) first detects join information from the join database (240). The join module (330) secondarily detects join information corresponding to the join condition among the first detected join information.

[0116] The join module (330) detects a golfer identifier from a booking request from the control module (310). The join module (330) detects evaluation information corresponding to the golfer identifier. The join module (330) tertiarily detects, from among the secondarily detected join information, join information corresponding to the preferred team of the evaluation information. The join module (330) generates a join list including the thirdly detected join information and transmits it to the control module (310).

[0117] The join module (330) may tertiarily detect join information, excluding join information corresponding to a non-preferred team in the evaluation information, among the secondarily detected join information, and may generate a join list including the thirdly detected join information and transmit it to the control module (310).

[0118] The join module (330) can generate a join list based on evaluation information.

[0119] The join module (330) generates a join list including the detected join information, but can also generate a join list including the number of times it was evaluated as a preferred team.

[0120] The join module (330) generates a join list sorted in descending order based on the number of times a team has been evaluated as a preferred team. The join module (330) generates a join list in which the join information with the highest number of times evaluated as a preferred team is placed at the top, and the join information with the lowest number of times evaluated as a preferred team is placed at the bottom.

[0121] The join module (330) can generate a join list by sorting the join information in ascending order based on the number of times the team has been evaluated as a non-preferred team, if the number of times the team has been evaluated as a preferred team is the same. The join module (330) generates a join list in which the join information with the highest number of times the team has been evaluated as a non-preferred team is placed at the bottom, and the join information with the lowest number of times the team has been evaluated as a non-preferred team is placed at the top.

[0122] The join module (330) may also generate a join list that further displays the total number of join rounds. The join module (330) may also generate a join list that further displays the percentage of times a team was evaluated as a preferred team among the total number of join rounds.

[0123] The replacement module (340) responds to the booking team replacement request of the control module (310) and determines whether to replace the booking team.

[0124] The replacement module (340) detects the booking information of a golfer who has requested a booking team change. When a golfer identifier is detected from a booking team change request, the replacement module (340) detects a booking identifier of booking information including the golfer identifier from the booking database (260). The replacement module (340) detects booking information from the booking database (260), and detects booking information including the booking identifier detected from the booking team change request or the booking identifier detected from the booking database (260).

[0125] The replacement module (340) detects booking information having a tee-up time after the golfer's booking. The replacement module (340) detects booking information from the booking database (260), and detects booking information including a tee-up time after the golfer's tee-up time. The replacement module (340) detects, from among the detected booking information, booking information that can be booked by the number of team members of the golfer who requested a booking team change, as replacement booking information.

[0126] The replacement module (340) detects one booking information from among bookings adjacent to the tee-up time of the existing booking as replacement booking information, and detects booking information that allows for additional players as replacement booking information. For example, if the team of a golfer requesting a booking team change consists of two players, the replacement module (340) detects booking information with three or fewer players as replacement booking information.

[0127] The replacement module (340) detects one booking information from among the bookings adjacent to the tee-up time of the existing booking as replacement booking information, but detects booking information that allows for additional people without including non-preferred golfers of the golfer who requested the booking team change as replacement booking information.

[0128] When replacement booking information is detected, the replacement module (340) transmits the booking replacement result to the golfer team that requested the booking team replacement, the golfer team of the booking including the golfer, and the golfer team of the booking detected with the replacement booking information.

[0129] If replacement booking information is not detected, the replacement module (340) determines that the booking team cannot be replaced and sends a notification that the booking team cannot be replaced to the golfer team that requested the booking team replacement.

[0130] When one or more booking information is detected, the replacement module (340) generates a booking team replacement list and transmits it to the control module (310).

[0131] The replacement module (340) can create a booking team replacement list that displays the booking information of a team evaluated as a preferred team by a golfer among the booking information included in the booking team replacement list, distinguishing it from other booking information.

[0132] The replacement module (340) can generate a filtered booking team replacement list based on the golfer's evaluation information. The replacement module (340) can detect the evaluation information of the golfer requesting a booking team replacement and generate a booking team replacement list that only includes the booking information of the team evaluated as the preferred team based on the evaluation information.

[0133] Meanwhile, if replacement booking information is not detected, the replacement module (340) transmits a booking team replacement impossibility message to the control module (310).

[0134] The evaluation module (350) responds to the join booking team evaluation request from the control module (310) by performing a preference evaluation on the opposing team that participated in the round together through join booking. The evaluation module (350) sets the time from the time the concierge completes check-out to the evaluation deadline as the evaluation period, and performs the preference evaluation during the evaluation period.

[0135] The evaluation module (350) requests a preference evaluation of the opposing team through a join booking from the golfer terminal (100) of the golfer who participated in the round together. The evaluation module (350) receives the preference evaluation result from the golfer terminal (100), and receives the preference evaluation result including the golfer identifier of the evaluated golfer, the opposing team's golfer identifier, and the evaluation result (preferred or not preferred).

[0136] The evaluation module (350) updates the golfer database (220) based on the preference evaluation results of the golfer terminal (100).

[0137] The evaluation module (350) counts and updates the number of evaluations of a golfer who has performed a preference evaluation. The evaluation module (350) updates the number of evaluations by one more than the previous number of evaluations.

[0138] The evaluation module (350) updates the golfer information of the golfer who performed the preference evaluation. The evaluation module (350) adds the golfer identifier of the opposing team to the preferred team of the golfer who evaluated the opposing team as preferred. The evaluation module (350) adds the golfer identifier of the opposing team to the non-preferred team of the golfer who evaluated the opposing team as unpreferred.

[0139] The evaluation module (350) can collect preference evaluation results and set a reputation score.

[0140] The evaluation module (350) can set a reputation score reflecting the preference evaluation time point. The evaluation module (360) can be configured to set a higher index for more recent results based on the preference evaluation time point, thereby increasing the reflection rate of recent preference evaluations.

[0141] The evaluation module (350) can be configured to set a low index for the preference evaluation of the golfer when the preference evaluation of the same golfer is repeated, thereby lowering the reflection rate when the preference evaluation is repeatedly input from the golfer.

[0142] The settlement module (360) responds to the cost presentation request from the control module (310) by presenting the golf round cost for the booking team that completed the golf round. The settlement module (360) presents the golf round cost including green fees, cart fees, and caddy fees.

[0143] The settlement module (360) differentiates and presents golf round costs based on the composition of the booking team. The settlement module (360) determines the golf round cost upon completion of the booking, and differentiates and presents the golf round cost based on tee time / time zone and number of players (game / team).

[0144] When a booking team consists of four golfers, the settlement module (360) presents a standard golf round fee. The settlement module (360) presents the same golf round fee (i.e., 1 / 4 of the standard golf round fee) to the four golfers in the booking team.

[0145] When a booking team consists of five people, the settlement module (360) proposes a golf round cost that is higher than the standard golf round cost and lower than the golf round cost for five people (i.e., 5 / 4 of the standard golf round cost). In other words, the settlement module (360) proposes a golf round cost that is higher than the standard golf round cost, while providing a discount on the golf round cost for each golfer.

[0146] Accordingly, the golf booking server (300) can increase the cost satisfaction of both golfers and golf course operators by reducing the cost of each golf round while increasing the cost of the golf course. Specifically, when booking for five people, golfers can use the golf course at a lower cost than when booking for four people. Furthermore, the golf course can offer a relatively higher profit per booking because the higher cost of a golf round is normalized compared to a four-person booking.

[0147] The settlement module (360) differentiates and presents golf round costs based on join conditions during join booking. In this case, the settlement module (360) presents a relatively higher golf round cost as the number of join conditions increases.

[0148] The settlement module (360) sets a set number of join conditions as the standard golf round cost. If the number of join conditions exceeds the set number, the settlement module (360) presents the golf round cost so that it sequentially increases from the standard golf round each time a join condition is added.

[0149] The settlement module (360) differentiates and presents the cost of a golf round according to the number of people in each team that makes up the join booking.

[0150] The settlement module (360) maintains the total golf round cost of the join booking the same, and sets the golf round cost for golfers in a majority team higher than that for golfers in a minority team. If the number of golfers in the first golf team is 3, and the number of golfers in the second golf team that joined the first golf team is 1, the settlement module (360) sets the golf round cost based on 4 people, but presents a higher golf round cost to golfers in the first golf team than to golfers in the second golf team.

[0151] The settlement module (360) differentiates and presents golf round fees based on whether the tee-up time (i.e., tee-off) is confirmed at the time of joining booking. The settlement module (360) presents a higher golf round fee to teams that join by setting a tee-up time to a specific time than to teams that join by setting a tee-up time to a specific time.

[0152] The settlement module (360) presents the costs incurred by golfers who have made joint bookings for rest areas between rounds, by team. If the first and second golfer teams have made joint bookings, the settlement module (360) presents the food and beverage costs incurred in rest areas (e.g., shade houses) between rounds separately as the first golfer team's costs and the second golfer team's costs.

[0153] The settlement module (360) can change the golf round cost presented at the time of booking and present it to the golfer terminal (10). When the booking team is changed, the settlement module (360) reflects the personnel composition of the existing booking team and the changed booking team, joining conditions, etc., and presents the recalculated golf round cost to the golfer terminal (10).

[0154] For example, the settlement module (360) suggests a relatively lower golf round fee compared to the opposing team in the first half of the round due to a smaller number of golfers in the existing booking team. If the booking team is replaced in the second half of the round and the golfer team is booked with another golfer team with a relatively smaller number of golfers, the settlement module (360) suggests a relatively higher golf round fee compared to the opposing team in the second half of the round. The settlement module (360) presents the combined golf round fee and the second half of the round to the golfer terminal (10), and the newly presented golf round fee is an increased golf round fee compared to the time when the booking was completed.

[0155] Meanwhile, referring to FIG. 10, the golf booking server (300) may be configured to include a communication unit (372), a memory (374), and a processor (376). Here, in FIG. 9, in order to easily explain the operation of the golf booking server (300) according to an embodiment of the present invention, the golf booking server (300) is illustrated and described as being configured to include a plurality of modules, but the communication unit (372), the memory (374), and the processor (376) may be configured to perform the operation of each of the modules described above.

[0156] The communication unit (372) can exchange data with external devices. Depending on the embodiments, the communication unit (372) can exchange data according to a wired or wireless communication protocol. That is, the communication unit (372) can exchange data with multiple golfer terminals (100) and a database (200) according to wired or wireless communication protocols.

[0157] The memory (374) can store data necessary for the operation of the golf booking server (300). According to embodiments, the memory (374) can store a program (i.e., a golf booking application) including a plurality of commands for performing various operations performed by the golf booking server (300). In addition, the memory (374) can store data transmitted from or to be transmitted to the outside.

[0158] The processor (376) can control the overall operation of the golf booking server (300). According to embodiments, the processor (376) has a computational processing function, executes an application stored in the memory (374), and performs multiple operations according to instructions included in the application. For example, the processor (376) can perform the multiple operations by controlling the communication unit (372) and the memory (374).

[0159] According to embodiments, some functions of the processor (376) may be implemented separately, additionally or alternatively, as part of the communication unit (372) and / or memory (374) of the golf booking server (300).

[0160] The processor (376) is configured to provide a booking function that generates bookings for a golf round through join booking, booking join, and general booking. The processor (376) may be configured as a single processor (376) that performs all functions, or as multiple processors (376) that perform individual functions.

[0161] Join booking allows golfers to join through join conditions, but there are problems such as difficulty or discomfort in playing a round of golf together due to other golfers' bad manners, nagging, and slow progress.

[0162] Accordingly, the processor (376) provides a booking team change function that allows a golfer to request a booking team change so that the golfer can play a round of golf with another team if the golfer wishes to change the booking team.

[0163] When a request for a booking team change is received from a golfer between the first and second half (or between the first and middle, or between the middle and the second half) of a golf round through the communication unit (372), the processor (376) allows the golfer who requested the booking team change to join another team and play a golf round if there is an empty spot in the team at a later time based on the time at which the golfer's request for a booking team change was entered.

[0164] The processor (376) provides a booking team evaluation function that evaluates the preference of the golfer for the companion team (or opposing golfer) with whom the golfer played a round of golf through a join booking after the golfer's golf round is completed.

[0165] After a golf round via booking is concluded, the processor (376) performs a booking team evaluation function. The processor (376) receives a preference evaluation for the accompanying team (i.e., the booking team) from the golfer terminal (100) via the communication unit (372). At this time, the processor (376) receives one of the preferences or non-preferences as the preference evaluation for the accompanying team.

[0166] The processor (376) provides various services to golfers using the preference evaluation results.

[0167] The processor (376) performs a preference evaluation function for the joining team (joining golfer) to enhance the experience satisfaction of a joining golf round through joining booking. To activate the preference evaluation, the processor (376) provides various benefits to golfers who have completed the preference evaluation. In this case, the processor (376) provides various benefits to golfers who have completed the preference evaluation more than a set number of times.

[0168] For example, the processor (376) prevents a join booking that includes a golfer evaluated as unfavorable during a join in the booking function from being exposed in the join booking list. In other words, the processor (376) provides a join booking list that removes the join booking of a golfer evaluated as unfavorable during a join, thereby providing a different join booking list for each golfer (team).

[0169] As another example, the processor (376) transmits a notification to the golfer terminal (100) when a golfer evaluated as preferred in the booking function makes a join booking (creation), thereby enabling the golfer to join another golfer preferred by the golfer.

[0170] As another example, the processor (376) displays multiple join bookings that can be joined in a join booking list when a golfer joins, and displays join bookings that include golfers evaluated as preferred so that they are distinguished from other join bookings. Through this, the processor (376) enables the golfer to easily identify join bookings that include golfers they prefer.

[0171] The processor (376) may be configured to provide a benefit to a golfer who has received a high number of preferred ratings from other golfers.

[0172] For example, the processor (376) is configured to generate a join booking list including join information and a number of preferred evaluations. The processor (376) is configured to generate a join booking list including a plurality of visible booking information, but further including the number of preferred evaluations of the golfer who generated the join information.

[0173] In another example, the processor (376) is configured to generate a join booking list sorted based on the number of preferred evaluations. Accordingly, the join booking list is arranged with the join booking with the highest number of preferred evaluations at the top.

[0174] As another example, the processor (376) is configured to provide reservation priority to golfers whose preference ratings exceed a preset number. Specifically, the processor (376) may set the join booking time for golfers without reservation priority to 8:00 a.m., and for golfers with reservation priority to approximately 7:00 a.m. In other words, the processor (376) allows golfers with preference ratings exceeding a preset number to reserve join bookings earlier than other golfers.

[0175] In this way, the processor (376) increases the satisfaction of the experience of a join golf round while relieving the inconvenience of a join golf round through exchanging booking teams, evaluating preferences, and providing benefits based on the results of the preference evaluation.

[0176] The processor (376) is configured to provide a settlement function that presents booking conditions and costs incurred during a round of golf.

[0177] For example, the processor (376) may be configured to differentiate the cost of a round of golf based on the number of people in the booking.

[0178] Processor (376) typically provides a standard golf round cost based on a 4-person booking.

[0179] The processor (376) proposes a golf round fee that is higher than the fee for a four-person golf round when booking as a team of five (joint booking, general booking) and lower than the fee for a five-person golf round. The processor (376) proposes a discounted golf round fee to each golfer included in a five-person booking, and the total golf round fee is configured to be higher than the fee for a four-person booking.

[0180] Accordingly, the processor (376) can increase the cost satisfaction of both golfers and golf course operators by reducing the cost of each golf round while increasing the cost of the golf course. Specifically, in a five-person booking, golfers can use the golf course at a lower cost than in a four-person booking, and the golf course can offer a relatively higher profit per booking because the higher cost of the golf round is normalized compared to a four-person booking.

[0181] As another example, the processor (376) may be configured to differentiate the cost of a golf round based on the join conditions during a join booking. The more stringent the join conditions (i.e., the more conditions there are), the more difficult it is to join with other teams. Accordingly, the processor (376) is configured to offer a relatively higher golf round cost when the join conditions are stringent.

[0182] The processor (376) may be configured to set a set number of join conditions as a standard golf round cost, and to present a golf round cost that sequentially increases from the standard golf round each time a join condition is added when the number of join conditions exceeds the set number.

[0183] As another example, the processor (376) may be configured to differentiate and present a golf round cost based on the number of players in each team forming a join booking. That is, the processor (376) maintains the overall golf round cost of the join booking the same, and sets a higher golf round cost for golfers in a majority team than for golfers in a minority team. If the number of players in the first golf team is 3, and the number of players in the second golf team that joins the first golf team is 1, the processor (376) may set a golf round cost based on 4 players, but may set a higher golf round cost for golfers in the first golf team than for golfers in the second golf team.

[0184] As another example, the processor (376) may be configured to present a golf round fee based on whether a tee-up time (i.e., tee-off) is confirmed at the time of joining booking. The processor (376) may present a higher golf round fee to a team that joins by setting the tee-up time to a specific time during joining booking than to a team that joins by setting the tee-up time to a specific time.

[0185] In this way, the processor (376) can prevent a decline in the golf course's profits by reducing the round cost of golfers who enjoy rounds under various conditions by presenting costs according to various join conditions such as join conditions, time, and number of people.

[0186] As another example, the processor (376) may be configured to present, by team, the costs incurred by golfers who have made joint bookings for a rest area (e.g., a shade house) between golf rounds. In the case where the first and second golfer teams have made joint bookings, the processor (376) is configured to present the food and beverage costs incurred in the shade house between golf rounds separately as the first golfer team cost and the second golfer team cost.

[0187] Typically, golf courses present the cost of a rest area per booking, requiring golfers who have made a joint booking to submit the cost again. In contrast, the processor (376) according to an embodiment of the present invention presents the cost of a rest area per team, thereby eliminating the need for golfers who have made a joint booking to submit the cost, making joint bookings more accessible to golfers.

[0188] The above description is merely an illustrative illustration of the technical idea of ​​the present invention, and those skilled in the art will appreciate that various modifications and variations can be made without departing from the essential characteristics of the present invention. Therefore, the embodiments disclosed in the present invention are intended to illustrate rather than limit the technical idea of ​​the present invention, and the scope of the technical idea of ​​the present invention is not limited by these embodiments. The scope of protection of the present invention should be interpreted by the following claims, and all technical ideas within a scope equivalent thereto should be interpreted as being included in the scope of the rights of the present invention.

[0189] The server described above may be implemented as hardware elements and / or software elements. For example, the server may be implemented using one or more general-purpose computers or special-purpose computers, such as a processor, a controller, an arithmetic logic unit (ALU), a digital signal processor, a microcomputer, a field programmable gate array (FPGA), a programmable logic unit (PLU), a microprocessor, or any other device capable of responding to and executing instructions in a defined manner. The server may run an operating system (OS) and one or more software applications running on the operating system. Additionally, the server may access, store, manipulate, process, and generate data in response to the execution of the software. For simplicity, the server may be described as a single server; however, those skilled in the art will recognize that the server may include multiple processing elements and / or multiple types of processing elements. For example, the server may include multiple processors, or a processor and a controller. Additionally, other processing configurations, such as parallel processors, are also possible.

[0190] The software may comprise computer programs, codes, instructions, or a combination thereof, which may independently or collectively configure or command a server to perform a desired operation. The software and data may be embodied permanently or temporarily in the form of propagated signal waves that can be interpreted by the server or provide instructions or data to the server, or in various types of machines, components, physical devices, virtual equipment, computer storage media, or devices. The software may be distributed across networked computer systems and stored and executed in a distributed manner. The software and data may be stored on one or more computer-readable recording media, including data storage devices that store data and can later be read by a computer system or server. The method according to the embodiment may be implemented in the form of program instructions that can be executed by various computer means and recorded on a computer-readable medium. Examples of computer-readable recording media include ROM, RAM, CD-ROM, magnetic tape, floppy disk, and optical data storage devices. It includes magnetic media such as hard disks, floppy disks and magnetic tapes, optical media such as CD-ROMs and DVDs, magneto-optical media such as floptical disks, and hardware devices specifically configured to store and execute program instructions such as ROMs, RAMs and flash memories.Additionally, the functional programs, codes, and code segments that accomplish the examples disclosed herein can be easily understood and implemented by a programmer having ordinary skill in the art related to these examples based on or using the flowcharts and block diagrams of the drawings and the descriptions provided herein.

[0191] Although not universally applicable, the golf terminal described herein may be applied to mobile devices such as cellular telephones, PDAs, digital cameras, portable game consoles, MP3 players, portable / personal multimedia players (PMPs), portable e-books, portable laptop PCs, GPS navigation, tablets, sensors, and desktop PCs, HDTVs, optical disc players, set-top boxes, home appliances, and devices capable of wireless or network communication.

[0192] And the above computer-readable medium may include program commands, data files, data structures, etc., alone or in combination. The program commands recorded on the medium may be specially designed and configured for the embodiment or may be known and available to those skilled in the art of computer software. Examples of the program commands include not only machine language codes such as those generated by a compiler, but also high-level language codes that can be executed by a computer using an interpreter, etc. The above-mentioned hardware device may be configured to operate as one or more software modules to perform the operations of the embodiment, and vice versa.

[0193] While various embodiments have been described above, it should be understood that various modifications are possible. For example, appropriate results may still be achieved if the described techniques are performed in a different order, and / or if elements of the described systems, structures, devices, circuits, etc. are combined in different ways, or if other elements or equivalents are substituted or supplemented. Accordingly, other implementations fall within the scope of the following claims.

Claims

1. In a golf booking server connected to enable communication with multiple golfer terminals, A communication circuit configured to exchange data with the plurality of golfer terminals; memory; and One or more processors configured to load commands stored in the memory and perform one or more operations according to the execution of the commands, wherein the one or more processors control the golf booking server to communicate with the plurality of golfer terminals. In response to a join booking request transmitted from the plurality of golfer terminals, a first booking is created by joining a first golfer team and a second golfer team, When the golf round of the above first booking is completed, the first golfer team and the second golfer team are asked to evaluate their preference for the opposing team, A golf booking server that links and stores the results of preference evaluations of golf teams that have evaluated preferences for booking teams.

2. In paragraph 1, One or more of the above processors, A golf booking server that responds to a booking team change request transmitted from a golfer terminal of the first golfer team in a previous round of the golf round of the first booking by joining the first golfer team to a second booking and changing the booking team of the first golfer team in the next round of the golf round.

3. In paragraph 2, One or more of the above processors, A golf booking server that detects a booking in progress of a previous round of the golf round among one or more bookings having a tee-up time after the tee-up time of the first booking as the second booking.

4. In paragraph 2, One or more of the above processors, When the golf round of the above first booking is completed, a preference evaluation for the above first golfer team is requested from the golfer terminal of the above second golfer team, When the golf round of the second booking is completed, a preference evaluation for the third golfer team of the second booking and the second golfer team is requested to the golfer terminal of the first golfer team, and a preference evaluation for the first golfer team is requested to the golfer terminal of the third golfer team. A golf booking server that receives, from the golfer terminals of the first golfer team to the third golfer team, one of the preferences and non-preferences as a preference evaluation result for the booking team.

5. In paragraph 1, One or more of the above processors, In response to a join request received from a golfer terminal, a join booking list including one or more join booking information is transmitted to the golfer terminal. A golf booking server that transmits to the golfer terminal a join booking list that does not include join booking information of golfer teams that the golfer team of the golfer terminal has evaluated as unfavorable in the previous golf round.

6. In paragraph 1, One or more of the above processors, In response to a join request received from a golfer terminal, a join booking list including one or more join booking information is transmitted to the golfer terminal. A golf booking server that transmits to the golfer terminal a join booking list that displays the join booking information of the golfer team that the golfer team of the golfer terminal has evaluated as preferred in the previous golf round, distinguishing it from other join booking information.

7. In paragraph 1, One or more of the above processors, Send a join booking creation alarm to the golfer terminal, A golf booking server that transmits a join booking creation alarm to the golfer terminal when a join booking is created for a golfer team that the golfer terminal has evaluated as preferred in a previous golf round.

8. In paragraph 1, A golf booking server that activates priority reservations for golfer terminals that have received preference ratings from other golfers more than a set number of times, wherein the above one or more processors are provided.

9. In paragraph 1, One or more of the above processors, A golf booking server that offers each golfer in a 5-person booking a lower round of golf cost than each golfer in a 4-person booking.

10. In paragraph 1, One or more of the above processors, When booking a join, the cost of a golf round is differentiated and presented based on the join conditions received from the golfer's terminal. A golf booking server that offers different golf round costs depending on the join conditions set in the golfer terminal.

11. In paragraph 10, One or more of the above processors, Golf booking server that offers higher golf round rates when you set difficult join conditions with other golf teams.

12. In paragraph 10, One or more of the above processors, When booking a join, the cost of a golf round is differentiated and presented based on the join conditions received from the golfer's terminal. Golf booking server that offers different golf round costs depending on the number of join conditions.

13. In paragraph 10, One or more of the above processors, A golf booking server that offers a higher golf round fee to golfers in a larger golf team than to golfers in other golf teams when making a join booking.

14. In paragraph 1, One or more of the above processors, A golf booking server that offers a higher golf round price to a team of golfers who set their tee time to a specific time than to a team of golfers who set their tee time to a specific time.

Images