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

Abstract

According to one embodiment of the present invention, provided are: a method for integrally managing different message (telegraphic message) interfaces between distributed internal servers and M x N relation servers of external organizations; and a system in which the method is implemented.

Description

Interface management system and method supporting communication between multiple devices

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

Currently, for business service transactions with servers in external organizations, the message (specialized) interface is managed in a layout dependent on the institution's business. It can be easy to configure the format of the specialty subordinate to a specific institution among external organizations, but there is a complexity that can only be directly searched through a specific type of black box structure rather than integrated interface management from the overall operation point of view.

The types of messages (messages) are largely fixed-size messages, international financial message standard formats (ISO8583), JSON, XML, and other types of messages (messages). In particular, processing brokers such as BC Card deal with service of various companies such as financial institutions, IT institutions, and public institutions, so they must handle all types of message types.

Since each external institution uses the same type of message format, it is easy to manage as a single piece of information dependent on the institution. In order to process a message type different from a standard that is not a standard format dependent on a specific institution at the same time, it is common to handle a rule of an exception handling format in a format dependent on the corresponding institution. Soon, operating with exceptions outside the management scope of'hard coding', rather than standardized format, leads to the problem of interface management currently expressed within financial institutions. It is bound to be limited to a specific institution or the same type of institution, and it is operated in a form in which integrated management is impossible.

For example, two types of BC card payment approvals are provided. VAN must provide magnetic approval transaction and IC approval transaction as an approval transaction in order to communicate with BC Card. However, these two formats operate in completely different types of formats:

[Table 1]

The two messages are sent in a format of different message types. The former case is a fixed-size text format layout, and the latter is a variable-length ISO8583 full text. A full-size text format full text can read only a specific location and determine the type of transaction, but in the case of an ISO8583 full text, the fixed location is after parsing the bitmap and packed data to determine whether to use the field. Should be used. For this, the program can be used only when it is limited to the VAN company, and when implementing other types of professional services, Tight Coupling, which has to be developed separately, cannot be avoided.

The present invention is to solve the above-mentioned problems of the prior art, a method for integrating and managing different message (expert) interfaces between distributed internal servers and servers of M x N relations of external organizations and a system implementing the same It aims to provide.

In addition, the present invention relates to an EIMS (Enterprise Interface Management System), and aims to provide a system for implementing and implementing a professional, connected system, message interface information integrated management and distribution method.

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

According to an embodiment of the present invention, a method and system for managing EIMS architecture and meta code information through an EIMS architecture and registration/management/deployment process is 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 methods corresponding to the same message number are provided.

According to another embodiment of the present invention, a method and system for managing EIMS interface information is provided through a flexible interface management/operation method that eliminates the dependency of a professional layout and a management method for a professional mapping.

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

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

In a method of supporting communication between a plurality of devices according to a first aspect of the present disclosure, the method may include: (a) when an interface management system obtains data field attribute information for communication between the plurality of devices through user input; , Registering a request message and a response message including the data field attribute information, and (b) the interface management system maps predetermined transaction information to the registered request message and response message to obtain interface configuration information. And generating.

In addition, the method may further include the step (c) of the interface management system to provide the generated interface configuration information to at least one device or store it in a DB for reference when communicating between the plurality of devices.

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

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, and the second interface configuration information is referenced to generate an external response message corresponding to the internal standard response message as a result of processing the internal standard request message and may be transmitted to the external device.

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

In addition, when the external request message of the external device is received, when the content of the service request is not identified only by 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 rest of the payload can be referenced to identify the service request.

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

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

According to a second aspect of the present disclosure, an interface management system supporting communication between a plurality of devices, the interface management system comprising: an input/output unit that acquires data field attribute information for communication between the plurality of devices with user input; And a control unit that registers a request message and a response message including the data field attribute information, and generates interface configuration information by mapping predetermined transaction information to the registered request message and response message.

In addition, the control unit may provide the generated interface configuration information to at least one device or store it in a DB to be referred to when communicating between the plurality of devices.

In addition, the controller may support communication to be smoothly performed between devices using different formats of text by allowing the automatically converted text to be used by referring 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 when the external request message is received from the external device, the control unit refers to the first interface configuration information to the external interface. An internal standard request message corresponding to the 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. .

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

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

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

In addition, the request message or the response message may include a variable length message, and the variable length message 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 integrally managing different message (expert) interfaces between distributed internal servers and servers of M x N relations of external organizations and a system implementing the same, the prior art There is an effect that can solve the problem of.

It should be understood that the effects of the present invention are not limited to the above-described effects, and include all effects that can be deduced from the configuration of the invention described in the detailed description of the invention.

1 is a diagram showing a registration/distribution procedure for an interface and a message in an 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 configuration information of a management interface 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 managing a transaction code according to an embodiment of the present invention.

7 is a diagram illustrating a page for managing a work code according to an embodiment of the present invention.

8 is a diagram illustrating a page for managing an institution 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 view showing ISO8583 header/body professional attributes according to an embodiment of the present invention.

12 is a view showing layout attributes required for ISO8583 header/body professional 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 specialized mapping information according to an embodiment of the present invention.

15 is a diagram illustrating a page managing a mapping function according to an embodiment of the present invention.

16 is a diagram illustrating a configuration for handling 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 a 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 illustrated 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 implemented in various different forms, and thus is not limited to the embodiments described herein. In addition, in order to clearly describe the present invention in the drawings, parts irrelevant to the description are omitted, and like reference numerals are assigned to similar parts throughout the specification.

Throughout the specification, a message is a network-based representation of request and response data for a service.

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

In addition, a transaction is a real transaction of an interface, and is network data exchanged between servers.

In addition, EIMS (Enterprise Interface Management System) is a meta management system for professional services such as professional layout of service transactions associated with interfaces, institutional information, institutional business information, and professional mapping information.

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

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

In addition, EAI (Enterprise Application Integration) is an enterprise-wide application integrated management system that handles business integration between multiple systems. MCI operates as a specialized data-based internal channel integration process, but EAI is a broker between systems and is directly delegated to the process. Process.

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

EIMS architecture and meta code information management

EIMS (Enterprise Interface Management System) is a solution for designing and managing interfaces and messages. It provides functions necessary for interface design and management, and provides interface distribution function with other connected systems. Information required for interface management is linked with the Meta system and uses information (terms, codes, etc.) registered in the Meta system.

1 is a diagram showing a registration/distribution procedure for an interface and a message in an EIMS according to an embodiment of the present invention. The registration/distribution procedure for the interface and the full text 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 target system is as follows.

[Table 2]

In the distribution method, providing both the Push and Pull methods are as follows.

[Table 3]

In the case of accessing as an unspecified number of Client roles, such as a UI terminal, it is possible to efficiently distribute by operating in a Pull method in a Client position rather than Push from the EIMS point of view. It is a figure showing configuration information. The management interface configuration information of the EIMS is as shown in FIG. 3.

The interface configuration information is as follows.

[Table 4]

The management functions of EIMS are as follows.

[Table 5]

In EIMS configuration information management, EIMS registers and manages coded information necessary for interface design through configuration information management. The coded data is automatically updated in association with Meta. In meta management, the transmission/reception system management manages the transmission/reception system necessary 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 as shown in FIG. 4.

The property description is as follows.

[Table 6]

Application code management is as follows. The standardized application code L3 required for the interface definition is managed. FIG. 5 is a diagram illustrating a page for managing an application according to an embodiment of the present invention. The application management page is shown in FIG. 5.

The property description is as follows.

[Table 7]

The transaction code management is as follows. Manage transaction codes required for interface definition. FIG. 6 is a diagram illustrating a page for managing transaction codes, according to an embodiment of the present invention. The transaction code management page is shown in FIG. 6.

The property description is as follows.

[Table 8]

In the work code management, the work codes necessary for the interface definition are managed. FIG. 7 is a diagram showing a page for managing the work codes according to an embodiment of the present invention. The work code management page is shown in FIG. 7.

The property description is as follows.

[Table 9]

The agency code management is as follows. The organization required for the interface definition is managed as an internal code as a separate internal code. FIG. 8 is a diagram illustrating a page for managing an organization code according to an embodiment of the present invention. The institution code management page is shown in FIG. 8.

The property description is as follows.

Table 10

Meta information management is as follows. Manage meta information necessary for professional definition (interlocked with the Meta system). FIG. 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 property description is as follows.

[Table 11]

EIMS professional management function

The full text is classified into a fixed layout (FIXED) and a variable full text (ISO8583, JSON, XML, etc.) layout according to the data expression format. In order to manage the request and response for one service, the existing professional management method defined and operated each layout on two servers for performing the request and response for the service. Here, in the role of the service requester for the service and the service responder providing the result of processing the service request, the service requester only needs to request one layout per service. When service requesters request to create various services, if they are configured as separate processes under an independent network, service responders can be implemented to parse each layout and parse each layout. However, under a non-independent network environment, various network protocols (X.25, TCP, HTTP, etc.), various specialized formats (fixed length, variable length), and various professional layouts are managed to provide various services for different purposes. There is a need for an information management plan as an integrated management subject that is not dependent on others.

In professional version management, multiple layouts targeting the same service are managed. BC Card manages and operates professional layouts for approximately 31 customers. For customer-approved transaction services, we operate a service with a special number '1100'. According to the guides and layout distributed by the company first, all customers 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, the customer's own field is additionally operated rather than the common layout among the first distributed 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 process an exceptional layout, when analyzing a professional layout, it is necessary to designate a hard code for each additional exception or a process dependent on the service process. This is a black box, and the complexity is increased in a form that cannot be integrated and managed throughout the company. To solve this, EIMS introduced an independent interface concept independent of the professional layout, without operating an exceptional hard coding for the specialized layout processing by institution. (See EIMS interface information management to be described later)

All organizations operate with the same professional number (type code), and each individual layout can be operated to provide individual services. In addition, by separating the professional layout from the interface properties, it is necessary to define an area for a common field for specialized management, inherit it, and define only additional fields. Thus, efficiency in resource management is secured, and information on the professional layout is integrated management.

In professional layout management, the common headers are:

When operating a number of services with external organizations, the professional number is generally identified to identify the service requested by the expert. In addition, a common part, such as a common header with a foreign institution, is defined for the transaction unique number for matching the request transaction and the response transaction, and information about the identity entity requested. EIMS operates external specialized DTO items so that the layout of individual parts of common and specialized services for each institution 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 data data for internal use corresponding to the layout of the external text and use it as a value object (VO).

Table 12

The management of the identification attributes of the common part is as follows. The detailed attributes that designate EIMS to be used to identify external text as standard content in the content are as follows.

[Table 13]

Common header property information is as follows.

Table 14

The common common header layout properties are as follows.

Table 15

ISO8583 header/individual management is as follows. The ISO8583 full text is an international standard full text for financial settlement transactions. It packs variable data and specifies whether or not to use the field in the bitmap field. Generally, there is a meaning defined for each indexed field. In the case of the full text of ISO8583, it consists of the following.

Table 16

The composition of the Bitmap field is largely composed of 3 sub-fields of 8 bytes each. It is composed of Primary bitmap, Secondary bitmap, and Third bitmap. If it is set as 1 in the first bit of each subfield, 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 (what data format is analyzed from fields 2 to 192). Until now, the specification has been defined and operated in the ISO8583 conversion module itself as a way to manage it. In other words, the specification for ISO8583 is also operated in the form of a black box, meta data that is dependent on a specific service or server, and it is operated in a form in which meta management at the enterprise level is impossible. EIMS includes the function of managing and distributing the management in an integrated manner.

Data representation format for ISO8583 fields can be classified into ASCII, BCD, and EBCDIC.

11 is a view showing ISO8583 header/body professional attributes according to an embodiment of the present invention. The ISO8583 header/body professional attributes are as shown in FIG. 11.

12 is a view showing layout attributes required for ISO8583 header/body professional definition according to an embodiment of the present invention. Layout attributes required for ISO8583 header/body professional definition are as shown in FIG. 12.

The attribute information for each ISO8583 field is as follows. The size information for the field and the data type of the field (BCD, ASCII, EBCDIC) can be specified and managed.

Table 17

EIMS interface information management

As mentioned, in general, in the role of analyzing an entire message to handle an extraordinary layout, it is necessary to designate a hardcoding for an extra exception or a process dependent on the service process. This is a black box, and the complexity is increased in a form that cannot be integrated and managed throughout the company. To solve this, EIMS introduced an independent interface concept independent of the professional layout without operating an exceptional hard coding for the specialized layout processing by 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 and managed by version, and each organization operates by operating the interface code for the professional service. To extract the interface for each institution, the interface ID is searched using the'institution number','institution work code' information allocated by each network session from the outside world, and the'expert number' extracted from the transmitted data.

The professional layout assigned to the interface ID is assigned the professional number and the professional version information, and can be used to convert or modulate to a full-text standard format. By operating the interface separately from the message, information on the message can be operated as a unique interface for each institution and system, so flexible operation application and service development are possible.

The EIMS solution integrates and manages interface information between systems, and the interface configuration information includes interface detailed attributes, full text, mapping information, etc., and detailed description of the interface configuration information is as follows.

Table 18

In many cases, the specialty with external organizations is managed as individual parts and common parts depending on the type of service provision. As a common common header type, a special number area is provided to specify a field's identification attribute in a special layout item. The transaction identified by the professional number can extract the interface ID, extract the service ID corresponding to the professional data by the common header searched by the interface ID, and route or execute the service program. Same as The professional mapping function is activated only when the “Specify whether to convert” item in the interface detail part is “Y”.

The professional information used in the professional mapping is automatically filled with reference to the specialized information specified in the transmitting system and the receiving system. The mapping field can be used to verify the mapping field.

In addition, if the “1:1 mapping” function is used, the English name of the source message and the English name of the target message can be automatically mapped.

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

The main function description of the mapping is as follows.

Table 19

The basic property description is as follows.

Table 20

Mapping function management is as follows. In EIMS, the mapping function information to be used when providing the professional mapping function in the channel system is integrated and managed. Information can be managed through the interface, and the converted information can be distributed in the form of policies and libraries, enabling integrated management based on EIMS. In the existing method, MCI, FEP, EAI, etc. provide each function dependent on each channel solution as needed, so it is difficult to manage standardization in the form of a black box or it may violate policies. 15 is a diagram illustrating a page managing a mapping function according to an embodiment of the present invention. The mapping function management page is as shown in FIG. 15.

The property description is as follows.

Table 21

The types of EIMS interfaces are: The interface types managed in EIMS are largely divided into internal and external channels, and are classified into multiple channel interfaces (MCI), external application integration (EAI), front end processors (FEP), and online file transfers according to business characteristics. Typical transaction flows are classified as follows. EIMS manages information on all interfaces for the following types.

Table 22

The basic interface information is as follows.

Table 23

The transmission/reception system properties are as follows.

Table 24

The interface details are as follows. Register and manage detailed information related to the interface. The 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 items entered in the pop-up are automatically filled in the main screen. The interface ID that has been automatically picked up cannot be modified, and the items used for picking up cannot also be changed. The items of detailed information are largely divided into basic items, transmission/reception systems, and detailed properties.

Table 25

Basic property information of Interface ID is as follows.

Table 26

The attributes of the Routing exception condition are as follows: In order to extract the interface ID, it is expected that the unique interface ID will be extracted with the agency code, agency service, and professional number, but provides the function to branch the interface ID by a specific value. . This allows separate management of the interface ID as a more granular condition. For example, BC was operating with VAN and 0100 MS approvals. Separately, if NH Fill Card borrows our VAN-approved layout to operate its own approval message, and needs to provide a service that relays processing to BC, it must be relayed separately with a specific value in the specialized data. It is possible to register a separate exception rule for this process rather than hard coding.

Routing exception condition attribute description is as follows.

Table 27

As shown below, in EIMS, the card number is selected as the information for interface 1, and if the routing exception condition for the preceding 6 digits is registered, RULE is also distributed when the interface information is distributed, so the channel (FEP, MCI, EAI) The additional branch is processed. FIG. 16 is a diagram illustrating a configuration for processing a routing exception condition according to an embodiment of the present invention.

The properties of the transmission/reception system are as follows.

Table 28

Details of external details are as follows.

Table 29

The detailed property description is as follows.

Table 30

The following describes the encryption and modulation properties. Manages reference information for encryption or unidirectional modulation, including personal information among interface items. By using the information, encryption and tampering of data can be performed to solve privacy issues.

EIMS interface distribution management

EIMS integrates and manages interface information between systems. The interface configuration information includes a target system to which interface information is distributed, interface detailed attributes, full text, mapping information, etc., and relates to a method of distributing interface information.

The interface deployment overview is as follows.

-Registered interface is distributed in interface unit

-The target system to be distributed can be registered and managed by selecting “Manage Configuration Information” · “Manage Distribution System”.

-Distribution is progressed 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. (When a specific system fails, the entire rollback process)

The interface distribution function is as follows.

The distribution function distributes the registered interface to the system to be distributed or manages the deployed history. Distribution screen is largely divided into distribution target system, processing result, and distribution history. The target system should be registered in advance using the "Configuration Information Management" and "Distribution System Management" functions. Registered distribution system can be selected and designated through the pop-up of distribution system addition. Clicking the Deploy button performs deployment to the target systems registered in the target system list. Distribution results are displayed in the “Process Results” part. When deploying to multiple systems, rollback is performed when deployment fails because of a problem with a specific system. If the distribution is processed normally, it is displayed in the “Distribution History” part and you can check the distribution history or redistribute it through “Detail View”.

The system management targeted for distribution 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 shown in FIG. 17.

The property description is as follows.

Table 31

The distribution procedure is as follows.

Table 32

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

Table 33

The main function description is as follows.

Table 34

Distribution system properties are as follows.

Table 35

The description of the distribution history attribute is as follows.

Table 36

18 is a block diagram illustrating an example of a configuration of an 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 embodiments of 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 user input. For example, the input/output unit 100 may display a UI screen and receive data length, type, field, etc. from a 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 special data field attribute information related to one or more field attributes designated to define and identify the full text, and may include one or more of the above-described full text attributes, For example, data representing data field attributes such as channel classification, transaction classification, and specialized type may be included.

The control unit 200 according to an embodiment may register a request message and a response message including data field attribute information. Here, the request message represents the representation format of the request data for the service, and the response message represents the representation format of the response data for the request data. For example, the control unit 200 designes and distributes an interface by defining one or more attributes defining characteristics of the request message and the response message based on the expert data field property information obtained through user input, and storing them in the storage unit 300 Can be used in the course.

In one embodiment, the request message or the response message can include a variable length message, and in one embodiment, the variable length message can include at least one bitmap information field and a packing data field. . For example, the variable length message may include a packing data field packing variable data based on ISO8583 message for financial settlement transaction, and a bitmap information field for indicating whether or not to use the packing data field.

In one embodiment, the bitmap information field may include one or more subfields indicating the presence or absence of the next subfield. For example, the bitmap field may include 1 to 3 subfields, the next subfield exists when the first bit of the subfield is 1, and the next subfield when the first bit of the subfield is 0. 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 message and response message. For example, the controller 200 may generate interface configuration information by mapping one request message or response message per transaction unit based on user input or design.

In one embodiment, the interface configuration information may include one or more of the interface ID described in Table 4, interface detailed attributes, transmission/reception system specialized information, professional mapping information, distribution system, and distribution history, and details shown in FIG. 3. Components may be included.

The control unit 200 according to an embodiment may provide interface configuration information generated to be referred to when communicating between a plurality of devices to at least one device or store it in a DB. When communicating between a plurality of devices, the controller 200 according to an embodiment allows the automatically converted message to be used by referring to the interface configuration information provided or stored in the device, so that communication between devices using messages of different formats can be smoothly performed. To help you lose. In one embodiment, the device may correspond to a system related to the internal interface described above, a system related to a foreign interface, or a unit system in charge of other solutions.

For example, the control unit 200 may create an interface including interface configuration information and distribute it directly to the device, and accordingly, the device 200 may use an automatically converted request message or response message through the interface to which the device is distributed. It can support communication. For another example, the control unit 200 may store an interface including interface configuration information in a database included in the storage unit 300, provide a stored interface during communication between devices, and provide an automatically converted request message or response through this. You can use a full text to support communication between devices.

The interface configuration information according to an embodiment may include first interface configuration information and second interface configuration information, and when the external request message is received from the external device, the controller 200 refers to the first interface configuration information. 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 an external device by referring to the second interface configuration information.

For example, when the external request message is received from the front end processor (FEP) corresponding to a system related to the external interface, the control unit 200 receives specific field information (eg, interface ID, interface detail property, etc.) of the received external request message. The service request contents can be determined by identifying the transmission/reception system front door information, etc., and the external request message can be automatically converted to the internal standard request message using the first interface configuration information according to the determined service content. When an internal standard response message is generated by processing the message, the internal standard response message can be automatically converted to 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 Chanel Interface (MCI) and Enterprise Application Integration (EAI), and in another embodiment, a system related to the external interface.

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

The controller 200 according to an embodiment may provide interface configuration information to at least one UI terminal in a pull method. For example, the controller 200 provides interface configuration information in an HTTP push method when distributing an interface to a distribution target system including one or more of an internal channel, an external channel, and F/W, In the case of distributing to a UI terminal, it is possible to operate the HTTP pool method to use the interface configuration information from an unspecified number of clients so that efficient distribution can be achieved.

The control unit 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 generated and requested in a data processing process to support communication between devices. In one embodiment, the storage unit 300 is 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 or 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 in FIGS. 1 to 18 or described above.

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 with user input. For example, the interface management system 1000 may receive data length, type, and field as user input information through a manual input process by the user.

You can define the full text.

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 a request message and a response message using user input information such as data length, type, and field related to the message, and store and register the message in the system.

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

In operation S1940, the interface management system 1000 according to an embodiment may provide interface configuration information generated to be referred to when communicating 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 the interface according to the generated interface configuration information to the device, or may store it and provide an interface for reference during communication between devices.

In step S1950, the interface management system 1000 according to an embodiment uses a message that is automatically converted by referring to interface configuration information provided or stored in a device when communicating between a plurality of devices, and thus, between devices using messages of different formats. It can support smooth communication.

For example, when the request message is received from the device, the interface management system 1000 may provide the automatically converted request message to another device by referring to the 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, referring to the first interface configuration information, and the second interface configuration information. An external response message corresponding to the internal standard response message can be generated and transmitted to an external device as a result of processing the internal standard request message with reference to.

The interface management system 1000 according to an embodiment may automatically convert a message based on the integrated interface management even if different messages are used between distributed internal servers and MxN-related servers of external organizations. And provide integrated management.

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

The above description of the present invention is for illustration only, and those skilled in the art to which the present invention pertains can understand that the present invention 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 distributed manner, and similarly, components described as distributed may be implemented in a combined form.

Claims (16)

1. In 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 user input, registering a request message and a response message including the data field attribute information, and

   (b) the interface management system supporting the communication between the plurality of devices by generating interface configuration information by mapping predetermined transaction information to the registered request message and response message.
2. According to claim 1,

   (c) the interface management system further comprising the step of providing the generated interface configuration information to at least one device for reference when communicating between the plurality of devices or storing it in a DB.
3. According to claim 2,

   In step (c),

   A method characterized in that communication is smoothly performed between devices using different formats of text by using the automatically converted text by referring to the provided or stored interface configuration information during communication between the plurality of devices.
4. According to claim 2,

   The generated interface configuration information,

   It includes the first interface configuration information and the second interface configuration information,

   When an external request message is received from an 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 an 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 Chanel Interface (MCI), and Enterprise Application Integration (EAI).
6. The method of claim 3,

   When the external request message of the external device is received, when the content of the service request is not identified only by specific field information of the external request message or the corresponding internal standard request message, the remaining pay of the external request message or the internal standard request message A method characterized in that the load is referenced and the content of the service request is identified.
7. According to claim 2,

   The interface configuration information is provided to at least one UI terminal in a pull method.
8. According to claim 1,

   The request message or the response message includes a variable length message,

   Wherein the variable length full text includes at least one bitmap information field and a packing data field.
9. In the interface management system supporting communication between a plurality of devices,

   An input/output unit that acquires data field attribute information for communication between the plurality of devices with user input; And

   An interface management system including a control unit that registers a request message and a response message including the data field attribute information, and generates interface configuration information by mapping predetermined transaction information to the registered request message and response message.
10. The method of claim 9,

    The control unit

    An interface management system that provides the generated interface configuration information to at least one device or stores it in a DB for reference when communicating between the plurality of devices.
11. The method of claim 10,

    The control unit

    An interface management system that supports communication between devices using different formats of text by smoothly using the automatically converted text with reference to the provided or stored interface configuration information during communication between the plurality of devices.
12. The method of claim 10,

    The generated interface configuration information,

    It includes the first interface configuration information and the second interface configuration information,

    The control unit

    When an external request message is received from an external device, an internal standard request message corresponding to the external request message is generated by referring to the first interface configuration information, and the internal standard request message is processed by referring to the second interface configuration information As a result, an interface management system that generates an external response message corresponding to the internal standard response message and transmits it to the external device.
13. The method of claim 12,

    The external device includes at least one of a Front End Processor (FEP), Multiple Chanel Interface (MCI), and Enterprise Application Integration (EAI).
14. The method of claim 11,

    The control unit

    When the external request message of the external device is received, when the content of the service request is not identified only by specific field information of the external request message or the corresponding internal standard request message, the remaining pay of the external request message or the internal standard request message Interface management system for identifying the content of the service request with reference to the load.
15. The method of claim 10,

    The control unit

    An interface management system that provides the interface configuration information to at least one UI terminal in a pull method.
16. The method of claim 9,

    The request message or the response message includes a variable length message,

    The variable length full text comprises at least one bitmap information field and a packing data field, an interface management system.

Images