Code processing system and code processing method

Abstract

A code processing system (100) is provided with an operating system (30) and a standby system (40). The operating system (30) and the standby system (40) are each configured so as to generate a multi-bit user code (12) when a code request from a user terminal (11) is received. The user code (12) includes a system code unique to a system (30, 40) that generates the user code (12) in a prescribed bit. The user code (12) generated by the working class system (30) is a working class code, and the user code (12) generated by the standby class system (40) is a standby class code. The code processing system (100) is configured so as to transmit, to a user terminal (11), either a working-class code or a standby-class code on the basis of error information in the working-class system (30).

Description

Technical Field

[0001] The present disclosure relates to a code processing system and a code processing method. Background Art

[0002] In recent years, electronic settlement services such as coded settlement have become increasingly common. Failures in the information systems that provide these services can significantly impact social life and reduce service reliability. To mitigate the impact of these information system failures, cluster systems are being utilized that include standby system servers, in addition to active system servers that operate normally, to replace active system servers in the event of failure.

[0003] For example, Patent Document 1 discloses a server switching method in which signs of hardware failure or software failure are collected and switching to a standby system server is performed as needed.

[0004] Prior art literature

[0005] Patent Literature

[0006] Patent Document 1: Japanese Patent Application Laid-Open No. 2016-224490 Summary of the Invention

[0007] Problems to be solved by the invention

[0008] In a code settlement service, user codes, such as barcodes or QR codes (registered trademark), are issued as identification information to identify the buyer and seller. For example, when the buyer displays the user code on their portable device and the seller reads the user code using a store terminal, the store terminal sends the read user code and the seller's identification code (store code) to the settlement system. The settlement system identifies the buyer and seller based on the received user code and store code and performs settlement processing between the two. Identification codes such as user codes are not limited to electronic settlements and are sometimes used to distribute coupons or as electronic receipts for entry management.

[0009] When multiple systems, such as active and standby systems, generate identification codes for the same purpose, the same identification code may be generated by multiple systems depending on the system switching situation. Furthermore, if multiple identification codes are circulated for what should be a single identification code, problems may arise in the settlement process.

[0010] An object of the present disclosure is to provide a code processing system and a code processing method capable of appropriately performing code processing even when a plurality of systems for generating identification codes are switched mutually.

[0011] Means for solving problems

[0012] A code processing system according to one embodiment of the present invention includes a working class system and a standby class system, wherein the working class system and the standby class system are each configured to generate a multi-bit identification code upon receiving a code request from a user terminal, wherein the identification code includes a system code inherent to the system generating the identification code in a prescribed bit, the identification code generated by the working class system is a working class code, and the identification code generated by the standby class system is a standby class code, and the code processing system is configured to send any one of the working class code and the standby class code to the user terminal based on error information in the working class system.

[0013] A code processing system in one embodiment of the present invention comprises a working system, one or more standby systems and a database, wherein the working system and the one or more standby systems are each configured to generate a multi-digit identification code upon receiving a code request from a user terminal, wherein the identification code includes, in a prescribed digit, a system code inherent to the working system and the one or more standby systems that generate the identification code, the database being configured to store a sending history of the identification codes generated by the working system and the one or more standby systems, and the code processing system being configured to generate a multi-digit identification code according to an error in the working system. Error information is received, and the identification code generated by any one of the working system and the one or more standby systems is sent to the user terminal, and is constructed as follows: when a code processing request containing the identification code is received, the code processing request is sent to the working system and the one or more standby systems that correspond to the system code contained in the identification code, and the working system and the one or more standby systems are each constructed as follows: when the code processing request is received, the identification code contained in the code processing request is checked against the identification code stored in the database.

[0014] One embodiment of the method disclosed herein is a code processing method in a code processing system, wherein the code processing system has a working type system and one or more standby type systems, wherein the working type system and the one or more standby type systems are each configured to generate a multi-bit identification code, and the identification code includes a system code inherent to the working type system and the one or more standby type systems in a specified bit, and the method includes the following processing: collecting error information in the working type system; receiving a code request from a user terminal; and sending the identification code generated by any one of the working type system and the one or more standby type systems to the user terminal based on the error information. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figure 1 It is a schematic diagram showing the structure of the code processing system according to the embodiment.

[0016] Figure 2 It is an explanation Figure 1 Flowchart of a code processing method executed by a code processing system.

[0017] Figure 3 Example error message.

[0018] Figure 4 This is a flowchart illustrating a method for switching systems based on error information. DETAILED DESCRIPTION

[0019] Below, refer to Figures 1 to 4 The present invention is not limited to these examples, and is intended to include all modifications within the meaning and scope of the claims, in addition to the contents indicated by the claims.

[0020] [Overview of Electronic Settlement Services]

[0021] Figure 1 The illustrated code processing system 100 is configured to generate identification codes as part of code processing associated with electronic settlement (hereinafter referred to as "code settlement"). A shopper, as an example of a user, can use a user terminal 11 to receive electronic settlement services. A settlement application for performing electronic settlement payments may also be installed on the user terminal 11. User terminal 11 may be, but is not limited to, a portable terminal such as a computer, a smartphone with a built-in camera, or a tablet.

[0022] The settlement application includes a computer program for causing the user terminal 11 to perform various operations. When the user activates the settlement application, a code display screen 15 is displayed on the user terminal 11. One or more identification codes 12, 13, and 14 are displayed on the code display screen 15. The identification codes 12, 13, and 14 displayed on the code display screen 15 are also referred to as user codes. User codes 12, 13, and 14 can be generated each time the settlement application is activated, can be regenerated by reloading the identification code (operating the reload button) or re-reading the code display screen 15, and can have a fixed validity period (e.g., 5 minutes).

[0023] Among the user codes 12, 13, and 14, the identification code 12 is a multi-digit string containing at least one of a number, a character, or a symbol. The number of digits in the string can be arbitrarily set. The identification codes 13 and 14 are two-dimensional codes. The two-dimensional codes 13 and 14 can be, but are not limited to, barcodes 13 or QR codes 14. The two-dimensional codes 13 and 14 are two-dimensional versions of the identification code 12. Therefore, when scanning the code display screen 15, even if the actual scan is of the two-dimensional code 13 or 14, it is referred to as "reading the user code 12."

[0024] The seller terminal 20 used by the merchant may include a code scanner 21, or may include a camera and a code reading application to scan the QR codes 13 and 14. The seller terminal 20 is pre-assigned with a store code 23, which serves as an identification code for identifying the seller. The store code 23 may also be a QR code. The QR code may be, but is not limited to, a barcode or a QR code. The user terminal 11 and the seller terminal 20 are examples of user terminals.

[0025] The seller terminal 20 may be installed in a store or mounted on a mobile object such as a taxi or a mobile sales vehicle. Each seller terminal 20 may be a POS (Point of Sales) cash register or a portable device such as a PC or tablet with a payment application installed.

[0026] Code settlement can be performed using either a store scanning method, in which the seller's terminal 20 scans the QR codes 13 and 14 displayed on the code display screen 15, or a user scanning method, in which the user terminal 11 scans the store code 23 presented by the seller. In the store scanning method, settlement processing is performed based on a settlement request sent from the seller's terminal 20 that accepts payment in electronic settlement (this is also referred to as the "first settlement process"). In the user scanning method, settlement processing is performed based on a settlement request sent from the user terminal 11 that makes payment in electronic settlement (this is also referred to as the "second settlement process").

[0027] Here, we will describe an overview of code payment using the store scanning method performed via the user terminal 11 and the seller terminal 20. Before payment, a payment screen 25 is displayed on the display 24 of the seller terminal 20. The payment amount is displayed on the payment screen 25. After the seller and user confirm the payment amount, the seller terminal 20 reads the user code 12. The read seller terminal 20 then executes the payment process.

[0028] When executing a payment process, the seller terminal 20 sends a settlement request including settlement information to the code processing system 100 via the network 29. The settlement information includes the user code 12, the store code 23, and the settlement amount. The settlement information may also include transaction information related to the settlement, such as information related to the purchased goods. After the settlement is completed, the settlement application of the user terminal 11 may also display a settlement completion screen (not shown) on the user terminal 11. The settlement completion screen may also include the seller's information, the payment date and time, and the settlement amount.

[0029] The network 29 includes, for example, the Internet, a WAN (Wide Area Network), a LAN (Local Area Network), a provider terminal, a wireless communication network, a wireless base station, a dedicated line, and the like. Figure 1 All combinations of the devices shown are capable of communicating with one another, and the network 29 may also partially comprise a local area network.

[0030] In the user scanning method, when the user reads the store code 23 via the user terminal 11, a payment screen (not shown) is displayed on the user terminal 11. When the user enters the payment amount on the payment screen and the payment process is executed, the user terminal 11 transmits a settlement request including settlement information to the code processing system 100 via the network 29. The settlement information includes the user code 12, the store code 23, and the settlement amount.

[0031] [Overview of the Code Processing System]

[0032] like Figure 1 As shown, the code processing system 100 is a cluster system comprising an active system 30 that operates normally and a standby system 40 that operates in the event of a failure in the active system 30. In addition to the first standby system 40, the code processing system 100 may further comprise a second standby system 50 that operates in the event of a failure in either system 30 or 40.

[0033] Systems 30, 40, and 50 are each configured to execute the generation of an identification code (first code processing) and verification of the identification code (second code processing) as code processing for code settlement. The first code processing includes the transmission of the generated identification code. The second code processing may also include processing related to the service using the identification code (e.g., settlement processing). Systems 30, 40, and 50 in this example are each configured to execute the generation and transmission of an identification code (user code 12) upon receiving a code request as a first code processing request. Furthermore, systems 30, 40, and 50 are each configured to execute the verification of the identification code and the settlement processing upon receiving a settlement request as a second code processing request.

[0034] Systems 30, 40, and 50 may provide the same services, or their service contents may differ. The following describes an example in which the standby systems 40 and 50 are configured to provide a portion of the services that can be provided by the active system 30. For example, in addition to code settlement using user scanning and store scanning methods (the first and second settlement processes), the active system 30 can also perform code settlement when the seller terminal 20 is a vending machine or self-service checkout machine. In contrast, the standby systems 40 and 50 can perform code settlement using store scanning (the first settlement process), but do not support code settlement using user scanning, vending machines, or self-service checkout machines.

[0035] Regardless of the type of code settlement, the system 30, 40, 50 generates a user code 12 based on the code request sent from the user terminal 11 and sends it to the user terminal 11. The settlement application is configured to generate two-dimensional codes 13 and 14 based on the user code 12. The user code 12 is, for example, a 16-digit positive integer sequence. A predetermined position in the 16-digit sequence (in this example, the 7th position, in Figure 1 The code (one or more digits, in this example, one digit) of the system 30, 40, or 50 that generates the code differs. The seventh digit of the code unique to each system 30, 40, or 50 is referred to as a system code.

[0036] In this example, the system code used to identify the active system 30 is "8" or "9," the system code used to identify the first standby system 40 is "7," and the system code used to identify the second standby system 50 is "6." That is, the seventh digit of the user code 12 generated by the active system 30 is "8" or "9," the seventh digit of the user code 12 generated by the first standby system 40 is "7," and the seventh digit of the user code 12 generated by the second standby system 50 is "6." System codes are not limited to numbers and may also be characters or symbols.

[0037] The user code 12 generated by the work-type system 30 is referred to as a "work-type code" or a "normal time code." The user code 12 generated by the first standby-type system 40 is referred to as a "first standby-type code" or a "first emergency time code." The user code 12 generated by the second standby-type system 50 is referred to as a "second standby-type code" or a "second emergency time code." The "first standby-type code" and the "second standby-type code" are also collectively referred to as "standby-type codes," and the "first emergency time code" and the "second emergency time code" are also collectively referred to as "emergency time codes."

[0038] System 100 may also include a switcher 101 configured to switch between systems 30, 40, and 50. Alternatively, system 100 may include a first switcher for switching from system 30 to system 40 and a second switcher for switching from system 40 to system 50. The state in which active system 30 is operating is referred to as "normal mode," and the state in which standby systems 40 and 50 are operating is referred to as "emergency mode."

[0039] System 100 may also include a user router 102 and a seller router 103. Upon receiving a code request from user terminal 11, user router 102 is configured to transmit the code request to any of systems 30, 40, and 50. The switch 101 determines which system 30, 40, or 50 the user router 102 transmits the code request to.

[0040] Upon receiving a settlement request including the user code 12 transmitted from the user terminal 11, the user router 102 transmits the settlement request to the systems 30, 40, and 50 corresponding to the system codes included in the user code 12. Specifically, if the user code 12 is a normal time code, the user router 102 transmits the settlement request to the system 30; if the user code 12 is a first emergency time code, the user router 102 transmits the settlement request to the system 40; and if the user code 12 is a second emergency time code, the user router 102 transmits the settlement request to the system 50.

[0041] When the seller router 103 receives a settlement request including the user code 12 transmitted from the seller terminal 20, it transmits the settlement request to the systems 30, 40, and 50 corresponding to the system codes included in the user code 12. Specifically, similarly to the user router 102, if the user code 12 is a normal time code, the seller router 103 transmits the settlement request to the system 30; if the user code 12 is a first emergency time code, the seller router 103 transmits the settlement request to the system 40; and if the user code 12 is a second emergency time code, the seller router 103 transmits the settlement request to the system 50.

[0042] System 100 may also include an error information collector 104 for collecting error information for each of systems 30, 40, and 50. Alternatively, system 100 may include a first error information collector, a second error information collector, and a third error information collector for collecting error information for each of systems 30, 40, and 50. Error information collector 104 may also be a chatbot configured to receive error information transmitted from devices within system 100.

[0043] During the operation of each system 30, 40, 50, the error information collector 104 collects error information of the corresponding system 30, 40, 50. The error information includes the number of errors in various processes executed in each system 30, 40, 50, the error content, and the date and time when the error occurred.

[0044] Switcher 101 is configured to control switching of systems 30, 40, and 50 based on error information collected by error information collector 104. Switching of systems 30, 40, and 50 is performed by switcher 101 changing the destination of code requests received by user router 102 from user terminal 11. For example, if an error that satisfies a predetermined switching condition occurs in working system 30, switcher 101 changes the destination of the code request sent to user router 102 from working system 30 to first standby system 40. System 100 may also include a history database 105 that stores a history of switching of systems 30, 40, and 50.

[0045] [Overview of the Electronic Settlement System]

[0046] The code processing system 100 of this example is configured to provide electronic settlement services and is therefore also referred to as an electronic settlement system. The following describes the configuration of the systems 30, 40, and 50 that implement the various functions of the electronic settlement system 100.

[0047] The systems 30, 40, and 50 may also include databases 34, 44, and 54, respectively. The first standby system 40 may also include a first data synchronization device 45 for synchronizing the working system database 34 with the first standby system database 44. In the event of a switch between the systems 30 and 40, the first data synchronization device 45 may also synchronize the working system database 34 with the first standby system database 44. The second standby system 50 may also include a second data synchronization device 55 for synchronizing the first standby system database 44 with the second standby system database 54. In the event of a switch between the systems 40 and 50, the second data synchronization device 55 may also synchronize the first standby system database 44 with the second standby system database 54.

[0048] Each of the databases 34, 44, and 54 may also include a user database, a seller database, a code database, and a settlement database. The user database stores information (hereinafter referred to as "user data") about multiple users (purchasers) registered with the settlement service. The seller database stores various data related to multiple sellers or stores participating in the electronic settlement service. The code database stores the transmission history of user codes 12 generated by each of the systems 30, 40, and 50. The settlement database stores the history of multiple settlement processes.

[0049] Each user data item may also include the corresponding user's name, user identifier, address, one or more payment information, payment method settings, and electronic settlement service usage history. The one or more payment information items may include, for example, a credit card number, a debit bank account, and electronic currency registration information. The payment method settings include information related to the payment method (e.g., a credit card number) that the user has pre-set as the default payment method for code settlement. Examples of payment methods include, but are not limited to, credit cards, bank accounts, electronic currency, or points. Each user data item may also include information about the user terminal 11 used by the user.

[0050] Information related to sellers includes, but is not limited to, the seller's name, seller identification information (including store identification information), location, transaction details, areas of business, and information about the seller's terminal 20. The seller database may also include payment history. This information includes, for example, the name of the store where the payment was made, the purchaser, the date and time of the payment, the transaction type, and the payment amount.

[0051] The transmission history of the user code 12 includes the recipient (user or user terminal 11 information) and the transmission date and time of each user code 12. The settlement process history may also include, for example, the user identification information and seller identification information (store identification information) used in each settlement process, the user code 12 used in the settlement, store information, the settlement date and time, the settlement location, the settlement amount, the payment method, the transaction details, and the deduction status after the settlement process.

[0052] The working type system 30 and the standby type systems 40 and 50 are each configured so that, when a second code processing request (settlement request) including a user code 12 is received, a comparison process is performed between the user code 12 included in the second code processing request and the sent user code 12 stored in the code database as the second code processing.

[0053] The work system 30 includes an authenticator 36, a configuration device 37, a code generator 38, and a payment processing device 39. Upon receiving a code request from the user terminal 11, the authenticator 36 references the user database to authenticate the user who sent the code request. The configuration device 37 references the work system database 34 for the authenticated user and retrieves the payment method set by the user.

[0054] The code generating device 38 is configured to generate the user code 12 of the corresponding user in response to the code request. The settlement processing device 39 is configured to perform settlement processing when receiving a settlement request from the user terminal 11 or the seller terminal 20.

[0055] Similar to the working system 30, the first standby system 40 includes an authentication device 46, a setting device 47, a code generator 48, and a settlement processing device 49. The functions of the authentication device 46, the setting device 47, the code generator 48, and the settlement processing device 49 are the same as those of the setting device 37, the code generator 38, and the settlement processing device 39, respectively. However, the settlement processing device 49 performs settlement processing when receiving a settlement request from the seller terminal 20. However, it does not support settlement requests from the user terminal 11 (the second settlement process).

[0056] Similar to the working system 30, the second standby system 50 also includes an authentication device 56, a setting device 57, a code generator 58, and a settlement processing device 59. The functions of the authentication device 56, the setting device 57, the code generator 58, and the settlement processing device 59 are the same as those of the setting device 37, the code generator 38, and the settlement processing device 39, respectively. However, the settlement processing device 59 performs settlement processing when receiving a settlement request from the seller terminal 20. However, it does not support settlement requests from the user terminal 11 (the second settlement process).

[0057] [Code settlement method]

[0058] Reference Figure 2 The code settlement method in systems 30, 40, and 50 will be described using the example of code settlement performed by a work system 30 using a store scanning method. Below, steps S11 to S13 represent the processing of the user terminal 11, steps S21 to S23 represent the processing of the seller terminal 20, and steps S31 to S39 represent the processing of the system 100.

[0059] First, in step S11, the user operates the user terminal 11 to activate the settlement application. This causes the settlement application to send a code request containing user data to the system 100. Then, in step S31, the user router 102 receives the code request from the user terminal 11. In this example, the user router 102 sends the code request to the authentication device 36 of the work-type system 30.

[0060] In step S32, the authentication device 36 performs user authentication by comparing the user data included in the code request (first code processing request) with the user data (registration data) stored in the user database. If the user data matches the registration data, the authentication device 36 completes user authentication. If the user data does not match the registration data, or if authentication cannot be performed due to an inappropriate authentication request, the authentication device 36 sends an error message. If an error occurs, the authentication device 36 may retry the authentication process.

[0061] In step S33, the setting device 37 references the database 34 to retrieve the payment method set by the corresponding user. If the payment method cannot be retrieved, or if the payment information request is inappropriate and the payment method cannot be retrieved, the setting device 37 sends an error message. If an error occurs, the setting device 37 may also retry the payment method retrieval process.

[0062] In step S34, the code generation device 38 generates a user code 12 (first code process). Then, in step S35, the work-type system 30 transmits the generated user code 12 to the user terminal 11. If the code generation process cannot be performed in step S34, the code generation device 38 transmits an error message. If an error occurs, the code generation device 38 may re-perform the generation process.

[0063] When the user terminal 11 receives the user code 12 in step S12 , the payment application generates the two-dimensional codes 13 and 14 and then displays the code display screen 15 including the user codes 12 , 13 , and 14 on the user terminal 11 .

[0064] The seller then inputs the settlement amount into the seller terminal 20. Then, in step S21, the seller terminal 20 reads the user code 12 on the code display screen 15. In the following step S22, the seller performs payment processing. As a result, the seller terminal 20 sends a settlement request (second code processing request) to the system 100. The settlement request includes payment information. The payment information includes at least the user code 12, the store code 23, and the payment amount obtained from the user terminal 11. In addition, the store code 23 scanned by the user terminal 11 in the user scanning method of settlement and the store code 23 included in the payment information in the store scanning method of settlement can also be different codes.

[0065] In step S36, the seller router 103 receives the settlement request. In this example, the user code 12 is a normal time code, so the seller router 103 sends the settlement request to the authentication device 36 of the work system 30.

[0066] In step S37, the authentication device 36 compares the user code 12 included in the settlement request with the previously sent user code 12 stored in the code database. Thus, the work-type system 30 is configured to perform a user code 12 comparison process by referring to the database 34 upon receiving a second code processing request including a user code 12. If the two user codes 12 match, the authentication device 36 completes the comparison process. If the two user codes 12 do not match, the authentication device 36 transmits an error message. If an error occurs, the authentication device 36 may also perform the comparison process again.

[0067] In step S38, the settlement processing device 39 performs settlement processing based on the payment information. If the settlement processing cannot be performed in step S38, the settlement processing device 39 sends an error message. If an error occurs, the settlement processing device 39 may also perform the settlement processing again.

[0068] When the settlement process is complete, in step S39, the work system 30 transmits the settlement result as settlement completion information to the user terminal 11 and the seller terminal 20. In this way, in step S13, the settlement application displays a settlement completion screen including the settlement completion information on the user terminal 11. Furthermore, in step S23, the settlement completion screen including the settlement completion information is displayed on the display 24 of the seller terminal 20.

[0069] In the case of code settlement using the user scanning method, similar to the store scanning method described above, when the settlement application on the user terminal 11 is activated in step S11, a code request is sent to the system 30. Upon receiving the code request (step S31), the system 30 performs authentication (step S32), obtains the payment method (step S33), and generates a code (step S34). The generated user code 12 is then sent to the user terminal 11 (step S35). As a result, in step S12, the code display screen 15 is displayed on the user terminal 11.

[0070] Then, in the user scanning method, instead of step S21, the user terminal 11 reads the store code 23. Then, instead of step S22, the user terminal 11 sends a settlement request to the system 30. The subsequent processing (steps S36 to S39, S13, S23) is performed in the same manner as in the store scanning method.

[0071] At least a portion of the error information sent within systems 30, 40, and 50 may be, for example, an HTTP (Hypertext Transfer Protocol) status code. For example, a status code number 400 indicates an error caused by an operation or defect on the client side, and is described as "4XX." Furthermore, a status code number 500 indicates an error caused by a failure on the server side, and is described as "5XX." For example, "500" indicates an error occurring within the server, and "503" indicates an error indicating that the server cannot be accessed. Such error information is collected by the error information collector 104.

[0072] [System switching conditions]

[0073] The switch 101 can also switch systems based on error information from the operating system (normally, the working system 30). Error information can also include the number of errors that occurred during various processes. For example, the error information can include at least one of the following: the number of generation errors that occurred during the code generation process for generating the user code 12, the number of authentication errors that occurred during the authentication process (including the verification process), or the number of settlement errors that occurred during the settlement process. Settlement errors can be caused by problems on the user side of the payment and by problems on the seller side of the payment.

[0074] The number of errors may also be recorded by the error information collector 104. The switching conditions of the system based on the error information may also be stored in at least one of the databases 34, 44, 54 or the history database 105.

[0075] The switching condition may also include multiple thresholds related to the number of error occurrences. In this case, the code processing system 100 may be configured to transmit either an active or standby code to the user terminal 11 based on the multiple thresholds related to the number of error occurrences. The multiple thresholds may also include a warning threshold (first threshold) and a switching threshold (second threshold). The warning threshold is used to determine if a fault has begun to occur in the corresponding system 30 or 40, while the switching threshold is used to actually execute the system switching.

[0076] The switch 101 may also be configured to automatically switch systems when an error exceeding a switching threshold occurs. Alternatively, the error information collector 104 may be configured to notify the administrator of the system 100 when an error exceeding a warning threshold or a switching threshold occurs. In this case, the administrator may also manually switch systems.

[0077] Figure 3 Shows the warning threshold and switching threshold of the system. Figure 3 In the example, the error code is represented by the HTTP status code. For example, in the code generation process, 100 errors / 2 minutes may be the warning threshold, and 500 errors / 2 minutes may be the switching threshold.

[0078] Multiple thresholds can also be set for different time periods. For example, different warning thresholds or switching thresholds can be set according to time periods. Figure 3 In the example of , in the authentication process, 100 errors / 2 minutes is set as the warning threshold in the middle of the night when the frequency of code settlement is low, and 500 errors / 2 minutes is set as the warning threshold in the daytime when the frequency of code settlement is high. In this case, the switching threshold may also be different according to the time period, but, for example, Figure 3 As shown, a common switching threshold value such as 1000 errors / 2 minutes may be set in the authentication process.

[0079] Different warning thresholds or switching thresholds can also be set based on the likelihood of errors. For example, if errors are more likely to occur in the payment method acquisition process than in the code generation and authentication processes, a higher number of errors can be tolerated in the payment method acquisition process compared to the code generation and authentication processes. For example, a warning threshold of 800 errors per two minutes and a switching threshold of 2000 errors per two minutes can be set.

[0080] The multiple thresholds may include one or more management thresholds. The management threshold may also be the number of errors that occur during a series of processes associated with a request from the administrator terminal 11. An example of a management threshold is the number of consecutive failures in code generation (including the transmission of user codes) or settlement processing for code processing requests sent from the administrator terminal 11. In this case, the user database includes multiple administrators (administrators of the system 100) as part of the multiple users, and includes multiple administrator terminals 11 used by the administrators as part of the multiple user terminals 11.

[0081] In this example, when the administrator runs the settlement application on the administrator terminal 11 pre-registered in the database 34, the administrator recognizes that the administrator terminal 11 has sent the code request during the user authentication in step S32. In this way, the administrator terminal 11 is applied with a general threshold value (e.g., Figure 3 The management switching conditions have different management thresholds (thresholds shown).

[0082] The administrator regularly or irregularly tests the work-related system 30 by sending code requests, etc., using the administrator terminal 11. This test can also be performed by having the robot operate the administrator terminal 11 (for example, by turning on the reload button of the user code 12 a predetermined number of times). By performing this test in an environment with stable communication, errors within the system 30 can be more appropriately detected.

[0083] The management threshold can also be set to a stricter condition than the general threshold. For example, the management threshold can be set to 10, 5, or 3 consecutive failures in code settlement, regardless of the process in which the error occurred. If the management threshold is set to 3 consecutive failures, the system can be quickly switched when code settlement fails 3 times in a row.

[0084] Some of the multiple administrators may be registered in the user database as designated administrators. Additionally or alternatively, some of the multiple administrator terminals 11 may be registered in the user database as designated terminals 11. Furthermore, even when the work-type system 30 is operating without malfunction, if a designated administrator or designated terminal 11 is identified, the system 100 may exceptionally transmit an emergency time code to the designated terminal 11. In this case, whether the person transmitting the code request is an administrator may be identified by the user router 102 or by another authentication device.

[0085] [System switching method]

[0086] Reference Figure 4The following describes a method for switching between systems 30, 40, and 50 based on error information. While the following illustrates switching from the active system 30 to the first standby system 40, the same method can also be used to switch from the first standby system 40 to the second standby system 50. The switcher 101 may also repeatedly execute steps S41 to S44 described below at a predetermined interval.

[0087] Prior to step S41, the error information collector 104 continuously collects error information from the operating system 30. Then, in step S41, the switch 101 obtains the error information collected by the error information collector 104. Next, in step S42, the switch 101 obtains the switching conditions corresponding to the error information. For example, if a code generation error occurs, the switch 101 obtains the code generation switching threshold; if an error occurs in a code processing request to the administrator terminal 11, the switch 101 obtains the management threshold; and if an authentication error occurs, the switch threshold for the current time period.

[0088] In the following step S43, the switch 101 determines whether the error count included in the error information exceeds the corresponding switching threshold. If the error count exceeds the switching threshold, the process proceeds to step S44, where a switch is performed from the working system 30 to the first standby system 40. More specifically, the switch 101 changes the destination of the code request received by the user router 102 from the user terminal 11 from the working system 30 to the first standby system 40. If the error count does not exceed the switching threshold, the switch 101 terminates the process without switching the system.

[0089] [Effects of the present disclosure]

[0090] When error information in the first standby system 40 satisfies a predetermined switching condition, a failure occurs in which errors repeatedly occur in the first standby system 40. Therefore, the switch 101 switches the system performing the first code processing (generating and transmitting the user code 12) from the working system 30 to the first standby system 40. Similarly, when error information in the first standby system 40 satisfies a predetermined switching condition, the switch 101 switches the system performing the first code processing from the first standby system 40 to the second standby system 50. Thus, the code processing system 100 is configured to transmit either an working system (normal operation) code or a standby system (emergency operation) code to the user terminal 11 based on error information in the working system 30.

[0091] Here, the user code 12 includes a system code unique to each of the systems 30, 40, and 50 in a predetermined position. Therefore, in the case of the store scanning method, the seller router 103, having received a settlement request from the seller terminal 20, can send the settlement request to the system that generated the user code 12 based on the system code of the user code 12 included in the settlement request.

[0092] That is, when the code processing system 100 receives the second code processing request (settlement request) containing the normal time code, it sends the second code processing request to the working type system 30 to perform the second code processing (code verification and settlement processing). When it receives the second code processing request containing the emergency time code, it sends the second code processing request to the first standby type system 40 to perform code processing.

[0093] For example, if user code 12 is a work-type code, seller router 103 sends a settlement request to work-type system 30. If user code 12 is a first standby-type code, seller router 103 sends a settlement request to first standby-type system 40. If user code 12 is a second standby-type code, seller router 103 sends a settlement request to second standby-type system 50. Then, each of systems 30, 40, and 50 is configured to verify user code 12 and perform settlement processing upon receipt of a settlement request.

[0094] In this way, if the active system 30 fails, the standby systems 40 and 50 take over. By making the code processing system 100 redundant using multiple systems 30, 40, and 50, the downtime of the code processing system 100 can be minimized regardless of any failure in any of the systems 30, 40, and 50. This improves the availability of services using identification codes.

[0095] [Effects of the Present Disclosure]

[0096] According to the present disclosure, the following effects can be achieved.

[0097] (1) The code processing system 100 transmits either an operating code or a standby code to the user terminal 11 based on error information in the operating system 30. Therefore, even when multiple systems 30 and 40 are switched, code processing can be performed appropriately.

[0098] (2) The user code 12 includes, in a predetermined position, a system code unique to each of the systems 30, 40, and 50 that generated the user code 12. Therefore, the seller router 103 can identify the system that generated the user code 12 based on the system code. This allows the seller router 103 to send a settlement request to the currently operating system.

[0099] (3) When each of the systems 30, 40, and 50 receives a second code processing request (settlement request), it performs a check process between the user code 12 included in the settlement request and the user code 12 already sent and stored in the code database. This allows the system 30, 40, and 50 that generated the user code 12 to perform settlement processing using the user code 12. Therefore, the system that executes the second code processing can be switched along with the system that issues the user code 12.

[0100] (4) If multiple errors occur during the code generation process, the system executing the process may fail. Therefore, the number of code generation errors can be used as a switching condition.

[0101] (5) If multiple errors occur during the user authentication process, the system executing the process may fail. Therefore, the number of authentication errors can be used as a switching condition.

[0102] (6) If multiple errors occur during the settlement process, the system executing the process may fail. Therefore, the number of settlement errors can be used as a switching condition.

[0103] (7) The number of processing requests to system 100 varies depending on the time period. Therefore, the impact, urgency, or importance of errors varies depending on the time period. Furthermore, depending on the time period, network congestion may cause frequent errors, but the congestion may also be temporary. Therefore, the optimal threshold for the number of errors at which systems 30, 40, and 50 should be switched varies depending on the time period. Therefore, by setting different thresholds depending on the time period, system 100 can be operated more appropriately.

[0104] (8) When switching between systems 30 and 40 based on error information, errors less than a threshold value are permitted to occur in the operating system 30. Therefore, by setting a management threshold value for errors generated in conjunction with a code processing request from the administrator terminal 11, it is possible to quickly switch between systems 30 and 40 without permitting errors until a general threshold value is reached.

[0105] (9) While making the system 100 redundant by having one or more standby systems 40 and 50 improves the availability of the system 100, it also increases costs. Therefore, the standby systems 40 and 50 only provide a portion of the services provided by the active system 30 (the first settlement process and the second settlement process) that is more important or frequently used (the first settlement process, for example, code settlement using a store scan method), thereby suppressing cost increases.

[0106] (10) Even when the working system 30 is operating without any faults, the system 100 sends an emergency time code to the designated administrator (designated terminal 11), and the designated administrator can use the emergency time code to confirm the operation of the standby system 40, 50. Alternatively, when a new standby system is introduced, the designated administrator can use the emergency time code generated exceptionally to confirm the operation of the new standby system.

[0107] (11) Switch 101 determines whether an error that satisfies the switching condition has occurred based on the switching condition and the error information collected by error information collector 104. The switching condition is stored in databases 34, 44, 54 or history database 105, and the error information is recorded by error information collector 104. By storing the switching condition and error information in a distributed manner, a single point of failure that could cause the entire system 100 to stop can be eliminated.

[0108] (12) The switch 101 specifies to which of the systems 30, 40, and 50 the user router 102 transmits the code request. Thus, by selectively specifying the destination of the code request by the switch 101, duplicate issuance of the user code 12 can be avoided.

[0109] (13) The code processing system 100 provides electronic settlement services. Therefore, code processing in code settlement can be appropriately performed.

[0110] This embodiment can be implemented by modifying as follows: This embodiment and the following modified examples can be implemented in combination with each other within a range that does not technically conflict.

[0111] [Change Example 1]

[0112] The above embodiment illustrates an active / standby configuration in which one of the three systems 30, 40, and 50 is designated as the active system 30, and when a failure occurs in the active system 30, processing is handed over to the standby system 40 or 50. The system and method of the present disclosure may also employ an active / standby configuration in which all systems 30, 40, and 50 are always in operation.

[0113] [Change Example 2]

[0114] The code processing system 100 may not include the second standby system 50 , or may include three or more standby systems.

[0115] [Change Example 3]

[0116] The code processing system 100 is not limited to code settlement; it can also be used for other services that utilize identification codes. For example, coupons with identification codes attached can be issued on an e-commerce website, and coupon benefits can be received based on the identification codes. Alternatively, electronic receipts with identification codes attached can be issued, and access management can be performed using these identification codes.

[0117] [Change Example 4]

[0118] In addition to switching the destination of code requests sent to user router 102, switch 101 can also switch the destination of settlement requests sent to user router 102 and seller router 103. In this case, standby systems 40 and 50, after switching from active systems 30 and 40, are configured to execute received code processing (settlement processing) regardless of the system code. This configuration is particularly advantageous when the time between the first code processing (transmission of user code 12) and the second code processing (code verification) is long.

[0119] [Way]

[0120] Hereinafter, aspects understood from the above-mentioned embodiment and modified examples will be listed. [1]

[0122] A code processing system includes a working system and a standby system, wherein:

[0123] Each of the working system and the standby system is configured to generate a multi-digit identification code upon receiving a code request from a user terminal, wherein the identification code includes a system code unique to the system generating the identification code in predetermined digits.

[0124] The identification code generated by the work class system is a work class code,

[0125] The identification code generated by the standby system is a standby code.

[0126] The code processing system is configured to transmit any one of the working class code and the standby class code to the user terminal based on error information in the working class system. [2]

[0128] The code processing system according to [1], wherein:

[0129] The code processing system is configured to perform code processing associated with electronic settlement via the user terminal and the seller terminal.

[0130] The seller terminal is configured to send a settlement request including the identification code obtained from the user terminal to the code processing system,

[0131] The code processing system includes a seller router configured to receive the settlement request sent from the seller terminal.

[0132] The seller router is configured to send the settlement request to the working type system when the identification code is the working type code, and to send the settlement request to the standby type system when the identification code is the standby type code. [3]

[0134] The code processing system according to [1] or [2] above, wherein:

[0135] The code processing system includes a database configured to store a transmission history of the identification code.

[0136] The code processing system is configured to: upon receiving a code processing request including the identification code, if the identification code is the working class code, send the code processing request to the working class system; if the identification code is the standby class code, send the code processing request to the standby class system;

[0137] Each of the working system and the standby system is configured to, upon receiving the code processing request, perform a check process on the identification code included in the code processing request and the identification code that has been sent and stored in the database. [4]

[0139] The code processing system according to any one of [1] to [3] above, wherein:

[0140] The error information includes the number of generation errors that occurred during the code generation process for generating the identification code. [5]

[0142] The code processing system according to any one of [1] to [4] above, wherein:

[0143] The code processing system includes a database configured to store information of users using the user terminal.

[0144] The working system and the standby system are each configured to, upon receiving a code request from the user terminal, refer to the database to perform user authentication, and upon completion of the authentication, generate the identification code.

[0145] The error information includes the number of authentication errors that occurred during the authentication process. [6]

[0147] The code processing system according to any one of [1] to [5] above, wherein:

[0148] The working system and the standby system are each configured to perform a settlement process when receiving a settlement request including the identification code.

[0149] The error information includes the number of settlement errors that occurred during the settlement process. [7]

[0151] The code processing system according to any one of [1] to [6] above, wherein:

[0152] The error information includes the number of times the error occurred.

[0153] The code processing system is configured to transmit any one of the working type code and the standby type code to the user terminal based on a plurality of thresholds related to the number of occurrences of the error,

[0154] The multiple thresholds may also be set for different time periods. [8]

[0156] The code processing system according to any one of [1] to [7] above, wherein:

[0157] The code processing system has a database storing information of a plurality of user terminals.

[0158] The plurality of user terminals include one or more administrator terminals used by an administrator of the code processing system.

[0159] The error information includes the number of times the error occurred.

[0160] The code processing system is configured to transmit any one of the working type code and the standby type code to the user terminal based on a plurality of thresholds related to the number of occurrences of the error,

[0161] The plurality of thresholds include one or more management thresholds, and the management thresholds are the number of times errors occur in a series of processes associated with the request from the manager terminal. [9]

[0163] The code processing system according to any one of [1] to [8] above, wherein:

[0164] The code processing system is configured to perform code processing associated with electronic settlement.

[0165] The first settlement process is a settlement process performed in response to a settlement request sent from a seller terminal that receives payment in the electronic settlement.

[0166] The settlement process performed in response to the settlement request sent from the user terminal that makes the payment in the electronic settlement is the second settlement process.

[0167] The working system and the standby system are each configured to perform settlement processing when receiving the settlement request.

[0168] The work system is capable of executing the first settlement process and the second settlement process.

[0169] The standby system can execute the first settlement process but cannot execute the second settlement process.

[10]

[0171] The code processing system according to any one of [1] to [9] above, wherein:

[0172] The code processing system has a database configured to store information of a plurality of users.

[0173] The plurality of users include an administrator of the code processing system,

[0174] The code processing system is configured to transmit the standby type code to a user terminal used by the manager upon receiving a code request from the manager during the operation of the working type system.

[11]

[0176] The code processing system according to any one of [1] to

[10] above, wherein the code processing system comprises:

[0177] a switch configured to switch between the working system and the standby system;

[0178] a database configured to store a switching condition for performing the switching; and

[0179] an error information collector configured to collect the error information,

[0180] The switcher is configured to switch the working system to the standby system based on the switching condition and the error information collected by the error information collector when an error that meets the switching condition occurs.

[12]

[0182] The code processing system according to any one of [1] to

[11] above, wherein the code processing system comprises:

[0183] a switch configured to switch between the working system and the standby system; and

[0184] The user router is configured to receive the code request from the user terminal and transmit the received code request to either the working system or the standby system.

[0185] The code processing system is configured such that the switch specifies to which of the working system and the standby system the user router transmits the code request.

[13]

[0187] The code processing system according to any one of [1] to

[12] above, wherein:

[0188] The code processing system is configured to provide electronic settlement services,

[0189] The working system and the one or more standby systems each include:

[0190] an authentication device configured to perform authentication processing for a user using the user terminal;

[0191] a setting device configured to obtain a payment method set by the user;

[0192] a code generating device configured to generate the identification code according to the code request; and

[0193] The settlement processing device is configured to perform settlement processing when a settlement request is received.

[0194] The payment method includes at least one of a credit card, a bank account, and electronic money.

[14]

[0196] A code processing system comprises a working system, one or more standby systems and a database, wherein:

[0197] The working system and the one or more standby systems are each configured to generate a multi-digit identification code upon receiving a code request from a user terminal.

[0198] The identification code includes, in predetermined bits, system codes unique to the active system and the one or more standby systems that generate the identification code.

[0199] The database is configured to store a transmission history of the identification code generated by each of the working system and the one or more standby systems.

[0200] The code processing system is configured to transmit the identification code generated by the working system and any one of the one or more standby systems to the user terminal based on error information in the working system, and is configured to transmit the code processing request to the system corresponding to the system code included in the identification code among the working system and the one or more standby systems upon receiving a code processing request including the identification code.

[0201] Each of the operating system and the one or more standby systems is configured to, upon receiving the code processing request, perform a check process between the identification code included in the code processing request and the identification codes stored in the database.

[15]

[0203] A code processing method in a code processing system, wherein the code processing system has a working system and one or more standby systems, wherein:

[0204] Each of the working system and the one or more standby systems is configured to generate a multi-digit identification code including a system code unique to each of the working system and the one or more standby systems in predetermined digits.

[0205] The method comprises the following processing:

[0206] Collecting error information from the work class system;

[0207] receiving a code request from a user terminal; and

[0208] The identification code generated by any one of the working system and the one or more standby systems is transmitted to the user terminal based on the error information.

Claims

1. A code processing system, comprising a working system and a standby system, wherein: Each of the working system and the standby system is configured to generate a multi-digit identification code upon receiving a code request from a user terminal, wherein the identification code includes a system code unique to the system generating the identification code in predetermined digits. The identification code generated by the work class system is a work class code, The identification code generated by the standby system is a standby code. The code processing system is configured to transmit any one of the working class code and the standby class code to the user terminal based on error information in the working class system.

2. The code processing system according to claim 1, wherein: The code processing system is configured to perform code processing associated with electronic settlement via the user terminal and the seller terminal. The seller terminal is configured to send a settlement request including the identification code obtained from the user terminal to the code processing system, The code processing system includes a seller router configured to receive the settlement request sent from the seller terminal. The seller router is configured to send the settlement request to the working type system when the identification code is the working type code, and to send the settlement request to the standby type system when the identification code is the standby type code.

3. The code processing system according to claim 1 or 2, wherein: The code processing system includes a database configured to store a transmission history of the identification code. The code processing system is configured to, upon receiving a code processing request including the identification code, send the code processing request to the working class system if the identification code is the working class code, and send the code processing request to the standby class system if the identification code is the standby class code. Each of the working system and the standby system is configured to, upon receiving the code processing request, perform a check process on the identification code included in the code processing request and the identification code that has been sent and stored in the database.

4. The code processing system according to any one of claims 1 to 3, wherein: The error information includes the number of generation errors that occur during the code generation process for generating the identification code.

5. The code processing system according to any one of claims 1 to 4, wherein: The code processing system includes a database configured to store information of users using the user terminal. The working system and the standby system are each configured to, upon receiving a code request from the user terminal, refer to the database to perform user authentication, and upon completion of the authentication, generate the identification code. The error information includes the number of authentication errors that occur during the authentication process.

6. The code processing system according to any one of claims 1 to 5, wherein: The working system and the standby system are each configured to perform settlement processing when receiving a settlement request including the identification code. The error information includes the number of settlement errors that occur during the settlement process.

7. The code processing system according to any one of claims 1 to 6, wherein: The error information includes the number of times the error occurred. The code processing system is configured to transmit any one of the working type code and the standby type code to the user terminal based on a plurality of thresholds related to the number of occurrences of the error, The multiple thresholds are set for different time periods respectively.

8. The code processing system according to any one of claims 1 to 7, wherein: The code processing system has a database storing information of a plurality of user terminals. The plurality of user terminals include one or more administrator terminals used by an administrator of the code processing system. The error information includes the number of times the error occurred. The code processing system is configured to send any one of the working type code and the standby type code to the user terminal based on a plurality of thresholds related to the number of occurrences of the error, The plurality of thresholds include one or more management thresholds, and the management thresholds are the number of times errors occur in a series of processes associated with the request from the manager terminal.

9. The code processing system according to any one of claims 1 to 8, wherein: The code processing system is configured to perform code processing associated with electronic settlement. The first settlement process is a settlement process performed in response to a settlement request sent from a seller terminal that receives payment in the electronic settlement. The settlement process performed in response to the settlement request sent from the user terminal that makes the payment in the electronic settlement is the second settlement process. The working system and the standby system are each configured to perform settlement processing when receiving the settlement request. The work system is capable of executing the first settlement process and the second settlement process. The standby system can execute the first settlement process but cannot execute the second settlement process.

10. The code processing system according to any one of claims 1 to 9, wherein: The code processing system has a database configured to store information of a plurality of users. The plurality of users include an administrator of the code processing system, The code processing system is configured to transmit the standby type code to a user terminal used by the manager upon receiving a code request from the manager during the operation of the working type system.

11. The code processing system according to any one of claims 1 to 10, wherein: The code processing system has: a switch configured to switch between the working system and the standby system; a database configured to store a switching condition for performing the switching; and an error information collector configured to collect the error information, The switcher is configured to switch the working system to the standby system based on the switching condition and the error information collected by the error information collector when an error that meets the switching condition occurs.

12. The code processing system according to any one of claims 1 to 11, wherein: The code processing system has: a switch configured to switch between the working system and the standby system; and The user router is configured to receive the code request from the user terminal and send the received code request to either the working system or the standby system. The code processing system is configured such that the switch specifies to which of the working system and the standby system the user router transmits the code request.

13. The code processing system according to any one of claims 1 to 12, wherein: The code processing system is configured to provide electronic settlement services, The working system and the one or more standby systems each include: an authentication device configured to perform authentication processing for a user using the user terminal; a setting device configured to obtain a payment method set by the user; a code generating device configured to generate the identification code according to the code request; and The settlement processing device is configured to perform settlement processing when a settlement request is received. The payment method includes at least one of a credit card, a bank account, and electronic money.

14. A code processing system comprising a working system, one or more standby systems, and a database, wherein: Each of the working system and the one or more standby systems is configured to generate a multi-digit identification code upon receiving a code request from a user terminal. The identification code includes, in predetermined bits, system codes unique to the active system and the one or more standby systems that generate the identification code. The database is configured to store a transmission history of the identification code generated by each of the working system and the one or more standby systems. The code processing system is configured to transmit the identification code generated by the working system and any one of the one or more standby systems to the user terminal based on error information in the working system, and is configured to transmit the code processing request to the system corresponding to the system code included in the identification code among the working system and the one or more standby systems upon receiving a code processing request including the identification code. Each of the operating system and the one or more standby systems is configured to, upon receiving the code processing request, perform a check process between the identification code included in the code processing request and the identification codes stored in the database.

15. A code processing method in a code processing system, the code processing system comprising a working system and one or more standby systems, wherein: Each of the working system and the one or more standby systems is configured to generate a multi-digit identification code, wherein the identification code includes a system code unique to each of the working system and the one or more standby systems in predetermined digits. The method comprises the following processing: Collecting error information from the work class system; receiving a code request from a user terminal; and The identification code generated by any one of the working system and the one or more standby systems is transmitted to the user terminal based on the error information.

Images