JP6939849B2 - Management device and management method - Google Patents

Description

Embodiments of the present invention relate to management devices and management methods.

Conventionally, there is a management device that manages a system in which a plurality of users participate in order to achieve a predetermined purpose. As a system of this kind, for example, there is a system in which a reward is obtained by applying to a local government or the like when a hunter captures a vermin such as a wild boar or a deer that damages crops.

Japanese Unexamined Patent Publication No. 2001-148957

However, in the conventional system, there is room for further improvement in user convenience.

An object of the present invention to be solved is to provide a management device and a management method capable of improving user convenience.

The management device according to the embodiment includes a reception unit, a issuing unit, and a management unit. The reception unit receives subscription information from the user via a predetermined application to each of a plurality of groups having different functions available to the user. The issuing unit issues identification information corresponding to each of a plurality of groups having different functions. The management unit associates the identification information with the subscription information received by the reception unit, and registers and manages the user in each of the plurality of groups.

FIG. 1 is a diagram showing a configuration example of a support system according to an embodiment. FIG. 2 is a block diagram showing a configuration example of the management device according to the embodiment. FIG. 3 is a diagram showing an example of functional information. FIG. 4 is a diagram showing an example of community information. FIG. 5 is a diagram showing an example of group information. FIG. 6 is a diagram showing an example of user information. FIG. 7 is a diagram showing an example of application information. FIG. 8 is a diagram showing a screen provided by the application. FIG. 9 is a diagram showing a process of joining the community. FIG. 10 is a diagram showing a process of joining a group. FIG. 11 is a diagram showing a bounty application process. FIG. 12 is a sequence diagram showing a processing procedure of the community registration process of the support system S according to the embodiment. FIG. 13 is a sequence diagram showing a processing procedure of the group registration process of the support system S according to the embodiment.

The management device 1 according to the embodiment described below includes a reception unit 31 and a management unit 33. The reception unit 31 receives subscription information from the user via a predetermined application to each of a plurality of groups having different functions that can be used by the user. The management unit 33 registers and manages users in each of a plurality of groups based on the subscription information received by the reception unit 31.

The management unit 33 according to the embodiment described below manages a group that can use the application function for making a predetermined application and a group that cannot use the application function as a plurality of groups.

The management unit 33 according to the embodiment described below manages an approval group that can use the approval function that approves the application made by the application function among one group that can use the application function.

The management unit 33 according to the embodiment described below manages a group that cannot use the application function as a group that can use the information sharing function among users belonging to the group.

The management unit 33 according to the embodiment described below manages a plurality of groups having different subscription conditions according to user attributes.

The management unit 33 according to the embodiment described below manages a plurality of groups having different information that can be shared by users belonging to the group.

Hereinafter, the management device and the management method according to the embodiment will be described with reference to the drawings. In the embodiment, the same parts are designated by the same reference numerals, and duplicate description is omitted.

FIG. 1 is a diagram showing a configuration example of a support system according to an embodiment. The support system S shown in FIG. 1 is for supporting the application of a bounty to the local government and the management of information on the bounty in the local government by a hunter (an example of a user) who has captured an animal to be captured such as a vermin. It is a system. In the present embodiment, the support system S for applying for a bounty for a captive animal is given as an example, but the present invention is not limited to this, and any system can be used as long as it is a system in which a plurality of users subscribe for a predetermined purpose. The system can be adopted.

As shown in FIG. 1, the support system S includes a management device 1, a plurality of terminal devices 10, and a local government terminal 100. Further, the management device 1, the terminal device 10, and the local government terminal 100 are communicably connected via a predetermined network N.

The management device 1 is a server that manages information on users (hunters and farmers) who are subscribed to the support system S and information on application for rewards. The management device 1 distributes a predetermined application for using each function of the support system S to the terminal device 10 of each user.

The terminal device 10 is a terminal owned by the user. For example, the terminal device 10 is a portable terminal device such as a smartphone, a tablet, and a digital camera. The terminal device 10 uses each function in the support system S via the application downloaded from the management device 1. The user who handles the terminal device 10 is not limited to a hunter, but may be a farmer, a local government employee, or a user in another industry. That is, the user who can join the support system S is not limited to the user (hunter) who applies for the bounty, but may be the user (farmer or the like) who does not apply for the bounty. In addition, the animals captured by hunters are wild boars, deer, birds, and other vermin that are eligible for boars, but are not limited to these, and are animals that are eligible for capture regardless of the boar. You may.

The local government terminal 100 is a terminal device installed in a local government that approves an application for a bounty and is handled by a local government employee. For example, the local government terminal 100 is a desktop type or notebook type PC (Personal Computer). The local government terminal 100 acquires various information regarding the application for the bounty from the management device 1 and the terminal device 10.

Here, the flow of the bounty application process in the support system S will be described. In the support system S, first, when the hunter captures the vermin, the hunter activates the application of the terminal device 10 and uses the camera function of the application to photograph the whole or a part of the vermin. Subsequently, the hunter transmits the application information in which the imaging date and time, the imaging location, and the like are added to the image as the information for applying for the bounty to the management device 1 via the application. The management device 1 stores the application information received from the hunter's terminal device 10 in association with the hunter's identification information. Further, the management device 1 issues a serial number (for example, the application ID shown in FIG. 7) associated with the application information, stores the serial number in association with the application information, and notifies the terminal device 10 of the serial number. In addition, the hunter submits a part of the captured vermin (for example, tail, etc.) as a voucher to the local government together with the serial number notified from the management device 1. When the local government receives the voucher and the serial number from the hunter, the local government requests the management device 1 to collate the serial number via the local government terminal 100. The management device 1 collates the serial number transmitted from the local government terminal 100 with the serial number stored in the management device 1, and transmits the collation result to the local government terminal 100. Then, if the serial numbers match, the local government official approves the bounty application and notifies the management device 1 of the fact that the bounty application is approved and the information that the bounty payment is completed. Then, the management device 1 updates the application information based on the information transmitted from the local government terminal 100.

Here, since the conventional support system is merely a system for applying for the above-mentioned bounty, it cannot be said that it is highly convenient for the user, and there is room for improvement. In other words, the conventional support system is a system specialized for hunter's bounty application, and is not highly useful for users other than hunter. In a broader sense, a conventional system is highly convenient for other users because it specializes in a function for performing a predetermined purpose for a plurality of users who subscribe to perform a predetermined purpose. I couldn't say.

Therefore, in the management method according to the embodiment, a plurality of groups having different functions available to the users are set, and each user is registered and managed in each of the plurality of groups. In the following, "group" will be referred to as "community", "sub-community" and "group". The management method according to the embodiment will be specifically described with reference to FIG.

In addition, in FIG. 1, a group including a local government and a hunter (hereinafter, a community) and a group including a farmer and a hunter (hereinafter, a group) are set. When joining a community or a group, each user transmits subscription information from the terminal device 10 to the management device 1 via an application. The subscription information includes, for example, information about the individual user (name, address, industry, etc.) and information on the community or group to which the user wants to subscribe. Then, the management device 1 registers and manages each user in the community and the group based on the received subscription information.

In the example shown in FIG. 1, a "community" and a "group" are groups having different functions available to users. Specifically, the "community" is a group that can use the application function for applying for a bounty to the local government, and the "group" is a group that cannot use the application function for applying for a bounty to the local government. The "group" is a group that can use the information sharing function between users belonging to the "group". In addition, the "community" issues an ID only to users grasped by the local government through the local government, and the "group" can issue an ID to all users. In other words, the "community" is composed of only a limited number of users, while the "group" has no restrictions on the constituent users (anyone can create and participate). That is, the "community" function is available only to a limited number of users, and the "group" function is available to all users if subscribed. In other words, the "community" and "group" have different conditions (subscription conditions) imposed on the user in order to use the function. The functions that can be used in the "community" and "group", the subscription conditions, etc. will be described later in FIGS. 3 to 5.

This allows, for example, hunter A and hunter B to apply for a bounty to the municipality by belonging to the "community", and hunter A, hunter B and the farmer to belong to the "group". , Information on hunting can be shared with other hunters and farmers. In addition, farmers who do not apply for bounties can join the "group" and share information with hunters, for example, to inform hunters of the appearance of vermin and the current hunting situation. You can hear from a hunter.

That is, in the management method according to the embodiment, the functions available to the user in the support system S are expanded by managing a plurality of groups having different functions available to the user. Thereby, for example, the convenience can be enhanced for both the user who does not apply for the bounty and the user who applies for the bounty.

The functions of the plurality of groups (communities and groups) described above are merely examples. Other functions of the plurality of populations will be described later. Further, the number of types of groups is not limited to two (community and group), and may be three or more groups. Further, a plurality of groups (subcommunities described later) may exist in one group, and the details of this point will be described later.

Next, the configuration of the management device 1 according to the embodiment will be described with reference to FIG. FIG. 2 is a block diagram showing a configuration example of the management device 1 according to the embodiment. As shown in FIG. 2, the management device 1 includes a communication unit 2, a control unit 3, and a storage unit 4.

The communication unit 2 is a network device for performing wireless communication processing and wired communication processing. For example, the communication unit 2 transmits and receives various information to and from the terminal device 10 and the local government terminal 100 via the network N shown in FIG.

The storage unit 4 is realized by, for example, a semiconductor memory element such as a RAM (Random Access Memory) or a flash memory (Flash Memory), or a storage device such as a hard disk or an optical disk. The storage unit 4 according to the embodiment stores the function information 41, the community information 42, the group information 43, the user information 44, and the application information 45.

Here, the function information 41, the community information 42, the group information 43, the user information 44, and the application information 45 stored in the storage unit 4 will be described.

The function information 41 is information regarding the contents of the functions available to the user in each group. FIG. 3 is a diagram showing an example of the functional information 41. As shown in FIG. 3, the function information 41 has items such as "unit" and "function".

A "unit" is information indicating a unit of a group. The "function" is information indicating a function available to the user.

In the example shown in FIG. 3, when the user joins the "community", the "final bounty application" function and the "application information viewing" function can be used. In addition, when the user joins the "sub-community", the "primary bounty application" function can be used. In addition, when the user joins the "group", the "hunting information sharing" function, the "trap information sharing" function, and the "chat function" can be used.

"Final application for bounty" is a function that allows you to make a final application to obtain a bounty. "Application information browsing" is a function that allows browsing of application information 45, which will be described later. "Primary application for bounty" is a function that allows you to make a primary application for obtaining a bounty. The "hunting information supply" function is a function that can share hunting information. Hunting information includes, for example, information on the appearance of pests to be captured (appearance report, place of appearance, time of appearance, animal species, etc.), hunting schedule information of hunters (day, place, time, etc. of hunting), etc. Information. The "trap information sharing" function is a function that can supply trap information. The trap information is information about the trap set by the hunter (installation position, type of trap, presence / absence of capture). The "chat function" is a function that allows you to chat with other users. The processing of the bounty application using the "final bounty application" function and the "primary bounty application" function will be described later.

The unit and function of the group shown in FIG. 3 are merely examples. The unit of the group may be two or four or more.

Next, the community information 42 is information about a "community" and a "sub-community" which are units of a group. FIG. 4 is a diagram showing an example of community information 42. As shown in FIG. 4, the community information 42 has items such as "community ID", "sub-community ID", "subscription conditions", and "number of subscribers".

The "community ID" is identification information that identifies each community. The "sub-community ID" is identification information that identifies each sub-community. "Conditions for joining" are information about conditions for joining a community or subcommunity. "Number of subscribers" is information about the number of subscribers to a community or subcommunity.

In the example shown in FIG. 4, the community identified by the community ID "C1" includes two sub-communities identified by the sub-community IDs "SC11" and "SC12". In addition, in order to join the community identified by the community ID "C1", it is a condition to join the "hunter in XX city". In addition, the community identified by the community ID "C1" has "30" hunters in the sub-community of the sub-community ID "SC11" and "50" people in the sub-community of the sub-community ID "SC12". The hunter has joined. In other words, it shows that a total of 80 hunters have joined the community with the community ID "C1".

Further, in the example shown in FIG. 4, the community identified by the community ID "C2" is a community having no sub-community, and it is shown that "500" people are subscribed to "hunters in XX prefecture". ing.

Next, the group information 43 is information about a "group" which is a unit of a group. FIG. 5 is a diagram showing an example of group information 43. As shown in FIG. 5, the group information 43 has items such as "group ID", "subscription conditions", and "number of subscribers".

The "group ID" is identification information that identifies each group. "Subscription conditions" are information regarding the conditions for joining a group. "Number of subscribers" is information about the number of subscribers to a group.

In the example shown in FIG. 5, the group identified by the group ID "G1" has no subscription conditions and can be subscribed to by anyone, indicating that "40" users are subscribed. Further, in the example shown in FIG. 5, the group identified by the group ID "G2" indicates that "15" users of the "XX district" are subscribed.

Next, the user information 44 is information about the user. FIG. 6 is a diagram showing an example of user information 44. As shown in FIG. 6, the user information 44 has items such as "user ID", "industry", and "affiliation".

The "user ID" is identification information that identifies a user. The "industry" is information about the user's industry. The "affiliation" is information about the user's affiliation (community, subcommunity, and group).

In the example shown in FIG. 6, the user identified by the user ID "U1" is a "hunter", and the affiliation belongs to the community of the community ID "C1", the sub-community of the sub-community ID "SC11", and the group ID " It shows that it is a group of "G1".

Further, in the example shown in FIG. 6, the user identified by the user ID "U2" is a "hunter", and the affiliation belongs to the community of the community IDs "C1" and "C2" and the sub-community ID "SC12". It indicates that it is a group of sub-community and group ID "G2". That is, the user identified by the user ID "U2" belongs to a plurality of communities.

Further, in the example shown in FIG. 6, the user identified by the user ID "U3" is a "farmer", and the affiliation is shown to be a group of the group ID "G2". That is, the user identified by the user ID "U3" does not join the community and the sub-community because it does not meet the joining conditions of the community and the sub-community.

Next, the application information 45 is information transmitted from a user who is a hunter, and is information for applying for a bounty. FIG. 7 is a diagram showing an example of application information 45. As shown in FIG. 7, the application information 45 has items such as "application ID", "application destination ID", "user ID", "location information", "captured individual information", "approval" and "payment". ..

The "application ID" is identification information that identifies each application information 45. The "application destination ID" is information indicating identification information of the community and subcommunity to which the application is made. The "user ID" is identification information that identifies a user who is an applicant. "Position information" is location information in which a captured individual is captured. "Captured individual information" is information about the captured individual. "Approval" is a diagram showing the approval status of the community and subcommunity to which the application is made. "Payment" is information indicating whether or not the local government has paid a bounty to the hunter.

In the example shown in FIG. 7, the application information 45 identified by the application ID "A1" is the information transmitted by the user with the user ID "U1", and "wild boar, female, ..." is the location information "# 1". ”Indicates that it was captured. The position information "# 1" can be represented by, for example, latitude and longitude. Further, the application information 45 identified by the application ID "A1" has been approved by the sub-community of the sub-community ID "SC11" and approved by the community of the community ID "C1", and the incentive has been paid. Shown.

Further, in the example shown in FIG. 7, the application information 45 identified by the application ID “A2” has not been approved by the sub-community, the approval by the community of the community ID “C2” has been completed, and the payment of the bounty has been completed. Indicates that there is no such thing.

Further, in the example shown in FIG. 7, the application information 45 identified by the application ID “A3” has been approved by the sub-community of the sub-community ID “SC11”, but has been approved by the community of the community ID “C1”. Has not been completed, indicating that the bounty payment has not been completed.

The control unit 3 has an internal memory for storing a program that defines various processing procedures and the like and required data, and executes various processing by these. The control unit 3 includes a reception unit 31, a issuing unit 32, a management unit 33, and an application unit 34.

The reception unit 31 receives various information from the user (terminal device 10) and the local government (local government terminal 100). For example, the reception unit 31 receives subscription information for each of a plurality of groups (community, subcommunity, and group) from the user via a predetermined application. The subscription information includes, for example, information about an individual user (name, address, industry, etc.) and information on a community or group to subscribe to (for example, ID).

In addition, the reception unit 31 receives various requests from the user (terminal device 10) and the local government (local government terminal 100). For example, the reception unit 31 receives a viewing request for application information 45 from a user (terminal device 10) or a local government (local government terminal 100).

The issuing unit 32 issues each identification information (ID). For example, the issuing unit 32 issues identification information corresponding to each of a plurality of groups having different functions available to the user. Specifically, the issuing unit 32 issues a community ID and a group ID. Further, when the issuing unit 32 receives the subscription information from the terminal device 10, the issuing unit 32 issues a user ID associated with the subscription information.

The management unit 33 registers and manages users in each of a plurality of groups based on the subscription information received by the reception unit 31. Specifically, the management unit 33 stores the personal information of the user included in the subscription information as the user information 44, and identifies the group (community, subcommunity and group) that the user wants to subscribe to based on the subscription information. The identification information (ID) of the group is associated with the user information 44. This completes the registration of users in communities, subcommunities, and groups. Then, when the registration is completed, the management unit 33 notifies the user that the function of the registered group (see FIG. 3) has become available in the terminal device 10.

Further, when the management unit 33 receives a viewing request for the application information 45 from a user or a local government registered in the community using the "application information viewing" function, the management unit 33 transmits the application information 45 to the user or the local government. For example, when transmitting the application information 45 to the local government, the management unit 33 may send all the application information 45 to the local government as the application destination, or the local government may specify the application information 45 (for example, unapproved or unapproved). , Application information 45 in an unpaid state, etc.), only the specified application information 45 may be transmitted.

Further, when transmitting the application information 45 to the user, the management unit 33 may transmit only the application information 45 applied by the user, or may transmit the application information 45 of the group to which the user belongs.

As shown in FIG. 3, the management unit 33 manages the community, the sub-community, and the group. Specifically, the management unit 33 manages a group (community and sub-community) that can use the application function for making a predetermined application (application for a bounty) and a group (group) that cannot use the application function. As a result, for users who do not apply for rewards such as farmers, it is possible to prevent unnecessary application functions from being used so that the functions of the application are not unnecessarily complicated. Therefore, even a user who is unfamiliar with the application can use the application without feeling any resistance.

Further, as shown in FIG. 3, the management unit 33 manages the group in which the reward application function cannot be used as a group in which the information sharing function among users belonging to the group can be used. As a result, for example, even for users who do not apply for incentives such as farmers, by joining the group, useful hunter information can be obtained from hunters, so that, for example, measures against vermin can be taken accurately. ..

Further, when viewed in terms of the relationship between the community and the group, the management unit 33 can share a plurality of groups having different information that can be shared by the users belonging to the group, specifically, the application information 45 possessed by the management device 1. And a group that can share the information (hunting information and trap information) that each user has. As a result, new information sharing can be realized, and by limiting the information that can be shared for each group, it is possible to prevent the information from being unnecessarily diffused.

Further, as shown in FIG. 4, the management unit 33 approves the application made by the application function in one group (community) in which the application function can be used, such as the relationship between the community and the sub-community. Manage multiple approval groups (subcommunities) that can use the function. The application processing by the community and the sub-community will be described later in FIG.

Further, as shown in FIGS. 4 and 5, the management unit 33 sets the community on the premise that the industry is a hunter as an enrollment condition, while does not set the industry as an enrollment condition for the group. .. In other words, the community can be joined only by hunters, and the group can be joined by any user. Further, as shown in FIGS. 4 and 5, the management unit 33 may have different joining conditions between communities and joining conditions between groups. In this way, the management unit 33 can prevent each user from joining an inappropriate group by managing groups with different joining conditions, so that each group can be composed of appropriate users.

The application unit 34 processes the application for the bounty by the user. Specifically, when the application information 45 is transmitted from the user, the application unit 34 receives the bounty application destination, application documents, and application based on the user information 44 stored in the storage unit 4. The serial number is transmitted to the terminal device 10. For example, the application unit 34 notifies the user of the community and the sub-community of the "community ID" and the "sub-community ID" in the user information 44 as the application destination. Further, the application unit 34 stores the application documents according to the application destination in advance, and distributes the determined application documents of the application destination to the user's terminal device 10. Further, the application unit 34 issues an application ID for each application information 45 and notifies the user's terminal device 10 as a serial number. As a result, the hunter who is the user submits the application documents and the serial number to the local government together with the voucher of the captured individual.

Then, when the application unit 34 receives a serial number verification request from the local government, the application unit 34 collates the serial number (application ID) transmitted via the local government terminal 100 with the application ID stored in the storage unit 4. The collation result of whether or not both application IDs match is transmitted to the local government terminal 100.

Then, the application unit 34 updates the "approval" item of the application information 45 when the local government notifies that the application for the bounty has been approved based on the collation result. In addition, the application department 34 updates the "payment" item of the application information 45 when the local government notifies that the payment of the bounty has been completed.

Next, the screen provided to the terminal device 10 via the application will be described with reference to FIG. FIG. 8 is a diagram showing a screen provided by the application. FIG. 8 shows the screens of the main menu, the community function menu, and the group function menu, respectively. The screen shown in FIG. 8 may be generated by the management device 1 and provided to the terminal device 10, or the management device 1 provides a program for screen generation to the terminal device 10 and the terminal device 10 is applied. The screen may be generated programmatically.

As shown in the left figure of FIG. 8, the terminal device 10 displays the main menu screen after the user logs in (for example, after inputting the user ID and password). Specifically, in the main menu, items for using functions such as "diary", "community function", "group function", "logout", and "debug menu" are displayed.

The "diary" is an item for the user to write a diary. The "community function" is an item for using the community function. The "group function" is an item for using the group function. "Logout" is an item for logging out. The "debug menu" is an item for displaying a menu for performing debug processing.

Hereinafter, the screen displayed when the "community function" and the "group function" are selected will be described.

<Community function>
As shown in FIG. 8, when the user performs an operation of selecting the "community function", the community function menu is displayed. FIG. 8 shows a community function menu when the user has not applied for the community.

Specifically, as shown in the upper part of the right figure of FIG. 8, the function of "community application" is displayed in a selectable manner, and "new application", "my application", "group leader", "member" and "notice" are displayed. The function of is displayed in a state where it cannot be selected (shaded display in FIG. 8). The method of expressing the non-selectable state is not limited to shading, and the display mode may be changed, for example, to reduce the shading of characters. Alternatively, the functions that cannot be selected may be hidden.

Here, the "new application" is a function of applying for a reward to the local government when a user who is a hunter captures a vermin or the like. "My application" is a function to check the current bounty application status of the logged-in user. The "group leader" is a function for displaying information about the group leader in the community and contacting the group leader (telephone, email, etc.). "Member" is a function to display information about members registered in the community and to contact members. "Notice" is a function to check the information distributed by the community.

In the community function menu shown in FIG. 8, when the user selects "community application", the terminal device 10 displays a screen for making a community application to the local government (or management device 1) for community application. I do.

Then, when the community application is completed (community registration is completed), the terminal device 10 can select "new application", "my application", "group leader", "member" and "notice" which could not be selected. Change to the state of. That is, the terminal device 10 expands the functions available in the application when the community application is completed.

<Group function>
When the user selects the "group function" in the main menu shown on the left side of FIG. 8, the group function menu is displayed. FIG. 8 shows a group function menu when a user has not applied for a group.

Specifically, as shown in the lower part of the right figure of FIG. 8, the function of "group application" is displayed in a selectable manner, and "group message", "hunting information sharing", "trap information sharing" and "notice" are displayed. The functions are displayed in a non-selectable state (shaded display in FIG. 8). The method of expressing the non-selectable state is not limited to shading, and the display mode may be changed, for example, to reduce the shading of characters. Alternatively, the functions that cannot be selected may be hidden.

Here, the "group message" is a function of transmitting predetermined information to the members registered in the group. "Hunting information sharing" is a function for sharing hunting information with members registered in the group. "Trap information sharing" is a function for sharing trap information with members registered in a group. "Notice" is a function to check the information distributed by the members of the group and the community to which the members of the group belong.

In the group function menu shown in FIG. 8, when the user selects "group application", the terminal device 10 makes a group application to the management device 1 by displaying a screen for making a group application.

Then, when the group application is completed (when the group registration is completed), the terminal device 10 can select "group message", "hunting information sharing", "trap information sharing", and "notification" which could not be selected. Change to state. That is, the terminal device 10 expands the functions available in the application when the group application is completed.

Next, with reference to FIG. 9, the processing in the support system S when the user joins the community will be described. FIG. 9 is a diagram showing a process of joining the community.

As shown in FIG. 9, first, the management device 1 provides an application to the terminal device 10 in response to a request from, for example, a non-subscriber (step S1). Further, the management device 1 establishes a new community and transmits the terms of use in the support system S, for example, in response to a community creation request from the local government (step S2). At this time, the management device 1 notifies the local government terminal 100 of the community ID that identifies the established community.

Subsequently, the local government notifies the hunter (user) known by the local government of the community ID (step S3). In this notification method, the local government terminal 100 may notify the terminal device 10 by e-mail, or the local government may mail a paper on which the community ID is written to the user. Further, the community ID may be notified from the management device 1 via the application. The hunter grasped by the local government is, for example, a user who applies for a hunter to the local government by means of documents or the like. That is, in step S3, the local government or the management device 1 notifies the user of the community ID of the local government registered as a hunter. The management device 1 is not limited to notifying the community ID of the municipality registered as a hunter, but may also distribute a list of currently registered community IDs to the user, including the municipality not registered as a hunter. good.

Subsequently, the user transmits the subscription information to the management device 1 together with the community ID distributed by the terminal device 10 (step S4). Subsequently, the management device 1 stores the subscription information and transmits it to the local government terminal 100 (step S5). Then, when the user satisfies the subscription condition based on the subscription information, the local government terminal 100 approves the subscription to the community, and the management device 1 manages the subscription information and the community ID in association with each other. The management device 1 notifies the user that the subscription to the community is completed. As a result, the user can use the community function (see FIG. 3) on the terminal device 10.

When distributing the list of communities, the management device 1 may distribute only the list of communities that satisfy the subscription conditions based on the information stored in the storage unit 4.

Next, the process in the support system S when the user joins the group will be described with reference to FIG. FIG. 10 is a diagram showing a process of joining a group. In addition, in FIG. 10, a case where a farmer and a hunter join a group will be described. Further, in FIG. 10, step S11-1 and steps S12 to S14 are group creation sequences, and steps S11-2 and steps S15 to S16 are group joining sequences.

As shown in FIG. 10, first, the management device 1 provides an application to each of the farmer and the hunter (steps S11-1 and S11-2). Subsequently, the farmer (or a hunter) transmits a group creation application together with the subscription information via the application of the terminal device 10 (step S12).

Subsequently, the management device 1 issues a new group ID and manages the subscription information and the group ID in association with each other (step S13). Subsequently, the management device 1 transmits a registration completion notification to the farmer via the application of the terminal device 10 (step S14). This registration completion notification includes information that the available group functions have been expanded. That is, the group functions (group message, hunting information sharing, trap information sharing, notification) of the hatching section shown in FIG. 8 can be used.

Next, in the group joining sequence, the hunter selects a joined group from the existing group list and applies for participation via the application of the terminal device 10 (step S15). At this time, the terminal device 10 also transmits the subscription information. That is, the hunter makes an application to the management device 1 to use the function of the group.

Then, when the management device 1 receives the participation application from the user, the management device 1 manages the group ID of the selected group in association with the subscription information, and notifies the participation completion (step S16). This registration completion notification includes information that the available group functions have been expanded. That is, the group functions (group message, hunting information sharing, trap information sharing, notification) of the hatching section shown in FIG. 8 can be used.

As a result, the hunter's participation in the group is completed, and the function of the group (see FIG. 3) becomes available in the terminal device 10. That is, as shown in FIG. 10, the information sharing function, which is a group function, enables information sharing between users.

For example, when user A creates a new group and contacts the created group ID to user B (various contact means such as telephone and mail can be used), user B corresponds from the list of groups. It is also possible to search for a group to join.

Further, FIG. 10 shows a case where the management device 1 provides a list of groups to a user. For example, a user having a group ID transmits group information including the group ID to another user, and the group information is described. Other users may apply to join the group with such a group ID. As a result, only acquaintance users can join the group, so that it is possible to prevent strangers from joining the group.

Next, the process of applying for a bounty in the support system S will be described with reference to FIG. FIG. 11 is a diagram showing a bounty application process. In FIG. 11, it is assumed that the hunter is a member of community A, sub-community A, and community B. Further, in FIG. 11, a route in which a hunter applies to community A and sub-community A for approval (approval route: route on the left side of the page) and an approval route in which only community B applies for approval (on the right side of the page). The case of applying using (route) and is explained.

First, the approval route to apply to the community A and the sub-community A will be described. The user who approves in the community A is an employee of the local government, and the user who approves in the sub-community A is, for example, a preset hunter (hereinafter referred to as an approver).

First, when the hunter captures the vermin, the hunter captures an image of the vermin via the application of the terminal device 10 and transmits the application information 45 including the image (step S21). When the management device 1 receives the application information, it issues an application ID, stores the application ID in association with the application information, and transmits the application ID to the hunter. After transmitting the application information 45, the hunter submits a voucher obtained by cutting out a part of the vermin to the sub-community A together with the application ID issued from the management device 1 (step S22).

Subsequently, the approver of the sub-community A acquires the application ID and the application information stored in the management device 1 via the terminal device 10, collates them with the application ID submitted together with the voucher, and if they match. Notifies the management device 1 that the primary approval has been made via the terminal device 10 (step S23). The verification of the application ID may be performed by the terminal device 10 or may be performed by the management device 1. Further, when the management device 1 receives the notification of the primary approval, the management device 1 updates the "approval" of the application information 45 stored in the storage unit 4.

Subsequently, the approver of the sub-community A submits the voucher to the community when the primary approval is completed (step S24). When a local government employee who is an approver of community A acquires the application ID and application information stored in the management device 1 via the terminal device 10, collates it with the application ID submitted with the voucher, and matches. Notifies the management device 1 that the final approval has been made via the terminal device 10 (step S25).

Subsequently, the approver of the community A requests the management device 1 to view the application information 45 via the local government terminal 100, and refers to the application information 45 stored in the management device 1 (step S26).

Then, when the approver of the community A completes the final approval of the referenced application information 45, the approver pays a reward to the sub-community A (step S27). Subsequently, the approver of the sub-community A provides the hunter with a reward (step S28) and ends the process.

By setting the community and sub-community and performing the application process in this way, it is possible to prevent an illegal application due to, for example, forgery of a voucher.

Next, a case where the application is processed only to the community B (route on the right side of the page) will be described. Specifically, first, when a hunter captures a vermin, he / she captures an image of the vermin via the application of the terminal device 10 and transmits application information 45 including such an image (step S31). Further, after transmitting the application information 45, the hunter submits the voucher obtained by cutting out a part of the vermin to the community B together with the application ID issued from the management device 1 (step S32).

The approver of the community B acquires the application ID stored in the management device 1 via the terminal device 10, collates it with the application ID submitted with the voucher, and if they match, the approver is via the terminal device 10. Then, the management device 1 is notified of the final approval (step S33).

Subsequently, the approver of the community B requests the management device 1 to view the application information 45 via the local government terminal 100, and refers to the application information 45 stored in the management device 1 (step S34).

Then, when the approver of the community B completes the final approval of the referenced application information 45, the approver pays a reward to the hunter (step S35) and ends the process.

Next, the flow of the community registration process of the support system S according to the embodiment will be described with reference to FIG. FIG. 12 is a sequence diagram showing a processing procedure of the community registration process of the support system S according to the embodiment. The "hunter" shown in FIG. 12 indicates the operation of the terminal device 10 possessed by the hunter, and the "local government" indicates the operation of the local government terminal 100.

First, as shown in FIG. 12, the hunter's terminal device 10 first downloads the application from the management device 1 (step S101).

Subsequently, the management device 1 issues a community ID in response to a community creation request from the local government (step S102).

Subsequently, the local government terminal 100 notifies the terminal device 10 of the community ID (step S103).

Subsequently, the terminal device 10 applies for joining the community by transmitting the joining information to the management device 1 together with the community ID selected by the user (step S104). Subsequently, the management device 1 stores the subscription information and transmits the subscription information to the corresponding community (step S105).

Subsequently, the local government terminal 100 approves the application for joining the community (step S106).

Subsequently, when the local government terminal 100 approves the application for joining the community, the local government terminal 100 sends an approval notice indicating the approval to the terminal device 10 (step S107-1). Further, the local government terminal 100 requests the management device 1 to register the user in the community in parallel with step S107-1 (step S107-2).

Subsequently, the management device 1 performs a process of registering the user in the community when there is a request for registration in the community (step S108). Specifically, the management device 1 manages the subscription information and the community ID in association with each other, and updates the community information 42, the group information 43, and the user information 44 stored in the storage unit 4.

Subsequently, when the terminal device 10 receives the approval notification from the local government terminal 100, the terminal device 10 performs a process of enabling the extended function (step S109). That is, the terminal device 10 enables the user to use the "community" function (community function menu) shown in FIG.

The processes from steps S110 to S113 described below are performed when a hunter possessing the terminal device 10 is set as a group leader (a user who performs "primary approval" of the sub-community). That is, if the hunter who possesses the terminal device 10 is not set as the group leader, the process ends up to step S109.

The processing after step S110 will be described. After approving the participation of the hunter who possesses the terminal device 10 in the community, the local government terminal 100 sets an approval route for applying for a bounty (step S110). Specifically, the local government terminal 100 will be an approval route approved only by the local government (community approver) or the approval route approved by the local government and the group leader (sub-community approver). Select.

Then, when the local government terminal 100 selects the approval route approved by the local government and the group leader, the local government terminal 100 selects the hunter who becomes the group leader, that is, the approver of the primary application for the bounty (step S111).

Subsequently, the local government terminal 100 notifies the terminal device 10 of the selected approver (hunter) that he / she has selected as the approver (step S112).

Subsequently, the terminal device 10 receives a notification from the local government terminal 100 that it has been selected as an approver, and when there is an operation of accepting the notification from the user, a notification indicating that the user has consented to become an approver is sent. This is performed for the local government terminal 100 (step S113).

Next, the flow of the group registration process of the support system S according to the embodiment will be described with reference to FIG. FIG. 13 is a sequence diagram showing a processing procedure of the group registration process of the support system S according to the embodiment. In FIG. 13, steps S201 to S205 are group creation sequences, and steps S206 to S211 are group joining sequences.

In the group creation sequence, as shown in FIG. 13, first, the hunter (or farmer) terminal device 10a downloads the application from the management device 1 (step S201).

Subsequently, the terminal device 10a makes a group creation application to the management device 1 (step S202). Subsequently, when the management device 1 receives the group creation application, the management device 1 issues a new group ID (step S203).

Subsequently, after issuing the group ID, the management device 1 notifies the terminal device 10a of the completion of registration indicating that the registration of the group is completed (step S204).

Then, the terminal device 10a expands the group function available in the application by receiving the registration completion notification (step S205).

Next, in the group joining sequence, as shown in FIG. 13, first, the terminal device 10b of the hunter (or farmer) downloads the application from the management device 1 (step S206).

Subsequently, the management device 1 notifies the existing group list via the application (step S207). When one group is selected by the user from the notified group list, the terminal device 10b makes an application for participation in the selected group (the above-mentioned application extension application and transmission of subscription information) (step S208). ).

Subsequently, the management device 1 approves the group application when the subscription information satisfies a predetermined subscription condition (step S209). Subsequently, the management device 1 notifies the terminal device 10b of the completion of participation in the group after approving the group application (step S210).

Then, by receiving the group ID, the terminal device 10b expands the group functions that can be used in the application (step S211).

As described above, the management device 1 according to the embodiment includes a reception unit 31, a issuing unit 32, and a management unit 33. The reception unit 31 receives subscription information from the user via a predetermined application to each of a plurality of groups having different functions that can be used by the user. The issuing unit 32 issues identification information corresponding to each of a plurality of groups having different functions. The management unit 33 associates the identification information with the subscription information received by the reception unit 31, and registers and manages the users in each of the plurality of groups. Thereby, the convenience of the user can be improved.

In the above-described embodiment, the case where the management device 1 distributes the application to the terminal device 10 has been described. However, for example, the application may be distributed to the terminal device 10 from another distribution server that distributes the application. ..

Although embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. This embodiment can be implemented in various other forms, and various omissions, replacements, and changes can be made without departing from the gist of the invention. This embodiment and its modifications are included in the scope and gist of the invention, as well as in the scope of the invention described in the claims and the equivalent scope thereof.

1 Management device 2 Communication section 3 Control section 4 Storage section 10 Terminal device 31 Reception section 32 Issuing section 33 Management section 34 Application section 41 Functional information 42 Community information 43 Group information 44 User information 45 Application information 100 Local government terminal N network S support system

Claims (5)

A reception unit that receives subscription information for each of a plurality of groups having different functions that can be used by the user via a predetermined application;
With a issuing department that issues identification information corresponding to each of a plurality of groups having different functions;
The user information included in the subscription information received by the reception unit is stored in the storage unit, the user information stored in the storage unit is associated with the identification information, and the user is registered in each of the plurality of groups. By doing so, with the management unit that performs processing related to the function corresponding to each of the groups;
Equipped with
The plurality of groups include a group that can use the application function for applying for a bounty and a group that cannot use the application function and can use the information sharing function between users belonging to the group. Including management equipment. The plurality of groups
The management device according to claim 1, which includes a plurality of approval groups that can use the approval function for approving the application made by the application function in one group that can use the application function. The plurality of groups
The management device according to claim 1 or 2, wherein the subscription conditions differ according to the user attributes. The plurality of groups
The management device according to any one of claims 1 to 3, wherein the information that can be shared by the users belonging to the group is different. It ’s a management method that a computer performs.
A reception process for receiving subscription information from a user to each of a plurality of groups having different functions available to the user via a predetermined application;
With the issuing process of issuing identification information corresponding to each of a plurality of groups having different functions;
The user information included in the subscription information received by the reception step is stored in the storage unit, the user information stored in the storage unit is associated with the identification information, and the user is registered in each of the plurality of groups. By doing so, with a management process that performs processing related to the function corresponding to each of the groups;
Including
The plurality of groups include a group that can use the application function for applying for a bounty and a group that cannot use the application function and can use the information sharing function between users belonging to the group. Including, management methods.

Images