JP2017162004A - Ticket medium processing terminal and processing system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a ticket medium processing terminal and a processing system for preventing unauthorized use.SOLUTION: According to an embodiment, a portable ticket medium processing terminal comprises a communication unit, a reading unit, a terminal authentication unit, a ticket information acquisition processing unit and a display unit. The communication unit communicates with a management server. The reading unit reads a code formed on a ticket medium. The terminal authentication unit decodes the code by using a terminal authentication key to perform terminal authentication. When the terminal authentication unit succeeds in terminal authentication, through the communication unit, the ticket information acquisition processing unit acquires ticket information from the management server using a ticket ID obtained by decoding the code. The display unit displays the ticket information.SELECTED DRAWING: Figure 1

Description

  Embodiments described herein relate generally to a ticket medium processing terminal and a processing system.

  In a processing system using a ticket medium on which a code such as a two-dimensional code is printed, a staff member reads the code using a terminal provided such as a window processing machine. In addition, a staff member may read a code using a handy type terminal from the viewpoint of convenience or cost. However, if a handy-type terminal is lost or stolen, there is a risk that it will be used illegally, such as illegally reading a code.

JP 2008-305068 A

  In order to solve the above problems, a ticket medium processing terminal and a processing system that prevent unauthorized use are provided.

  According to the embodiment, the portable ticket medium processing terminal includes a communication unit, a reading unit, a terminal authentication unit, a ticket information acquisition processing unit, and a display unit. The communication unit communicates with the management server. The reading unit reads a code formed on the ticket medium. The terminal authentication unit performs terminal authentication by decrypting the code using a terminal authentication key. When the terminal authentication by the terminal authentication unit is successful, the ticket information acquisition processing unit acquires the ticket information from the management server using the ticket ID obtained by decrypting the code through the communication unit. The display unit displays the ticket information.

FIG. 1 is a block diagram illustrating a configuration example of a processing system according to the embodiment. FIG. 2 is a block diagram illustrating a configuration example of the handy terminal according to the embodiment. FIG. 3 is a diagram illustrating a configuration example of the ticket medium according to the embodiment. FIG. 4 is a diagram illustrating a display example of the display unit of the handy terminal according to the embodiment. FIG. 5 is a diagram illustrating an operation example of the handy terminal according to the embodiment. FIG. 6 is a diagram illustrating a display example of the display unit of the handy terminal according to the embodiment. FIG. 7 is a diagram illustrating a display example of the display unit of the handy terminal according to the embodiment. FIG. 8 is a diagram illustrating an operation example of the handy terminal according to the embodiment. FIG. 9 is a diagram illustrating a display example of the display unit of the handy terminal according to the embodiment. FIG. 10 is a diagram illustrating a display example of the display unit of the handy terminal according to the embodiment. FIG. 11 is a diagram illustrating a display example of the display unit of the handy terminal according to the embodiment. FIG. 12 is a diagram illustrating a display example of the display unit of the handy terminal according to the embodiment. FIG. 13 is a diagram illustrating a display example of the display unit of the handy terminal according to the embodiment. FIG. 14 is a sequence diagram illustrating an operation example of the processing system according to the embodiment. FIG. 15 is a flowchart illustrating an operation example of the handy terminal according to the embodiment. FIG. 16 is a flowchart illustrating an operation example of the handy terminal according to the embodiment.

Hereinafter, embodiments will be described with reference to the drawings.
The processing system according to the embodiment processes a ticket medium on which a code such as a two-dimensional code is printed. The processing system presents ticket information of a ticket medium possessed by the user to an attendant or the like. In addition, the processing system performs a settlement process such as a transit settlement for the ticket medium possessed by the user.

  For example, the processing system processes a ticket printed with a code generated by coding ticket information as a ticket medium at a station or the like. Further, the processing system may process a ticket such as a theme park or a movie theater as a ticket medium. The use of the processing system and the contents of the ticket medium are not limited to a specific configuration.

  Here, the processing system will be described assuming a system that processes a ticket printed with a code generated by encoding ticket information at a station or the like.

FIG. 1 is a block diagram illustrating a configuration example of a processing system 1 according to the embodiment.
As shown in FIG. 1, the processing system 1 includes a management server 10, a handy terminal 20 (ticket medium processing terminal), a counter processor 30, a ticket medium 40, and the like. The management server 10 and the handy terminal 20 are communicably connected. The handy terminal 20 and the counter processor 30 are connected to be communicable. Further, the management server 10 and the counter processor 30 are connected so as to be communicable.

  The management server 10 manages ticket information of the ticket medium 40. The management server 10 includes a storage unit that stores ticket information for each ticket medium 40. The ticket information will be described later.

  The handy terminal 20 processes a ticket medium such as a ticket. The handy terminal 20 is a terminal device that can be carried (portable) by an attendant. The handy terminal 20 has a function of acquiring ticket information corresponding to a specific ticket medium 40 from the management server 10. The handy terminal 20 has a function of displaying or printing the ticket information as a function of presenting the ticket information. In addition, the handy terminal 20 performs a settlement process on the ticket medium 40 based on the ticket information and the like.

The window processing machine 30 performs window processing for ticket media. The counter processor 30 is a device that processes a ticket medium in response to an operation of a staff at a counter provided at a ticket gate or the like.
The ticket medium 40 is a ticket used as a boarding ticket or the like. The ticket medium 40 is a ticket medium possessed by a customer or the like. In the ticket medium 40, a code indicating a ticket ID, ticket information, and the like are recorded. For example, the ticket medium 40 is issued by a ticket issuing machine or the like.

Next, a configuration example of the handy terminal 20 will be described.
FIG. 2 is a block diagram illustrating a configuration example of the handy terminal 20.

  As shown in FIG. 2, the handy terminal 20 includes a CPU 21, a ROM 22, a RAM 23, an NVM 24, a communication unit 25, an operation unit 26, a display unit 27, a code reader 28 (reading unit), and the like as basic configurations. The CPU 21, the ROM 22, the RAM 23, the NVM 24, the communication unit 25, the operation unit 26, the display unit 27, and the code reader 28 are connected to each other via a data bus. In addition, the handy terminal 20 may include a configuration as necessary in addition to the configuration illustrated in FIG. 2 or may exclude a specific configuration. For example, the handy terminal 20 may include a printer that prints ticket information and the like.

  The CPU 21 has a function of controlling the operation of the entire handy terminal 20. The CPU 21 may include an internal cache and various interfaces. The CPU 21 implements various processes by executing a program (code) stored in advance in the internal memory, the ROM 22 or the NVM 24. The CPU 21 is, for example, a processor.

  Note that some of the various functions realized by the CPU 21 executing the program may be realized by a hardware circuit. In this case, the CPU 21 controls functions executed by the hardware circuit.

  The ROM 22 is a nonvolatile memory in which a control program and control data are stored in advance. The control program and control data stored in the ROM 22 are incorporated according to the specifications of the handy terminal 20 in advance. The ROM 22 stores, for example, a program (for example, BIOS) for controlling the circuit board of the handy terminal 20.

  The RAM 23 is a volatile memory. The RAM 23 temporarily stores data being processed by the CPU 21. The RAM 23 stores various application programs based on instructions from the CPU 21. The RAM 23 may store data necessary for executing the application program, an execution result of the application program, and the like.

  The NVM 24 is a nonvolatile memory that can write and rewrite data. The NVM 24 is configured by, for example, a hard disk, SSD, EEPROM (registered trademark), flash memory, or the like. The NVM 24 stores a control program, an application, and various data according to the usage application of the handy terminal 20.

  The NVM 24 includes a storage area 24a for storing clerk authentication information, a storage area 24b for storing usable range information, a storage area 24c for storing terminal authentication keys, a storage area 24d for storing unlocking encryption information, and the like.

  The communication unit 25 (wireless communication unit) is an interface for transmitting / receiving data to / from the management server 10 and the counter processor 30. For example, the communication unit 25 includes an interface for accessing the management server 10 through the Internet and the like, and an interface for physically connecting to the window processor 30.

  Various operation instructions are input to the operation unit 26 (authentication information acquisition unit) by the operator of the handy terminal 20. The operation unit 26 transmits operation instruction data input to the operator to the CPU 21. The operation unit 26 is, for example, a keyboard, a numeric keypad, and a touch panel.

  The display unit 27 is a display device that displays various information under the control of the CPU 21. The display unit 27 is, for example, a liquid crystal monitor. Here, it is assumed that the operation unit 26 includes a touch panel and the display unit 27 is formed integrally with the operation unit 26.

  The code reader 28 reads a code formed on the ticket medium 40. For example, the code reader 28 reads the code from the ticket medium 40 that is trapped at a predetermined distance and a predetermined angle from the code reader 28. Here, the code reader 28 reads a two-dimensional code as a code. The code reader 28 reads the code from the ticket medium 40 by, for example, irradiating the medium with light to obtain reflected light.

The code reader 28 reads a code using visible light or invisible light. For example, the code reader 28 reads the code by irradiating the ticket medium 40 with predetermined light to obtain reflected light. For example, the code reader 28 includes a camera and / or an illumination for reading a code.
The code reader 28 transmits the read code to the CPU 21.

Next, a configuration example of the ticket medium 40 will be described.
FIG. 3 shows a configuration example of the ticket medium 40.
As shown in FIG. 3, the ticket medium 40 includes character information 41 and a code 42.

  The character information 41 is a character string related to the ticket medium 40. For example, the character information 41 includes a character string indicating at least a part of data obtained by decoding the code 42. For example, the character information 41 includes ticket information or ticket ID.

  In the example illustrated in FIG. 3, the character information 41 includes a departure station, a boarding fee, a ticket ID, and a ticket issue date and time. The character information is not limited to a specific configuration.

  The code 42 is a code obtained by coding the ticket information and ticket ID. Here, the code 42 is a two-dimensional code. For example, the code 42 is a QR code (registered trademark) or the like.

  The ticket information indicates available boarding sections and the like. For example, the ticket information includes a departure / arrival station, a valid period, a valid section, and the like. The valid section is, for example, a terminal station or a boarding fee. The ticket information may include information such as a railway company. The ticket information is not limited to a specific configuration.

  The ticket ID is an ID that identifies the ticket medium 40. For example, ticket ID is comprised from a number, a character string, a symbol, or those combination. The ticket ID is determined by the ticket issuing machine when the ticket medium 40 is issued. For example, the ticket issuing machine sets a randomly generated character string or the like as the ticket ID. Further, the ticket issuing machine may acquire a character string or the like from a predetermined list and set the acquired character string or the like as a ticket ID. Further, the ticket issuing machine may obtain a ticket ID from the host device.

  For example, the ticket issuing machine determines the ticket ID when the ticket medium 40 is issued. The ticket issuing machine prints on the ticket medium 40 a code 42 indicating the determined ticket ID and ticket information.

Next, functions of the management server 10 will be described.
The management server 10 has a function of transmitting ticket information of the ticket medium 40 to the handy terminal 20 (ticket information transmission processing unit).
The ticket information is information regarding the ticket medium 40. The ticket information includes information indicating the use stage as information indicating the state of the ticket medium 40. The information indicating the use stage is, for example, information indicating that the ticket has been issued, entered, settled, or used. Further, the ticket information includes information (entrance information) indicating an entrance station where the ticket medium 40 has entered if the ticket medium 40 is in a stage after the entrance. The ticket information includes a settlement amount. For example, the management server 10 calculates the payment amount based on the ticket information of the ticket medium 40 and the like. Further, the management server 10 may specify a station where the ticket medium 40 exists based on a request from the handy terminal 20 and calculate a settlement amount. The ticket information is not limited to a specific configuration.

  The management server 10 manages the ticket information associated with the ticket ID of the ticket medium 40. The management server 10 includes a storage unit that stores ticket information for each ticket ID of the ticket medium 40. The management server 10 receives information associated with a ticket ID from station equipment such as a ticket issuing machine, an automatic ticket gate, or a window processing machine 30, and updates the ticket information as needed based on the received information.

  The management server 10 has a function of transmitting ticket information to the handy terminal 20. When receiving a request including a ticket ID from the handy terminal 20, the management server 10 transmits ticket information corresponding to the ticket ID to the handy terminal 20 as a response to the request. Note that the management server 10 may transmit ticket information to the handy terminal 20 through an external network such as the Internet.

Next, functions realized by the window processor 30 will be described.
The counter processor 30 has a function of communicating with the handy terminal 20. The counter processor 30 receives information related to the settlement process from the handy terminal 20 as a processing history, and accumulates the received information (processing history). Further, the counter processor 30 may transmit the accumulated processing history to the management server 10.

Next, functions realized by the handy terminal 20 will be described.
First, the CPU 21 of the handy terminal 20 has a function of performing staff authentication (operator authentication) of the handy terminal 20 using the staff authentication information stored in the storage area 24a (operator authentication unit).
The staff authentication information (operator authentication information) is information for authenticating the staff in comparison with the authentication information input by the staff. The staff authentication information is a password or the like.

  The CPU 21 acquires authentication information from the operation unit 26 or the like. For example, the CPU 21 receives an input of a password as authentication information. The CPU 21 compares the clerk authentication information with the input authentication information. When the CPU 21 determines that the two match, the CPU 21 determines that the clerk authentication is successful. If the CPU 21 determines that the two do not match, the CPU 21 determines that the clerk authentication has failed.

  Note that the CPU 21 may perform clerk authentication using biometric information. For example, the clerk authentication information is biometric information such as a fingerprint. The CPU 21 may acquire a fingerprint from an attendant through a predetermined acquisition unit and compare it with the attendant authentication information.

Further, the CPU 21 has a function of specifying the position of the handy terminal 20 (position specifying unit).
The CPU 21 specifies the position of the handy terminal 20 through the communication unit 25 or the like. Here, it is assumed that the communication unit 25 performs wireless communication with a communication device having a predetermined communication range. The CPU 21 specifies a position based on a communication device capable of wireless communication using the communication unit 25. For example, the CPU 21 acquires the ID of the connected access point or the ID of the paired Bluetooth (registered trademark) terminal through the communication unit 25 or the like.

Further, the CPU 21 has a function of performing position authentication of the handy terminal 20 using the usable range information stored in the storage area 24b (position authentication unit).
The usable range information indicates an area in which the handy terminal 20 can be used. The usable range may be set by a wireless device with which the handy terminal 20 can perform wireless communication. In this case, the usable range information is information indicating a wireless device capable of wireless communication, and is determined to be usable when the handy terminal 20 is paired or the ID of an access point determined to be usable when the handy terminal 20 is connected. It may be the ID of the Bluetooth terminal to be used.

  CPU21 determines whether the handy terminal 20 exists in the area | region which usable range information shows. That is, the CPU 21 determines whether or not the area indicated by the usable range information includes the position specified as the current position of the handy terminal 20. For example, the CPU 21 compares the ID of the access point or the Bluetooth terminal connected for communication with the ID of the access point or the Bluetooth terminal indicated by the usable range information. If both match, the CPU 21 determines that the handy terminal 20 is included in the area indicated by the usable range information. If the two do not match, the CPU 21 determines that the handy terminal 20 is not included in the area indicated by the usable range information.

  When the CPU 21 determines that the handy terminal 20 is in the area indicated by the usable range information, the CPU 21 determines that the location authentication has been successful. If the CPU 21 determines that there is no handy terminal 20 in the area indicated by the usable range information, the CPU 21 determines that the position authentication has failed.

Further, the CPU 21 has a function of performing terminal authentication of the handy terminal 20 using a terminal authentication key (terminal authentication unit).
The terminal authentication key is a key for obtaining code data from a code. That is, the terminal authentication key is a key for decrypting the code. The terminal authentication key is, for example, letters, numbers, or a combination thereof.

  For example, the CPU 21 acquires a code through the code reader 28. The CPU 21 decrypts the code using the terminal authentication key. When the CPU 21 succeeds in decoding the code, the CPU 21 determines that the terminal authentication of the handy terminal 20 is successful. Further, when the code 21 fails to decode the code, the CPU 21 determines that the terminal authentication of the handy terminal 20 has failed.

  In addition, the CPU 21 has a function of locking the handy terminal 20 when each authentication process of clerk authentication, position authentication, or terminal authentication fails for a predetermined number of times set (lock processing unit). For example, the CPU 21 prevents the handy terminal 20 from accepting an operation other than a predetermined operation.

  Further, the CPU 21 has a function of releasing the lock using the unlocking encryption information stored in the storage area 24d. For example, the CPU 21 receives an input of a terminal release key through the operation unit 26. The terminal release key is a key for decrypting the lock release encryption information.

  The CPU 21 decrypts the unlocking encryption information using the terminal authentication key. When the decryption is successful, the CPU 21 unlocks the handy terminal 20. Further, when the decryption fails, the CPU 21 continues to lock the handy terminal 20.

  Further, the CPU 21 has a function of reading the code 42 from the ticket medium 40 through the code reader 28. The CPU 21 reads the code 42 as follows.

  FIG. 4 shows a display example of the display unit 27 when the CPU 21 performs a reading operation.

  As shown in FIG. 4, the CPU 21 displays an icon 101 and an icon 102 on the display unit 27.

The icon 101 is an icon for displaying a processing history. The display of the processing history will be described later.
The icon 102 is an icon for instructing the start of the reading operation.
When the CPU 21 detects a touch on the icon 102 through the operation unit 26, the CPU 21 proceeds to a code 42 reading operation.

FIG. 5 shows an operation example of the handy terminal 20 when the operation shifts to the reading operation.
As shown in FIG. 5, when the CPU 21 shifts to the reading operation, a staff member who operates the handy terminal 20 puts the ticket medium 40 on the code reader 28 so that the code reader 28 can read the code 42.

FIG. 6 shows a display example of the display unit 27 when the clerk puts the ticket medium 40 on the code reader 28.
As shown in FIG. 6, the CPU 21 sets a display area 130 on the display unit 27.
The display area 130 displays an image taken by the code reader 28 camera. In the example shown in FIG. 6, the camera of the code reader 28 captures the vicinity of the code 42 of the ticket medium 40. The display area 130 displays the vicinity of the code 42 of the ticket medium 40.
The CPU 21 reads a code 42 in an image photographed by the camera of the code reader 28 (an image displayed in the display area 130).

In addition, when the CPU 21 reads the code 42 through the code reader 28, the CPU 21 has a function of decrypting the code 42 and acquiring a ticket ID and ticket information.
The CPU 21 decrypts the code 42 using the terminal authentication key. CPU21 acquires ticket ID and boarding ticket information from the code data acquired by decoding. Further, the CPU 21 displays the acquired ticket ID on the display unit 27.

FIG. 7 is a display example of the display unit 27 that displays the ticket ID.
As shown in FIG. 7, the CPU 21 displays the acquired ticket ID in a predetermined area of the display unit 27. Note that the CPU 21 may display ticket information.

Moreover, CPU21 has a function which acquires the ticket information of the ticket medium 40 from the management server 10 using ticket ID (ticket information acquisition process part).
FIG. 8 is a diagram illustrating an operation example in which the CPU 21 acquires ticket information.
As illustrated in FIG. 8, the CPU 21 transmits a request for ticket information including the acquired ticket ID to the management server 10 through the communication unit 25. Further, the CPU 21 receives ticket information corresponding to the acquired ticket ID from the management server 10 through the communication unit 25.

  Moreover, CPU21 has a function which displays the acquired ticket information on the display part 27 (display process part). The CPU 21 displays a character string indicating at least a part of the ticket information on the display unit 27. Here, the CPU 21 displays the ticket information in addition to the ticket information.

FIG. 9 shows a display example of the display unit 27 that displays ticket information.
As shown in FIG. 9, the CPU 21 displays the ticket information on the display unit 27. Here, the CPU 21 displays “entrance station”, “payment amount”, and “passover adjustment” at predetermined positions on the display unit 27 as ticket information. Here, the CPU 21 displays “section” at a predetermined position on the display unit 27 as the ticket information.

The “entrance station” is a ticket gate station where the ticket medium 40 is entered. The “settlement amount” is a shortage amount necessary for participation in the ticket medium 40. “Ride-over settlement” indicates whether the settlement amount has been settled. The “section” is an effective section of the ticket medium 40.
Further, the CPU 21 displays the icon 104 and the icon 105 on the display unit 27. The icon 104 is an icon for instructing the start of the checkout process. The icon 105 is an icon for instructing the end of the process without performing the settlement process.

Further, the CPU 21 has a function of performing a settlement process based on the ticket information (a settlement processing unit).
When the CPU 21 receives a touch on the icon 104 through the operation unit 26, the CPU 21 starts a settlement process.

FIG. 10 shows a display example of the display unit 27 during the settlement process.
As shown in FIG. 10, the CPU 21 displays a numeric keypad for inputting the amount received from the customer on the display unit 27. The CPU 21 receives an amount input through the numeric keypad.

  When the input amount exceeds the settlement amount, the CPU 21 completes the settlement process.

Further, the CPU 21 has a function of transmitting settlement information to the management server 10 through the communication unit 25 when the settlement process is completed (transmission processing unit). The settlement information stores a ticket ID and information indicating that the settlement process has been completed.
When the CPU 21 receives the payment management notification indicating that the payment is completed from the management server 10, the CPU 21 displays a message indicating that the payment is completed on the display unit 27.

FIG. 11 is a display example of the display unit 27 when the payment information transmission is completed.
As shown in FIG. 11, the CPU 21 displays a message indicating that the payment has been completed on the display unit 27. Further, the CPU 21 displays an icon 106 and an icon 107.

The icon 106 is an icon for starting the reading operation again.
The icon 107 is an icon for ending the process.
Note that the CPU 21 may display a change when the input amount exceeds the settlement amount.

  Further, when receiving the payment management notification indicating that the payment is completed from the management server 10, the CPU 21 stores information indicating that the payment is completed in the NVM 24 as a history.

The CPU 21 has a function of displaying a processing history on the display unit 27.
When the CPU 21 detects a touch on the icon 101 through the operation unit 26, the CPU 21 displays the processing history of the display unit 27. The processing history indicates past processing contents performed by the handy terminal 20. For example, the processing history includes a checkout process, an entrance process, or an entry process.

FIG. 12 shows a display example of the display unit 27 that displays the processing history.
As shown in FIG. 12, the CPU 21 displays on the display unit 27 a processing history such as a payment process, an entrance process, or an entry process performed in the past.

  Further, the CPU 21 has a function of transmitting a processing history (settlement history) relating to the settlement process to the window processor 30. For example, the CPU 21 accepts an operation for causing the window processing machine 30 to transmit a payment history through the operation unit 26. When the CPU 21 accepts the operation, the CPU 21 transmits the settlement history to the window processor 30 through the communication unit 25 or the like.

FIG. 13 shows a display example of the display unit 27 when the settlement history is transmitted.
As shown in FIG. 13, the CPU 21 displays a payment history to be transmitted.

Next, an operation example of the processing system 1 will be described.
FIG. 14 is a sequence diagram for explaining an operation example of the processing system 1.
Here, it is assumed that the attendant checks the ticket information by putting the ticket medium 40 on the handy terminal 20. In addition, the clerk shall perform the settlement process.

  First, the handy terminal 20 performs clerk authentication, location authentication, and terminal authentication (S11). Here, it is assumed that the handy terminal 20 has succeeded in staff authentication, position information, and terminal authentication. When the clerk authentication, the position information, and the terminal authentication are successful, the handy terminal 20 starts reading the code 42 of the ticket medium 40.

  When the handy terminal 20 performs clerk authentication, position authentication, and terminal authentication, the clerk tricks the handy terminal 20 into the ticket medium 40 (S12). The handy terminal 20 may include S12 as terminal authentication.

  When the attendant tricks the ticket medium 40, the handy terminal 20 reads the code 42 and displays the ticket ID on the display unit 27 (S13). After displaying the ticket ID, the handy terminal 20 transmits a ticket information request including the ticket ID to the management server 10 (S14).

  When receiving the request, the management server 10 extracts ticket information corresponding to the ticket ID included in the request. When the ticket information is extracted, the management server 10 transmits the extracted ticket information to the handy terminal 20 (S15).

  When the handy terminal 20 receives the ticket information, the handy terminal 20 displays the ticket information and the ticket information on the display unit 27 (S16). When the handy terminal 20 displays the ticket information and the ticket information, the clerk inputs an operation for performing a settlement process on the handy terminal 20 (S17).

When receiving the input of the operation for performing the settlement process, the handy terminal 20 transmits the settlement information to the management server 10 (S18).
The management server 10 receives the settlement information from the handy terminal 20. When the settlement information is received from the handy terminal 20, the management server 10 transmits a settlement completion notice to the handy terminal 20 (S19).

  When the handy terminal 20 receives the payment completion notification from the management server 10, the processing system 1 ends the operation.

Next, an operation example of the handy terminal 20 will be described.
15 and 16 are flowcharts for explaining an operation example of the handy terminal 20.

  First, the CPU 21 of the handy terminal 20 acquires authentication information through the operation unit 26 or the like (S21). When the authentication information is acquired, the CPU 21 performs clerk (operator) authentication by comparing the acquired authentication information with the authentication information of the operator permitted to operate. The CPU 21 determines whether the clerk (operator) authentication is successful as a result of the clerk authentication (S22).

  If it is determined that the staff authentication is successful (S22, YES), the CPU 21 specifies the position of the handy terminal 20 (S23). When the position of the handy terminal 20 is specified, the CPU 21 determines whether or not the position authentication is successful depending on whether or not the position of the specified handy terminal 20 is in the area indicated by the usable information (S24).

  If it is determined that the position authentication is successful (S24, YES), the CPU 21 acquires the code 42 of the ticket medium 40 through the code reader 28 (S25). When the code 42 is acquired, the CPU 21 decrypts the code 42 using the terminal authentication key (S26).

  When the code 42 is decrypted, the CPU 21 determines whether or not the terminal authentication is successful based on whether or not the decryption of the code 42 is successful (S27). If it determines with terminal authentication having been successful (S27, YES), CPU21 will display ticket ID on the display part 27 (S28).

  When the ticket ID is displayed on the display unit 27, the CPU 21 acquires ticket information corresponding to the ticket ID from the management server 10 through the communication unit 25 (S29). If ticket information is acquired, CPU21 will display ticket information and boarding ticket information on the display part 27 (S30).

  When the ticket information and the ticket information are displayed, the CPU 21 determines whether it is necessary to perform a settlement process (that is, whether there is a settlement amount and is not yet settled) (S31). If it is determined that the settlement process needs to be performed (S31, YES), the CPU 21 performs the settlement process (S32). When the payment process is performed, the CPU 21 transmits the payment information to the management server 10 through the communication unit 25 (S33).

  If it is determined that the clerk authentication is successful (S22, NO), if it is determined that the location authentication has failed (S24, NO), or if it is determined that the terminal authentication has failed (S27, NO), the CPU 21 fails. The number of failed authentications is counted up (S34).

  When counting up the number of failed authentication failures, the CPU 21 determines whether each number of failures exceeds a predetermined threshold (S35). If it is determined that the number of failures does not exceed the predetermined threshold (S35, NO), the CPU 21 returns to S21.

  If it is determined that the number of failures exceeds a predetermined threshold (S35, YES), the CPU 21 locks the handy terminal 20 (S36).

  When it is determined that it is not necessary to perform the settlement process (S31, NO), when the settlement information is transmitted (S33), or when the handy terminal 20 is locked (S36), the CPU 21 ends the operation.

  The CPU 21 may acquire a route from the predetermined station to the predetermined station from the management server 10 and display it on the display unit 27. Further, the CPU 21 may acquire the delay information of the vehicle operation from the management server 10 and display it on the display unit 27.

  The handy terminal configured as described above has a function of performing clerk authentication, and can be used when clerk authentication is successful. As a result, the handy terminal can be prevented from being illegally used by a person without usage authority in the case of theft or loss.

  In addition, the handy terminal has a function of performing position authentication, and can be used when the position authentication is successful. As a result, the handy terminal can be prevented from being used illegally outside the usable area.

  Further, the handy terminal has a function of performing terminal authentication, and becomes usable when the terminal authentication is successful. As a result, when the handy terminal is stolen or lost, the user can prevent the handy terminal from illegally reading the code by updating the key for encrypting the code.

  In addition, the handy terminal acquires a ticket ID from the ticket medium. The handy terminal acquires ticket information corresponding to the ticket ID from the management server. As a result, the handy terminal can present the state of the ticket medium to the staff.

In addition, the handy terminal has a function of transmitting settlement information to the management server. With this function, the handy terminal can provide information indicating the result of the settlement process to the management server.

Although several embodiments of the present invention have been described, these embodiments are presented by way of example and are not intended to limit the scope of the invention. These novel embodiments can be implemented in various other forms, and various omissions, replacements, and changes can be made without departing from the scope of the invention. These embodiments and modifications thereof are included in the scope and gist of the invention, and are included in the invention described in the claims and the equivalents thereof.

  DESCRIPTION OF SYMBOLS 1 ... Processing system, 10 ... Management server, 20 ... Handy terminal, 21 ... CPU, 24 ... NVM, 24a thru | or 24d ... Storage area, 25 ... Communication part, 26 ... Operation part, 27 ... Display part, 28 ... Code reader, 30 ... Window processing machine, 40 ... Ticket medium, 42 ... Code.

Claims (8)

A portable ticket medium processing terminal,
A communication unit that communicates with the management server;
A reading unit for reading a code formed on the ticket medium;
A terminal authentication unit that performs terminal authentication by decrypting the code using a terminal authentication key;
When terminal authentication by the terminal authentication unit is successful, through the communication unit, a ticket information acquisition processing unit that acquires ticket information from the management server using a ticket ID obtained by decrypting the code;
A display unit for displaying the ticket information;
A ticket medium processing terminal. An authentication information acquisition unit for acquiring authentication information;
An operator authentication unit that determines that the operator authentication is successful when the operator authentication information for authenticating the operator matches the authentication information acquired by the authentication information acquisition unit,
The ticket medium processing terminal according to claim 1. A position specifying unit for specifying the position of the ticket medium processing terminal;
A position authentication unit that determines that the position authentication is successful when the position specified by the position specifying unit is included in the usable range;
The ticket medium processing terminal according to claim 1 or 2. A wireless communication unit that wirelessly communicates with a communication device having a predetermined communication range,
The position specifying unit specifies a position based on a communication device capable of wireless communication using the wireless communication unit;
The ticket medium processing terminal according to claim 3. When the terminal authentication fails a predetermined number of times, a lock processing unit that locks the ticket medium processing terminal is provided.
The ticket medium processing terminal according to any one of claims 1 to 4. A settlement processing unit for performing a settlement process based on the ticket information;
Through the communication unit, a transmission processing unit that transmits settlement information indicating completion of the settlement process to the management server;
Comprising
The ticket medium processing terminal according to any one of claims 1 to 5. The code is a two-dimensional code;
The ticket medium processing terminal according to any one of claims 1 to 6. A processing system comprising a management server and a ticket medium processing terminal,
The management server
A ticket information transmission processing unit for transmitting ticket information of the ticket medium to the ticket medium processing terminal;
The ticket medium processing terminal
A communication unit that communicates with the management server;
A reading unit for reading a code formed on the ticket medium;
A terminal authentication unit that performs terminal authentication by decrypting the code using a terminal authentication key;
When terminal authentication by the terminal authentication unit is successful, through the communication unit, a ticket information acquisition processing unit that acquires ticket information from the management server using a ticket ID obtained by decrypting the code;
A display unit for displaying the ticket information;
Comprising
Processing system.