KR20170131028A - Management system of private network using public cloud server & management method using the same - Google Patents

Abstract

The present invention relates to a private network client management system through a server of a public network, which is configured to manage a private network client in a server on a public cloud without any separate configuration to control a client in a private network, and to a management method using the same. More specifically, the private network client management system through a server of a public network comprises: a client connected to a private network; and a server constructed in a public network to transmit and receive data to and from the client, and managing the client configured on the private network. The client and the server exchange data with each other based on a representational state transfer application program interface (RESTful API), and the server operates after receiving data from the client.

Description

TECHNICAL FIELD [0001] The present invention relates to a private network client management system using a server of a public network, and a management method using the same. ≪ Desc / Clms Page number 1 >

The present invention relates to a private network client management system through a server of a public network and a management method using the same. More particularly, the present invention relates to a private network client management system for managing a client in a public cloud, To a private network client management system via a server and a management method using the same.

In general, clients providing services in enterprise or home networking can communicate with private IP addresses within a private network.

However, in order to construct a system with a client and a server structure, a server may be built in a private network, or a NAT (Network Address Translation) setting may be performed in a firewall between a private network and a public network, .

That is, in a general server-client management architecture, a management protocol such as Simple Network Management Protocol (SNMP) is used to set configuration information and collect performance information to manage each client in the server.

Therefore, in order to manage the client (s) in the private network, the management server must be built in the same private network.

Alternatively, the management server must be established in the public network, and each connection must be set to be port-forwardable in the firewall so that the client can access the client (s) from the outside (public network) so that the client can access the client (s).

However, in the first case, building and operating a server on its own requires a lot of time and money compared to building and running a server using a public cloud tenancy, Therefore, there is a problem that the benefits of the current cloud and SaaS (Software as a Service) can not be utilized.

In the second case, since the number of clients in the enterprise or home networking is very large and it is installed and removed dynamically, the network management for the clients in the NAT and the firewall, that is, the firewall connection setting for each client, There is a problem that a large cost is required for operation.

Meanwhile, the technology related to the server and the client has been disclosed in Korean Patent Registration No. 10-0793420 (connection system of a server and a client for providing a data transmission service on a network, and connection method between a server and a client or a client and a client using the same) .

(0001) Patent No. 10-0793420

SUMMARY OF THE INVENTION The present invention provides a private network client management system for managing a client of a private network through a server of a public network without a restriction or building a separate network environment between the private network and the public network, And to provide a management method using the same.

Another object of the present invention is to provide a private network client management system using a server of a public network which can facilitate maintenance, maintenance and management of a client of a private network through a server installed in the public network, .

In order to achieve the above object, a private network client management system through a server of a public network of the present invention comprises a client connected to a private network and a server configured to exchange data with the client and to manage the client configured in a private network, Wherein the client and the server exchange data with each other based on a RESTful API (RE-State Application Program Interface), and the server operates after receiving data from the client.

The client includes a RESTful API first center, and the RESTful API first center includes a communication connection unit, a data request unit, and a data processing unit.

The RESTful API first center may further include a network switching unit.

In addition, the server includes a RESTful API second center connected to the public network and a controller.

The RESTful API second center may include a request processing unit, a command queue, and a response processing unit.

In addition, the control information transmitted from the server to the client may include a network switching command for switching from a connection state with any one private network to a connection state with another private network.

The data transmission from the client to the server may be periodically transmitted or transmitted upon occurrence of an event.

Meanwhile, a method of managing a private network client through a server of a public network of the present invention includes a communication connection step, a state information transmission step, and a response information transmission step.

At this time, in the communication connection step, an active state is connected to any one private network and is connected to another private network or a plurality of private networks in a standby state. In the active private network state, As shown in FIG.

The status information transmission step may include an initial information transmission step and a change information transmission step.

In addition, the response information transmitted from the server to the client may include control information for the client.

According to the present invention as described above, data is exchanged between a client connected to a private network and a server constructed in the public network based on a RESTful API (RE-RESTful State Transfer Application Program Interface), and the server transmits data It is possible to manage a client connected to a private network through a server established in the public network without constructing or setting a separate network environment between the private network and the public network.

In addition, by connecting (connecting) the RESTful API first center to the client, the client and the server based service can be easily provided as a plug and play method.

In addition, when the client is connected to a plurality of private networks, the network switching unit is configured in the first center of the RESTful API, so that an immediate action can be taken in the event of a network failure, so that an emergency can be prepared easily.

Also, by configuring the RESTful API second center and control unit in the server built on the public network, it is possible to easily manage the client connected to the private network through the status information transmitted from the client.

In addition, the network environment of a client connected to a plurality of private networks can be diagnosed through a server, and easily changed to a normal private network through a network switching command transmitted from a server when a problem occurs in a currently connected private network or a problem occurs.

In addition, by configuring the transmission of data from the client to the server periodically or transmitting it when an event (accident) occurs, it is possible to promptly cope with the occurrence of a client failure, and to establish a service environment without interruption of the client.

1 is a conceptual diagram schematically showing an embodiment of a private network client management system through a server of a public network according to the present invention,
Fig. 2 is a view schematically showing the configuration of Fig. 1,
3 is a diagram illustrating data transmitted between a client and a server according to an embodiment of the present invention,
4 is a diagram illustrating a method of managing a private network client through a server of a public network according to an embodiment of the present invention.

While the invention is susceptible to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and will herein be described in detail.

It should be understood, however, that the invention is not intended to be limited to the particular embodiments, but includes all modifications, equivalents, and alternatives falling within the spirit and scope of the invention. Like reference numerals are used for like elements in describing each drawing.

The terms including ordinal, such as second, first, etc., may be used to describe various elements, but the elements are not limited to these terms.

The terms used herein are used only for the purpose of distinguishing one element from another. For example, without departing from the scope of the present invention, the second component may be referred to as a first component, and similarly, the first component may also be referred to as a second component. And / or < / RTI > includes any combination of a plurality of related listed items or any of a plurality of related listed items.

It is to be understood that when an element is referred to as being "connected" or "connected" to another element, it may be directly connected or connected to the other element, . On the other hand, when an element is referred to as being "directly connected" or "directly connected" to another element, it should be understood that there are no other elements in between.

The terminology used in this application is used only to describe a specific embodiment and is not intended to limit the invention. The singular expressions include plural expressions unless the context clearly dictates otherwise. In the present application, the terms "comprises" or "having" and the like are used to specify that there is a feature, a number, a step, an operation, an element, a component or a combination thereof described in the specification, But do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, or combinations thereof.

Unless defined otherwise, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. Terms such as those defined in commonly used dictionaries should be interpreted as having a meaning consistent with the meaning in the context of the related art, and unless otherwise explicitly defined in the present application, interpreted in an ideal or overly formal sense It does not.

Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings.

FIG. 1 is a conceptual diagram schematically showing a management system of a private network client 100 through a server 200 of the public network according to the present invention, FIG. 2 is a view schematically showing a configuration state of FIG. 1, FIG. 4 is a diagram illustrating data transmitted between a client 100 and a server 200 according to an embodiment of the present invention.

1 to 3 are conceptual diagrams illustrating an embodiment in which a network separation service client 100 existing in a private network is managed in a SaaS type server 200 on a cloud of a public network. Referring to FIGS. 1 to 3 The management system of the private network client 100 through the public network server 200 of the present invention will now be described.

The private network client 100 management system through the server 200 of the public network of the present invention comprises a client 100 connected to a private network and a client 100 constructed in a public network and exchanges data with the client 100, And a server 200 for managing the server.

At this time, the client 100 and the server 200 exchange data with each other on the basis of the RESTful API (RE-State Transfer Application Program Interface), and the server 200 operates after receiving the data from the client 100 .

The client 100 may be connected to a private network to provide a service, such as a terminal such as an automatic teller machine (ATM) or a computer providing a service, and includes all known devices providing a service through a private network Will be.

The client 100 includes a RESTful API first center 110. The RESTful API first center 110 includes a communication connection unit 111, a data request unit 112, and a data processing unit 113, It can be implemented in hardware. Hardware and the like connected to the client 100 in a plug-and-play manner, it is possible to establish a data transmission environment between the client 100 and the server 200 at the same time of mounting.

The communication connection unit 111 may be configured to connect the client 100 to one private network or to a plurality of private networks. The communication environment of the client 100 can be established such that it is connected to one private network when connected to a plurality of private networks and connected to another private network or a plurality of other private networks in a standby state. Although the connection state of the wired port is shown in the figure, it is conceptually shown to illustrate an embodiment, and the communication connection may be composed of wired communication or wireless communication, or wired communication and wireless communication may be combined.

The data requesting unit 112 transmits status information about the client 100 to the server 200 through any one private network connected in an active state. The status information may include all the information related to the software of the current client 100 including the registration information and the device information of the client 100, and the registration information preferably uses a mac address.

It is preferable that the data (state information) transmission from the client 100 to the server 200 is periodically transmitted or transmitted upon occurrence of an event. Examples of the event include a failure of the client 100, such as a failure of the private network, and event information is also included in the status information.

The data processing unit 113 receives and processes response information for the client 100 transmitted from the server 200 through any one of the private networks connected in the active state.

The RESTful API first center 110 may further include a network switching unit 114 that automatically switches to another private network in a standby state when a failure occurs in an active private network and communicates with the other private network. The client 100 itself can be prepared for the network failure state in the configuration of the network switching unit 114, so that quick response is possible. That is, when one of the active private networks is used, when a network failure occurs to one of the private networks, the other private network in the standby state can be activated and used. In addition, since the information related to the information is also included in the status information and transmitted to the server 200, the server 200 can immediately grasp the situation of the client 100, and the server 200 can quickly cope with the situation.

Meanwhile, the server 200 includes a RESTful API second center 220 and a control unit 210, and can be implemented in software in the cloud public network. Accordingly, the RESTful API first center 110 may be configured as a device on the client 100 side and used immediately upon connection.

The RESTful API second center 220 includes a request processing unit 221, an instruction queue 222, and a response processing unit 223.

The request processing unit 221 transmits the status information transmitted from the client 100 to the control unit 210. [ The control unit 210 is connected to the RESTful API second center 220 and receives status information transmitted from the client 100 through the RESTful API second center 220 and receives the status information transmitted from the client 100 100) and transmits the response response information to the client 100 through the second center 220 of the RESTful API. Alternatively, when a change occurs in the status information, the change command (control information) for the status information is transmitted to the client 100, and the control information is stored in the command queue 222.

The response processing unit 223 transmits the reception response information generated from the control unit 210 to the client 100. When there is a change in the status information, the response processing unit 223 also includes the control information included in the response information.

The control information may include a network switching command for switching from a connection state with any one of the private networks on the client 100 side to a connection state with another private network. However, the server 200 can confirm the malfunction of the network switching unit 114 on the side of the server 200, and it is possible to take immediate action. In addition, since the server 200 can selectively manage other private networks according to the maintenance information on the private network, it is possible to promptly cope with a service failure due to network failure, It is possible.

In FIG. 2, S1 represents the current status information of the client 100, and S2 represents the changed status information at the request of the server 200. FIG. In addition, S3 represents reception response information for S1, and S4 represents response information including control information. An example of information transmission between the client 100 and the server 200 can also be confirmed through FIG.

On the other hand, the status information periodically transmitted from the client 100 to the server 200 can be expressed as follows.

Address: http: // [manager url] / [updateService] / [client macAddress]

HTTP Method: POST

HTTP Body: List of [name] - [value] pairs containing the following information:

- client status name and status value

- client IP

- client model information

- client Serial Number

In addition, the changed status information for sending the command (control information) processing result from the client 100 to the server 200 can be expressed as follows.

Address: http: // [manager url] / [client macAddress] / [commandType] / [commandld]

HTTP Method: POST

HTTP Body: List of [name] - [value] pairs containing the following information:

- command response code

- commandld

- command value

In addition, the response information sent from the server 200 to the client 100 together with the command (control information) can be expressed as follows.

HTTP Response Code: 200 (success), 500 (failure)

HTTP Responder Body: List of [name] - [value] pairs containing the following information:

- commandld

- command value

4 is a diagram illustrating a method of managing a private network client 100 through a public network server 200 according to an embodiment of the present invention. Referring to FIG. 4, a private network client 100 ) Management method is as follows.

Since the contents of the management system described above can be referred to, it will be briefly described step by step.

The method of managing the private network client 100 through the public network server 200 according to the present invention may include a communication connection step S100, a state information transmission step S200, and a response information transmission step S300.

The communication connection step S100 is a step of establishing a private network communication environment of the client 100. The communication connection step S100 may be connected to one private network or may be connected to a plurality of private networks and may be connected to a plurality of private networks. When connected to a plurality of private networks, it is connected to one private network in an active state, connected to another private network or a plurality of private networks in a standby state, and connected to another private network connected in a standby state in an active private network failure .

The state information transmission step S200 is a step of transmitting the state information of the client 100 through the activated private network to the server 200 based on the RESTful API. The state information is transmitted to the server 200 through the active private network, An initial information transmission step S210 for transmitting status information and a change information transmission step for transmitting and receiving control information for the client 100 from the server 200 and transmitting the changed status information of the client 100 S220).

The response information transmission step S300 is a step of transmitting response information to the client 100 through the status information transmitted to the server 200 to the client 100 based on the RESTful API, May be included.

The overall flow of the present invention described above will now be described with reference to a state in which control information is transmitted.

The private network should basically be able to access the external web server 200 from the inside. The client 100 of the private network periodically transmits status information to the server 200 in the public cloud of the public network through the data request unit 112 of the RESTful API first center 110, ).

The server 200 on the public cloud's public cloud sends commands (control information) to be sent from the server 200 to the client 100 in response to HTTP response to the status information sent from the client 100. When the client 100 receives the response information from the RESTful API second center 220, the client 100 checks whether the command (control information) sent from the server 200 is present together with the response information. After processing the command, 1 center 110 to the server 200 through the data request unit 112. [

The client 100 of the private network can perform bidirectional communication with the server 200 without setting an external access private network for the client 100. [

In other words, the present invention is based on the Restful API using a port of HTTP, in view of keeping a security policy for allowing connection and response of an external HTTP port to connect an external web server in a general private network, And transmits the status information to the server 200 side so that the server 200 transmits the response information back to the client 100 side based on the status information.

More specifically, the client 100 provides a network separation service in a private network of a company or an individual, an active port of the client 100 is connected to a private network for general communication, a standby port is connected to a private network do. Each private network is connected to the public network through a firewall and restricts access from the public network.

In addition, the private network itself has a separate address system through NAT (Network Address Translation). The server 200 that manages the client 100 exists in a public network and is based on a virtualization technology such as cloud and SaaS (Software as a Service).

The server 200 can not establish the configuration or collect the status information by directly connecting to the clients 100 in the private network unless the clients 100 are separately connected to the firewall, And periodically transmits status information from the server 100 to the server 200 to the server 200. This periodic state information is transmitted to the first center 110 of the RESTful API in a POST format based on HTTP, and then transmitted to the server 200 through the firewall.

The request processing unit 221 of the RESTful API second center 220 of the server 200 obtains the eigenvalue and state information of the client 100 from the periodic state information and transmits the eigenvalue and the state information to the control unit 210, Determines the validity of the client 100 based on the status information of the client 100. [

The RESTful API second center 220 stores the instructions sent from the control unit 210 to the client 100 in the instruction queue 222. The response processing unit 223 adds json Command (control information) is sent together. The response information is transmitted to the client 100 through the firewall, and the client 100 extracts the control information from the data portion of the response information and performs the setting and changing commands. If the control information does not exist, the state information is maintained. The client 100 transmits the command execution result information to the server 200 in the next state information in response to the command.

The state information including the execution result information of this command is transmitted to the server 200 through the RESTful API first center 110 in POST format based on HTTP. The request processing unit 221 of the RESTful API second center 220 analyzes the status information again and transmits the result to the control unit 210. [ The RESTful API second center 220 stores the control information sent from the control unit 210 to the client 100 in the instruction queue 222 and the response processing unit 223 sends the control information to the data part of the response information for the status information Send json type command (control information) together.

If the response information includes control information, the client 100 repeats the command (control information) processing procedure as described above. If the command does not exist, the state information remains unchanged and the next periodic state information transmission begins.

The control information stored in the command queue 222 is deleted after a predetermined time. For example, when the result information of command execution for the control information is transmitted from the client 100 to the server 200, Even if the execution result information is deleted or the command execution result information is not transmitted to the server 200, the command is deleted after a predetermined period of time. Therefore, the updated command information is updated in the command queue 222 (Which may be control information) is stored and transmitted to the client 100.

It is preferable that the process of transmitting information from the server 200 to the client 100 is repeatedly performed based on information transmission from the client 100 to the server 200 and information transmitted from the client 100 , The status of the client 100 can be checked periodically through repetitive execution, which makes maintenance, maintenance, and management very easy.

For example, in the case of an ATM, conventionally, a server is installed in a separate private network to control the automatic teller machine, or a separate worker is periodically input to perform maintenance and updating functions. According to the present invention, the state of the client 100 can be checked instantaneously through the server 200 of the public network, and the state information of the client 100 can be changed through the server 200 , Which can save a considerable cost compared to the prior art.

In addition, the present invention provides a 1: 1 communication connection between a client 100 and a server 200, so that a plurality of clients 100 are connected to one server 200 to form a plurality of 1: 1 communication connections can do.

100: Client
110: RESTful API first center 111: communication connection
112: Data requesting unit 113: Data processing unit
114: Network switching section
200: Server
210: Control department 220: RESTful API 2nd center
221: Request processing unit 222: Instruction queue
223:
S100: Communication connection step
S200: Status information transmission step
S210: initial information transmission step S220: change information transmission step
S300: Response information transmission step

Claims (11)

Clients connected to a private network; And
And a server configured in the public network to exchange data with the client and manage the client configured in the private network,
Wherein the client and the server exchange data with each other on the basis of a RESTful API (RE-RESTful State Transfer Application Program Interface), and the server operates after receiving data from the client. Client management system.
The method of claim 1, wherein the client includes a RESTful API first center,
The RESTful API first center,
A communication connection unit connected to any one private network in an active state and connected to another private network or a plurality of other private networks in a standby state to establish a communication environment of the client;
A data request unit for transmitting status information on the client to the server through any one private network connected in the active state; And
And a data processing unit for receiving and processing response information for the client transmitted from the server through the one private network connected in the active state.
3. The method of claim 2, wherein the RESTful API first center comprises:
And a network switching unit for automatically switching to another private network in a standby state when a failure occurs in an active private network and communicating with the other private network in a standby state.
The server according to claim 1,
A RESTful API second center for exchanging data with the client and connected to the public network; And
The RESTful API is connected to the second center, receives the status information of the client transmitted from the client through the RESTful API second center, judges the validity of the client based on the received status information, And a control unit for transmitting response information to the client through the center,
Wherein the response information includes control information on a change of the status information, when there is a change in the status information.
5. The method of claim 4, wherein the RESTful API second center comprises:
A request processing unit for transmitting the status information transmitted from the client to the control unit;
A command queue storing control information transmitted from the control unit to the client; And
And a response processor for transmitting the response information to the client.
6. The method according to claim 5,
And a network switching command for switching from a connection state with any one of the private networks to a connection state with another private network.
The method according to claim 1,
Wherein the data transmission from the client to the server is periodically transmitted or transmitted upon occurrence of an event.
A management method using a private network client management system through a server of the public network according to any one of claims 1 to 7,
A communication connection step of establishing a private network communication environment of the client;
A status information transmission step of transmitting status information of the client through the established private network to the server based on the RESTful API; And
And a response information transmitting step of transmitting response information to the client through the RESTful API based on the status information transmitted to the server to the client based on the RESTful API.
9. The method according to claim 8,
A server of a public network connected in an active state to any one private network and connected to another private network in a standby state and connected to another private network connected in a standby state in an active private network failure, How to manage your private network clients.
9. The method of claim 8,
An initial information transmission step of transmitting current status information on the client through the active private network; And
And a change information transmission step of transmitting and receiving control information for the client from the server and transmitting the changed state information of the client to the client.
9. The method according to claim 8,
Wherein the control information for the client is included in the private network client management information.

Images