JP2009151416A - Transaction access history referencing system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a transaction access history referencing system that displays online transaction access history information for each customer in an easy to understand way and edits and processes the information for display to allow easy recognition of each customer's transaction situation. <P>SOLUTION: In the transaction access history referencing system, as a process means that can be executed as a control part 11 of a securities server 1 reads a process program stored in a storage unit 13, a customer-based access history creation means 112 creates an access history file 132 for each customer out of an access log, and a customer-based access history editing means 114 references a translation table 135 and a brand table 134 upon requests and instructions from a user PC2 and outputs the access history information to the user PC2 for display in terms that are easy for customers to understand. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to a transaction access history reference system that displays transaction access history information when trading stocks and the like via a network, and in particular, displays the access history information for each customer in an easily understandable manner. It is related with the transaction access history reference system which can be provided by editing.

Through an Internet network, customers trade stocks on a trading server operated by a securities company.
Since transactions such as stocks (online transactions) via this network are simple, online transactions have recently increased.

  In addition, as a prior art which refers to the history of transactions such as stocks via a network, there is JP 2007-279811 “Transaction system, transaction information provision method, transaction information provision program in online trade” (Patent Document 1).

  In this patent document 1, when an acquisition request for information related to a transaction is received from a user terminal, the acquisition unit acquires the date when the transaction was completed from the transaction history storage unit, and a calendar is displayed with characters / symbols indicating that the transaction has been completed It is described to do.

JP 2007-279811 A

  In recent years, there are many inquiries from customers such as “I do not remember placing such orders” and “I want to see past history of transactions on the screen” under the situation where online transactions via the network are increasing. As a securities company, it is necessary to respond quickly.

  In addition, there is a need for a system that allows the customer himself / herself to immediately know whether someone other than himself has logged in, such as when a cyber attack that attempts to log in occurs while impersonating the customer.

  In Patent Document 1, since only the transaction information on which a transaction has been established is displayed, it has not been possible to deal with orders, cyber attacks, etc. on which a transaction has not been established.

  The present invention has been made in view of the above circumstances, and transaction history for displaying online transaction access history information in an easy-to-understand manner for each customer, and further editing and displaying the transaction status for the customer. An object is to provide an access history reference system.

  The present invention for solving the problems of the above-described conventional example displays access history information related to the transaction on the user device when the user device accesses the securities server from the user device via the network and makes a transaction such as stocks. A transaction access history reference system for outputting, wherein the securities server includes a control unit and a storage unit, and the storage unit includes an access log file for storing processing programs, access log data, and an access log for each customer. An access history file for each customer that stores the data, an access history edit data storage unit that stores data obtained by editing the data in the access history file for each customer, and a translation table that stores translation data corresponding to the data in the access log As a processing means that the control unit can read and execute the processing program stored in the storage unit Access history creation means for creating access log data for transaction access and storing it in the access log file; access by customer referring to the access log file and writing the access log data to the customer access history file for each customer Reads access log data for a specific period from the access history file for each customer in response to a request from the history creation means and user device, and translates the access log data using the translation data read and referenced from the translation table And an access history editing data storage unit that stores the edited data in the access history editing data storage unit and displays and outputs the edited data in the access history editing data storage unit.

  According to the present invention, in the transaction access history reference system, the storage unit includes a brand table that stores brand names corresponding to brand codes, and the access history editing unit for each customer that can be executed by the control unit includes: When the edit data in the edit data storage section contains a brand code, the brand code in the edited data is converted into a brand name using the brand code read from the brand table and referenced. It is characterized by.

  In the transaction access history reference system, the control unit refers to a customer-specific access history file as a processing unit that can read and execute a processing program stored in the storage unit, The customer code determines whether data related to other customers other than the customer is included, and if data related to other customers is included, the data related to the other customers is accessed by the corresponding customer. It is characterized by having customer-specific access history check means for performing processing of writing data in a history file and deleting data related to the other customers from the customer-specific access history file.

  According to the present invention, in the transaction access history reference system, the access history editing unit for each customer reads access log data related to login of a specific customer from the access history file for each customer, counts the number of logins by date, The number of logins is displayed and output on the user device.

  In the transaction access history reference system, the storage unit includes a contract table that stores an order identifier, a contract date, a unit price, the number of shares, and a contract code as contract data for the contracts contracted for each customer. Access history editing means reads access log data related to specific customer orders from customer-specific access history files, reads contract data for the customer from the contract table, and enables comparison of order data and contract data for each brand Display output.

  In the transaction access history reference system according to the present invention, when a specific operation type is designated as a search condition from the user device by the customer access history editing unit, the specific operation type of the specific customer is obtained from the customer access history file. The access log data for a specific period is read, the access log data is translated using the translation data read from the translation table and referenced, and stored as edit data in the access history edit data storage unit. The editing data of the storage unit is displayed and output.

  According to the present invention, the access history creation means that can be executed by the control unit of the securities server creates access log data for transaction access and stores it in the access log file. By referring to the log file, the access log data for each customer is written in the access history file for each customer, and the access history editing means for each customer accesses the access log for a specific period from the customer access history file for a specific customer in response to a request from the user device. The access log data is translated using the translation data read from the translation table and referenced, and stored as edit data in the access history edit data storage unit. As a transaction access history reference system that displays and outputs So, there is likely to display can effectively understand the access history information of online transactions for each customer.

  According to the present invention, the access history editing unit for each customer reads access log data related to login of a specific customer from the access history file for each customer, counts the number of logins by date, and stores the number of logins for each date in the user device. Since the transaction access history reference system is displayed and output, the online transaction access history information is displayed for each customer in an easy-to-understand manner, and the number of logins is edited and processed to display the transaction status at the customer. effective.

  According to the present invention, the storage unit has a contract table that stores the order identifier, contract date, unit price, number of shares, and stock code as contract data for the contracts contracted for each customer. The above transaction that reads the access log data related to the order of a specific customer from the access history file for each customer, reads the contract data of the customer from the contract table, and displays and outputs the order data and contract data for each brand on the user device. Since it is an access history reference system, online transaction access history information is displayed in an easy-to-understand manner for each customer, and the order data and contract data are edited and processed so that they can be compared. There is an effect that can be done.

Embodiments of the present invention will be described with reference to the drawings.
[Outline of the embodiment]
In the transaction access history reference system according to the embodiment of the present invention, the access history creation unit for each customer is read from the access log as a processing unit that can be executed by reading the processing program stored in the storage unit by the control unit of the securities server. An access history file for each customer is created, and the access history information for each customer displays the access history information on the user PC in terms that are easy for the customer to understand by referring to the translation table and brand table in response to a request from the user PC. The customer can easily recognize the transaction access history.

  Further, in the transaction access history reference system according to the embodiment of the present invention, the access history editing unit for each customer edits the access history information according to a request instruction from the user PC, and displays and outputs it to the user PC. By displaying the number of logins of a customer as a bar graph or comparing and displaying the order and execution status, the login count and order and execution status can be easily recognized.

[Entire system: Fig. 1]
A transaction access history reference system (this system) according to an embodiment of the present invention will be described with reference to FIG. FIG. 1 is a configuration block diagram of a transaction access history reference system according to an embodiment of the present invention.
As shown in FIG. 1, the system includes a securities server 1 that realizes online transactions, and a user computer (user PC) 2 that displays a transaction status when a customer accesses the server and inputs an online transaction instruction. Basically, the securities server 1 and the user PC 2 are connected to each other and a network 3 such as the Internet.

  A plurality of user PCs 2 are connected to the securities server 1. Further, the user PC 2 may be a terminal device such as a mobile phone or a PDA (Personal Digital Assistants) as long as it can perform online transactions.

[Each part]
[Securities server 1]
As shown in FIG. 1, the securities server 1 includes at least a control unit 11, a main memory 12, a storage unit 13, and an interface unit 14.
The control part 11 reads the processing program memorize | stored in the memory | storage part 13, loads it into the main memory 12, and enables the process realization means mentioned later to be performed.
The main memory 12 is a work memory, loaded with a processing program, and used for processing operations.

The storage unit 13 stores a processing program, files necessary for processing, a table, a data storage unit, and the like.
The interface unit 14 is an interface for connecting to an external device, and includes, for example, an interface unit for connecting to the network 3.

[User PC2]
The user PC 2 is a user device basically composed of a computer, and has the same configuration as that of the securities server 1. The user PC 2 includes an input unit for a customer to input an instruction and a display unit for displaying a transaction status and the like, and is connected to the main body through an interface unit.

  In particular, the user PC 2 outputs a request to the stock server 1 to display access log data for a specific customer for a specific period, and further outputs a specific operation type in the access log as a search condition. . Details will be described later.

[Processing means: FIG. 2]
Next, various processing means realized by the control unit 11 of the securities server 1 and a data group stored in the storage unit 13 will be described with reference to FIG. FIG. 2 is a diagram showing an outline of the processing means in this system.

  As shown in FIG. 2, the processing means for the control unit 11 to read a processing program from the storage unit 13 and load it into the main memory 12 for execution is an access history creation unit 111, an access history creation unit 112 for each customer, , Customer-specific access history checking means 113 and customer-specific access history editing means 114.

  In addition, the storage unit 13 includes an access log file 131, an access history file 132 for each customer, an access history edit data storage unit 133, a brand table 134, a translation table 135, and a contract table 136. .

[Data group]
The access log file 131 stores all access logs to the securities server 1 in time series.
The customer-specific access history file 132 extracts an access log for each customer from the access log file 131 based on a user identifier (user ID) and stores the access log in time series.

The access history edit data storage unit 133 stores data edited and processed based on the access history information for each customer acquired from the access history file 132 for each customer.
The brand table 134 stores brand names corresponding to brand codes.
The translation table 135 is a conversion table for converting the access log (expressed in English or symbols) stored in the customer access history file 132 into terms (Japanese) that can be easily understood by the customer.

  The contract table 136 stores an order identifier (order ID), a contract date, a unit price, the number of shares, and a brand code for the brand contracted for each customer (user ID). In this contract table 136, data is written when an order is executed, and the control unit 11 may write the data. When the contract processing is performed by another server, the data is stored in the securities table. The server 1 may receive and write.

Next, specific processing means will be described.
[Access history creation means 111]
The access history creation unit 111 performs a process of writing access logs from all user PCs 2 to the securities server 1 in the access log file 131 in time series.

[Customer access history creation means 112]
The access history creation unit 112 for each customer refers to the access log file 131 periodically, reads the access log for a specific period, and distributes it for each customer (user ID) to access the customer by time as the access history information for each customer. Processing to add to the history file 132 and perform writing is performed.

[Customer access history check means 113]
The customer-specific access history check unit 113 checks whether or not the customer-specific access history information added to the customer-specific access history file 132 includes data other than the customer (data of other customers). If the data related to other than the customer is included, the data is written in the access history file of the corresponding customer, and the data related to other than the customer is deleted from the access history file 132 for each customer.

[Customer access history editing means 114]
The customer-specific access history editing unit 114 acquires access history information from the customer-specific access history file 132 in response to a request from the customer, performs an editing operation, and displays and outputs it to the user PC 2. Details of the editing operation will be described below.

[First processing of access history editing means for each customer]
For example, when there is an input of a request instruction to display access history information of a specific customer (in this case, a user of the user PC 2) from the user PC 2, the customer-specific access history editing unit 114 accesses the specified period. The history information is acquired from the customer-specific access history file 132, the access log written in English or symbols is converted into Japanese understandable by the customer using the translation table 135 and the brand table 134, and the access history edit data is stored. The edited data is displayed and output to the user PC 2.
Instead of using the translation table 135 and the brand table 134, the access log may be displayed and output to the user PC 2 for a specific period with the English or symbol notation.

[Second process of customer access history editing means]
For example, when a request instruction for displaying the number of logins of the customer in a specific period is input from the user PC 2, the customer-specific access history editing unit 114 obtains login history information for a specified period from the customer-specific access history file 132. The number of logins for each date within the period is counted, and the number of logins for each date is displayed and output to the user PC 2 as a bar graph using the graphic function.
The number of logins for each date may be displayed by a method other than the bar graph. For example, the number of logins may be displayed numerically for each date.

[Third processing of access history editing means for each customer]
For example, when a request instruction for displaying the order / contract status of the customer in a specific period is input from the user PC 2, the customer-specific access history editing unit 114 displays the access history information regarding the order in the specified period as access history for each customer. The contract data is acquired from the file 132 and the contract data for the customer for the period or the period specified by the customer is read from the contract table 136, and the order data (limited to those for which the order has been completed) can be compared with the contract data for each brand. Then, display is output to the user PC 2. For comparison, for example, it is conceivable to display a bar graph according to the number of shares or the amount of money.

Note that the order data and the contract data may be associated one-to-one with the order ID as a key so that the relationship between the order and the contract is displayed and output.
Further, the order data and the contract data may be divided into a buy order and a sell order, and the contract data corresponding to these orders may be displayed.

  The second and third processing results of the customer-specific access history editing means may be displayed instead of the first processing result, but are displayed together with the first processing result, that is, in addition to the first processing result. You may do it.

[Display screen: Fig. 3]
Next, a screen displayed on the display unit of the user PC 2 will be described with reference to FIG. FIG. 3 is a schematic diagram showing a display screen.
As shown in FIG. 3, the display screen displayed on the display unit of the user PC 2 is provided with a tab serving as an operation index on the upper side of the screen. Tabs include “stock”, “credit”, “withdrawal / withdrawal”, “management” and the like. A character string (access history reference button) corresponding to the index is displayed on the left side of the screen.

  Here, in order to refer to the access history information of the transaction, click “Access history reference” in the character string on the left side of the screen, or click “Management” on the tab, and select “Access history” from the displayed selection items. By clicking “Browse”, a dedicated password (password different from login password) input window for referring to access history information is displayed. When the correct password is entered, the login / access history is displayed in the display area (A). The search screen is displayed.

[Login / access history search screen: Fig. 4]
The login / access history search screen will be described with reference to FIG. FIG. 4 is a schematic diagram showing a login / access history search screen.
As shown in FIG. 4, the login / access history search screen includes “year”, “month”, “day”, “period”, “time”, “operation type”, “brand”, and the like as search condition input items.

"Operation type" includes: "All", "Login", "Stock spot purchase input", "Stock spot purchase confirmation", "Stock spot purchase completed", "Stock spot sale input", "Stock spot sale confirmation", "Stock""Sale in kind""Credit purchase entry""Credit purchase confirmation""Credit purchase completion""Credit sale entry""Credit sale confirmation""Credit sale completion""Credit purchase repayment confirmation""Credit"Purchase repayment completion""Credit sale repayment input""Credit sale repayment confirmation""Credit sale repayment completion""Paymentinput""Paymentconfirmation""Paymentcompletion""Paymentinput""Paymentconfirmation" “Finish” can be selected from the pull-down menu.
In FIG. 4, when a search condition is input and set and a search instruction is given by clicking the “Search” button, a search result screen as shown in FIG. 5 is displayed.

[Login / access history search result screen: Fig. 5]
Next, the login / access history search result screen will be described with reference to FIG. FIG. 5 is a schematic diagram showing a login / access history search result screen.
On the login / access history search result screen, as shown in FIG. 5, a part of the access log raw data (English or symbol notation data) for a specific period is displayed.
Note that FIG. 5 shows a display example in which the access log described in the first process of the customer-specific access history editing unit 114 is displayed for a specific period as the access history editing data in the form of English or symbols.

  In FIG. 5, the request occurrence date and time are shown in square brackets, “X XX XXX--000000” shows the order route classification, company code, department code, administrator code, operator code, customer code, and “ "FROM screen name", "AID (Application ID)", "TO screen name", and "Job-specific output items" are displayed.

  “FROM screen name” is the screen name that was already displayed when the access was made (screen name before transition), and “TO screen name” is the screen name of the transition destination that was migrated by the user's operation. Yes, “AID” indicates screen transition processing, and “business-specific output item” indicates data input by the user.

For example, “AccountLogin”, “Home”, “Menu”, “EquityExecuteReference”, and “EquityBuyInput” as “FROM screen names” are “Customer login screen”, “Home screen”, “Menu screen”, “Spot stock contract inquiry screen”, “Spot stock purchase” It means “additional input screen”.
In addition, for example, “TPTradingPower”, “EquityBalanceReferenceList”, “SrvRegiExec”, and “SrvRegiReference” as “TO screen names” are “transaction reserve screen”, “actual stock balance inquiry screen”, “service start button press screen”, and “service list screen”. Each means.
The relationship between the raw data and the translation terms is stored in the translation table 135.

[Login and access history translation screen: Fig. 6]
The login / access history translation screen will be described with reference to FIG. FIG. 6 is a schematic diagram showing a login / access history translation screen.
As shown in FIG. 6, the login / access history translation screen is obtained by translating the login / access history search result screen shown in FIG.
The login / access history translation screen allows the user to easily recognize the access history.

[Processing flow 1: FIG. 7]
Next, the processing of the customer-specific access history creation unit 112 will be described with reference to FIG. FIG. 7 is a flowchart showing the processing of the customer-specific access history creating means.
As shown in FIG. 7, the customer-specific access history creation unit 112 reads an access log for a specific period (a fixed period from immediately after reading the previous time) from the access log file 131 when the process is started (S11). Then, the access log is sorted for each user ID and written in the customer-specific access history file 132 (S12).
In this way, access history information for each customer is stored in the access history file 132 for each customer.

[Processing flow 2: FIG. 8]
Next, the processing of the customer-specific access history check unit 113 will be described with reference to FIG. FIG. 8 is a flowchart showing the processing of the access history check unit for each customer.
As shown in FIG. 8, the customer-specific access history check unit 113 refers to the customer-specific access history file 132 when the processing is started (S21), and determines whether or not other person's access log data is included. (S22).

  If another person's access log data is erroneously included (in the case of Yes), the other person's access log data is written to the other person's customer-specific access history file 132 in chronological order (S23), The data is deleted from the access history file 132 for each customer who is referring (S24). And it returns to process S21 and repeats a process.

  If it is determined in the determination process S22 that no other person's access log data is included (in the case of No), it is then determined whether or not all access logs have been checked (S25), and the check ends. If (Yes), the process is terminated. If the check process has not been completed (in the case of No), the process returns to the process S21 and is repeated.

[Display screen when other person's access log data is included: Fig. 9]
Here, a display screen when data of another person's access log is included will be described with reference to FIG. FIG. 9 is a schematic diagram showing a display screen when data of another person's access log is included.
In FIG. 9, since the 6-digit number in “X XX XXX--000000” indicates the customer code, if the customer code includes a customer code other than the principal, the access log data of the other person Will be included.
In FIG. 9, “000021” and “000022” are customer codes of other people, and access log data corresponding to the customer codes are data of other people's access logs.

[Display Example 1 of Access History Editing Data 1: FIG. 10]
Next, a display example of access history edit data will be described with reference to FIG. FIG. 10 is a diagram illustrating a display example in which the number of logins is displayed as a bar graph.
FIG. 10 is a display example described in the second process of the access history editing unit 114 for each customer. The vertical axis indicates the number of logins in one day, and the horizontal axis indicates the date. By performing such display, the customer can easily recognize the outline of the number of logins in a specific period.

[Access History Editing Data Display Example 2: FIG. 11]
A display example of the access history edit data will be described with reference to FIG. FIG. 11 is a diagram illustrating a display example in which order data and contract data are displayed for comparison for each brand.
FIG. 11 is a display example described in the third processing of the customer-specific access history editing unit 114, in which the brand name is displayed in the vertical direction and the order and the contract amount are displayed in the horizontal direction. By performing such display, the customer can easily recognize the order and execution status in a specific period for each brand.

[Effect of the embodiment]
According to this system, since the customer can refer to the transaction access history information on the user PC 2, it is possible to know whether or not there is a sign that another person has logged in. In addition, it is possible to know what screen transitions have been made in the past, enter orders, and know what orders have been placed, so it is possible for customers to save the trouble of making inquiries to securities companies, etc. Inquiries to securities companies are expected to decrease. Therefore, there is an effect that the burden on both the customer and the securities company can be reduced.

  INDUSTRIAL APPLICABILITY The present invention is suitable for a transaction access history reference system in which online transaction access history information is displayed in an easy-to-understand manner for each customer, and further edited and displayed to easily recognize the transaction status of the customer.

1 is a configuration block diagram of a transaction access history reference system according to an embodiment of the present invention. It is a figure which shows the outline | summary of the processing means in this system. It is the schematic which shows a display screen. It is the schematic which shows a login and access log | history search screen. It is the schematic which shows a login and access log | history search result screen. It is a schematic diagram showing a login / access history translation screen. It is a flowchart which shows the process of the access log | history production means classified by customer. It is a flowchart which shows the process of the access log | history check means classified by customer. It is the schematic which shows a display screen in case the data of another person's access log are contained. It is a figure which shows the example of a display which displayed the frequency | count of login with the bar graph. It is a figure which shows the example of a display which displayed order data and contract data so that comparison was possible for every brand.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 1 ... Securities server, 2 ... User PC, 3 ... Network, 11 ... Control part, 12 ... Main memory, 13 ... Memory | storage part, 14 ... Interface part, 111 ... Access history creation means, 112 ... Access history creation means classified by customer, 113: Customer-specific access history check means, 114: Customer-specific access history editing means, 131 ... Access log file, 132 ... Customer-specific access history file, 133 ... Access history edit data storage unit, 134 ... Brand table, 135 ... Translation table 136 ... Contract table

Claims (6)

A transaction access history reference system that displays and outputs access history information related to the transaction on the user device when a stock server or the like is accessed from a user device via a network,
The securities server includes a control unit and a storage unit,
In the storage unit, the processing program, the access log file for storing the access log data, the customer access history file for storing the access log data for each customer, and the data for the customer access history file are edited. An access history editing data storage unit for storing data, and a translation table for storing translation data corresponding to the data of the access log,
As the processing means that enables the control unit to read and execute the processing program stored in the storage unit,
Access history creation means for creating access log data for transaction access and storing it in the access log file;
A customer-specific access history creation means for referring to the access log file and writing access log data to the customer-specific access history file for each customer;
Read access log data of a specific period for a specific customer from the customer access history file in response to a request from the user device, translate the access log data using the translation data read and referenced from the translation table, and A transaction access history reference system, comprising: an access history editing means for each customer that stores data as edit data in an access history edit data storage unit and displays and outputs the edit data of the access history edit data storage unit. The storage unit has a brand table that stores brand names corresponding to brand codes,
When the customer-specific access history editing means that can be executed by the control unit includes a brand code in the edited data in the access history editing data storage unit, the brand code read and referenced from the brand table 2. The transaction access history reference system according to claim 1, wherein a brand code in the edited data is converted into a brand name by using.   As a processing means that allows the control unit to read and execute the processing program stored in the storage unit, refer to the access history file for each customer, and in the access log data, other customers other than the customer from the customer code If data related to other customers is included, the data related to the other customers is written in the access history file of the corresponding customer, and the access history file for each customer 3. The transaction access history reference system according to claim 1, further comprising a customer-specific access history check means for performing a process of deleting data relating to the other customer from the customer.   The access history editing means for each customer reads the access log data related to the login of a specific customer from the access history file for each customer, counts the number of logins by date, and displays and outputs the number of logins for each date on the user device. The transaction access history reference system according to any one of claims 1 to 3. The storage unit has a contract table that stores the order identifier, contract date, unit price, number of shares, and stock code as contract data for the contracts contracted for each customer,
Customer access history editing means reads access log data related to specific customer orders from customer-specific access history files, reads contract data for the customer from the contract table, and compares order data and contract data for each brand 4. The transaction access history reference system according to claim 1, wherein the transaction access history reference system is displayed on a user device.   When a specific operation type is designated as a search condition from the user device, the customer-specific access history editing means reads the access log data for a specific period for the specific operation type of the specific customer from the customer-specific access history file, and translates The access log data is translated using the translation data read and referenced from the table and stored as edit data in the access history edit data storage unit, and the edit data in the access history edit data storage unit is displayed and output. 4. The transaction access history reference system according to claim 1, wherein the transaction access history reference system is a transaction access history reference system.

Images