KR20230153664A - The wedding system using tag recognition attached to the wedding invitation. - Google Patents

Abstract

The present invention relates to a wedding ceremony system, and in particular, to a wedding ceremony system that can easily acquire and interact with various information related to the ceremony through recognition of tags attached to wedding invitations. The present invention can recognize guidance information related to the ceremony by recognizing the tag of the wedding invitation with the tag attached to the guest terminal. In addition, the present invention recognizes tags so that guests can easily record the electronic guestbook on the mobile web or app, and the wedding guest can receive it in real time. Additionally, the present invention can identify specific guests and provide specific content. In addition, according to the present invention, when a guest visits the wedding hall by car, the wedding invitation can be used as a parking ticket, and it is easy to know that the guest has come to the wedding hall. Additionally, the present invention can accurately database information on guests who actually came to celebrate at the wedding hall. Additionally, in the present invention, the tag attached to the wedding invitation can be used instead of a meal ticket, and thus the number of guests who have eaten can be accurately recorded, making it easy to settle meal expenses.

Description

{The wedding system using tag recognition attached to the wedding invitation.}

The present invention relates to a wedding ceremony system using tag recognition attached to a wedding invitation, and to a wedding ceremony system that can easily acquire and interact with various information related to the ceremony through recognition of the tag attached to the wedding invitation.

Typically, wedding invitations are sent to guests with text inviting others to the wedding. In addition, guests who receive a wedding invitation will attend the wedding by referring to the location of the wedding hall and the date and time of the wedding ceremony written on the invitation. However, this existing wedding procedure had difficulty in allowing guests to visit the wedding hall due to the limited information that could be included in the wedding invitation. In addition, existing wedding invitations simply convey information about the ceremony to the guests and do not perform any further functions. If a guest visits the wedding hall but does not pay a congratulatory fee or take a photo, the wedding invitation is later passed on to the guest. There is a problem that makes it impossible to express gratitude.

The purpose of the present invention is to provide a wedding ceremony system that allows guests to easily check guidance information related to the ceremony. In addition, another object of the present invention is to allow the wedding couple to create customized wedding invitations for each guest they wish to invite.

The goal is to provide a wedding ceremony system that can easily identify guests attending the wedding.

In order to achieve the above-described object, the present invention provides a tag attached to a wedding invitation and recorded with tag information including guest information, a reader that recognizes the tag, and a tag recorded in the tag recognized by the reader in conjunction with the reader. A marriage ceremony system is provided, which includes a system operation server that stores information.

The reader includes at least one of a guest smartphone, a parking lot reader, a wedding hall reader, and a restaurant reader.

When the reader is a guest smartphone, the tag information includes guest information and web or app linkage information, which is a mobile web or app access command provided in the system operation server. The mobile web or app includes a content database including content including a customized invitation greeting video, greeting voice, or greeting text tailored to each guest among the bride, groom, and bride, wedding ceremony schedule information, and a map showing the location of the wedding hall, It includes a content providing module that transmits the content to the guest's smartphone, and an electronic guest book module that allows the guest to create an electronic guest book using the guest's smartphone. The mobile web or app may further include an electronic guestbook transmission module that transmits the electronic guestbook to the shared terminal.

The content database includes a greeting video, greeting voice, or greeting text for a specific guest, and the mobile web or app further includes a guest information identification module that identifies guest information in a tag recognized and transmitted by the reader, If a greeting video, greeting voice, or greeting text for a specific guest exists in the content database, the content providing module provides a greeting video, greeting message, or greeting text for the specific guest to the specific guest according to the identification of the specific guest in the guest information identification module. Voice or greeting text can be transmitted to the guest's smartphone. If the reader is a parking lot reader installed at the entrance of the parking lot, the tag information includes wedding guest information and parking information in which the vehicle number and entry time are recorded. The parking lot reader includes a tag recognition module that recognizes the tag, a parking information generation module that generates parking information including an entry time according to the tag recognition time of the tag recognition module, and tag information including the parking information. It includes a tag information transmission module that transmits to the system operation server. It may further include a license plate recognition device linked to the parking lot reader. In this case, the parking information further includes a vehicle number obtained from the license plate recognition device.

When the reader is a wedding hall reader, the wedding hall reader includes a tag recognition module that recognizes the tag, and a tag information transmission module that transmits tag information stored in the tag recognized by the tag recognition module to the system operation server. . In addition, the present invention may further include an electronic guestbook writing device linked to the reader. In this case, the tag information stored in the tag recognized by the tag recognition module is transmitted to the electronic guestbook writing device, and the electronic guestbook device It includes a display module and an input module.

In addition, the system operation server includes a mobile web or app, and the mobile web or app includes an electronic guestbook module that provides an electronic guestbook creation form to the electronic guestbook creation device, and a terminal for combining the electronic guestbook from the electronic guestbook module. Includes an electronic guestbook transmission module that transmits to .

When the reader is a restaurant reader, the restaurant reader transmits a tag recognition module that recognizes the tag, tag information recorded in the tag recognized by the tag recognition module, and restaurant usage information to the system operation server. Includes an information transmission module.

The restaurant reader includes a restaurant usage information recording module that records restaurant usage information in the tag information of the tag recognized by the tag recognition module, and a message that displays a restaurant unavailable message when the restaurant usage information is identified in the tag recognition module. It further includes a cover module.

The present invention can recognize guidance information related to the ceremony by recognizing the tag of the wedding invitation with the tag attached to the guest terminal. In addition, the present invention recognizes tags so that guests can easily record the electronic guestbook on the mobile web or app, and can share it with them.

can be transmitted in real time.

Additionally, the present invention can identify specific guests and provide specific content.

In addition, according to the present invention, when a guest visits the wedding hall by car, the smart wedding invitation can be used as an electronic parking ticket, and it is easy to know that the guest has come to the wedding hall.

Additionally, the present invention can accurately database information on guests who actually came to celebrate at the wedding hall.

Additionally, in the present invention, the tag attached to the wedding invitation can be used instead of a meal ticket, and thus the number of guests who have eaten can be accurately recorded, making it easy to settle meal expenses.

Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

However, the present invention is not limited to the embodiments disclosed below and will be implemented in various different forms. These embodiments only serve to ensure that the disclosure of the present invention is complete and to those skilled in the art to fully convey the scope of the invention. It is provided to inform you clearly. Like symbols in the drawings refer to like elements.

1 is a conceptual diagram of a wedding ceremony system according to a first embodiment of the present invention.

As shown in FIG. 1, the wedding ceremony system according to the first embodiment of the present invention operates a tag 100, a reader 200 that recognizes the tag 100, and a system linked to the reader 200. Includes server 300. Additionally, it may include a customer terminal (not shown) connected to the system operation server 300.

The tag 100 is intended to provide wedding information, etc. to guests, and this embodiment illustrates that the tag 100 is attached to the wedding invitation 10. Additionally, the present invention uses a Near Field Communication (NFC) or Radio Frequency Identification (RFID) tag as the tag 100 described above.

Tag information is recorded in the tag 100, and the tag information includes wedding guest information and web or app linkage information.

The guest information includes at least one of the guest's personal information and the guest identification code. The guest's personal information may include the guest's name, address, relationship with the wedding partner/groom/bride, etc., and the guest identification code may include numbers, letters, and symbols that can identify the guest. In other words, only the guest's identification code may be recorded, excluding the guest's personal information. Instead of performing the embodiment described later, the wedding invitation 10 is simply recognized as a smartphone and the operation recorded in the web or app linkage information is performed. When terminated, only web or app linkage information may be recorded in the tag.

Web or app linkage information allows a guest who has received a wedding invitation (10) to perform a pre-planned action when a smartphone capable of using an NFC or RFID (Radio Frequency Identification) tag recognizes the tag (100) attached to the wedding invitation (10). Includes information that: Specifically, the web or app linkage information may include commands for accessing the web or app built on the system operation server 300, which will be described later. Accordingly, when a guest recognizes the tag with a smartphone, the smartphone automatically connects to the web or the web recorded in the app linkage information. In addition, on the web or app, you can view guidance information including the location of the wedding hall and the date and time of the wedding, an electronic guestbook and greeting video, and a map showing the location of the wedding hall.

The reader 200 is used to recognize the tag 100, and basically represents a smartphone owned by a wedding guest. At this time, the above-mentioned smartphone must be a smartphone capable of using NFC or RFID (Radio Frequency Identification) tags. As these smartphones recognize the tag 100 attached to the wedding invitation 10, without any additional special configuration, the functions that the smartphone can perform are expressed and recorded in the above-described web or app linkage information. The action can be performed.

The system operation server 300 is equipped with a mobile web or app that is accessed through web or app linkage information. At this time, the mobile web or app performs a greeting video, wedding ceremony schedule information, and a map display function that shows the location of the wedding hall. For this purpose, the mobile web or app provided in the system operation server 300 includes a content database that stores common greeting videos commonly shown to all guests, wedding ceremony schedule information, and maps, and a content database that stores the wedding ceremony schedule information and maps, and allows guests to access the mobile web or app. It includes a content provision module that provides the relevant content to the guests, and an electronic guestbook module that allows guests to create an electronic guestbook or view the created electronic guestbook. Here, when the guest's basic information is included in the above-described tag, the guest does not have to manually write additional information such as his or her name when writing the electronic guest book, but can use the guest's basic information recorded in the tag 100 to make his or her own personal information. Information is automatically recorded. Additionally, mobile web or apps can provide content including video and audio from guests to the bride or groom. To this end, the electronic guestbook described above may additionally have video and audio recording functions in addition to message recording. In other words, guests can record congratulatory voice messages, videos, and congratulatory messages to the groom, bride, or wedding couple. At this time, the video and audio of the guests can be acquired with the guest's smartphone and transmitted to the mobile web or app, or the video and audio produced through other means can be uploaded to the mobile web or app. Of course, it is preferable that the electronic guestbook written by the guest be transmitted to the guestbook terminal through the electronic guestbook transmission module provided in the mobile web or app. Here, shared terminals include computers, smartphones, etc. Meanwhile, specific greetings for specific guests can be additionally stored in the content database of the mobile web or app, and are provided when the specific guest accesses the mobile web or app. Of course, for this, the mobile web or app must be additionally equipped with a guest information identification module, and the guest information identification module identifies the guest information included in the tag information, determines whether the guest is a specific guest, and then provides a specific greeting for that guest. . In addition, it is effective to additionally record specific guest information in the content database and compare it with the guest information included in the tag information to determine whether the guest is a specific guest.

In addition, this embodiment illustrates that the above-described mobile web or app is provided in the system operation server 300, but the present invention is not limited to this. In other words, the mobile web or app may be installed on the guest's smartphone. In this case, the web or app linkage information must include a command that causes the guest smartphone that recognizes the tag to access the system operation server 300 and download the mobile web or app. In addition, it is desirable that all content generated from the mobile web or app installed on the guest's smartphone is stored in the system operation server 300.

As described above, in this embodiment, the tag of the wedding invitation with the tag attached can be recognized by the guest terminal to check guidance information related to the ceremony. In addition, this embodiment recognizes the tag so that guests can easily record the electronic guestbook on the mobile web or app, and the wedding guest can receive it in real time. Additionally, this embodiment can identify specific guests and provide specific content.

Next, a wedding ceremony system according to a second embodiment of the present invention applied to a parking lot will be described with reference to the drawings. Among the content to be described later, content that overlaps with the description of the marriage ceremony system according to the first embodiment of the present invention described above will be omitted or briefly described. Additionally, the second embodiment of the present invention, which will be described later, may include the configuration mentioned in the first embodiment of the present invention described above.

Figure 2 is a conceptual diagram of a wedding ceremony system according to a second embodiment of the present invention.

As shown in FIG. 2, the wedding ceremony system according to the second embodiment of the present invention operates a tag 100, a reader 200 that recognizes the tag 100, and a system linked to the reader 200. Includes server 300. Additionally, it may include a customer terminal (not shown) connected to the system operation server 300.

The tag 100 exemplifies an NFC tag or a Radio Frequency Identification (RFID) tag, similar to the first embodiment of the present invention described above. Additionally, tag information is recorded in the tag 100. In this embodiment, tag information includes wedding guest information and parking information. Here, the guest information includes at least one of the guest's personal information and the guest identification code. However, the present invention is not limited to this, and the tag information may further include at least one of mixed color information and mixed color identification code. Parking information is basically not generated unless the guest touches the tag 100 on the parking lot reader. Parking information will be explained in the reader 200, which will be described later.

The reader 200 is used to identify the tag 100 attached to the wedding invitation 10 and to record parking information on the tag 100. This embodiment illustrates a parking lot reader provided at the entrance to a wedding hall parking lot. This parking lot reader includes a tag recognition module 210 that recognizes the tag 100, a parking information generation module 220 that generates parking information, and tag information including the generated parking information to the system operation server 300. It may further include a tag information transmission module 230 for transmitting. Here, the parking information includes the entry time according to the tag recognition time. That is, in this embodiment, it is possible to know which guest parked the vehicle and when, even if there is no vehicle number, by using the entry time and guest information included in the tag information. Of course, if a license plate recognition device (not shown) linked to the reader 200 is provided, accurate parking information can be obtained by including the vehicle number in the vehicle information.

The tag recognition module 210 is for recognizing the tag 100 attached to the wedding invitation 10 of the guest. Since this embodiment exemplifies an NFC tag or RFID (Radio Frequency Identification) tag as the tag, the tag recognition module 210 ) must also be able to recognize NFC tags or RFID (Radio Frequency Identification) tags. Additionally, tag recognition by the tag recognition module 210 may be performed by touching the tag 100.

The parking information generation module 220 generates parking information including the entry time based on the time when the tag 100 was recognized. In addition, this parking information is included in the tag information and is transmitted to the system operation server through the tag information transmission module 230, which will be described later.

Sent to (300).

The tag information transmission module 230 transmits the tag information recognized by the tag recognition module 210 to the system operation server 300, which can be confirmed by the owner. In addition, according to this, the wedding couple can know that the guest visited the wedding venue based on the guest information included in the tag information.

Meanwhile, this embodiment includes a parking information recording module (not shown, included in the reader 200) that records parking information in the recognized tag 100 when parking information is not transmitted to the system operation server 300. You may. This can be used later when the guest settles parking fees. Of course, this embodiment can also be used when you simply want to allow only authorized vehicles to enter the parking lot. In this case, it is desirable to install bar-type entry control equipment at the entrance of the parking lot equipped with a parking lot reader, and unless the reader recognizes the tag 100 with the tag information recorded, vehicles that are not authorized by the parking lot control equipment Entry and exit can be blocked.

The system operation server 300 is linked to the reader 200 and is equipped with a guest database 310. Here, interworking between the reader 200 and the system operation server 300 can be implemented through a wired or wireless connection.

The guest database 310 includes guest information and parking information acquired by the reader 200. Of course, since not all guests visit the wedding hall by car, guest information may not be acquired by the reader 200 but may be recorded in advance in the guest database.

Meanwhile, this embodiment illustrates that the system operation server 300 is provided with a guest database 310, but the present invention is not limited to this and may further include the above-described mobile web or app (not shown). In addition, according to this, in this embodiment, vehicle information and guest information corresponding to the vehicle information can be transmitted to the wedding reception terminal through the mobile web or app, and the marriage ceremony can know that the guest has visited the wedding hall. Additionally, for this function, the mobile web or app may be equipped with a vehicle/guest information transmission module (not shown). In addition, the system operation server 300 has a guest database

In addition to 310, a mixed drink database 320 in which mixed drink information is stored may be provided. The guest database 310 and the wedding ceremony database 320 must be linked with each other to identify which guests are associated with which wedding couples. Of course, the wedding guest database 320 may not be created separately but may exist within the wedding guest database 310. In the following embodiments, mention of the pooled database 320 will be omitted.

Meanwhile, although this embodiment only illustrates a parking lot, the present invention can be implemented by combining the above-described first embodiment and this embodiment.

As described above, in this embodiment, when a guest visits the wedding hall by car, the wedding invitation 10 can be used as a parking ticket. Additionally, you can easily tell that the guest in question has come to the wedding hall.

Next, a wedding ceremony system according to a third embodiment of the present invention applied to a wedding hall will be described with reference to the drawings. Among the content described later, content that overlaps with the description of the marriage ceremony system according to the first and second embodiments of the present invention described above will be omitted or briefly described. In addition, the third embodiment of the present invention, which will be described later, can be implemented in combination with the configurations mentioned in the first and second embodiments of the present invention described above, even if there is no separate mention.

Figure 3 is a conceptual diagram of a wedding ceremony system according to a third embodiment of the present invention.

As shown in FIG. 3, the wedding ceremony system according to the third embodiment of the present invention operates a tag 100, a reader 200 that recognizes the tag 100, and a system linked to the reader 200. Includes server 300. Additionally, it may include a customer terminal (not shown) connected to the system operation server 300.

Tag information stored in the tag 100 includes wedding guest information. Of course, when the above-described embodiments are combined with the present embodiment, the tag information includes wedding guest information, web connection information, and parking information. Additional mixed drink information may be added here. The reader 200 recognizes the tag 100 attached to the wedding invitation 10, and this embodiment exemplifies a wedding hall reader provided at a wedding hall. This wedding hall reader includes a tag recognition module 210 that recognizes the tag 100, and a system operation server that sends tag information to the system operation server.

It includes a tag information transmission module 230 that transmits to 300. Here, since the tag recognition module 210 has the same configuration as described above, its description is omitted.

The tag information transmission module 230 transmits the tag information stored in the tag 100 recognized by the tag recognition module 210 to the system operation server.

Send to (300). Accordingly, the wedding couple can later accurately recognize that the guest with the corresponding tag information has visited the wedding hall.

Meanwhile, this embodiment may further include an electronic guestbook creation device 400.

The electronic guest book writing device 400 is linked with the reader 200 to enable the guest to write an electronic guest book when the tag 100 is recognized by the reader 200. In other words, when the tag 100 is recognized by the reader 200, the tag information is transmitted to the electronic guest book creation device 400, and accordingly, the guest can write a congratulatory message without manually entering information that can identify him/her. do. Of course, the congratulatory message includes at least one of text, video, and audio. Additionally, this electronic guestbook creation device 400 may be implemented through a display module 410 and an input module 420. Here, when using a general monitor as the display module 410, the input module 420 may include input tools such as a mouse and keyboard. Additionally, when a touch screen is used as the display module 410, the input module 420 can also be a touch screen. If the guest is old, it may be inconvenient to use input tools such as a keyboard and mouse, so it is preferable to use a touch screen for the display module 410 and the input module 420 for the convenience of the guest.

The system operation server 300 is linked to the wedding hall reader and electronic guest book writing device 400, and is equipped with a guest database 310, a wedding guest database 320, and a mobile web or app 330.

The mobile web or app 330 includes an electronic guestbook module that provides an electronic guestbook creation form displayed on the electronic guestbook creation device 400. Here, the electronic guestbook module is implemented in the mobile web or app, and the guestbook writing device performs the function of displaying it. Of course, this function is not implemented on the mobile web or app, but inside the electronic guestbook creation device.

It may be stored and implemented in (400), and in this case, only the contents of the electronic guest book may be transmitted to the system operation server (300) and stored in the guest database (310).

The guest database 310 stores and manages guest information provided in advance by the wedding guest and electronic guest book creation information. Additionally, if a guest to whom a wedding invitation 10 is included in the guest information actually visits the wedding hall, attendance information is additionally recorded in the guest information. Accordingly, the wedding couple can later express their gratitude to the guests who attended the wedding. Additionally, the recorded electronic guestbook can be viewed through the electronic guestbook writing device 400, and can also be viewed through the reader 200 or the shared terminal of the first embodiment described above.

As described above, this embodiment can accurately database information on guests who actually came to celebrate at the wedding hall.

Next, the wedding ceremony system according to the fourth embodiment of the present invention applied to a restaurant will be described with reference to the drawings. Among the content to be described later, content that overlaps with the description of the marriage ceremony system according to the first to third embodiments of the present invention described above will be omitted or briefly described. Additionally, the fourth embodiment of the present invention to be described later may include the configurations mentioned in the first to third embodiments of the present invention described above.

Figure 4 is a conceptual diagram of a wedding ceremony system according to a fourth embodiment of the present invention.

As shown in FIG. 4, the wedding ceremony system according to the fourth embodiment of the present invention operates a tag 100, a reader 200 that recognizes the tag 100, and a system linked to the reader 200. Includes server 300.

In this embodiment as well, the tag 100 includes tag information, and the tag information includes wedding guest information and meal ticket information. Of course, when all of the above-described embodiments are combined, the tag information includes wedding guest information, web or app linkage information, parking information, and meal ticket information. In addition, mixed drink information may be included.

The reader 200 identifies the tag 100 attached to the wedding invitation 10, and this embodiment illustrates a restaurant reader placed at the entrance of a restaurant targeting guests attending a wedding ceremony. When a guest recognizes the tag 100 attached to the wedding invitation 10, this restaurant reader can read the tag information and display in the guest database 310 of the system operation server 300 that the guest used the restaurant. there is. This can be accomplished by additionally recording restaurant usage information in the guest database 310. For this purpose, the restaurant reader includes a tag recognition module 210 that recognizes the tag 100, and a restaurant usage information transmission module 240 that transmits restaurant usage information to the system operation server 300. Of course, tag information may be transmitted instead of restaurant usage information, and the system operation server 300 may record the restaurant usage information in the guest database 310 after recognizing that the tag information has been transmitted from the restaurant reader. Additionally, in addition to the guest database 310, a separate restaurant usage information database (not shown) may be created to record guests' restaurant usage information.

Additionally, the reader 200 may further include a restaurant usage information recording module 250. This is to prevent additional use if the restaurant has been used once with one tag (100). In other words, if the number of uses of the tag 100 is not limited in a restaurant, for example, a wedding invitation 10 with the tag 100 attached can be acquired and used by another person, so the use of the tag 100 in the restaurant is limited. It is desirable to limit the number of times. Also, for this purpose, the reader 200 may further include a message indicator module 260 that displays a message that the restaurant is not available when restaurant usage information is identified in the tag recognition module 210.

Meanwhile, the present invention can automatically add meal ticket information to the tag information when the tag 100 is recognized by the wedding hall reader of the third embodiment described above. Additionally, since a meal ticket is generally issued when a gift is paid, a reader can be installed at the place where the gift is received to add food ticket information.

In addition, in this embodiment, when the meal cost is settled only by the number of guests, the system operation server 300 may be provided with a meal cost settlement module 340 to automatically settle the meal cost.

As described above, in this embodiment, the tag attached to the wedding invitation can be used instead of a meal ticket, and thus the number of guests who have eaten can be accurately recorded, making it easy to settle meal expenses.

Although the above has been described with reference to the drawings and examples, those skilled in the art can make various modifications and changes to the present invention without departing from the technical spirit of the present invention as set forth in the claims below. You will understand.

Claims (11)

A tag attached to a wedding invitation and recording tag information including guest information, a reader that recognizes the tag, and
It includes a system operation server that is linked to the reader and stores tag information recorded in the tag recognized by the reader,
A wedding ceremony system characterized in that the reader includes at least one of a guest smartphone, a parking lot reader, a wedding hall reader, and a restaurant reader. In claim 1,
The reader includes a guest smartphone,
A wedding ceremony system characterized in that the tag information includes guest information and web or app linkage information, which is a mobile web or app access command provided on the system operation server. The method of claim 2, wherein the mobile web or app,
A content database including content having a customized greeting video, greeting voice, or greeting text for at least one of the wedding couple, the groom, and the bride, wedding ceremony schedule information, and a map showing the location of the wedding venue;
A content provision module that transmits the content to the guest smartphone, and
A wedding ceremony system characterized by including an electronic guest book module that allows the guest to create an electronic guest book using the guest's smartphone. In claim 3,
A wedding ceremony system, wherein the mobile web or app further includes an electronic guest book transmission module that transmits the electronic guest book to a wedding terminal. In claim 3,
The content database includes a greeting video, greeting voice, or greeting text for a specific guest, and the mobile web or app has a guest information identification module that identifies guest information in a tag recognized and transmitted by the reader.
It further includes,
If there is a greeting video, greeting voice, or greeting text for a specific guest in the content database, the content providing module provides a greeting video for the specific guest, according to the specific guest identification in the guest information identification module. A wedding ceremony system characterized by transmitting a greeting voice or a greeting text to the guest's smartphone. In claim 1,
The reader includes a parking lot reader installed at the parking lot entrance, and the parking lot reader includes,
A tag recognition module that recognizes the tag, a parking information generation module that generates parking information including the entry time according to the tag recognition time of the tag recognition module, and a tag information including the parking information to the system operation server. Includes a tag information transmission module,
A wedding ceremony system characterized in that the tag information includes guest information and parking information in which vehicle number and entry time are recorded. In claim 6,
Further comprising a license plate recognition device linked to the parking lot reader,
A wedding ceremony system, wherein the parking information further includes a vehicle number obtained from the license plate recognition device. In claim 1,
The reader includes a wedding hall reader, and the wedding hall reader includes a tag recognition module that recognizes the tag, and a tag information transmission module that transmits tag information stored in the tag recognized by the tag recognition module to the system operation server. ,
Further comprising an electronic guest book writing device linked to the reader,
The tag information stored in the tag recognized by the tag recognition module is transmitted to an electronic guest book creation device, and the electronic guest book device includes a display module and an input module. In claim 8,
The system operating server includes a mobile web or app,
The mobile web or app includes an electronic guestbook module that provides an electronic guestbook creation form to the electronic guestbook creation device, and an electronic guestbook transmission module that transmits the electronic guestbook from the electronic guestbook module to the shared terminal.
A wedding ceremony system. In claim 1
The reader includes a restaurant reader,
The restaurant reader includes a tag recognition module that recognizes the tag,
A wedding ceremony system comprising a restaurant usage information transmission module that transmits the tag information recorded in the tag recognized by the tag recognition module and the restaurant usage information to the system operation server. In claim 10,
The restaurant reader includes a restaurant usage information recording module that records restaurant usage information in tag information of the tag recognized by the tag recognition module;
A wedding ceremony system further comprising a message beacon module that displays a restaurant unavailable message when the restaurant usage information is identified in the tag recognition module.