JP2021179805A - Information processing method, information processing system, information processing apparatus, and program - Google Patents

Abstract

To provide an information processing method, an information processing system, an information processing apparatus, and a program which allow an exhibitor to download visitor data in a real-time fashion.SOLUTION: A visitor management system for an exhibitor has a management apparatus 1, a portable terminal 2, and an exhibitor terminal 3. The management apparatus transmits an exhibitor code used for being read by the portable terminal 2 lent to a plurality of exhibitors for exhibition in an event and used for identification of the exhibitor, receives a log-in of the portable terminal 2 through the exhibitor code, stores, in association with the exhibitor, visitor data corresponding to a visitor code read by the portable terminal 2 after its log-in, notifies each exhibitor of exhibitor access information for use in downloading the visitor data before or during the exhibition, and outputs the visitor data in response to a download request for the visitor data based on the access information of the notified exhibitor.SELECTED DRAWING: Figure 1

Description

The present invention relates to an information processing method, an information processing system, an information processing device and a program.

When a visitor visits a facility or an event venue, there is a technology to accept the visitor using a code for identifying the visitor. For example, Patent Document 1 discloses a visitor management system that reads a visitor identification code printed on a letter brought by a visitor and registers the read visitor identification code in a visitor database.

Japanese Unexamined Patent Publication No. 2006-99786

However, the invention according to Patent Document 1 has a problem that the visitor data cannot be confirmed at any time until the delivery date.

One aspect is to provide an information processing method or the like that allows exhibitors to download visitor data in real time.

The information processing method according to one aspect is to send an exhibitor code that identifies the exhibitor for reading with a mobile terminal lent to a plurality of exhibitors exhibiting at the event, and the mobile device through the exhibitor code. Accepts the login of the terminal, stores the visitor data corresponding to the visitor code read by the mobile terminal after login in association with the exhibitor, and downloads the visitor data before or during the exhibition. The exhibitor's access information for this purpose is notified to each exhibitor, and the visitor data is output in response to the visitor data download request based on the notified exhibitor's access information.

On one side, exhibitors can download visitor data in real time.

It is explanatory drawing which shows the outline of the visitor management system for exhibitors. It is a block diagram which shows the configuration example of a server. It is explanatory drawing which shows an example of the record layout of the event DB. It is explanatory drawing which shows an example of the record layout of a download data DB. It is explanatory drawing which shows an example of the record layout of a visitor DB. It is explanatory drawing which shows an example of the record layout of an exhibitor DB. It is explanatory drawing which shows an example of the record layout of the terminal monitoring DB. It is a block diagram which shows the configuration example of a mobile terminal. It is a block diagram which shows the configuration example of an exhibitor terminal. It is explanatory drawing explaining the operation of a visitor management system. It is a flowchart which shows the processing procedure at the time of performing the login processing of the mobile terminal through the exhibitor code. It is a flowchart which shows the processing procedure at the time of outputting a visitor data. It is a flowchart which shows the processing procedure at the time of outputting a visitor data. It is explanatory drawing which shows an example of the screen which displays the exhibitor code on an exhibitor terminal. It is explanatory drawing which shows an example of the screen which reads the exhibitor code with a mobile terminal. It is explanatory drawing which shows an example of the download screen of a visitor data. It is a block diagram which shows the configuration example of the server of Embodiment 2. It is explanatory drawing which shows an example of the record layout of a download setting DB. It is a flowchart which shows the processing procedure at the time of accepting the selection of the item to be downloaded. It is a flowchart which shows the processing procedure at the time of outputting the visitor data based on the item to be downloaded. It is explanatory drawing which shows an example of the screen which accepts the selection of the item to be downloaded. It is a block diagram which shows the configuration example of the server of Embodiment 3. It is explanatory drawing which shows an example of the record layout of the visitor management DB. It is a block diagram which shows the structural example of the mobile terminal of Embodiment 3. It is explanatory drawing which shows an example of the record layout of a read history DB. It is explanatory drawing which shows an example of the record layout of the visitor information display DB. It is a functional block diagram which shows the processing operation which performs the synchronization processing based on a visitor ID. It is a flowchart which shows the processing procedure at the time of accepting the visitor who came to the event. It is a flowchart which shows the processing procedure at the time of accepting the visitor who came to the event. It is explanatory drawing which shows an example of the reception screen of a visitor. It is explanatory drawing which shows an example of the reading history screen.

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

(Embodiment 1)
The first embodiment relates to a form of outputting visitor data in response to a download request of an exhibitor exhibiting at an event. FIG. 1 is an explanatory diagram showing an outline of a visitor management system for exhibitors. The system of the present embodiment includes a management device 1, a mobile terminal 2, and an exhibitor terminal 3, and each device transmits and receives information via a network N such as the Internet.

The management device 1 is an information processing device that processes, stores, and transmits / receives various information. The management device 1 is, for example, a server device, a personal computer, or the like. In the present embodiment, the management device 1 is assumed to be a server device, and is referred to as a server 1 in the following for the sake of brevity.

The mobile terminal 2 is a terminal device that logs in to the mobile terminal through the exhibitor code, reads the visitor code, and transmits the visitor identification information read from the visitor code. The mobile terminal 2 is an information processing device such as a smartphone or a tablet. Alternatively, the mobile terminal 2 may be a terminal device provided with a dedicated reading module capable of reading the code.

For example, the mobile terminal 2 checks the attendance of visitors at an event in which a plurality of sub-events (for example, an exhibition booth or a seminar in the event) are held, such as an exhibition event in which a plurality of exhibitors exhibit their booths. Therefore, the code is read. The event is not limited to the exhibition event, and may be another event such as a lecture or a live music. The mobile terminal 2 is operated by, for example, the event organizer or an exhibitor exhibiting at an individual booth in the event venue, and reads the code at a predetermined reception desk installed at the event venue or at each booth. .. For example, the mobile terminal 2 is rented out to the person in charge of the event organizer or the organizer (exhibitor) of each sub-event at the time of the event, and is returned after the event is over.

The exhibitor terminal 3 is a terminal device for downloading visitor data, displaying visitor data, and the like. The exhibitor terminal 3 is an information processing device such as a smartphone, a mobile phone, a tablet, or a personal computer terminal.

In the present embodiment, the server 1 issues an exhibitor code for identifying an exhibitor to be read by a mobile terminal 2 lent to a plurality of exhibitors exhibiting at an event. The server 1 accepts the login of the mobile terminal 2 through the exhibitor code issued to the exhibitor, and performs the login process. The server 1 pre-registers information about visitors (applicants) who come to the event in association with the visitor identification information, and issues a visitor code describing the visitor identification information to the visitors in advance. do.

After logging in to the mobile terminal 2, the mobile terminal 2 reads the visitor identification information from the visitor code issued to the visitor and transmits it to the server 1 via the network N. The server 1 stores the visitor data in association with the exhibitor based on the visitor identification information transmitted from the mobile terminal 2. The server 1 transmits the exhibitor's access information for downloading the visitor data to the exhibitor terminal 3 of each exhibitor before or during the exhibition. The exhibitor terminal 3 receives the exhibitor's access information transmitted from the server 1. The exhibitor terminal 3 transmits a download request for the exhibitor's visitor data to the server 1.

When the server 1 receives the visitor data download request transmitted from the exhibitor terminal 3, the server 1 determines whether or not the number of visitor data download requests exceeds a predetermined number of times. When the server 1 determines that the number of download requests does not exceed the predetermined number of times, the server 1 outputs the visitor data to the exhibitor terminal 3 in response to the download request. When the server 1 determines that the number of download requests exceeds the predetermined number of times, the server 1 retransmits the access information of the new exhibitor to the exhibitor terminal 3.

FIG. 2 is a block diagram showing a configuration example of the server 1. The server 1 includes a control unit 11, a storage unit 12, a communication unit 13, an input unit 14, a display unit 15, a reading unit 16, and a large-capacity storage unit 17. Each configuration is connected by bus B.

The control unit 11 includes an arithmetic processing unit such as a CPU (Central Processing Unit), an MPU (Micro-Processing Unit), and a GPU (Graphics Processing Unit), and reads and executes the control program 1P stored in the storage unit 12. , Performs various information processing, control processing, etc. related to the server 1. Although the control unit 11 is described as a single processor in FIG. 2, it may be a multiprocessor.

The storage unit 12 includes memory elements such as a RAM (Random Access Memory) and a ROM (Read Only Memory), and stores the control program 1P or data required for the control unit 11 to execute processing. Further, the storage unit 12 temporarily stores data and the like necessary for the control unit 11 to execute arithmetic processing. The communication unit 13 is a communication module for performing processing related to communication, and transmits / receives information to / from the mobile terminal 2 and the exhibitor terminal 3 via the network N.

The input unit 14 is an input device such as a mouse, a keyboard, a touch panel, and a button, and outputs the received operation information to the control unit 11. The display unit 15 is a liquid crystal display, an organic EL (electroluminescence) display, or the like, and displays various information according to the instructions of the control unit 11.

The reading unit 16 reads a portable storage medium 1a including a CD (Compact Disc) -ROM or a DVD (Digital Versatile Disc) -ROM. The control unit 11 may read the control program 1P from the portable storage medium 1a via the reading unit 16 and store it in the large-capacity storage unit 17. Further, the control unit 11 may download the control program 1P from another computer via the network N or the like and store it in the large-capacity storage unit 17. Furthermore, the control unit 11 may read the control program 1P from the semiconductor memory 1b.

The large-capacity storage unit 17 includes a recording medium such as an HDD (Hard disk drive) or SSD (Solid State Drive). The large-capacity storage unit 17 includes an event DB (database: database) 171, a download data DB 172, a visitor DB 173, an exhibitor DB 174, and a terminal monitoring DB 175. The event DB 171 stores information about the event. The download data DB 172 stores visitor data for download. The visitor DB 173 stores information about the visitor. Exhibitor DB 174 stores information about exhibitors. The terminal monitoring DB 175 stores information about a plurality of mobile terminals to be monitored.

In this embodiment, the storage unit 12 and the large-capacity storage unit 17 may be configured as an integrated storage device. Further, the large-capacity storage unit 17 may be composed of a plurality of storage devices. Furthermore, the large-capacity storage unit 17 may be an external storage device connected to the server 1.

In the present embodiment, the server 1 is described as one information processing device, but it may be distributed and processed by a plurality of servers, or it may be configured by a virtual machine.

FIG. 3 is an explanatory diagram showing an example of the record layout of the event DB 171. The event DB 171 has an event ID column, an event name column, a program column, a venue column, a date column, a holding start time column, a holding end time column, a downloadable period column, a loginable period column, an application start date and time column, and an application end. Includes date / time column, reception start time column, reception end time column, sub-event ID column, and sub-event name column.

The event ID column stores the ID of the event to be uniquely specified in order to identify each event. The event name column stores the name of the event. The program column stores the program (contents) of the event. The venue column remembers where the event is held. The date column remembers the date when the event is held. The start time column stores the start time of the event. The event end time column remembers the end time of the event. The downloadable period column stores the period during which the visitor data can be downloaded.

The loginable period column stores the period during which the mobile terminal 2 can log in to the server 1 through the exhibitor code. The application start date and time column stores the start date and time when the event is applied. The application end date and time column stores the end date and time when the event is applied. The reception start time column stores the start time for accepting an event. The reception end time column stores the end time for accepting an event. The sub-event ID column stores the sub-event ID that uniquely identifies the sub-event in the event. The sub-event name column stores the name of the sub-event.

FIG. 4 is an explanatory diagram showing an example of the record layout of the download data DB 172. The download data DB 172 includes a terminal ID column, an exhibitor ID column, a reading date / time column, a visitor ID column, a request code string, and a read ID column. The terminal ID column stores the mobile terminal ID that identifies the mobile terminal 2 lent to the exhibitor. The exhibitor ID column stores the exhibitor ID that identifies the exhibitor. The reading date / time column stores the date / time information when the visitor code is read. The visitor ID column stores the visitor ID (read content) read from the visitor code.

The request code string stores the request code that identifies the request. The request code is an identifier for identifying the request of the visitors who come to the event (for example, the person in charge of explanation on the day, the degree of interest, the catalog of distribution, etc.), and the organizer (exhibitor) of the sub-event arbitrarily decides. Define. By confirming the request code, the organizer of the sub-event can quickly grasp the request of the visitor. The lead ID column stores an ID for each applicant that is unique to the event (campaign, seminar, etc.).

FIG. 5 is an explanatory diagram showing an example of the record layout of the visitor DB173. The visitor DB173 includes a visitor ID column, an event ID column, a sub-event ID column, a number of visitors column, a surname column, a middle name column, a first name column, a surname frigana column, a first name frigana column, a company name column, and a company name frigana column. , Department column and attribute column. The visitor ID column stores the ID of the visitor uniquely specified in order to identify each visitor. The event ID column stores an event ID that identifies an event. The sub-event ID column stores the sub-event ID that identifies the sub-event that the visitor visits. The number of visitors column stores the number of visitors to the event according to one visitor ID. One visitor ID can be used by a plurality of visitors (multiple people) at the same time.

The surname column remembers the surname of the visitor. The middle name column remembers the middle name of the visitor. The name string remembers the names of the visitors. The surname furigana column remembers the furigana of the visitor's surname. The furigana column remembers the furigana of the visitor's name. The company name column remembers the name of the company to which the visitor belongs. The furigana column of the company name remembers the furigana of the company name. The department column remembers the department of the company to which the visitor belongs. The attribute column stores attribute information according to the attributes of the visitors. The attribute information can be expressed by, for example, a "VIP (Very Important Person) member", a "product A purchasing customer", or the like when the event is an exhibition of products.

FIG. 6 is an explanatory diagram showing an example of the record layout of the exhibitor DB 174. The exhibitor DB 174 includes an exhibitor ID column, an event ID column, a sub-event ID column, an exhibitor name column, an available terminal number column, an email address column, a passcode column, a data download date / time column, and a download request count column. The exhibitor ID column stores the exhibitor ID uniquely specified in order to identify each exhibitor. The event ID column stores an event ID that uniquely identifies an event. The sub-event ID column stores the sub-event ID that uniquely identifies the sub-event in the event. The exhibitor name column remembers the exhibitor's name. The number of available terminals column stores the number of mobile terminals 2 that can be lent to the exhibitor.

The email address column stores the exhibitor's email address. The passcode column stores the passcode for authentication when the visitor data is downloaded. The data download date / time column stores the date / time information when the visitor data was downloaded. The download request count column stores the number of times the visitor data is requested to be downloaded according to the exhibitor's access information. The access information will be described later.

FIG. 7 is an explanatory diagram showing an example of the record layout of the terminal monitoring DB 175. The terminal monitoring DB 175 includes a terminal ID column, a terminal name column, a last application login date / time column, a last read date / time column, a status column, and an exhibitor ID column. The terminal ID column stores the ID of the mobile terminal 2 uniquely specified in order to identify each mobile terminal 2 to be monitored. The terminal name column stores the name of the mobile terminal 2 to be monitored. The last application login date / time column stores the date / time information that the mobile terminal 2 to be monitored last logged in (connected) to the server 1.

The last read date / time column stores the date / time information at which the communication state of the mobile terminal 2 was last read. The status column stores the communication status with the mobile terminal 2 to be monitored. In the present embodiment, the status of "online", "offline" or "stopped" is stored as the communication status. In "online", the server 1 is in a communicable state with the mobile terminal 2. “Offline” means that the server 1 cannot communicate with the mobile terminal 2. "Stop" is a state in which the communication function of the mobile terminal 2 is stopped from the server 1. The exhibitor ID column stores the exhibitor ID that identifies the exhibitor.

The storage form of each DB described above is an example, and other storage forms may be used as long as the relationship between the data is maintained.

FIG. 8 is a block diagram showing a configuration example of the mobile terminal 2. The mobile terminal 2 includes a control unit 21, a storage unit 22, a communication unit 23, an input unit 24, a display unit 25, a clock unit 26, a photographing unit 28, and a code reading unit 29. Each configuration is connected by bus B.

The control unit 21 includes an arithmetic processing unit such as a CPU and an MPU, and performs various information processing, control processing, and the like related to the mobile terminal 2 by reading and executing the control program 2P stored in the storage unit 22. Although the control unit 21 is described as a single processor in FIG. 8, it may be a multiprocessor. The storage unit 22 includes memory elements such as RAM and ROM, and stores the control program 2P or data required for the control unit 21 to execute the process. Further, the storage unit 22 temporarily stores data and the like necessary for the control unit 21 to execute the arithmetic processing.

The communication unit 23 is a communication module for performing processing related to communication using a wireless wireless WAN (Wide Area Network), and transmits / receives information to / from a server 1 or the like via a network N. The wireless WAN is a network for connecting to a business operator's communication network through a mobile phone line such as LTE (Long Term Evolution) which is a communication standard 4G (Generation) or 5G, and is provided to a contractor. The input unit 24 may be a keyboard, a mouse, or a touch panel integrated with the display unit 25. The display unit 25 is a liquid crystal display, an organic EL display, or the like, and displays various information according to the instructions of the control unit 21.

The clock unit 26 is a circuit that measures time, elapsed time, and the like, and gives a time measurement result to the control unit 21 in response to a request from the control unit 21. Further, the clock unit 26 provides a timer function. The timer function is a function of notifying the control unit 21 when a preset time has elapsed since the start instruction was given. Alternatively, the timer function is a function that responds to an inquiry from the control unit 21 whether or not a preset time has elapsed since the start was instructed.

The photographing unit 28 is an photographing device such as a CCD (Charge Coupled Device) camera or a CMOS (Complementary Metal Oxide Semiconductor) camera. The photographing unit 28 may be composed of a plurality of photographing devices. The photographing unit 28 may not be built in the mobile terminal 2 but may be directly connected to the mobile terminal 2 externally so that photography can be performed. The code reading unit 29 is a read-only module for reading a two-dimensional code, a one-dimensional code, or the like. The reading of the code will be described later.

FIG. 9 is a block diagram showing a configuration example of the exhibitor terminal 3. The exhibitor terminal 3 includes a control unit 31, a storage unit 32, a communication unit 33, an input unit 34, and a display unit 35. Each configuration is connected by bus B.

The control unit 31 includes an arithmetic processing unit such as a CPU and an MPU, and performs various information processing, control processing, and the like related to the exhibitor terminal 3 by reading and executing the control program 3P stored in the storage unit 32. Although the control unit 31 is described as a single processor in FIG. 9, it may be a multiprocessor. The storage unit 32 includes memory elements such as RAM and ROM, and stores the control program 3P or data required for the control unit 31 to execute the process. Further, the storage unit 32 temporarily stores data and the like necessary for the control unit 31 to execute the arithmetic processing.

The communication unit 33 is a communication module for performing processing related to communication, and transmits / receives information to / from the server 1 or the like via the network N. The input unit 34 may be a keyboard, a mouse, or a touch panel integrated with the display unit 35. The display unit 35 is a liquid crystal display, an organic EL display, or the like, and displays various information according to the instructions of the control unit 31.

FIG. 10 is an explanatory diagram illustrating the operation of the visitor management system. FIG. 10A is an explanatory diagram illustrating an operation of performing a login process of the mobile terminal 2 through the exhibitor code. First, the server 1 generates and transmits an exhibitor code for identifying an exhibitor to be read by a mobile terminal 2 lent to a plurality of exhibitors exhibiting at an event.

The exhibitor code is, for example, a two-dimensional code, a one-dimensional code, or the like. The two-dimensional code is a display type code that has information in the horizontal direction and the vertical direction, as opposed to the one-dimensional code that has information only in the horizontal direction. Typical two-dimensional codes are, for example, QR code (registered trademark), DataMatrix (registered trademark) or VeriCode (registered trademark). The one-dimensional code is, for example, a bar code. In the present embodiment, as an example, a two-dimensional code will be read.

Further, when a plurality of mobile terminals 2 are lent to the exhibitor, an individual exhibitor code may be issued to each mobile terminal 2, or a common exhibitor code may be issued among the plurality of mobile terminals 2. May be issued.

Specifically, the server 1 acquires the exhibitor ID of the exhibitor to whom the two-dimensional code is issued from the exhibitor DB 174 based on the event ID. The server 1 uses a two-dimensional code generation library to generate an exhibitor code that describes an exhibitor ID and an event ID. As the items to be embedded in the exhibitor code, any item may be set according to the actual needs. For example, the exhibitor ID, the exhibitor name, and the event ID are described in the exhibitor code.

The server 1 sends, for example, an e-mail to send the generated exhibitor code to the exhibitor terminal 3. The exhibitor terminal 3 receives the e-mail sent from the server 1 and displays the exhibitor code. It should be noted that the process is not limited to the process of sending and receiving the exhibitor code by e-mail. For example, the server 1 outputs the generated exhibitor code to the exhibitor's page in the application for the exhibitor. The exhibitor terminal 3 may log in to the application by the exhibitor and display the exhibitor code output on the exhibitor's page. The exhibitor code may be mailed directly to the exhibitor.

Next, the mobile terminal 2 logs in to the server 1 through the exhibitor code. Specifically, the mobile terminal 2 reads the exhibitor ID and the event ID from the exhibitor code, and transmits the read exhibitor ID and the event ID and the mobile terminal ID to the server 1. The server 1 determines whether or not login is possible based on the exhibitor ID and the event ID transmitted from the mobile terminal 2.

Specifically, the server 1 collates the received exhibitor ID and event ID with the exhibitor ID and event ID stored in the exhibitor DB 174. When the server 1 determines that the two match, the server 1 acquires the login possible period from the event DB 171 based on the received event ID. When the server 1 determines that the current date and time is within the login possible period, the server 1 acquires the number of available mobile terminals from the exhibitor DB 174 based on the received exhibitor ID and event ID. The server 1 totals the number of logged-in mobile terminals 2 from the online state of the monitored terminal stored in the terminal monitoring DB 175, and the total number of logged-in mobile terminals 2 exceeds the number of available mobile terminals. Determine if it is. When the server 1 determines that the number of logged-in mobile terminals 2 does not exceed the number of available mobile terminals, it determines that login is possible.

When the server 1 determines that login is possible, the server 1 stores the terminal ID, the terminal name, the login date / time, the reading date / time, the communication status, and the exhibitor ID as one record in the terminal monitoring DB 175. The server 1 transmits the reception screen of the visitor to the mobile terminal 2. The mobile terminal 2 receives the reception screen of the visitor transmitted from the server 1 and displays the received reception screen.

FIG. 10B is an explanatory diagram illustrating an operation of outputting visitor data in response to an exhibitor's download request. After logging in to the server 1 through the exhibitor code, the mobile terminal 2 reads the visitor identification information from the visitor code issued to the visitors who came to the event. The visitor code is, for example, a two-dimensional code, a one-dimensional code, or the like, similar to the exhibitor code. The visitor identification information is, for example, a visitor ID for identifying a visitor. The mobile terminal 2 transmits the read visitor ID and the mobile terminal ID to the server 1.

The server 1 receives the visitor ID and the mobile terminal ID transmitted from the mobile terminal 2, and acquires the exhibitor ID from the terminal monitoring DB 175 based on the received mobile terminal ID. The server 1 stores the mobile terminal ID, the reading date and time, and the visitor ID as one record in the download data DB 172 in association with the acquired exhibitor ID.

When the request code and the read ID are described in the visitor code or another dedicated two-dimensional code, the mobile terminal 2 uses the request code and the read ID read from the code as a server together with the visitor ID and the mobile terminal ID. Send to 1. The server 1 stores the mobile terminal ID, the reading date and time, the visitor ID, the request code, and the read ID as one record in the download data DB 172 in association with the exhibitor ID. Since the request code and read ID are not essential transmission items, they can be omitted.

The server 1 creates the exhibitor's access information for downloading the visitor data before or during the exhibition and sends it to the exhibitor terminal 3. The access information includes, for example, a URL (Uniform Resource Locator) for accessing a download-only site, a URL for reissuing a passcode, a passcode for authentication, and the like. The access information may be sent to the exhibitor by e-mail, or may be sent to the exhibitor via the app for the exhibitor. Furthermore, the access information printed out on paper may be mailed directly to the exhibitor.

The exhibitor terminal 3 receives the access information transmitted from the server 1. When the exhibitor terminal 3 accepts the touch (click) operation of the link of the URL described in the access information by the exhibitor, the exhibitor terminal 3 acquires and acquires the download page posted on the download-only site specified by the URL. Display the downloaded page. When the exhibitor terminal 3 accepts the input of the exhibitor's e-mail address and the authentication passcode, the exhibitor terminal 3 transmits the accepted exhibitor's e-mail address and the authentication passcode to the server 1.

The server 1 receives the e-mail address and passcode transmitted from the exhibitor terminal 3. The server 1 determines whether or not it is possible to download the visitor data based on the received e-mail address and passcode. Specifically, the server 1 acquires the exhibitor ID, the event ID, and the number of download requests from the exhibitor DB 174 based on the received e-mail address and passcode.

The server 1 acquires a downloadable period from the event DB 171 based on the acquired event ID. When the server 1 determines that it is within the downloadable period, the server 1 acquires a predetermined number of times (threshold value) stored in advance in the storage unit 12 or the large-capacity storage unit 17. For example, if the visitor data can be downloaded only once as a security measure, the threshold value is set to "1".

When the server 1 determines that the number of acquired download requests exceeds the predetermined number of times, the server 1 responds to the request for reissuing the passcode based on the URL for reissuing the passcode, and obtains access information different from the previously issued access information. Retransmit (reissue) to the exhibitor terminal 3. The reissued access information includes the URL for accessing the download-only site (similar to the previously issued URL), the passcode reissue URL (similar to the previously issued URL), and the new authentication path. Includes code etc. In the case of initial issuance and reissue of access information, the server 1 updates the number of download requests stored in the exhibitor DB 174 to the initial value (not downloaded: 0).

When the server 1 determines that the number of download requests does not exceed the predetermined number of times, the server 1 acquires the visitor data from the download data DB 172 and the visitor DB 173 based on the exhibitor ID and the visitor ID. The visitor data includes the first and last name of the visitor, the attributes of the visitor (for example, VIP member, customer purchasing product A, etc.), the name and department of the company to which the visitor belongs, and the like. The server 1 writes the acquired visitor data in a CSV (comma-separated values) format file. The server 1 transmits the written CSV file to the exhibitor terminal 3.

The exhibitor terminal 3 receives the CSV file transmitted from the server 1 and displays the received CSV file. The server 1 may write the visitor data in a PDF (Portable Document Format) format file and transmit the visitor data, or the visitor data itself may be directly transmitted to the exhibitor terminal 3. Furthermore, the visitor data may be written in a file of EXCEL (registered trademark) such as XLS or XLSX which is an extension.

FIG. 11 is a flowchart showing a processing procedure when the login processing of the mobile terminal 2 is performed through the exhibitor code. The control unit 11 of the server 1 acquires the exhibitor ID from the exhibitor DB 174 based on the event ID, and generates an exhibitor code describing the exhibitor ID and the event ID by using the two-dimensional code generation library. (Step S101). The control unit 11 transmits the generated exhibitor code to the exhibitor terminal 3 by e-mail via the communication unit 13 (step S102).

The control unit 21 of the mobile terminal 2 reads the exhibitor code issued to the exhibitor via the photographing unit 28 or the code reading unit 29 (step S201). The control unit 21 acquires the exhibitor ID and the event ID from the read exhibitor code (step S202). The control unit 21 transmits the acquired exhibitor ID and event ID and the mobile terminal ID to the server 1 by the communication unit 23 (step S203). The control unit 11 of the server 1 receives the exhibitor ID, the event ID, and the mobile terminal ID transmitted from the mobile terminal 2 by the communication unit 13 (step S103).

The control unit 11 collates the received exhibitor ID and event ID with the exhibitor ID and event ID stored in the exhibitor DB 174, and determines whether or not they match (step S104). When the control unit 11 determines that the two do not match (NO in step S104), the control unit 11 transmits an error screen to the mobile terminal 2 by the communication unit 13 (step S105). The control unit 21 of the mobile terminal 2 receives the error screen transmitted from the server 1 by the communication unit 23 (step S204), and displays the received error screen by the display unit 25 (step S205).

When the control unit 11 determines that they match (YES in step S104), the control unit 11 determines whether or not the current date and time is within the loginable period (step S106). When the control unit 11 determines that the current date and time is outside the loginable period (NO in step S106), the control unit 11 proceeds to the process of step S105.

When the control unit 11 determines that the current date and time is within the loginable period (YES in step S106), the control unit 11 determines whether or not the number of logged-in mobile terminals 2 exceeds the number of available mobile terminals. (Step S107). Specifically, the control unit 11 acquires the number of available mobile terminals from the exhibitor DB 174 based on the received exhibitor ID and event ID. The control unit 11 totals the number of logged-in mobile terminals 2 from the online state of the monitored terminal stored in the terminal monitoring DB 175, and the total number of logged-in mobile terminals 2 and the number of available mobile terminals 2. And compare.

When the control unit 11 determines that the number of logged-in mobile terminals 2 exceeds the number of available mobile terminals (YES in step S107), the control unit 11 transitions to the process of step S105. When the control unit 11 determines that the number of logged-in mobile terminals 2 does not exceed the number of available mobile terminals (NO in step S107), the terminal ID, terminal name, login date and time, reading date and time, communication status, and The exhibitor ID is stored in the terminal monitoring DB 175 as one record (step S108). The control unit 11 transmits the reception screen of the visitor to the mobile terminal 2 by the communication unit 13 (step S109). The control unit 21 of the mobile terminal 2 receives the reception screen of the visitor transmitted from the server 1 by the communication unit 23 (step S206), and displays the received reception screen by the display unit 25 (step S207).

12 and 13 are flowcharts showing a processing procedure when outputting visitor data. After the login process of the mobile terminal 2 is performed through the exhibitor code, the control unit 21 of the mobile terminal 2 inputs the visitor code of the visitor who came to the event via the shooting unit 28 or the code reading unit 29. Read (step S211). The control unit 21 acquires a visitor ID from the read visitor code (step S212). The control unit 21 transmits the acquired visitor ID and mobile terminal ID to the server 1 by the communication unit 23 (step S213).

The control unit 11 of the server 1 receives the visitor ID and the mobile terminal ID transmitted from the mobile terminal 2 by the communication unit 13 (step S111), and the exhibitor ID is transmitted from the terminal monitoring DB 175 based on the received mobile terminal ID. Acquire (step S112). The control unit 11 stores the mobile terminal ID, the reading date and time, and the visitor ID as one record in the download data DB 172 in association with the acquired exhibitor ID (step S113). The control unit 11 determines whether or not the predetermined date and time when the exhibitor's access information for downloading the visitor data can be transmitted to the exhibitor terminal 3 has been reached (step S114). The predetermined date and time may be, for example, two weeks before the event date and time (exhibition date and time) stored in the event DB 171 or one day or more before the event date and time. Furthermore, the predetermined date and time may be, for example, after the designated time of the date (for example, 10:00 AM). The predetermined date and time may be stored in the storage unit 12 in advance, for example. In this embodiment, it is determined whether or not the exhibitor's access information for downloading the visitor data has reached a predetermined date and time that can be transmitted to the exhibitor terminal 3, but the determination process ( The configuration of step S114) is not essential.

When the control unit 11 determines that the predetermined date and time has not been reached (NO in step S114), the control unit 11 stands by. When the control unit 11 determines that the predetermined date and time has been reached (YES in step S114), the control unit 11 creates the exhibitor's access information for downloading the visitor data (step S115). The access information includes a URL for accessing the download-only site, a password for reissuing a passcode, a passcode for authentication, and the like. The control unit 11 transmits the created access information to the exhibitor terminal 3 by e-mail via the communication unit 13 (step S116). The control unit 11 updates the number of download requests stored in the exhibitor DB 174 to the initial value (not downloaded: 0), and updates the authentication passcode stored in the exhibitor DB 174 to the issued passcode. (Step S117).

The control unit 31 of the exhibitor terminal 3 receives the access information transmitted from the server 1 by the communication unit 33 (step S311). The control unit 31 accepts the touch operation of the URL link described in the access information by the exhibitor by the input unit 34 (step S312). The control unit 31 acquires the download page posted on the download-only site specified by the URL by the communication unit 33 (step S313).

The control unit 31 displays the acquired download page on the display unit 35 (step S314). The control unit 31 accepts the input of the exhibitor's e-mail address and the passcode for authentication by the input unit 34 (step S315), and the control unit 31 accepts the exhibitor's e-mail address and the passcode for authentication in the communication unit. It is transmitted to the server 1 by 33 (step S316).

The control unit 11 of the server 1 receives the e-mail address and passcode transmitted from the exhibitor terminal 3 by the communication unit 13 (step S118). The control unit 11 compares the received e-mail address and passcode with the e-mail address and passcode stored in the exhibitor DB 174. If the control unit 11 determines that the two do not match, the control unit 11 returns to the process of step S118. When the control unit 11 determines that the two match, the control unit 11 acquires the exhibitor ID and the event ID from the exhibitor DB 174 based on the e-mail address and the passcode.

The control unit 11 acquires a downloadable period from the event DB 171 based on the acquired event ID, and determines whether or not the downloadable period is within the downloadable period (step S119). When the control unit 11 determines that it is out of the downloadable period (NO in step S119), the control unit 11 ends the process. The control unit 11 may send a message including the fact that it is out of the downloadable period to the exhibitor terminal 3 by the communication unit 13.

When the control unit 11 determines that it is within the downloadable period (YES in step S119), the control unit 11 acquires a predetermined number of times stored in advance in the storage unit 12 or the large capacity storage unit 17 (step S120). The control unit 11 determines whether or not the number of download requests exceeds a predetermined number (step S121). Specifically, the control unit 11 acquires the number of download requests from the download data DB 172 based on the exhibitor ID. The control unit 11 compares the acquired number of download requests with the predetermined number of times.

When the control unit 11 determines that the number of acquired download requests exceeds a predetermined number (YES in step S121), the control unit 11 returns to the process of step S115 and recreates the access information including the new passcode. When the control unit 11 determines that the number of acquired download requests does not exceed the predetermined number (NO in step S121), the control unit 11 determines the download data DB 172 and the visitor DB 173 based on the visitor ID and the exhibitor ID. Visitor data is acquired from (step S122).

The control unit 11 writes the acquired visitor data in a CSV format file (step S123). The control unit 11 transmits the written CSV file to the exhibitor terminal 3 by the communication unit 13 (step S124). The control unit 31 of the exhibitor terminal 3 receives the CSV file transmitted from the server 1 by the communication unit 33 (step S317), and displays the received CSV file by the display unit 35 (step S318).

FIG. 14 is an explanatory diagram showing an example of a screen for displaying an exhibitor code on the exhibitor terminal 3. FIG. 14A is an explanatory diagram showing an example of a screen displaying an exhibitor code transmitted by e-mail. The server 1 uses a two-dimensional code generation library to generate an exhibitor code that describes an exhibitor ID and an event ID. The server 1 sends the generated exhibitor code to the exhibitor terminal 3 by e-mail. The exhibitor terminal 3 receives the e-mail including the exhibitor code transmitted from the server 1, and displays the exhibitor code on the screen using the e-mail software.

FIG. 14B is an explanatory diagram showing an example of an exhibitor code display screen for exhibitors via an application. The server 1 outputs the generated exhibitor code to the exhibitor's page in the application for exhibitors. The exhibitor terminal 3 logs in to the application by the exhibitor and displays the exhibitor code output on the exhibitor's page on the screen.

FIG. 15 is an explanatory diagram showing an example of a screen for reading the exhibitor code by the mobile terminal 2. The screen includes a keyboard switching button 11a and a scan button 11b. The keyboard switching button 11a is a button for switching to a keyboard capable of directly inputting information for exhibitor authentication (for example, exhibitor ID, password, etc.) instead of reading the two-dimensional code. When the mobile terminal 2 receives the touch operation of the keyboard switching button 11a, the mobile terminal 2 calls the keyboard and displays it on the screen.

The scan button 11b is a button for reading the exhibitor code. When the mobile terminal 2 accepts the touch operation of the scan button 11b, the mobile terminal 2 activates the photographing unit 28 or the code reading unit 29. The mobile terminal 2 acquires the exhibitor ID and the event ID for login authentication from the exhibitor code via the photographing unit 28 or the code reading unit 29. The mobile terminal 2 transmits the acquired exhibitor ID and event ID to the server 1.

FIG. 16 is an explanatory diagram showing an example of a visitor data download screen. FIG. 16A is an explanatory diagram showing an example of a screen for displaying the access information notified to the exhibitor. The server 1 creates the exhibitor's access information for downloading the visitor data and sends it to the exhibitor terminal 3. The access information includes, for example, a URL for accessing a download-only site, a passcode for authentication, a URL for reissuing a passcode, a URL for browsing a manual, and the like.

The exhibitor terminal 3 receives and displays the access information transmitted from the server 1. When the exhibitor terminal 3 accepts the touch operation of the link of the URL described in the access information by the exhibitor, the exhibitor terminal 3 acquires the download page posted on the download-only site specified by the URL, and the acquired download page. (FIG. 16B) is displayed.

FIG. 16B is an explanatory diagram showing an example of a screen that accepts the input of the exhibitor's e-mail address and the passcode for authentication. The screen includes an email address input field 12a, a passcode input field 12b, and a download start button 12c. The e-mail address input field 12a is a text field that accepts the input of the e-mail address. The passcode input field 12b is a text field that accepts the input of the passcode. The download start button 12c is a button for downloading visitor data.

When the exhibitor terminal 3 accepts the touch operation of the download start button 12c, the exhibitor terminal 3 transmits the exhibitor's e-mail address entered in the e-mail address input field 12a and the passcode entered in the passcode input field 12b to the server 1. The server 1 determines whether or not it is possible to download the visitor data based on the e-mail address and the passcode transmitted from the exhibitor terminal 3.

When the server 1 determines that it is possible to download the visitor data, the server 1 acquires the visitor data from the download data DB 172 and the visitor DB 173 based on the exhibitor ID and the visitor ID. The server 1 writes the acquired visitor data in a CSV format file, and transmits the written CSV file to the exhibitor terminal 3. The exhibitor terminal 3 receives the CSV file transmitted from the server 1 and displays the received CSV file on the screen.

Exhibitor codes can be issued for each type of event (exhibition booth, seminar, etc.). For example, when the code for the first exhibitor for the exhibit booth and the code for the second exhibitor for the seminar are issued, after accepting the login of the mobile terminal 2 through the code for the first exhibitor, the code for the exhibit booth is used. Visitor data can be downloaded. In addition, after accepting the login of the mobile terminal 2 through the code for the second exhibitor, the visitor data for the seminar can be downloaded.

By issuing an exhibitor code for each event type, for example, when an exhibitor exhibits at both an exhibition booth and a seminar, visitor data can be output for each event type. Since the process of issuing the exhibitor code and the process of downloading the visitor data for each event type are the same as the above-mentioned processes, the description thereof will be omitted.

According to this embodiment, it is possible to acquire visitor data in real time without waiting for the delivery date.

According to this embodiment, since the maximum number of download requests is set, when the maximum number of download requests is reached, new access information is reissued to the exhibitor to improve the security level.

(Embodiment 2)
The second embodiment relates to a form of outputting visitor data based on items to be downloaded selected from a plurality of items of visitor data. The description of the contents overlapping with the first embodiment will be omitted.

FIG. 17 is a block diagram showing a configuration example of the server 1 of the second embodiment. The contents overlapping with FIG. 2 are designated by the same reference numerals and the description thereof will be omitted. The download setting DB 176 is stored in the large-capacity storage unit 17. The download setting DB 176 stores information about the item to be downloaded.

FIG. 18 is an explanatory diagram showing an example of the record layout of the download setting DB 176. The download setting DB 176 includes an exhibitor ID column, a default item name column, a setting item name column, a permutation column, and an option column. The exhibitor ID column stores the exhibitor ID that identifies the exhibitor. The default item name column stores the default item name of the item to be downloaded. The setting item name column stores the names of the items to be downloaded set by the exhibitor. The sort permutation stores the sort order of the items to be downloaded. The option column stores option information for the item to be downloaded. The option information is, for example, "display items to be downloaded in double quotes".

Visitor data has multiple items. Visitor data includes visitor ID, visitor's first and last name, visitor's first and last name, furigana of the company to which the visitor belongs, company name's furigana, department, exhibitor ID, mobile terminal ID lent to the exhibitor, request code. , Read ID, reading date of visitor code, etc. When the exhibitor selects an item to be downloaded from a plurality of items of the visitor data, the server 1 acquires the visitor data based on the selected item to be downloaded and outputs it to the exhibitor terminal 3.

Next, a process of outputting visitor data based on the items to be downloaded will be described. The exhibitor terminal 3 accepts the selection of the item to be downloaded from the plurality of items of the visitor data by the exhibitor. The exhibitor terminal 3 transmits the exhibitor ID, the selected download target item, and the setting information related to the target item to the server 1. The setting information includes, for example, the order of the target items, the name of the setting item for display, the option for the target item, and the like.

The server 1 receives the exhibitor ID, the item to be downloaded, and the setting information related to the target item transmitted from the exhibitor terminal 3. The server 1 stores the received download target item and the setting information related to the target item in the download setting DB 176 in association with the exhibitor ID. Specifically, the server 1 stores the default item name, the setting item name, the order, and the option as one record in the download setting DB 176 in association with the exhibitor ID.

When the server 1 receives the visitor data download request from the exhibitor terminal 3, the server 1 acquires the visitor data based on the set items to be downloaded and outputs the visitor data to the exhibitor terminal 3. Specifically, the server 1 receives the exhibitor's e-mail address and the authentication passcode from the exhibitor terminal 3, and based on the received exhibitor's e-mail address and the authentication passcode, the server 1 is used from the exhibitor DB 174. Obtain an exhibitor ID. The server 1 acquires the download target item set by the exhibitor from the download setting DB 176 based on the acquired exhibitor ID.

The server 1 acquires the corresponding download target item from the download data DB 172 and the visitor DB 173 based on the acquired download target item. The server 1 writes the acquired items to be downloaded into, for example, a CSV format file, and transmits the written CSV file to the exhibitor terminal 3. The exhibitor terminal 3 receives the CSV file transmitted from the server 1 and displays the received CSV file.

FIG. 19 is a flowchart showing a processing procedure when accepting the selection of the item to be downloaded. The control unit 31 of the exhibitor terminal 3 accepts the selection of the item to be downloaded from the plurality of items of the visitor data via the input unit 34 (step S331). The control unit 31 transmits the exhibitor ID, the selected download target item, and the setting information (arrangement order, setting item name, option, etc.) related to the item to the server 1 by the communication unit 33 (step S332).

The control unit 11 of the server 1 receives the exhibitor ID, the item to be downloaded, and the setting information related to the item transmitted from the exhibitor terminal 3 (step S131). The control unit 11 stores the received item to be downloaded and the setting information related to the item in the download setting DB 176 of the large-capacity storage unit 17 in association with the exhibitor ID (step S132).

FIG. 20 is a flowchart showing a processing procedure when outputting visitor data based on items to be downloaded. The contents overlapping with FIG. 13 are designated by the same reference numerals and the description thereof will be omitted. The control unit 11 of the server 1 executes step S121. When the control unit 11 determines that the number of download requests does not exceed the predetermined number (NO in step S121), the control unit 11 downloads and sets the download target item set by the exhibitor based on the exhibitor ID. Obtained from DB176 (step S141). The control unit 11 acquires the corresponding visitor data from the download data DB 172 and the visitor DB 173 based on the acquired items to be downloaded (step S142). The control unit 11 executes the process of step S123.

FIG. 21 is an explanatory diagram showing an example of a screen that accepts selection of items to be downloaded. The reception screen for selecting items to be downloaded includes an item selection check box 13a, an order input field 13b, a setting item name input field 13c, an option selection combo box 13d, and a save button 13e.

The item selection check box 13a is a check box that accepts selection of items to be downloaded. The checked items are output as items to be downloaded. The sort order input field 13b is a text field that accepts input of the sort order of items. The setting item name input field 13c is a text field that accepts the input of the item name. In addition to the default item name, any item name can be set by the exhibitor. The option selection combo box 13d is a combo box that accepts the setting of options for items. Options such as "enclose with (double quotation marks)", "full-width display", and "insert space" may be set in the option selection combo box 13d. The save button 13e is a button for saving the selected item to be downloaded.

The exhibitor terminal 3 acquires and displays the reception screen for selecting the item to be downloaded from the server 1. When the exhibitor terminal 3 accepts the touch operation of the save button 13e, the exhibitor ID, the target item selected by the item selection check box 13a, the arrangement order input by the arrangement order input field 13b, and the setting item name input. The setting item name input in the field 13c and the option selected in the option selection combo box 13d are transmitted to the server 1. The server 1 receives the download target item, the order corresponding to the target item, the item name, and the option transmitted from the exhibitor terminal 3. The server 1 stores the received download target item, the order corresponding to the target item, the item name, and the option in the download setting DB 176 in association with the exhibitor ID.

According to this embodiment, it is possible to create the report desired by the exhibitor by outputting the visitor data based on the items to be downloaded.

(Embodiment 3)
The third embodiment relates to a mode in which a synchronization process is performed based on a visitor ID when it is determined that the mobile terminal 2 cannot communicate with the server 1 according to the communication state of the network N. The description of the contents overlapping with the first and second embodiments will be omitted.

FIG. 22 is a block diagram showing a configuration example of the server 1 of the third embodiment. The contents overlapping with FIG. 2 are designated by the same reference numerals and the description thereof will be omitted. The visitor management DB 177 is stored in the large-capacity storage unit 17. The visitor management DB 177 stores management information for managing visitors who come to the event.

FIG. 23 is an explanatory diagram showing an example of the record layout of the visitor management DB 177. The visitor management DB 177 includes an event ID column, a visitor ID column, an application status column, a reception status column, and a sub-event ID column. The event ID column stores an event ID that identifies an event. The visitor ID column stores the visitor ID that identifies the visitor. The application status column stores the application status for event visits. For example, "applied", "cancelled", etc. are stored in the application status column. The reception status column stores the reception status of visitors. For example, "visited", "not accepted", etc. are stored in the reception status column. The sub-event ID column stores the sub-event ID that identifies the sub-event that the visitor has already visited.

FIG. 24 is a block diagram showing a configuration example of the mobile terminal 2 of the third embodiment. The contents overlapping with FIG. 8 are designated by the same reference numerals and the description thereof will be omitted. The mobile terminal 2 includes an auxiliary storage unit 27. The auxiliary storage unit 27 includes a recording medium such as an HDD or SSD. The auxiliary storage unit 27 includes a read history DB 271 and a visitor information display DB 272.

The reading history DB 271 stores the history information read from the visitor code that describes the visitor ID. The visitor information display DB 272 stores visitor information regarding visitors who come to the event. In this embodiment, the storage unit 22 and the auxiliary storage unit 27 may be configured as an integrated storage device. Further, the auxiliary storage unit 27 may be composed of a plurality of storage devices. Furthermore, the auxiliary storage unit 27 may be an external storage device connected to the mobile terminal 2.

FIG. 25 is an explanatory diagram showing an example of the record layout of the read history DB 271. The read history DB 271 includes an event ID column, a visitor ID column, a visit date / time column, and a status column. The event ID column stores an event ID that identifies an event. The visitor ID column stores the visitor ID that identifies the visitor. The visit date and time column stores information on the date and time when the visitor came to the event.

The status column stores the synchronization status of the visitor ID read from the visitor code. The synchronization state is represented by, for example, "transmitted", "not transmitted", "transmission error", and "reading error" states. The "sent" state is a synchronized state in which the visitor ID is transmitted to the server 1 and the visitor information is acquired. The "not transmitted" state is a state in which the visitor ID has not been transmitted because it is determined that communication is not possible. The "transmission error" state is a state in which transmission fails due to a line malfunction or the like during transmission. The "reading error" state is a state in which synchronization of the visitor ID fails due to reading an invalid visitor code.

FIG. 26 is an explanatory diagram showing an example of the record layout of the visitor information display DB 272. The visitor information display DB 272 includes a visitor ID column, a company name column, a visitor name column, a number of visitors column, and an attribute column. The visitor ID column stores the visitor ID that identifies the visitor. The company name column remembers the name of the company to which the visitor belongs. The visitor name column remembers the names of the visitors. The number of visitors column stores the number of visitors to the event according to one visitor ID. The attribute column stores attribute information according to the attributes of the visitors.

The storage form of each DB described above is an example, and other storage forms may be used as long as the relationship between the data is maintained.

FIG. 27 is a functional block diagram showing a processing operation for performing synchronization processing based on a visitor ID. The mobile terminal 2 reads the visitor code issued to the visitor. The visitor code is, for example, a two-dimensional code, a one-dimensional code, or the like. In the present embodiment, as an example, a two-dimensional code will be read. The mobile terminal 2 uses a two-dimensional code analysis library and acquires a visitor ID from the read two-dimensional code.

The mobile terminal 2 determines whether or not communication with the server 1 is possible according to the communication state of the network N. Specifically, the mobile terminal 2 uses a connection line acquisition API (Application Programming Interface), which is one of the functions of the control program 2P in the mobile terminal 2, to determine whether or not communication with the server 1 is possible. The connection line includes a public line network such as a communication standard 4G or 5G, or a wireless communication line such as Wi-Fi (registered trademark).

When the mobile terminal 2 determines that it can communicate with the server 1, it transmits the visitor ID read from the two-dimensional code to the server 1. The server 1 receives the visitor ID transmitted from the mobile terminal 2. The server 1 determines whether or not to allow the visitor based on the received visitor ID. Specifically, the server 1 acquires the reception status of the visitor from the visitor management DB 177 based on the visitor ID and the event ID. When the server 1 determines that the acquired reception status is "visited", it determines that the visit is a duplicate visit. When the server 1 determines that the acquired reception status is "not accepted", it determines that there is no duplicate visit.

If the server 1 determines that there are no duplicate visits, it determines that the visit is permitted. In this case, the server 1 acquires the visitor information from the visitor management DB 177 based on the visitor ID. The visitor information includes the name of the company to which the visitor belongs, the name of the visitor, the number of visitors, and the attributes of the visitor (for example, VIP member, product A purchasing customer, etc.). The server 1 updates the reception status column of the visitor management DB 177 to "visited" based on the event ID and the visitor ID. The server 1 transmits the acquired visitor information to the mobile terminal 2.

The mobile terminal 2 receives and displays the visitor information transmitted from the server 1. The mobile terminal 2 stores the reading history of the two-dimensional code in the reading history DB 271. Specifically, the mobile terminal 2 stores the event ID, the visitor ID, and the "sent" state as one record in the reading history DB 271 in association with the visit date and time (reading time when the visitor ID is read). .. The mobile terminal 2 stores the visitor information in the visitor information display DB 272. Specifically, the mobile terminal 2 stores the visitor ID, the company name, the visitor name, the number of visitors, and the attributes as one record in the visitor information display DB 272.

When the server 1 determines that the visit is duplicated, it determines that the visit is not permitted. In this case, the server 1 does not send the visitor information to the mobile terminal 2, and sends a reading error message to the mobile terminal 2 stating that the visit is not permitted. The mobile terminal 2 stores the reading history of the two-dimensional code in the reading history DB 271 with the transmission state of the visitor ID as a "reading error" in response to the reading error message transmitted from the server 1. Specifically, the mobile terminal 2 stores the event ID, the visitor ID, and the "reading error" state as one record in the reading history DB 271 in association with the visit date and time. By the above processing, the server 1 and the mobile terminal 2 synchronize based on the visitor ID, and share the determination result of whether or not to allow the visitor and the visitor information of the visitor who is allowed to visit.

On the other hand, when it is determined that the mobile terminal 2 cannot communicate with the server 1, the visitor ID (unsynchronized visitor ID) read from the two-dimensional code is stored in the reading history DB 271. Specifically, the mobile terminal 2 stores the event ID, the visitor ID, and the "not transmitted" state as one record in the read history DB 271 in association with the visit date and time.

In order to retransmit the untransmitted visitor ID to the server 1, the mobile terminal 2 activates a timer to calculate the elapsed time. When the mobile terminal 2 determines that a predetermined time interval (for example, 10 seconds) has elapsed, it redetermines whether or not communication with the server 1 is possible. When the mobile terminal 2 determines that it can communicate with the server 1, it retransmits the visitor ID to the server 1. Since the communication re-judgment process and the visitor ID retransmission process are the same as those described above, the description thereof will be omitted.

In this way, when the mobile terminal 2 cannot transmit the visitor ID to the server 1 due to deterioration of the communication state or the like, the mobile terminal 2 temporarily stores the visitor ID as "not transmitted", and as soon as the communication is restored, the visitor ID is temporarily stored. Resume transmission. As a result, even if the communication status is poor depending on the event venue, for example, the reception of visitors can be performed without delay.

28 and 29 are flowcharts showing a processing procedure for accepting visitors who have come to the event. The control unit 21 of the mobile terminal 2 reads the visitor code via the photographing unit 28 or the code reading unit 29 (step S251). The control unit 21 uses a two-dimensional code analysis library and acquires a visitor ID from the read visitor code (step S252).

The control unit 21 uses the connection line acquisition API to perform communication determination processing as to whether or not communication is possible with the server 1 via the network N (step S253). When the control unit 21 determines that communication with the server 1 is impossible (NO in step S253), the event ID, the visitor ID, and the "untransmitted" state are read as one record in association with the visit date and time. Store in DB271 (step S254). The control unit 21 determines whether or not a predetermined time interval (for example, 5 seconds) has elapsed by the clock unit 26 (step S255).

When the control unit 21 determines that the predetermined time interval has elapsed (YES in step S255), the control unit 21 returns to step S253 and redetermines whether or not communication with the server 1 is possible. When the control unit 21 determines that the predetermined time interval has not elapsed (NO in step S255), the control unit 21 waits for processing.

When the control unit 21 determines that communication with the server 1 is possible (YES in step S253), the control unit 21 transmits the visitor ID read from the visitor code to the server 1 by the communication unit 23 (step S256). The control unit 11 of the server 1 receives the visitor ID transmitted from the mobile terminal 2 via the communication unit 13 (step S151). The control unit 11 acquires the reception status of the visitor from the visitor management DB 177 based on the visitor ID and the event ID, and determines whether or not the visitor is a duplicate visit based on the acquired reception status ( Step S152).

When the control unit 11 determines that the visitors are duplicate visitors (YES in step S152), the control unit 11 transmits a reading error to the mobile terminal 2 by the communication unit 13 (step S153). The control unit 21 receives the reading error transmitted from the server 1 by the communication unit 23 (step S257). The control unit 21 stores the event ID, the visitor ID, and the "read error" state as one record in the read history DB 271 in association with the visit date and time according to the received read error (step S258).

When the control unit 11 determines that the visitors are not duplicate visitors (NO in step S152), the control unit 11 acquires the visitor information from the visitor management DB 177 based on the visitor ID (step S154). Visitor information includes the name of the company to which the visitor belongs, the name of the visitor, the number of visitors, and the attributes of the visitor. The control unit 11 updates the reception status column of the visitor management DB 177 to "visited" based on the event ID and the visitor ID (step S155). The control unit 11 transmits the acquired visitor information to the mobile terminal 2 via the communication unit 13 (step S156).

The control unit 21 receives the visitor information transmitted from the server 1 (step S259), and stores the read history and the received visitor information in the auxiliary storage unit 27 (step S260). Specifically, the control unit 21 stores the event ID, the visitor ID, and the "transmitted" state as one record in the read history DB 271 in association with the visit date and time. The control unit 21 stores the visitor ID, the company name, the visitor name, the number of visitors, and the attributes as one record in the visitor information display DB 272. The control unit 21 displays the visitor information on the display unit 25 (step S261).

FIG. 30 is an explanatory diagram showing an example of a reception screen for visitors. The reception screen includes an event name 20a, a number display column 20b, a visitor display column 20c, a button 20d, and an object 20e. The event name 20a is a display field for displaying the name of the event. The number display column 20b is a display column that displays the total number of visitor codes read (“total read”), the number of visitors (“visitors”), and the number of unsynchronized visitor IDs (“unsynchronized”). be. The visitor display field 20c is a display field for displaying visitor information.

The button 20d is a button for switching the reading mode. The reading mode includes a code reading mode for reading a visitor code and a direct input mode for directly inputting a visitor ID (attendance slip ID). The object 20e is a button or a text field for accepting a visitor ID. In the direct input mode, the object 20e is a text field for inputting a visitor ID. In the code reading mode, the object 20e changes to a button for reading a two-dimensional code.

The mobile terminal 2 totals the total number of read cases (the number of synchronized cases and the number of unsynchronized cases) from the read history DB 271 based on the event ID. The mobile terminal 2 totals the number of visitors from the visitor information display DB 272. Based on the event ID, the mobile terminal 2 totals the number of unsynchronized cases in the "untransmitted" or "error" state from the read history DB 271. The mobile terminal 2 displays the total number of read cases, the number of visitors, and the number of unsynchronized cases in the number display column 20b. In this embodiment, an example of displaying the total number of cases in the “unsent” state and the number of cases in the “error” state as the number of unsynchronized cases has been described, but the present invention is not limited to this. For example, the number of cases in the "unsent" state and the number of cases in the "error" state may be displayed respectively.

When the mobile terminal 2 accepts the touch operation of the button 20d, the mobile terminal 2 switches the reading mode. In the code reading mode, the mobile terminal 2 acquires the visitor ID from the visitor code read by the object 20e (button). In the direct input mode, the mobile terminal 2 directly accepts the input visitor ID from the object 20e (text field).

The mobile terminal 2 performs a communication determination process with the server 1. When the mobile terminal 2 determines that it can communicate with the server 1, it transmits the accepted visitor ID to the server 1. The server 1 receives the visitor ID transmitted from the mobile terminal 2 and determines whether or not to allow the visit based on the received visitor ID. When the server 1 determines that the visit is permitted, the server 1 acquires the visitor information including the visitor name, the number of visitors, the company, the attributes, etc. from the visitor management DB 177 based on the visitor ID.

The server 1 transmits the acquired visitor information to the mobile terminal 2. The mobile terminal 2 receives the visitor information transmitted from the server 1. The mobile terminal 2 stores the visitor date and time and the "sent" state as one record in the read history DB 271 based on the event ID and the visitor ID. The mobile terminal 2 displays the received visitor information in the visitor display field 20c.

FIG. 31 is an explanatory diagram showing an example of a reading history screen. Since the number display column 20b is the same as the number display column 20b in FIG. 30, the description thereof will be omitted. The reading history screen has a reading history display field 21a, a transmission icon 21b, an untransmitted icon 21c, a transmission error icon 21d, a reading error icon 21e, a cancel icon 21f, a transmission extraction button 21g, an untransmitted extraction button 21h, and a transmission error extraction button 21i. And a read error extraction button 21j.

The reading history display field 21a is a display field for displaying the reading history of the visitor code. The reading history displayed in the reading history display field 21a includes the reading time of the visitor ID and the visitor code. The transmission icon 21b is an icon indicating a “send” state. "Send" is a read history in which the visitor ID is successfully transmitted. The unsent icon 21c is an icon indicating a “not sent” state. “Not transmitted” indicates a state in which the visitor ID is read when the line is out of order, but is not transmitted to the server 1.

The transmission error icon 21d is an icon indicating a “transmission error” state. The "transmission error" represents a state in which transmission fails due to a line malfunction or the like during transmission. The reading error icon 21e is an icon indicating a “reading error” state. "Reading error" indicates that the visitor code is invalid. The cancel icon 21f is an icon indicating a "cancelled" state. "Cancel" indicates that the read visitor ID has been cancelled. Not limited to the various icons described above, any icon may be provided according to actual needs.

The transmission extraction button 21g is a button for displaying only the reading history in the “transmission” state. The untransmitted extraction button 21h is a button for displaying only the reading history in the “untransmitted” state. The transmission error extraction button 21i is a button for displaying only the reading history of the "transmission error" state. The reading error extraction button 21j is a button for displaying only the reading history in the "reading error" state. The mobile terminal 2 acquires the visitor ID, the visit date / time information, and the synchronization state from the read history DB 271 based on the event ID. The mobile terminal 2 displays the acquired visitor ID and visit date / time information in the reading history display field 21a. The mobile terminal 2 displays the corresponding icon based on the synchronization state corresponding to the acquired visitor ID.

When the mobile terminal 2 receives the touch operation of the transmission extraction button 21g, the mobile terminal 2 extracts the reading history corresponding to the "transmission" state from the reading history acquired from the reading history DB 271. When the mobile terminal 2 receives the touch operation of the untransmitted extraction button 21h, the mobile terminal 2 extracts the reading history corresponding to the "untransmitted" state from the reading history acquired from the reading history DB 271. When the mobile terminal 2 receives the touch operation of the transmission error extraction button 21i, the mobile terminal 2 extracts the reading history corresponding to the "transmission error" state from the reading history acquired from the reading history DB 271. When the mobile terminal 2 receives the touch operation of the reading error extraction button 21j, the mobile terminal 2 extracts the reading history corresponding to the "reading error" state from the reading history acquired from the reading history DB 271. The mobile terminal 2 displays the extracted reading history in the reading history display field 21a.

According to this embodiment, it is possible to accept visitors who come to the event by reading the visitor code that describes the visitor ID.

According to the present embodiment, when the mobile terminal 2 that accepts the visitor cannot connect to the server 1, the visitor ID can be stored and retransmitted after the communication status is restored.

According to this embodiment, it is possible to continue accepting visitors when the communication status of the network N is not good or when the system on the server 1 is down.

According to this embodiment, it is possible to accept visitors on the mobile terminal 2 without depending on the local environment.

The embodiments disclosed this time should be considered to be exemplary in all respects and not restrictive. The scope of the present invention is indicated by the scope of claims, not the above-mentioned meaning, and is intended to include all modifications within the meaning and scope equivalent to the scope of claims.

1 Management device (server)
11 Control unit 12 Storage unit 13 Communication unit 14 Input unit 15 Display unit 16 Reading unit 17 Large-capacity storage unit 171 Event DB
172 Download data DB
173 Visitor DB
174 Exhibitor DB
175 Terminal monitoring DB
176 Download setting DB
177 Visitor management DB
1a Portable storage medium 1b Semiconductor memory 1P Control program 2 Mobile terminal 21 Control unit 22 Storage unit 23 Communication unit 24 Input unit 25 Display unit 26 Clock unit 27 Auxiliary storage unit 271 Read history DB
272 Visitor information display DB
28 Imaging unit 29 Code reader 2P control program 3 Exhibitor terminal 31 Control unit 32 Storage unit 33 Communication unit 34 Input unit 35 Display unit 3P control program

Claims (9)

Send an exhibitor code that identifies the exhibitor for reading with a mobile terminal that is lent to multiple exhibitors exhibiting at the event.
Accepting the login of the mobile terminal through the exhibitor code,
Visitor data corresponding to the visitor code read by the mobile terminal after login is stored in association with the exhibitor.
Before or during the exhibition, each exhibitor will be notified of the exhibitor's access information for downloading the visitor data.
An information processing method that outputs visitor data in response to a request to download the visitor data based on the notified access information of the exhibitor. The information processing method according to claim 1, wherein when the number of visitor data download requests exceeds a predetermined number of times, access information different from the access information is re-notified. The visitor data has a plurality of items and has a plurality of items.
Accepts the selection of items to be downloaded from the above multiple items,
The information processing method according to claim 1 or 2, wherein the visitor data based on the selected item is output in response to the visitor data download request. The information processing method according to any one of claims 1 to 3, wherein when a plurality of mobile terminals are lent to the exhibitor, a common or individual exhibitor code is issued among the mobile terminals. The information processing method according to any one of claims 1 to 4, which stores visitor data including a visitor name and a company name to which the visitor belongs. The mobile terminal
Determine whether it is possible to communicate with the management device that manages visitor data,
When it is determined that communication is possible, the visitor identification information read from the visitor code is transmitted to the management device.
If it is determined that communication is not possible, the read visitor identification information is stored and stored.
It is re-determined whether or not it is possible to communicate with the management device at predetermined time intervals, and it is determined again.
The information processing method according to any one of claims 1 to 5, wherein when it is determined that communication is possible, the stored visitor identification information is transmitted to the management device. An information processing system having a mobile terminal and a management device for managing visitor data.
The management device is
The first transmitter that sends the exhibitor code that identifies the exhibitor for reading with a mobile terminal that is lent to multiple exhibitors exhibiting at the event.
A reception unit that accepts login of the mobile terminal through the exhibitor code transmitted by the first transmission unit, and a reception unit.
A storage unit that stores visitor data corresponding to the visitor code read by the mobile terminal after login in association with the exhibitor.
A notification unit that notifies each exhibitor of the exhibitor's access information for downloading the visitor data before or during the exhibition.
An information processing system including an output unit that outputs visitor data in response to a visitor data download request based on the exhibitor's access information notified by the notification unit. The first transmitter that sends the exhibitor code that identifies the exhibitor for reading with a mobile terminal that is lent to multiple exhibitors exhibiting at the event.
The reception section that accepts login of the mobile terminal through the exhibitor code, and
A storage unit that stores visitor data corresponding to the visitor code read by the mobile terminal after login in association with the exhibitor.
A notification unit that notifies each exhibitor of the exhibitor's access information for downloading the visitor data before or during the exhibition.
An information processing device including an output unit that outputs visitor data in response to a request to download the visitor data based on the notified access information of the exhibitor. Send an exhibitor code that identifies the exhibitor for reading with a mobile terminal that is lent to multiple exhibitors exhibiting at the event.
Accepting the login of the mobile terminal through the exhibitor code,
Visitor data corresponding to the visitor code read by the mobile terminal after login is stored in association with the exhibitor.
Before or during the exhibition, each exhibitor will be notified of the exhibitor's access information for downloading the visitor data.
A program that causes a computer to execute a process of outputting visitor data in response to a request to download the visitor data based on the notified access information of the exhibitor.

Images