KR102636966B1 - Method, device and system for managing and sharing integrated interface information - Google Patents

Abstract

Provided is an integrated interface information management and sharing method. According to one embodiment, the integrated interface information management and sharing method performed by a device includes the following steps of: receiving a registration request of a first interface defining a relationship for data exchange and interaction between a first system and a second system from a first user terminal; confirming first interface information based on the registration request of the first interface; storing and registering the first interface information in a database; receiving an interface search request from a second user terminal; performing a search according to the interface search request and generating a search result; transmitting the search result to the second user terminal; receiving a sharing request of the first interface from the second user terminal when the first interface is selected from the search result; and transmitting the first interface information to the second user terminal.

Description

Integrated interface information management and sharing method, device, and system {METHOD, DEVICE AND SYSTEM FOR MANAGING AND SHARING INTEGRATED INTERFACE INFORMATION}

The embodiments below relate to technology for managing and sharing interface information through integration.

Due to the growth of the IT industry, connection and ESB solutions are gradually being introduced into projects due to the complexity caused by the introduction of various systems. As a result, the need to develop standardized texts and interfaces between various systems and manage them in an integrated environment is increasing.

Accordingly, the demand to efficiently manage and share interfaces between various linked solutions and systems is increasing, and the implementation of related technologies is required.

Korean Patent Publication No. 10-2023-0150892 Korean Patent Publication No. 10-2022-0114075 Korean Patent No. 10-1561524 Korean Patent No. 10-0821167

According to one embodiment, the purpose is to provide a method, device, and system for managing and sharing interface information through integration.

The object of the present invention is not limited to the object mentioned above, and other objects not mentioned can be clearly understood from the description below.

According to one embodiment, in a method of managing and sharing integrated interface information performed by a device, the method includes: a first interface defining a relationship for data exchange and interaction between a first system and a second system from a first user terminal; Receiving a registration request; Confirming first interface information based on the registration request for the first interface; storing and registering the first interface information in a database; Receiving an interface inquiry request from a second user terminal; performing a search according to the interface inquiry request and generating search results; transmitting the search results to the second user terminal; When the first interface is selected in the search results, receiving a request to share the first interface from the second user terminal; A method for managing and sharing integrated interface information is provided, including transmitting the first interface information to the second user terminal.

The first interface information includes the ID of the first system, the ID of the second system, the ID of the first server performing work between the first system and the second system, the system type of the first system, and the System type of the second system, transaction type of the first server, professional serial number, ID of the first interface, name of the first interface, description of the first interface, and information on business authority of the first interface may include.

The ID of the first interface is composed of a combination of a first character, a second character, a third character, a fourth character, and a fifth character, the first character is set as the ID of the first system, and the second character is set to the ID of the first system. The character is set to the ID of the first server, the third character is set to the ID of the second system, the fourth character is set to a transaction code corresponding to the transaction type of the first server, and the third character is set to the ID of the second system. 5 characters can be set to the above full text serial number.

The step of storing and registering the first interface information in a database includes comparing the ID of the first interface with the ID of a pre-registered interface, and if it is confirmed that there is no matching ID, storing the first interface information in the database. It may include steps of saving and registering.

According to one embodiment, there is an effect of increasing the reliability and convenience of the interface in business development by managing and sharing interface information through integration.

Meanwhile, the effects according to the embodiments are not limited to those mentioned above, and other effects not mentioned can be clearly understood by those skilled in the art from the description below.

1 is a diagram schematically showing the configuration of a system according to an embodiment.
Figure 2 is a diagram illustrating a structure utilizing a system according to an embodiment.
Figure 3 is a flow chart to explain the process of managing and sharing interface information through integration according to an embodiment.
Figure 4 is a flow chart to explain the interface registration process according to one embodiment.
Figure 5 is a flow chart to explain the process of sorting search results according to an embodiment.
Figure 6 is an exemplary diagram of the configuration of a device according to an embodiment.

Hereinafter, embodiments will be described in detail with reference to the attached drawings. However, various changes can be made to the embodiments, so the scope of the patent application is not limited or limited by these embodiments. It should be understood that all changes, equivalents, or substitutes for the embodiments are included in the scope of rights.

Specific structural or functional descriptions of the embodiments are disclosed for illustrative purposes only and may be modified and implemented in various forms. Accordingly, the embodiments are not limited to the specific disclosed form, and the scope of the present specification includes changes, equivalents, or substitutes included in the technical spirit.

Terms such as first or second may be used to describe various components, but these terms should be interpreted only for the purpose of distinguishing one component from another component. For example, a first component may be named a second component, and similarly, the second component may also be named a first component.

When a component is referred to as being “connected” to another component, it should be understood that it may be directly connected or connected to the other component, but that other components may exist in between.

The terms used in the examples are for descriptive purposes only and should not be construed as limiting. Singular expressions include plural expressions unless the context clearly dictates otherwise. In this specification, terms such as “comprise” or “have” are intended to designate the presence of features, numbers, steps, operations, components, parts, or combinations thereof described in the specification, but are not intended to indicate the presence of one or more other features. It should be understood that this does not exclude in advance the possibility of the existence or addition of elements, numbers, steps, operations, components, parts, or combinations thereof.

Unless otherwise defined, all terms used herein, including technical or scientific terms, have the same meaning as generally understood by a person of ordinary skill in the technical field to which the embodiments belong. Terms defined in commonly used dictionaries should be interpreted as having a meaning consistent with the meaning in the context of the related technology, and unless explicitly defined in the present application, should not be interpreted in an ideal or excessively formal sense. No.

In addition, when describing with reference to the accompanying drawings, identical components will be assigned the same reference numerals regardless of the reference numerals, and overlapping descriptions thereof will be omitted. In describing the embodiments, if it is determined that detailed descriptions of related known technologies may unnecessarily obscure the gist of the embodiments, the detailed descriptions are omitted.

Embodiments may be implemented in various types of products such as personal computers, laptop computers, tablet computers, smart phones, televisions, smart home appliances, intelligent vehicles, kiosks, and wearable devices.

1 is a diagram schematically showing the configuration of a system according to an embodiment.

Referring to FIG. 1, a system according to an embodiment may include a plurality of user terminals 100 and devices 200 that can communicate with each other through a communication network.

First, a communication network can be configured regardless of the communication mode, such as wired or wireless, and can be implemented in various forms to enable communication between servers and between servers and terminals.

Each of the plurality of user terminals 100 may be implemented as a computing device with a communication function, and may be implemented as, for example, a mobile phone, desktop PC, laptop PC, tablet PC, smartphone, POS terminal, etc. It is not limited and may be implemented as various types of communication devices that can be connected to an external server.

The plurality of user terminals 100 are terminals used by users and may include a first user terminal 110 used by a first user, a second user terminal 120 used by a second user, etc.

Each of the plurality of user terminals 100 may be configured to perform all or part of the calculation function, storage/reference function, input/output function, and control function of a typical computer. A plurality of user terminals 100 may be configured to communicate with the device 200 in a wired or wireless manner.

Each of the plurality of user terminals 100 is connected to a web page operated by a person or organization providing services using the device 200, or is developed and distributed by a person or organization providing services using the device 200. An application can be installed. Each of the plurality of user terminals 100 may be linked to the device 200 through a web page or application.

That is, each of the plurality of user terminals 100 can access the device 200 through a web page or application provided by the device 200.

Hereinafter, for convenience of explanation, the operation of the first user terminal 110 will be mainly described, but of course, other user terminals such as the second user terminal 120 can perform the operation of the first user terminal 110 instead. am.

The device 200 may be its own server owned by a person or organization that provides services using the device 200, a cloud server, or a p2p (peer-to-peer) set of distributed nodes. It may be possible. The device 200 may be configured to perform all or part of the calculation function, storage/reference function, input/output function, and control function of a typical computer.

The device 200 may be configured to communicate wired or wirelessly with a plurality of user terminals 100, control the operation of each of the plurality of user terminals 100, and display certain information on the screen of each of the plurality of user terminals 100. You can control whether to display it or not.

The device 200 may be implemented as a server that provides an integrated interface information management and sharing platform, thereby providing a platform for managing and sharing integrated interface information. A detailed description regarding this will be provided later with reference to FIG. 2 .

Meanwhile, for convenience of explanation, only the first user terminal 110 and the second user terminal 120 are shown in FIG. 1 among the plurality of user terminals 100, but the number of terminals may vary depending on the embodiment. . As long as the processing capacity of the device 200 allows, the number of terminals is not particularly limited.

Figure 2 is a diagram illustrating a structure utilizing a system according to an embodiment.

Referring to FIG. 2, the device 200 can provide an integrated interface information management and sharing platform, and developers can define an interface through a plurality of user terminals 100, register it on the platform, and search for the interface. The platform and multiple systems are connected, and interface information can be shared and interface information provided through the platform. At this time, the interface information may be stored in a storage database of the device 200.

According to one embodiment, the integrated interface information management and sharing platform may be an enterprise interface management solution that can manage and distribute specialized information and interfaces used in various enterprise systems in a single, integrated environment. Here, the full text may refer to a data format or message exchanged between specific systems.

According to one embodiment, an interface may refer to a method of establishing relationships for data exchange and interaction between systems and modules. This has a structure in which the source system transmits and requests actual data, and the target system processes these data and requests and returns a response. It consists of an Integration Server, a middleware that relays between these two systems and handles routing and message conversion.

In other words, the interface establishes a relationship for data exchange and interaction between the source system and the target system through the linkage server. The interface information includes identification information of the source system, identification information of the target system, identification information of the linkage server, and source system. It may include information about the system type of the target system and the transaction type of the linked server.

The source system may refer to a system that delivers data and performs requests, and the target system may refer to a system that processes data and requests and returns a response.

Linkage is a technology that enables information exchange and interworking between different systems, and a linkage server can refer to a server that performs routing and message conversion tasks between the source system and the target system.

The system type represents the actual data type or communication method of the source system and target system. For example, there may be types such as Online, File, and DB (Database).

Transaction type refers to the form or characteristics of requests and responses processed by the linked server. For example, there may be types such as synchronous, batch, and asynchronous.

The device 200 provides an integrated interface information management and sharing platform, processing the entire process of registering interface information through interface definition, providing interface information through interface search, and sharing interface information, thereby managing and sharing interface information. Support is available.

According to one embodiment, developers can register interface information on the platform through interface definition and share interface information through interface search. A detailed description regarding this will be provided later with reference to FIG. 3 .

Figure 3 is a flow chart to explain the process of managing and sharing interface information through integration according to an embodiment.

Referring to FIG. 3, first, in step S301, the device 200 may receive a registration request for the first interface from the first user terminal 110. Here, the first interface is an interface that regulates the relationship for data exchange and interaction between the first system and the second system, and the first system may be the source system and the second system may be the target system.

According to one embodiment, the request for registration of the first interface is to request registration of the first interface through the definition of the first interface. When requesting registration of the first interface, the information necessary to define the first interface is input. This can be done, and a detailed description related to this will be described later with reference to FIG. 4.

When the information necessary to define the first interface is input, the first user terminal 110 may generate first interface information based on the input information and request registration of the first interface including the first interface information. can be transmitted to the device 200.

The first interface information includes the ID of the first system, the ID of the second system, the ID of the first server performing work between the first system and the second system, the system type of the first system, the system type of the second system, It may include information on the transaction type of the first server, professional serial number, ID of the first interface, name of the first interface, description of the first interface, and business authority of the first interface. Here, the ID of the first system is identification information of the first system that is the source system, the ID of the second system is identification information of the second system that is the target system, and the ID of the first server is the identification information of the first server that is the linked server. information, and the ID of the first interface may mean identification information of the first interface.

The ID of the first system and the ID of the second system can be set according to the system type. For example, if the type of the first system is selected as an open banking system, the ID of the first system can be set to OBK, , if the type of the first system is selected as a basic system, the ID of the first system may be set to COR, and if the type of the first system is selected as an approval system, the ID of the first system may be set to APR. there is. For this purpose, a classification code may be set for each system type.

The ID of the first server may be set according to the server type. For example, if the type of the first server is selected as an EAI (Enterprise Application Integration) server, the ID of the first server may be set to EAI, and the 1 If the type of server is selected as a FEP (Front End Processor) server, the ID of the first server can be set to FEP, and if the type of the first server is selected as an MCI (Multi Channel Architecture) server, the ID of the first server can be set to FEP. ID can be set to MCI. For this purpose, a classification code may be set for each server type.

The ID of the first interface may be composed of a combination of multiple characters. For example, the ID of the first interface may be composed of a combination of the first character, the second character, the third character, the fourth character, and the fifth character. At this time, the first character is set as the ID of the first system, the second character is set as the ID of the first server, the third character is set as the ID of the second system, and the fourth character is set as the ID of the first server. It is set to the transaction code corresponding to the type, and the fifth character can be set to the full text serial number.

The transaction code may be set according to the transaction type of the first server. For example, if the transaction type of the first server is selected as Synchronous, the transaction code may be set to S, and the transaction code of the first server may be set to S. If the type is selected as Asynchronous, the transaction code can be set to A.

The professional serial number can be set to a certain number or more.

For example, if the ID of the first system is OBK, the first character may be set to “OBK”, and if the ID of the first server is FEP, the second character may be set to “FEP”, If the ID of the second system is OBK, the third character may be set to “OBK”, if the transaction type of the first server is synchronous, the fourth character may be set to “S”, and the full text serial number If is 12345, the 5th character can be set to “12345”, and the ID of the first interface is a combination of the 1st character, 2nd character, 3rd character, 4th character, and 5th character as “”. It can be configured. At this time, duplication of the ID of the first interface is not allowed, and in case of duplication, redefinition of the first interface can be requested.

In step S302, the device 200 may check first interface information based on the registration request for the first interface.

In step S303, the device 200 may store and register the first interface information in a database.

According to one embodiment, the device 200 checks whether the ID of the first interface, which is identification information of the first interface, is duplicated, and if it is confirmed that the ID of the first interface is not duplicated, the device 200 connects the first interface to the device 200. It can be saved and registered in the database.

That is, if the device 200 compares the ID of the first interface and the ID of the previously registered interface and determines that there is no matching ID, the device 200 may store the first interface information in the database and register it. Here, the ID of the pre-registered interface may mean the ID of the interface stored in the database.

When registering information about the first interface, the device 200 may store and register the first user's ID, which is identification information of the first user who defined the first interface. Here, the ID of the first user may mean identification information of the first user.

In step S304, the device 200 may receive an interface inquiry request from the second user terminal 120.

According to one embodiment, an interface inquiry request is to request an interface inquiry through an interface search. When requesting an interface inquiry, a search for the interface is requested through a search word, system ID, linked server ID, user ID, etc. It can be.

In step S305, the device 200 may perform a search according to the interface inquiry request and generate a search result. At this time, the search result may include the first interface.

Specifically, when the interface inquiry request is a search request through a search term, the device 200 performs a search based on the search term, and confirms that the search term and the ID of the first interface match, or determines that the search term and the ID of the first interface match. If the name is confirmed to match, a search result may be generated based on the first interface.

In addition, when the interface inquiry request is a inquiry request through the ID of the source system, the device 200 performs a search based on the ID of the source system and confirms that the ID of the source system matches the ID of the first system. If so, search results can be generated based on the first interface.

In addition, when the interface inquiry request is a query request through the ID of the linked server, the device 200 performs a search based on the ID of the linked server and confirms that the ID of the linked server matches the ID of the first server. If so, search results can be generated based on the first interface.

In addition, when the interface inquiry request is a inquiry request through the ID of the target system, the device 200 performs a search based on the ID of the target system and confirms that the ID of the target system and the ID of the second system match. If so, search results can be generated based on the first interface.

In addition, when the interface inquiry request is a inquiry request through the user's ID, the device 200 performs a search based on the user's ID, and if it is confirmed that the user's ID and the first user's ID match, the device 200 performs a search based on the user's ID. 1 Search results can be generated based on the interface.

According to one embodiment, when a plurality of interfaces are included in the search results, the search results can be sorted, and a detailed description regarding this will be described later with reference to FIG. 5.

In step S306, the device 200 may transmit the search result to the second user terminal 120. At this time, the device 200 can control the search results to be displayed on the screen of the second user terminal 120.

In step S307, when the first interface is selected in the search results, the device 200 may receive a request to share the first interface from the second user terminal 120. Here, the request to share the first interface is to request sharing of the first interface to check first interface information.

That is, in order to check the first interface information, the second user can select the first interface within the search results displayed on the screen of the second user terminal 120, and the second user terminal 120 can select the first interface within the search results. When the first interface is selected, a sharing request for the first interface may be transmitted to the device 200.

In step S308, the device 200 may transmit the first interface information to the second user terminal 120. At this time, the device 200 can control the first interface information to be displayed on the screen of the second user terminal 120.

Figure 4 is a flow chart to explain the interface registration process according to one embodiment.

First, the device 200 may transmit a first page for interface registration to the first user terminal 110. At this time, the device 200 can control the first page to be displayed on the screen of the first user terminal 110.

Referring to FIG. 4, in step S401, the first user may select an interface registration button on the first page.

In step S402, the first user may select a linked server on the first page.

In step S403, the first user may select a source system on the first page. A drop-down menu may appear on the first page when selecting a source system. This menu provides the ability to select the desired system based on internal and external classification and system tasks.

In step S404, the first user may select a target system on the first page. A drop-down menu may appear on the first page when selecting a target system. This menu provides the ability to select the desired system based on internal and external classification and system tasks.

In step S405, the first user may select the transaction type of the linked server on the first page.

In step S406, the first user may select the system type of the source system and the system type of the target system on the first page.

In step S407, the first user may enter the full text serial number on the first page.

In step S408, the first user may enter the name, description, and permissions of the interface on the first page.

In step S409, the first user may select the save button on the first page.

When the save button is selected on the first page, the first user terminal 110 may generate interface information based on information selected or input through steps S402 to S408.

Figure 5 is a flow chart to explain the process of sorting search results according to an embodiment.

Referring to FIG. 5, first, in step S501, the device 200 can confirm that a plurality of interfaces are included in the search result.

For example, the device 200 may confirm that the first interface and the second interface are included in the search result.

In step S502, the device 200 may classify the interfaces included in the search results into the first group.

In step S503, the device 200 may check the number of deployments of each interface classified into the first group, based on the distribution history of each interface classified into the first group. Here, the distribution history may consist of a list of distribution information about when and to whom it was shared and distributed, and the distribution information may include information on the date and time of distribution, version of the distributed interface, comments entered at the time of distribution, distribution requester, etc. You can. For this purpose, distribution history divided by interface is stored in the database of the device 200.

For example, if the first interface and the second interface are classified into the first group, the device 200 searches the information stored in the database to obtain the distribution history of the first interface and the distribution history of the second interface. The number of deployments of the first interface can be confirmed based on the deployment history of the first interface, and the number of deployments of the second interface can be confirmed based on the deployment history of the second interface.

In step S504, the device 200 may classify interfaces with a distribution count greater than the first reference value among the interfaces classified into the first group into the second group. Here, the first reference value may be set differently depending on the embodiment.

In step S505, the device 200 may classify interfaces whose distribution count is not greater than the first reference value among the interfaces classified into the first group into the third group.

After step S504, in step S506, the device 200 may check the number of changes to each interface classified into the second group based on the change history of each interface classified into the second group. Here, the change history may consist of a list of change information about when and by whom the change was made, and the change information includes information about the version of the changed interface, change date and time, comments entered at the time of change, and the modifier who made the change. can do. For this purpose, change history divided by interface is stored in the database of the device 200.

For example, when the first interface and the second interface are classified into the second group, the device 200 searches the information stored in the database to obtain the change history of the first interface and the change history of the second interface. The number of changes to the first interface can be confirmed based on the change history of the first interface, and the number of changes to the second interface can be confirmed based on the change history of the second interface.

In step S508, the device 200 may classify interfaces whose number of changes is greater than the second reference value among the interfaces classified into the second group into the fourth group. Here, the second reference value may be set differently depending on the embodiment.

If there are a plurality of interfaces classified into the fourth group, the device 200 checks the latest distribution date of each interface classified into the fourth group based on the distribution history of each interface classified into the fourth group, and determines the latest distribution date of each interface classified into the fourth group. The faster the work, the higher the priority can be assigned to sort the order of the interfaces classified into the fourth group.

In step S509, the device 200 may classify interfaces whose change count is not greater than the second reference value among the interfaces classified into the second group into the fifth group.

If there are a plurality of interfaces classified into the fifth group, the device 200 checks the latest distribution date of each interface classified into the fifth group based on the distribution history of each interface classified into the fifth group, and determines the latest distribution date of each interface classified into the fifth group. The faster the work, the higher the priority can be assigned to sort the order of the interfaces classified into the fifth group.

After step S505, in step S507, the device 200 may check the number of changes to each interface classified into the third group based on the change history of each interface classified into the third group.

In step S510, the device 200 may classify interfaces whose number of changes is greater than the second reference value among the interfaces classified into the third group into the sixth group.

If there are a plurality of interfaces classified into the sixth group, the device 200 checks the latest distribution date of each interface classified into the sixth group based on the distribution history of each interface classified into the sixth group, and determines the latest distribution date of each interface classified into the sixth group. The faster the work, the higher the priority can be assigned to sort the order of the interfaces classified into the 6th group.

In step S511, the device 200 may classify interfaces whose change count is not greater than the second reference value among the interfaces classified into the third group into the seventh group.

If there are multiple interfaces classified into the 7th group, the device 200 checks the latest deployment date of each interface classified into the 7th group based on the distribution history of each interface classified into the 7th group, and determines the latest deployment date of each interface classified into the 7th group. The faster the work, the higher the priority can be assigned to sort the order of the interfaces classified into Group 7.

In step S512, the device 200 may generate search results sorted in the order of the fourth group, the fifth group, the sixth group, and the seventh group.

That is, the device 200 may arrange the fourth group at the top so that it is displayed first within the search results, followed by the fourth group, the fifth group, the sixth group, and the seventh group.

Figure 6 is an exemplary diagram of the configuration of a device according to an embodiment.

Device 200 according to one embodiment includes a processor 210 and memory 220. The processor 210 may include at least one device described above with reference to FIGS. 1 to 5 or may perform at least one method described above with reference to FIGS. 1 to 5 . A person or organization using the device 200 may provide services related to some or all of the methods described above with reference to FIGS. 1 to 5 .

The memory 220 may store information related to the methods described above or store a program in which methods described later are implemented. Memory 220 may be volatile memory or non-volatile memory.

The processor 210 can execute programs and control the device 200. The code of the program executed by the processor 210 may be stored in the memory 220. The device 200 is connected to an external device (eg, a personal computer or a network) through an input/output device (not shown) and can exchange data through wired or wireless communication.

The embodiments described above may be implemented with hardware components, software components, and/or a combination of hardware components and software components. For example, the devices, methods, and components described in the embodiments may include, for example, a processor, a controller, an arithmetic logic unit (ALU), a digital signal processor, a microcomputer, and a field programmable gate (FPGA). It may be implemented using one or more general-purpose or special-purpose computers, such as an array, programmable logic unit (PLU), microprocessor, or any other device capable of executing and responding to instructions. A processing device may execute an operating system (OS) and one or more software applications that run on the operating system. Additionally, a processing device may access, store, manipulate, process, and generate data in response to the execution of software. For ease of understanding, a single processing device may be described as being used; however, those skilled in the art will understand that a processing device includes multiple processing elements and/or multiple types of processing elements. It can be seen that it may include. For example, a processing device may include a plurality of processors or one processor and one controller. Additionally, other processing configurations, such as parallel processors, are possible.

The method according to the embodiment may be implemented in the form of program instructions that can be executed through various computer means and recorded on a computer-readable medium. The computer-readable medium may include program instructions, data files, data structures, etc., singly or in combination. Program instructions recorded on the medium may be specially designed and configured for the embodiment or may be known and available to those skilled in the art of computer software. Examples of computer-readable recording media include magnetic media such as hard disks, floppy disks, and magnetic tapes, optical media such as CD-ROMs and DVDs, and magnetic media such as floptical disks. -Includes optical media (magneto-optical media) and hardware devices specifically configured to store and execute program instructions, such as ROM, RAM, flash memory, etc. Examples of program instructions include machine language code, such as that produced by a compiler, as well as high-level language code that can be executed by a computer using an interpreter, etc. The hardware devices described above may be configured to operate as one or more software modules to perform the operations of the embodiments, and vice versa.

Software may include a computer program, code, instructions, or a combination of one or more of these, which may configure a processing unit to operate as desired, or may be processed independently or collectively. You can command the device. Software and/or data may be used on any type of machine, component, physical device, virtual equipment, computer storage medium or device to be interpreted by or to provide instructions or data to a processing device. , or may be permanently or temporarily embodied in a transmitted signal wave. Software may be distributed over networked computer systems and stored or executed in a distributed manner. Software and data may be stored on one or more computer-readable recording media.

Although the embodiments have been described with limited drawings as described above, those skilled in the art can apply various technical modifications and variations based on the above. For example, the described techniques are performed in a different order than the described method, and/or components of the described system, structure, device, circuit, etc. are combined or combined in a different form than the described method, or other components are used. Alternatively, appropriate results may be achieved even if substituted or substituted by an equivalent.

Therefore, other implementations, other embodiments, and equivalents of the claims also fall within the scope of the following claims.

Claims (3)

In a unified interface information management and sharing method performed by a device,
Receiving, from a first user terminal, a request for registration of a first interface defining a relationship for data exchange and interaction between the first system and the second system;
Confirming first interface information based on the registration request for the first interface;
storing and registering the first interface information in a database;
Receiving an interface inquiry request from a second user terminal;
performing a search according to the interface inquiry request and generating search results;
transmitting the search results to the second user terminal;
When the first interface is selected in the search results, receiving a request to share the first interface from the second user terminal; and
Comprising transmitting the first interface information to the second user terminal,
The first interface information includes the ID of the first system, the ID of the second system, the ID of the first server performing work between the first system and the second system, the system type of the first system, and the System type of the second system, transaction type of the first server, professional serial number, ID of the first interface, name of the first interface, description of the first interface, and information on business authority of the first interface Including,
The ID of the first interface is composed of a combination of the first character, the second character, the third character, the fourth character, and the fifth character,
The first character is set as the ID of the first system,
The second character is set as the ID of the first server,
The third character is set as the ID of the second system,
The fourth character is set as a transaction code corresponding to the transaction type of the first server,
The fifth character is set to the full text serial number,
The step of storing and registering the first interface information in the database includes:
As a result of comparing the ID of the first interface with the ID of a pre-registered interface, if it is confirmed that there is no matching ID, storing and registering the first interface information in a database,
The step of generating the search results is,
When the interface inquiry request is a search request through a search term, as a result of performing a search based on the search term, it is confirmed that the search term and the ID of the first interface match, or the search term and the name of the first interface are confirmed to be identical. If a match is confirmed, generating a search result based on the first interface;
When the interface inquiry request is a inquiry request through the ID of the source system, as a result of performing a search based on the ID of the source system, if it is confirmed that the ID of the source system and the ID of the first system match, generating search results based on the first interface;
When the interface inquiry request is a inquiry request through the ID of the linked server, as a result of performing a search based on the ID of the linked server, if it is confirmed that the ID of the linked server and the ID of the first server match, generating search results based on the first interface;
When the interface inquiry request is a inquiry request through the ID of the target system, as a result of performing a search based on the ID of the target system, if it is confirmed that the ID of the target system and the ID of the second system match, generating search results based on the first interface; and
When the interface inquiry request is a inquiry request through the user's ID, as a result of performing a search based on the user's ID, if it is confirmed that the user's ID and the first user's ID match, the first interface Including generating search results based on
The step of generating the search results is,
If it is confirmed that a plurality of interfaces are included in the search results, classifying the interfaces included in the search results into a first group;
Confirming the number of deployments of each interface classified into the first group based on the distribution history of each interface classified into the first group;
Among the interfaces classified into the first group, interfaces with a distribution count greater than a preset first reference value are classified into a second group, and among interfaces classified into the first group, interfaces with a distribution count not greater than the first reference value are classified into a second group. Classification into 3 groups;
Checking the number of times each interface classified into the second group has been changed, based on the change history of each interface classified into the second group;
Among the interfaces classified into the second group, interfaces whose number of changes is greater than the preset second standard value are classified into the fourth group, and among the interfaces classified into the second group, interfaces whose number of changes is not more than the second standard value are classified into the fourth group. Classification into 5 groups;
Checking the number of times each interface classified into the third group has been changed, based on the change history of each interface classified into the third group;
Among the interfaces classified into the third group, interfaces with a change count greater than the second reference value are classified into a sixth group, and among interfaces classified into the third group, interfaces with a change count less than the second reference value are classified into a seventh group. Classifying into groups;
If there are multiple interfaces classified into the fourth group, the latest distribution date of each interface classified into the fourth group is checked based on the distribution history of each interface classified into the fourth group, and the latest distribution date is confirmed. Sorting the order of the interfaces classified into the fourth group by assigning higher priority as they are faster;
If there are multiple interfaces classified into the fifth group, the latest distribution date of each interface classified into the fifth group is checked based on the distribution history of each interface classified into the fifth group, and the latest distribution date is confirmed. Sorting the order of the interfaces classified into the fifth group by assigning higher priority as they are faster;
If there are multiple interfaces classified into the sixth group, the latest distribution date of each interface classified into the sixth group is checked based on the distribution history of each interface classified into the sixth group, and the latest distribution date is confirmed. Sorting the order of the interfaces classified into the sixth group by assigning higher priority as they are faster;
If there are multiple interfaces classified into the 7th group, the latest distribution date of each interface classified into the 7th group is checked based on the distribution history of each interface classified into the 7th group, and the latest distribution date is confirmed. Sorting the order of the interfaces classified into the seventh group by assigning higher priority as they are faster; and
Comprising the step of generating search results sorted in the order of the fourth group, the fifth group, the sixth group, and the seventh group,
Unified interface information management and sharing method. delete delete