JP5802143B2 - Server, control method and program - Google Patents

Description

  The present invention relates to a technique for managing play information (play result, play date, etc.) of a user who has played sports in a sports facility.

  For example, Patent Document 1 describes a golf course management apparatus that provides score management services to members of a golf course. Patent Documents 2 and 3 describe that the scores of users who have played golf at a plurality of golf courses are centrally managed by a server.

JP 2004-113535 A JP 2004-246858 A Japanese Patent Laid-Open No. 2004-078492

  By the way, since the server which manages a user's score centrally and a golf course management apparatus are separate systems, each user's score data is managed by giving a user ID independently. That is, even for the same user, the user ID given by the server and the user ID given by the golf course management apparatus are different. Since the user ID used in the server is different from the user ID used in the golf course management device in this way, the problem is that score data cannot be transferred between the server and the golf course management device. was there.

  The present invention has been made in view of the above-described circumstances, and even when the server and the management device manage each user's play information using their own user identification information. It is a problem to be able to exchange play information between the two.

  Means employed by the present invention to solve the above problems will be described below. In addition, in order to make an understanding of this invention easy, the reference sign of an accompanying drawing is attached in parenthesis writing, However, This invention is not limited to the aspect of illustration.

  The server (10) according to the present invention manages play information including a play result of a user who played sports at a sports facility (G), and provides the play information to a terminal (50) operated by the user. (10) Management for managing the play information of the user and the facility information indicating the sports facility (G) played by the user in association with the first user identification information for identifying the user Part (110, 150) and first user identification information and facility information associated with play information designated from the terminal (50) among information managed by the management part (110, 150) A specifying unit (110) for specifying the user, a first acquisition unit (110) for acquiring personal information of the user specified by the first user identification information specified by the specifying unit (110), and the specifying unit ( A management device (20) for managing each user's play information and personal information in the sports facility (G) specified by the facility information identified by 10) in association with second user identification information for identifying the user; A second acquisition unit (110, 140) that accesses and acquires the second user identification information that matches the personal information acquired by the first acquisition unit (110), the designated play information, and the first And a transmission unit (110, 140) for transmitting the second user identification information acquired by the two acquisition unit (110, 140) to the management device (20).

  According to the above configuration, for example, when the server X transmits play information of the user X at the sports facility A to the management device of the sports facility A, the server changes the personal information of the user X from the management device of the sports facility A. The adapted second user identification information is acquired, and the acquired second user identification information and the play information of the user X are transmitted to the management device of the sports facility A. Thus, by acquiring the second user identification information that matches the personal information of the user X from the management device of the sports facility A, the second management device of the sports facility A assigned to the user X User identification information can be acquired. Therefore, even when the server and the management device each manage the play information of each user using unique user identification information, the first user identification information used by the server, The inconsistency with the second user identification information used by the management device is resolved, and the play information of the user X transmitted from the server is registered as the play information of the user X even in the management device of the sports facility A. It becomes possible.

  The “sport facility” is, for example, a golf course, a bowling alley, a tennis court, a sports gym, a swimming club, an athletic stadium, or the like. Also, the “sport facility” includes a golf bar in which a virtual golf machine is installed. As is clear from this, “sports” includes, for example, golf, bowling, tennis, swimming, various athletics, and the like. The “play result” is, for example, a score, winning / losing, ranking, time, and the like. In addition to the play result, “play information” may include, for example, play date, weather, information about users who played together, and the like. As the “facility information”, in addition to the facility identification information for uniquely identifying the sports facility, the facility name, information combining the facility name and the name of the location, or the like can be used. “Personal information” is, for example, one or more of name, date of birth, address, telephone number (home or mobile phone), and mail address. The “first user identification information” is user identification information used for managing play information and the like on the server, and the “second user identification information” is a user used for managing play information and the like on the management device. Identification information. Information managed by the management unit may be stored in the server, or may be stored in a device different from the server. That is, the database that stores the “play information”, “facility information”, and “first user identification information” in association with each other may be stored in a storage unit included in the server, or in a device different from the server. You may memorize | store in the memory | storage part with which it is equipped. The first acquisition unit may acquire the personal information of the user from within the server or may be acquired from a device different from the server. That is, the user's personal information may also be stored in a storage unit provided in the server, or may be stored in a storage unit provided in a device different from the server.

  Also, information managed by the management device may be stored in the management device, or may be stored in a device different from the management device. That is, the database that stores the “play information”, “personal information”, and “second user identification information” in association with each other may be stored in a storage unit provided in the management apparatus, or may be different from the management apparatus. You may memorize | store in the memory | storage part with which an apparatus is equipped. In addition, the database associates and stores "play information" and "second user identification information", "personal information" and "second user identification information". You may divide into the 2nd database to store. Moreover, the management apparatus should just be the structure which can link and manage play information with 2nd user identification information, and does not necessarily need to hold | maintain play information. In addition, the management device, for example, a first management server that manages “play information” and “second user identification information” in association with each other, “personal information”, and “second user identification information” And a second management server that manages them in association with each other. The “play information” managed by the server and the “play information” managed by the management device may have different data configurations. For example, “play information” managed by the server may be composed of a play result, a play date, and weather, while “play information” managed by the management device may be composed of a play result and a play date. Further, the data formats (data recording formats) of the two may be different. The transmission unit may not transmit “play information” and “second user identification information” together to the management device. For example, the transmission unit may transmit “play information” first, and when there is an inquiry about a user from the management apparatus, it may transmit “second user identification information” in response to the inquiry.

  Further, in the server (10) described above, the management unit (110, 150) specifies the second user identification information acquired by the second acquisition unit (110, 140) by the specifying unit (110). The second acquisition unit (110, 140) associates with the first user identification information and the facility information specified by the specifying unit (110). When the second user identification information is managed by the management unit (110, 150), the second user identification information is acquired from the management unit (110, 150), and the specifying unit (110 110) If the second user identification information is not managed in the management unit (110, 150) in association with the first user identification information and facility information specified by 110), the management device (20) is accessed. And the first The resulting unit (110) may acquire the second user identification information compatible with the acquired personal information.

  In this case, for a combination of “user” and “management device” that has transmitted play information even once in the past, when the play information is transmitted from the next time onward, the processing by the first acquisition unit and the second acquisition are performed. The processing by the unit can be omitted. For this reason, the processing required for transmitting play information can be simplified and the processing time can be shortened. In this case as well, the “second user identification information” acquired by the second acquisition unit and the “first user identification information” and “facility information” specified by the specifying unit are stored in association with each other. May be stored in a storage unit provided in the server, or may be stored in a storage unit provided in a device different from the server.

  Further, in the server (10) described above, the play information further includes date information indicating a play date, and the second acquisition unit (110, 140) accesses the management device (20), The second information that matches the personal information acquired by the first acquisition unit (110) and the date information included in the designated play information or the date / time information indicating the play date input from the terminal (50). User identification information may be acquired.

  For example, when the second user identification information is acquired using the name as personal information, there is a possibility that there is a person with the same surname and the same name, so the second user identification information may not be narrowed down to one. . In addition, when the second user identification information is acquired using the home address or the home phone number as personal information, there may be a plurality of users of the same sports facility in the family. There are cases where the user identification information cannot be narrowed down to one. The management device manages “play information” in addition to “personal information” in association with “second user identification information”, and this “play information” includes information on play dates. . In addition, even if the play result is not registered in the management device, the second use can be made in accordance with the reservation for the use of the sports facility and the fact that the user has accepted at the front of the sport facility on the day of the play day. In many cases, user identification information and play date information are registered. Therefore, in addition to the personal information, the second user identification information is acquired using the date information of the play date included in the play information to be transmitted or the date information of the past play date input by the user of the terminal. Thus, the acquisition accuracy of the second user identification information can be increased. Note that the date information of the play date may include information on the time of play.

In the server (10) described above, when the second acquisition unit (110, 140) includes a plurality of second user identification information that matches the personal information acquired by the first acquisition unit (110), Personal information associated with each of the plurality of second user identification information is acquired from the management device (20) and transmitted to the terminal (50), and the terminal (50) among the transmitted personal information. The second user identification information associated with the personal information designated by the user is determined as the second user identification information transmitted to the management device (20) in association with the designated play information. Good.
According to this configuration, when the second user identification information cannot be narrowed down to one, the personal information of a plurality of candidates is presented to the terminal user, and the final selection is made to the terminal user. Can be done.

  In the server (10) described above, when the first user identification information and the facility information are designated from the terminal (50), the first acquisition unit (110) designates the designated first user. The personal information of the user specified by the identification information is acquired, and the second acquisition unit (110, 140) accesses the management device (20) corresponding to the designated facility information, and the first acquisition The second user identification information that matches the personal information acquired by the unit (110) and the play information associated with the second user identification information are acquired, and the management unit (110, 150) The play information acquired by the second acquisition unit (110, 140) may be managed in association with the specified first user identification information and facility information.

  According to the above configuration, for example, when the play information of the user X is acquired from the management device of the sports facility A, the server matches the personal information of the user X from the management device of the sports facility A. By acquiring the user identification information, it is possible to acquire the second user identification information given to the user X by the management device of the sports facility A. Therefore, the user identification information is associated with the second user identification information. It is possible to acquire the play information of the user X by acquiring the played information from the management device of the sports facility A. Therefore, even when the server and the management device each manage the play information of each user using unique user identification information, the first user identification information used by the server, The inconsistency with the second user identification information used by the management device is resolved, the play information of the user X is acquired from the management device of the sports facility A, and this is also used as the play information of the user X on the server. Can be managed. In addition, since the play information of the user X can be acquired from each management device and managed by the server, the play information of the user X can be centrally managed by the server.

  In the server (10) described above, the management unit (110, 150) uses the second user identification information acquired by the second acquisition unit (110, 140) as the designated first use. The second acquisition unit (110, 140) manages the user identification information and facility information in association with the designated first user identification information and facility information, and manages the management unit (110, 150). When the second user identification information is managed, the play information associated with the second user identification information is acquired from the management device (20), and the designated first user is obtained. When the second user identification information is not managed by the management unit (110, 150) in association with the identification information and the facility information, the management device (20) is accessed and the first acquisition unit (110) is accessed. Acquired A second user identification information compatible with the human information, may be acquired and play information associated with the second user identification information.

  In this case, for the combination of “user” and “management device” that has transmitted or acquired play information even once in the past, the process of acquiring personal information when acquiring play information from the next time, The process of acquiring the second user identification information that matches the acquired personal information from the management apparatus can be omitted. For this reason, the processing required for transmitting play information can be simplified and the processing time can be shortened.

Further, in the server (10) described above, the management unit (110, 150) manages the second acquisition unit (110, 140) among play information associated with the second user identification information. You may acquire the play information which is not.
In this case, since the play information already managed by the server can be refrained from being acquired from the management apparatus, it is not necessary to acquire useless data.

Further, in the server (10) described above, when browsing of the play information is requested from the terminal (50), the management unit displays the play information requested to be browsed and the facility information associated with the play information. You may further provide the browsing control part (110,140) which acquires from (110,150) and transmits to the said terminal (50).
In this case, play information and facility information can be browsed on the terminal.

Further, in the server (10) described above, the management unit (110, 150) manages the play information of a plurality of users who have played together in association with the same identification information as accompanying play identification information, When the accompanying play identification information is associated with the play information requested to be browsed, the browsing control unit (110, 140) displays a plurality of pieces of play information associated with the accompanying play identification information as the management unit. (110, 150) and may be transmitted to the terminal (50).
In this case, it is possible to view the play information of the user who played together with the terminal.

Further, in the server (10) described above, a receiving unit (110, 140) for receiving play information of each of a plurality of users who have played together from the terminal (50), and the receiving unit (110, 140) You may further provide the provision part (110) which provides the said accompanying play identification information with respect to each of several received play information.
In this case, accompanying play identification information can be given by the server.

The present invention can also be understood as a server control method. In this case, the control method of the server (10) according to the present invention manages play information including a play result of a user who has played sports in the sports facility (G), and a terminal on which the user operates the play information ( 50) A control method of the server (10) provided to 50), wherein the play information of the user and the facility information indicating the sports facility (G) played by the user are used for identifying the user. The first user identification information and the facility information associated with the play information designated from the terminal (50) are identified from the information to be managed in association with the user identification information, and identified. The personal information of the user specified by the user identification information is acquired, and the play information and personal information of each user at the sports facility (G) indicated by the specified facility information are identified with the second user. The management device (20) managed in association with the user identification information is accessed, the second user identification information that matches the acquired personal information is acquired, the specified play information and the acquired second use The person identification information is transmitted to the management device (20).
According to the above structure, there exists an effect similar to the server (10) of this invention.

Moreover, this invention is specified also as a program for functioning a computer as the server (10) mentioned above. In this case, the program according to the present invention manages play information including a play result of a user who played sports at the sport facility (G), and provides the play information to the terminal (50) operated by the user. (10) a management unit that manages the play information of the user and the facility information indicating the sports facility (G) played by the user in association with the first user identification information for identifying the user ( 110, 150) and the first user identification information and facility information associated with the play information designated by the terminal (50) are specified from the information managed by the management unit (110, 150). A specifying unit (110), a first acquiring unit (110) for acquiring personal information of the user specified by the first user identification information specified by the specifying unit (110), and the specifying unit ( A management device (20) for managing each user's play information and personal information in the sports facility (G) specified by the facility information identified by 10) in association with second user identification information for identifying the user; A second acquisition unit (110, 140) that accesses and acquires the second user identification information that matches the personal information acquired by the first acquisition unit (110), and the designated play information and the first 2 The second user identification information acquired by the acquisition unit (110, 140) is caused to function as a transmission unit (110, 140) that transmits to the management device (20).
According to the above structure, there exists an effect similar to the server (10) of this invention. The program of the present invention is provided, for example, in a form recorded in a computer-readable recording medium to an administrator and installed in the computer, or provided in a form distributed via a communication network. Installed on. Examples of the recording medium include a CD-ROM and a USB memory.

  According to the present invention, even when the server and the management device manage each user's play information using unique user identification information, the play information is transferred between the two. Can do.

It is a block diagram which illustrates the whole structure of a management system. It is a figure which illustrates the data structure of user management DB of a golf course server. It is a figure which illustrates the data structure of play information management DB of a golf course server. It is a block diagram which illustrates the hardware constitutions of a SNS server. It is a figure which illustrates the data structure of profile management DB. It is a figure which illustrates the data structure of golf course management DB. It is a figure which illustrates the data structure of play information management DB. It is a figure which illustrates the data structure of user ID registration DB. It is a flowchart which illustrates the flow of round pre-processing. It is a figure which illustrates the data structure of a play information recording table. It is a sequence chart which illustrates the flow of browsing processing. It is a figure which shows the example of a screen display of a smart phone. It is a sequence chart which illustrates the flow of transmission processing of play information. It is a figure which shows the example of a screen display of a smart phone. It is a figure which shows the example of a screen display of a smart phone. It is a sequence chart which illustrates the flow of acquisition processing of play information. It is a sequence chart which shows the modification of a transmission process.

Embodiments of the present invention will be described below with reference to the drawings.
<1. Embodiment>
FIG. 1 is a block diagram illustrating the overall configuration of the management system 1.
A management system 1 shown in FIG. 1 is a system that manages play information (score, play date, etc.) of a user who has played golf on a golf course. For example, the management system 1, SNS (Social Networking Service) server 10, golf _{G 1,} G 2, ... _G golf server m stand provided corresponding to _{m 20} 1, ₂₀ 2, ... 20 _m And the Internet 30, a mobile communication network 40, and n smart phones 50 ₁ , 50 ₂ ,... 50 _n . Note that m and n are both integers of 2 or more. The mobile communication network 40 includes a base station, an exchange station, a gateway server, etc., which are not shown. The SNS server 10 can perform packet communication with each of the smartphones 50 ₁ , 50 ₂ ,... 50 _n via the Internet 30 and the mobile communication network 40. In addition, the SNS server 10 can perform packet communication with each of the golf course servers 20 ₁ , 20 ₂ ,... 20 _m via the Internet 30.

Hereinafter, in the present specification, each of the golf courses G ₁ , G ₂ ,... G _m will be referred to as “golf course G” and the golf course servers 20 ₁ , 20 ₂ ,. Each of _m is described as “golf course server 20”, and each of the smartphones 50 ₁ , 50 ₂ ,... 50 _n is described as “smart phone 50”.

  The SNS server 10 is a membership-based site, and communication between members to build new relationships and deepen exchanges with friends through connections such as hobbies, preferences, residential areas, and schools of origin. To provide a place. For example, the functions provided by the SNS server 10 include a function of releasing one's own profile to other members, a function of exchanging messages between members, and an address book for registering friends and circle friends (both members). Functions, hobbies and areas, etc. are decided, a bulletin board is created, and there is a function to interact with members who have the same hobbies or members who live in the same region. With these functions, for example, members who have golf as a hobby through the SNS server 10 can exchange information, or recruit members who play golf together.

  Further, the SNS server 10 has a function of managing play information (scores, play dates, etc.) of members who played golf on the golf course G. The member can operate his / her smartphone 50 to access the SNS server 10 and browse play information managed by the SNS server 10. The SNS server 10 also has a function of transmitting member play information managed by the SNS server 10 to the golf course server 20 and a function of acquiring past play information of members from the golf course server 20.

The golf course server 20 is provided, for example, for each golf course G, and provides a user of the golf course G with a management service for play information such as a score and a play date, and a use reservation service for the golf course G. The users of the golf course G include visitors other than the members in addition to the members who have the membership of the golf course G. For example, as shown in FIG. 1, golf server 20 ₁ is provided for golf G _1, golf server 20 ₂ is provided for golf G _2, ... golf against golf G _m If the server 20 _m is provided, the golf course server 20 _1, and user management DB (DataBase) 21 ₁ for managing personal information of a user of the golf _{G 1,} the golf _{G 1} of the user play information management to manage the play information DB22 ₁ and is stored. In addition, the golf course server 20 _2, the user management DB 21 ₂ and play information management for golf _{G 2} DB 22 ₂ is stored in the golf course server 20 _m, the user management DB 21 _m for golf _{G m} And the play information management DB 22 _m is stored.

In addition, the golf course server 20 is not restricted to the aspect provided for every golf course G. For example, a plurality of golf courses G may be managed by one golf course server 20. Further, the installation location of the golf course server 20 may be inside the golf course G or outside the golf course G. In addition, each golf course server 20 uniquely assigns a user ID (IDentification) to manage the personal information and play information of the user, and each golf course server 20 manages the user's managing information. In addition to different personal information and play information, the user ID used is also different. Hereinafter, in the present specification, each of the user management DBs 21 ₁ , 21 ₂ ,... 21 _m will be referred to as “user management DB 21” and play information management DBs 22 ₁ , 22 ₂ ,. ... 22 _m is described as “play information management DB 22”.

  The smartphone 50 is a small computer having the function of a mobile phone. For example, the smartphone 50 includes a voice call function, a web browsing function, an e-mail transmission / reception function, a GPS (Global Positioning System) positioning function, and the like. The member can operate his / her smartphone 50 to access the SNS server 10 and enjoy various services provided by the SNS server 10. In addition, in the storage (auxiliary storage device) of the smartphone 50, a golf navigation application 51 (hereinafter referred to as “golf navigation application 51”) that supports golf play using the GPS function is installed. .

  The golf navigation application 51, for example, measures the current position of a user who is playing golf with the smartphone 50, specifies the golf course G or hole that is playing, the course of the hole that is being played It has a function to display the layout, a function to advise how to capture the hole being played, a function to calculate and notify the distance to the green, hazard and pin positions, and the shot flight distance. The golf navigation application 51 also has a function of inputting play information such as a score, a function of uploading the input play information to the SNS server 10, a function of browsing play information managed by the SNS server 10, and a golf course G. It has a function to make a reservation for use.

Figure 2 is a diagram illustrating a user management DB 21 ₁ of the data structure stored in the golf course server 20 ₁ of the hard disk. In the user management DB 21 ₁ , for each user of the golf course G _1, a user ID and a user's personal information (name, date of birth, address, and telephone number) are stored in association with each other. User ID is identification information for uniquely identifying a user of the golf G _1. For example, golf server 20 _1, to grant a new user ID for the new user of the golf course G _1, the grant the user ID, user management DB21 ₁ in association with the personal information of the user Register with. It is to be noted that the user management DB21 _1, as the personal information of the user, gender, age, occupation, e-mail address, information of the place of employment or the like may be further stored.

Figure 3 is a diagram illustrating a data structure of the play information management DB 22 ₁ stored in the golf course server 20 ₁ of the hard disk. The play information management DB 22 ₁ stores the play information (play date and score) of the user of the golf course G ₁ in association with the user ID. A play date is date information which shows the date which played golf. In this embodiment, a case where a play date and a score are managed as play information will be described. However, the score includes information such as the number of hits for each hole and the amount of stopper in addition to the total number of hits in 18 holes. . “NULL” indicates an empty state in which no score is registered. That is, if the score item is “NULL”, it means that the score is not registered.

For example, after the user has been playing golf at the golf course G _1, and if you submit a score card to the front, the user is sent the play information from SNS server 10 by operating the smartphone 50 to the golf course server 20 ₁ If you were instructed, user ID, and play information is registered in the play information management DB22 _1. In addition, in response to the user and if you make the use reservation of golf G ₁ by operating the smartphone 50, the user has spoofing reception in front of the golf course G ₁ on the day of the play date, the score user ID and play date except there also be registered in the play information management DB22 _1.

Incidentally, in FIGS. 2 and 3 has been illustrated user management DB 21 ₁ and play information management DB 22 ₁ stored in the golf course server 20 _1, golf server 20 other than ₁ stored in the golf course server 20 The user management DB 21 and the play information management DB 22 that are provided have a data structure that is substantially the same. However, as described above, since each golf course server 20 uniquely assigns a user ID, the user ID assigned by each golf course server 20 is different even for the same user.

FIG. 4 is a block diagram illustrating a hardware configuration of the SNS server 10.
The SNS server 10 includes a CPU (Central Processing Unit) 110, a ROM (Read Only Memory) 120, a RAM (Random Access Memory) 130, a communication IF (InterFace) 140, and a hard disk 150. Note that the SNS server 10 may further include an input unit such as a keyboard and a mouse, and a display unit such as a liquid crystal display. The CPU 110 controls each unit of the SNS server 10 by executing various programs stored in the ROM 120 and the hard disk 150. The ROM 120 stores a program that performs basic control of each unit of the SNS server 10. The RAM 130 is used as a work area for the CPU 110. The communication IF 140 controls packet communication performed between the smartphone 50 and the golf course server 20 under the control of the CPU 110. The hard disk 150 includes, for example, a profile management DB 151 and a golf course management, as well as a program for controlling processing performed by the SNS server 10 among play information transmission processing (FIG. 13) and acquisition processing (FIG. 16) described later. A DB 152, a play information management DB 153, and a user ID registration DB 154 are stored.

FIG. 5 is a diagram illustrating a data structure of the profile management DB 151.
In the profile management DB 151, for each member of the SNS server 10, a member ID and member profile information (name, date of birth, and telephone number) are stored in association with each other. The member ID is identification information that uniquely identifies a member of the SNS server 10. For example, the SNS server 10 assigns a new member ID to a new member who has registered a member, and associates the assigned member ID with the profile information of the member input at the time of member registration. Register with. Since the member ID is identification information given by the SNS server 10, it is different from the user ID used in each golf course server 20. That is, the member ID used in the SNS server 10 and the user ID used in each golf course server 20 are different. The profile management DB 151 may further store information such as address, gender, age, occupation, mail address, home phone number, office, etc., and face photo image data as member profile information. As the member ID, for example, a member's e-mail address or the phone number of the smartphone 50 owned by the member can be used.

FIG. 6 is a diagram illustrating a data structure of the golf course management DB 152.
The golf course management DB 152 stores a golf course ID, a golf course name, and an access method in association with each golf course G. The golf course ID is identification information for uniquely identifying the golf course G, and is given by the SNS server 10. When the golf course server 20 is provided for each golf course G, the golf course ID is also identification information for uniquely identifying not only the golf course G but also the golf course server 20. For example, in the case of “A country club” shown in the figure, the access method items include the URL (Uniform Resource Locator) of the golf course server 20 of “A country club” and the golf of “A country club”. An API (Application Program Interface) that defines a communication procedure and the like when performing exchange of play information with the venue server 20 and profile matching described later is registered.

  The operator of the SNS server 10 checks the golf course name and the access method (URL and API) in advance for all the golf courses G, and registers them in the golf course management DB 152 in association with the golf course ID. When a new golf course G is opened, the operator of the SNS server 10 checks the golf course name and the access method for the newly opened golf course G, and the golf course ID newly given by the SNS server 10 And is registered in the golf course management DB 152. In addition, as a golf course ID, the character string which combined the golf course name and the golf course name and the name of the location can also be used, for example.

FIG. 7 is a diagram illustrating a data structure of the play information management DB 153. As shown in FIG.
In the play information management DB 153, member play information (play date and score) is stored in association with the member ID, golf course ID, and round ID. In the present embodiment, the play information managed by the play information management DB 153 (SNS server 10) and the play information managed by the play information management DB 22 (golf course server 20) are the same, and the score includes As described above, in addition to the total number of hits in 18 holes, information such as the number of hits for each hole and the gain stop is included. The round ID is unique identification information for each party (a group of 3 to 4 people who round together), and is given by, for example, the SNS server 10. This round ID is used to identify the accompanying competitor. For example, in the play information management DB 153 shown in the figure, the four member IDs “M00000001” to “M00000003” and “M00000698” all played golf together because the round ID was “R00000001”. You can see that you are a member.

  The SNS server 10 registers member play information uploaded from the smartphone 50 in the play information management DB 153. The SNS server 10 can also acquire past play information of members from the golf course server 20 and register it in the play information management DB 153. In the play information management DB 153, one record is added for each piece of play information registered. For example, when three pieces of play information are registered in the play information management DB 153 as play information of a certain member, each of the three pieces of play information is stored in the play information management DB 153 as a separate record. In this way, a plurality of pieces of play information are registered in the play information management DB 153 as separate records. Therefore, for example, the CPU 110 can extract the play information of the member whose member ID is “M00000001” by searching the play information management DB 153 using the member ID “M00000001” as a search key. Further, the CPU 110 can extract the play information of each member in the golf course G having the golf course ID “G00001” by searching the play information management DB 153 using the golf course ID “G00001” as a search key, for example. .

FIG. 8 is a diagram illustrating a data structure of the user ID registration DB 154. As shown in FIG.
As described above, each golf course server 20 manages a user's play information by assigning a user ID independently, and the user IDs used are different. Further, the member ID used in the SNS server 10 is also different from the user ID used in each golf course server 20. For example, as will be apparent from the user ID registration DB 154 shown in the figure, for the member with the member ID “M00000001”, the user ID “001612” is assigned to the golf course server 20 with the golf course ID “G00001”. The golf course server 20 with the golf course ID “G00732” is assigned the user ID “YA-0001-1235”, and the golf course server 20 with the golf course ID “G00112” has the user ID. “GM0033361” is assigned. Therefore, in order to exchange play information between the SNS server 10 and each golf course server 20, it is necessary to eliminate the mismatch between the member ID and the user ID. For this reason, the SNS server 10 performs profile matching using profile information (personal information) with the golf course server 20 that delivers play information.

For example, in the play information management DB 153 shown in FIG. 7, in the play information with the record number “1”, the member with the member ID “M00000001” played golf at the golf course G with the golf course ID “G00001”. It is information indicating the play date and score when. When this play information is transmitted to the golf course server 20 with the golf course ID “G00001” (for example, the golf course server 20 ₁ ), the SNS server 10 sends the golf course server 20 ₁ to the member with the member ID “M00000001”. It is necessary to specify the user ID assigned by the user. For this reason it will be described in detail later, SNS server 10, access to the golf course server 20 _1, performs a profile matching using the personal information of members of the Member ID is "M00000001" (for example, name, phone number, etc.), It is specified that the user ID of this member is “001612”. Further, the SNS server 10 registers the user ID “001612” specified by the profile matching in the user ID registration DB 154 in association with the member ID “M00000001” and the golf course ID “G00001” (record number “FIG. 8”). 1 ").

  Thus, the user ID specified by profile matching is registered in the user ID registration DB 154 in association with the corresponding member ID and golf course ID. In addition, even if it is the same member, since user IDs differ for every golf course server 20, the user ID specified by profile matching is linked | related with the group of member ID and golf course ID, and it registers in user ID registration DB154. It is necessary to keep it.

  FIG. 9 is a flowchart showing the flow of the round pre-processing executed in the smartphone 50. Members of the SNS server 10 can recruit members who play golf together using the bulletin board function of the SNS server 10 or the like. In addition, any one member (representative) who plays golf together carries the smartphone 50 and plays golf. For example, the representative can enter the golf course G on the day of play. When arriving, the smartphone 50 is operated to start the golf navigation application 51 before starting the play, and the execution of the round pre-processing is instructed.

  When the round pre-processing is started, first, the smartphone 50 performs a selection process of the golf course G to be played (step S101). For example, the smartphone 50 can display a list of golf courses G on the screen and allow the representative to select the golf course G from the list. The smartphone 50 may identify the golf course G from the current position measured using the GPS function, display the name of the identified golf course G on the screen, and ask the representative for confirmation. Moreover, the smart phone 50 may make a representative input the name of the golf course G to play. In addition, the golf navigation application 51 has the database which linked | related and recorded golf course ID, the golf course name, and the positional information on the golf course G for every golf course G, and the smart phone 50 plays golf course G to play. Is selected, the corresponding golf course ID is specified with reference to this database.

  Next, the smartphone 50 performs a play date input process (step S102). For example, the smartphone 50 may cause the representative to directly input the play date (year / month / day), or may acquire information on the current date using a calendar function, and may use this as the play date. The smartphone 50 displays a play start button for instructing the start of play on the screen. When the play start button is touched, the smartphone 50 acquires information on the current date using the calendar function, and uses this as the play date. Also good. In addition, since the same golf course G may be rounded multiple times a day, play date information (year / month / day / minute) including the play start time may be used instead of the play date.

  Next, the smartphone 50 performs a companion player selection process (step S103). When all the members who play golf together are members of the SNS server 10, the companion player may be registered in the representative's address book (for example, a friend list or a golf companion list) in the SNS server 10. Many. Therefore, the smart phone 50 logs into the SNS server 10, displays the address book of the representative on the screen, and causes the representative to select a companion player from the list. For example, when three representatives are selected by the representative, the SNS server 10 refers to the profile management DB 151 (FIG. 5), and the member IDs of a total of four members of the representative and the accompanying athletes and The name is specified, and the specified information is transmitted to the smartphone 50. In addition to the member ID and name, face photo image data may be acquired as representative and companion athlete information.

  Next, the smartphone 50 performs a play information recording table creation process (step S104). Here, for example, a play information recording table TBL1 shown in FIG. 10 is created using the information obtained in steps S101 to S103. As shown in the figure, in the play information recording table TBL1, play information (play date and score) of each member who plays golf together is recorded in association with the golf course name, golf course ID, member ID and name. The FIG. 10 illustrates the play information recording table TBL1 in which score item data is already recorded. However, at the stage where the play information recording table TBL1 is created in step S104, the score item data is Not registered. Further, in the play information recording table TBL1 shown in FIG. 10, the items “golf course name” and “name” may be omitted. For example, even if the “golf course name” is not stored in the play information recording table TBL1, if the “golf course ID” is stored in the SNS server 10 to which the play information recording table TBL1 is uploaded, the golf course management DB 152 The corresponding “golf course name” can be acquired with reference to FIG. Similarly, if “member ID” is stored even if “name” is not stored in the play information recording table TBL1, the SNS server 10 refers to the profile management DB 151 and acquires the corresponding “name”. be able to.

  The round pre-processing described above can be performed not only on the play date but also on the day before the play date. The place where the round pre-processing is executed is not limited to the golf course G. For example, the round pre-processing may be performed at home or in a car facing the golf course G. Moreover, it is not necessary that all members who play golf together are members of the SNS server 10.

  When golf play is started after the round pretreatment, the representative goes around the course with the smartphone 50 and inputs the scores of himself and each accompanying competitor to the smartphone 50 for each hole. The input score is recorded in the play information recording table TBL1. Moreover, a representative will upload the play information of each member recorded on play information recording table TBL1 to the SNS server 10 by operating the smart phone 50, after finishing the play of golf. At the time of uploading, for example, data of each item excluding the golf course name and name in the play information recording table TBL1 shown in FIG. 10 is transmitted. In addition, in the case of the play information recording table TBL1 shown in FIG. 10, the uploaded data are members who played golf together with the four members recorded in the play information recording table TBL1. Accompanied round information is given.

  CPU110 of SNS server 10 will register the received data in play information management DB153 (FIG. 7), if the data uploaded from the smart phone 50 are received via communication IF140. At this time, if accompanying data is attached to the uploaded data, the CPU 110 issues a round ID, and registers the issued round ID in the play information management DB 153 in association with the received play information of each member. To do. For example, when data recorded in the play information recording table TBL1 shown in FIG. 10 is uploaded, data is registered in the play information management DB 153 as shown by record numbers “1” to “4” in FIG. .

  Note that the play information may be uploaded sequentially at the end of one hole, instead of being collectively uploaded after the round. The round ID can also be issued by the smartphone 50. In this case, for example, the smartphone 50 generates a round ID by combining a terminal ID unique to each smartphone 50 such as a telephone number and an email address and a time stamp, and the generated round ID is uploaded to the SNS server together with data to be uploaded. 10 to send.

  For example, all four members who play golf together carry the smart phone 50, respectively, and the mode which inputs only own play information into the own smart phone 50 and uploads to the SNS server 10 can be considered. In this case, if each member has set the golf course G, the play date, and the information of the companion player in the round pre-processing described above, the SNS server 10 has four members who each have their own play information at different timings. Even if only uploading from their smartphone 50, the same round ID is given to the play information of these four members on the basis of the golf course G, the play date, and the information of the accompanying competitors. It can be registered in the play information management DB 153.

FIG. 11 is a sequence chart illustrating the flow of browsing processing.
The member can log in to the SNS server 10 by operating the smartphone 50, and can view the score of himself or his / her competing player on his / her own page. For example, when the member operates the smartphone 50 to shift to the score browsing page for browsing the golf score in the My Page, the smartphone 50 transmits a browsing request including the member ID of the member to the SNS server 10 (step S201). ). For example, when a member assigned with “M00000001” as a member ID operates the smartphone 50 to shift to the score browsing page, the smartphone 50 transmits a browsing request including the member ID “M00000001” to the SNS server 10.

  When receiving the browsing request from the smartphone 50, the CPU 110 of the SNS server 10 searches the play information management DB 153 (FIG. 7) using the member ID included in the received browsing request as a search key, and identifies one or more corresponding record data. (Step S202). What is specified here is the record data of the member who requested browsing. For example, if the received browsing request includes the member ID “M00000001”, the CPU 110 searches the play information management DB 153 shown in FIG. 7 using the member ID “M00000001” as a search key, and the record number is “1”. Specify record data.

  Next, CPU110 specifies the other record data which has round ID contained in record data for every specified record data (step S203). What is specified here is the record data of the accompanying competitor. For example, when the record data identified in step S202 described above is the record number “1” of the play information management DB 153 shown in FIG. 7, the round ID included in this record data is “R00000001”. Therefore, the CPU 110 specifies three record data with record numbers “2” to “4” from the play information management DB 153 (FIG. 7) as other record data having the round ID “R00000001”. When there are a plurality of record data specified in step S202, the record data of the accompanying player is specified for each specified record data.

  Next, the CPU 110 acquires browsing data (step S204). For example, CPU110 acquires item data other than member ID among each record data specified by step S202, S203 as browsing data. In addition, the CPU 110 acquires, from the profile management DB 151 (FIG. 5), as browsing data, the name and face photo image data of the member who requested browsing and their accompanying competitors. Thereafter, the CPU 110 returns the browsing data acquired in step S204 to the smartphone 50 (step S205).

  When receiving the browsing data from the SNS server 10, the smartphone 50 displays on the screen a score list of the member who requested browsing and the accompanying competitors based on the received browsing data (step S206). The browsing data includes the golf course ID instead of the golf course name. As described above, the golf navigation application 51 has a database that records the correspondence between the golf course ID and the golf course name. Therefore, in the smart phone 50, the golf course name corresponding to the golf course ID can be specified by referring to this database. Of course, the SNS server 10 can also include the golf course name in the browsing data instead of the golf course ID and transmit it to the smartphone 50. In this case, the SNS server 10 may acquire the golf course name corresponding to the golf course ID from the golf course management DB 152 (FIG. 6). In addition, the round ID is included in the browsing data. When there are a plurality of scores of members who requested browsing, the round ID is used to specify the accompanying competitor and the score for each score. Used.

FIG. 12 is a diagram illustrating a screen display example of the smartphone 50.
As shown in the figure, the member can browse the history of the scores of himself and his companion players on his / her score browsing page. The score list also displays golf course name and play date information. In the figure, “AP” is an against stopper. In the figure, the underline indicates a link. For example, when the “A country club” part is touch-operated in the same figure, the score list of “Taro Suzuki” for only “A country club” can be displayed. In addition, when the item data “E” of the AP of “Ichiro Sato” is touch-operated in the same figure, the score for each hole (18 holes) can be displayed for “Ichiro Sato”. In addition, when the “Hanako Takahashi” portion is touch-operated in the same figure, the score browsing page of “Hanako Takahashi” is displayed, and the score list of “Hanako Takahashi” can be browsed.

  As described above, the SNS server 10 can view not only the player's own score but also the score of the accompanying player. Moreover, in the SNS server 10, it is also possible to browse the scores of members other than the accompanying competitors. However, the member can arbitrarily set who can view his / her score and who can permit viewing (disclosure range of his / her score). For example, a member sets his / her score release range to “all members of SNS server 10”, “members who played golf together”, “members registered as friends in the address book”, “golf to address book” “Members registered as friends” or “Only me (private)” can be set. In addition, when the browsing of the score is permitted, the golf course name and the play date information are also disclosed together with the score. Also, you can set the disclosure range and non-disclosure for each score, “Do not disclose companion competitor's personal information and score”, “Do not disclose play date information”, “Play golf together as companion competitors” It is also possible to make a setting such as “allowing others to view their score list while allowing their own scores etc. to be disclosed to the score list of the member who has been selected”.

  For example, “Hanako Takahashi” has the scope of public disclosure of his score “Although his / her own score list is permitted to be disclosed to the list of scores of members who played golf together as companion players, Is set to “prohibit browsing”, the score list of “Hanako Takahashi” is not displayed even if the portion of “Hanako Takahashi” in FIG. 12 is touched, and browsing is prohibited. Message is displayed. In the above browsing process, the case where the player's score is displayed together with the accompanying player's score has been described, but a list of only the player's score can also be displayed.

FIG. 13 is a sequence chart illustrating the flow of play information transmission processing.
The SNS server 10 has a function of transmitting the member's play information (score and play date) registered in the play information management DB 153 (FIG. 7) to the corresponding golf course server 20. Note that transmits to the golf course server 20 corresponding play information, for example, if the play information obtained as a result of playing golf in golf G ₁ is transmitted to the golf course server 20 _1, golf courses G ₂ if the play information obtained as a result of playing golf is meant to send to the golf course server 20 _2.

  For example, as shown in FIG. 14A, when the score list is displayed on the screen of the smartphone 50, the play information is not yet transmitted to the golf course server 20 on the right side of the own score. The display button BN1 instructing to transmit play information to the golf course server 20 is displayed. When the member transmits play information to the golf course server 20, the member touches the display button BN1. When the play information has already been transmitted, a display button BN2 indicating that the play information has been transmitted is displayed as shown in FIG.

  When detecting that the display button BN1 is touched, the smartphone 50 transmits a transmission request including play information designation data for designating play information to be transmitted to the SNS server 10 (step S301). In addition, play information designation | designated data may be comprised by member ID, a play date, for example, may be comprised by member ID, a play date, and a score, and is member ID, golf course ID, a play date, and a score. It may be configured. Further, the play information designation data may be information for designating a record number in the play information management DB 153.

  When receiving the transmission request from the smartphone 50, the CPU 110 of the SNS server 10 refers to the play information management DB 153 (FIG. 7) and is included in the same record as the play information specified by the play information specifying data included in the received transmission request. Member ID and golf course ID to be identified (step S302). For example, when the play information designated by the play information designation data is play information included in the record number “1” in FIG. 7, the CPU 110 specifies the member ID “M00000001” and the golf course ID “G00001”. Next, the CPU 110 refers to the golf course management DB 152 (FIG. 6), and identifies the access method (URL and API) corresponding to the golf course ID identified in step S302 (step S303). For example, when the golf course ID specified in step S302 is “G00001”, the CPU 110 specifies the access method to the golf course server 20 of “A country club”.

  Thereafter, the CPU 110 determines whether or not the user ID has been acquired (step S304). Here, the user ID is registered by referring to the user ID registration DB 154 and checking whether or not the user ID is registered in association with the set of the member ID and the golf course ID specified in step S302. Then, it is determined that the user ID has been acquired (step S304: YES), and if the user ID is not registered, it is determined that the user ID has not been acquired (step S304: NO). For example, when the member ID “M00000001” and the golf course ID “G00001” are specified in step S302, the user ID registration DB 154 shown in FIG. 8 includes the set of the member ID “M00000001” and the golf course ID “G00001”. Since the user ID “001612” is registered in association with (record number “1”), it is determined in step S304 that the user ID has been acquired.

  If the determination result of step S304 is YES, the CPU 110 proceeds to step S308. On the other hand, if the determination result in step S304 is NO, the CPU 110 refers to the profile management DB 151 (FIG. 5) and acquires part or all of the profile information corresponding to the member ID specified in step S302 (step S305). . For example, if the member ID identified in step S302 is “M00000001”, the CPU 110 obtains “Taro Suzuki (name)”, “1969/05/23” as profile information from the profile management DB 151 shown in FIG. Birth date) ”or“ 090-1111-1111 (phone number) ”.

  Next, CPU110 performs profile matching with the golf course server 20 used as the transmission destination of play information (step S306). First, the CPU 110 accesses the golf course server 20 indicated by the URL specified in step S303. Moreover, CPU110 communicates with the golf course server 20 using API specified by step S303. And CPU110 notifies the golf course server 20 of the profile information acquired by step S305, and inquires the user ID which corresponds to the notified profile information. In addition, when there are few types of API required in order to communicate with all the golf course servers 20, it does not register each API in golf course management DB152 (FIG. 6), but control for SNS server 10. Each API may be incorporated as a subroutine or module in the program.

When the golf course server 20 receives the profile information from the SNS server 10, the golf course server 20 refers to the user management DB 21 (FIG. 2) and identifies a user ID that matches the received profile information (personal information). Moreover, the golf course server 20 returns the identified user ID to the SNS server 10. For example, when the golf course server 20 (for example, the golf course server 20 ₁ ) whose golf course ID is “G00001”, which is the transmission destination of play information, is profile information received from the SNS server 10, “Taro Suzuki” Figure 2 shows the user management DB 21 ₁ reference to obtains the user ID "001 612" matching "Taro Suzuki", and returns it to the SNS server 10. This SNS server 10, it is possible to get the member user ID golf server 20 ₁ has been assigned to (Taro Suzuki) "001612" of the member ID "M00000001".

  As personal information used for profile matching, for example, any one of a name, a home address, a mail address, a phone number of the smartphone 50 owned, and a home phone number can be used alone. However, in the case of a full name, there may be a person with the same surname and the same name. In the case of a home address or a home phone number, there may be a plurality of users of the same golf course G in the family. For this reason, when any one of the name, the home address, and the home phone number is used alone, the user ID may not be narrowed down to one by profile matching. Therefore, when using any one of the profile information (personal information) alone, it is preferable to use the e-mail address or the phone number of the smartphone 50 in order to increase the matching accuracy.

  However, also in this case, in the golf course server 20, the user management DB 21 has not been updated for a long time, and the e-mail address and the phone number of the smartphone 50 may not be registered as the user's personal information. is there. For this reason, when the mail address or the phone number of the smartphone 50 is used alone, the user ID may not be specified by profile matching. From the above, for example, if the user ID cannot be specified by profile matching using an email address or phone number of the smartphone 50, profile matching is performed using the name, home address, or home phone number. Also good. In addition, if profile matching by name, home address, or home phone number cannot be narrowed down to one, further combine information such as gender, age, date of birth, occupation, work, etc. Profile matching may be performed. In this way, profile matching is performed by appropriately combining two or more of name, home address, e-mail address, phone number of own smartphone 50, home phone number, gender, age, date of birth, occupation, workplace, etc. By doing so, the matching accuracy can be increased. Note that the user himself / herself may arbitrarily set a combination of user personal information used in profile matching.

  Next, the CPU 110 registers the user ID specified by profile matching in the user ID registration DB 154 in association with the set of the member ID and golf course ID specified in step S302 (step S307). For example, when the user ID specified by profile matching is “001612” and the member ID “M00000001” and the golf course ID “G00001” are specified in step S302, the CPU 110 changes the user ID “001612” to the member. It is registered in the user ID registration DB 154 in association with the set of ID “M00000001” and golf course ID “G00001” (record number “1” in FIG. 8).

  If the determination result in step S304 is YES, the CPU 110 refers to the user ID registration DB 154, and determines the user ID registered in association with the set of the member ID and golf course ID specified in step S302. Acquire (step S308) and proceed to step S309. Here, for the golf course server 20 in which the member has transmitted play information even once in the past, the determination result in step S304 is YES, and the processing from step S305 to S307 including profile matching is not executed. In both cases, the user ID can be acquired from the user ID registration DB 154. Therefore, the play information transmission process can be simplified and the processing time can be shortened.

  Thereafter, when the determination result in step S304 is NO, the CPU 110 determines the user ID specified by the profile matching performed in step S306 and the play information (score and play date) specified by the play information specifying data. Is transmitted to the golf course server 20 via the communication IF 140, and if the determination result in step S304 is YES, the user ID acquired from the user ID registration DB 154 in step S308 and the play specified by the play information specifying data Information is transmitted to the golf course server 20 (step S309). In step S309, the SNS server 10 may not transmit the user ID and the play information to the golf course server 20 simultaneously (together). For example, the SNS server 10 may transmit play information first, and when there is an inquiry about the user from the golf course server 20, the user ID may be transmitted in response to the inquiry.

When the golf course server 20 receives the user ID and the play information from the SNS server 10, the golf course server 20 associates the received user ID and the play information with each other and registers them in the play information management DB 22 (FIG. 3) (step S310). For example, the play information included in the record data with the record number “1” in the play information management DB 153 shown in FIG. 7 from the smartphone 50 to the SNS server 10, that is, the play information of the member with the member ID “M00000001”. When transmission of (score “71” and play date “20011/10/09”) is instructed, this play information and the user ID “001612” acquired by profile matching are the golf course ID “G00001”. sent to the golf course server 20 _1, it is registered in the play information management DB 22 ₁ shown in FIG.

Here, as will be apparent when referring to the profile management DB 151 (FIG. 5) and the user management DB 21 (FIG. 2), both the member ID “M00000001” and the user ID “001612” correspond to “Taro Suzuki”. Is granted. Therefore, it is possible to register the play information of the SNS server 10 "Taro Suzuki" and are managed by, the play information management DB22 ₁ as the play information of the golf course server 20 ₁ even "Taro Suzuki". In addition, according to the use reservation of the golf course G and the user having completed reception at the front of the golf course G on the day of the play date, the user ID and the play date excluding the score are already registered in the play information management DB 22 If it is, only the item data of the unregistered score is registered.

  Thereafter, the golf course server 20 transmits a completion notification indicating that the registration of the play information has been completed to the SNS server 10 (step S311). Upon receiving the completion notification from the golf course server 20, the SNS server 10 transmits a completion notification indicating that the play information transmission process has been completed to the smartphone 50 (step S312).

  The profile matching can be performed at an arbitrary timing as a process separate from the play information transmission process described above. In this case, for example, as shown in FIG. 15 (A), when the score list is displayed on the screen of the smartphone 50, it is used from the golf course server 20 that is the transmission destination of the play information on the right side of the own score. When the user ID is not acquired, a display button BN3 for instructing execution of profile matching is displayed. When performing profile matching, the member touches the display button BN3. When the user ID has already been acquired from the golf course server 20 that is the transmission destination of the play information, a display button BN4 indicating that matching has been completed is displayed as shown in FIG.

  Further, the profile matching and the process of transmitting play information to the golf course server 20 are basically processes performed for each member. For example, the member A performs profile matching of the member B, or the member A It is basically prohibited for the member to instruct the transmission of member B's play information. However, it may be configured to permit the transmission of play information of other members without prohibiting it. In this case, for example, if all the members who played golf together have already completed profile matching, the representative of the member can collectively transmit the play information of all the members. For example, as shown in FIG. 15C, when the score list is displayed on the screen of the smartphone 50, if all the members who played golf together have already completed the profile matching, the right of the scores of all the members Aside from this, a display button BN5 for instructing transmission of play information of all members to the golf course server is displayed. The member representative touches the display button BN5 when transmitting the play information of all members to the golf course server 20.

  In addition, you may provide the setting which prohibits the transmission of one's own play information from another member being instructed. In this case, when the member representative touches the display button BN5, only the play information of the member who does not enable the prohibition setting is transmitted to the golf course server 20, and the play information of the member who enables the prohibition setting The transmission to the golf course server 20 is cancelled. Further, after finishing the play information transmission process, for example, a message such as “Member A could not transmit play information to the golf course server 20 due to the transmission prohibition setting” is displayed.

FIG. 16 is a sequence chart illustrating the flow of the play information acquisition process.
The SNS server 10 has a function of acquiring past play information of members from the golf course server 20. In the following description of the operation, the description of the portion that performs the same process as the play information transmission process shown in FIG. 13 is simplified as appropriate.

  For example, when the member operates the smartphone 50 and selects a golf course G from which to acquire his / her play information from the golf course list, the smartphone 50 records a correspondence relationship between the golf course name and the golf course ID. The golf course ID corresponding to the golf course G selected by the member is specified. In addition, the smartphone 50 transmits an acquisition request including the member ID of the member and the identified golf course ID to the SNS server 10 (step S401). For example, when a member with “M00000001” as the member ID instructs to acquire his / her play information from the golf course server 20 of “A country club”, the smartphone 50 has the member ID “M00000001” and the golf course ID. An acquisition request including “G00001” is transmitted to the SNS server 10.

  When the CPU 110 of the SNS server 10 receives the acquisition request from the smartphone 50, the CPU 110 refers to the golf course management DB 152 (FIG. 6) and specifies the access method (URL and API) corresponding to the golf course ID included in the received acquisition request. (Step S402). For example, when the golf course ID included in the acquisition request is “G00001”, the CPU 110 specifies an access method to the golf course server 20 of “A country club”.

  Next, the CPU 110 determines whether or not a user ID has been acquired (step S403). Here, referring to the user ID registration DB 154 (FIG. 8), it is checked whether or not the user ID is registered in association with the set of the member ID and the golf course ID included in the acquisition request received in step S401. If the user ID is registered, it is determined that the user ID has been acquired (step S403: YES), and if the user ID is not registered, it is determined that the user ID has not been acquired (step S403). S403: NO). For example, when the member ID “M00000001” and the golf course ID “G00001” are included in the acquisition request, the user ID registration DB 154 shown in FIG. 8 includes the member ID “M00000001” and the golf course ID “G00001”. Since the user ID “001612” is registered in association with the group (record number “1”), it is determined in step S403 that the user ID has been acquired.

  If the determination result in step S403 is YES, the CPU 110 proceeds to step S407. On the other hand, if the determination result in step S403 is NO, the CPU 110 refers to the profile management DB 151 (FIG. 5) and acquires part or all of the profile information corresponding to the member ID included in the acquisition request received in step S401. (Step S404). For example, if the member ID included in the acquisition request is “M00000001”, the CPU 110 obtains “Taro Suzuki (name)”, “1969/05/05” as profile information from the profile management DB 151 shown in FIG. Acquire one or more of “23 (date of birth)” and “090-1111-1111 (phone number)”.

  Next, CPU110 performs profile matching between the golf course servers 20 used as the acquisition destination of play information (step S405). First, the CPU 110 accesses the golf course server 20 indicated by the URL specified in step S402. Moreover, CPU110 communicates with the golf course server 20 using API specified by step S402. And CPU110 notifies the golf course server 20 of the profile information acquired by step S404, and inquires the user ID which corresponds to the notified profile information.

When the golf course server 20 receives the profile information from the SNS server 10, the golf course server 20 refers to the user management DB 21 (FIG. 2) and identifies a user ID that matches the received profile information (personal information). Moreover, the golf course server 20 returns the identified user ID to the SNS server 10. For example, when the golf course server 20 (for example, the golf course server 20 ₁ ) whose golf course ID is “G00001”, which is the acquisition destination of play information, is profile information received from the SNS server 10, “Taro Suzuki” Figure 2 shows the user management DB 21 ₁ reference to obtains the user ID "001 612" matching "Taro Suzuki", and returns it to the SNS server 10. This SNS server 10, it is possible to get the member user ID golf server 20 ₁ has been assigned to (Taro Suzuki) "001612" of the member ID "M00000001". The personal information used in profile matching is as described in the play information transmission process described above.

  Next, the CPU 110 registers the user ID specified by profile matching in the user ID registration DB 154 in association with the set of member ID and golf course ID included in the acquisition request received in step S401 (step S406). For example, when the user ID specified by profile matching is “001612” and the member ID “M00000001” and the golf course ID “G00001” are included in the acquisition request, the CPU 110 uses the user ID “001612”. The member ID “M00000001” and the golf course ID “G00001” are registered in association with the user ID registration DB 154 (record number “1” in FIG. 8).

  If the determination result in step S403 is YES, the CPU 110 refers to the user ID registration DB 154 and is registered in association with the set of member ID and golf course ID included in the acquisition request received in step S401. A user ID is acquired (step S407). Here, for the golf course server 20 in which the member has transmitted or acquired play information even once in the past, the determination result in step S403 is YES, and the processing from step S404 to S406 including profile matching is executed. Without it, the user ID can be acquired from the user ID registration DB 154. Therefore, the play information acquisition process can be simplified and the processing time can be shortened.

  Thereafter, when the determination result of step S403 is NO, the CPU 110 transmits an acquisition request including the user ID specified by the profile matching performed in step S405 to the golf course server 20 via the communication IF 140, and the step If the determination result in S403 is YES, an acquisition request including the user ID acquired from the user ID registration DB 154 in step S407 is transmitted to the golf course server 20 (step S408).

When the golf course server 20 receives the acquisition request from the SNS server 10, the golf course server 20 refers to the play information management DB 22 (FIG. 3) and specifies one or more play information corresponding to the user ID included in the received acquisition request ( Step S409). For example, in the golf course server 20 (for example, the golf course server 20 ₁ ) whose golf course ID is “G00001”, which is the acquisition destination of the play information, the user ID included in the acquisition request received from the SNS server 10 is “ "If the was the play information management DB 22 ₁ referring to the user ID of that shown in FIG. 3" 001,612 identify the "play information corresponding to the (score" 001612 NULL "and play date" 20011/10/09 ") To do.

Next, the golf course server 20 returns the play information specified in step S409 to the SNS server 10 (step S410). When the CPU 110 of the SNS server 10 receives the play information from the golf course server 20, the play information management DB 153 (FIG. 7) associates the received play information with the member ID and the golf course ID included in the acquisition request received in step S401. (Step S411). Then, CPU110 transmits the completion notification which shows that the acquisition process of play information was completed to the smart phone 50 (step S412). For example, the play information received from the golf course server 20 ₁ is a score "NULL" and the play date "20011/10/09", contains the member ID "M00000001" and the golf course ID "G00001" to the acquisition request In such a case, the SNS server 10 registers the play information (score “NULL” and play date “20011/10/09”) in the play information management DB 153 in association with the member ID “M00000001” and the golf course ID “G00001”. .

  The play information acquired from the golf course server 20 may have an unregistered score, but even in that case, since the play date information can be acquired, the member personally manages his / her past score. If it is, it is possible to operate the smartphone 50 to access the SNS server 10 and input an unregistered score. In addition, when the CPU 110 of the SNS server 10 receives play information from the golf course server 20 in step S410, especially when there is a plurality of play information, reception of play information already registered in the play information management DB 153 is refrained. Only the play information that is not registered in the play information management DB 153 may be received. In this case, the SNS server 10 does not need to receive useless play information.

  According to the play information acquisition process described above, for example, the play information of “Taro Suzuki” is acquired from the golf course server 20, and this is registered in the play information management DB 153 as play information of “Taro Suzuki” even in the SNS server 10. can do. In addition, since the member can acquire his / her past play information from each golf course server 20 and register it in the play information management DB 153 of the SNS server 10 as necessary, he / she plays golf at golf courses G in various places. The SNS server 10 can centrally manage the play information of the selected members.

  Note that the profile matching performed in step S405 can also be performed at an arbitrary timing as a process separate from the play information acquisition process. Further, the process of acquiring play information from the golf course server 20 is also a process that is basically performed for each member. For example, it is basically prohibited for the member A to instruct the acquisition of the play information of the member B. Yes. However, it may be configured not to prohibit other members from instructing to acquire play information, or a setting may be provided to prohibit other members from instructing to acquire their own play information. Good.

<2. Modification>
The present invention is not limited to the above-described embodiment, and for example, the following modifications are possible. Also, two or more of the following modifications can be combined as appropriate.

[Modification 1]
When profile matching (step S306) is performed in the transmission process shown in FIG. 13, information on play dates may be used in addition to personal information. As described above, in the play information management DB 22 of the golf course server 20, the user ID and the play date other than the score are often registered according to the use reservation of the golf course G or the like. Therefore, in addition to the personal information, profile matching is performed by using the play date information included in the play information to be transmitted or the past play date information remembered by the member, thereby improving the matching accuracy. it can.

  In this case, when starting the profile matching in step S306, the SNS server 10 operates the smartphone 50 by the information on the play date specified by the play information specifying data or the member in addition to the profile information acquired in step S305. The golf course server 20 is notified of the past play date information entered in the above. When the golf course server 20 receives the profile information and the play date information from the SNS server 10, for example, even if referring to the user management DB 21 (FIG. 2), the user ID that matches the received profile information is one. If the user ID cannot be narrowed down, the play information management DB 22 (FIG. 3) is referred to, and the user ID that matches the received play date information is specified. Next, the golf course server 20 specifies a user ID by taking an AND of a plurality of user IDs matching the profile information and one or more user IDs matching the play date information. The person ID is transmitted to the SNS server 10.

  Note that the play date information used in the profile matching is not limited to one but may be plural. The use of multiple pieces of play date information can further improve the accuracy of matching. Also, in the case where profile matching (step S405) is performed in the acquisition process shown in FIG. 16, in addition to personal information, play date information may be used.

[Modification 2]
FIG. 17 is a sequence chart showing a modification of the transmission process shown in FIG.
The process shown in the figure is started when the user ID matching the profile information (personal information) received by the golf course server 20 from the smartphone 50 is specified by profile matching (step S306 in FIG. 13).

  First, the golf course server 20 determines whether or not there are a plurality of user IDs specified by profile matching (step S501). If the determination result of step S501 is NO, the process proceeds to step S307 shown in FIG. In addition, when the determination result of step S501 is YES, that is, when the user ID cannot be narrowed down to one by profile matching, the golf course server 20 is identified with reference to the user management DB 21 (FIG. 2). Personal information (for example, name, date of birth, address, telephone number) corresponding to each of the plurality of user IDs is acquired (step S502). Next, the golf course server 20 generates a set of a user ID and personal information corresponding to the user ID for each identified user ID. Moreover, the golf course server 20 transmits the set (plurality) of the generated user ID and personal information to the SNS server 10 (step S503).

  When the SNS server 10 receives the set (plurality) of the user ID and the personal information from the golf course server 20, the SNS server 10 stores this in the RAM 130 and transmits the received personal information for the plurality of persons to the smartphone 50 (step S504). ). When the smartphone 50 receives the personal information (for a plurality of people) from the SNS server 10, the smartphone 50 displays the received personal information for the plurality of people on the screen (step S505). In addition, the smartphone 50 displays a message such as “The user ID could not be narrowed down to one by matching. Please select because there are multiple candidates.” And prompt the member to select. . In response to this, when the member operates the smartphone 50 and selects one of the personal information for a plurality of persons displayed on the screen, the smartphone 50 displays the selection information for specifying the personal information selected by the member on the SNS server. 10 (step S506). When the SNS server 10 receives the selection information from the smartphone 50, the SNS server 10 identifies the same set of user IDs as the personal information specified by the received selection information from the information stored in the RAM 130, and sets the identified user ID as a profile. The final user ID obtained by matching is determined (step S507).

  As described above, when the user ID cannot be narrowed down to one by profile matching, the user may make a final selection. Note that the contents of this modification can be similarly applied to profile matching (step S405) performed in the acquisition process illustrated in FIG.

[Modification 3]
In the play information transmission process (FIG. 13) described above, the user ID specified by profile matching is registered in the user ID registration DB 154 (FIG. 8) in association with the set of member ID and golf course ID specified in step S302. (Step S307), steps S304, S307, and S308 are deleted, and the user ID registration DB 154 (FIG. 8) is not provided, and the SNS server 10 is instructed whenever play information transmission is instructed. Profile matching may be performed. The same applies to the play information acquisition process (FIG. 16). That is, steps S403, S406, and S407 are deleted and the user ID registration DB 154 (FIG. 8) is not provided, and the SNS server 10 performs profile matching every time play information acquisition is instructed. Good.

[Modification 4]
The play information managed by the SNS server 10 and each golf course server 20 may include handicap, weather, wind speed, information on members who have rounded together, etc. in addition to the play date and score. Further, the play information may include only the score without including the play date. In addition, the score may include information such as the number of putts per hole, the average number of putts in all holes, and the ranking among members who have rounded together. The play information managed by the SNS server 10 and the play information managed by each golf course server 20 may have different data configurations. For example, while the play information managed by the SNS server 10 is configured by the play date, the score, and the weather, the play information managed by each golf course server 20 may be configured by the play date and the score. . In this case, when the play information is transmitted from the SNS server 10 to the golf course server 20, the play date and the score excluding the weather are transmitted from the SNS server 10. Further, when the play information is acquired from the golf course server 20, the play date and the score are acquired from the golf course server 20, and the item of weather is “NULL”. Further, for example, the data recording format of the play information may be different between the SNS server 10 and each golf course server 20, such as a plain text format and a rich text format. In this case, the SNS server 10 may have a function of converting the data recording format.

[Modification 5]
The user management DB 21 may be provided with at least one item of, for example, name, date of birth, address, telephone number, and mail address as personal information of the user. Similarly, in the profile management DB 151, for example, at least one item of name, date of birth, address, telephone number, and mail address may be provided as member profile information. However, since profile matching is performed, at least one item needs to be the same in the personal information stored in the user management DB 21 and the profile information stored in the profile management DB 151.

[Modification 6]
The profile management DB 151 may be stored in a member management server provided separately from the SNS server. In this case, the SNS server 10 makes an inquiry to the member management server and acquires profile information of the members to be profile-matched. Moreover, the item of round ID may not be in play information management DB153.

[Modification 7]
The profile management DB 151, the golf course management DB 152, the play information management DB 153, and the user ID registration DB 154 may be stored in a device (for example, an information storage server) different from the SNS server 10. In this case, the SNS server 10 accesses the information storage server as necessary, and acquires information or stores new information. Similarly, the user management DB 21 and the play information management DB 22 are also stored in a device (for example, an information storage server) different from the golf course server 20, and the golf course server 20 accesses the information storage server as necessary, The configuration may be such that information is acquired or new information is accumulated. Moreover, the golf course server 20 may be comprised by the user management server which memorize | stores user management DB21, and the play information management server which memorize | stores play information management DB22.

[Modification 8]
The terminal is not limited to a smartphone, and may be, for example, a mobile phone having a web browsing function, a tablet computer having a wireless communication function, a dedicated terminal for GPS golf navigation, or the like. The terminal may not have a golf navigation function using GPS. In addition, since the terminal only needs to be able to browse the play information managed by the SNS server 10 and to instruct the SNS server 10 to transmit and acquire play information, the terminal is not limited to a portable communication device. It may be a stationary personal computer or the like.

[Modification 9]
In addition to the golf course, the sports facility may be a golf bar in which one or a plurality of virtual golf machines are installed, for example. In this case, the date when the virtual golf was played at the golf bar and its score are managed as play information. The present invention can also be applied to sports other than golf, and sports facilities are, for example, a bowling alley, a tennis court, a sports gym, a swimming club, an athletic stadium, etc. in addition to a golf course and a golf bar. Also good. For example, in the case of a bowling alley, the date when the bowling is played at the bowling alley and its score are managed as play information. In addition, the sports play result managed as the play information may be winning / losing, ranking, time, etc. in addition to the score.

[Modification 10]
The server according to the present invention is not limited to an SNS server. In other words, the server is not limited to a membership system server or a server whose main service is a social network service, and manages play information of sports facility users by communicating with one or more sports facility management devices. Any server can be used. The network interposed between the server and the terminal is not limited to the Internet or a mobile communication network, but may be a WAN (Wide Area Network), a LAN (Local Area Network), or the like.

1 ... management system, 10 ... SNS _{server, G,} G 1 ~G m _... golf course, 20,20 ₁ ~20 m _... golf server, 21,21 ₁ ~21 m _... user management DB, 22,22 ₁ -22 _m ... Play information management DB, 30 ... Internet, 40 ... Mobile communication network, 50, 50 ₁ to 50 _n ... Smartphone, 51 ... Golf navigation application, 110 ... CPU, 120 ... ROM, 130 ... RAM, 140 ... Communication IF, 150 ... Hard disk, 151 ... Profile management DB, 152 ... Golf course management DB, 153 ... Play information management DB, 154 ... User ID registration DB, TBL1 ... Play information record table, BN1-BN5 ... Display buttons.

Claims (10)

A server that manages play information including a play result of a user who has played sports at a sports facility and date information indicating a date of play, and provides the play information to a terminal operated by the user,
A management unit for managing the play information of the user and the facility information indicating the sports facility played by the user in association with the first user identification information for identifying the user;
Among the information managed by the management unit, a specifying unit that specifies first user identification information and facility information associated with play information designated from the terminal,
A first acquisition unit that acquires personal information of the user specified by the first user identification information specified by the specification unit;
Accesses the management apparatus for managing the play information and personal information of each user in sports facilities facility information the identifying unit has identified indicates association with the second user identification information for identifying the user, the The second user identification information that matches the personal information acquired by the first acquisition unit and the date information included in the designated play information or the date / time information indicating the play date input from the terminal is acquired. A second acquisition unit to perform,
A transmission unit for transmitting the designated play information and the second user identification information acquired by the second acquisition unit to the management device;
A server comprising: The management unit manages the second user identification information acquired by the second acquisition unit in association with the first user identification information and facility information specified by the specifying unit,
The second acquisition unit includes
When the second user identification information is managed by the management unit in association with the first user identification information and facility information specified by the specification unit, the second user identification information is stored in the management unit. Get from
When the second user identification information is not managed by the management unit in association with the first user identification information and facility information specified by the specification unit, the management device is accessed, and the first acquisition unit The second user identification information that matches the personal information acquired by the user and the date information included in the designated play information or the date / time information indicating the play date input from the terminal is acquired. The server according to claim 1. When the first user identification information and the facility information are specified from the terminal, the first acquisition unit acquires the personal information of the user specified by the specified first user identification information,
The second acquisition unit accesses the management device corresponding to the designated facility information, and second user identification information that matches the personal information acquired by the first acquisition unit, and the second use And the play information associated with the user identification information,
The server according to claim 1, wherein the management unit manages the play information acquired by the second acquisition unit in association with the designated first user identification information and facility information. The management unit manages the second user identification information acquired by the second acquisition unit in association with the designated first user identification information and facility information,
The second acquisition unit includes
When the second user identification information is managed in the management unit in association with the designated first user identification information and facility information, the play associated with the second user identification information Obtaining information from the management device;
When the second user identification information is not managed in the management unit in association with the designated first user identification information and facility information, the management device is accessed and the first acquisition unit acquires 4. The server according to claim 3 , wherein second server identification information that matches the personal information and play information associated with the second user identification information are acquired. The said 2nd acquisition part acquires the play information which the said management part does not manage among the play information linked | related with the said 2nd user identification information. The Claim 3 or 4 characterized by the above-mentioned. Server. When browsing of play information is requested from the terminal, a browsing control unit that acquires the play information requested to be browsed and facility information associated with the play information from the management unit and transmits the information to the terminal The server according to any one of claims 1 to 5 , further comprising: The management unit associates and manages the same identification information as accompanying play identification information for each piece of play information of a plurality of users who have played together,
When the accompanying play identification information is associated with the play information requested to be browsed, the browsing control unit acquires a plurality of pieces of play information associated with the accompanying play identification information from the management unit, and The server according to claim 6 , wherein the server is transmitted to a terminal. A receiving unit that receives play information of each of a plurality of users who have played together from the terminal;
The server according to claim 7 , further comprising: an assigning unit that assigns the accompanying play identification information to each of a plurality of pieces of play information received by the receiving unit. A server control method that manages play information including a play result of a user who has played sports in a sports facility and date information indicating a date of play, and provides the play information to a terminal operated by the user. ,
Managing the play information of the user and the facility information indicating the sports facility played by the user in association with the first user identification information for identifying the user;
From the information to be managed, specify the first user identification information and facility information associated with the play information specified from the terminal,
Obtain the personal information of the user specified by the specified first user identification information,
It accesses the management apparatus for managing the play information and personal information of each user in sports facilities indicated by the specified property information in association with the second user identification information for identifying the user, the personal information acquired If, acquires the date information or the second user identification information matches the date and time information indicating a play date inputted from the terminal included in the designated play information,
Transmitting the designated play information and the acquired second user identification information to the management device;
And a server control method. A computer that manages play information including a play result of a user who played sports at a sports facility and date information indicating a date of play, and provides the play information to a terminal operated by the user,
A management unit that manages the play information of the user and the facility information indicating the sports facility played by the user in association with first user identification information for identifying the user;
A specifying unit for specifying first user identification information and facility information associated with play information designated by the terminal from information managed by the management unit;
A first acquisition unit that acquires personal information of the user specified by the first user identification information specified by the specification unit;
Accesses the management apparatus for managing the play information and personal information of each user in sports facilities facility information the identifying unit has identified indicates association with the second user identification information for identifying the user, the The second user identification information that matches the personal information acquired by the first acquisition unit and the date information included in the designated play information or the date / time information indicating the play date input from the terminal is acquired. A second acquisition unit that transmits the specified play information and the second user identification information acquired by the second acquisition unit to the management device;
Program to function as.

Images