Temple lodging system at Shinto shrines and Buddhist temples

Abstract

To make it possible to stay at shrine / temple lodging utilizing a network.SOLUTION: A user terminal 3, a shrine / temple terminal 4, and a server 2 can communicate with each other via a network 5. By accessing the server 2 by the user terminal 3, shrine / temple browsing data 6 is transmitted to the user terminal 3, and when a desired shrine / temple for accommodation use is selected from the transmitted shrine / temple browsing data 6 and sent back to the server 2, the server 2 transmits a selection signal to the selected shrine / temple terminal 4. The selected shrine / temple terminal 4 transmits lodging data of the shrine / temple to the user terminal 3, and the accommodation use is determined between the user terminal 3 and the shrine / temple terminal 4.SELECTED DRAWING: Figure 6

Description

Technical Field

[0001] The present invention relates to a temple lodging system of a shrine or temple that enables public communication lines to be used for staying at a temple lodging operated by a shrine or temple.

Background Art

[0002] Staying at a temple lodging operated by a shrine or temple is desired by the general public because one can experience meditation, sutra copying, sermons, and other religious practices. Since staying at a temple lodging is done by applying through a travel agency or by applying directly to the shrine or temple, it is inconvenient as it takes time and effort.

[0003] On the other hand, in recent years, services related to shrines and temples using the Internet have been provided. Patent Document 1 discloses a system for providing a virtual experience of visiting a shrine or temple by introducing the shrine or temple on a homepage on the Internet and sequentially displaying each scene of worship in order of the worship process. Patent Document 2 discloses a system for outputting requests to a shrine or temple via the Internet and having the shrine or temple perform religious acts corresponding to the requests. However, these systems are related to visiting a shrine or temple and are different from staying at a temple lodging of a shrine or temple. Staying at a temple lodging still requires applying through a travel agency or the shrine or temple, and is still inconvenient as it takes time and effort.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Patent Document 2

Summary of the Invention

Problems to be Solved by the Invention

[0005] This invention has been made in consideration of the above, and aims to provide a system for staying at temple lodgings in Shinto shrines and Buddhist temples that eliminates inconvenience by making it possible to stay at temple lodgings in Shinto shrines and Buddhist temples using the internet or other online means. [Means for solving the problem]

[0006] The present invention relates to a temple lodging system for shrines and temples, in which a user terminal, a temple terminal, and a server are able to communicate via the internet, and the system enables users to stay at temple lodgings of shrines and temples. The temple terminal comprises a temple data unit that records data related to the temple and temple and data on accommodation costs, an accommodation data unit that records data related to stays at temple lodgings, and means for transmitting the data from the temple data unit to the user terminal when a selection signal is input from the server. The server comprises temple browsing data, means for transmitting the temple browsing data to the user terminal, and means for transmitting a selection signal to the temple terminal of a selected temple. When the user terminal accesses the server, the temple browsing data is transmitted to the user terminal. When a temple or shrine that the user wishes to stay at is selected from the transmitted temple browsing data and sent back to the server, the server transmits a selection signal to the selected temple terminal, the selected temple terminal transmits the lodging data of that temple or shrine to the user terminal, and the use of accommodation is determined between the user terminal and the temple terminal.

[0007] Furthermore, the present invention is characterized in that when a lodging reservation is canceled between the user terminal and the shrine / temple terminal, the user terminal sends a cancellation signal to the server, and the server retransmits the shrine / temple browsing data to the user terminal. Furthermore, the aforementioned shrine and temple browsing data is characterized in that the training data and shrine and temple data are separated into sect / deity data, and the sect / deity data is further separated into regional data in a list format. Furthermore, the shrine / temple terminal further includes an update unit for updating the data in the shrine / temple data unit and the accommodation data unit, and the server further includes a data update unit for updating the data in the shrine / temple data unit. [Effects of the Invention]

[0008] According to the present invention, since a user terminal, a shrine / temple terminal, and a server equipped with a shrine / temple browsing data unit can communicate via the internet, it becomes possible to stay at a temple lodging, thus eliminating the inconvenience of staying at a temple lodging. [Brief explanation of the drawing]

[0009] [Figure 1] This is a diagram illustrating the configuration of the temple lodging system of the present invention. [Figure 2] Server block. [Figure 3] This is a block diagram of the user terminal. [Figure 4] This is a block diagram of the terminals for shrines and temples. [Figure 5] This diagram shows a list of access data for shrines and temples. [Figure 6] This is a flowchart showing the operation of the temple lodging system. [Figure 7] This figure shows a list of other examples of data viewed at shrines and temples. [Modes for carrying out the invention]

[0010] Figure 1 is a diagram of the configuration of the temple lodging system of the present invention, Figure 2 is a block diagram of the server, Figure 3 is a block diagram of the user terminal, Figure 4 is a block diagram of the shrine / temple terminal, Figure 5 is a diagram showing the data viewed by shrines and temples, and Figure 6 is an operation flowchart.

[0011] As shown in Figure 1, the temple lodging system 1 of the present invention allows communication between a server 2, multiple user terminals 3, and multiple shrine / temple terminals 4 via the internet 5 (hereinafter referred to as "net 5"). The server 2, user terminals 3, and shrine / temple terminals 4 can be personal computers, smartphones, tablets, etc.

[0012] As shown in Figure 2, Server 2 comprises a receiving unit 2a, a transmitting unit 2b, an output unit 2c, a data update unit 2d, shrine and temple browsing data 6, and a control unit 2e, all connected by a bus 2f. The output unit 2c includes a display unit 2g such as a monitor and a printing unit 2h such as a printer. The data update unit 2d adds, deletes, and rewrites data in the shrine and temple browsing data 6. The control unit 2e controls the receiving unit 2a, the transmitting unit 2c, the output unit 2c, and the data update unit 2d. The shrine and temple browsing data 6 is divided into data on shrines and temples, and data on the training at the temple lodgings, categorized into sect / deity data and regional data. The shrine and temple browsing data 6 will be described later.

[0013] As shown in Figure 3, the user terminal 3 is a terminal used by users who wish to stay at a temple lodging, and has a receiving unit 3a, a transmitting unit 3b, an output unit 3c, a selection unit 3d, and a control unit 3e, which are connected by a bus 3f. The output unit 3c is equipped with a display unit 3g such as a monitor and a printing unit 3h such as a printer as needed. The selection unit 3d selects a temple or shrine that suits the user's purpose from the temple and shrine browsing data 6 transmitted by the server 2. The control unit 3e controls the receiving unit 3a, the transmitting unit 3b, the output unit 3c, and the selection unit 3d.

[0014] As shown in Figure 4, the shrine / temple terminal 4 is a terminal provided by each individual shrine or temple, and has a receiving unit 4a, a transmitting unit 4b, an output unit 4c, an update unit 4d, a shrine / temple data unit 4e, an accommodation data unit 4f, and a control unit 4g, which are connected by a bus 4h. The output unit 4c has a display unit 4i such as a monitor and a printing unit 4j such as a printer.

[0015] The shrine and temple data section 4e is a recording section that records data related to the shrine and temple. For example, the name, address, email address of the shrine and temple, and the cost of staying at the temple are recorded. The accommodation data section 4f is a recording section that records data related to users staying at the temple. The name of the guest, their address, the number of guests and the dates of stay, and the time of stay are recorded. The data in the shrine and temple data section 4e and the accommodation data section 4f are added, deleted, and changed by the update section 4d and updated. The control section 4g controls the operations of the receiving section 4a, the transmitting section 4b, the output section 4c, and the update section 4d.

[0016] Figure 5 shows the shrine and temple browsing data 6 provided by the server 2. The training data (such as zazen, sutra copying, sermons, and offerings) conducted at the temple of the shrine and temple, and the data of the shrine and temple where the training is conducted (data such as the name of the shrine and temple and the address and email address) are arranged side by side and correspond. Thus, for example, a user who wants to practice "zazen" can select "Temple A", a user who wants to practice "sutra copying and yamabushi" can select "Temple B", a user who wants to practice "zazen and sermons" can select "Temple C", a user who wants to select "offering" can select "Shrine F", a user who wants to select "tea ceremony" can select "Shrine G", a user who wants to practice "zazen and sutra copying" can select "Temple H", a user who wants to practice "purification and waterfall walk" can select "Shrine I", and a user who wants to practice "purification and fire crossing" can select "Shrine J". A user who wants to practice one of multiple trainings can select the shrine and temple where the training is conducted. In the present invention, it is not limited to the above. In addition to the traditional cultures of "the three arts (tea ceremony, flower arrangement, incense ceremony)", artistic arts such as sencha tea ceremony and clothing pattern art, trainings can be set so that a wide range of styles of skills and techniques, such as noh, kyogen, hojote, bonsai, swordsmanship, archery, etc., which are inherited with the head family, main family, etc. as the apex, can be widely experienced.

[0017] In the shrine and temple browsing data 6, these training data and shrine and temple data are classified into sect and deity data (for example, Tendai sect, Shingon sect, Amaterasu, Hachiman). Thus, the user can select a temple that matches the sect and deity they desire. Furthermore, the sect and deity data is classified into regional data (e.g., Tokyo and Kanagawa). In such shrine and temple browsing data 6, the user can select the region they desire, then select the sect and deity they desire from that region, and further select the practice they desire from the sect and deity, thereby selecting the region, sect and deity, and further the lodging temple for the practice that the user desires. As described above, the user can select the practice and the shrine or temple in light of the region, sect, and deity. Since such shrine and temple browsing data 6 is in a list form, it has the merit of being easy for the user to view. The selection of the lodging is made by the selection unit 3d of the user terminal 3 by clicking on one horizontally arranged line.

[0018] Such a shrine and temple browsing data section 6 can be updated, such as added, deleted, or changed, by the data update section 2d of the server 2, thereby enabling the registration of new shrines and temples and the update of data according to the actual situation of the shrines and temples. The update of this shrine and temple browsing data section 6 is performed by the data update section 2d of the server 2 when the shrine and temple terminal 4 accesses the server 2.

[0019] FIG. 6 shows a flowchart for the user to select a lodging temple and determine the stay in that lodging. When the user terminal 3 accesses the server 2 via the network 5 (S1), the server 2 transmits the shrine and temple browsing data 6 to the user terminal 3 (S2), and the user views the shrine and temple browsing data section 6 in the form of a list on the display unit 3g and determines whether to use it (S3).

[0020] When the user uses the shrine and temple browsing data section 6 (S3(Y)), the user selects a shrine or temple that meets their requirements. This selection is made by clicking on one horizontally arranged line of the shrine and temple browsing data section 6 and transmitting a selection signal to the server 2 (S4). In S4, information such as the name of the guest, address, number of guests, arrival date, and number of days of stay is also transmitted in parallel with the selection signal. On the other hand, when the user does not use the lodging temple of the shrine or temple, the user terminal 3 transmits that fact to the server 2 (S11). Thereby, the stay in this lodging is cancelled.

[0021] Following S4, Server 2 sends a selection signal to the selected shrine / temple terminal 4 indicating that Server 2 has been selected (S5). At the same time, the guest's name, address, number of guests, date of stay, and number of nights of stay sent from the user terminal 3 are also transmitted. Following S5, the notified shrine / temple terminal 4 transmits the data from the shrine / temple data unit 4e to the user terminal 3 (S6). The user can then see the name, address, email address, and cost of the shrine / temple on the display unit 3g of the user terminal 3. The cost is calculated based on the type of training, the number of people staying, the number of nights, etc. This allows users to decide whether or not to use the lodging facilities at the shrine or temple (S7).

[0022] When a user chooses to stay at a temple or shrine's lodging facility (S7(Y)), the user terminal 3 sends a confirmation of the decision to the temple / shrine terminal 4 (S8). The temple / shrine terminal 4 then sends an acceptance signal to the user terminal 3, and the lodging reservation is completed (S9). The temple / shrine terminal 4 records the guest's name, address, number of guests, date of stay, and date of stay in the lodging data section 4f.

[0023] On the other hand, if the user does not intend to use the accommodation at the shrine or temple (S7(N)), the user terminal 3 sends a rejection to the server 2 indicating that it will not use the accommodation (S10). Upon receiving this, the server 2 resends the shrine / temple browsing data 6 to the user terminal 3 (S2). This allows the user to select another shrine or temple, and after step S3, the process proceeds to steps S4 and S11.

[0024] Figure 7 shows another example of the shrine and temple browsing data stored on Server 2. This shrine and temple browsing data 7 is first categorized by religious sect and deity (e.g., Tendai, Shingon, Soto, Amaterasu, Hachiman, Susanoo), and then further categorized by region (e.g., Tokyo, Kanagawa). With this type of data, users can select their desired religious sect and deity, then their desired region, and finally their desired type of religious practice to select a temple lodging. This type of shrine and temple browsing data 7 has the advantage of making selection more convenient because it allows users to prioritize the selection of religious sect and deity. The shrine and temple data 6 and 7 shown in Figures 6 and 7 above are provided by Server 2, and users can switch to whichever data they need.

[0025] In the above-described temple lodging system, shrines and temples have off-seasons outside of busy periods such as the end of the year. During these off-seasons, the staff of the shrines and temples (monks, Shinto priests, etc.) can participate in preparing meals (porridge, vegetarian meals, etc.) and other aspects of the temple lodging's operation for the guests. Furthermore, by holding events where guests of temple lodgings participate in activities such as cultivating fields and rice paddies, gathering firewood, harvesting crops, and assisting with fishing and forestry work, in addition to training at shrines and temples, the number of guests at the temple lodgings can increase, contributing to the revitalization of the region where the shrine or temple is located. Furthermore, shrines and temples can construct lodging facilities on land they own as manors. In this case, not only can the lodging facilities be used, but the manors can also be utilized for religious training and the events mentioned above. This allows for a wider range of activities for users. In this invention, accommodation facilities such as hotels operated or affiliated with shrines and temples can be used as temple lodgings. In this case, the shrine / temple terminal 4 can function by being installed in accommodation facilities such as hotels, rather than being installed in the shrine or temple itself.

[0026] In the above embodiment, by utilizing the internet, it becomes possible to stay at temple lodgings (shukubo) in Shinto shrines and Buddhist temples, thus eliminating the inconveniences associated with staying at such lodgings. [Explanation of symbols]

[0027] 1. The system of lodging at shrines and temples 2 servers 3. User terminals 4. Shrine and Temple Terminals 5. Shrine and Temple Browsing Data 6 Flowchart 7. Other shrine and temple browsing data

Claims

[Claim 1] This system allows users to stay at temple lodgings in shrines and temples, with the user terminal, the shrine / temple terminal, and the server communicating via the internet. The aforementioned shrine and temple terminal comprises a shrine and temple data unit for recording data relating to shrines and temples, a lodging data unit for recording data relating to stays at temple lodgings, and means for transmitting the data from the shrine and temple data unit to the user terminal when a selection signal is input from the server. The server comprises shrine and temple browsing data, means for transmitting the shrine and temple browsing data to the user terminal, and means for transmitting a selection signal to the shrine and temple terminal of the selected shrine or temple. The aforementioned shrine and temple browsing data is divided into two groups: one where regional data corresponds to sect / deity data, and another where ascetic practice data corresponds to shrine and temple data. The data is presented as a list where the aforementioned ascetic practice data corresponds to the aforementioned sect / deity data. When the user terminal accesses the server, data on shrines and temples visited is transmitted to the user terminal. When a shrine or temple where the user wishes to stay is selected from the transmitted data and sent back to the server, the server sends a selection signal to the selected shrine or temple terminal. The selected shrine or temple terminal then sends lodging data for that shrine or temple to the user terminal. After this transmission, if the user terminal sends a confirmation of decision to the shrine or temple terminal, the shrine or temple terminal sends a confirmation of acceptance to the user terminal. This transmission then confirms the lodging arrangement between the user terminal and the shrine or temple terminal. The aforementioned shrine and temple terminal has an update unit that updates the data in the shrine and temple data section and the accommodation data section, and the server has a data update unit that updates the data in the shrine and temple browsing data in response to access from the shrine and temple terminal, characterized in that it is a lodging system for shrines and temples.

Images