JP5763822B1 - Data processing system - Google Patents

Abstract

Inconsistency between data and its format is detected in a business system. A provider is connected to a plurality of securities companies (clients). The backbone system 106 configured in the provider 100 transmits a format file that defines the format of the data together with the data to the securities company 102. Before the transmission, it is determined whether or not the data is consistent with the format, and the data is transmitted to the securities company 102 on the condition that the data is consistent. The backbone system 106 includes a plurality of processing servers 110 and a relay server 112 (gateway), and the relay server 112 has a consistency check function. [Selection] Figure 1

Description

  The present invention relates to a technique for checking data in a server / client system.

  An ASP (Application Service Provider) provides various services via a network to a plurality of users. A user usually receives an ASP service via a web browser. For example, it can be said that the cloud service is a kind of ASP.

  Even in the securities industry, ASP-type server-client systems are often introduced (see, for example, Patent Document 1). The securities business service ASP (hereinafter simply referred to as “provider”) performs stock transactions, customer information management, credit checks, etc. in the background, and the securities company provides customers with various data provided by the provider. A business model of providing front-end services is also possible. Each securities company can outsource its core business to a provider, so there is no need to build a business system from scratch. Providers also have the advantage of being able to provide common services to multiple securities companies using a single business system.

  The simplest system configuration is that a securities company installs only a web server and handles only the user interface to customers. In this case, the securities company can leave all processing of data input from the customer to the provider.

  On the other hand, securities companies also want to provide their own services by extending and supplementing the provider's business system (hereinafter referred to as “core system”) with its own business system (hereinafter referred to as “extended system”). There are also needs. In this case, the provider provides the securities company with a format file as well as a data file such as customer information. The data file is the output of the core system. The format file is a specification that defines the format of data included in the data file. For example, when the customer's investment experience is selected from “none”, “less than 3 years”, and “more than 3 years”, the format file defines such an option.

JP 2005-38146 A

  In order to deal with various securities operations, the backbone system built by the provider tends to be large-scale. In a large-scale backbone system, distributed programs executed on a plurality of processing servers are frequently updated. The data format is also changed appropriately during operation. For example, it is assumed that the software engineer has redesigned the options to four options of “none”, “less than 3 years”, “more than 3 years but less than 10 years”, and “more than 10 years” regarding investment experience. At this time, the corresponding part of the format file must also be changed. If you forget to update the format file or mistakenly update the format file, you will not know if the specifications (format file) are wrong or the output (data file) is wrong. In particular, if a data file that does not match the format file is sent to a securities company, the extended system of the securities company is affected.

  The present invention has been made in view of the above problems, and its main purpose is to detect inconsistency between data and its format in a business system.

A data processing system according to an aspect of the present invention includes a data transmission unit that is connected to a plurality of clients and transmits data to the clients, a format transmission unit that transmits a format file that defines the format of the data, and the format file. And a determination unit that determines whether or not the data is consistent with the format.
The data transmission unit transmits data to the client on condition that the data to be transmitted is consistent with the format.

  According to the present invention, it is easy to suppress transmission of data that does not match the format in the business system.

It is a hardware block diagram which shows the relationship between a provider and a securities company. It is a figure which shows an attribute file. It is a figure which shows a transaction file. It is a figure which shows an attribute format file. It is a figure which shows a transaction format file. It is a functional block diagram of a relay server. 5 is a flowchart illustrating a process of checking consistency between a data file and a format file.

FIG. 1 is a hardware configuration diagram showing the relationship between the provider 100 and the securities company 102.
The provider 100 constructs a backbone system 106 for securities business services. The provider 100 is connected to a plurality of securities companies 102a, 102b, 102c,. The securities company 102 (client) is connected to the user terminal 104 of the customer via the Internet 108. For example, the securities company 102a is connected to user terminals 104a, 104b, 104c, 104d.

  The securities company 102 operates a web server and provides securities services to customers through a web browser. The backbone system 106 includes a plurality of processing servers 110a to 110f and a relay server 112 (gateway). From the user terminal 104, the customer inputs various information. For example, when a customer places a stock transaction, an ordering instruction is sent from the securities company 102 to the provider 100 and processed by the stock transaction program in one or more processing servers 110 in the backbone system 106, and the processing result is processed by the processing server 110f, The information is provided to the web browser of the user terminal 104 via the relay server 112 and the securities company 102.

  The securities company 102 may be in charge of only the user interface, and may entrust all processing for securities business to the core system 106 or may construct a unique extension system 114. For example, it is assumed that the securities company 102c wants to provide a stock fee discount service to a customer who has made a stock transaction of 1 million yen or more during the campaign period. At this time, the securities company 102c uses the extended system 114 to execute a process for selecting a preferential treatment person.

  In order to construct such an extended system 114, not only a data file that is an output of the core system 106 but also a format file as a specification that defines the format of the data is required. Therefore, the provider 100 according to the present embodiment can provide the securities company 102 with a format file in addition to the data file in response to a request from the securities company 102. Although details will be described later, the data file is various output information generated in the process of the core system 106 such as customer attribute information and transaction information.

FIG. 2A shows the attribute file 116.
The attribute file 116 is a data file indicating customer attributes. The attribute file 116 is mainly a collection of information input from the customer. In the attribute file 116 of FIG. 2A, customer attribute data such as name: Taro Nomura, annual income: 6-8 million yen, bankruptcy experience: none, stock trading experience: 5-10 years, and the like are registered. The attribute file 116 may be generated for each customer, or may be generated as a single data file in which a plurality of customer attributes are collected.

FIG. 2B is a transaction file 118.
The transaction file 118 is a data file indicating stock transaction information for “Taro Nomura” shown in FIG. The transaction file 118 is also a kind of customer information. According to the transaction file 118 in FIG. 2 (b), 100 shares of company A were purchased on March 6, 2014 at a unit price of 4,280 yen, and 10 shares of company B were purchased on June 8, 2014. You can see that you are buying for 141,000 yen.

FIG. 3A shows the attribute format file 120.
The attribute format file 120 in FIG. 3A is a format file that defines the data format of the attribute file 116. The attribute format file 120 defines the type and input conditions for each data item. In the attribute format file 120 of FIG.
(1) Name: Freely entered in kana characters. It can be entered in the range of 2 to 15 characters.
(2) Annual income: Selection formula from “0 to 100 (10,000 yen)” to “3000 (10,000 yen) or more”. There are 10 options.
(3) Bankruptcy experience: “Yes” or “No”.
(4) Years of stock trading experience: Selection formula from “None” to “10 years or more”. There are 5 options.
It is defined as
For example, even if a customer enters more than 16 characters when registering a name, the core system 106 will not accept such a name. The format file is a specification of the core system 106, and is compiled as a document file by Excel (registered trademark).

FIG. 3B shows a transaction format file 122.
The transaction format file 122 in FIG. 3B is a format file that defines the data format of the transaction file 118. The transaction format file 122 defines input conditions for each data item. The backbone system 106 generates a transaction file 118 according to the input from the customer.

  According to the transaction format file 122 of FIG. 3 (b), the transaction date can be set from January 1, 2001 to the current date and time, and an input outside this period is illegal. In other words, if a transaction date and time outside this period is registered in the transaction file 118, an error has occurred in the backbone system 106. Brands that can be invested, such as Company A, Company B, etc., are designated. For each issue, a minimum trading unit is specified. A range of contract prices is also specified. For example, in the case of Company A, it is not possible to assume a contract price that falls outside the range of 3000-8000 yen in view of the recent transaction price. there is a possibility. The stock trading method is any one of spot buying, credit buying, spot selling, and credit selling.

  Many of the data included in the attribute file 116 and the transaction file 118 are frequently changed in format. Data item choices may change, new data items may be added, or existing data items may be retired. As for the transaction file 118, a new company may be listed on the stock market, may be delisted, or its unit stock may change. A software engineer who maintains the backbone system 106 appropriately changes the program of the backbone system 106 according to the situation.

  There is no problem as long as the format file corresponding to the specification document is properly updated when the system of the backbone system 106 is changed. However, if you forget to update the format file or make an incorrect change, the data file and the format file will be inconsistent. In this case, it is difficult to know whether the format file is wrong or whether the format file is correct and the program of the core system 106 is wrong. Therefore, it is important not only to properly maintain the format file, but also to detect it early when a mismatch between the format file and the data file occurs.

  In general, inconsistency between the attribute file 116 and the attribute format file 120 is likely to occur when the system change is not correctly reflected in the attribute format file 120. On the other hand, the inconsistency between the transaction file 118 and the transaction format file 122 is highly likely due to an error in the backbone system 106. For example, if the transaction history of 1950 is registered in the transaction file 118, an error of the core system 106 is suspected. Even in such a case, by checking the transaction file 118 based on the transaction format file 122, an error can be detected early.

  In the present embodiment, the backbone system 106 transmits the format file together with the data file to the securities company 102. More specifically, these files are periodically transmitted from the provider 100 to the securities company 102 by batch processing.

  If the data file and the format file are inconsistent, there is a possibility that the expansion system 114 of the securities company 102 will be confused. For example, it is assumed that the number of characters of the customer name is changed to 2 to 20 characters instead of 2 to 15 characters, and an 18 character name is actually registered in the attribute file 116. On the other hand, in the attribute format file 120, it is assumed that the name input condition is 2 to 15 characters and is not updated properly. Even if the core system 106 can support “2 to 20 characters”, the attribute file 116 and the attribute format file 120 are inconsistent because the new specification is not reflected in the attribute format file 120.

  Alternatively, when “2000-2500 (10,000 yen)” is set in the attribute file 116 (data file) for the annual income of a certain customer, no such selection items are defined in the attribute format file 120. However, they are not consistent.

  If the data file and the format file are inconsistent, the securities company 102 cannot handle the data provided from the provider 100 with peace of mind.

  Therefore, the backbone system 106 in this embodiment addresses such a problem by transmitting the data file after checking the consistency between the data file and the format file.

  Further, in the transaction file 118, if the contract price of the company A whose stock price is on the order of several thousand yen is on the order of several tens of thousands of yen, there is a possibility that an error has occurred in the backbone system 106. In the transaction format file 122, a boundary condition of 3000 to 8000 yen is set for the contract price of the company A (see FIG. 3B), so the consistency between the transaction file 118 and the transaction format file 122 is checked. Thus, even if there is an error in the basic system 106, it can be detected early.

FIG. 4 is a functional block diagram of the relay server 112.
Each component of the relay server 112 is centered on an arbitrary computer CPU, memory, a program for realizing the components shown in the figure loaded in the memory, a storage unit such as a hard disk for storing the program, and a network connection interface. Realized by any combination of hardware and software. It will be understood by those skilled in the art that there are various modifications to the implementation method and apparatus. Each figure described below shows functional unit blocks, not hardware unit configurations.

  In the present embodiment, the consistency check function between the data file and the format file is integrated in the relay server 112 which is a gateway server. Since the check function can be added simply by adding the relay server 112, there is an advantage that the compatibility with the existing backbone system 106 is high. Of course, any processing server 110 may be responsible for all or part of the check function.

  The relay server 112 includes a communication unit 124 serving as a communication interface with the securities company 102 and the processing server 110, a determination unit 126 that checks the consistency between the data file and the format file, a format storage unit 128 that stores the format file, A data storage unit 130 for storing data files is included.

  The communication unit 124 includes a transmission unit 132, a reception unit 134, and a notification unit 136. The notification unit 136 notifies the person in charge of the core system 106, the specific processing server 110, and the like of the discovery of inconsistency when inconsistency is detected. The person in charge may be notified by e-mail, or may be notified by transmitting predetermined error information to the processing server 110.

  The transmission unit 132 includes a data transmission unit 138 that transmits a data file to the securities company 102 and a format transmission unit 140 that transmits a format file to the securities company 102. The receiving unit 134 includes a data receiving unit 142 that acquires a data file from the processing server 110 and a format receiving unit 144 that acquires a format file from the processing server 110.

  The determination unit 126 checks whether the data file and the format file are consistent before transmitting the data file and the format file. When there is a mismatch, the notification unit 136 notifies an error. Further, the data transmission unit 138 does not transmit the data file in which the inconsistency is detected to the securities company 102.

FIG. 5 is a flowchart showing the consistency check process between the data file and the format file.
The relay server 112 executes the check process shown in FIG. 5 at a predetermined time in the night by the batch process. The data receiving unit 142 receives the data file from the processing server 110 (S10), and the format receiving unit 144 receives the format file from the processing server 110 (S11). The data file is stored in the data storage unit 130, and the format file is stored in the format storage unit 128.

  If there is a data file that has not been checked for consistency among data files to be transmitted next time (Y in S12), the determination unit 126 selects one data file (S14) and refers to the corresponding format file. The consistency is checked (S16). If the consistency of all data can be confirmed (Y in S18), the process returns to S12 to check the next data file. If there is a mismatch (N in S18), the notification unit 136 notifies the mismatch (S20), and the determination unit 126 isolates the data file (S22). The quarantined data file is not sent.

  When the consistency check is executed for all the data files to be transmitted next time (N in S12), the processing is ended, and the format files corresponding to the data files whose consistency has been confirmed are collectively transmitted at a predetermined time.

The backbone system 106 has been described above based on the embodiment.
According to this embodiment, when a data file that summarizes data output from the core system 106 and a format file that defines the format are provided to the securities company 102 that is a client company, the consistency between the two is confirmed and transmitted. it can. For this reason, it is possible to suppress the risk that the data file that is the actual output in the core system 106 and the format file as the specification document are provided to the outside while being inconsistent.

  The present invention has been described based on the embodiments. The embodiments are exemplifications, and it will be understood by those skilled in the art that various modifications can be made to combinations of the respective constituent elements and processing processes, and such modifications are within the scope of the present invention. .

  In this embodiment, the ASP service for the securities company has been described. However, the present invention is not limited to the securities business and can be applied to various ASP services. For example, ASP services such as online shopping and ticket sales can be considered.

  100 provider, 102 securities company, 104 user terminal, 106 core system, 108 Internet, 110 processing server, 112 relay server, 114 extended system, 116 attribute file, 118 transaction file, 120 attribute format file, 122 transaction format file, 124 communication Unit, 126 determination unit, 128 format storage unit, 130 data storage unit, 132 transmission unit, 134 reception unit, 136 notification unit, 138 data transmission unit, 140 format transmission unit, 142 data reception unit, 144 format reception unit.

Claims (5)

Connected to multiple clients,
A data transmission unit for transmitting data to the client;
A format transmission unit that transmits a format file that defines the format of the data to the client;
A determination unit that refers to the format file and determines whether or not the format defined in the format file and the actual format of the data to be transmitted match ;
The data transmission system, wherein the data transmission unit transmits the data to the client on condition that data to be transmitted is consistent with the format. The data processing system includes:
A processing server for generating the data;
A relay server that mediates the plurality of clients and the processing server,
The data processing system according to claim 1, wherein functions of the data transmission unit, the format transmission unit, and the determination unit are integrated in the relay server. The format file defines selectable items for selection type data,
The data processing system according to claim 1, wherein the determination unit notifies data inconsistency when selection-type data is not defined in the selectable item. The format file defines a settable range for numeric data,
4. The data processing system according to claim 1, wherein the determination unit notifies data inconsistency when numerical data is out of the settable range. 5. In order to provide common financial services to multiple securities companies, it is connected to the business systems of each securities company,
A data transmission unit that transmits a customer information file of a securities company to the securities company;
A format transmission unit that transmits a format file that defines a format of data included in the customer information file to the securities company;
A determination unit that refers to the format file and determines whether or not the format defined in the format file and the actual format of the data in the customer information file are consistent ;
The data transmission system, wherein the data transmission unit transmits the customer information file to the securities company on condition that the data of the customer information file to be transmitted is consistent with the format.

Images