KR20230143822A - Method and apparatus for providing QoS based restoration services of network failure - Google Patents

Abstract

This disclosure relates to a software-based network recovery method and device that can provide network services of various qualities depending on the time required for fault recovery. This disclosure is controlled by a central control management system, and various failure recovery service settings and performance procedures can be implemented by referring to the failure recovery service level defined by the failure recovery service table. Accordingly, users can select network service quality according to their budget.

Description

{Method and apparatus for providing QoS based restoration services of network failure}

This disclosure relates to a software-based network recovery method and device that can provide network services of various qualities depending on the time required for fault recovery.

Network service refers to a service in which a telecommunication service provider establishes a network connecting remote sites to transmit reliable voice/data to customers.

If it is difficult to provide normal network service due to a current network failure, the network service is normally restored by replacing the failed working path with a backup path using two representative methods. The two methods include protection transfer method (data plane protection) and failure recovery method using a central control management system (MCS based restoration). The protection switching method replaces the working path with a backup path using the hardware-based APS (Automatic Protection Switching) protocol between transmission devices such as routers. On the other hand, the failure recovery method is a software-based method of replacing the working path with a backup path through a protocol between the transmission equipment and the central control management system.

The protection transfer method is currently widely used because it allows rapid fault recovery within 50ms. However, since it operates based on hardware and always requires waiting for a backup path, it has the disadvantage of reducing operational flexibility and efficiency in network resource use. The failure recovery method performs failure recovery through a central control management system. The fault recovery method has the disadvantage that it takes a lot of time to recover from a fault compared to the protection transfer method. However, because it operates based on software, it can provide flexibility in network operation. Nevertheless, the failure recovery method is not actively used because there is no method of providing various services that utilizes this flexibility. In order to overcome this problem, the present invention provides various failure recovery service methods depending on the time required for failure recovery.

The technical problem of the present disclosure is to provide a failure recovery method that can provide various failure recovery times according to the requirements of network users.

Additionally, the purpose of the present disclosure is to provide various quality failure recovery services depending on the time required for failure recovery.

Additionally, the purpose of the present disclosure is to enable users to select network service quality for failure recovery according to their budget.

The technical problems to be achieved by this disclosure are not limited to the technical problems mentioned above, and other technical problems not mentioned can be clearly understood by those skilled in the art from the description below. You will be able to.

According to an embodiment of the present disclosure, a method and device for providing a network failure recovery service are disclosed.

According to an embodiment of the present disclosure, in a method of providing a network failure recovery service performed by a central control and control system (MCS), a failure recovery service level and a first parameter related to the failure recovery service level are received. steps; determining a working path based on the first parameter; determining a second parameter required for a failure recovery service from a failure recovery service table based on the failure recovery service level; Receiving whether a failure has occurred in a working path detected by a network node; and upon receiving whether a failure of the working path has occurred, restoring the network service according to the second parameter.

The step of receiving the failure recovery service level may be characterized by receiving a failure recovery service level determined by considering the time required for failure recovery desired by the user.

The first parameter may include at least one of a used bandwidth, an end point, a source, or a destination.

The second parameter may include either a failure recovery failure type or a backup path setting method.

The failure recovery failure type is any of standard fault (Standard Fault, S Fault), customized fault (C Fault), standard alarm (Standard Alarm, S Alarm), or custom alarm (Customized Alarm, C Alarm). It could be one.

The backup path setting method may be one of an activated backup path, a predefined backup path, or an undefined backup path.

The central control management system may include a step of instructing network nodes passing through the working path to perform working path setting.

The central control management system may further include instructing the network nodes to set a failure recovery service using a second parameter.

The second parameter may include at least one of a failure recovery failure type or a backup path setting method.

The step of instructing the network nodes to configure the failure recovery service may include instructing the relevant network nodes to configure OAM (Operation Administration Maintenance) to monitor the working path using the failure recovery failure type information. there is.

The step of instructing the network nodes to set up the disaster recovery service may include preparing a backup path according to a backup path setting method.

The central control management system may include a step of normalizing the service by transferring data traffic from the failed working path to the backup path.

It may include the step of the central control management system instructing the network node to restore data traffic on a failed working path by diverting it to a backup path.

According to another embodiment of the present disclosure, in a method for providing a network failure recovery service,

Network nodes performing working path settings instructed by the central control management system; performing second parameter settings instructed by the central control management system; Monitoring the occurrence of a failure in the working path; If a failure occurs in the working path as a result of monitoring the failure occurrence, notifying the central control management system of the failure; And it may include a step of recovering the data traffic of the broken working path by diverting it to the backup path according to the instructions of the central control management system.

The second parameter may include at least one of a failure recovery failure type or a backup path setting method.

The step of setting the second parameter may include setting the OAM to monitor a failure of the working path using the failure recovery failure type information.

The step of setting the second parameter may include preparing a backup path according to a backup path setting method.

According to another embodiment of the present disclosure, an apparatus for providing a network failure recovery service performed by a central control management system includes: a first parameter receiving unit that receives a failure recovery service level and a first parameter related to the failure recovery service level; a working path determination unit that determines a working path based on the first parameter; a second parameter determination unit that determines a second parameter required for a failure recovery service from a failure recovery service table based on the failure recovery service level; It may include a failure status receiver that receives whether a failure has occurred in the working path detected by the network node, and when receiving whether a failure has occurred in the working path, restores the network service according to the second parameter. .

The second parameter may include at least one of a failure recovery failure type or a backup path setting method.

The failure recovery service level may be determined in consideration of the failure recovery time desired by the user.

The features briefly summarized above with respect to the present disclosure are merely exemplary aspects of the detailed description of the present disclosure described below, and do not limit the scope of the present disclosure.

According to the present disclosure, it is possible to provide various quality failure recovery services depending on the time required for failure recovery.

Additionally, according to the present disclosure, the user has the advantage of being able to select the network service quality according to his or her budget.

Additionally, according to the present disclosure, various failure recovery times can be provided according to the requirements of network users.

The effects that can be obtained from the present disclosure are not limited to the effects mentioned above, and other effects not mentioned can be clearly understood by those skilled in the art from the description below. will be.

1 is a flowchart illustrating a method for providing a network failure recovery service according to the present disclosure.
Figure 2 is a diagram showing a failure recovery service table of the present disclosure.
Figure 3 is a diagram showing a simple network structure for the failure recovery service of the present disclosure.
FIG. 4 is a diagram illustrating a network structure for a failure recovery service of the present disclosure.
Figure 5 is a diagram illustrating a procedure for providing a disaster recovery service according to the present disclosure.
Figure 6 is a diagram illustrating a procedure for providing a failure recovery service according to an embodiment of the present disclosure.
FIG. 7 is a diagram illustrating an example of the configuration of a network failure recovery service providing device of the present disclosure.

Hereinafter, with reference to the attached drawings, embodiments of the present disclosure will be described in detail so that those skilled in the art can easily practice them. However, the present disclosure may be implemented in many different forms and is not limited to the embodiments described herein.

In describing embodiments of the present disclosure, if it is determined that detailed descriptions of known configurations or functions may obscure the gist of the present disclosure, detailed descriptions thereof will be omitted. In addition, in the drawings, parts that are not related to the description of the present disclosure are omitted, and similar parts are given similar reference numerals.

In the present disclosure, when a component is said to be “connected,” “coupled,” or “connected” to another component, this is not only a direct connection relationship, but also an indirect connection relationship in which another component exists in between. It may also be included. In addition, when a component is said to "include" or "have" another component, this does not mean excluding the other component, but may further include another component, unless specifically stated to the contrary. .

In the present disclosure, terms such as first and second are used only for the purpose of distinguishing one component from other components, and do not limit the order or importance of the components unless specifically mentioned. Therefore, within the scope of the present disclosure, a first component in one embodiment may be referred to as a second component in another embodiment, and similarly, the second component in one embodiment may be referred to as a first component in another embodiment. It may also be called.

In the present disclosure, distinct components are only for clearly explaining each feature, and do not necessarily mean that the components are separated. That is, a plurality of components may be integrated to form one hardware or software unit, or one component may be distributed to form a plurality of hardware or software units. Accordingly, even if not specifically mentioned, such integrated or distributed embodiments are also included in the scope of the present disclosure.

In the present disclosure, components described in various embodiments do not necessarily mean essential components, and some may be optional components. Accordingly, embodiments consisting of a subset of the elements described in one embodiment are also included in the scope of the present disclosure. Additionally, embodiments that include other components in addition to the components described in the various embodiments are also included in the scope of the present disclosure.

In this disclosure, expressions of positional relationships used in this specification, such as top, bottom, left, right, etc., are described for convenience of explanation, and when the drawings shown in this specification are viewed in reverse, the positions described in the specification The relationship can also be interpreted the other way around.

Prior to explanation, the terms used in this specification will be briefly explained.

'Network service' as used in this specification is a term used to mean a service that enables a communication service provider to transmit voice/data to customers by configuring a network connecting remote sites.

'Failure', as used in this specification, is used to mean a state in which a failure recovery service is required because it is difficult to provide normal network services to users.

‘Types of restoration failure’ used in this specification refers to types of failures that require restoration services because it is difficult to provide normal network services, and includes faults and alarms. There is an (alarm).

'Fault' as used in this specification is used to mean a failure declared when a network abnormal state persists for more than a certain period of time, and the type of fault is determined by the standard (ITU) according to the communication protocol used. -T, etc.) or by the user, and representative examples may include LOC (Loss of Connectivity), LOS (Loss of Signal), and LOF (Loss of Frame).

'Alarm', as used in this specification, is used to mean a failure declared when a network fault condition persists for more than a certain period of time, and the type of fault is determined by standard (standard) depending on the communication protocol used. ITU-T, etc.) or can be defined by the user.

The 'Central Management and Control System (MCS)' used in this specification is used to mean a system that directly controls and manages network equipment (nodes) in a centralized manner.

'Network service parameters' used in this specification refer to service parameters that a user uses to request a network service from a communication service provider, and can be broadly divided into two parameters. These include general service parameters used for general network services (hereinafter referred to as 'first parameters') and failure recovery service parameters used for failure recovery services (hereinafter referred to as 'second parameters'). General service parameters may include usage bandwidth, service level, connection point (end point), etc., and failure recovery service parameters may include failure recovery service grade. Before entering into a service agreement with a user, the communication service provider determines the type of failure recovery failure and backup path to be used according to the failure recovery service level, and can provide related information to the user when necessary.

'MCS based Restoration' used in this specification is a term that refers to a software-based method of normalizing network services by replacing a failed network (working) path with a backup path using a central control management system. It is a fault recovery method that is distinguished from the data plane protection method that operates based on hardware by the APS (Automatic Protection Switching) protocol between currently widely used data transmission equipment.

'Restoration time' used in this specification is a term used to mean the time required to restore normal service by replacing the broken working path with a backup path after a fault occurs.

'Types of backup path' used in this specification can be divided into three types depending on the method of setting the backup path before a network failure occurs, and may affect the failure recovery time. Specifically, there may be an activated backup path, a predefined backup path, and an undefined backup path.

The present disclosure is a software-based network recovery method and device that can provide network services of various qualities depending on the time required for fault recovery.

The quality (grade) of failure recovery service is determined by the time required for failure recovery when a failure occurs. The shorter the time it takes to recover from a failure, the more service interruption time can be minimized, making it possible to provide high-quality network services. On the other hand, rapid recovery from failure requires network resource reservation to standby the backup path, which increases costs. Key parameters that determine the time required for restoration include types of restoration failure and types of backup path.

Hereinafter, an apparatus and method according to an embodiment of the present disclosure will be described with reference to the accompanying drawings.

1 is a flowchart illustrating a method for providing a network failure recovery service according to the present disclosure.

A method of providing a network failure recovery service according to an embodiment of the present disclosure includes a step (110) of a central control and management system (MCS) receiving a failure recovery service level and a first parameter, the central control management system Step 130 of determining and setting the routing path of the working path, Step 150 of determining and setting the second parameters necessary for the central control management system to perform the failure recovery service, and Preliminary notification in case of a failure in the network service path. It may include a step (170) of restoring the network service according to the backup path setting method agreed upon with the user.

In the failure recovery service grade and first parameter receiving step 110, the failure recovery service grade is determined by the user (Customer) determining the required failure recovery time and then using the failure recovery service table 200 to determine the failure recovery service grade. You can.

Additionally, the first parameter is a general service parameter and may include used bandwidth, service level, connection point (end point), etc.

Additionally, the step 130 of determining the routing path of the working path can be determined by the central control management system with reference to the first parameter. Accordingly, the central control management system can instruct network nodes passing through the working path to set the working path. Accordingly, the network nodes that have received the working path setting instruction can perform the working path setting.

In the second parameter determination step 150, the second parameters are parameters necessary for performing a disaster recovery service, and may include a disaster recovery failure type and a backup path setting method.

In addition, the central control management system can retrieve the second parameter required for the disaster recovery service from the disaster recovery service table 200 by referring to the failure recovery service level provided by the user. The failure recovery service table 200 will be described in detail later with reference to FIG. 2.

In the step 170 of restoring the network service according to the backup path setting method agreed upon with the user in advance, a failure of the working path is detected by a network node, and the central control management system detects the occurrence of a failure from the network node. Upon reception, the central control management system may normalize the service by diverting data traffic from the broken working path to a backup path.

Figure 2 is a diagram showing a failure recovery service table of the present disclosure.

Figure 2 illustrates a failure recovery service table used by a communication service provider to enter into a failure recovery service agreement with a user and perform a failure recovery service. The communication service provider creates a failure recovery service table 200, agrees to a failure recovery service with the user, and performs the failure recovery service using the second parameter. The failure recovery service table 200 includes failure recovery time required for each failure recovery service level (210) (220), user price information (unit band price, 230), and the second parameter required to perform the failure recovery service (failure recovery failure type). (240), Backup path setting method (250)) information is provided. The failure recovery service level (210) is higher as the failure recovery time (220) is shorter, and the user has to pay more. Depending on the characteristics of the network used, the network operator may configure the failure recovery failure type 240 and backup path setting method 250 for each level differently from those in FIG. 2.

The failure recovery time (220) is the time required to restore normal service by replacing the broken working path with a backup path after a fault occurs.

The unit band price (230) is the price that the user must pay per unit band.

The failure recovery failure type 240 is information used to declare that the network service is in an abnormal state and initiate a failure recovery service, and is defined in the following four types.

Fault recovery fault types (240) include standard fault (S Fault), customized fault (C Fault), standard alarm (S Alarm), and custom alarm (Customized alarm, C Alarm). It can be included.

Here, the standard fault (S Fault) may mean a failure declared when an abnormal state of the network continues for more than a certain period of time according to the international standard (ITU-T).

Additionally, the Customized Fault (C Fault) may refer to a fault declared when an abnormal state of the network continues for a certain period of time or more as defined by the user. Custom faults may be declared earlier or later than standard faults.

In addition, the standard alarm (S Alarm) may mean a failure declared when the standard failure state of the network continues for more than 2.5 ± 0.5 seconds according to international standards (ITU-T, etc.).

In addition, the Customized Alarm (C Alarm) is a failure declared when the standard failure state of the network continues for more than a certain period of time by user definition. The Customized Alarm can be declared earlier or later than the standard alarm. there is.

For example, according to international standards, a standard failure is declared when an optical signal is not normally received in an optical link for a certain period of time, and a standard alarm is declared when the failure persists for more than 2.5 seconds. Therefore, the failure recovery service initiated when a standard failure occurs can normalize the network service more than 2.5 seconds faster than the failure recovery service initiated when a standard alarm occurs.

The backup path setting method 250 refers to the preparation state of the backup path before a network failure occurs, and can be defined in three ways as follows.

The backup path setting method 250 may include an activated backup path, a predefined backup path, and an undefined backup path. However, the definition is not limited to this and the related definition may be defined in more detail depending on the telecommunication service provider.

The activated backup path can always maintain the backup path in a state where packet delivery is possible in case of a failure that may occur in the working path. Therefore, since the activated backup path is always capable of delivering packets, when a failure occurs in the working path, service recovery may be possible only by switching the backup path. Accordingly, rapid failure recovery is possible, but network resource efficiency may be reduced because network resources are always required to stand by for a backup path.

Additionally, the predefined backup path may mean a state in which route calculation or network resources for the backup path are pre-allocated before a failure occurs in the working path. However, it may not be in an activated state where packets can be transmitted. Accordingly, because the backup path has been calculated or network resources have been allocated before the backup path failure occurs, faster failure recovery is possible compared to a backup path that is not predefined. However, recovery may be slower compared to the active backup path method, which always puts the backup path on standby.

Additionally, the non-predefined backup path may mean a state in which the backup path has not been calculated or connected before a failure occurs in the working path. However, since backup path calculation and path setting are required after a failure occurs in the working path, recovery from failure may be slower compared to the activated backup path and the predefined backup path.

Figure 2 shows an example of a failure recovery service table 200 that provides a failure recovery service level 210 according to the failure recovery time 220. The failure recovery service grades 210 in FIG. 2 are sequentially assigned according to the speed of the failure recovery time 220. In other words, the failure recovery failure type and backup path setting method with the fastest failure recovery time, such as unit bandwidth price (230), are displayed as the highest grade failure recovery service with the most expensive fee, and the failure recovery failure type with the fastest failure recovery time is displayed as the highest level of failure recovery service. The type of failure recovery and the method of setting up a backup path will be indicated by the lowest level of failure recovery service paying the lowest rate.

Accordingly, the failure recovery service level 210 is determined according to the failure recovery time 220. Each failure recovery service grade (210) guarantees a faster failure recovery time than the failure recovery time (R1~R5) (220) assigned to each service grade (1~5).

For example, if the time required for disaster recovery (=t) required by the user is between R2<t<R3, a level 3 disaster recovery service should be selected.

In Figure 2, the highest level (level 1) failure recovery service uses a standard or user-defined failure signal as the failure recovery failure type and has an activated backup path as the backup path setting method.

The second level uses standard or user-defined failures as the failure recovery failure type and uses a predefined backup path as the backup path setting method.

The third level uses standard or user-defined alarms as a failure recovery type and uses a predefined backup path as the backup path setting method.

The fourth level uses standard or user-defined failures as the failure recovery failure type, and uses a backup path that is not predefined as the backup path setting method.

The fifth level is a failure recovery type that uses standard or user-defined alarm signals and uses a backup path that is not predefined as a backup path setting method.

The sixth level (lowest level) is the Best Effort service, which provides a failure recovery service depending on network conditions without a defined failure recovery time.

However, because the failure recovery time may vary depending on the characteristics of the network operated by the communication service provider and the type of failure defined by the user, the failure recovery service level may be defined differently from FIG. 2.

Figure 3 is a diagram showing a simple network structure for the failure recovery service of the present disclosure.

Figure 3 shows the configuration of the failure recovery service network and a brief failure recovery procedure of the present disclosure.

A simple network structure for a failure recovery service according to the present disclosure may be composed of a service user (customer) 310, a central control management system 320, and a node 330.

According to an embodiment of the present disclosure, the user 310 may request (341) a network service from the central control management system (320).

Additionally, the central control management system 320, which has received a request for a network service from the user 310, can configure the network service in the node 330 (342).

Additionally, if a failure occurs in the working path, the node 330 may notify the central control management system 320 of the failure (343). The specific network structure will be described in detail later with reference to FIG. 4.

Additionally, the central control management system 320, which has been notified of the occurrence of a failure, may instruct the node 330 to change the broken working path to a backup path (344).

FIG. 4 is a diagram illustrating a network structure for a failure recovery service of the present disclosure.

The network for disaster recovery service may be composed of a service user (customer) 410, a central control management system 420, and network nodes 431, 432, 433, 434, and 435.

Specifically, the dotted arrow in FIG. 4 may indicate a failure recovery service performance step procedure. In addition, the solid arrow in FIG. 4 may indicate a failure recovery service configuration step procedure, and the thin lines connected between the user 410, the central control management system 420, and the network nodes 431-435 represent each device. It can mean the connection structure between them.

Among the network nodes, nodes corresponding to 431 and 435 may be End Nodes. The End Nodes (431, 435) are nodes corresponding to both ends and may mean the first transmitting node and the final receiving node.

More specifically, the failure recovery service may be comprised of a failure recovery service configuration stage and a failure recovery service performance stage after a failure occurs.

The failure recovery service configuration step is a step in which the user 410 requests the central control management system 420 for a network service consisting of a working path 481 and a backup path 484, as in step 440, and a central control step in step 450. The management system 420 may be configured to set up network services for network nodes. Here, the central control management system 420 may be connected to one or more network nodes 431, 432, 433, 434, and 435, respectively.

If a failure occurs in the working path 481 (491), the network node 433 can detect the occurrence of a failure in the working path and notify the central control management system 420. In addition, as in step 470, the central control management system 420 may be configured to normalize the service by diverting data traffic from the broken working path to the backup path.

Figure 5 is a diagram illustrating a procedure for providing a disaster recovery service according to the present disclosure.

More specifically, Figure 5 shows a specific procedure for providing failure recovery services.

The failure recovery service consists of a failure recovery service configuration stage (511, 521, 522, 523, 531), such as step 540, and a failure recovery service performance stage (524, 532, 533), such as step 550.

The failure recovery service configuration step 540 is performed by the following procedure. In step 511, the user 510 determines the time required for disaster recovery and then determines the disaster recovery service level by referring to the disaster recovery service table 200. In addition, the first parameter including at least one of the source, destination, or bandwidth to be used and the failure recovery service level may be transmitted to the central control management system 520. In step 521, the central control management system 520 may determine the routing path of the working path by referring to the first parameter provided by the customer and instruct the network nodes passing through the working path to set the working path. In step 522, the central control management system 520 may retrieve the second parameter required for the failure recovery service from the failure recovery service table 200 by referring to the failure recovery service level provided by the user 510. In step 523, the central control management system 520 may instruct the network nodes 530 to set a failure recovery service using the second parameters (failure recovery failure type, backup path setting method). More specifically, first, the central control management system 520 can instruct related nodes to set OAM to monitor the working path using failure recovery failure type information (failure or alarm). If the failover failure type is fault, nodes can be configured to initiate a failover service when a fault occurs. If it is an alarm, nodes can be configured to initiate a failover service when the alarm occurs. Second, the central control management system 520 can prepare a backup path according to the backup path setting method (activated backup path, predefined backup path, non-predefined backup path). If an activated backup path is required to be set, the central control management system 520 may request the nodes passing through the backup path to set the route. If a predefined backup path is required, a routing path for the backup path can be calculated. And you can optionally allocate a backup path band. If a backup path that is not predefined is required, the backup path may not be prepared in advance. In step 531, network nodes 530 that have been instructed to set the working path can perform the setting of the working path. Additionally, the network nodes 530 can set OAM to monitor failures in the working path using the failure recovery failure type information provided by the central control management system 520. Additionally, the backup path can be prepared according to the backup path setting method. Here, the step of setting the working path is not bound to the failure recovery service provision procedure and can be performed at any time within the failure recovery service configuration step 540. This will be described in detail below with reference to FIG. 6.

The failure recovery service performance step 550 can be performed by the following procedure. In step 532, the network nodes 530 can monitor whether a failure occurs in the working path. If a failure occurs, this can be notified to the central control management system 520. The central control management system 520, which has been notified of the occurrence of a failure by the network node 530 in step 524, sets the backup path according to the backup path setting method agreed upon with the user in advance and switches the data traffic of the failed working path to the backup path. This allows the service to be normalized. If the backup path setting method agreed upon with the user is set to an active backup path, the central control management system 520 may instruct the network nodes 530 to transfer data traffic from the working path to the backup path. . If it is set to a predefined backup path, the central control management system 520 activates the backup path calculated in advance or to which the bandwidth has been allocated and instructs the network nodes to transfer the data traffic of the working path to the backup path. You can. If it is set to a backup path that is not predefined, the central control management system 520 can calculate the backup path, set the path, and instruct the network nodes to transfer the data traffic of the working path to the backup path. In step 533, network nodes that have received instructions for failure recovery service from the central control management system 520 can restore data traffic on the failed working path by bypassing it to the backup path according to the instructions of the central control management system 520.

Figure 6 is a diagram illustrating a procedure for providing a failure recovery service according to an embodiment of the present disclosure.

In FIG. 6 , similar to FIG. 5 , the user 610 determines the time required for failure recovery and then determines the failure recovery service level by referring to the failure recovery service table 200 . In addition, the first parameters including the source, destination, and bandwidth to be used, as well as the failure recovery service level, can be transmitted to the central control management system (611). Accordingly, the central control management system 620 determines the routing path of the working path with reference to the first parameter provided by the customer and instructs the network nodes 630 passing through the working path to set the working path (621). You can. Nodes 630 that have been instructed to set the working path can immediately set the working path (631). The remaining process can be performed in the same manner as in FIG. 5 above.

FIG. 7 is a diagram illustrating an example of the configuration of a network failure recovery service providing device of the present disclosure. Referring to FIG. 7, a network failure recovery service providing apparatus includes a device 700. The device 700 may include a memory 720, a processor 730, a transceiver 740, and a peripheral device 710. Additionally, as an example, the device 700 may further include other components and is not limited to the above-described embodiment. At this time, as an example, the device 700 may be the network failure recovery service provider described above.

More specifically, the device 700 of FIG. 7 may be exemplary hardware/software that provides a network failure recovery service. At this time, as an example, the memory 720 may be a non-removable memory or a removable memory. Additionally, as an example, the peripheral device 710 may include a display, GPS, or other peripheral devices, and is not limited to the above-described embodiment.

Additionally, as an example, the above-described device 700 may include a communication circuit like the transceiver 740, and may communicate with an external device based on this.

Additionally, as an example, the processor 730 may include a general-purpose processor, a digital signal processor (DSP), a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), a Field Programmable Gate Array (FPGA) circuit, and any other It may be at least one of a tangible integrated circuit (IC) and one or more microprocessors associated with a state machine. In other words, it may be a hardware/software configuration that performs a control role to control the device 700 described above.

At this time, the processor 730 may execute computer-executable instructions stored in the memory 720 to perform various essential functions of the image depth information estimation performance improvement device. As an example, the processor 730 may control at least one of signal coding, data processing, power control, input/output processing, and communication operations. Additionally, the processor 730 can control the physical layer, MAC layer, and application layer. Additionally, as an example, the processor 730 may perform authentication and security procedures at the access layer and/or application layer, and is not limited to the above-described embodiment.

As an example, the processor 730 may communicate with other devices through the transceiver 740. As an example, the processor 730 may control a node to communicate with other nodes through a network through execution of computer-executable instructions. That is, communication performed in the present invention can be controlled. As an example, other nodes may be NDN servers, content routers, and other devices. As an example, the transceiver 740 may transmit an RF signal through an antenna and may transmit signals based on various communication networks.

Additionally, as an example, MIMO technology, beamforming, etc. may be applied as antenna technology, and is not limited to the above-described embodiment. Additionally, signals transmitted and received through the transmitting and receiving unit 740 may be modulated and demodulated and controlled by the processor 730, and are not limited to the above-described embodiment.

The various embodiments of the present disclosure do not list all possible combinations but are intended to explain representative aspects of the present disclosure, and matters described in the various embodiments may be applied independently or in combination of two or more.

Additionally, various embodiments of the present disclosure may be implemented by hardware, firmware, software, or a combination thereof. For hardware implementation, one or more ASICs (Application Specific Integrated Circuits), DSPs (Digital Signal Processors), DSPDs (Digital Signal Processing Devices), PLDs (Programmable Logic Devices), FPGAs (Field Programmable Gate Arrays), general purpose It can be implemented by a processor (general processor), controller, microcontroller, microprocessor, etc. For example, it is obvious that it can be implemented in the form of a program stored in a non-transitory computer-readable medium that can be used at the end or edge, or in the form of a program stored in a non-transitory computer-readable medium that can be used at the edge or in the cloud. do. Additionally, it can be implemented by combining various hardware and software.

The scope of the present disclosure is software or machine-executable instructions (e.g., operating system, application, firmware, program, etc.) that cause operations according to the methods of various embodiments to be executed on a device or computer, and such software or It includes non-transitory computer-readable medium in which instructions, etc. are stored and can be executed on a device or computer.

The present disclosure described above may be subject to various substitutions, modifications, and changes without departing from the technical spirit of the present disclosure to those skilled in the art to which the present disclosure pertains. Therefore, the scope of the present disclosure is limited to the above. It is not limited to one embodiment and the attached drawings.

Claims (20)

In a method of providing a network failure recovery service performed by a management and control system (MCS),
Receiving a failure recovery service level and a first parameter related to the failure recovery service level;
determining a working path based on the first parameter;
determining a second parameter required for a failure recovery service from a failure recovery service table based on the failure recovery service level;
Receiving whether a failure has occurred in a working path detected by a network node; and
Upon receiving whether a failure of the working path has occurred, restoring the network service according to the second parameter,
Method of providing network failure recovery service.
According to clause 1,
The step of receiving the failure recovery service level is characterized in that receiving a failure recovery service grade determined by considering the time required for failure recovery desired by the user.
Method of providing network failure recovery service.
According to clause 1,
The first parameter includes at least one of a used bandwidth, an end point, a source, or a destination.
Method of providing network failure recovery service.
According to clause 1,
The second parameter includes either a failure recovery failure type or a backup path setting method,
Method of providing network failure recovery service.
According to clause 4,
The failure recovery failure type is any of standard fault (Standard Fault, S Fault), customized fault (C Fault), standard alarm (Standard Alarm, S Alarm), or custom alarm (Customized Alarm, C Alarm). one person,
Method of providing network failure recovery service.
According to clause 4,
The backup path setting method includes one of an activated backup path, a predefined backup path, or an undefined backup path,
Method of providing network failure recovery service.
According to clause 1,
Including the step of the central control management system instructing network nodes passing through the working path to perform working path setting,
Method of providing network failure recovery service.
According to clause 1,
Further comprising the step of the central control management system instructing the network nodes to set a failure recovery service using a second parameter,
Method of providing network failure recovery service.
According to clause 8,
The second parameter includes at least one of a failure recovery failure type or a backup path setting method,
Method of providing network failure recovery service.
According to clause 8,
The step of instructing the network nodes to configure the failure recovery service includes instructing the relevant network nodes to configure OAM (Operation Administration Maintenance) to monitor the working path using the failure recovery failure type information.
Method of providing network failure recovery service.
According to clause 8,
In the step of instructing the network nodes to set up the disaster recovery service,
Including preparing a backup path according to the backup path setting method,
Method of providing network failure recovery service.
According to clause 1,
The central control management system includes the step of normalizing the service by switching data traffic from the broken working path to the backup path,
Method of providing network failure recovery service.
According to clause 1,
Including the step of the central control management system instructing the network node to restore the data traffic of the broken working path by bypassing it to the backup path,
Method of providing network failure recovery service.
In a method of providing network failure recovery service,
Network nodes performing working path settings instructed by the central control management system;
performing second parameter settings instructed by the central control management system;
Monitoring the occurrence of a failure in the working path;
If a failure occurs in the working path as a result of monitoring the failure occurrence, notifying the central control management system of the failure; and
Including the step of recovering data traffic from the broken working path by bypassing it to the backup path according to the instructions of the central control management system,
Method of providing network failure recovery service.
According to clause 14,
The second parameter includes at least one of a failure recovery failure type or a backup path setting method,
Method of providing network failure recovery service.
According to clause 15,
The step of performing the second parameter setting includes setting OAM to monitor a failure of the working path using the failure recovery failure type information,
Method of providing network failure recovery service.
According to clause 15,
The step of performing the second parameter setting includes preparing a backup path according to a backup path setting method,
Method of providing network failure recovery service.
In a network failure recovery service provision device performed by a central control management system,
a first parameter receiving unit that receives a failure recovery service level and a first parameter related to the failure recovery service grade;
a working path determination unit that determines a working path based on the first parameter;
a second parameter determination unit that determines a second parameter required for a failure recovery service from a failure recovery service table based on the failure recovery service level;
Includes a failure status receiver that receives whether a failure has occurred in the working path detected by the network node,
Characterized in that, upon receiving whether a failure of the working path has occurred, network service is restored according to the second parameter,
A device that provides network failure recovery services.
According to clause 18,
The second parameter includes at least one of a failure recovery failure type or a backup path setting method,
A device that provides network failure recovery services.
According to clause 18,
The failure recovery service level is determined by considering the time required for failure recovery desired by the user.
A device that provides network failure recovery services.

Images