KR100723881B1 - Customer network management system and method thereof in virtual private networks - Google Patents

Abstract

Disclosed are a subscriber network management system and method thereof in a virtual private network. In the virtual private network according to the present invention, the subscriber network management system receives the subscription information of a specific line to the subscriber information management system and receives key information of the specific line as the line configuration information from the subscriber information management system. The external interworking unit that interfaces with the VPN network management system and the subscriber information management system and the web service interface receives the circuit configuration information from the external interworking unit, and requests the external interworking unit the web service interface with the VPN network management system and the subscriber information management system. It checks the validity of the circuit configuration information through the external interlocking unit, manages the subscriber's profile according to the check result, and includes a CNM configuration processing unit that provides a service according to the type and authority of the subscriber, the subscriber self identity management , Group management and line grouping It is possible to manage, and by automatically correcting errors for data inconsistencies that may occur due to network interworking, subscribers can effectively manage the network.

Description

Subscriber network management system and method in virtual private network {Customer Network Management System And Method Thereof In Virtual Private Networks}

1 is a view for explaining the interworking between a subscriber network management system and another system in a VPN network.

2 is a block diagram schematically showing an embodiment of a subscriber network management system according to the present invention.

3A and 3B are flowcharts illustrating an embodiment of a subscriber network management method performed in the system shown in FIG.

4 is a flowchart illustrating an embodiment of a method of managing a line group of a subscriber in a subscriber network management system of a virtual private network.

The present invention relates to a subscriber network management system in which a subscriber directly manages and operates his or her own information in a virtual private network (VPN). In particular, the present invention relates to an error regarding data inconsistency that may occur due to interworking between networks. The present invention relates to a subscriber network management system and a method in a virtual private network that can be efficiently managed by the subscriber.

Recently, subscriber network that allows subscribers to efficiently manage network configuration, performance, failure, traffic, environment setting, and other additional functions along with VPN (Virtual Private Networks) service, a technology for building private networks in public or Internet networks. The development of a customer network management (CNM) system is actively underway.

International standards for CNM management information are recommended for ATM, X.25data and Frame Relay networks, respectively, in the ATM-Forum M3 specification, the ITU-T X.16x Recommendations and the FR Forum FRF.6 Recommendations. However, these standard documents do not present practical implementation plans for providing virtual private network services or CNM services in the Internet, or specific methods for subscriber information management, policy management, and line error correction. In the prior art in this field, the line opening is given priority as a service standard, and only the contractor applied by the subscriber is reflected, and the facility information tending to be reflected later by the facility worker. As a result, the information between the upper subscriber management system and the lower network management system was inconsistent, which made it difficult to provide accurate information of the network to the subscriber. As a result, the opening of the subscriber network management system was delayed for a long time until the actual facility information and the contract information matched. And even if the subscriber's line was lost due to network error, network management system or process error, it was managed and managed separately after a certain time. In addition, the subscriber ID management, line management, and policy management were performed only after all the subscriber lines were opened, which required a long time until the subscribers could use the customer network management system. In addition, since there is no systematic ID management method, there are many difficulties in integrated subscriber ID management.

The technical problem to be achieved by the present invention is that subscribers can manage their own ID management, group management and line grouping, etc., and the subscribers can efficiently manage the network by automatically correcting errors for data inconsistencies that may occur due to network interworking. To provide a subscriber network management system and a method in a virtual private network capable of.

In order to achieve the above technical problem, it is interoperable with the subscriber information management system constituting the subscriber information in the virtual private network and the VPN network management system, which is a lower network management system at the VPN network level, to operate and manage the operator and subscriber's own network information. In a virtual private network providing a service to enable a subscriber network management system according to the present invention, the subscription information of a specific line is received in the subscriber information management system and the key information of the specific line is transmitted from the subscriber information management system. The VPN network management system is provided as configuration information, and receives the circuit configuration information from the external interworking unit and the external interworking unit, which are web service interfaced with the VPN network management system and the subscriber information management system, upon request. And the subscriber information management system and web service It includes a CNM configuration processing unit for checking the validity of the circuit configuration information through the interface requesting interface and the interface, manages the profile of the subscriber according to the check result, and provides a service according to the type and authority of the subscriber It is preferable.

In order to achieve the above technical problem, it interoperates with the subscriber information management system constituting the subscriber information in the virtual private network and the VPN network management system, which is a lower network management system at the virtual private network level, and operates and manages the network information of the operator and the subscriber himself. Subscriber network management method according to the present invention in a virtual private network that provides a service to enable the subscription information of a particular line is received in the subscriber information management system to provide the key information of a particular line as the line configuration information from the subscriber information management system In step (a), it determines whether there is an error in the circuit configuration information, and if there is an error, stores the error history in a database, and (b) requests an error action from the system operator. The information determines whether the type of line is new, terminated, or changed, and the determination (C) establishing, canceling, or changing circuit information in the database according to the procedure and CNM ID management and group management depending on whether the subscriber has at least one CNM ID or the subscriber has a master ID that can manage the entire circuit. And (d) performing management such as line grouping management.

Hereinafter, a subscriber network management system and a method thereof in a virtual private network according to the present invention will be described in detail as follows.

1 is a view for explaining the interworking between a subscriber network management system and another system in a VPN network.

Referring to FIG. 1, the VPN subscriber network management system 100 includes a subscriber information management system 101 constituting subscriber information in a virtual private network, a failure management system 102 that manages all failures occurring in the virtual private network, and a VPN network. It works in conjunction with the VPN network management system 103, which is a lower level network management system. The CNM operator and subscriber 104 may operate and manage their network information using the VPN subscriber network management system 100.

2 is a block diagram schematically illustrating an embodiment of a subscriber network management system according to the present invention, and includes an external linkage unit 201 and a CNM configuration processing unit 203. 2 illustrates a subscriber information management system 101 and a VPN network management system 103 for convenience of description.

2, the subscriber information management system 101 performs a function of receiving subscription information of all VPN subscriber lines.

The external linkage unit 201 receives the key information of a specific line from the subscriber information management system 101 as line configuration information when the subscription information of a specific line is received by the subscriber information management system 101. 203, the interface between the VPN network management system 103 and the subscriber information management system 101 using a web service at the request of the CNM configuration processing unit 203. In detail, the external linkage unit 201 includes a configuration message queue 202 and a configuration information interworking module 208.

When the subscription information of a specific line is received by the subscriber information management system 101, the configuration message queue 202 receives the subscription information of a specific line from the subscriber information management system 101, and configures the received subscription information of the specific line. The information is sent to the CNM configuration processing unit 203.

The configuration information interworking module 208 serves as a mutual interface between the CNM configuration processing module 203, the VPN network management system 103, and the subscriber information management system 101.

When CNM configuration processing unit 203 receives the line configuration information from the external interlocking unit 201, the CNM configuration processing unit checks the validity of the line configuration information in conjunction with the external interlocking unit 201, manages the subscriber's profile according to the check result, Provide services according to their type and authority. Specifically, the CNM configuration processing unit 203 includes a subscription processing unit 204, a web interface 212, a VPN policy management unit 209, and a database management unit 211.

When the subscription processing unit 204 receives the line configuration information from the external interlocking unit 201, it checks the validity of the line configuration information in conjunction with the external interlocking unit 201, and the line management, ID performed by the subscriber according to his authority Manage subscriber profiles according to management and group management of circuits. In addition, the subscription processing unit 204 provides the error information to the database management unit 211 when it is confirmed that there is an error as a validity check. In detail, the subscription processing unit 204 includes an event receiver 205, a validity checker 207, and a profile manager 210.

The event receiving unit 205 receives line configuration information for a specific line from the external interlocking unit 201. Attributes of the circuit configuration information include customer ID, port identifier, circuit type, CNM ID information, master ID information, group information, circuit grouping information, and the like. Here, the customer ID is a customer ID identified internally in the system, and the CNM ID indicates an ID of a user who can access through the web interface 212. Further, the line type indicates whether the received line configuration information is new, terminated, or changed in the line. Master ID is an ID that has the authority to create / modify / delete CNM ID separately, and it is an ID of an administrator's nature that can manage the entire line information assigned to integrated subscribers. Do. The circuit grouping information is information in which lines are grouped by CNM IDs by a subscriber having a master ID, and the group information is information classified into a specific group by subscribers having a corresponding CNM ID in a circuit grouped by CNM IDs.

 The validity checker 207 interoperates with the VPN network management system 103 through the configuration information interlocking unit 208 of the external interlocking unit 201 when the line configuration information is received through the event receiving unit 205. In other words, it is checked whether the contents of the line configuration information exist in the lower VPN network management system 103 constituting the VPN network and whether the contents match. If the content of the line configuration information does not exist or does not match in the VPN network management system 103, the error history is provided to the database management unit 211.

 The profile manager 210 manages the subscriber's profile in real time according to the subscriber's line management, ID management, and group management of the circuit according to his / her authority. Here, the subscriber's authority is whether the subscriber is a subscriber to which the master ID has been granted. As described above, the master ID is an ID having a right to separately create / change / delete a CNM ID and is an ID of an administrator's personality capable of managing the entire line information assigned to the integrated subscriber. Therefore, the upper subscriber with the master ID can manage the profile and perform ID management and group management of the entire line. On the other hand, the lower subscriber who has not been given the master ID can manage the profile while performing ID management, group management, and circuit grouping only on some circuits he can manage.

Subsequently, the VPN policy management unit 209 checks the type and authority of the customer, that is, the subscriber, and checks the services provided by the system according to the authority of the subscriber, such as system configuration information, system failure information, system performance information, and other additional services. Provided selectively. The type of subscriber can be classified into a 'premium customer' and a 'general customer', and the VPN policy management unit 209 provides a service according to the rights of the subscriber.

The database manager 211 stores and manages the circuit information and all the configuration information of the subscriber and the error history provided from the validity checker 207 in a database, and generates statistical information about the error history for a predetermined period and provides the system operator to the system operator. do. Here, the statistical information includes error history information of the line, worker information, system error information, and the like. The system operator may use the error information to handle the error history between the VPN network management system 103 and the subscriber information management system 101.

The web interface 212 allows a customer to receive subscriber network management service using a CNM ID.

3A and 3B are flowcharts illustrating an embodiment of a subscriber network management method performed in the system shown in FIG.

2, 3A and 3B, the external interlocking unit 201 and the CNM configuration processing unit 203 are driven to process the line subscription of the CNM subscriber in the virtual private network (step 301).

After the step 301, the event receiving unit 205 receives the line configuration information on the specific line from the subscriber information management system 101 through the configuration message queue 202 of the external linking unit 202 (step 302). As described above, the attributes of the circuit configuration information include a customer ID (CustID), a port identifier, a circuit type, a CNM ID, a master ID, group information, and circuit grouping information.

After step 302, the validity check unit 207 is connected to the subscriber management system 101 and the VPN network management system 103 through the configuration information linkage module 208 using the web service in the external linkage unit 201. The key value is checked to confirm the existence of the corresponding line (step 304).

If the content of the line configuration information received from the subscriber information management system 101 does not exist in the VPN network management system 103 in step 304, the circuit configuration information error is provided to the database manager 211 (step 307). . On the other hand, in step 304, if there is a subscriber line in the VPN network management system 103, the validity check unit 207 through the configuration information linkage module 208 subscriber information management system 101 and VPN network management system 103 In step 305, all the information about the line is taken from each of them, and their correspondence is examined. Here, all information about the line is subscriber information (subscriber ID, subscriber name, etc.) and line information (line identifier, IP information, etc.).

In step 305, if all information on the corresponding line between the VPN network management system 103 and the subscriber information management system 101 does not match, a mismatch history regarding the line information and the subscriber information is provided to the database manager 211. Notify the operator (step 306).

After operation 306, the database manager 211 generates statistical information on an error history on a daily basis and provides the same to the operator (operation 307). As described above, the contents of the statistical information include line error history information, worker information, system error information, and the like.

After operation 307, the operator measures line / subscriber error between the VPN network management system 103 and the subscriber information management system 101 and retransmits the line configuration information for the corresponding line to the subscriber information management system 101. Request (step 308). Through this process, it is possible to manage such that there is no error in subscriber and line information between the VPN subscriber network management system 100, the VPN network management system 103, and the subscriber information management system 101.

On the other hand, if all information on the line between the subscriber information management system 101 and the VPN network management system 103 in step 305 is identical, the profile manager 210 performs line management according to the line type in the line configuration information.

First, the profile manager 210 analyzes the line type from the line configuration information (step 309).

In step 309, if the line type is changed, the profile manager 210 checks whether subscriber / line information for the subscriber exists in the database (step 317).

In step 317, if there is subscriber / line information, the profile manager 310 updates the changed subscriber / line information to the database through the database manager 211 (step 318).

On the other hand, in step 317, if the subscriber / line information does not exist in the database, the validity check unit 207 corresponds to the subscriber information management system 101 and the VPN network management system 103 through the configuration information linkage unit 208. In step 319, the subscriber / line information about the subscriber is checked to determine whether the line for the CNM subscriber is correct.

If the validation check is true in step 319, it may be determined that the subscriber / line information of the corresponding subscriber is missing from the database due to a network error or a system error. In this case, the flow proceeds to step 310 and newly establishes subscriber / line information of the corresponding subscriber in a database. In this case, the subscriber / line information of the subscriber is established and the validity check unit 207 obtains all the subscriber / line information of the subscriber from the subscriber information management system 101 through the configuration information linkage unit 208 and stores it in a database. Just do it. In operation 319, the database may be actualized for the missing line even in the system. If the validity check is not true in step 319, it is determined that the CNM subscriber does not have the right to change the line information, and terminates without performing the line information change.

On the other hand, if the line type is new in step 309 or the validity of the CNM subscriber is confirmed in step 319, the validity check unit 207 brings all the line information about the subscriber through the configuration information interworking module 208 to the database. Store and newly establish the subscriber's line information, and if the line type is terminated, deletes the subscriber's subscriber / line information from the database (step 310).

After step 310 or step 318, the profile manager 210 checks whether the master ID flag is set in the currently received line configuration information (step 320). As described above, the master ID flag indicates whether or not the corresponding subscriber is authorized to manage information on the entire line assigned to the integrated subscriber.

In step 320, if the master ID flag is set, a master ID for the corresponding subscriber is generated (step 321), and the subscriber is authorized to manage the entire line. In step 322, the flag is checked for the entire circuit of the integrated subscriber stored in the database so that the subscriber assigned the master ID can manage the entire circuit assigned to the integrated subscriber. Here, checking the flag means that the flag is managed by the subscriber having the master ID for the checked line.

After step 322, it is checked whether group management of the line is set (step 323). In step 323, if the group management of the line is set, the subscriber who has been assigned the master ID creates / deletes a specific group, or selects / adds / changes / deletes only the desired line information to a specific group already created. The line is group-managed (step 324). In addition, line grouping for grouping circuits by CNM IDs may be performed together with group management of subscribers to whom a master ID has been assigned in step 324. After operation 324, the database manager 311 stores the results of operations 321 to 324 in the database (operation 325). On the other hand, if the group management of the line is not set in step 323, the results of the steps 321 and 322 are stored in the database (step 325).

On the other hand, in step 320, if the master ID flag is not set in the circuit configuration information, it is checked whether or not the CNM ID of the subscriber exists (step 328). In step 328, if the CNM ID of the corresponding subscriber does not exist, CNM authority is generated by generating a CNM ID for the corresponding subscriber (step 332). On the other hand, in step 328, if there is a CNM ID of the subscriber, it is determined whether to further generate a CNM ID (step 329). In step 329, if the subscriber additionally generates a CNM ID, the process proceeds to step 332 to add a new CNM ID and grants CNM authority to the added CNM ID. On the other hand, in step 329, it is determined whether or not the authority available to the corresponding subscriber is changed or deleted (step 330). As described above, according to the present invention, a plurality of CNM IDs can be managed for one circuit, and therefore, it is possible to group and manage circuits for each CNM ID. This method allows a subscriber to efficiently manage subscriber information of a network management system in a virtual private network. For example, by managing a plurality of CNM IDs, subscriber information can be selectively provided for each subscriber. In addition, a customer with a specific CNM ID can be controlled to view only the lines grouped into the group to which they belong. This can provide reliable services by applying to security between mutual subscribers.

After step 332 or step 330, the group line information is analyzed and the process proceeds to step 323 (step 331), in which a specific group is created / deleted for circuits grouped by the corresponding CNM ID or is already created. The group is managed by selecting / adding / changing / deleting only the line information desired by the subscriber in the specific group and storing the result in the DB (steps 323 to 325).

4 is a flowchart illustrating an embodiment of a method of managing a line group of a subscriber in a subscriber network management system of a virtual private network.

Referring to FIG. 4, when a CNM customer logs in through a line management site provided from a subscriber network management system (operation 400), the subscriber network management system performs a login procedure and checks whether the login ID is a master ID. Confirm (step 401).

If the login ID is not the master ID in step 401, it is determined whether to perform separate group management based on the circuit grouped with the CNM ID used for logging in (step 406).

If it is determined in step 406 that group management is to be performed, group creation / modification / deletion management is performed (step 407), and the result of performing group management is stored in a database (step 408).

On the other hand, in step 406 it is confirmed that the group management is not to be performed or after step 408, the CNM service provided by the subscriber network management system is used (step 409), and when the service is completed, the user logs out (step 410). step).

On the other hand, if the login ID is confirmed as the master ID in step 401, it is checked whether or not to manage the CNM ID (step 402).

If it is determined in step 402 that CNM ID management is not to be performed, the flow proceeds to step 406 to perform group management for classifying all or part of circuits into a specific group. However, if it is determined in step 402 that the CNM ID is to be managed, a CNM ID is generated / changed / deleted with respect to the CNM ID that is newly created, changed or deleted (step 403).

After step 403, it is checked whether line grouping management is performed on the CNM ID generated / changed in step 403 (step 404).

If it is determined in step 404 that the circuit grouping management is not to be performed, the flow proceeds to step 406 to perform group management for classifying all or part of circuits into a specific group. However, if it is determined in step 404 that the circuit grouping management is to be performed, after the circuit grouping is performed (step 405) by setting a flag for the circuits (all or a part) that the subscriber directly manages for each CNM ID of the subscriber, In step 406, group management for classifying and managing all or part of the circuit into a specific group is performed.

The above circuit grouping management and group management will be described in detail. For example, if Company A has a total of 12 lines, and Subscriber B has a Master ID, Subscriber B can also provide Subscriber C with a CNM ID to provide information on some lines. That is, subscriber B can provide subscriber C with information about the selected 10 circuits by selecting a circuit of the 12 circuits, for example 10, and grouping them with the CNM ID for subscriber C (step 405). . At this time, when subscriber C logs in with his CNM ID, he can be provided with information on 10 circuits grouped by his CNM ID and manages the circuit. In addition, subscriber C may classify the 10 circuits grouped to the user into a specific group and manage the circuits for each group (steps 406 to 407).

As described above, according to the subscriber network management system and method therefor in the VPN network according to the present invention, the upper subscriber having the master ID performs ID management, group management and line grouping of the subscriber over the entire circuit, and CNM The subordinate subscriber who is given ID can systematically manage ID management, group management, and circuit grouping by performing ID management, group management, and circuit grouping on some circuits that can be managed. In addition, the subscriber's information such as automatic line grouping function and the database's current function for missing line are corrected for system-specific error of subscriber's circuit configuration information managed in various systems in the Internet and public network environment that make up the virtual private network. Can be managed accurately and systematically.

The invention can also be embodied as computer readable code on a computer readable recording medium. The computer-readable recording medium includes all kinds of recording devices in which data that can be read by a computer system is stored. Examples of computer-readable recording media include ROM, RAM, CD-ROM, magnetic tape, floppy disk, optical data storage, and the like, which are also implemented in the form of a carrier wave (for example, transmission over the Internet). It also includes. The computer readable recording medium can also be distributed over network coupled computer systems so that the computer readable code is stored and executed in a distributed fashion. And functional programs, codes and code segments for implementing the present invention can be easily inferred by programmers in the art to which the present invention belongs.

Although the preferred embodiments of the present invention have been shown and described above, the present invention is not limited to the specific preferred embodiments described above, and the present invention belongs to the present invention without departing from the gist of the present invention as claimed in the claims. Various modifications can be made by those skilled in the art, and such changes are within the scope of the claims.

 As described above, the subscriber network management system and method in the VPN network according to the present invention, the upper subscriber with the master ID performs ID management, group management and line grouping of the subscriber for the entire circuit, and grants CNM ID. Received subordinate subscriber can systematically manage ID management, group management, and circuit grouping by performing ID management, group management, and circuit grouping only on some circuits that can be managed. In addition, it is possible to accurately and systematically manage subscriber information by compensating system-specific errors with respect to circuit configuration information of subscribers managed in various systems in an Internet network and a public network environment constituting a virtual private network.

Claims (13)

Virtual to interoperate with the subscriber information management system constituting the subscriber information in the virtual private network and the VPN network management system, which is a lower network management system at the virtual private network level, and provide services for operating and managing the network information of the operator and subscriber. In the subscriber network management system in a private network, Subscription information of a specific line is received by the subscriber information management system, and receives key information of the specific line as line configuration information from the subscriber information management system, and upon request, the VPN network management system and the subscriber information. An external interworking unit that interfaces with the management system and the web service; And When the circuit configuration information is received from the external interlocking unit, the external interworking unit requests a web service interface with the VPN network management system and the subscriber information management system, and checks the validity of the circuit configuration information through the interface. The subscriber network management system in the virtual private network, characterized in that it comprises a CNM configuration processing unit for managing the profile of the subscriber according to the check result, and providing services according to the type and authority of the subscriber. In Figure 1, the external linkage, A configuration message queue for transmitting the line configuration information provided from the subscriber information management system to the CNM configuration processing unit; And And a configuration information interworking module configured to interface a web service with the VPN network management system and the subscriber information management system according to a request of the CNM configuration processing unit. The CNM configuration processing unit according to claim 1, When the circuit configuration information is received from the external linkage unit, the validity of the circuit configuration information is checked through a web service interface of the external linkage unit, and if there is an error, error information is provided. Subscription processing unit for managing the profile of the subscriber according to the line management, ID management and group management of the line to perform; A VPN policy management unit which checks the type and authority of the subscriber and selectively provides the services provided by the system according to the authority of the subscriber; A database manager that stores and manages subscriber information, line information, and error details provided from the validity checker in a database, and generates statistical information on the error details for a predetermined period and provides the system operator to the system operator; And Subscriber network management system in a virtual private network, characterized in that it comprises a web interface for providing subscriber network management services to subscribers connected using their unique ID. According to claim 3, wherein the subscription processing unit An event receiver for receiving the line configuration information from the external linkage unit; When the circuit configuration information is received from the event receiver, the existence and matching of the circuit configuration information is checked between the VPN network management system and the subscriber information management system through a web service interface of the external interworking unit. A validity check unit for providing an error history to the database manager; And And a profile management unit configured to manage the profile of the subscriber in real time according to the result, when the subscriber performs line management, ID management, and group management of the line according to his / her authority. It interoperates with the subscriber information management system constituting subscriber information in the virtual private network and the VPN network management system, which is a lower network management system at the virtual private network level, and provides services for operating and managing the network information of the operator and subscriber. In the subscriber network management method in a virtual private network, (a) receiving subscription information of a specific line in the subscriber information management system and receiving key information of the specific line as line configuration information from the subscriber information management system; (b) determining whether the line configuration information is in error, if there is an error, storing an error history in a database, and requesting an error action from a system operator; (c) if there is no error in the circuit configuration information, determining whether the type of the circuit is new, terminated, or changed in the circuit configuration information, and constructing, canceling, or changing the circuit information in the database according to the determination result; And (d) performing management of CNM ID management, group management, and circuit grouping management according to whether the subscriber has at least one CNM ID or a subscriber having a master ID capable of managing the entire circuit. Subscriber network management method in a virtual private network. The method of claim 5, The circuit configuration information includes a customer ID, a port identifier, a circuit type, a CNM ID, a master ID information, a group information, and a circuit grouping information. The method of claim 5, wherein (b) is (b1) checking whether the contents of the line configuration information received from the subscriber management system actually exist in the VPN network management system; (b2) if the content of the circuit configuration information does not actually exist in the VPN network management system, storing the circuit configuration information error in a database and requesting an error action from a system operator; (b3) if the contents of the circuit configuration information are actually present in the VPN network management system, retrieving all the information on the corresponding line from each of the subscriber information management system and the VPN network management system and examining their correspondence; ; And (b4) If the information on the corresponding line does not match in the step (b3), the subscriber network management in the virtual private network, characterized in that it comprises storing the inconsistency in the database, and requesting an error action to the system operator Way. The method of claim 5, wherein step (c) (c1) determining whether a type of a line is new, terminated, or changed in the line configuration information; (c2) if the type of the line is new in step (c1), reconstructing the line information of the subscriber by retrieving all the information of the corresponding line from the subscriber information management system and storing it in the database; (c3) if the type of the line is terminated in step (c1), deleting all information of the line from the database; (c4) if the line type is changed in step (c1), checking whether line information of the line exists in the database; (c5) if the line information of the line exists in the database in step (c4), changing the line information; (c6) If the line information of the corresponding line does not exist in the database in step (c4), check the line information of the subscriber information management system and the VPN network management system to confirm whether the corresponding line is a line for the CNM subscriber. Doing; (c7) if the corresponding line is identified as a line for the CNM subscriber in step (c6), retrieving line information about the corresponding line from the subscriber information management system and newly constructing it in the database; And (c8) if it is determined in step (c6) that the corresponding line is not a line for the CNM subscriber, terminating the operation, characterized in that the subscriber network management method in a virtual private network. The method of claim 5, wherein step (d) (d1) checking whether the master ID flag is set in the currently received circuit configuration information; (d2) If the master ID flag is set, the master ID is generated for the subscriber so that the subscriber can manage the entire line, and group management and line grouping for the entire line is performed according to the authority of the master ID. step; And (d3) if the master ID flag is not set in the circuit configuration information, performing group management on circuits grouped by the CNM ID according to the authority of the CNM ID. Subscriber network management method. The method of claim 9, wherein step (d2) (d21) if the master ID flag is set, generating a master ID for the subscriber so that the subscriber can manage the entire line; (d22) checking whether group management of the line is set; (d23) If line management is set, create / delete a specific group, or select / add / change / delete only the desired line information to a specific group that has already been created. Performing circuit grouping to group the circuits; And (d24) A method for managing a subscriber network in a virtual private network, comprising storing group management and circuit grouping results in a database. The method of claim 9, wherein step (d3) (d31) if a master ID flag is not set in the circuit configuration information, managing a CNM ID according to whether a CNM ID of a corresponding subscriber exists; (d32) analyzing group information of the corresponding line to confirm whether group management of the line is set; (d33) performing group management of the line, such as creating / deleting a specific group or selecting / adding / changing / deleting only the line information desired by the subscriber to the already created specific group if the line management is set ; And (d34) A method for managing a subscriber network in a virtual private network, comprising storing group management results in a database. The method of claim 11, wherein step (d31) (d311) if a master ID flag is not set in the line configuration information, checking whether a CNM ID of the corresponding subscriber exists; (d312) generating a CNM ID for the subscriber and granting CNM authority if the CNM ID for the subscriber does not exist; And (D313) If the CNM ID for the subscriber exists, the subscriber in the virtual private network comprising the step of additionally creating or changing / deleting the CNM ID according to whether to create additional CNM ID How to manage your network. A recording medium having recorded thereon a program capable of executing the method of any one of claims 5 to 12 with a computer.

Images