KR101346778B1 - Method for approving card transactions and method for managing card transaction approval informaion - Google Patents

Abstract

The present invention relates to a card transaction approval system, a method, a terminal, and a card transaction approval information management method, a server, a terminal, and a card transaction management server technology. By using the pattern, it is easier to approve card transactions using electronic money in transportation card transactions and distribution for public transportation such as buses, subways, taxis, and the like. In the case of storing the information, the fixed data is generated by dividing the stored data and the non-saved data based on the pattern information of the identification number, and the pattern information is stored in the fixed data together to facilitate the change and addition of the pattern information. do. According to the present invention, the conventional fixed memory area allocation prevents the capacity increase caused by the increase in the number of cards and the change information, and the pattern change information can be updated, thereby facilitating management and reducing search time. have.

Description

METHOD FOR APPROVING CARD TRANSACTIONS AND METHOD FOR MANAGING CARD TRANSACTION APPROVAL INFORMAION}

The present invention relates to a card transaction approval method and a card transaction approval information management method. More specifically, the present invention stores the pattern information about the pattern type of the attribute information of the cards included in a single block on the basis of the unique number of each card, the attribute information of the cards included in any block is stored in the pattern information By determining whether or not to store the attribute information of the cards included in the block according to whether or not the pattern type, not only can reduce the memory capacity of the system and improve the update speed, but also need to change the system even when the pattern information is changed. The present invention relates to a card transaction approval method and a card transaction approval information management method.

The card transaction approval system is a system that collects the corresponding fee by approving the card. For example, in the case of a transportation card, the fee is collected by differentiating the payment fee according to various attribute information (availability, general, youth, etc.). Or control use.

The card transaction approval system needs to continuously manage the change of the attribute information corresponding to the card number or the unique number of the card in order to differentially collect charges or control authorization according to various attribute information.

The card has a unique number of the card, for example, Alias No., in order to determine the attribute information of the card.

1 is a diagram showing fixed data of the prior art for storing flag information of all cards in a conventional card transaction approval system.

As shown in Fig. 1, the conventional card transaction approval system is a kind of flag information (a card indicating whether or not the card can be used) corresponding to the Alias No. (a series of identification numbers starting from 1) of the card in the fixed data 100. Attribute information, for example, flag information 1 may be a usable card and flag information 0 may indicate an unusable card) in order to facilitate authentication when the card is used.

More specifically, the conventional card transaction approval method sets flag information on the availability of the card with respect to the Alias No. uniquely assigned to each card at the time of card issuance, and all the memory addresses corresponding to the Alias No. Flag information about the card is sequentially stored in a bitmap method. When the card is used, the Alias No. of the card is read from the card, the flag information stored in the memory address corresponding to the read Alias No. is read, and the availability of the card is determined according to the flag information.

However, the conventional card transaction approval technique occupies a large memory area because all flag information corresponding to the total number of cards must be sequentially stored regardless of whether the card is used or not. In particular, since the usage area is determined for each card issuer, when the memory area of the flag information indicating whether the card is used is exhausted at the memory address corresponding to the previously assigned Alias No., the flag information is sequentially added. Rather, since the memory information area corresponding to a separate card number must be allocated and the flag information is stored even for a card which is not actually issued, unnecessary capacity consumption occurs. Currently, the Seoul Transportation Terminal uses about 51M of memory space to store and manage the flag information of 270 million cards, but it is expected to exhaust the memory address area in the future. The memory area is expanding.

Therefore, the conventional card transaction approval technology has a large capacity increase due to the method of storing Alias No. corresponding to all cards, which causes the limitation of storage capacity. In other words, there was a problem that can be accompanied by the overall operation of the terminal due to insufficient memory capacity.

Korean Registered Patent No. 0549209 (registered on Jan. 26, 2006) Korean Registered Patent No. 0694803 (registered March 7, 2007)

In the conventional card transaction approval technology operating as described above, the capacity is greatly increased due to the way of storing Alias No. corresponding to all the cards, which causes the limitation of storage capacity. There was a problem that the overall failure of the terminal operation due to lack.

Accordingly, an embodiment of the present invention, by using the pattern of the attribute information, such as whether the use of the card corresponding to the unique number of the card, discount, etc., the electronic card in the transportation card transaction and distribution for public transportation means such as bus, subway, taxi A card transaction approval method, a terminal, a system, and a card transaction approval information management method, a terminal, a server, and a card transaction management server, which can more easily perform card transaction approval using money, can be provided.

In addition, the embodiment of the present invention, while storing the pattern information about the pattern type of the attribute information (for example, flag information) of the cards included in a single block on the basis of the unique number of each card, it is included in any block It is necessary to change the system software even when the pattern information is changed by reducing the memory capacity of the system by determining whether or not the attribute information of the cards included in the block is stored according to whether the attribute information of the cards is the pattern type stored in the pattern information or not. There is provided a card transaction approval method, a terminal, a system and a card transaction approval information management method, a terminal, a server, a card transaction management server.

In addition, in the embodiment of the present invention, when the attribute information of the card is changed, the structure for updating the changed attribute information for each block is designed, but the block of the attribute information to be added at the last position of the fixed data, By recording the location information of the block in the header of the fixed data, it is possible to provide a card transaction approval method, a terminal, a system and a card transaction approval information management method, a terminal, a server, and a card transaction management server that can increase the ease of management and update speed. have.

According to an embodiment of the present invention, a card transaction approval method includes storing pattern information about a pattern type of attribute information of cards included in a unit block based on a unique number of a card, storing location information of each block, Generating fixed data including header information including pattern type information and body information in which card attribute information is stored in units of blocks based on the storage location information, and approving the transaction of the card based on the fixed data; Determining whether or not.

The pattern type information corresponds to a pattern type stored in the pattern information, and the pattern type information for each block may indicate a pattern type of attribute information of cards included in the corresponding block.

The pattern information may be included in the fixed data or linked with the fixed data.

The unique number may be an Alias No.

The attribute information may be represented by flag information.

The number of pattern types may be 256.

If the attribute information of the cards included in any block is not the pattern type stored in the pattern information, the attribute information of the cards included in the block is stored in the body information, and the storage location information of the corresponding block is stored in the corresponding block. The storage location in the body information may be indicated.

And determining whether to approve a transaction of a card based on the fixed data comprises: recognizing a unique number of the card, retrieving attribute information corresponding to the unique number of the card from the fixed data, and And determining whether to approve the transaction of the card according to the retrieved attribute information.

The retrieving may include: calculating a block including a unique number of the recognized card; retrieving header information of the calculated block; storage location information and pattern type of the calculated block; Retrieving the information.

The retrieving of the storage location information and the pattern type information may include retrieving attribute information of the card stored in the body information when the storage location information of the block exists, and when the pattern type information of the block exists. The attribute information of the card may be obtained from the pattern type information.

In accordance with another aspect of the present invention, there is provided a method of managing card transaction approval information, the method comprising: storing pattern information about a pattern type of attribute information of cards included in a unit block based on a unique number of a card; Generating fixed data including header information including information and pattern type information and body information in which card attribute information is stored in units of blocks based on the storage location information, and when attribute information of a card is changed, The method may include determining a pattern of attribute information of cards included in the block to which the card belongs, and updating the fixed data according to the determined pattern.

The updating may include recording attribute information of cards included in a block to which the card belongs, at the last position of the body information, when the determined pattern is not a pattern type stored in the pattern information. Updating body information location information for the block.

The updating may include recording a corresponding pattern type in pattern type information of a block to which the card belongs when the determined pattern is a pattern type stored in the pattern information.

The updating may include deleting the corresponding block from the body information when the determined pattern type is a pattern type stored in the pattern information, and when the pattern of the corresponding block before the change is not the pattern type stored in the pattern information. And deleting the block recorded at the last position of the body information, and recording the block recorded at the last position of the body information at the position where the corresponding block is deleted.

The card transaction approval terminal according to an embodiment of the present invention includes pattern information on a pattern type of attribute information of cards included in a unit block based on a unique number of a card, storage location information and pattern type information of each block. Memory means for storing fixed data including body information in which the header information and the body information in which the card attribute information is stored in units of blocks based on the storage location information are stored, and the corresponding card according to the attribute information of the card retrieved from the fixed data. It may include a control means for determining whether to approve the transaction.

Card transaction management server according to an embodiment of the present invention, the pattern information on the pattern type of the attribute information of the cards included in the unit block based on the unique number of the card, the storage location information and pattern type information of each block A data generation unit configured to store fixed data including header information to be included and body information in which card attribute information is stored in units of blocks based on the storage location information, and transmitting the fixed data to a card transaction approval terminal. It may include a control unit.

Card transaction approval information management terminal according to an embodiment of the present invention, the pattern information on the pattern type of the attribute information of the cards included in the unit block based on the unique number of the card, the storage location information and pattern type of each block Memory means for storing fixed data including header information including information and body information in which card attribute information is stored in units of blocks based on the storage location information; And control means for determining a pattern of attribute information of cards included in a block to which the block belongs, and updating the fixed data according to the determined pattern.

Card transaction approval information management server according to an embodiment of the present invention, the pattern information on the pattern type of the attribute information of the cards included in the unit block based on the unique number of the card, the storage location information and pattern type of each block A data generation unit for storing fixed data including header information including information and body information in which card attribute information is stored in units of blocks based on the storage location information; The controller may include a controller configured to determine a pattern of attribute information of the cards included in the block to which the card belongs, and to update the fixed data according to the determined pattern.

Card transaction approval system according to an embodiment of the present invention, the pattern information on the pattern type of the attribute information of the cards included in the unit block based on the unique number of the card, the storage location information and pattern type information of each block And a card transaction approval terminal configured to store fixed data including header information to be included and body information in which card attribute information is stored in units of blocks based on the storage location information. The card transaction approval terminal may include: It is possible to determine whether to approve the transaction of the corresponding card according to the attribute information of the card retrieved from the fixed data.

According to the card transaction approval system, the method, the terminal and the card transaction approval information management method, the server, the terminal, the card transaction management server according to the embodiment of the present invention as described above has one or more of the following effects.

According to the card transaction approval system, method, terminal and card transaction approval information management method, server, terminal, and card transaction management server according to an embodiment of the present invention, the card transaction approval system stores the data using pattern information of attribute information corresponding to the unique number of the card. Since the memory capacity can be reduced by dividing the data from the non-storage data and compressing the fixed data based on the data, the fixed memory area allocation prevents the capacity increase due to the increase of the number of cards and the change information, and the change. By updating the information, it is possible to simplify management and reduce search time. In addition, even if the data is compressed and stored in the storage space, it is possible to quickly process the approval, and it is possible to easily manage the change of information to enable stable system operation.

In addition, the present invention stores the pattern information on the pattern format of the attribute information of the cards included in a single block based on the unique number of each card, not stored in the system, but stored in the fixed data or stored separately from the fixed data. However, by processing the operation information rather than storing in the system, even if the pattern information is changed or added, it is possible to operate without changing the system.

In addition, the present invention, when updating the fixed data, by placing the newly added block information at the end of the fixed data and write the position information in the header of the fixed data, it is possible to update without additional memory and the update speed is improved It works.

1 is a diagram showing fixed data of the prior art for storing flag information of all cards in a conventional card transaction approval system.
2 is a block diagram schematically showing the overall configuration of a card transaction approval system according to an embodiment of the present invention;
3 is a block diagram briefly illustrating an internal configuration of a card transaction management server according to an embodiment of the present invention;
4 is a block diagram briefly illustrating an internal configuration of a card transaction approval terminal according to an embodiment of the present invention;
5 is a diagram illustrating a structure of fixed data according to an embodiment of the present invention;
6 is a diagram illustrating a method of updating fixed data according to an embodiment of the present invention;
7 is a diagram illustrating a method of updating fixed data according to another embodiment of the present invention;
8 is a flowchart illustrating a fixed data generation procedure according to an embodiment of the present invention;
9 is a flowchart illustrating an operation procedure for determining whether to approve a card transaction according to an embodiment of the present invention;
10 to 11 are flowcharts illustrating an operation procedure of a fixed file update according to an embodiment of the present invention.

Advantages and features of the present invention and methods for achieving them will be apparent with reference to the embodiments described below in detail with the accompanying drawings. The present invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art. To fully disclose the scope of the invention to those skilled in the art, and the invention is only defined by the scope of the claims. Like reference numerals refer to like elements throughout.

In the following description of the present invention, a detailed description of known functions and configurations incorporated herein will be omitted when it may make the subject matter of the present invention rather unclear. The following terms are defined in consideration of the functions in the embodiments of the present invention, which may vary depending on the intention of the user, the intention or the custom of the operator. Therefore, the definition should be based on the contents throughout this specification.

Each block of the accompanying block diagrams and combinations of steps of the flowchart may be performed by computer program instructions. These computer program instructions may be loaded into a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus so that the instructions, which may be executed by a processor of a computer or other programmable data processing apparatus, And means for performing the functions described in each step are created. These computer program instructions may also be stored in a computer usable or computer readable memory capable of directing a computer or other programmable data processing apparatus to implement the functionality in a particular manner so that the computer usable or computer readable memory It is also possible for the instructions stored in the block diagram to produce a manufacturing item containing instruction means for performing the functions described in each block or flowchart of the block diagram. Computer program instructions may also be mounted on a computer or other programmable data processing equipment, such that a series of operating steps may be performed on the computer or other programmable data processing equipment to create a computer-implemented process to create a computer or other programmable data. Instructions that perform processing equipment may also provide steps for performing the functions described in each block of the block diagram and in each step of the flowchart.

Also, each block or each step may represent a module, segment, or portion of code that includes one or more executable instructions for executing the specified logical function (s). It should also be noted that in some alternative embodiments, the functions noted in the blocks or steps may occur out of order. For example, the two blocks or steps shown in succession may in fact be executed substantially concurrently or the blocks or steps may sometimes be performed in the reverse order, depending on the functionality involved.

Embodiment of the present invention, by using the pattern of the attribute information, such as the use of the card corresponding to the unique number of the card, discount, etc., electronic money in the transportation card transaction and distribution for public transportation means such as bus, subway, taxi In order to more easily perform the card transaction authorization using the, the pattern information about the pattern format of the attribute information of the cards included in the same block on the basis of the unique number of each card, but stores the card information included in any block By determining whether or not to store the attribute information of the cards included in the block according to whether or not the attribute information is in the pattern format stored in the pattern information, not only can reduce the memory capacity of the system and improve the update speed, but also change the pattern information. Even if it does, there is no need to change the system software.

Therefore, when the attribute information corresponding to the card identification number in the unit memory block is changed, a structure that can update the changed attribute information for each block is designed so that the added block information is placed at the end of the fixed file, and the corresponding position information is added to the header. To record.

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

2 is a block diagram schematically showing the overall configuration of a card transaction approval system according to an embodiment of the present invention.

Referring to FIG. 2, the card transaction approval system of the present invention includes a card transaction management server 10 and a card transaction approval terminal 20, and the like. It can be interlocked.

Specifically, the card transaction management server 10 receives the attribute information corresponding to the unique number of the card from the card issuer system (not shown) to provide fixed data for processing whether to use the prepaid card or the postpaid card, discount, or authentication. Create At this time, in one embodiment, the unique number of the card may be Alias No. In addition, the attribute information of the card may include at least one information of the card type, discount information, availability of the card, the attribute information of the card may be expressed as flag information, for example.

The card transaction management server 10 may transmit the generated fixed data to the card transaction approval terminal 20. In addition, when the attribute information of the card is changed, the card transaction management server 10 may periodically receive the change information from the card issuer system and update the information of the pre-generated fixed data based on this, and update the updated fixed data. The card may be transmitted to the card transaction approval terminal 20 upon request of a predetermined period or the card transaction approval terminal 20.

In addition, in another embodiment of the present invention, the card transaction management server 10 transmits the change information received from the card issuer system to the card transaction approval terminal 20, and the card transaction approval terminal 20 is applied to the received change information. Based on the previously stored fixed data may be updated.

Meanwhile, the card approval terminal may be a POS (Point of Sales) terminal installed in a bus, subway and taxi card terminal, a restaurant, a convenience store, and the like, and when a request for approval by a card occurs from a card user, a unique number stored in the card Recognition of the card, and by searching the attribute information of the card to be used in the pre-stored fixed data, it is possible to determine whether or not to accept the transaction of the card.

3 is a block diagram schematically showing the internal configuration of the card transaction management server 10 according to an embodiment of the present invention.

As shown in FIG. 3, the card transaction management server 10 may include a data generation unit 12, a data storage unit 14, a control unit 16, and the like.

The data generation unit 12 of the card transaction management server 10 divides a plurality of card attribute information that needs to be managed based on a unique number of the card into blocks of a predetermined size, and body information in which the attribute information of the card is actually stored. And generating fixed data including pattern information in which all preset pattern types are stored, pattern information of each block, and header information storing whether or not the data is stored in the body region based on each pattern type in the pattern information. The fixed data can be stored in the data storage unit 14.

In addition, the data controller 16 may store and delete the fixed data, transmit the fixed data to the card transaction approval terminal 20, receive the change data, and update the fixed data based on the change data.

4 is a block diagram schematically illustrating an internal configuration of a card transaction approval terminal 20 according to an embodiment of the present invention.

As shown in FIG. 4, the card transaction approval terminal 20 may include a memory means 22, a control means 24, and the like.

The memory means 22 may store fixed data, change data, and the like received from the card transaction approval server 10. Further, the control means 24 recognizes the unique number of the card when the card is to be used, reads attribute information corresponding to the unique number of the card from the fixed data stored in the memory means 22, and then reads the attribute information. Depending on the card, it may be possible to decide whether to accept the transaction or decline the transaction.

5 is a diagram illustrating a structure of fixed data according to an embodiment of the present invention.

Referring to FIG. 5, the fixed data 500 may include pattern information 510, header information 520, and body information 530 through 560.

The pattern information 510 stores a pattern format of attribute information of cards included in the same (single) block based on the unique number of the card and functions as operation information. In one embodiment, when the card is a prepaid card, the attribute information of the card may be represented by 2 bits of flag information, and when the card is a postpaid card, the attribute information of the card may be represented by 1 bit of flag information.

When the size of the pattern information is 1 byte, the pattern information may have 256 types of patterns, and the pattern information may be changed and operated according to circumstances. For example, as shown in FIG. 5, the pattern type of the attribute information of the cards included in the same block is 0x00 is set as the pattern type 1, and when it is 0x55, the pattern type 2 is set. , 0xEE can be set to pattern type 255.

In addition, the header information 520 includes all block information 522 representing the total number of blocks, storage location information 524 representing the storage location in the body information of each block, and a pattern format of attribute information of the cards included in each block. May include pattern type information 526 indicating information, wherein the information stored in the pattern type information 526 corresponds to the pattern format stored in the pattern information 510.

The body information 530 to 560 may store attribute information of a card in units of blocks based on header information.

In this case, when the attribute information of the cards included in any block is a pattern format stored in the pattern information, the pattern type information 526 of the block includes the corresponding block corresponding to the pattern format stored in the pattern information 510. The pattern type of the attribute information of the cards may be stored (in this case, the storage location information 524 of the corresponding block included in the header information may have a value of 0).

On the contrary, when the attribute information of the cards included in any block is not a pattern format stored in the pattern information, the attribute information of the cards included in the block is stored in the body information 530 to 560, and the header information 520 The storage location information 524 of the corresponding block included in may indicate the storage location in the body information of the corresponding block.

On the other hand, the pattern information 510 is not stored in the fixed data 500, but may be separately stored and managed as a system file in the card transaction management server 10 or the card transaction approval terminal 20 in the card transaction approval system. In this case, there may be a disadvantage that the system program needs to be changed when the pattern type information is changed, which also causes a problem of system stability and increases the risk.

In the present invention, the pattern type is changed or added and deleted by processing the pattern information on the pattern format of the attribute information of the cards included in the same block based on the unique number of each card as the operation information, rather than storing the information in the system. If applicable, it can be applied immediately without changing the system or software.

That is, the block pattern in the body information set to each pattern type may be changed due to an operation problem. For example, when the 0x55 pattern set as the pattern information 1 is changed to the 0x66 pattern, the pattern information is controlled through the controller 16 of the card transaction management server 10 or the control means 24 of the card transaction approval terminal 20. After changing the 0x55 pattern for the pattern type 1 to the 0x66 pattern in step 510, the pattern information may be changed by performing a fixed data update procedure or rebooting.

However, the pattern information 510 is not necessarily included in the fixed data 500, and only the pattern information 510 is separated and linked with the fixed data 500, thereby minimizing a change factor of the card transaction approval system as operation information. It can also be configured to.

In FIG. 5, attribute information of cards corresponding to blocks 3, 5, 6, and 7 areas 530 to 560 is not a pattern format stored in pattern information, and attribute information of cards corresponding to blocks 1, 2, and 4 is The fixed data 500 in the case of the pattern format stored in the pattern information is shown.

Specifically, since the seven pieces of block information are recorded in the header information 520 of the fixed data 500, the information on the total number of blocks 522 is displayed as seven pieces, and in the case of blocks 1,2 and 4, a regular pattern Since the card information is not stored in the body information, which is the lower end of the header information 520, the card attribute information for blocks 1, 2, and 4 may be stored only in the preset pattern type information.

In this case, '0', '1', '2', and '3', which mean a specific pattern type of the attribute information of the card, may be pattern type information, which is a pattern type previously stored in the pattern information 510. Corresponds to. For example, the pattern type information '0' is the pattern type 0 and means that the pattern type of the entire block is 0x00, and the pattern type information '1' is pattern type 1 and the entire block is 0x55. The pattern type information '2' means a case in which the entire block is 0xAA, and the pattern type information '3' means a case in which the entire block is 0xFF.

However, in the case of block 3 (530), block 5 (540), block 6 (550), and block 7 (560), since the pattern is not a pattern stored in the pattern information, the pattern is formed in a random form that is not constant. The storage location information of blocks 3, 5, 6, and 7 (530 through 560) included in 520 stores a location where the block is stored in body information, and also blocks 3, 5, 6, and 7 (530 through 560). The attribute information of the cards included in) may be sequentially stored in the body information in block units.

In this case, each block may have a size of 512 bytes, and 510 bytes of 512 bytes of each block may store 2040 (2 bits) card information for prepaid cards and 4080 (1 bit) cards for postpaid cards, and the remaining 2 bytes May be used for CRC check checks.

In other words, in the case of block 1, since the entire block represents the pattern '0x55', the pattern type '1' corresponding to the pattern '0x55' is identified in the pattern information 510 and stored in the body information of the fixed data 500. The pattern type '1' may be recorded in the header information 520 (in this case, the storage location information may have a value of '0').

In addition, since the entire block 2 represents the '0xAA' pattern, the pattern information '510' corresponding to the '0xAA' pattern is checked in the pattern information 510, and the header information is not stored in the body of the fixed data 500. The pattern type '2' may be recorded in 520.

However, in the case of block 3, since the random pattern is not set in the pattern information 510, the attribute information of the card corresponding to block 3 is stored (530) at the '1' position of the body information area, and the header information is stored. The storage location information of the block 3 area in 520 is recorded as a location 1, and '0' or no information may be input to the pattern type information of the block 3.

In block 4, since the entire block represents the pattern '0x00', the pattern type information '0' corresponding to the pattern '0x00' is checked in the pattern information 510 and the header is not stored in the body of the fixed data 500. The pattern type information '0' may be recorded in 520.

In addition, since block 5 represents a random pattern not set in the pattern information 510, the block 5 is stored 540 in the '2' position of the body information region, and the storage position information of the block 5 region in the header information 520. Is recorded in 2 positions, and since the pattern represents a random pattern, '0' may be input or no information may be input. Likewise, block 6 and block 7 may also be stored in the same manner.

6 illustrates a method of updating fixed data according to an embodiment of the present invention.

Referring to FIG. 6, when the pattern data is changed or the attribute information of the card is changed, the fixed data 600 may be updated by adding or deleting the changed information in the fixed data 600 through a simple change method. .

That is, the controller 16 of the card transaction management server 10 that receives the changed information from the card issuer system may update the pre-generated fixed data 600 based on the change data.

First, when the pattern type information is changed, added, or deleted, the controller 16 may replace the corresponding pattern type information in the pattern information 655 with the deleted or changed pattern type information, and when there is additional pattern type information. In the next stored pattern type information can be stored in.

On the other hand, when the change history information is necessary due to the changed card information, when the card transaction management server 10 receives the block 6 (630) information in which the attribute information of some cards are changed, the fixed data 600 previously generated The updated fixed data 650 may be generated based on the reflection.

Since the block 6 information included in the existing fixed data 600 is a pattern '3', the block information is not stored in the body region and only the pattern type information is included in the header information 610 region.

However, since the changed block 6 630 information includes a random pattern rather than a predetermined regular pattern, as shown in the updated fixed data 650, the lowest block in the body information area, that is, next to the block 7 675, is included. Can be recorded at position 4.

The storage location information may be changed from 0 to 4 as block 6 information in the header information 660. In addition, the pattern information of block 6 may also be changed from 3 to 0. FIG.

On the other hand, the updated block 6 (630) may be located between the block 5 (670) and the block 7 (675) and recorded, but in this case, since the header information for the block 7 (675) should also be changed, the controller 16 ), The load increase and update speed may decrease.

By placing the updated block at the bottom of the body information area, the update can be performed without changing the header information of the blocks located in the existing body information area, thereby reducing the load and improving the update speed of the controller 16. I can bring it.

7 illustrates a method of updating fixed data according to another embodiment of the present invention.

Referring to FIG. 7, when the card transaction management server 10 receives the block 5 630 information in which the attribute information of some cards has been changed, the controller 16 updates the reflected data in the generated fixed data 650. Fixed data 700 can be generated.

Since the block 5 information 670 previously included in the existing fixed data 650 includes a random pattern, the block 5 information 670 is stored in two positions of the body information area.

The controller 16 may delete the existing block 5 (670) first. In addition, the changed block 5 (685) information can be checked to determine the case where one block is 0xFF.

Since the pattern type is set to '3' for the 0xFF in the preset pattern information 655, the changed block 5 (685) information is the block 5 information in the header information 710 without being stored in the body information area. The information can be changed from 0 to 3.

Since the block 5 in the body information area is deleted, the storage location information may also be changed from 2 to 0 in the block 5 information in the header information 710.

Meanwhile, when a block to be deleted in the body information area is generated through the update of the changed block as described above, the last stored block may be moved and stored at the position of the deleted block.

That is, as in the updated fixed data 700, block 6 725, which is stored last at the location where the block 5 670 information is deleted, may be moved and stored in the body information area 2 location. As the block 6 information in the header information 710, the storage location information may be changed from 4 to 2.

When updating the variation information of the block, when the changed block is set to the pattern type stored in the pattern information in the random pattern, after deleting the block stored in the body information area, only the pattern type information can be recorded in the header area. At the block position, the last stored block is placed, so that no additional memory allocation is required and the update speed can be increased.

In this regard, FIG. 7 is an exemplary embodiment, in which the updated fixed data 700 has seven total blocks, and in one block, for example, attribute information of one card is represented by a value of 2 bits. The case where 20 card informations are stored in one block is shown. At this time, block 1 is 1-20, block 2 is 21-40, block 3 is 41-60, block 4 is 61-80, block 5 is 81-100, block 6 is 101-120, block 7 is 121 Attribute information corresponding to the card identification number ˜140 may be stored.

Meanwhile, the card transaction approval terminal 20 may determine whether to approve a transaction of the card using the fixed data 700. For example, card 49 is stored in block 3, and when the information of block 3 is retrieved from the header area 710, the body area location information of the block is set to 1. That is, there are 41 to 60 card information in the block information 715 at the 1st position, and since one card information is composed of 2 bits, 00, the 17th and 18th bits of the block 3 (715) in the body area, is the 49th card. It can be seen that the attribute information of this through the card number 49 can be seen that the card is not available, thereby rejecting the transaction approval request for the card number 49.

8 is a flowchart illustrating a fixed data generation procedure according to an embodiment of the present invention.

Referring to FIG. 8, in operation 800, the data generation unit 12 of the card transaction management server sets and stores pattern information about a pattern format of attribute information of cards included in the same block based on a unique number of each card. . Thereafter, in operation 802, the source file transmitted from the card issuer system is opened, and in operation 804, a text to binary function is performed to convert the text into a binary number.

In operation 808, the unique number area is determined from the source file converted into the binary format. Thereafter, in step 810, a fixed file of a fixed data format is opened, and in step 812, the total number of blocks is calculated using the unique number area of the source file as a block form.

Through this, in step 814, the pattern memory and the header memory for the fixed file are allocated based on the total number of blocks. Thereafter, in step 816, it is determined whether all data in the raw file has been checked. If there is still data to be checked, the process proceeds to step 818 to read the raw file again and performs text-to-binary conversion in step 820.

Thereafter, in step 822, the option information is read, and in step 824, the block position of the unique alias number is calculated. In step 826, it is determined whether the current working block is the same as the previous working block. If the same is the case, the process proceeds to step 836, the option is set in the corresponding option area, and the process returns to step 816. FIG.

However, in step 826, it is determined whether the current working block and the previous work block are the same. If not, the block check proceeds to step 828, and in step 830, the block pattern is random. .

If the pattern is random, block information is recorded in the body region in step 834, position information of the body is recorded in the header region, and after setting options in step 836, the process returns to step 816. However, if the block pattern is a preset pattern format in step 830, the process proceeds to step 832 to record the corresponding pattern format in reverse, and in step 836 to set the option, and returns to step 816.

On the other hand, when the reading of all the data in the raw file is finished in step 816, the block check is performed in step 838, and in step 840, the pattern is analyzed through the pattern analysis on the corresponding block. In the case of one format, the process proceeds directly to step 844 to record the pattern information in the header area without recording in the body area.

However, if the pattern for the block is a random pattern instead of the pattern format stored in the pattern information in step 840, the block proceeds to step 842 to record the block in the body information area, and in step 844, the body in which the block is recorded in the header area. The location information of the information area is recorded.

Through this, data about the entire block is recorded in the body area and the header area of the fixed file.

9 is a flowchart illustrating an operation procedure for determining whether to approve a card transaction according to an embodiment of the present invention.

Referring to FIG. 9, when the control means 24 of the card transaction approval terminal 20 receives a search for the attribute information value of a specific card for card approval, in step 900, the unique number of the search request card (eg For example, by checking the Alias No.) to determine the area of the unique number.

In step 902, the fixed file, that is, the fixed data is opened, and in step 904, the total number of blocks is read. In operation 906, a bit mask for each bit type is set to read a specific bit in the block. That is, when the bit type is 1 bit, the bit type is set to 1 bit mask, and when the bit type is 2 bit, the 2 bit mask is set.

Thereafter, in step 908, the location of the block in which the requested attribute information of the card is stored is calculated and determined. In step 910, the pattern information included in the pattern information area is read, and then the header of the block is determined based on the block location determined in step 912. The area will be read.

In step 914, it is checked whether the corresponding block is recorded in the body region. That is, since the header area includes the location information of the block recorded in the body area, if the block is recorded in the body area, the body block information is read based on the location information in step 916 and the card information is read in step 920. You will be confirmed.

However, if the corresponding block is not recorded in the body region in step 914, after confirming the pattern type information recorded in the header region in step 918, the card information requested for the search is checked in step 920.

10 to 11 are flowcharts illustrating an operation procedure of a fixed file update according to an embodiment of the present invention.

Referring to FIG. 10, the variation file received in step 1000 is read, and the reference unique number is read in step 1002. In step 1004, the area of the unique number is determined, and in step 1006, the name of the fixed file is set.

In step 1008, the set fixed file is opened, and in step 1010, a merge file to merge the change file is opened. In step 1012, first, the number of blocks is read. In step 1014, the total number of blocks is set, and then memory is allocated. In step 1016, the header information is read and copied to the merge file.

After that, in step 1018, if it is not done by checking whether the variation file is finished, proceed to step 1020 to convert the variation record to a unique number, and in step 1022, check whether all variation records are finished or not. In this case, the bit mask is set in step 1024.

In step 1026, the block position is calculated, and in step 1028, it is determined whether the current work block and the previous work block are the same. In step 1030, the option value is set to the current work block. After that, the process returns to step 1022 to confirm whether or not the record check is finished. If the record check is finished, the process returns to step 1018.

On the other hand, if the check of the variation file is completed in step 1018 and proceeds to step 1100 of FIG. 11 performs a block check, in step 1102 it is checked whether the pattern of the block is random through the pattern information check.

If the pattern of the block is random, in step 1104, the changed block information is recorded in the area where the existing block is located in the body area. In step 1106, the location information in which the changed block is recorded in the body area is recorded in the header information. Will return to.

However, in step 1102, if the pattern of the block is any one of the predetermined pattern information that is not random, the process proceeds to step 1108 to determine whether the block is located at the last storage block or at the end of the body information area.

If the position is located at the end of the body information area, even if the existing block is deleted, there is no change in the position of the block. In step 1112, the value of the pattern type in the block is preset and searched in the stored pattern information area. The corresponding pattern type is recorded in the header area. The process proceeds to step 1114.

On the other hand, if the block is not located at the end or the last storage block in the body information area in step 1108, a block position change may occur when the existing block is deleted. In other words, the process proceeds to step 1110 where the end-of-file record is moved to the position where the recording block is deleted to perform recording.

Thereafter, in step 1112, the position information of the moved block is recorded in the header area, and the pattern information of the changed block is searched in the preset and stored pattern information area, and then the corresponding pattern type is recorded in the header area. do. The process proceeds to step 1114.

In operation 1114, the controller 10 determines whether the change operation on all the variation files is completed, and returns to operation 1022 of FIG. 10 when the change files remain. However, in step 1114, when all changes to the change file are completed, the change is terminated.

As described above, the card transaction approval system, method, terminal and card transaction approval information management method, server, terminal, card transaction management server according to an embodiment of the present invention, whether the card corresponding to the unique number of the card, By using the pattern of attribution information such as discounts, it is easier to approve card transactions using electronic money in transportation card transactions and distribution for public transportation such as buses, subways and taxis. The memory capacity can be reduced by classifying the stored data and the non-stored data by using the pattern information of the corresponding attribute information, and compressing and generating the fixed data based on the pattern information. Prevents capacity explosion due to increase and enables update of change information Lee's easier to shorten the search time can be performed. In addition, even if the data is compressed and stored in the storage space, it is possible to quickly process the approval, and it is possible to easily manage the change of information to enable stable system operation.

In addition, the card transaction approval system, method, terminal and card transaction approval information management method, server, terminal, card transaction management server according to an embodiment of the present invention, the card included in the same block based on the unique number of each card The pattern information is changed or added by including the pattern information about the pattern format of the attribute information in the fixed data instead of being managed by the system, or by storing it separately from the fixed data but processing it as operational information rather than storing it in the system. Even if it is, it can be operated without changing the system.

While the present invention has been described in connection with what is presently considered to be the most practical and preferred embodiment, it is to be understood that the invention is not limited to the disclosed embodiments, but is capable of various modifications within the scope of the present invention. Therefore, the scope of the present invention should not be limited to the described embodiments, but should be defined not only by the claims below, but also by those equivalent to the claims.

10: card transaction management server 20: card transaction approval terminal
12: data generation unit 14: data storage unit
16: control unit 22: memory means
24: control means 100: fixed data of the prior art
500, 600, 650, 700: fixed data according to an embodiment of the present invention

Claims (19)

Based on the card's unique number, it is divided into blocks of a certain size Storing pattern information in which a pattern format of attribute information of the cards is stored;
Generating fixed data including header information including storage location information of each block and each pattern type information in the pattern information, and body information storing attribute information of a card in units of blocks based on the storage location information; Steps,
Determining whether to approve the transaction of the card based on the fixed data;
How to approve card transactions.
The method of claim 1,
The pattern type information corresponds to a pattern type stored in the pattern information.
The pattern type information for each block indicates the pattern format of attribute information of the cards included in the block.
How to approve card transactions.
The method of claim 1,
The pattern information is operational information that may be included in the fixed data or interlocked with the fixed data.
How to approve card transactions.
The method of claim 1,
The unique number is Alias No.
How to approve card transactions.
The method of claim 1,
The attribute information may be represented by flag information.
How to approve card transactions.
The method of claim 1,
The number of the pattern type is characterized in that 256
How to approve card transactions.
The method of claim 1,
If the attribute information of the cards included in any block is not the pattern type stored in the pattern information, the attribute information of the cards included in the block is stored in the body information, and the storage location information for the block is Indicating the storage location in the body information
How to approve card transactions.
The method of claim 1,
Determining whether or not to approve the transaction of the card based on the fixed data,
Recognizing the unique number of the card;
Retrieving attribute information corresponding to the unique number of the card from the fixed data including the body information;
Determining whether to approve the transaction of the card according to the retrieved attribute information.
How to approve card transactions.
The method of claim 8,
Wherein the searching comprises:
Calculating a block including a unique number of the recognized card;
Retrieving header information for the calculated block;
Retrieving storage location information and pattern type information for the calculated block.
How to approve card transactions.
The method of claim 9,
The retrieving the storage location information and the pattern type information may include:
If the storage location information of the block exists, the attribute information of the card stored in the body information is retrieved,
When the pattern type information of the block exists, the attribute information of the card is obtained from the pattern type information.
How to approve card transactions.
Storing pattern information in which a pattern format of attribute information of cards divided into blocks of a predetermined size is stored based on the unique number of the card;
Generating fixed data including header information including storage location information of each block and each pattern type information in the pattern information, and body information storing attribute information of a card in units of blocks based on the storage location information; Steps,
If the attribute information of the card is changed, determining a pattern of attribute information of the cards included in the block to which the card belongs;
Updating the fixed data according to the determined pattern;
How to manage card transaction authorization information.
The method of claim 11,
Wherein the updating comprises:
If the determined pattern is not the pattern type stored in the pattern information, the attribute information of the cards included in the block to which the card belongs is recorded at the last position of the body information, and the body information position information of the block to which the card belongs. Including updating the
How to manage card transaction authorization information.
The method of claim 11,
Wherein the updating comprises:
If the determined pattern is a pattern type stored in the pattern information, recording the pattern type in pattern type information of a block to which the card belongs;
How to manage card transaction authorization information.
The method of claim 11,
Wherein the updating comprises:
When the determined pattern type is a pattern type stored in the pattern information and the pattern of the corresponding block before the change is not a pattern type stored in the pattern information,
Deleting the corresponding block from the body information;
Deleting the block recorded at the last position of the body information, and recording the block recorded at the last position of the body information at the position where the corresponding block is deleted;
How to manage card transaction authorization information.
A pattern information in which a pattern format of attribute information of cards divided into blocks of a predetermined size is stored based on the unique number of the card, header information including storage location information of each block, and each pattern type information in the pattern information; Memory means for storing fixed data including body information in which attribute information of a card is stored in units of blocks based on the storage location information;
And controlling means for reading the attribute information corresponding to the unique number of the card from the fixed data stored in the memory means, and determining whether to approve the transaction of the corresponding card according to the read attribute information.
Card transaction approval terminal.
A pattern information in which a pattern format of attribute information of cards divided into blocks of a predetermined size is stored based on the unique number of the card, header information including storage location information of each block, and each pattern type information in the pattern information; A data generator configured to store fixed data including body information in which attribute information of the card is stored in units of blocks based on the storage location information;
And a control unit for transmitting the fixed data to a card transaction approval terminal.
Card Transaction Management Server.
A pattern information in which a pattern format of attribute information of cards divided into blocks of a predetermined size is stored based on the unique number of the card, header information including storage location information of each block, and each pattern type information in the pattern information; Memory means for storing fixed data including body information in which attribute information of a card is stored in units of blocks based on the storage location information;
A control means for determining the pattern of attribute information of the cards included in the block to which the card belongs, if the attribute information of the card is changed, and adding or deleting the updated attribute information in the fixed data according to the determined pattern; Containing
Card transaction approval information management terminal.
A pattern information in which a pattern format of attribute information of cards divided into blocks of a predetermined size is stored based on the unique number of the card, header information including storage location information of each block, and each pattern type information in the pattern information; A data generator configured to store fixed data including body information in which attribute information of the card is stored in units of blocks based on the storage location information;
If the attribute information of the card is changed, the control unit for determining the pattern of the attribute information of the cards included in the block to which the card belongs, and adds or deletes the changed attribute information in the fixed data in accordance with the determined pattern to include a control unit; doing
Card transaction authorization information management server.
A pattern information in which a pattern format of attribute information of cards divided into blocks of a predetermined size is stored based on the unique number of the card, header information including storage location information of each block, and each pattern type information in the pattern information; And a card transaction approval terminal for storing fixed data including body information in which attribute information of the card is stored in units of blocks based on the storage location information.
The card transaction approval terminal reads the attribute information corresponding to the unique number of the card from the fixed data stored in the memory means, and determines whether to approve the transaction of the corresponding card according to the read attribute information of the card.
Card transaction approval system.

Images