WO2020159089A2 - Système de gestion d'interface et procédé de prise en charge de communication entre une pluralité de dispositifs - Google Patents

Système de gestion d'interface et procédé de prise en charge de communication entre une pluralité de dispositifs Download PDF

Info

Publication number
WO2020159089A2
WO2020159089A2 PCT/KR2019/018714 KR2019018714W WO2020159089A2 WO 2020159089 A2 WO2020159089 A2 WO 2020159089A2 KR 2019018714 W KR2019018714 W KR 2019018714W WO 2020159089 A2 WO2020159089 A2 WO 2020159089A2
Authority
WO
WIPO (PCT)
Prior art keywords
interface
request message
configuration information
information
external
Prior art date
Application number
PCT/KR2019/018714
Other languages
English (en)
Korean (ko)
Other versions
WO2020159089A3 (fr
Inventor
이덕영
박재홍
이태영
이재원
Original Assignee
비씨카드(주)
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from KR1020190145759A external-priority patent/KR102379919B1/ko
Application filed by 비씨카드(주) filed Critical 비씨카드(주)
Publication of WO2020159089A2 publication Critical patent/WO2020159089A2/fr
Publication of WO2020159089A3 publication Critical patent/WO2020159089A3/fr

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management

Definitions

  • 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.
  • 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.
  • messages are largely fixed-size messages, international financial message standard formats (ISO8583), JSON, XML, and other types of messages (messages).
  • 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.
  • VAN must provide magnetic approval transaction and IC approval transaction as an approval transaction in order to communicate with BC Card.
  • IC approval transaction
  • these two formats operate in completely different types of formats:
  • 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.
  • 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.
  • 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.
  • EIMS Enterprise Interface Management System
  • a method and system for managing EIMS architecture and meta code information through an EIMS architecture and registration/management/deployment process is provided.
  • 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.
  • 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.
  • 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.
  • a method and system for managing data modulation is provided.
  • 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.
  • 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.
  • 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.
  • 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.
  • the external device may include at least one of a Front End Processor (FEP), Multiple Chanel Interface (MCI), and Enterprise Application Integration (EAI).
  • FEP Front End Processor
  • MCI Multiple Chanel Interface
  • EAI Enterprise Application Integration
  • the external request message of the external device 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.
  • the interface configuration information may be provided to at least one UI terminal in a pull method.
  • the request message or the response message may include a variable length message
  • the variable length message may include at least one bitmap information field and a packing data field.
  • 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.
  • 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.
  • 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.
  • 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. .
  • the external device may include at least one of FEP, MCI, and EAI.
  • the control unit 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.
  • the controller may provide the interface configuration information to at least one UI terminal in a pull method.
  • the request message or the response message may include a variable length message
  • the variable length message may include at least one bitmap information field and a packing data field.
  • FIG. 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.
  • FIG. 2 is a diagram illustrating the configuration of an EIMS system according to an embodiment of the present invention.
  • FIG. 3 is a diagram illustrating configuration information of a management interface of an EIMS according to an embodiment of the present invention.
  • FIG. 4 is a diagram illustrating a page for managing a transmission/reception system according to an embodiment of the present invention.
  • FIG. 5 is a diagram illustrating a page for managing an application according to an embodiment of the present invention.
  • FIG. 6 is a diagram illustrating a page managing a transaction code according to an embodiment of the present invention.
  • FIG. 7 is a diagram illustrating a page for managing a work code according to an embodiment of the present invention.
  • FIG. 8 is a diagram illustrating a page for managing an institution code according to an embodiment of the present invention.
  • FIG. 9 is a diagram illustrating a page for managing meta information, according to an embodiment of the present invention.
  • FIG. 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.
  • FIG. 12 is a view showing layout attributes required for ISO8583 header/body professional definition according to an embodiment of the present invention.
  • FIG. 13 is a diagram illustrating a configuration for managing EIMS interface information according to an embodiment of the present invention.
  • FIG. 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.
  • FIG. 18 is a block diagram illustrating an example of a configuration of an interface management system according to an embodiment of the present invention.
  • FIG. 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.
  • a message is a network-based representation of request and response data for a service.
  • an interface is an attribute unit of data transaction generated based on a message.
  • a transaction is a real transaction of an interface, and is network data exchanged between servers.
  • EIMS Enterprise Interface Management System
  • EIMS Enterprise Interface Management System
  • professional services such as professional layout of service transactions associated with interfaces, institutional information, institutional business information, and professional mapping information.
  • Front End Processor 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.
  • MCI Multiple Chanel Interface
  • UI terminals User Equipment
  • upper manager User Equipment
  • complex transaction relaying for transactions between departments.
  • EAI Enterprise Application Integration
  • 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.
  • EIMS Enterprise Interface Management System
  • Meta System Enterprise Interface Management System
  • FIG. 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.
  • FIG. 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.
  • the interface configuration information is as follows.
  • EIMS The management functions of EIMS are as follows.
  • 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.
  • meta management the transmission/reception system management manages the transmission/reception system necessary for interface definition.
  • FIG. 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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 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.
  • FIXED fixed layout
  • ISO8583, JSON, XML, etc. variable full text
  • the existing professional management method defined and operated each layout on two servers for performing the request and response for the service.
  • the service requester only needs to request one layout per service.
  • service responders can be implemented to parse each layout and parse each layout.
  • 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.
  • FIG. 10 is a diagram illustrating a configuration for managing an EIMS message according to an embodiment of the present invention.
  • 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)
  • 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).
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • FIG. 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.
  • FIG. 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.
  • EIMS introduced an independent interface concept independent of the professional layout without operating an exceptional hard coding for the specialized layout processing by institution.
  • FIG. 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.
  • 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.
  • 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.
  • the specialty with external organizations is managed as individual parts and common parts depending on the type of service provision.
  • 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.
  • the English name of the source message and the English name of the target message can be automatically mapped.
  • FIG. 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.
  • mapping The main function description of the mapping is as follows.
  • mapping function management is as follows.
  • 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.
  • 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.
  • 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.
  • the basic interface information is as follows.
  • the transmission/reception system properties are as follows.
  • 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.
  • 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.
  • 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.
  • 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 target system to be distributed can be registered and managed by selecting “Manage Configuration Information” ⁇ “Manage Distribution System”.
  • 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.
  • FIG. 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 distribution procedure is as follows.
  • the interface redistribution procedure is as follows. Provides the function to redistribute the interface information of the previous version that has been distributed.
  • Distribution system properties are as follows.
  • the description of the distribution history attribute is as follows.
  • FIG. 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 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.
  • the interface management system 1000 may include an input/output unit 100, a control unit 200, and a storage unit 300.
  • the input/output unit 100 may acquire data field attribute information for communication between a plurality of devices through user input.
  • 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.
  • 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 may register a request message and a response message including data field attribute information.
  • the request message represents the representation format of the request data for the service
  • the response message represents the representation format of the response data for the request data.
  • 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.
  • 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.
  • 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.
  • the bitmap information field may include one or more subfields indicating the presence or absence of the next subfield.
  • 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 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.
  • 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 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.
  • the controller 200 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.
  • 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.
  • 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.
  • 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 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.
  • 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.
  • 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.
  • 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.
  • FEP FEP
  • MCI Multiple Chanel Interface
  • EAI Enterprise Application Integration
  • the control unit 200 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 specific field information eg, interface ID, interface detailed attribute, transmission/reception system front door information, etc.
  • the controller 200 may provide interface configuration information to at least one UI terminal in a pull method.
  • 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,
  • 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.
  • the control unit 200 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 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.
  • 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.
  • FIG. 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.
  • FIGS. 1 to 18 may be understood with reference to all embodiments disclosed in FIGS. 1 to 18 or described above.
  • the interface management system 1000 may acquire data field attribute information for communication between a plurality of devices with user input.
  • the interface management system 1000 may receive data length, type, and field as user input information through a manual input process by the user.
  • the interface management system 1000 may register a request message and a response message including data field attribute information.
  • 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.
  • the interface management system 1000 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.
  • the interface management system 1000 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.
  • 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.
  • the interface management system 1000 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.
  • the interface management system 1000 may provide the automatically converted request message to another device by referring to the interface configuration information.
  • the interface management system 1000 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 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.

Abstract

Selon un mode de réalisation de la présente invention, l'invention concerne: un procédé de gestion intégrale de différentes interfaces de message (message télégraphique) entre des serveurs internes distribués et M x N serveurs de relations d'organisations externes; et un système dans lequel le procédé est mis en oeuvre.
PCT/KR2019/018714 2019-02-01 2019-12-30 Système de gestion d'interface et procédé de prise en charge de communication entre une pluralité de dispositifs WO2020159089A2 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
KR20190013272 2019-02-01
KR10-2019-0013272 2019-02-01
KR1020190145759A KR102379919B1 (ko) 2019-02-01 2019-11-14 복수의 디바이스 간 통신을 지원하는 인터페이스 관리 시스템 및 방법
KR10-2019-0145759 2019-11-14

Publications (2)

Publication Number Publication Date
WO2020159089A2 true WO2020159089A2 (fr) 2020-08-06
WO2020159089A3 WO2020159089A3 (fr) 2020-09-24

Family

ID=71842100

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2019/018714 WO2020159089A2 (fr) 2019-02-01 2019-12-30 Système de gestion d'interface et procédé de prise en charge de communication entre une pluralité de dispositifs

Country Status (1)

Country Link
WO (1) WO2020159089A2 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115174650A (zh) * 2022-09-06 2022-10-11 深圳领筑科技有限公司 开放服务平台、服务响应方法、装置、设备和存储介质

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB0023169D0 (en) * 2000-09-20 2000-11-01 Ibm Message parsing in message processing systems
US7694287B2 (en) * 2005-06-29 2010-04-06 Visa U.S.A. Schema-based dynamic parse/build engine for parsing multi-format messages
BRPI0921524A2 (pt) * 2008-11-10 2018-05-29 Zomojo Pty Ltd sistema de negociação automatizada aperfeiçoado
JP4934699B2 (ja) * 2009-05-28 2012-05-16 株式会社三井住友銀行 マルチフォーマット変換システム
KR101135010B1 (ko) * 2010-05-19 2012-04-09 스탠다드네트웍스 주식회사 비동기 방식의 전문을 교환하는 대외계 게이트웨이 시스템

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115174650A (zh) * 2022-09-06 2022-10-11 深圳领筑科技有限公司 开放服务平台、服务响应方法、装置、设备和存储介质

Also Published As

Publication number Publication date
WO2020159089A3 (fr) 2020-09-24

Similar Documents

Publication Publication Date Title
WO2014027785A1 (fr) Méthode de gestion de planning, serveur de gestion de planning et terminal mobile utilisant cette méthode
WO2020032482A1 (fr) Procédé et système de fourniture de transaction financière au moyen d'une carte vide
WO2020050555A1 (fr) Procédé de transaction ulb et dispositif électronique associé
WO2016190680A1 (fr) Procédé et dispositif de gestion consolidée de données de navire
WO2017039341A1 (fr) Dispositif d'affichage et procédé de commande correspondant
WO2017213281A1 (fr) Procédé de désidentification de données volumineuses
WO2017213304A1 (fr) Système de données de navire intégrées et navire comprenant celui-ci
WO2019107907A1 (fr) Dispositif électronique de commande de paiement électronique et procédé associé
WO2014030960A1 (fr) Procédé et système de fourniture d'informations en utilisant un terminal de stockage
WO2016182209A1 (fr) Serveur, système de fourniture de service de beauté et procédé
WO2014035178A1 (fr) Système et procédé pour la fourniture d'un service lié à un objet
WO2014123341A1 (fr) Système et procédé permettant de fournir un objet pour accéder à un service d'un fournisseur de services
WO2021025387A1 (fr) Procédé de commerce électronique capable de commande intégrée et de distribution intégrée, et serveur associé
WO2020159089A2 (fr) Système de gestion d'interface et procédé de prise en charge de communication entre une pluralité de dispositifs
WO2019109521A1 (fr) Procédé, appareil et dispositif de validation d'identité pour un entretien vidéo et support d'enregistrement lisible
WO2021125719A1 (fr) Système et procédé de diagnostic intelligent
AU2019337074A2 (en) Method for UWB transaction and electronic device therefor
WO2019004670A1 (fr) Procédé et dispositif électronique de rendu de contenu svg
WO2018174319A1 (fr) Procédé de calcul d'indice de transport pour fournir un indice de transport en conteneur en asie et procédé de prestation de service de courtage d'informations de transport utilisant ledit procédé
WO2020189993A1 (fr) Procédé et système de prévention de perte de cryptomonnaie
WO2018030827A1 (fr) Système et procédé d'émission et de gestion d'un bordereau d'expédition sécurisé à l'aide d'informations personnelles virtuelles
WO2017094967A1 (fr) Schéma de traitement de langage naturel et procédé et système pour établir une base de données de connaissances pour ce dernier
WO2023048537A1 (fr) Serveur et procédé pour fournir un contenu de recommandation
WO2023038324A1 (fr) Procédé de propriété distribuée de jetons non fongibles
WO2019098428A1 (fr) Procédé de fourniture de fonction erp faisant appel à une table de gestion extensible spécifique à un utilisateur, et système de fourniture de fonction erp permettant la mise en œuvre dudit procédé

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19914041

Country of ref document: EP

Kind code of ref document: A2

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19914041

Country of ref document: EP

Kind code of ref document: A2