JP2005128660A - Push message sending system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a push message system that increases the participation rate of applicants to various events such as employment explanation meetings and interviews by companies. <P>SOLUTION: The push message sending system sends a push message to applicants to an event when preset push timing is reached. As to new applicants after arbitrarily set push timing (S50), the push message will be sent in the push time zone on the day following the application. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

  The present invention relates to a push message transmission system for reminding participation of an event when a person who has applied for participation in various events such as company briefing sessions, interviews, product exhibitions, etc. approaches the event date.

A schedule reminder system that calls attention by setting a computer system to send a message at a preset time has been proposed. For example, Japanese Patent Laid-Open No. 2001-350884 discloses an example of reminding the progress of a travel preparation schedule.
JP 2001-350884 A

  However, a reminder system (push message system) that improves the participation rate in the event itself is not introduced to the reservation participants of the event. In addition, when a service such as a remind system is performed on a web server, the load on the web server increases.

  Therefore, an object of the present invention is to provide a push message system that improves the participation rate of reservation persons in various events such as a company job briefing session and an interview.

  Another object of the present invention is to provide a push mail system with less load on the web server.

  In order to achieve the above object, the push message transmission system of the present invention is arbitrarily set in the push message transmission system for transmitting a push message to the event attendees when a preset push timing arrives. A push message is transmitted to a person who has made a new reservation after the push timing has elapsed, during the push time zone of the next day after the reservation processing is executed. Thereby, it becomes possible to maintain the push message function without increasing the load on the server device.

  The push message transmission system according to the present invention is a push message transmission system that transmits a push message to a reservation participant who has participated in an event when a preset push timing has arrived. When re-reservation is executed after canceling, this reservation person is excluded from the push message transmission processing target of the next day. This makes it possible to avoid duplicate push message transmissions.

  In addition, the push message transmission system of the present invention executes a new reservation in the push time zone in the push message transmission system that transmits a push message to a reservation participant who participates in an event when a preset push timing has arrived. When the actual push message transmission process for the reservation person is not yet processed, this reservation person is set as a push message transmission target person. As a result, it is possible to avoid as late as possible the delay when the remind period is started.

  By adopting the configuration of the present invention, it is possible to provide a push message transmission system that can efficiently improve the participation rate of the reservation person in various events without increasing the burden on the server device.

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

  FIG. 1 is an explanatory diagram for explaining the network environment of a web server that executes the push message system of the present invention. A user connects a user terminal device 11 such as a personal computer, a mobile phone, and a personal digital assistant (PDA) to the service provider 13 via a communication path such as a public line. The service provider 13 connects the user terminal device 11 to a high-speed network 14 such as the Internet. The client 12 connects the client terminal device 12 such as a personal computer to the high-speed network 14 via the service provider 13 or directly. A web server 15 is connected to the high-speed network 14 and provides a push message system service to the user terminal device 11 and the client device 12. Here, a case where employment information is provided by the web server 15 will be described as an example. That is, in the company information session and interview event push message system of the embodiment described later, a user is a student, a client is a company (company), and a web server is operated by a job information provider. .

  FIG. 2 schematically shows a configuration example of the web server 15. The web server 15 holds a communication device 151 that communicates with the network 14, a CPU (arithmetic processing unit) 152 that executes various service programs and provides job information services to users and clients, a program, processing data, and a database. A large-capacity memory 153, an input device 154 for instructing the CPU 152, a hard disk device 155 for storing a large amount of information in a nonvolatile manner, a display device 156 for displaying information on a screen, and the like. Since the memory 153 and the hard disk device 153 are equivalent hardware from the viewpoint of a storage device, the contents stored in the memory 153 can be stored in the hard disk device 153, or vice versa.

  FIG. 3 shows a database associated with the push message system held in memory 153. The company database holds general company information such as an ID for identifying a registered job-seeking company (client), the contents of a job offer, capital, head office address, and number of employees. The student (user) database holds an ID, a name, an address, a message address, a telephone number, school information, and the like for identifying a student who has registered for the purpose of providing employment information. The briefing session database holds data such as company briefing sessions and interview dates. Various template databases hold templates for various input screens on the web. The reservation / cancellation list holds a list of reservations so that each user can identify each briefing session when applying for a company event (such as a briefing session or interview). In addition, when a reservation is canceled later, a list of canceled users is retained so that each briefing session can be identified. The reminder completed list holds a list of users who have transmitted push messages for each briefing session described later. The reminder time data stores the time when the push message is transmitted to the reserved user set individually for each briefing session or the like. The reservation / cancellation list and the reminded list can be integrated as one list, and in the case of integration, a record is formed using, for example, a student ID or a company ID as a key. The record includes, for example, various cells such as a student ID item (company code / event code item) / event code item (student ID item) / reservation / cancellation flag item / reminder flag item. Furthermore, this integration can also be performed by forming a record in the company DB and student DB using each company ID and student ID as a key.

  FIG. 4 is a flowchart for explaining a user briefing session application. As shown in the figure, the user connects the user terminal 11 to the network and accesses the web server 15 in order to search for recruiting company information and apply for an event interview held by the company (U2). The web server 15 transmits the initial screen template of the home page to the user (S2). The user inputs an ID code on the screen displayed on the user terminal 11 and a code and password registered in advance in the password field, and transmits them to the web server 15 (U4). The web server 15 makes it possible to use the user's web service (search and browse for recruiting company information) (S4).

  When the user completes the search for job offer company information, for example, the user can obtain a screen as shown in FIG. Here, the user requests the display of the event information by clicking the “information session / event information” of the corresponding company on the screen shown in FIG. 5 (U6). The web server 15 transmits a briefing session application template to the user terminal 11 to display an input screen (S6). FIG. 6 shows an example of a briefing session application template. This template displays a briefing session code, a date and time of reception, a reception deadline, a reception status, a holding location, and the like described in advance by a client company as a client. The reception status (full or empty) is updated each time an application is made. The user fills in the template with necessary items and transmits it to the web server 15 (U8). The web server 15 displays the member information registered in advance by the user and the reservation contents described in the briefing session application template on the user terminal 11 and receives the contents as reservation application data when the user clicks a “send” icon ( S8). FIG. 7 shows an example of a transmission screen.

  The web server 15 registers the reservation application from each user in the reservation / cancel list of the database together with the code of each briefing session. It should be noted that the contents of items described in the user such as a questionnaire at the time of application vary depending on the client. When the user makes a reservation for participation in the briefing session, the web server 15 updates the list of reservation persons each time (S10).

  When a briefing session is reserved as shown in FIG. 8, a web message for accepting a reservation (guidance on the web screen) is transmitted from the company to the user. This screen shows a “cancel” icon for the reservation. When the user clicks the “cancel” icon, reservation cancellation information is transmitted to the web server 15, and the cancellation of the user's participation reservation to the corresponding briefing session is registered in the reservation / cancellation list.

  In this way, reservations (or cancellations for reservations) such as company briefings and interviews are performed. In addition, although the above process was demonstrated in the example which performs the search of company information after a user logs in, for example, a search and an inquiry of an event can be performed without logging in, and when logging in to participate in an event, login is performed. Prompt processing is also possible.

  Next, the auto push function of the web server 15 that automatically sends a reminder to the reserved user before the event interview will be described.

  As shown in FIG. 9, when the briefing is held on December 10, the auto push function transmits a remind message to the reservation person any number of days in advance, for example, seven days in advance. Encourage participation in events.

  FIG. 10 shows an example of a remind message. This reminder can also serve as a briefing reception sheet, and in this case, a barcode that facilitates the reception process can be displayed. The reminder displays the user registration number, name, briefing session code, host prefecture, date, time, and the like. The user can receive the reminder message via a mail box installed in the web server 15 or via general Internet mail.

  FIG. 11 shows an example of a template displayed on the screen of the client terminal 12 when the client company accesses the web server 15 from the client terminal 12 to set the auto push function.

  As shown in the figure, the client clicks on the reservation code of the scheduled briefing session displayed in the “Unset reservation code list” column to highlight it, and clicks the downward “arrow icon” As a result, it is moved to the “auto push transmission target reservation code list”. As a result, a reservation code (event code) to activate the auto push function is selected.

  Next, the client selects a template of a message to be transmitted by setting its ID in the “auto push transmission message” field. A plurality of templates preliminarily describing various messages are given an identification ID so that they can be selected and stored in the database. The client selects from the pull-down menu the number of days before the date of the event to be reminded in the “Period for Auto Push Transmission” column. For example, 7 days before to 1 day before can be set. Also, the time zone for transmission is selected from a pull-down menu. In the example shown in the figure, it is set to perform an over push (remind) between “13: 00 to 15:00” from “7 days before” to the day before the date of the event. Here, the transmission time is set in the time zone in consideration of the processing load of the web server 15. The web server 15 provides an auto push function to a plurality of clients, and provides other services, so the load is distributed on the time axis.

  The client can set an appropriate name for the auto push setting in the “auto push transmission setting name” field. After completing the setting, select “Active” for the Auto Push transmission setting in the “Operation status” column. When the “confirm content” icon is clicked, the auto push control means composed of software stored in the web server 15 sets the auto push transmission function to the operation state (operation flag on), and the auto push of the explanatory meeting as shown in FIG. A transmission setting list is displayed on the screen of the client device 12.

  Next, the operation of the auto push function controlled by the auto push control means of the web server 15 will be described with reference to the flowchart of FIG.

  The auto push control means of the web server 15 determines whether or not it is a processing time zone (for example, 13: 0 to 15:00) preset for each client (S50). If it is not the time allocated to the client (S50; NO), the remind process is not performed (S70).

  Further, the auto-push control means performs a remind process for the client assigned in the time zone (S50; YES70). The client's briefing session database is read, and a reservation code (event code) set to auto push is extracted (S52). It is determined whether or not the remind date of the briefing session corresponds to the current month and day (S54). For example, as shown in FIG. 9, when the briefing date is December 10 and the remind date is set to 7, December 3 corresponds to the remind execution date. If not, the process related to the reservation code is terminated (S54; NO), and the process proceeds to the process for another briefing session code (S70).

  When the current date is the remind execution date (S54; YES), the auto-push control means refers to the reservation / cancellation list and determines the reservation person of the reservation code (for example, T0001) to be held on December 10. Specify (S56; NO), and read out the reservation person corresponding to the reservation code (S58). Next, with reference to the reservation / cancellation list, it is confirmed that the reservation person is not canceled (cancellation flag item is valid) (S60). Next, it is confirmed with reference to the reminder completed list that the reservation person is not the person who has already sent the reminder (S62). The reservation person who has completed the confirmation is selected as a transmission target (S64), and the push message (reminder) described above (see FIG. 10) is assembled and transmitted (S66). The reservation person sets the reminder on the reminder completed list (reminder flag item is valid), and excludes it from the next reminder target (S68). This example corresponds to the (1) reservation pattern in FIG.

  The same processing is repeated for the reservation person of the same briefing session (reservation code) (S56 to S68). The process is repeated until the remind process described above is executed for all the reservation persons of the reservation persons corresponding to this reservation code. When the remind process is finished for the last reservation person (S56; YES), the remind process is finished (S70).

  In the reservation cancellation pattern of (2) cancellation in FIG. 9, since the user is registered in the reservation / cancellation list as a reservation canceler on December 1 (the cancel flag item is valid) (S60), The message transmission that is excluded and executed on December 3 is not performed (S64, S66).

  Generally, a push message is not transmitted after a preset push message transmission date and time has elapsed. However, the push message control means of the present invention can transmit a push message even after a preset push message transmission date and time has elapsed. That is, after the push message transmission date and time, transmission is attempted in a processing time zone (for example, 13: 0 to 15:00) preset for each client. In the case of (3) re-reservation in FIG. 9, after a reservation is made on November 3, a push message (reminder) is once received, then canceled on December 4, and the event canceled on December 5 is re-restarted. Make a reservation. In this case, since the message is transmitted on December 3, and the reminder flag item of the reminder completed list is valid (S62), the message is not transmitted again.

  In the case of (4) vacant reservation in FIG. 9, user B made a reservation for the explanatory meeting on December 3, but the reservation was not possible because the number of participants exceeded the planned number (FIG. 6). Equivalent to “full”. However, since user A canceled the reservation on December 4, it was possible to apply for a briefing session, and user B made a reservation on December 5. In this case, the auto-push control means pushes the push message from step S58 to S62 for a new reservation person from the date and time zone preset as the reminder time data until the day before the briefing session (event) date. Therefore, a push message is also transmitted to the user B between 13:00 and 15:00 on December 6.

  FIG. 14 illustrates a case where a user's reservation is entered in the time zone registered as the reminder time data after the client performs auto-push setting on the screen of FIG. When the set time zone is from 13:00 to 15:00 and the start of transmitting the push message related to this reservation is (at the start of the process of FIG. 13 for transmission) is 14:00, for example, from 13:00 to 14:00 (13:00 For the reservation 1 registered by 59 minutes), the auto push control means transmits a push message. However, the auto-push control means does not set the reminder process for the reservation 2 made after 14:00 on the current day, so it is not subject to the process for this day. Send.

It is explanatory drawing explaining the network to which the user terminal, the client terminal, and the web server were connected. It is a block diagram explaining the structural example of a server apparatus. It is explanatory drawing explaining the database constructed | assembled in memory. It is a flowchart explaining the reservation of the briefing session from a user terminal. It is explanatory drawing explaining the example of the display screen displayed on a user terminal. It is explanatory drawing explaining the example of a briefing session reservation template. It is explanatory drawing explaining the example of reservation entry information. It is explanatory drawing explaining the example of a reply message. It is explanatory drawing explaining the various reservation patterns in the remind period to the date of a briefing session. It is explanatory drawing explaining the example of a push message. It is explanatory drawing explaining the example of the auto push setting screen of a client. It is explanatory drawing explaining the example of the confirmation screen of an auto push setting. 4 is a flowchart for explaining a remind process by a server 15; It is explanatory drawing explaining the example when a reservation enters into a reminding process execution time slot | zone.

Explanation of symbols

11 User terminal device, 12 Client terminal device, 13 Service provider, 14 Network (Internet), 15 Server device

Claims (3)

In a push message transmission system that transmits a push message to a reservation participant of event participation when a preset push timing has arrived,
A push message transmission system, wherein a push message is transmitted to a person who makes a new reservation after elapse of an arbitrarily set push timing during a push time zone of the next day after the reservation processing is executed. In a push message transmission system that transmits a push message to a reservation participant of event participation when a preset push timing has arrived,
A push message transmission system characterized in that, when a reservation person who has received a push message cancels the same event again and executes re-reservation of the same event, this reservation person is excluded from the push message transmission processing target of the next day. In a push message transmission system that transmits a push message to a reservation participant of event participation when a preset push timing has arrived,
A push message transmission system in which, when an actual push message transmission process is unprocessed for a reservation person who has made a new reservation during the push time period, this reservation person is the target person of the push message transmission.

Images