KR102639787B1 - System of multi-connection module in application and method performing the same - Google Patents

Abstract

The present invention provides a method for multiple connection between modules within an application, including the steps of a central management server extracting user information from a connection approval request message received from a user terminal and then generating a user token and a common token using the user information, the central management server providing a user token to the user terminal and providing a common token to a common API module, depending on whether the pre-stored user token is valid when the user terminal logs into an application or each of a plurality of modules provided by the application. Providing a login request message including the user token to the central management server, each of the application or the plurality of modules receiving the login request message from the user terminal receiving a common token from a common API module, and and allowing the user terminal to successfully log in depending on whether the user token and the common token are the same.

Description

Multiple connection system between modules within an application and method of implementing it {SYSTEM OF MULTI-CONNECTION MODULE IN APPLICATION AND METHOD PERFORMING THE SAME}

The present invention relates to a multiple connection system between modules within an application and a method of executing the same. More specifically, it relates to a multiple connection system between modules within an application that can modularize and connect different applications of a company and a method of executing the same. will be.

The growth of the software industry has made it useful for a wide range of applications, and electricity generality has become heavily dependent on these applications. Additionally, it is common for businesses to utilize multiple tasks within the company for day-to-day activities.

Because these tasks are provided by a variety of vendors, coordination to support business control pathways is a critical task that requires skilled personnel provided by resources used in other locations.

Therefore, it is very important for businesses to interconnect their work and share information in a stable and secure manner.

However, there is a need to integrate their work so that businesses can cooperate with each other and share information, but there are many difficulties in realizing such integration.

One common problem with traditional approaches is that new solutions must be used every hour to change or terminate business operations. This approach costs a lot of money due to large-scale disruption of business, sometimes fails to achieve business objectives, and is not a solution for the future.

Another problem with the traditional approach is that it requires manual coordination of each task so that the task can be linked to other tasks in the business. Additionally, this approach is costly and time consuming. Additionally, this approach has the disadvantage of being inflexible as business is updated or added or tasks are transformed.

Meanwhile, in response to recent improvements in the performance of mobile communication terminals and various convergence needs of customers, attempts are being made to install 'General Purpose OS (Operating System)' in feature phones and smartphones, and mobile applications are also developing accordingly. Change is required.

The emergence of specialized terminals that meet the diverse needs of these customers makes it a burden to install huge mobile applications equipped with all functions. Therefore, a lightweight mobile application that combines only the necessary functions according to the characteristics of the terminal is needed.

Korean Patent Publication No. 10-2006-0029245 discloses a method and device for determining and notifying users with matching preference profiles to access a multi-access online application, but solves the above problems. There is no disclosed method for doing so.

The purpose of the present invention is to provide a multiple connection system between modules within an application that can modularize and connect different applications of a company and a method for executing the same.

In addition, the purpose of the present invention is to provide a multiple connection system between modules within an application and a method of executing the same, which allows connecting modules within an application by generating a token-type key on a central server and providing it to the modules within the application.

In addition, the present invention is an application that ensures user convenience and contributes to increasing the frequency of use of modules by enabling movement between modules directly or indirectly through a multi-connection structure when a B2B operator provides various application-based modules. The purpose is to provide a multi-connection system between my modules and a method to implement them.

The objects of the present invention are not limited to the objects mentioned above, and other objects and advantages of the present invention that are not mentioned can be understood by the following description and will be more clearly understood by the examples of the present invention. Additionally, it will be readily apparent that the objects and advantages of the present invention can be realized by the means and combinations thereof indicated in the patent claims.

The multiple connection method between modules within an application to achieve this purpose includes the steps of a central management server extracting user information from a connection approval request message received from a user terminal and then using the user information to generate a user token and a common token; A central management server providing a user token to the user terminal and providing a common token to a common API module, checking whether the pre-stored user token is valid when the user terminal logs into an application or each of a plurality of modules provided by the application. Providing a login request message including the user token to the central management server depending on whether the user terminal receives the login request message, each of the application or the plurality of modules receiving a common token from a common API module and the user terminal succeeding in logging in according to whether the user token and the common token are the same.

In addition, to achieve this purpose, the multiple connection system between the modules within the application including the central management server and the user terminal extracts user information from the connection approval request message received from the user terminal and then uses the user information to create a user token and common Check whether the pre-stored user token is valid when logging in to each of the central management server and application or a plurality of modules provided by the application that generates a token, provides a user token to the user terminal, and provides a common token to a common API module. Depending on whether a login request message including the user token is provided to the central management server, each of the application or the plurality of modules that receives the login request message receives a common token from a common API module, a user token, and and a user terminal that successfully logs in depending on whether the common token is the same.

According to the present invention as described above, there is an advantage that different applications of a company can be modularized and connected.

Additionally, according to the present invention, there is an advantage that modules within an application can be connected by generating a token-type key in the central server and providing it to the module within the application.

In addition, according to the present invention, when a B2B operator provides various application-based modules, movement between modules is possible directly or indirectly through a multi-connection structure, thereby securing user convenience and contributing to increasing the frequency of module use. There is.

Figure 1 is a network configuration diagram to explain a multiple connection system between modules within an application according to an embodiment of the present invention.
Figure 2 is a flowchart illustrating an embodiment of a method for multiple connection between modules within an application according to the present invention.
Figure 3 is an example diagram illustrating a multiple connection method between modules within an application according to the present invention.
Figure 4 is an example diagram illustrating a multiple connection method between modules within an application according to the present invention.

The above-mentioned objects, features, and advantages will be described in detail later with reference to the attached drawings, so that those skilled in the art will be able to easily implement the technical idea of the present invention. In describing the present invention, if it is determined that a detailed description of known technologies related to the present invention may unnecessarily obscure the gist of the present invention, the detailed description will be omitted. Hereinafter, preferred embodiments according to the present invention will be described in detail with reference to the attached drawings. In the drawings, identical reference numerals are used to indicate identical or similar components.

Figure 1 is a network configuration diagram to explain a multiple connection system between modules within an application according to an embodiment of the present invention.

Referring to Figure 1, the multiple connection system between modules within the application includes a user terminal 100, a plurality of modules (200_1, 200_2 to 200_N), an application 300, a central management server 400, and a common API module 500. Includes

The user terminal 100 accesses one module 200_1 or an application 300 among the plurality of modules 200_1, 200_2 to 200_N through a common user interface and uses the application 300 or the plurality of modules 200_1, 200_2. This is a terminal owned by a user who receives ~200_N) services.

This user terminal 100 may be implemented as a smart phone, tablet PC, etc. The common user interface connects multiple modules (200_1, 200_2 to 200_N) and applications (300), and is displayed sequentially starting from the most accessible module.

The user terminal 100 uses the user token received from the central management server 400 to access any one module 200_1 or application 300 among the plurality of modules 200_1, 200_2 to 200_N through a common user interface. Depending on validity, a new user token is received by communicating with the central management server 400 and then used to access one of the modules 200_1 or the application 300 among the plurality of modules 200_1, 200_2 to 200_N or to use it in advance. You can access one of the plurality of modules (200_1, 200_2 to 200_N) (200_1) or the application (300) using the stored user token.

In one embodiment, if the user token received from the central management server 400 is invalid, the user terminal 100 provides a connection approval request message including user information to the central management server 400, and the central management server 400 A user token is received in response to a connection approval request message from (400).

Afterwards, when the user terminal 100 receives the user token from the central management server 400, it provides a login request message including the user token to the application 300 or each of the plurality of modules 200_1, 200_2 to 200_N. The services of the corresponding application 300 or a plurality of modules (200_1, 200_2 to 200_N) can be provided.

In another embodiment, if the user token received from the central management server 400 is valid, the user terminal 100 sends a login request message including the user token to the application 300 or a plurality of modules 200_1, 200_2 to 200_N. ) can be provided to each to receive the services of the corresponding application 300 or a plurality of modules (200_1, 200_2 ~ 200_N).

The central management server 400 controls the user terminal 100 when the user terminal 100 accesses any one module 200_1 or application 300 among the plurality of modules 200_1, 200_2 to 200_N through a common user interface. Receive a connection approval request message from .

Afterwards, the central management server 400 generates a user token and a common token using the user information extracted from the access approval request message, provides the user token to the user terminal 100, and provides the common token to the common API module 500. provides.

In one embodiment, the central management server 400 generates a common token to which token creation information is assigned according to the connection type of the user terminal (eg, by module, by inflow characteristics). At this time, the token creation information may include the type of module accessed and the inflow path (eg, web, mobile, etc.).

The reason for assigning token creation information to the common token is to determine the authentication time in the process of encrypting the common token when the common API module 500 transmits the common token to a plurality of modules (200_1, 200_2 to 200_N) or the application 300. This is so that it can be referenced.

When each of the plurality of modules (200_1, 200_2 to 200_N) receives a login request message including a user token from the user terminal 100, it calls the common API module 500 and receives a common token from the common API module 500. do.

Thereafter, each of the plurality of modules 200_1, 200_2 to 200_N accepts or rejects the login depending on whether the user token and the common token match.

In one embodiment, a plurality of modules (200_1, 200_2 to 200_N) call the common API module 500 to receive a common token from the common API module 500, and then accept login if the common token and the user token match. do.

In another embodiment, a plurality of modules (200_1, 200_2 to 200_N) call the common API module 500 to receive a common token from the common API module 500, and then log in if the common token and the user token do not match. do not accept

Each of the plurality of modules (200_1, 200_2 to 200_N) stores a common token received from the common API module 500, where the common token includes an SSL security authentication key (Http://), SHA256 encryption algorithm, and authentication time. Because it is encapsulated through , it is used only within the authentication time and is discarded once the authentication time has elapsed.

The common API module 500 stores a common token generated by the central management server 400, and the common token is used by the user when the user accesses the application 300 or each of the plurality of modules (200_1, 200_2 to 200_N). Used for authentication.

When transmission of a common token is requested from each of the application 300 or a plurality of modules (200_1, 200_2 to 200_N), the common API module 500 transmits the common token to the application 300 or a plurality of modules (200_1, 200_2 to 200_N). Provided to each.

At this time, the common API module 500 encapsulates the common token using the SSL security authentication key (Http://), SHA256 encryption algorithm, and authentication time to ensure security.

The above SSL authentication key (Http://) is used to encrypt the communication section, the SHA256 encryption algorithm is an algorithm that cannot be decrypted, and the authentication time is used to strengthen security by controlling the time when the common token is valid. In other words, the authentication time ensures that when a common token is leaked through effective time control, it is used and discarded only within a limited time.

At this time, the common API module 500 calculates different authentication times according to token creation information assigned to the common token.

In one embodiment, the common API module 500 determines the time corresponding to the mobile as the authentication time when the token creation information assigned to the common token is mobile.

In another embodiment, the common API module 500 determines whether the connection information (e.g., IP address, etc.) of the user terminal 100 is the same as the predetermined connection information when the token creation information assigned to the common token is web. Depending on availability, the authentication time is determined by decreasing or increasing the time corresponding to the web information.

That is, if the connection information (for example, IP address, etc.) of the user terminal 100 is not the same as the predetermined connection information, the common API module 500 determines that the terminal is different from the existing user terminal and corresponds to web information. The authentication time is determined by reducing the authentication time.

Figure 2 is a flowchart illustrating an embodiment of a method for multiple connection between modules within an application according to the present invention.

Referring to FIG. 2, the central management server extracts user information from the connection approval request message received from the user terminal, generates a user token and a common token using the user information (step S205), and then sends the user to the user terminal 100. A token is provided (step S207) and the common token is provided to the common API module 500 (step S209).

When logging into an application or each of a plurality of modules provided by the application, the user terminal provides a login request message including the user token depending on whether the pre-stored user token is valid (step S210).

The application or each of the plurality of modules that has received the login request message calls a common API module (step S220) and receives a common token from the common API module 500 (step S230).

At this time, the common API module 500 encapsulates the common token using the SSL security authentication key (Http://), SHA256 encryption algorithm, and authentication time to ensure security.

The above SSL authentication key (Http://) is used to encrypt the communication section, the SHA256 encryption algorithm is an algorithm that cannot be decrypted, and the authentication time is used to strengthen security by controlling the time when the common token is valid. In other words, the authentication time ensures that when a common token is leaked through effective time control, it is used and discarded only within a limited time.

The application or each of the plurality of modules that has received the login request message compares the user token extracted from the login request message and the common token received from the common API module (step S240).

The application or each of the plurality of modules that has received the login request message compares the user token and the common token (step S250), allows login according to the comparison result, and provides the corresponding service to the user terminal (step S250).

Figure 3 is an example diagram illustrating a multiple connection method between modules within an application according to the present invention.

Referring to Figure 3, when the office supplies management module 420, attendance management module 430, meal ticket management module 440, and vehicle management module 450 exist in the management support application 410, the user terminal 100 ) can access each of the management support application 410, office supplies management module 420, attendance management module 430, meal ticket management module 440, and vehicle management module 450.

Hereinafter, a case where the user terminal 100 accesses the office supplies management module 420 and then accesses the attendance management module 430 while connected to the office supplies management module 420 will be described.

First, the user terminal 100 may access the office supplies management module 420 depending on whether the user token received from the central management server 400 is valid or not. You can.

In one embodiment, the user terminal 100 provides a login request message including the user token to the office supplies management module 420 if the user token received from the central management server 400 is valid.

In another embodiment, if the user token received from the central management server 400 is invalid, the user terminal 100 provides a connection approval request message including user information to the central management server 400.

Then, the central management server 400 generates a user token and a common token using the user information extracted from the access approval request message, provides the user token to the user terminal 100, and provides the common token to the common API module 500. to provide.

The user terminal 100 receives a user token in response to a connection approval request message from the central management server 400 and then provides a login request message including the user token to the office supplies management module 420.

When the office supplies management module 420 receives a login request message including a user token from the user terminal 100, it calls the common API module 500 and receives a common token from the common API module 500.

The office supplies management module 420 stores a common token received from the common API module 500, and the common token is encapsulated through an SSL security authentication key (Http://), SHA256 encryption algorithm, and authentication time. Therefore, it is used only within the authentication time and is discarded when the authentication time has elapsed.

Thereafter, the office supplies management module 420 accepts or rejects the login depending on whether the user token extracted from the login request message and the common token received from the common API module 500 match.

When the user terminal 100 accesses the attendance management module 430 within the office supplies management module 420, the office supplies management module 420 sends a connection approval request message including a user token to the attendance management module 430. provided to.

Afterwards, when the attendance management module 430 receives a connection approval request message from the office supplies management module 420, it calls the common API module 500, and the common API module 500 performs encryption on the common token. It is provided to the attendance management module 430.

That is, the common API module 500 encapsulates the common token using the SSL security authentication key (Http://), SHA256 encryption algorithm, and authentication time to ensure security.

The above SSL authentication key (Http://) is used to encrypt the communication section, the SHA256 encryption algorithm is an algorithm that cannot be decrypted, and the authentication time is used to strengthen security by controlling the time when the common token is valid. In other words, the authentication time ensures that when a common token is leaked through effective time control, it is used and discarded only within a limited time.

Figure 4 is an example diagram illustrating a multiple connection method between modules within an application according to the present invention.

Referring to FIG. 4, the human resources/general affairs application 410 includes an A module 420, a B module 430, and a C module 440. In the present invention, each of the A module 420, B module 430, and C module 440 in the personnel/general affairs application 410 is multiple connected through a common token stored in a common API module.

To this end, when the central management server receives a connection approval request message from the user terminal, it creates a user token and a common token using the user information extracted from the connection approval request message, provides the user token to the user terminal, and provides the common token to the user terminal. Provided in API module.

At this time, the common token stored in the common API module is only valid for a specific time, and when the user accesses the HR/General Affairs application (410), A module (420), B module (430), and C module (440), the The application 410, A module 420, B module 430, and C module 440 each use a common token stored in a common API.

When each of the above human resources/general affairs application 410, A module 420, B module 430, and C module 440 communicates with the common API and requests a common token, the common API provides SSL security authentication to ensure security. After encapsulating the common token using the key, SHA256 encryption algorithm, and authentication time, the encapsulated common token is sent to the personnel/administrative application (410), A module (420), B module (430), and C module (440). Provided to each.

The above SSL authentication key (Http://) is used to encrypt the communication section, the SHA256 encryption algorithm is an algorithm that cannot be decrypted, and the authentication time is used to strengthen security by controlling the time when the common token is valid. In other words, the authentication time ensures that when a common token is leaked through effective time control, it is used and discarded only within a limited time.

As above, the human resources/general affairs application (410) -> A module (420), B module (430) -> human resources/general affairs application (410), B module (430) <-> C module (440) can be connected. there is.

Although the present invention has been described with reference to limited embodiments and drawings, the present invention is not limited to the above embodiments, and various modifications and variations can be made by those skilled in the art from these descriptions. Accordingly, the spirit of the present invention should be understood only by the scope of the claims set forth below, and all equivalent or equivalent modifications thereof shall fall within the scope of the spirit of the present invention.

100: user terminal
200_1, 200_2 ~ 200_N: Multiple modules
300: Application
400: Central management server
500: Common API

Claims (2)

A central management server extracting user information from a connection approval request message received from a user terminal, and generating token generation information including an accessed module type and inflow path according to the connection type of the user terminal among the extracted user information;
the central management server using the user information to generate a common token and a user token to which the token creation information is assigned, providing the user token to the user terminal and providing the common token to a common API module;
When the common API module requests transmission of a common token from an application or each of a plurality of modules, determining the time corresponding to the mobile as the authentication time when the token creation information assigned to the common token is mobile;
If the token creation information assigned to the common token is web, the common API module determines that the user terminal is different from the existing user terminal if the connection information of the user terminal is not the same as the predetermined connection information, and reduces the time corresponding to the web information. determining an authentication time;
If the access information of the user terminal is the same as the predetermined access information, the common API module determines that it is the same terminal as the existing user terminal, increases the time corresponding to the web information, determines the authentication time, and uses the SHA256 encryption algorithm and authentication time. Proceeding to encapsulate a common token using;
When a user terminal logs into an application or each of a plurality of modules provided by the application, providing a login request message including the user token to the central management server according to whether the pre-stored user token is valid;
The application or each of the plurality of modules through which the user terminal receives the login request message receives a common token from a common API module, and successful login depending on whether the user token and the common token are the same.
Multiple connection methods between modules within an application. In a multi-connection system between modules within an application including a central management server and user terminal,
After extracting user information from the connection approval request message received from the user terminal, token generation information including the accessed module type and inflow path according to the connection type of the user terminal among the extracted user information is generated, and the user information is used. The central management server generates a common token and a user token to which the token creation information is assigned, provides the user token to the user terminal, and provides the common token to the common API module; and
a plurality of modules that, when receiving a login request message including a user token from a user terminal, receive a common token from a common API module and accept login depending on whether the common token and the user token match;
When transmission of a common token is requested from an application or each of a plurality of modules, if the token creation information assigned to the common token is mobile, the time corresponding to the mobile is determined as the authentication time, and the token creation information assigned to the common token is determined as the authentication time. In this case, if the connection information of the user terminal is not the same as the predetermined connection information, it is determined that the terminal is different from the existing user terminal, the time corresponding to the web information is reduced to determine the authentication time, and the connection information of the user terminal is determined in advance. If the connection information is the same, it is determined to be the same terminal as the existing user terminal, and the authentication time is determined by increasing the time corresponding to the web information. A common API module that encapsulates the common token using the SHA256 encryption algorithm and authentication time. ; and
When logging into an application or each of a plurality of modules provided by the application, a login request message including the user token is provided to the central management server depending on whether the pre-stored user token is valid, and the login request message is received. The application or the plurality of modules each includes a user terminal that receives a common token from a common API module and successfully logs in depending on whether the user token and the common token are the same.
Multiple connection system between modules within an application.