KR102379919B1 - Interface management system and method for supporting communication between a plurality of devices - Google Patents

Abstract

According to an embodiment of the present invention, there is provided a method for integrated management of different message (message) interfaces among distributed internal servers and M x N servers of external organizations, and a system implementing the same.

Description

INTERFACE MANAGEMENT SYSTEM AND METHOD FOR SUPPORTING COMMUNICATION BETWEEN A PLURALITY OF DEVICES

The present invention relates to a method for integrated management of different message (message) interfaces between distributed internal servers and M x N servers of external organizations, and to a system implementing the same.

Currently, for business service transactions with servers of external organizations, the message (professional) interface is managed in a layout subordinate to the organization's work. It may be easy to configure to identify the format of a specialist subordinate to a specific institution among external institutions, but there is a complexity that can only be found directly as a specific type of black box structure rather than an integrated interface management from the perspective of overall operation.

There are various types of messages (messages), such as a fixed-size message format, an international financial message standard format (ISO8583), JSON, and XML. In particular, in the case of a processing broker such as BC Card, since service transactions are made with various companies such as financial institutions, IT institutions, and public institutions, all types of message types must be processed.

Since each external organization uses the same type of message format, it is easy to manage as a single information subordinate to the organization. In order to simultaneously process a message type different from the standard, which is not a standard format that is dependent on a specific institution, it is common to process the rule of the exception handling format in a form that is dependent on the relevant institution. Soon, the management of the relevant institution with an exception outside the management scope of 'hard coding' rather than the standardized format is derived from the interface management problem expressed within the current financial institution. It has to be limited to a specific institution or the same type of institution, and it is operated in a form that cannot be managed in an integrated way.

For example, there are two forms of BC Card payment approval text. VAN must be provided as magnetic approval transaction and IC approval transaction as approval transaction for service communication with BC card. However, these two formats operate as completely different types of formats:

professional name Length format example MS approval fix text 010000000000000000000000000000000000000001100000000004000000000400001091003701000019390001161700352137880003230+ ******** 0000002137B9100370100001939=22060000000000000**************** IC approval variable ISO8583 'BCINTMSG0001\x03\x00\xf28f\x81\x08B\x82\x10\x00\x00\x00\x00\x00\x00\x04\x00\x10U\x96 \x00#yR\x92\x01\x10\x00\x00 \x00\x00\x00\x00\x00%\x00\x12\x04\x00\x00\x01\x99we\x00\x00\x01\x12\x04\x00\x00\x04\x10\x05\x00\x00\ x01\x00\x05\x002%

The two messages are transmitted as transactions of different message types in their own format. The former is a fixed-size text format layout, and the latter is a variable-length ISO8583 full text. In the text format of fixed size, the type of transaction can be determined by reading only a specific location, but in the case of ISO8583 text, the fixed location is a bitmap that determines whether the field is used and the packed data is parsed after parsing. should be used For this purpose, when implementing the program, the program can be used only in cases limited to the VAN company, and when implementing other types of professional services, it is impossible to avoid tight coupling, which must be developed separately.

The present invention is to solve the problems of the prior art, and a method for integrated management of different message (message) interfaces between distributed internal servers and M x N servers of external organizations and a system implementing the same is intended to provide

In addition, the present invention relates to an EIMS (Enterprise Interface Management System), and an object of the present invention is to provide a method for integrated management and distribution of information on a telegram, a linkage system, and a message interface, and a system implementing the same.

Objects of the present invention are not limited to the objects mentioned above, and other objects not mentioned will be clearly understood from the description below.

According to an embodiment of the present invention, a method and system for managing the EIMS architecture and meta code information through the EIMS architecture and registration / management / distribution process are provided.

According to another embodiment of the present invention, a method and system for managing an EIMS message through a plurality of layout integrated management schemes corresponding to the same message number are provided.

According to another embodiment of the present invention, there is provided a method and system for managing EIMS interface information through a flexible interface management/operation scheme and a management scheme for message mapping in which the dependency of a message layout is removed.

According to another embodiment of the present invention, a method and a system for managing an EIMS interface distribution are provided through a method for distributing an interface in an EIMS and managing the same.

According to another embodiment of the present invention, a method and system for managing data modulation is provided.

In the method for supporting communication between a plurality of devices according to the first aspect of the present disclosure, the method includes (a) when the interface management system obtains data field attribute information for communication between the plurality of devices as a user input , registering the full request and response text including the data field attribute information, and (b) the interface management system maps predetermined transaction information to the registered request text and response text to obtain interface configuration information It may include the step of generating.

In addition, the method may further include the step of (c) providing, by the interface management system, the generated interface configuration information to at least one device to be referenced during communication between the plurality of devices or storing the information in a DB.

In addition, in step (c), the message automatically converted by referring to the provided or stored interface configuration information is used during communication between the plurality of devices, so that communication can be made smoothly between devices using a message in a different format. .

In addition, the generated interface configuration information includes first interface configuration information and second interface configuration information, and when an external request message is received from an external device, the first interface configuration information is referenced to the external request message. A corresponding internal standard request message is generated, the second interface configuration information is referred to, and as a result of processing the internal standard request message, an external response message corresponding to the internal standard response message is generated and transmitted to the external device.

In addition, the external device may include at least one of a Front End Processor (FEP), a Multiple Channel Interface (MCI), and an Enterprise Application Integration (EAI).

In addition, when the external request message from the external device is received, when the service request content is not identified only with the specific field information of the external request message or the corresponding internal standard request message, the external request message or the internal standard request message The content of the service request may be identified by referring to the remaining payload.

In addition, the interface configuration information may be provided to at least one UI terminal in a pull method.

In addition, the full text of the request or the full response of the response may include a text of a variable length, and the text of the variable length may include at least one bitmap information field and a packing data field.

According to a second aspect of the present disclosure, there is provided an interface management system supporting communication between a plurality of devices, the interface management system comprising: an input/output unit configured to obtain data field attribute information for communication between the plurality of devices through a user input; and a control unit that registers a request full text and a response text including the data field attribute information, and generates interface configuration information by mapping predetermined transaction information to the registered request text and response text.

Also, the controller may provide the generated interface configuration information to at least one device or store it in a DB to be referenced during communication between the plurality of devices.

In addition, the control unit can support communication between devices using different formats of the telegrams smoothly by allowing the automatically converted telegram to be used with reference to the provided or stored interface configuration information during communication between the plurality of devices.

In addition, the generated interface configuration information includes first interface configuration information and second interface configuration information, and the controller refers to the first interface configuration information when an external request message is received from an external device and refers to the external configuration information. It is possible to generate an internal standard request message corresponding to the request message, and generate an external response message corresponding to the internal standard response message as a result of processing the internal standard request message by referring to the second interface configuration information to be transmitted to the external device. .

In addition, the external device may include at least one of FEP, MCI, and EAI.

In addition, when the external request message from the external device is received, when the service request content is not identified only with specific field information of the external request message or the internal standard request message corresponding thereto, the external request message or the internal standard The content of the service request may be identified by referring to the remaining payload of the request text.

Also, the controller may provide the interface configuration information to at least one UI terminal in a pull method.

In addition, the full text of the request or the full response of the response may include a text of a variable length, and the text of the variable length may include at least one bitmap information field and a packing data field.

According to an embodiment of the present invention, by providing a method for integrated management of different message (message) interfaces between distributed internal servers and M x N relational servers of external institutions, and a system implementing the same, the prior art is effective in solving the problems of

The effects of the present invention are not limited to the above effects, but it 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 invention.

1 is a diagram illustrating a registration/distribution procedure for an interface and a message in EIMS according to an embodiment of the present invention.
2 is a diagram illustrating the configuration of an EIMS system according to an embodiment of the present invention.
3 is a diagram illustrating management interface configuration information of an EIMS according to an embodiment of the present invention.
4 is a diagram illustrating a page for managing a transmission/reception system according to an embodiment of the present invention.
5 is a diagram illustrating a page for managing an application according to an embodiment of the present invention.
6 is a diagram illustrating a page for managing a transaction code according to an embodiment of the present invention.
7 is a diagram illustrating a page for managing a business code according to an embodiment of the present invention.
8 is a diagram illustrating a page for managing an organization code according to an embodiment of the present invention.
9 is a diagram illustrating a page for managing meta information according to an embodiment of the present invention.
10 is a diagram illustrating a configuration for managing an EIMS message according to an embodiment of the present invention.
11 is a diagram illustrating ISO8583 header/body text attributes according to an embodiment of the present invention.
12 is a diagram illustrating layout attributes required for ISO8583 header/body full text definition according to an embodiment of the present invention.
13 is a diagram illustrating a configuration for managing EIMS interface information according to an embodiment of the present invention.
14 is a diagram illustrating full text mapping information according to an embodiment of the present invention.
15 is a diagram illustrating a page for managing a mapping function according to an embodiment of the present invention.
16 is a diagram illustrating a configuration for processing a routing exception condition according to an embodiment of the present invention.
17 is a diagram illustrating a page for managing a distribution system according to an embodiment of the present invention.
18 is a block diagram illustrating an example of the configuration of an interface management system according to an embodiment of the present invention.
19 is a flowchart illustrating an example of a method in which the interface management system shown in FIG. 18 supports communication between a plurality of devices.

Hereinafter, the present invention will be described with reference to the accompanying drawings. However, the present invention may be embodied in several different forms, and thus is not limited to the embodiments described herein. And in order to clearly explain the present invention in the drawings, parts irrelevant to the description are omitted, and similar reference numerals are attached to similar parts throughout the specification.

Throughout the specification, a message is an expression format of request data and response data for a service on a network basis.

In addition, an interface is an attribute unit of data transaction generated based on a message.

In addition, a transaction is a network data exchanged between both ends of the server as an actual transaction of the interface.

In addition, EIMS (Enterprise Interface Management System) is a meta management system for professional services such as professional layout of service transaction related to the interface, agency information, agency work information, and professional mapping information.

In addition, FEP (Front End Processor) is an application network channel system for server combat to provide professional services with external organizations, and is responsible for organization operation information, internal and external professional layout editing and mapping, etc.

In addition, MCI (Multiple Channel Interface) is a system for processing specialized transactions between various types of internal systems, and is a channel system for processing session management for UI terminals, and complex transaction relay for transactions between upper managers and departments.

In addition, EAI (Enterprise Application Integration) is an enterprise-wide application integration management system that handles business integration between multiple systems, and MCI operates as an internal channel integration process based on professional data, but EAI is directly entrusted with the process as a broker between systems. handle

Hereinafter, embodiments of the present invention will be described in detail for each configuration of the invention.

Management of EIMS architecture and meta-code information

EIMS (Enterprise Interface Management System) is a solution that designs and manages interfaces and messages. Provides functions necessary for interface design and management, and provides interface distribution with other linked systems. The information required for interface management is linked to the meta system and the information (terms, codes, etc.) registered in the meta system is used.

1 is a diagram illustrating a registration/distribution procedure for an interface and a message in EIMS according to an embodiment of the present invention. The registration/distribution procedure for the interface and the telegram in the EIMS is as shown in FIG. 1 .

2 is a diagram illustrating the configuration of an EIMS system according to an embodiment of the present invention. The configuration of the EIMS system is as shown in FIG. 2 .

The distribution target systems are as follows.

deployment target system explanation internal channel Systems related to internal interfaces (Ex: MCI, EAI, F/W, etc.) external channels System related to external interface (Ex: FEP, EAI, F/W, etc.) F/W System related to internal/external interface UI System related to internal interface other systems Unit system responsible for other solutions

In the distribution method, both push and pull methods are provided as follows.

deployment target system Distribution method internal channel HTTP Push method in EIMS external channels HTTP Push method in EIMS F/W HTTP Push method in EIMS UI terminal HTTP Pull method in UI

In the case of connecting as a number of unspecified client roles, such as UI terminals, efficient distribution is possible only when the EIMS is operated in a pull method from the client's point of view rather than a push.

3 is a diagram illustrating management interface configuration information of an EIMS according to an embodiment of the present invention. The management interface configuration information of the EIMS is shown in FIG. 3 .

The interface configuration information is as follows.

turn Component explanation One interface ID - Interface ID is automatically numbered by combining application information, sending/receiving system information, etc.
- Interface definitions created in Excel at the design stage are registered in batches, and interface IDs are numbered at the time of registration. 2 interface details - There is a difference in the detailed attribute items managed by each type (MCI, EAI, etc.)
- For a detailed description of the detailed attribute items for each interface type, see “5. Refer to “EIMS Interface Management” 3 Transmission system specialized information - Manage request messages and response messages in units of sending and receiving systems
- Management of the professional itself is provided through the professional management function
- Professional management is “4. Refer to “EIMS Professional Management” 4 Professional Mapping Information -Provides a full text mapping function for cases where the request text or response text layout is different between the systems defined in the interface
- Full text mapping is designated in units of request text and response text 5 Distribution system and distribution history - Interface information managed by EIMS is distributed to the system designated by each interface ID unit
- When deploying to multiple systems, if there is no response from a specific system, the entire rollback is processed.

The management functions of EIMS are as follows.

turn top menu sub menu explanation One professional management professional management Commonly manage the full text used in the interface External Expertise Professional inquiry related to external channels 2 Internal interface management Internal MCI interface Register and manage internal MCI-related interfaces Internal EAI interface Register and manage internal EAI-related interfaces 3 External interface management External FEP interface External FEP-related interface registration management External file transfer Register and manage external file transfer interface 4 Manage configuration information Distribution system management Manage interface deployment target systems Send and receive system management Manage the sending/receiving system required for interface registration Application code management Manage application code required for interface registration Transaction Code Management Manage the transaction code required for interface registration business code management Manage the business code required for interface registration Agency Code Management Manage the institutional code required for interface registration Meta information management Manage meta information required for professional registration Mapping function management Manage mapping functions required for professional mapping 5 history management Action history management Manage interface and professional related performance history 6 Preferences User Management Manage registration of EIMS users role management Manage EIMS user roles Permission Management Manage privileges according to EIMS user roles

In EIMS configuration information management, EIMS registers and manages code information necessary for interface design through configuration information management. Codeability data is automatically updated in connection with Meta.

In meta management, the transmission/reception system management manages the transmission/reception system required for interface definition.

4 is a diagram illustrating a page for managing a transmission/reception system according to an embodiment of the present invention. The transmission/reception system management page is shown in FIG. 4 .

The attribute description is as follows.

attribute name explanation Transceiver system code Transceiver system code Transmission system name Sending/receiving system name explanation explanation

Application code management is as follows. Manages standardized application code (L3) required for interface definition.

5 is a diagram illustrating a page for managing an application according to an embodiment of the present invention. The application management page is as shown in FIG. 5 .

The attribute description is as follows.

attribute name explanation Required? Remarks (example) application code application code Y application code name application code name Y upper application code parent application code Y level code level code Y explanation explanation N

Transaction code management is as follows. Manages transaction codes required for interface definition.

6 is a diagram illustrating a page for managing a transaction code according to an embodiment of the present invention. The transaction code management page is as shown in FIG. 6 .

The attribute description is as follows.

attribute name explanation Required? transaction code transaction code Y Transaction code name Transaction code name N Management system code management system code Y explanation explanation N

In business code management, business codes required for interface definition are managed.

7 is a diagram illustrating a page for managing a business code according to an embodiment of the present invention. The business code management page is as shown in FIG. 7 .

The attribute description is as follows.

attribute name explanation Required? work code work code Y work code name work code name Y explanation explanation N

Institutional code management is as follows. Manage the agency code as a separate internal code for the agency required for interface definition.

8 is a diagram illustrating a page for managing an organization code according to an embodiment of the present invention. The organization code management page is as shown in FIG. 8 .

The attribute description is as follows.

attribute name explanation Required? agency code agency code Y Organization code name Organization code name Y division of organs division of organs Y explanation explanation N

Meta information management is as follows. Manage meta information necessary for professional definition (linked with Meta system).

9 is a diagram illustrating a page for managing meta information according to an embodiment of the present invention. The meta information management page is as shown in FIG. 9 .

The attribute description is as follows.

attribute name explanation meta english name meta english name Meta Korean name Meta Korean name type type Length Length Scale Scale influence Impact analysis popup according to term change

EIMS professional management function

The text is managed by classifying it into fixed layout (FIXED) and variable text (ISO8583, JSON, XML, etc.) layouts according to the data expression format. In the existing professional management method, each layout was defined and operated on two servers for performing a request and a response for a service in order to manage a request and a response for one service. Here, in the role of the service requester for the service and the service responder who provides the processing result for the service request, the service requester only needs to request one layout per service. When a service requester requests to create various services, if it is configured as a separate process under an independent network, the service responder can be implemented to parse each layout by separating the professional layout. However, a server that provides various services for different purposes under the management of various network protocols (X.25, TCP, HTTP, etc.), various specialized formats (fixed length, variable length), and various specialized layouts under non-independent network environments An information management plan as an integrated management entity that is not subordinate to other companies is needed.

In professional version management, multiple layouts for the same service are managed. BC Card manages and operates professional layouts for about 31 customers. We are operating a service with a professional number '1100' for customer approval transaction services. According to the guide and layout initially distributed by our company, all customers were operated in a common data format, but recently, various types of individual services have been requested. Even if the same 1100 professional service is provided, each customer's own field is additionally operated rather than a common layout among the initially deployed customers.

10 is a diagram illustrating a configuration for managing an EIMS message according to an embodiment of the present invention.

In general, in order to handle exceptionally separate layouts, when analyzing the layout of the text, hard coding for each additional exception or processing dependent on the service process should be specified. This is a black box, which increases complexity in a form that cannot be integrated across the company. In order to solve this problem, EIMS introduced an independent interface concept independent of professional layout without operating exceptional hard coding for specialized layout processing for each institution. (Refer to EIMS interface information management, which will be described later)

As all organizations operate with the same professional number (category code), each operates an individual layout, so individual services can be provided. In addition, by separating the professional layout and interface properties, the area for the common field for professional management is defined, and only additional fields need to be defined by inheriting it.

For professional layout management, common headers are as follows.

In the case of operating multiple services with external organizations, in general, a telegram number is identified to identify the service requested by the telegram. In addition, it defines a common part, such as a header common to external organizations, such as a transaction identification number for matching a request transaction and a response transaction, and information on the requested identification subject. In EIMS, the external specialized DTO item is operated so that the layout of the common part for each institution and the individual part of the professional service can be used as it is in the framework. By using this, it is possible to map the external text as it is without defining the internal data corresponding to the external text layout and use it as a VO (Value Object).

turn function explanation One External version management Support when the layout is different for the same telegram in the external message 2 Reuse of external F/W Support reuse of foreign texts in F/W by using “external text DTO” item

The management of the identification attributes of the common part of the full text is as follows. The detailed attributes that designate the external message to be identified so that it can be used as data in the standard format for public content in EIMS are as follows.

attribute name explanation Required? Channel Classification Code to distinguish channels that use full text Y Transaction Classification Code to distinguish between professional transaction types Y professional type professional classification code Y Professional ID ID to identify the full text, and automatically number according to the numbering rules N/A professional name A professional name by which the full text can be identified N professional version When the full text layout of the same text number is different for each institution, it is used for the purpose of distinguishing the full text using the full text version attribute. N Professional number DTO name
file name Enter text identifiers for each text type.
External text: Enter the text number
Internal full text: Enter DTO name
External placement text: Enter file name Y application code Application code to be used in full Y External business code External business code for external specialists. Y Name of DTO specializing in foreign affairs DTO name required for class creation (DTO naming rule: Application L4 + “.” + io + “.” + class name) when external text is reused in the internal system N Registrant ID managed by the server N Registration date managed by the server N expert explanation Description of the full text N

Common header attribute information is as follows.

turn property explanation One Channel Classification foreign choice 2 Transaction Classification online selection 3 professional type Common header selection 4 Professional ID automatic numbering 5 professional name Enter your professional name 6 professional version If the layout is different for the same text number, enter the version number 7 professional number Enter the professional number 8 application code Select application code 9 External business code External business code selection 10 Name of DTO specializing in foreign affairs DTO name required for class creation (DTO naming rule: Application L4 + “.” + io + “.” + class name) when external text is reused in the internal system 11 Registrant ID managed by the server 12 registration date managed by the server

External common header layout properties are as follows.

Item name explanation Required? identification number The field is a foreign dialect number attribute. N Matching key information Field is external matching key information attribute N

ISO8583 header/individual part management is as follows. The ISO8583 text is an international standard text for financial settlement transactions. It specifies whether the field is used or not in the bitmap field by packing the variable data. In general, there is a defined meaning for each indexed field. In the case of two-line ISO8583 full text, it is composed as follows.

Header by brand Bitmap information (64~192bit) packed data

The bitmap field consists of 3 subfields of 8 bytes each. It consists of a primary bitmap, a secondary bitmap, and a third bitmap. If the first bit of each subfield is set to 1, it is used as information indicating that the next subfield exists, so the Bitmap field can also be viewed as a variable field.

In order to manage ISO8583, it is necessary to define the specification for each institution (which data format is analyzed from fields 2 to 192), and the ISO8583 conversion module itself defines and operates the specification as a way to manage it in Korea so far. In other words, the specification for ISO8583 is also operated in the form of a black box or metadata dependent on a specific service or server, making it impossible to manage company-wide meta. EIMS includes the function of integrating management and distribution.

The data expression format for fields of ISO8583 can be classified into ASCII, BCD, and EBCDIC.

11 is a diagram illustrating ISO8583 header/body text attributes according to an embodiment of the present invention. ISO8583 header/body full text attributes are as shown in FIG.

12 is a diagram illustrating layout attributes required for ISO8583 header/body full text definition according to an embodiment of the present invention. The layout attributes required for the ISO8583 header/body full text definition are as shown in FIG. 12 .

Attribute information for each ISO8583 field is as follows. You can specify and manage the size information for the field and the data type (BCD, ASCII, EBCDIC) of the field.

attribute name explanation Required? Specification number ISO8583 professional field number Y variable or not Select whether or not to be a variable field. Y field length type Full length type LEN_FIX : Fixed length field
LEN_BCD: Among the variable fields, the BCD method is interpreted by dividing the length field by 2
LEN_BYTE : Interpretation processing as much as length field in BCD method among variable fields
LEN_LLVAR : The first two digits of the length of the variable field
LEN_LLLVAR : The first three digits of the length of the variable field Y Whether length is included Whether the length of the specialized variable field contains itself Y Whether to copy length Whether to include the length field in the converted field Y transmission data length Maximum length of field to send/receive with external organizations Y

EIMS interface information management

As mentioned, in general, in the role of analyzing the full text to handle exceptionally separate layouts, hard coding for separate exceptions or processing dependent on the service process must be specified. This is a black box, which increases complexity in a form that cannot be integrated across the company. In order to solve this problem, EIMS introduced an independent interface concept independent of professional layout without operating exceptional hard coding for specialized layout processing for each institution.

13 is a diagram illustrating a configuration for managing EIMS interface information according to an embodiment of the present invention.

The professional layout is derived separately and managed by version, and each institution operates and operates the interface code for the professional service. To extract the interface for each institution, the interface ID is found using the 'organization number' and 'organization work code' information assigned to each network session in the external world and the 'professional number' extracted from the transmitted data.

The full text layout assigned to the interface ID is assigned a full text number and full text version information, and it can play a role of converting or modulating a text in a standard format for public content using this. By operating the separate interface from the telegram, information on the telegram can be operated as a unique interface for each institution and system, enabling flexible operation application and service development.

The EIMS solution integrates management of interface information between systems, and interface configuration information includes interface detailed properties, text, and mapping information. The detailed description of interface configuration information is as follows.

turn Component explanation One interface ID Interface ID is automatically numbered by combining application information, sending/receiving system information, etc.
Interface definitions created in Excel at the design stage are registered in batches, and interface IDs are numbered at the time of registration. 2 interface details There are differences in the detailed attribute items managed by interface type (MCI, EAI, etc.) For a detailed description of the detailed attribute items for each interface type, see “5. Refer to “EIMS Interface Management” 3 Transmission system specialized information Management of the request message and response message in units of sending and receiving systems is provided through the specialized management function
Professional management is “4. Refer to “EIMS Professional Management” 4 Professional Mapping Information Provides a full text mapping function for cases where the layout of the full request or full response text is different between the systems defined in the interface. Full text mapping is specified in units of request text and response text. 5 Distribution system and distribution history Interface information managed by EIMS is distributed to the specified system in unit of each interface ID When deploying to multiple systems, if there is no response from a specific system

In many cases, professional affairs with external organizations are managed in separate departments and common departments depending on the type of service provision. As an external common header type, a text number area is provided to designate identification attributes of fields in text layout items. The transaction identified by the telegram number can be routed or executed to the service program by extracting the interface ID, and extracting the service ID corresponding to the telegram data from the common header searched by the interface ID.

Professional mapping features include: The full text mapping function is activated only when the “text conversion status” item of the interface detail information part is “Y”.

The specialized information used for message mapping is automatically filled by referring to the specialized information specified by the sending system and the receiving system. If you use the “Mapping Verification” function, you can verify the mapping field.

Also, by using the “1:1 mapping” function, if the English name of the source text and the English name of the target text are the same, it can be automatically mapped.

14 is a diagram illustrating full text mapping information according to an embodiment of the present invention. The full text mapping information is as shown in FIG. 14 .

The description of the main mapping functions is as follows.

turn function explanation One Mapping Verification If the input classification is specified by the attribute name, the source text field is specified. If the field attribute (type, length) is different from the target attribute, it is displayed in color. 2 1:1 mapping Automatically maps the source field to the mapping data item only when the field name of the source text and the target text are the same.

Basic attribute description is as follows.

attribute name explanation Sauce Special Display the source text to be mapped Target Specialist Mark the target text to be mapped Input Classification Input Classification Optional Attribute Name for Mapping
a constant
system date
function
no conversion mapping data Depending on the input classification, the corresponding data input or selection attribute name: select a field from the list
Constant: Enter a constant value
System Date: Select a date format from the list
Function: Select a function from the mapping function lookup and setting popup
No conversion: none

Mapping function management is as follows. EIMS integrates and manages mapping function information to be used when providing a professional mapping function in the channel system. Information is managed through the interface and the conversion information can be distributed in the form of policies and libraries, enabling integrated management based on EIMS. The existing method provides the functions dependent on each channel solution in MCI, FEP, EAI, etc. as needed, making standardization management difficult or violating policies in the form of a black box.

15 is a diagram illustrating a page for managing a mapping function according to an embodiment of the present invention. The mapping function management page is as shown in FIG. 15 .

The attribute description is as follows.

attribute name explanation Mapping function name Mapping function name number of arguments Number of arguments to be used in the mapping function explanation explanation

The EIMS interface types are as follows. The interface types managed by EIMS are largely divided into internal channels and external channels, and are classified into MCI (Multiple Channel Interface), EAI (External Application Integration), FEP (Front End Processor), and online file transfer according to business characteristics. Representative transaction flows are classified as follows, and EIMS integrates and manages information on all interfaces for the following types.

Channel Classification category transaction flow internal channel internal MCI

internal EAI

external channels External FEP

External file transfer

The interface basic item information is as follows.

attribute name explanation Required? interface ID Interface ID is automatically selected through the “Generate Interface ID” pop-up
The items required for ID numbering are as follows.
Application: Select application code
Sending system: Select the sending system
Receiving System: Select the receiving system
Transaction Type: Select the transaction type
Synchronous classification: Select synchronous/asynchronous method Y interface name interface name N Classification of sending and receiving Send/receive division value Y application Display the selected application code in the “Generate Interface ID” popup N/A Synchronization Displays the selected synchronous classification in the “Generate Interface ID” popup. N/A Professional conversion Full text mapping is enabled when full text translation status is “Y” Y Registrant ID managed by the server N/A state Display status for interface registration and deployment N/A note note N

The transmission/reception system properties are as follows.

attribute name explanation Required? division Show selected send/receive method in “Generate Interface ID” popup N/A system code Show selected system code in “Generate Interface ID” popup N/A system name Show selected system name in “Generate Interface ID” popup N/A transaction code In case of F/W system, select transaction code Y

The interface details are as follows. Registers and manages detailed information related to the interface. Interface ID is automatically numbered according to the numbering rule according to the interface type. A pop-up screen is provided for interface ID numbering, and the items entered in the pop-up are automatically filled in the main screen. Interface IDs automatically numbered cannot be modified, and items used for numbering cannot be changed either. The items of detailed information are largely divided into basic items, transmission/reception system, and detailed attributes.

basic items It is a common property for interface management. transceiver system Registration and management of system-limited information such as “transaction code” detailed properties It is an item managed by interface type and can be specified and managed by type

Interface ID basic attribute information is as follows.

attribute name explanation Required? interface ID Interface ID is automatically selected through the “Generate Interface ID” pop-up
The items required for ID numbering are as follows.
Application: Select application code
Sending system: Select the sending system
Receiving System: Select the receiving system
Transaction Type: Select the transaction type
Synchronous classification: Select synchronous/asynchronous method Y interface name interface name N Classification of sending and receiving Send/receive division value Y application Display the selected application code in the “Generate Interface ID” popup N/A Synchronization Display the selected synchronous classification in the “Generate Interface ID” popup N/A Professional conversion Full text mapping is enabled when full text translation status is “Y” Y Transaction type Show selected transaction type in “Create Interface ID” popup N/A Registrant ID managed by the server N/A state Display status for interface registration and deployment N/A note note N

Routing exception condition attribute description is as follows.

To extract the interface ID, it is expected that the unique interface ID will be extracted with the agency code, agency work, and professional number, but it provides the function of branching the interface ID by a specific value. This can separate and manage the interface ID as a more refined condition. BC, for example, was operating exclusively with VAN and 0100 MS approvals. Separately, if it is necessary to provide a relay service by entrusting processing to BC while operating its own approved text by borrowing our VAN approval layout from NH Chaeum Card, it must be relayed separately with a specific classification value in the professional data. It is possible to register a separate exception rule instead of hard-coding the processing for this.

Routing exception condition attribute description is as follows.

attribute name explanation Required? SEQ Exception condition search sequence number N/A offset offset position value Y Length length of condition value Y VALUE Value to be compared in exception condition Y

As shown below, if a card number is selected as information for interface 1 in EIMS and a routing exception condition for the first 6 digits is registered, RULE is also distributed when interface information is distributed. Allow additional branches to be processed.

16 is a diagram illustrating a configuration for processing a routing exception condition according to an embodiment of the present invention.

The description of the transmission and reception system properties is as follows.

attribute name explanation division Show selected send/receive method in “Generate Interface ID” popup system code Show selected system code in “Generate Interface ID” popup system name Show selected system name in “Generate Interface ID” popup transaction code In case of F/W system, select transaction code

The external detailed information item description is as follows.

attribute name explanation agency code Select the institution code from the pop-up Institutional business classification code Select the agency task classification code from the pop-up Request text number Request text number Response message number Response text number

Detailed attribute description is as follows.

attribute name explanation Timeout (seconds) timeout occurred How to handle timeouts Timeout handling method Delayed response Delay response? Current interface identifier Current interface identifier Whether personal information is included including personal information Whether to be encrypted Whether to be encrypted Transmission error response Transmission error response Request Wrapper Dto Name When using multiple text, enter the wrapper DTO name to be used in F/W (DTO naming convention: Application L4 + “.” + io + “.” + class name) Response Wrapper Dto Name When using multiple text, enter the wrapper DTO name to be used in F/W (DTO naming convention: Application L4 + “.” + io + “.” + class name)

The description of encryption and modulation properties is as follows. Manages standard information for encryption or unidirectional modulation, including personal information among interface items. Using the information, encryption and falsification of data can be performed to solve personal information protection issues.

EIMS interface deployment management

EIMS integrates and manages interface information between systems. Interface configuration information includes a target system to distribute interface information, interface detailed properties, text, mapping information, etc., and relates to a method for distributing interface information.

The interface deployment overview is as follows.

- Registered interfaces are distributed in units of interfaces

“배포시스템 관리”를 선택하면 배포할 대상 시스템을 등록 관리할 수 있다.- Distribution target system is “Configuration information management”

If you select “Manage Distribution System”, you can register and manage the target system to be distributed.

- Distribution proceeds by clicking the distribution button in the interface distribution accordion located at the bottom of each interface information.

- Distribution is performed as All or Nothing. (Processing full rollback in case of a failure in a specific system)

The interface distribution function is as follows.

“배포시스템관리” 기능을 이용하여 미리 등록해야 한다. 등록된 배포시스템은 배포시스템 추가 팝업을 통해서 선택 지정할 수 있다. 배포 버튼을 클릭하면 배포대상시스템 목록에 등록한 대상 시스템으로 배포를 수행한다. 배포 결과는 “처리결과” 파트에 표시된다. 여러 시스템을 대상으로 배포할 때, 특정 시스템에 문제가 있어 배포가 실패하는 경우 Rollback 처리된다. 배포가 정상 처리되면 “배포이력” 파트에 표시되며 “상세보기”를 통해 배포내역을 확인하거나 재배포 할 수 있다.The distribution function distributes the registered interface to the distribution target system or manages the distribution history. The distribution screen is largely divided into distribution target system, processing result, and distribution history. The distribution target system is “Configuration Information Management”

You must register in advance using the “distribution system management” function. The registered distribution system can be selected and specified through the Add Distribution System pop-up. If you click the deploy button, distribution is performed to the target system registered in the distribution target system list. The distribution result is displayed in the “Processing Result” part. When deploying to multiple systems, if the deployment fails due to a problem with a specific system, rollback is processed. When the distribution is processed normally, it is displayed in the “distribution history” part, and the distribution history can be checked or redistributed through the “detailed view”.

The distribution target system management is as follows.

17 is a diagram illustrating a page for managing a distribution system according to an embodiment of the present invention. The distribution system management page is as shown in FIG. 17 .

The attribute description is as follows.

attribute name explanation Required? Remarks (example) distribution system code distribution system code Y Distribution system name Distribution system name Y division Select the distribution system classification value Y MCI, EAI, FEP Distribution system URL URL of the distribution system Y explanation Description of the distribution system N

The distribution procedure is as follows.

turn step explanation One Registering the deployment target system

EIMS 구성정보

배포시스템 관리에서 배포할 대상 시스템을 등록menu

EIMS configuration information

Register the target system to be distributed in the distribution system management 2 Add deployment target system Add deployment target systems in Deployment at the bottom of each interface management screen 3 distribute Deploy by clicking the “Deploy” button at the top right of the deployment part 4 Confirm deployment Check the processing result item of the distribution target system In case of Fail, take action after checking the error details

The interface redistribution procedure is as follows. Provides a function to redistribute interface information of the previous version that has been distributed.

turn step explanation One Select version from deployment history Select the version to redistribute from the distribution history
Check the distribution history using the detailed view 2 redistribution Click the redistribute button to perform redistribution 3 redistribution confirmation Check the processing result item of the distribution target system In case of Fail, take action after checking the error details

The main function description is as follows.

turn function explanation One distribute If the input classification is specified as an attribute name, the source text field is specified. If the field attribute is different from the target attribute, it is displayed in color. 2 Distribution history details Automatically maps the source field to the mapping data item only when the field name of the source text and the target text are the same. 3 redistribution You can redistribute by selecting previously deployed interface information from the distribution history list

The description of the distribution target system properties is as follows.

attribute name explanation system code Display the system code of the distribution system system name Display the system name of the distribution system Deployment URL Display the distribution URL of the distribution system processing result Display processing results for deployment

The description of the distribution history properties is as follows.

attribute name explanation distribution version Show distribution version Distribution date Distribution date and time display distribution system Show deployed systems View Details Retrieve deployed interface information redistribution Redistributing to a Previous Version

18 is a block diagram illustrating an example of the configuration of the interface management system 1000 according to an embodiment of the present invention.

The interface management system 1000 according to an embodiment may support communication between a plurality of devices, and may include all of the embodiments related to the EIMS disclosed in FIGS. 1 to 17 or described above or perform a corresponding function.

Referring to FIG. 18 , the interface management system 1000 according to an embodiment may include an input/output unit 100 , a control unit 200 , and a storage unit 300 .

The input/output unit 100 according to an embodiment may acquire data field attribute information for communication between a plurality of devices through a user input. For example, the input/output unit 100 may display a UI screen and receive data length, type, field, etc. from the user based on an input operation by the user and receive it as data field attribute information.

In one embodiment, the data field attribute information may include full text data field attribute information regarding one or more field attributes designated for defining and identifying a full text, and may include one or more of the above-mentioned preamble attributes, For example, data representing data field properties such as channel classification, transaction classification, and message type may be included.

The controller 200 according to an embodiment may register a request full text and a response text including data field attribute information. Here, the request message indicates an expression format of request data for a service, and the response text indicates an expression format of response data for the request data. For example, the control unit 200 defines one or more properties defining characteristics of the request text and the response text based on the text data field property information obtained as a user input, and stores it in the storage unit 300 to design and distribute the interface available for the course.

In an embodiment, the request full text or the response full text may include a variable-length full text, and in an embodiment, the variable-length full text may include at least one bitmap information field and a packing data field. . For example, the variable length message may include a packing data field in which variable data is packed based on ISO8583 telegram for a financial settlement transaction and a bitmap information field for indicating whether the packing data field is used.

In an embodiment, the bitmap information field may include one or more subfields indicating the existence or nonexistence of the next subfield. For example, the bitmap field may include 1 to 3 subfields, and when the first bit of the subfield is 1, the next subfield exists, and when the first bit of the subfield is 0, the next subfield The field may not exist.

The controller 200 according to an embodiment may generate interface configuration information by mapping predetermined transaction information to the registered request text and response text. For example, the controller 200 may generate interface configuration information by mapping one full request or response text per transaction unit based on a user input or design.

In an embodiment, the interface configuration information may include one or more of the interface ID, interface detailed attributes, transmission/reception system specialized information, expert mapping information, distribution system, and distribution history described in Table 4, the details shown in FIG. It may contain components.

The controller 200 according to an embodiment may provide the interface configuration information generated to be referenced during communication between a plurality of devices to at least one device or store it in a DB. The control unit 200 according to an embodiment allows the automatically converted telegram to be used with reference to interface configuration information provided or stored in the device during communication between a plurality of devices, so that communication between devices using different formats of the telegram is smoothly performed. can support you. In an embodiment, the device may correspond to the above-described internal interface-related system, external interface-related system, or a unit system responsible for other solutions.

For example, the control unit 200 may generate an interface including interface configuration information and directly distribute it to the device, and accordingly, the device may communicate with other devices using the automatically converted request or response message through the distributed interface. We can support you to communicate. For another example, the control unit 200 may store the interface including the interface configuration information in the database included in the storage unit 300 , and provide the stored interface during communication between devices to automatically convert the request message or response through this. You can support communication between devices by using the telegram.

The interface configuration information according to an embodiment may include the first interface configuration information and the second interface configuration information, and the controller 200 refers to the first interface configuration information when an external request message is received from the external device. An internal standard request message corresponding to the external request message may be generated, and an external response message corresponding to the internal standard response message may be generated and transmitted to the external device as a result of processing the internal standard request message by referring to the second interface configuration information.

For example, when an external request message is received from a Front End Processor (FEP) corresponding to a system related to an external interface, the control unit 200 includes specific field information (eg, interface ID, interface detailed attribute, The service request content can be determined by identifying the sending/receiving system front door information, etc.) When the message is processed and an internal standard response message is generated, the internal standard response message can be automatically converted into an external response message using the stored second interface configuration information and provided to the FEP.

In one embodiment, the external device may include at least one of FEP, Multiple Channel Interface (MCI), and Enterprise Application Integration (EAI), and in another embodiment, it may include a system related to the external interface.

The control unit 200 according to an embodiment of the present invention may include, when a full external request from an external device is received, when the service request content is not identified only with specific field information of the external request full text or a corresponding internal standard request full text, the external request full text or The content of the service request can be identified by referring to the rest of the payload of the full internal standard request. For example, the control unit 200 receives the external request message from the FEP, but identifies the service request content from specific field information of the received external request message (eg, interface ID, interface detailed attributes, transmission/reception system front door information, etc.). If not, a service routing function that determines a function called from an external device may be supported by analyzing the remaining payload except for the header and corresponding field information.

The controller 200 according to an embodiment may provide the interface configuration information to at least one UI terminal in a pull method. For example, the control unit 200 provides interface configuration information in an HTTP push method when an interface is distributed to a distribution target system including one or more of an internal channel, an external channel, and F/W, In the case of distribution targeting UI terminals, efficient distribution can be achieved by operating the interface configuration information to be used in the HTTP pull method from the perspective of a large number of unspecified clients.

The controller 200 according to an embodiment may be implemented as a processor that controls overall operations of the interface management system 1000 , and may control data flow between the input/output unit 100 and the storage unit 300 .

The storage unit 300 according to an embodiment may store a message and an interface including a registered request message and a response message, and may store data requested and generated in a data processing process for supporting communication between devices. In an embodiment, the storage unit 300 may be implemented as a database, a cloud, or a separate storage server to provide data and storage space required for the interface management system 1000 through a wired/wireless communication network.

19 is a flowchart illustrating an example of a method in which the interface management system 1000 illustrated in FIG. 18 supports communication between a plurality of devices.

19 may be understood with reference to all embodiments disclosed or described above in FIGS. 1 to 18 .

In operation S1910, the interface management system 1000 according to an embodiment may acquire data field attribute information for communication between a plurality of devices through a user input. For example, the interface management system 1000 may receive data length, type, field, etc. as user input information through a manual input process by a user.

Specialization can be defined.

In step S1920, the interface management system 1000 according to an embodiment may register a request message and a response message including data field attribute information. For example, the interface management system 1000 may define the request text and the response text by using user input information such as data length, type, field, etc. related to the text, and store and register it in the present system.

In step S1930, the interface management system 1000 according to an embodiment may generate interface configuration information by mapping predetermined transaction information to the registered request message and response message. For example, the interface management system 1000 may generate an interface by mapping one full request or response text per transaction unit based on user input and design.

In step S1940, the interface management system 1000 according to an embodiment may provide interface configuration information generated to be referenced during communication between a plurality of devices to at least one device or store it in a DB. For example, the interface management system 1000 may directly distribute an interface according to the generated interface configuration information to a device, or store it and provide the interface so that it can be referred to during communication between devices.

In step S1950, the interface management system 1000 according to an exemplary embodiment uses a message automatically converted with reference to interface configuration information provided or stored in the device during communication between a plurality of devices, so that between devices using a message in a different format It can support smooth communication.

For example, when a request message is received from the device, the interface management system 1000 may provide the automatically converted request message to another device with reference to interface configuration information. For another example, when the external request message is received from the external device, the interface management system 1000 generates an internal standard request message corresponding to the external request message with reference to the first interface configuration information, and the second interface configuration information As a result of processing the internal standard request message by referring to , an external response message corresponding to the internal standard response message can be generated and transmitted to an external device.

The interface management system 1000 according to an embodiment is an interface capable of automatically converting a telegram based on integrated interface management even if different telegrams are used between distributed internal servers and M x N relational servers of external organizations. can be provided and integrated management is possible.

The present disclosure may provide an enterprise interface integrated management system, and the interface management system 1000 may include the enterprise interface integrated management system and the above-described EIMS.

The above description of the present invention is for illustration, and those of ordinary skill in the art to which the present invention pertains can understand that it can be easily modified into other specific forms without changing the technical spirit or essential features of the present invention. will be. Therefore, it should be understood that the embodiments described above are illustrative in all respects and not restrictive. For example, each component described as a single type may be implemented in a dispersed form, and likewise components described as distributed may be implemented in a combined form.

1000: interface management system
100: input/output unit
200: control unit
300: storage

Claims (16)

A method for supporting communication between a plurality of devices,
(a) when the interface management system obtains data field attribute information for communication between the plurality of devices through a user input, registering a request message and a response message including the data field attribute information; and
(b) the interface management system supports communication between the plurality of devices, including generating interface configuration information by mapping predetermined transaction information to the registered request message and response message;
The interface configuration information is
It is provided to at least one UI terminal corresponding to an unspecified number of client terminals in an HTTP pull method,
It is provided to a distribution target system including an internal channel representing a system related to an internal interface in an HTTP push method, an external channel representing a system related to an external interface, and a framework representing a system related to an internal/external interface,
When the interface configuration information is distributed to a plurality of distribution target systems, if there is no response from a specific distribution target system among the plurality of distribution target systems, rollback processing is performed for all of the plurality of distribution target systems and the result of the rollback process is recorded in the distribution history included in the interface configuration information.
The method of claim 1,
(c) providing, by the interface management system, the generated interface configuration information to at least one device to be referenced during communication between the plurality of devices, or storing the information in a DB.
3. The method of claim 2,
In step (c),
In the communication between the plurality of devices, a message automatically converted with reference to the provided or stored interface configuration information is used, so that communication between devices using a message in a different format is smoothly performed,
In step (b),
When mapping the predetermined transaction information, the mapping verification indicating the verification method of verifying whether the field properties match the target properties and displaying them in a preset color if they do not match is performed first, and then the source text and the target text How one-to-one mapping is performed, indicating the mapping method of mapping source fields to mapping data items only when the field names of are the same.
3. The method of claim 2,
The generated interface configuration information is,
a first interface configuration information and a second interface configuration information;
When an external request message is received from the external device, the first interface configuration information is referenced to generate an internal standard request message corresponding to the external request message, and the second interface configuration information is referenced to process the internal standard request message As a result, an external response message corresponding to the internal standard response message is generated and transmitted to the external device.
5. The method of claim 4,
The external device includes at least one of a Front End Processor (FEP), Multiple Channel Interface (MCI), and Enterprise Application Integration (EAI).
4. The method of claim 3,
When the external request message from the external device is received, when the service request content is not identified only by the specific field information of the external request message or the corresponding internal standard request message, the remaining payment of the external request message or the internal standard request message A method according to claim 1 , wherein the load is referenced to identify the content of the service request.
The method of claim 1,
The interface configuration information is
including interface ID, interface detailed properties, transmission/reception system specialized information, professional mapping information, and the distribution history;
A professional number and professional version information are allocated to the professional layout assigned to the interface ID,
For each institution, the interface ID is retrieved using the institution number allocated for each network session, the institution work code, and the text number extracted from the external request text,
When the full text of the external request is received from the external device, an internal standard request text corresponding to the full text of the external request is generated using the text number and the full text version information.
The method of claim 1,
The full text of the request or the full response of the response includes a full text of a variable length,
and the variable length full text includes at least one bitmap information field and a packing data field.
In the interface management system supporting communication between a plurality of devices,
an input/output unit configured to obtain data field attribute information for communication between the plurality of devices through a user input; and
a control unit that registers a full request and a full response including the data field attribute information, and maps predetermined transaction information to the registered request and response text to generate interface configuration information,
The interface configuration information is
It is provided to at least one UI terminal corresponding to an unspecified number of client terminals in an HTTP pull method,
It is provided to a distribution target system including an internal channel representing a system related to an internal interface in an HTTP push method, an external channel representing a system related to an external interface, and a framework representing a system related to an internal/external interface,
When the interface configuration information is distributed to a plurality of distribution target systems, if there is no response from a specific distribution target system among the plurality of distribution target systems, rollback processing is performed for all of the plurality of distribution target systems and a result of the rollback process is recorded in a distribution history included in the interface configuration information.
10. The method of claim 9,
the control unit
An interface management system for providing the generated interface configuration information to at least one device or storing it in a DB to be referenced during communication between the plurality of devices.
11. The method of claim 10,
the control unit
When communicating between the plurality of devices, the automatically converted telegram is used with reference to the provided or stored interface configuration information, thereby supporting communication between devices using different formats of the telegram smoothly,
When mapping the predetermined transaction information, the mapping verification indicating the verification method of verifying whether the field properties match the target properties and displaying them in a preset color if they do not match is performed first, and then the source text and the target text An interface management system in which one-to-one mapping indicating a mapping method of mapping a source field to a mapping data item is performed only when the field names of are the same.
11. The method of claim 10,
The generated interface configuration information is,
a first interface configuration information and a second interface configuration information;
the control unit
When an external request message is received from the external device, an internal standard request message corresponding to the external request message is generated with reference to the first interface configuration information, and the internal standard request message is processed with reference to the second interface configuration information As a result, an external response message corresponding to the internal standard response message is generated and transmitted to the external device.
13. The method of claim 12,
The external device, FEP (Front End Processor), MCI (Multiple Channel Interface), and EAI (Enterprise Application Integration) including at least one of the interface management system.
12. The method of claim 11,
the control unit
When the external request message from the external device is received, when the service request content is not identified only by the specific field information of the external request message or the corresponding internal standard request message, the remaining payment of the external request message or the internal standard request message An interface management system for identifying the content of the service request with reference to the load.
10. The method of claim 9,
The interface configuration information is
including interface ID, interface detailed properties, transmission/reception system specialized information, professional mapping information, and the distribution history;
A professional number and professional version information are allocated to the professional layout assigned to the interface ID,
For each institution, the interface ID is retrieved using the institution number allocated for each network session, the institution work code, and the text number extracted from the external request text,
When the full text of the external request is received from the external device, an internal standard request text corresponding to the full text of the external request is generated by using the text number and the full text version information, an interface management system.
10. The method of claim 9,
The full text of the request or the full response of the response includes a full text of a variable length,
and the variable-length full text includes at least one bitmap information field and a packing data field.

Images