Method for providing test information, virtual collaborative device and system

Abstract

To provide a method that enables testing of outbound transactions by utilizing and verifying transactions that occur in a real transaction environment, a virtual cooperation device, and a system.SOLUTION: According to an embodiment, a method by which a virtual cooperation device provides test information includes steps of obtaining a transaction history between an existing device and a conventional cooperation device, obtaining, based on the transaction history, a first request provided from the existing device and a first response received from the conventional cooperation device in response to the first request, obtaining a second request corresponding to the first request from a new device and obtaining a second response corresponding to the second request, and providing test information for the new device based on a result of comparison between the first response and the second response.SELECTED DRAWING: Figure 3

Description

[Technical Field]

[0001] The present disclosure relates to a method, a virtual collaborative device, and a system for providing test information, and more particularly to a method, a virtual collaborative device, and a system for enabling testing of outbound transactions by utilizing transactions occurring in a real trading environment for validation. [Background technology]

[0002] Typically, when a particular system is developed, separate verification procedures are performed to ensure that the developed system is free of defects or faults.

[0003] However, conventional development system verification techniques have the disadvantage that developers or designers perform limited verification by manually generating verification cases using arbitrary virtual data or a small amount of actual data, or that even when using a large amount of actual data, the development of additional business-specific conversion programs is required.

[0004] In addition, in the case of conventional technology, when integrated verification is performed, a large number of managers gather together to manually perform mutual verification, which has the disadvantage of requiring a relatively large amount of time and cost to ensure the quality of the developed system through verification, and also has the disadvantage of limiting the number of people available to perform the verification.

[0005] In addition, in the case of outbound testing, since the internal business processing methods of the institution's system are not known, the same response is sent to all requests, or a separate test environment is often created in which individual programs are written to generate responses according to the content of the request, and test data is generated based on test scenarios created by developers or testers for each test case, which means that test cases that were not discovered before operation cannot be verified, and various requests that occur in the actual operating environment cannot be tested.If a direct test linkage with the system of a partner institution is planned to overcome these limitations, there are problems such as costs and time required to define the full text of test messages and negotiate test schedules.

[0006] Therefore, there is a growing demand for the development of development system verification technology that can deal with the vast number of cases that may occur in real-world environments in advance in all aspects of trading, and there is an urgent need to come up with solutions to the above-mentioned problems. Summary of the Invention [Problem to be solved by the invention]

[0007] One embodiment of the present disclosure is intended to solve the problems of the conventional technology described above, and may provide a method, a virtual collaborative device, and a system that enable testing of outbound transactions by performing verification using transactions that occur in a real trading environment.

[0008] The objects of the present disclosure are not limited to the above-mentioned objects, and other objects not mentioned will be clearly understood from the following description. [Means for solving the problem]

[0009] A method for providing test information by a virtual collaborative device according to a first aspect of the present disclosure includes: obtaining a transaction history between an existing device and a conventional collaborative device; and obtaining, based on the transaction history, a first request provided by the existing device and a first response received from the conventional collaborative device in response to the first request.

[0010] The method may include the steps of obtaining a second request from the new device corresponding to the first request and obtaining a second response corresponding to the second request, and providing test information to the new device based on a comparison result between the first response and the second response.

[0011] Also, the first request includes a full sentence including text arranged in a preset format.

[0012] In addition, the step of obtaining the second response may include a step of obtaining IP information and port information indicating the virtual collaborative device from the second request, a step of determining a business field indicated by the second request from the second request, a step of obtaining unique information indicating the second request from the second request, and a step of obtaining the second response based on the IP information, the port information, the business field, and the unique information.

[0013] The first request may include a request transmitted from the existing device to the conventional linked device during a previously set period of time.

[0014] In addition, the step of providing the test information may include a step of obtaining a plurality of first result values ​​indicated by the first response and a plurality of second result values ​​indicated by the second response, and a step of obtaining the test information determined based on the type and magnitude of error of different result values ​​among the first result values ​​and the second result values.

[0015] In addition, the step of obtaining the test information may include a step of categorizing the first result value according to characteristics of the conventional linked device, a step of comparing the first result value and the second result value by category, a step of obtaining an importance weight determined for each category, and a step of obtaining the test information based on the importance weight and the comparison result by category.

[0016] The importance weight may be determined according to the occurrence frequency for each category indicated by the second result value.

[0017] In addition, the step of obtaining the test information may include a step of determining a test score using importance weights that are determined differently for each category and a difference between the first result value and the second result value calculated for each category, and a step of outputting a warning message indicating that there is a serious error in the test together with the test information if the test score is less than a predetermined value.

[0018] In addition, the step of obtaining the first response may further include the steps of obtaining the first request from the transaction history, obtaining IP information and port information indicating the conventional linked device, a business field indicated by the first request, and unique information indicating the first request from the first request, and obtaining the first response from the transaction history via a matching key determined using the IP information, the port information, the business field, and the unique information.

[0019] The matching key may also be determined by a calculation that combines the IP information, the port information, the business field, and the unique information.

[0020] A virtual collaborative device that provides test information according to a second aspect of the present disclosure may include a memory that stores a transaction history between an existing device and a conventional collaborative device; and a processor that obtains a first request provided by the existing device and a first response received from the conventional collaborative device in response to the first request based on the transaction history, obtains a second request from a new device in response to the first request, obtains a second response in response to the second request, and provides test information for the new device based on a comparison result between the first response and the second response.

[0021] The first request may also include a full sentence including text arranged in a preset format.

[0022] In addition, the processor obtains IP information and port information indicating the virtual collaborative device from the second request, determines the business field indicated by the second request from the second request, obtains unique information indicating the second request from the second request, and obtains the second response based on the IP information, the port information, the business field, and the unique information.

[0023] The first request may include a request transmitted from the existing device to the conventional linked device during a previously set period of time.

[0024] The processor can also obtain a plurality of first result values ​​indicated by the first response and a plurality of second result values ​​indicated by the second response, and obtain the test information determined based on the type and magnitude of error of different result values ​​among the first result values ​​and the second result values.

[0025] The processor also categorizes the first result value according to the characteristics of the conventional linked device, compares the first result value and the second result value by category, obtains an importance weight determined for each category, and obtains the test information based on the importance weight and the comparison result by category.

[0026] The importance weight may be determined according to the occurrence frequency for each category indicated by the second result value.

[0027] The processor also obtains the first request from the transaction history, obtains from the first request IP information and port information indicating the conventional linked device, a business field indicated by the first request, and unique information indicating the first request, and can obtain the first response from the transaction history via a matching key determined using the IP information, the port information, the business field, and the unique information.

[0028] The matching key may also be determined by a calculation that combines the IP information, the port information, the business field, and the unique information.

[0029] A system for providing test information according to a third aspect of the present disclosure includes a database that stores a transaction history between an existing device and a conventional linked device; a new device that receives a first request provided by the existing device and a first response received from the conventional linked device in response to the first request based on the transaction history; and a virtual linked device that receives a second request corresponding to the first request from the new device and a second response corresponding to the second request, wherein the virtual linked device may provide test information to the new device based on a comparison result between the first response and the second response.

[0030] A fourth aspect of the present disclosure may provide a computer-readable recording medium having recorded thereon a program for causing a computer to perform the method according to the first aspect. Alternatively, a fifth aspect of the present disclosure may provide a computer program stored on a recording medium for implementing the method according to the first aspect. [Effects of the Invention]

[0031] According to an embodiment of the present disclosure, testing of outbound transactions can be effectively performed by performing verification using transactions that occur in a real trading environment.

[0032] In addition, testing can be performed regardless of time or message type, which is efficient in terms of the burden, cost, and time required for scheduling with partner systems required during the testing process.Since responses to outbound requests can be automated, the scope of work that can be subject to automated testing can be expanded.

[0033] Furthermore, by conducting tests using actual transaction messages, the same results can be obtained as if the business function were opened in advance without disclosing the test information to actual users. After the test, even those without business knowledge can easily check whether messages generated from the previous server have been processed in the same way on the current server, whether they remain unprocessed, and whether any further transactions have occurred, allowing for an immediate assessment of the test results.

[0034] The effects of the present disclosure are not limited to the effects described above, but should be understood to include all effects that can be inferred from the configuration of the invention described in the detailed description of the present disclosure or the claims. [Brief explanation of the drawings]

[0035] [Figure 1] 1 is a diagram illustrating a schematic configuration of a system for providing test information according to an embodiment. [Figure 2] FIG. 2 is a block diagram illustrating a configuration of a virtual cooperative device according to an embodiment. [Figure 3] 10 is a flowchart illustrating a method for a virtual collaborative device to provide test information according to one embodiment. [Figure 4] 1 is a flowchart illustrating a method for providing test information by a system for providing test information according to an embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0036] The present disclosure will now be described with reference to the accompanying drawings. However, the present disclosure may be embodied in various different forms and is not limited to the embodiments described herein. In addition, in order to clearly explain the present disclosure in the drawings, parts that are not relevant to the description are omitted, and similar parts are designated by similar reference numerals throughout the specification.

[0037] The terms used in the examples are currently widely used and general terms that have been selected as much as possible while taking into consideration the functions in the present disclosure, but these may vary depending on the intentions of engineers in the field, precedents, the emergence of new technologies, etc. In addition, in certain cases, the applicant may arbitrarily select terms, and in such cases, the meanings thereof will be described in detail in the relevant description of the invention. Therefore, the terms used in the present disclosure should be defined based on the meanings of the terms and the overall content of the present disclosure, rather than simply by the names of the terms.

[0038] Throughout this specification, when a part is said to be "connected" to another part, this includes not only when it is "directly connected" to another part, but also when it is "indirectly connected" through another member in between. Furthermore, when a part is said to "include" a certain component, this does not exclude other components, and means that it may further include other components, unless otherwise specified.

[0039] Throughout this specification, the term "provide" may be interpreted to include the process by which an object obtains specific information or transmits or receives it directly or indirectly to a specific object, and to comprehensively include the performance of any related actions required in that process.

[0040] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0023] The present disclosure will be described in detail below with reference to the accompanying drawings so that those skilled in the art can easily implement the present disclosure. However, the present disclosure may be embodied in various different forms and is not limited to the embodiments set forth herein.

[0041] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings.

[0042] FIG. 1 is a diagram illustrating a schematic configuration of a system 1000 for providing test information according to one embodiment.

[0043] Referring to FIG. 1, a system 1000 for providing test information according to one embodiment may include at least one of an existing device 100-1, a new device 100-2, a conventional collaborative device 300, and a virtual collaborative device 400.

[0044] Two or more of the existing device 100-1, the new device 100-2, the conventional cooperative device 300, and the virtual cooperative device 400 may be connected via a network. Here, the network may be configured regardless of communication type, such as wired or wireless, and may be configured from various communication networks, such as a local area network (LAN), a metropolitan area network (MAN), and a wide area network (WAN).

[0045] The virtual collaborative device 400 can obtain a transaction history between the existing device 100-1 and the conventional collaborative device 300. In one embodiment, the virtual collaborative device 400 can store and manage transactions between the existing device 100-1 and the conventional collaborative device 300 that occurred in the actual operating environment in the database 200. For example, each time a transaction occurs, the virtual collaborative device 400 can store a transaction message in the database 200, the transaction message including a request provided from the existing device 100-1 to the conventional collaborative device 300 and a response provided from the conventional collaborative device 300 to the existing device 100-1 in response to the request. In one embodiment, the transaction history can be interpreted as comprehensively including not only the request and response, but also user inputs transmitted and received during the request or response, transactions with a related authority server (not shown), and the like. For example, the database 200 can store all transaction data transmitted and received by the existing device 100-1 and / or the conventional collaborative device 300 in the actual operating environment.

[0046] The virtual coordination device 400 can obtain test information for the new device 100-2 based on the transaction history between the existing device 100-1 and the conventional coordination device 300. For example, the existing device 100-1 may correspond to an existing business system currently being used by an existing first company, the new device 100-2 may correspond to a new business system currently being developed by the first company (or a second company) due to reasons such as switching to a next-generation business system, and the conventional coordination device 300 may correspond to a coordination institution system connected to the existing device 100-1, which is the existing business system, and exchanging actual transaction messages. In this case, to test an outbound transaction, which indicates a transaction in which the existing business system first transmits a request message to the coordination institution system and receives a response message, the existing business system must communicate with the conventional coordination device 300, which is the coordination institution system. However, because the conventional coordination device 300 is currently connected to the existing device 100-1, it can be difficult to configure an environment for testing the outbound transaction. The virtual collaboration device 400 functions as a virtual collaboration system that stores transaction messages between the existing device 100-1, which is an existing business system, and the conventional collaboration device 300, which is a collaboration system, and provides an appropriate response message to a request message received from the new device 100-2, which is a new business system, based on the stored transaction message, thereby performing an outbound test on the new device 100-2. Thus, the transaction history of the outbound transactions between the existing device 100-1 and the conventional collaboration device 300, stored in the database 200, can be applied to the new device 100-2 to reproduce past outbound transactions between the new device 100-2 and the virtual collaboration device 400. During this reproduction process, the system analyzes whether an appropriate response is received in response to the request of the new device 100-2, and generates test information indicating whether the outbound transaction in response to the request of the new device 100-2 is operating properly. This will be described in more detail below with reference to FIGS. 2 to 4.

[0047] In one embodiment, the virtual collaborative device 400 may be understood as a concept including a server that operates via a computer program to implement the functions described herein.

[0048] The database 200 may be one component of the virtual collaborative device 400 and may store a transaction history between the existing device 100-1 and the conventional collaborative device 300. In one embodiment, the database 200 may store a transaction history received from the existing device 100-1, or in another embodiment, the database 200 may capture network packets sent and received between the existing device 100-1 and the conventional collaborative device 300, or may use a log file to acquire, store, and manage transaction messages.

[0049] The conventional linked device 300 is a device (e.g., an existing linked institution system) that is the outbound transaction target of the new device 100-2. In one embodiment, the conventional linked device 300 was the outbound transaction target of the existing device 100-1 in the past and sent and received transactions with the existing device 100-1, but may no longer exist due to a current discontinuation of operation.

[0050] The virtual collaborative device 400 is a device (e.g., a virtual collaborative institution system) that is a virtual outbound transaction target of the new device 100-2. In one embodiment, the virtual collaborative device 400 replicates the conventional collaborative device 300 as the outbound transaction target of the new device 100-2 according to a pre-stored algorithm based on the transaction history between the existing device 100-1 and the conventional collaborative device 300, and when a request is received from the new device 100-2, it can transmit a response to the received request.

[0051] In one embodiment, the existing device 100-1 and the new device 100-2 may each be embodied as a server, and may be understood throughout the specification as a conventional server and a current server, respectively.

[0052] In one embodiment, the system 1000 for providing test information may have included an existing device 100-1, a database 200, a conventional linked device 300, and a virtual linked device 400 in the past, and may have included a new device 100-2, a database 200, and a virtual linked device 400 in the present. For example, when an existing device 100-1, which is an existing business system, does not currently exist, a simulation of an outbound transaction between the new device 100-2 and the virtual linked device 400 may be performed in a state where only a transaction history collected in the past between the existing device 100-1 and the conventional linked device 300 is retained. The following description will focus on the above-described embodiment, but is not limited thereto, and various other embodiments may be used, such as a simulation performed in a state where both the existing device 100-1 and the new device 100-2 are present.

[0053] In addition to the components shown in FIG. 1, other general-purpose components may also be included in the system 1000 for providing test information, such as various other terminals or servers that send and receive transactions with the existing device 100-1 or the new device 100-2 for specific business purposes.

[0054] FIG. 2 is a block diagram showing the configuration of a virtual cooperative device 400 according to an embodiment.

[0055] Referring to FIG. 2, the virtual collaborative device 400 may include a memory 410 and a processor 420 .

[0056] According to one embodiment, the virtual collaborative device 400 may include a memory 410 that stores a transaction history between the existing device 100-1 and the conventional collaborative device 300, and a processor 420 that obtains a first request provided by the existing device 100-1 and a first response received from the conventional collaborative device 300 in response to the first request based on the transaction history, obtains a second request from the new device 100-2 in response to the first request, obtains a second response in response to the second request, and provides test information for the new device 100-2 based on a comparison result between the first response and the second response.

[0057] The above-mentioned series of operations and configuration will be described in detail below with reference to FIGS.

[0058] In one embodiment, the memory 410 may include a secondary storage device embodied as a non-volatile memory such as a solid state disk (SSD) or a hard disk drive (HDD) that can store information required for the overall operation of the virtual collaborative device 400, or a primary storage device embodied as a volatile memory such as a random access memory (RAM). In another embodiment, the memory 410 may include the database 200, which may be embodied as a separate storage server and may provide storage space for collecting transaction histories between the existing device 100-1 and the conventional collaborative device 300 via a wired or wireless communication network.

[0059] In one embodiment, the processor 420 may be embodied as a central processor unit (CPU) that can perform a series of operations to provide test information and control the overall operation of the virtual collaborative device 400, and may be electrically connected to the memory 410 and other components to control the flow of data therebetween.

[0060] 2, it will be understood by those skilled in the art that other general-purpose components may be included in the virtual collaborative device 400. For example, the virtual collaborative device 400 may further include a communication device for communicating with other devices (e.g., terminals or servers) via a network, an input / output interface for receiving user input or outputting information, and the like.

[0061] FIG. 3 is a flow chart illustrating a method for a virtual collaborative device 400 to provide test information according to one embodiment.

[0062] 3 , in step S310, the virtual collaborative device 400 may obtain a transaction history between the existing device 100-1 and the legacy collaborative device 300. In one embodiment, the transaction history may include transaction messages including requests provided by the existing device 100-1 to the legacy collaborative device 300 and responses received from the legacy collaborative device 300 in response to the requests.

[0063] In one embodiment, the virtual collaboration device 400 may capture network packets exchanged between the legacy device 100-1 and the legacy collaboration device 300 in the actual operating environment, convert the captured network packets into transaction messages consisting of requests and responses, and store and manage the requests, responses, and message identifiers in the database 200. For example, the virtual collaboration device 400 may record all transaction data in the database 200 in connection with an actual outbound transaction that occurs in the actual operating environment of the legacy device 100-1, including a user input requesting a transaction at a counter terminal, a request transmitted to the legacy collaboration device 300 to execute the transaction based on the user input, and a response received from the legacy collaboration device 300 after transactions with one or more collaboration institution (e.g., a card company, a VAN, etc.) servers in response to the request. In this manner, the virtual collaboration device 400 may continuously collect and manage a transaction history between the legacy device 100-1 and the legacy collaboration device 300 in the database 200 by collecting all transaction data related to the transaction each time a transaction occurs (or during a predetermined period).

[0064] In one embodiment, the transaction message may further include system information (e.g., collaborating institution information) and information for encryption and / or decryption of at least one of the request and response. For example, each transaction message may further include information for encryption or decryption required during the sending and receiving process in addition to common header information including the request, response, source / destination IP addresses, TCP port, message protocol, message length, etc. Therefore, a process of decrypting or encrypting the request or response may be further performed during the process of obtaining or using the request and response.

[0065] In operation S320, the virtual collaborative device 400 may obtain a first request provided by the existing device 100-1 and a first response received from the conventional collaborative device 300 in response to the first request based on the transaction history. For example, the virtual collaborative device 400 may use the transaction history to obtain a first request transmitted by the existing device 100-1 to the conventional collaborative device 300 and a first response transmitted by the conventional collaborative device 300 to the existing device 100-1 in response to the first request, and manage the first request and the first response using identifiers. When a user input requesting an outbound test for the new device 100-2 is received, the virtual collaborative device 400 may extract an identifier from the request for which the test is requested and query the database 200 for a response in a previously stored existing outbound transaction corresponding to the request.

[0066] In one embodiment, the first request and the first response may include multiple requests and multiple responses, respectively. In one embodiment, the first request may include multiple requests transmitted from the pre-existing device 100-1 to the conventional interconnected device 300 during a predetermined past period (e.g., a specific past day), and the first response may include multiple responses to the multiple requests received from the pre-existing device 100-1 to the conventional interconnected device 300 during that period. For example, when testing the new device 100-2 against requests transmitted from the pre-existing device 100-1 to the conventional interconnected device 300 during a specific past day in response to a user input, the virtual interconnected device 400 may extract from the transaction history all requests transmitted from the pre-existing device 100-1 to the conventional interconnected device 300 during the specified past day and all responses transmitted from the conventional interconnected device 300 to each of the requests.

[0067] In one embodiment, the first request may include a full sentence including text arranged according to a preset format. In one embodiment, the full sentence may include at least one of a number stream in which numbers are arranged consecutively and a character stream in which letters, etc. are arranged according to the number of digits and position-specific code defined in the full sentence interface. For example, the content format by number of digits may be defined in such a manner that the first M digits of the numbers arranged in the full sentence correspond to a request code (e.g., remittance, payment, etc.), the next N digits correspond to a user identifier, and the next O digits correspond to an account number. In one embodiment, the full sentence in the first request may be determined based on a first full sentence interface previously stored in the existing device 100-1 or the conventional linked device 300.

[0068] In one embodiment, the first request may include at least one of IP information and port information indicating the conventional linked device 300, a business field indicated by the first request, and unique information indicating the second request. In one embodiment, the IP information may include a source and / or destination IP address, and the port information may include TCP information used internally by the institution, and different values ​​may be assigned to the IP information and port information for each institution. In one embodiment, the business field may include a business key for identifying the type of business (e.g., remittance, payment) of the first request, and may include, for example, a unique serial number for each business used by the financial institution. In one embodiment, the unique information may include a unique identification key designated to identify the first request.

[0069] In one embodiment, the virtual collaborative device 400 obtains a first request from the transaction history, obtains IP information, port information, a business field, and unique information from the first request, and obtains a first response to the first request from the transaction history using a matching key determined using the IP information, port information, business field, and unique information. For example, in the process of storing and managing a first request and a first response previously transmitted and received between the existing device 100-1 and the conventional collaborative device 300 in the database 200, the virtual collaborative device 400 may extract a business key of a business field, such as an IP address, port information, or a number having a predetermined number of digits in the entire text, from the first request, determine a unique matching key by combining the extracted business keys, and match the first request and the first response using the matching key to store and manage them in the database 200. As a result, when a test is performed on the new device 100-2 using the first request stored in the database 200 in a subsequent stage, meaningful identification information can be extracted from the second request corresponding to the first request obtained from the new device 100-2 to find a matching key, and a response matching the request can be retrieved from the database 200 via the matching key.

[0070] In operation S330, the virtual collaborative device 400 may receive a second request corresponding to the first request from the new device 100-2 and obtain a second response. In one embodiment, the virtual collaborative device 400 may receive a second request for outbound testing from the new device 100-2, which reproduces a transaction to be tested with the same requirements as the existing transaction. The virtual collaborative device 400 may extract a matching key from the received second request in a manner similar to the above-described embodiment, retrieve a response (e.g., the first response) corresponding to the matching key from the database 200, and obtain the second response. If a conversion process is necessary, the virtual collaborative device 400 may convert the second response according to a structure and format defined in the new device 100-2 and transmit the converted response to the new device 100-2 to prepare for a test based on a real transaction.

[0071] In one embodiment, the virtual collaboration device 400 may convert the first response into a second response according to a format corresponding to the new device 100-2 based on the full-text interface. In another embodiment, the virtual collaboration device 400 may convert the first request received from the new device 100-2 into a second request based on the full-text interface. In one embodiment, the full text in the first response is determined based on a first full-text interface in a first format corresponding to the existing device 100-1 or the legacy collaboration device 300, and the full text in the second response is determined based on a second full-text interface in a second format corresponding to the new device 100-2 or including interface changes to the collaboration system previously stored in the virtual collaboration device 400. The first and second full-text interfaces may be different from each other. For example, the virtual collaborative device 400 obtains format information including a second full-text interface that defines the full text of the new device 100-2 through user input, compares the second full-text interface with a previously saved first full-text interface that defines the full text of the existing device 100-2, determines rule information for format conversion (e.g., changing the number of digits, adding a code, changing the content according to the number of digits, changing the value corresponding to the field name, changing the field name, etc.), and appropriately changes the parts of the full text of the first response that require changes to the new device 100-2 according to the rule information, thereby converting it into a second response.

[0072] In one embodiment, the virtual collaborative device 400 obtains IP information and port information indicating the new device 100-2 from the second request, determines the business field indicated by the second request from the second request, and obtains unique information indicating the second request from the second request. For example, the virtual collaborative device 400 may extract a business key of the business field, such as an IP address, port information, or a predetermined number of digits in the entire text, from the second request. In one embodiment, the IP information, port information, business field, and unique information obtained from the second request may correspond to the IP information, port information, business field, and unique information obtained from the first request, respectively, and in one embodiment, they may be identical to each other or at least partially different from each other.

[0073] In one embodiment, the virtual collaborative device 400 can obtain a second response based on the IP information, port information, business field, and unique information extracted from the second request. For example, the virtual collaborative device 400 can determine a matching key using the IP information, port information, business field, and unique information extracted from the second request, query the database 200 using the matching key to find a first response corresponding to the matching key, obtain the second response, and apply the second response to the new device 100-2.

[0074] In step S340, the virtual collaborative device 400 may provide test information for the new device 100-2 based on the comparison result between the first response and the second response. In one embodiment, the virtual collaborative device 400 may convert the message sent by the conventional collaborative device 300 into a message structure and format defined by the new device 100-2 in order to compare the first response and the second response. For example, the virtual collaborative device 400 may convert the first response by performing character set conversion, URL decoding, BASE64 decoding, decryption, message ID extraction and mapping, message item mapping and conversion, etc., and then compare the converted first response with the second response to test the real transaction infrastructure.

[0075] In one embodiment, the virtual collaborative device 400 can obtain a plurality of first result values ​​indicated by the first response and a plurality of second result values ​​indicated by the second response, and can obtain test information determined based on the type and magnitude of error of the different result values ​​among the first result values ​​and the second result values. For example, the virtual collaborative device 400 can reproduce, in the new device 100-2, a second request converted from a first request, including all requests transmitted from the existing device 100-1 to the conventional collaborative device 300 during a specific period (e.g., a specific one-day period) in the past when a test was requested, by performing the above steps. When the virtual collaborative device 400 obtains a second response based on the second request received from the new device 100-2, the virtual collaborative device 400 can analyze whether a subsequent transaction generated by the second response of the new device 100-2 was successfully processed, compare the second response with the first response of the conventional collaborative device 300, and, if different, analyze the type of fields or differences in parameter values ​​that differ by more than a predetermined value from the response or request, and generate test information related thereto. In one embodiment, the test information may include the contents of existing requests and responses, the contents of requests and responses that were ultimately used in the test through message conversion processing using existing messages, and the final success or failure of the message processing.

[0076] In one embodiment, the virtual collaborative device 400 may obtain test information for the new device 100-2 based on the result of comparing the second response (or second request) with the first response (or first request) converted into a format corresponding to the new device 100-2. For example, the virtual collaborative device 400 may convert the first response into a format corresponding to the second response using rule information (e.g., changing the number of digits, adding a code, changing the content according to the number of digits, etc.) used to convert the first request into a second request, compare the converted first response with the second response, and compare and analyze the degree to which the values ​​of each position-specific field, parameter, etc. differ from each other.

[0077] In one embodiment, the virtual collaborative device 400 may store detailed error information about a transaction in which an error equal to or greater than a preset value has occurred based on the comparison result, and may reflect the status of the message in the database 200. In one embodiment, the status of the message reflected in the database 200 may be managed as a status of not yet processed, in process, or completed.

[0078] In one embodiment, the virtual collaborative device 400 may categorize the first result value according to the characteristics of the conventional collaborative device 300 and compare the first result value and the second result value by category. For example, the first response and the second response may each include a plurality of responses, and each response may be expressed in one of a plurality of preset categories. For example, if the conventional collaborative device 300 is a server of an insurance company, the virtual collaborative device 400 may classify the first result value and the second result value according to a plurality of preset categories related to the insurance company (e.g., insurance type, maturity year, insurer age, etc.), and calculate the difference between the first result value and the second result value for each category.

[0079] In one embodiment, the virtual collaborative device 400 may obtain importance weights determined for each category and obtain test information based on the importance weights and the comparison results for each category. For example, different values ​​may be set for multiple categories and importance weights for each category depending on the type of institution (e.g., insurance company, bank, credit card company, etc.) corresponding to the conventional collaborative device 300. The virtual collaborative device 400 may calculate a test score based on the sum of the differences between the first and second result values ​​for each category, reflecting the importance weights.

[0080] In one embodiment, the importance weight may be determined based on the frequency of occurrence of each category indicated by the second result value. For example, if the conventional collaborative device 300 is a bank server, various transactions such as remittance, payment, and loan may occur, and the frequency of occurrence of the "balance" category may be higher than a preset value. In such a case, the virtual collaborative device 400 may assign the highest importance weight to the "balance" category, which has the highest frequency of occurrence, or may assign weights proportional to the frequency of occurrence to one or more categories, which have a frequency higher than a preset level, to calculate the test score.

[0081] In one embodiment, the virtual cooperative device 400 may assign a first importance weight when the difference between the first result value and the second result value is equal to or greater than a preset first value, assign a second importance weight when the occurrence frequency by category is equal to or greater than a preset second value, and assign a third importance weight to one or more specific categories determined as major categories according to the characteristics of the conventional cooperative device 300, and calculate a test score reflecting the first to third importance weights. In one embodiment, the first importance weight may be greater than the second importance weight, and the second importance weight may be greater than the third importance weight.

[0082] In one embodiment, when considering all transactions for a particular period, for example, one day, it may be difficult to consider transactions successful only if they are 100% identical during that period, so weights may be used as a way to compare transactions that are not all identical.

[0083] In one embodiment, the virtual collaborative device 400 may determine that the test failed if the test score is less than a first value, and may output a warning message along with the test information indicating that there is a critical error in the test if the test score is less than a second value that is less than the first value.

[0084] According to one embodiment of the present invention, even if the conventional collaborative device 300, which is an external institution, disappears in the future, the virtual collaborative device 400 may utilize past transactions to reproduce past requests on the new device 100-2, rather than creating a large number of test cases, and verify whether the new device 100-2 makes the request appropriately and whether the virtual collaborative device 400 responds appropriately to the request.

[0085] In addition, the virtual collaborative device 400 may be configured to mimic an actual transaction with an external institution upon request from the new device 100-2, thereby effectively simulating an outbound transaction of the new device 100-2 in a virtual environment based on the actual transaction platform.

[0086] FIG. 4 is a flow chart illustrating a method for providing test information by the system 1000 for providing test information according to one embodiment.

[0087] 4, in steps S401 to S403, the virtual collaborative device 400 may store a transaction history between the existing device 100-1 and the conventional collaborative device 300 in the database 200. In FIG. 4, each step is illustrated as an embodiment divided into a first part in which the virtual collaborative device 400 obtains the transaction history and a second part in which the virtual collaborative device 400 performs a test using the transaction history. However, this is not intended to be limiting, and various embodiments are possible, such as each operation being performed in the same virtual collaborative device 400 without requiring message transmission between internal components, or each operation being performed separately by multiple servers included in the virtual collaborative device 400.

[0088] In step S401, the existing device 100-1 may transmit a request to the conventional linked device 300 during an actual transaction in an actual operating environment, and in step S402, may receive a response to the request from the conventional linked device 300. For example, in the case of an outbound transaction, the existing device 100-1, which is an existing business system, transmits a request to the conventional linked device 300, which is a linked institution system, and receives a response to the request from the conventional linked device 300. In step S403, the virtual linked device 400 may capture transaction packets and log files, convert the captured data into requests and responses, and then store them in the database 200.

[0089] In step S403, the virtual collaborative device 400 may capture transactions, including requests and responses, between the existing device 100-1 and the conventional collaborative device 300 using transaction packets or a log file.

[0090] In step S404, the virtual collaborative device 400 may store all transaction data generated during the transaction process, including the first request and the first response corresponding to the first request, in the database 200 based on the capture data obtained through the capture. Thereafter, as similar steps are repeated in an actual operating environment, transaction data from actual transactions between the existing device 100-1 and the conventional collaborative device 300 may be continuously collected in the database 200.

[0091] In one embodiment, the virtual collaborative device 400 may generate a matching key by combining IP information, port information, business field, and unique information extracted from the first request transmitted from the existing device 100-1 to the conventional collaborative device 300, and manage the matching relationship between the first request and the first response stored in the database 200 through the matching key.

[0092] In steps S405 to S408, when the existing device 100-1 and / or the conventional collaborative device 300 are not currently present, or based on a test environment constructed for outbound testing, the virtual collaborative device 400 may be tested against the new device 100-2, which is a new business system, while retaining the transaction history that has previously taken place between the existing device 100-1 and the conventional collaborative device 300.

[0093] In step S405, the virtual collaborative device 400 may receive a second request from the new device 100-2. For example, the new device 100-2 may reproduce a test transaction with the same requirements as the existing transaction, and transmit the second request to the virtual collaborative device 400. Although FIG. 4 omits outbound testing for convenience, an embodiment may also include an embodiment in which a second request obtained from the first request stored in the database 200 is transmitted from the virtual collaborative device 400 to the new device 100-2, and an inbound test is performed based on the transaction history.

[0094] In step S406, the virtual collaborative device 400 may query a response corresponding to the second request and obtain the second response through conversion. For example, the virtual collaborative device 400 may determine a matching key using identification information extracted from the second request, query a response corresponding to the matching key from among multiple responses stored in the database 200, and if a conversion process is required, convert the queried response according to a full-text interface to obtain the second response.

[0095] In step S407, the virtual collaborative device 400 may apply the second response to the new device 100-2.

[0096] In operation S408, the virtual collaborative device 400 can obtain test information for the new device 100-2 based on the comparison result between the first response and the second response. For example, a comparative analysis of the existing device 100-1 and the new device 100-2 can be performed using the second response transmitted from the virtual collaborative device 400 to the new device 100-2. A comparative analysis of the existing system and the system to be verified can be performed by converting the first response into a format compatible with the new device 100-2 and then comparing it with the second response, or by comparing the first request and the second request. Testing of subsequent transactions generated by the responses can also be performed. For example, test information including the results of comparison and analysis of whether the second response of the new device 100-1 was successfully processed in response to the second request, whether the second response is compared with the first response of the conventional collaborative device 300 and is consistent, whether the second request is compared with the first request of the existing device 100-1 and is consistent, and if there are differences, the types of fields that differ by more than a preset value, differences in parameter values, etc., can be generated, recorded, and displayed.

[0097] According to one embodiment, in the process of a loan application and loan review transaction, for example, when a user requests a loan application transaction, the existing device 100-1 may request an outbound transaction related to the review application from a review agency after processing its internal logic, and may receive a response regarding the review result from the review agency, i.e., the conventional linked device 300. In this case, the virtual linked device 400 may capture the transaction between the existing device 100-1 and the conventional linked device 300, store a transaction message including the request and the response in the database 200, and store and manage the transaction together with an identifiable message identifier (e.g., a matching key, unique information, etc.).

[0098] Thereafter, the new device 100-2 can reproduce a transaction with the same requirements as the existing transaction between the existing device 100-1 and the conventional interconnected device 300 for an outbound test to the conventional interconnected device 300, and transmit a second request to the virtual interconnected device 400 instead of the conventional interconnected device 300. The virtual interconnected device 400 can generate a matching key using identification information extracted from the received second request, query the database 200 for a second response corresponding to the second request, and compare the second response with the first response to perform a test. If the test result is successful, the new device 100-2 can receive the same response as the existing institution, even without communication with the conventional interconnected device 300, which is the existing interconnected institution.

[0099] In addition, after testing the transaction requesting review, the virtual collaborative device 400 may identify cases requiring further analysis other than transactions that were processed successfully, compare message identifiers (e.g., matching keys) based on the actual transaction data already stored to identify review transaction messages that did not occur in the new device 100-2, and analyze the reason why they did not occur in the new device 100-2.

[0100] In addition, when the virtual collaborative device 400 receives an actual transaction message for which a test is requested and not stored in the database 200, the virtual collaborative device 400 may provide a comparison result for the conditions under which the request was received. For example, in the case of a transaction requesting a test that is not stored in the database 200 but is input to the new device 100-2, the virtual collaborative device 400 may analyze the conditions under which the request was made that differ from those of the existing device 100-1, and generate a comparison result between the existing device 100-1 and the new device 100-2.

[0101] As a result, when it is necessary to test the outbound transactions of the new device 100-2 due to the development of a new business system or changes to the collaboration institution system, the virtual collaboration device 400 may test the outbound function of the new device 100-2 by replicating the operation of the conventional collaboration device 300 based on actual transaction data between the existing device 100-1 and the conventional collaboration device 300 and transmitting a response corresponding to the request of the new device 100-2.

[0102] As described above, the order and combination of steps shown in the figures are one embodiment, and it will be understood that the order, combination, branching, functions and their performers may be added, omitted or modified in various ways within the scope that does not deviate from the essential characteristics of each component described in the specification.

[0103] Meanwhile, the above-described methods can be created as a computer-executable program and can be implemented on a general-purpose digital computer that runs the program using a computer-readable recording medium. Furthermore, data structures used in the above-described methods can be recorded in various ways on a computer-readable recording medium. Computer-readable recording media include storage media such as magnetic storage media (e.g., ROM, RAM, USB, floppy disk, hard disk, etc.) and optically readable media (e.g., CD-ROM, DVD, etc.).

[0104] The above description of the present disclosure is for illustrative purposes only, and those skilled in the art will understand that the present disclosure can be easily modified into other specific forms without changing the technical spirit or essential features of the present disclosure. Therefore, the above-described embodiments should be understood to be illustrative in all respects and not restrictive. For example, each component described as a single component may be implemented in a distributed form, and similarly, components described as distributed may be implemented in a combined form.

[0105] The scope of the present disclosure is defined by the claims that follow, and all modifications and variations that fall within the meaning and scope of the claims and their equivalent concepts should be construed as being included within the scope of the present disclosure. [Explanation of symbols]

[0106] 1000 Test Information Providing System 100-1 Existing Devices 100-2 New Device 410 memory 420 processor 200 databases 300 Conventional linked devices 400 Virtual Collaboration Devices

Claims

1. 1. A method for a virtual collaborative device to provide test information, comprising: obtaining a transaction history between the existing device and a conventional linked device; obtaining a first request provided by the existing device based on the transaction history and a first response received from the conventional linked device in response to the first request; obtaining a second request from the new device corresponding to the first request and obtaining a second response corresponding to the second request; providing test information for the new device based on a comparison of the first response and the second response; The step of obtaining the second response comprises: obtaining IP information and port information indicating the virtual collaborative device from the second request; determining a business field indicated by the second request from the second request; obtaining unique information indicating the second request from the second request; obtaining the second response based on the IP information, the port information, the business field, and the unique information; Including, method.

2. The method of claim 1 , wherein the first request includes a full sentence containing text arranged according to a predefined format.

3. The method of claim 1 , wherein the first request comprises a request transmitted from the pre-existing device to the legacy cooperative device during a previously established period of time.

4. The step of providing test information comprises: obtaining a plurality of first result values ​​indicated by the first response and a plurality of second result values ​​indicated by the second response; and obtaining the test information determined based on the types and magnitudes of errors of different result values ​​from the first result value and the second result value.

5. The step of obtaining test information comprises: categorizing the first result value according to a characteristic of the conventional linked device; comparing the first result value and the second result value categorically; obtaining a weight of importance determined for each category; and deriving the test information based on the importance weights and the categorical comparison results.

6. The importance weight is The method of claim 5 , wherein the frequency of occurrence of each of the categories indicated by the second result value is determined.

7. The step of obtaining test information comprises: determining a test score using the weight of importance determined differently for each category and the difference between the first result value and the second result value calculated for each category; 6. The method of claim 5, further comprising: if the test score is less than a predetermined value, outputting a warning message together with the test information indicating that there is a serious error in the test.

8. The step of obtaining a first response comprises: obtaining the first request from the transaction history; obtaining IP information and port information indicating the conventional linked device, a business field indicated by the first request, and unique information indicating the first request from the first request; The method of claim 1 , further comprising: obtaining the first response from the transaction history through a matching key determined using the IP information, the port information, the business field, and the unique information.

9. The matching key is The method of claim 8 , wherein the IP address is determined by a calculation that combines the IP address, the port address, the transaction field, and the unique address.

10. A virtual collaborative device that provides test information, a memory for storing a transaction history between the existing device and a conventional linked device; obtaining a first request provided by the existing device based on the transaction history and a first response received from the conventional linked device in response to the first request; obtaining a second request from the new device corresponding to the first request and obtaining a second response corresponding to the second request; a processor that provides test information for the new device based on a comparison of the first response and the second response; The processor: Obtaining IP information and port information indicating the virtual collaborative device from the second request; determining a business field indicated by the second request from the second request; obtaining unique information indicating the second request from the second request; obtaining the second response based on the IP information, the port information, the business field, and the unique information; Virtual collaborative devices.

11. The virtual collaborative device of claim 10 , wherein the first request includes a full sentence including text arranged in a preset format.

12. The virtual collaborative device of claim 10 , wherein the first request includes a request transmitted from the existing device to the conventional collaborative device during a previously set period of time.

13. The processor: obtaining a plurality of first result values ​​indicated by the first response and a plurality of second result values ​​indicated by the second response; The virtual collaborative device according to claim 10 , wherein the test information is determined based on the types of different result values ​​between the first result value and the second result value and the magnitude of an error.

14. The processor: categorizing the first result value according to characteristics of the conventional linked device; comparing the first result value and the second result value by category; Obtaining the weights of importance determined for each category, The virtual collaborative device of claim 13 , wherein the test information is obtained based on the importance weights and the categorical comparison results.

15. The importance weight is The virtual collaborative device according to claim 14 , wherein the second result value is determined according to the frequency of occurrence of each of the categories indicated by the second result value.

16. The processor: obtaining the first request from the transaction history; Obtaining IP information and port information indicating the conventional linked device from the first request, a business field indicated by the first request, and unique information indicating the first request; The virtual collaborative device of claim 10 , wherein the first response is obtained from the transaction history through a matching key determined using the IP information, the port information, the business field, and the unique information.

17. The matching key is The virtual collaboration device of claim 16 , wherein the virtual collaboration device is determined by a calculation that combines the IP information, the port information, the business field, and the unique information.

18. 1. A system for providing test information, comprising: a database that stores transaction history between existing devices and traditional linked devices; a new device that obtains a first request provided by the existing device based on the transaction history and a first response received from the conventional linked device in response to the first request; a virtual cooperative device that receives a second request from the new device corresponding to the first request and receives a second response corresponding to the second request; the virtual collaborative device provides test information to the new device based on a comparison result between the first response and the second response; Obtaining IP information and port information indicating the virtual collaborative device from the second request; determining a business field indicated by the second request from the second request; obtaining unique information indicating the second request from the second request; obtaining the second response based on the IP information, the port information, the business field, and the unique information; system.

Images