Method and System for Informing SRLG Information between Multiple Layers of a Communication Network

Abstract

Embodiments of this specification provide a method for informing Shared Risk Link Group (SRLG) information between multiple layers of a communication network. The method includes a step in which an optical domain controller (100) determines SRLG information associated with an optical domain and an IP domain to be shared with an IP domain controller (200), and a step in which the optical domain controller (100) determines a layer identifier for establishing a multi-protocol enabled Border Gateway Protocol (BGP) session between the optical domain and the IP domain. The method also includes a step in which the optical domain controller (100) establishes a multi-protocol enabled BGP session between the optical domain controller (100) and the IP domain controller (200) based on the layer identifier, and a step in which the optical domain controller (100) informs the IP domain controller (200) of the SRLG information associated with the optical domain and the SRLG information associated with the IP domain via the established multi-protocol enabled BGP session.

Description

Technical Field

[0001] Cross - reference to related applications This application claims priority based on Indian Patent Application No. 202241056284 filed on September 30, 2022, and the disclosure thereof is incorporated herein by reference in its entirety.

[0002] The present invention relates to a communication network, and more specifically, to a method and system for informing shared risk link group (SRLG) information between multiple layers of a communication network.

Background Art

[0003] Generally, SRLG information is propagated from the optical layer of the transport domain, i.e., the L0 / L1 layer, to the Internet Protocol (IP) layer, i.e., the L3 layer, via a manual process. In the transport domain, the optical layer and the IP layer operate independently of each other. Each of the optical layer and the IP layer is managed by an administrator who cooperates with each other to share and configure the SRLG information. Further, the configured SRLG information is passed to an IP domain controller that determines a further calculation method based on the configured SRLG information. SRLG information includes data links that are routed through the same fiber path or cause multiple outage states during scenarios such as fiber cuts.

[0004] Therefore, it is essential to define SRLG information in both layers. However, when the communication carriers managing the optical layer and the IP layer are not the same, adjustment problems may occur because the SRLG information is not efficiently configured, which may ultimately lead to diversity problems affecting the user experience. Also, the manual sharing of SRLG information will affect human errors and the time lapse that reduces the efficiency of the communication network. Therefore, it is desirable to address the above-mentioned disadvantages or other drawbacks, or at least provide a useful alternative.

[0005] Object of the Invention The main object of the embodiments of this specification is to provide a method and a system for advertising shared risk link group (SRLG) information between multiple layers of a communication network. The proposed method includes the automatic detection and advertisement of SRLG information from the optical domain layer (L1 / L0) to the IP domain layer (L3) in the transport domain. Therefore, the proposed method automates the process, thereby making the process faster, more efficient, and resource-effective while reducing possible human errors. Summary of the Invention

[0006] Accordingly, embodiments of the present specification provide a method for informing shared risk link group (SRLG) information among multiple layers of a communication network. The method includes a step in which an optical domain controller determines SRLG information associated with an optical domain to be shared with an IP domain controller and SRLG information associated with the IP domain, and a step in which the optical domain controller determines a layer identifier for establishing a multi-protocol enabled Border Gateway Protocol (BGP) session between the optical domain and the IP domain. The layer identifier indicates that it is an advertising of SRLG information associated with the optical domain and SRLG information associated with the IP domain. The method also includes a step in which the optical domain controller establishes a multi-protocol enabled BGP session between the optical domain controller and the IP domain controller based on the layer identifier, and a step in which the optical domain controller informs the IP domain controller of the SRLG information associated with the optical domain and the SRLG information associated with the IP domain via the established multi-protocol enabled BGP session.

[0007] In one embodiment, the method further includes a step in which the IP domain controller receives the SRLG information associated with the optical domain and the SRLG information associated with the IP domain via the established multi-protocol enabled BGP session, and a step in which the IP domain controller locally creates an SRLG-specific database. The method also includes a step in which the IP domain controller stores the received SRLG information associated with the optical domain and the SRLG information associated with the IP domain in the SRLG-specific database, and a step in which the IP domain controller executes at least one of path calculation and path update using at least one of the SRLG information associated with the optical domain and the SRLG information associated with the IP domain stored in the SRLG-specific database.

[0008] In one embodiment, the step in which the optical domain controller establishes a multiprotocol-enabled BGP session between the optical domain controller and the IP domain controller based on a request to the IP domain controller includes: the optical domain controller transmitting a request including a layer identifier for establishing a multiprotocol-enabled BGP session between the optical domain controller and the IP domain controller to the IP domain controller; and the optical domain controller receiving a response accepting the establishment of the multiprotocol-enabled BGP session between the optical domain controller (100) and the IP domain controller. The method also includes: the optical domain controller exchanging functions associated with the multiprotocol-enabled BGP session with the IP domain controller; and the optical domain controller establishing a multiprotocol-enabled BGP session between the optical domain controller and the IP domain controller.

[0009] In one embodiment, the SRLG information associated with the optical domain includes at least one of the SRLG number associated with the optical domain and the information of the UNI interface.

[0010] In one embodiment, the SRLG information associated with the IP domain includes information associated with the IP domain router interface, the router identifier (ID) discovered using the neighbor exchange protocol, the link set, the virtual local area network identifier (VLAN ID), and the VLAN details.

[0011] In one embodiment, the layer identifier is at least one of the address family identifier (AFI) and the subsequent address family identifier (SAFI).

[0012] Accordingly, embodiments of the present specification provide a system for informing shared risk link group (SRLG) information between multiple layers of a communication network. The system includes an optical domain controller for an optical domain and an IP domain controller for an IP domain. The optical domain controller is configured to determine SRLG information associated with the optical domain to be shared with the IP domain controller and SRLG information associated with the IP domain, and to determine a layer identifier for establishing a multi-protocol enabled Border Gateway Protocol (BGP) session between the optical domain and the IP domain. The layer identifier indicates the notification of the SRLG information associated with the optical domain and the SRLG information associated with the IP domain. The optical domain controller is also configured to establish a multi-protocol enabled BGP session between the optical domain controller and the IP domain controller based on the layer identifier, and to notify the IP domain controller of the SRLG information associated with the optical domain and the SRLG information associated with the IP domain via the established multi-protocol enabled BGP session.

[0013] Accordingly, embodiments of the present specification provide an optical domain controller that advertises shared risk link group (SRLG) information between multiple layers of a communication network. The optical domain controller includes a memory, a processor, a communication unit, and an optical domain SRLG manager. The optical domain SRLG manager is configured to determine SRLG information associated with an optical domain to be shared with an IP domain controller and SRLG information associated with the IP domain, and to determine a layer identifier for establishing a multi-protocol enabled Border Gateway Protocol (BGP) session between the optical domain and the IP domain. The layer identifier indicates the advertisement of the SRLG information associated with the optical domain and the SRLG information associated with the IP domain. The optical domain SRLG manager is configured to establish a multi-protocol enabled BGP session between the optical domain controller and the IP domain controller based on the layer identifier, and to advertise the SRLG information associated with the optical domain and the SRLG information associated with the IP domain to the IP domain controller via the established multi-protocol enabled BGP session.

[0014] Accordingly, embodiments of the present specification provide an IP domain controller that advertises shared risk link group (SRLG) information between multiple layers of a communication network. The IP domain controller includes a memory, a processor, a communication unit, and an IP domain SRLG manager. The IP domain SRLG manager is configured to receive a multiprotocol enabled BGP session between an optical domain controller and the IP domain controller, and receive SRLG information associated with the optical domain and SRLG information associated with the IP domain from the optical domain controller via the established multiprotocol enabled BGP session. The IP domain SRLG manager is configured to locally create an SRLG specific database, store the received SRLG information associated with the optical domain and SRLG information associated with the IP domain in the SRLG specific database, and use at least one of the SRLG information associated with the optical domain and SRLG information associated with the IP domain stored in the SRLG specific database to perform at least one of path calculation and path update.

[0015] Accordingly, embodiments of this specification provide a computer program product (CPP) that advertises Shared Risk Link Group (SRLG) information between multiple layers of a communication network. The CPP includes computer-executable program code recorded on a computer-readable non-transitory storage medium, and when the computer-executable program code is executed, it causes an operation including the following steps. The following steps are: determining SRLG information associated with an optical domain to be shared with an IP domain controller and SRLG information associated with the IP domain; and determining a layer identifier for establishing a multi-protocol enabled Border Gateway Protocol (BGP) session between the optical domain and the IP domain. The layer identifier indicates that it is an advertisement of SRLG information associated with the optical domain and SRLG information associated with the IP domain. The CPP also includes, based on the layer identifier, establishing a multi-protocol enabled BGP session between the optical domain controller and the IP domain controller, and advertising, via the established multi-protocol enabled BGP session, the SRLG information associated with the optical domain and the SRLG information associated with the IP domain to the IP domain controller.

[0016] These and other aspects of the embodiments of this specification will be better recognized and understood when considered in conjunction with the following description and the accompanying drawings. However, it should be understood that the following description, while showing preferred embodiments and numerous specific details thereof, is given by way of illustration and not limitation. Within the scope of the embodiments of this specification, many changes and modifications can be made without departing from that scope, and the embodiments of this specification include all such modifications.

[0017] Embodiments of the present invention are shown in the accompanying drawings, and throughout the drawings, like reference numerals, symbols, and characters indicate corresponding parts of the various figures. Embodiments of this specification will be better understood from the following description with reference to the drawings.

Brief Description of the Drawings

[0018]

Figure 1

[0019]

Figure 2

[0020]

Figure 3A

[0021]

Figure 3B

[0022]

Figure 4

[0023]

Figure 5

[0024]

Figure 6

[0025]

Figure 7

[0026]

Figure 8

[0027] The embodiments of this specification, along with their various features and advantageous details, are shown in the accompanying drawings and will be more fully described with reference to the non-limiting embodiments detailed in the following description. To avoid unnecessarily obscuring the embodiments of this specification, descriptions of well-known components and processing techniques are omitted. Also, the various embodiments described in this specification are not necessarily mutually exclusive since some embodiments can be combined with one or more other embodiments to form new embodiments. The term "or" as used in this specification means "non-exclusive or" unless otherwise specified. The examples used in this specification are only intended to facilitate the understanding of the methods by which the embodiments of this specification can be implemented and to further enable those skilled in the art to implement the embodiments of this specification. Therefore, the examples should not be construed as limiting the scope of the embodiments of this specification.

[0028] As is traditional in the art, embodiments may be described and illustrated from the perspective of blocks that perform one or more of the described functions. These blocks, which may be referred to herein as managers, units, modules, hardware components, etc., are physically implemented by analog and / or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits, etc., and may optionally be driven by firmware. The circuits may be embodied, for example, within one or more semiconductor chips or on a substrate support such as a printed circuit board. The circuits that make up a block may be implemented by dedicated hardware, or by a processor (e.g., one or more programmed microprocessors and associated circuits), or by a combination of dedicated hardware for performing some of the functions of the block and a processor for performing other functions of the block. Each block of an embodiment may be physically separated into two or more interacting individual blocks without departing from the scope of the present disclosure. Similarly, the blocks of an embodiment may be physically combined into more complex blocks without departing from the scope of the present disclosure.

[0029] The accompanying drawings are used to assist in easily understanding various technical features, and it should be understood that the embodiments presented herein are not limited by the accompanying drawings. Accordingly, the disclosure of the present invention should be construed to cover any modifications, equivalents, and alternatives in addition to those specifically recited in the accompanying drawings. In this specification, terms such as first, second, etc. may be used to describe various elements, but these elements should not be limited by these terms. These terms are generally used only to distinguish one element from another.

[0030] Accordingly, embodiments of the present specification provide a method for informing shared risk link group (SRLG) information between multiple layers of a communication network. The method includes a step in which an optical domain controller determines SRLG information associated with an optical domain to be shared with an IP domain controller and SRLG information associated with the IP domain, and a step in which the optical domain controller determines a layer identifier for establishing a multi-protocol enabled Border Gateway Protocol (BGP) session between the optical domain and the IP domain. The layer identifier indicates that it is an announcement of SRLG information associated with the optical domain and SRLG information associated with the IP domain. The method also includes a step in which the optical domain controller establishes a multi-protocol enabled BGP session between the optical domain controller and the IP domain controller based on the layer identifier, and a step in which the optical domain controller informs the IP domain controller of the SRLG information associated with the optical domain and the SRLG information associated with the IP domain via the established multi-protocol enabled BGP session.

[0031] Accordingly, embodiments of the present specification provide an IP domain controller that advertises shared risk link group (SRLG) information among multiple layers of a communication network. The IP domain controller includes a memory, a processor, a communication unit, and an SRLG manager. The SRLG manager is configured to receive a multiprotocol enabled BGP session between an optical domain controller and the IP domain controller, and to receive SRLG information associated with the optical domain and SRLG information associated with the IP domain from the optical domain controller via the established multiprotocol enabled BGP session. The SRLG manager is configured to locally create an SRLG specific database, store the received SRLG information associated with the optical domain and the SRLG information associated with the IP domain in the SRLG specific database, and use at least one of the SRLG information associated with the optical domain and the SRLG information associated with the IP domain stored in the SRLG specific database to perform at least one of path calculation and path update.

[0032] Accordingly, embodiments of this specification provide a computer program product (CPP) that advertises shared risk link group (SRLG) information between multiple layers of a communication network. The CPP includes computer-executable program code recorded on a computer-readable non-transitory storage medium, and when the computer-executable program code is executed, it causes an operation including the following steps. The following steps are: determining SRLG information associated with an optical domain to be shared with an IP domain controller and SRLG information associated with the IP domain; and determining a layer identifier for establishing a multi-protocol enabled Border Gateway Protocol (BGP) session between the optical domain and the IP domain. The layer identifier indicates that it is an advertisement of SRLG information associated with the optical domain and SRLG information associated with the IP domain. The CPP also includes, based on the layer identifier, establishing a multi-protocol enabled BGP session between the optical domain controller and the IP domain controller; and advertising, via the established multi-protocol enabled BGP session, the SRLG information associated with the optical domain and the SRLG information associated with the IP domain to the IP domain controller.

[0033] In conventional methods and systems, SRLG information from the optical domain (L0 / L1) is manually supplied to the IP domain (L3). This requires a lot of human resources and may lead to synchronization errors. Different from conventional methods and systems, the method proposed in this disclosure includes automatic synchronization of SRLG information between cross-domains.

[0034] In conventional methods and systems, manual configuration of SRLG information in the IP domain may result in human errors and time lags that reduce the efficiency of the communication network.

[0035] Unlike conventional methods and systems, the method proposed in this disclosure includes the step of using specific AFI values and SAFI values indicating SRLG information in the MP BGP protocol that automates the process of informing SRLG information between layers.

[0036] Referring now to the drawings, and more particularly to FIGS. 1 - 8, like reference numerals throughout the figures indicate corresponding features consistently, and preferred embodiments are shown.

[0037] FIG. 1 shows an overall view of the optical layer and Internet Protocol (IP) layer of a transport domain according to the related art.

[0038] Referring to FIG. 1, in an existing network architecture, the IP layer, i.e., layer 3 (a group of router links), is established using services from the optical layer, i.e., layer 1. The network - to - network interface (NNI) links in layer 3 are services (UNI links) in layer 1. In the era of software - defined networking (SDN), an optical domain controller and an IP domain controller are used to define paths in the optical layer and the IP layer, respectively.

[0039] When two links share a common fiber path, the two links are part of an SRLG. SRLG information is important in a transport domain that provides various services such as, but not limited to, scenarios of dis - joint path management during fiber cuts. SRLG information is generally propagated from the optical layer, i.e., the L0 / L1 layer, to the IP layer, i.e., the L3 layer, through a manual process in which the optical layer and the IP layer operate independently of each other. Each of the optical layer and the IP layer is managed by an administrator who coordinates with each other to share and configure the SRLG information. Further, the configured SRLG information is passed to an IP domain controller that determines further calculation methods based on the configured SRLG information. However, when the network operators managing the optical layer and the IP layer are not the same, coordination issues may occur due to inefficient configuration of SRLG information, which may ultimately lead to diversity issues that affect the user experience. Also, the manual sharing of SRLG information will affect up to the scope of human errors, time lags that reduce the efficiency of communication networks, and synchronization issues.

[0040] Figure 2 shows the manual exchange of SRLG information between the optical layer and the IP layer of a transport domain according to the related art.

[0041] Referring to FIG. 2, an existing mechanism for manually sharing SRLG information will be described. In step 1, the SRLG information is composed of an L0 / L1 network in the optical layer. In step 2, the SRLG information is manually adjusted by the optical domain administrator and the IP domain administrator respectively between the optical layer and the IP layer. Further, in step 3, the IP domain administrator sets the SRLG information received from the optical domain administrator as the SRLG information composed of an L3 / IP network in the IP layer of the transport domain. In step 4, the SRLG is then notified to the IP / SDN controller for path calculation.

[0042] However, the existing method of manually setting SRLG information in the IP domain may lead to human errors, reduce the efficiency of the communication network between the optical domain and the IP domain, and cause time-lapse or synchronization problems.

[0043] FIG. 3A is a block diagram of an optical domain controller (100) for automatically notifying SRLG information between multiple layers of a communication network according to an embodiment disclosed herein. In one embodiment, the optical domain controller (100) includes a memory (120), a processor (140), a communication unit (160), and an optical domain SRLG manager (180).

[0044] The memory (120) is configured to store SRLG information associated with the optical domain and SRLG information associated with the IP domain. The memory (120) is also configured to store layer identifiers determined by the optical domain controller (100). Further, the memory (120) stores instructions executed by the processor (140). The memory (120) can include a non-volatile memory element. Examples of such non-volatile memory elements may include magnetic hard disks, optical disks, floppy disks, flash memories, or forms of electrically programmable memory (EPROM) or electrically erasable programmable (EEPROM) memory. Further, in some examples, the memory (120) can be considered a non-transitory storage medium. The term "non-transitory" can indicate that the storage medium is not embodied in a carrier wave or a propagated signal. However, the term "non-transitory" should not be construed to mean that the memory (120) is non-movable. In some examples, the memory (120) can be configured to store a larger amount of information. In a particular example, the non-transitory storage medium can store data that can change over time (e.g., in a random access memory (RAM) or a cache).

[0045] The processor (140) communicates with the memory (120), the communication unit (160), and the optical domain SRLG manager (180). The processor (140) is configured to execute instructions stored in the memory (120) and perform various processes. The processor can include one or more processors, optionally a general-purpose processor such as a central processing unit (CPU), an application processor (AP), a graphics-only processing unit such as a graphics processing unit (GPU), a visual processing unit (VPU), and / or an artificial intelligence (AI)-only processor such as a neural processing unit (NPU).

[0046] The communication unit (160) includes electronic circuits specific to the standard that enables wired or wireless communication. The communication unit (160) is configured to communicate internally between the internal hardware components of the optical domain controller (100) and with external devices via one or more networks.

[0047] In one embodiment, the optical domain SRLG manager (180) is implemented by a processing circuit such as a logic gate, integrated circuit, microprocessor, microcontroller, memory circuit, passive electronic component, active electronic component, optical component, hardwired circuit, etc., and can optionally be driven by firmware. The circuit may be embodied, for example, by one or more semiconductors. The optical domain SRLG manager (180) includes an SRLG information manager (182), a layer identifier manager (184), a BGP session manager (186), and an SRLG information advertiser (188).

[0048] In one embodiment, the SRLG information manager (182) is configured to determine SRLG information associated with the optical domain to be shared with the IP domain controller (200) and SRLG information associated with the IP domain. The SRLG information associated with the optical domain includes the SRLG number associated with the optical domain and information on the UNI interface. The SRLG information associated with the IP domain includes information associated with the IP domain router interface, the router identifier (ID) discovered using the neighbor exchange protocol, link aggregation, virtual local area network identifier (VLAN ID), and VLAN details.

[0049] In one embodiment, the layer identifier manager (184) is configured to determine a layer identifier for establishing a multi-protocol enabled Border Gateway Protocol (BGP) session between an optical domain and an IP domain. The layer identifier indicates that it is an advertisement of SRLG information associated with the optical domain and SRLG information associated with the IP domain. The layer identifier is, for example, but not limited to, an address family identifier (AFI) and a subsequent address family identifier (SAFI).

[0050] In one embodiment, the BGP session manager (186) is configured to send a request to establish a multi-protocol enabled BGP session between the optical domain controller (100) and the IP domain controller (200) to the IP domain controller (200), and receive a response from the IP domain controller (200) accepting the establishment of the multi-protocol enabled BGP session between the optical domain controller (100) and the IP domain controller (200). This request includes a layer identifier. The BGP session manager (186) is configured to exchange functions associated with the multi-protocol enabled BGP session with the IP domain controller (200) and establish a multi-protocol enabled BGP session between the optical domain controller (100) and the IP domain controller (200).

[0051] In one embodiment, the SRLG information advertiser (188) is configured to advertise the SRLG information associated with the optical domain and the SRLG information associated with the IP domain to the IP domain controller (200) via the established multi-protocol enabled BGP session.

[0052] At least one of the multiple modules / components of the optical domain SRLG manager (180) may be implemented by an AI model. The functions associated with the AI model can be executed by the memory (120) and the processor (140). One or more processors control the processing of input data according to predetermined operation rules or an AI model stored in non-volatile memory and volatile memory. The predetermined operation rules or artificial intelligence model are provided by training or learning.

[0053] Here, being provided by learning means that a predetermined operation rule or an AI model with desired characteristics is created by applying a learning process to a plurality of learning data. The learning may be executed in the device itself where the AI according to the embodiment is executed, and / or may be implemented by a separate server / system.

[0054] The AI model may be composed of multiple neural network layers. Each layer has a plurality of weight values and executes layer operations through the calculation of the previous layer and the calculation of a plurality of weights. Examples of neural networks include, but are not limited to, convolutional neural networks (CNNs), deep neural networks (DNNs), recurrent neural networks (RNNs), restricted Boltzmann machines (RBMs), deep belief networks (DBNs), bidirectional recurrent deep neural networks (BRDNNs), generative adversarial networks (GANs), and deep Q networks.

[0055] The learning process is a method of training a predetermined target device (e.g., a robot) using a plurality of learning data, causing the target device to make a determination or prediction, permit, or control. Examples of the learning process include, but are not limited to, supervised learning, unsupervised learning, semi-supervised learning, or reinforcement learning.

[0056] FIG. 3A shows various hardware components of the optical domain controller (100), but it should be understood that other embodiments are not limited thereto. In other embodiments, the optical domain controller (100) can include fewer or more components. Further, the labels or names of the components are used for illustrative purposes only and do not limit the scope of the present invention. One or more components can be combined to perform the same or substantially similar functions as managing the application log based on various events.

[0057] FIG. 3B is a block diagram of an IP domain controller (200) that automatically receives SRLGs in communication with an optical domain controller according to the embodiments disclosed herein. In one embodiment, the IP domain controller (200) includes a memory (220), a processor (240), a communication unit (260), and an IP domain SRLG manager (280).

[0058] The memory (220) is configured to store SRLG information associated with the optical domain received from the optical domain controller (100) and SRLG information associated with the IP domain. The memory (220) is also configured to store layer identifiers. Further, the memory (220) stores instructions executed by the processor (240). The memory (220) can include a non-volatile memory element. Examples of such non-volatile memory elements may include magnetic hard disks, optical disks, floppy disks, flash memories, or forms of electrically programmable memory (EPROM) or electrically erasable programmable (EEPROM) memory. Further, in some examples, the memory (220) can be considered a non-transitory storage medium. The term "non-transitory" can indicate that the storage medium is not embodied in a carrier wave or propagated signal. However, the term "non-transitory" should not be construed to mean that the memory (220) is non-portable. In some examples, the memory (220) can be configured to store a larger amount of information. In a particular example, the non-transitory storage medium can store data that can change over time (e.g., in a random access memory (RAM) or cache).

[0059] The processor (240) communicates with the memory (220), the communication unit (260), and the IP domain SRLG manager (280). The processor (140) is configured to execute instructions stored in the memory (220) and perform various processes. The processor may include one or more processors, optionally a general-purpose processor such as a central processing unit (CPU), an application processor (AP), a graphics-only processing unit such as a graphics processing unit (GPU), a vision processing unit (VPU), and / or an artificial intelligence (AI)-only processor such as a neural processing unit (NPU).

[0060] The communication unit (260) includes electronic circuits specific to the standard that enable wired or wireless communication. The communication unit (260) is configured to communicate internally between the internal hardware components of the IP domain controller (200) and with external devices via one or more networks.

[0061] In one embodiment, the IP domain SRLG manager (280) is implemented by a processing circuit such as a logic gate, integrated circuit, microprocessor, microcontroller, memory circuit, passive electronic component, active electronic component, optical component, hardwired circuit, etc., and can optionally be driven by firmware. The circuit may be embodied, for example, by one or more semiconductors. The IP domain SRLG manager (280) includes an SRLG information manager (282) and a BGP session manager (284).

[0062] In one embodiment, the SRLG information manager (282) is configured to receive a request from the IP domain controller (200) to establish a multiprotocol enabled BGP session between the optical domain controller (100) and the IP domain controller (200).

[0063] In one embodiment, a BGP session manager (284) is configured to receive, from an optical domain controller (100), a request including a layer identifier requesting establishment of a multi-protocol enabled BGP session between the optical domain controller (100) and an IP domain controller (200), and to send a response accepting establishment of the multi-protocol enabled BGP session between the optical domain controller (100) and the IP domain controller (200). Further, the BGP session manager (284) is configured to exchange functions associated with the multi-protocol enabled BGP session with the optical domain controller (100), and to accept the multi-protocol enabled BGP session between the optical domain controller (100) and the IP domain controller (200). The BGP session manager (284) is configured to receive, via the established multi-protocol enabled BGP session, SRLG information associated with the optical domain and SRLG information associated with the IP domain from the optical domain controller (100).

[0064] The SRLG information manager (282) is also configured to locally create an SRLG-specific database, and to store the received SRLG information associated with the optical domain and the SRLG information associated with the IP domain in the SRLG-specific database. Further, the SRLG information manager (282) is configured to perform at least one of path computation and path update using the SRLG information associated with the optical domain and the SRLG information associated with the IP domain stored in the SRLG-specific database.

[0065] At least one of the plurality of modules / components of the IP domain SRLG manager (280) may be implemented by an AI model. The functions associated with the AI model can be executed by the memory (220) and the processor (240). One or more processors control the processing of input data according to predetermined operation rules or an AI model stored in the non-volatile memory and the volatile memory. The predetermined operation rules or the artificial intelligence model are provided by training or learning.

[0066] Here, being provided by learning means that a predetermined operation rule or an AI model with desired characteristics is created by applying a learning process to a plurality of learning data. The learning may be executed in the device itself where the AI according to the embodiment is executed, and / or may be implemented by a separate server / system.

[0067] The AI model may be composed of a plurality of neural network layers. Each layer has a plurality of weight values and executes the operations of the layer and the operations of the plurality of weights by the calculation of the previous layer. Examples of neural networks include, but are not limited to, convolutional neural networks (CNNs), deep neural networks (DNNs), recurrent neural networks (RNNs), restricted Boltzmann machines (RBMs), deep belief networks (DBNs), bidirectional recurrent deep neural networks (BRDNNs), generative adversarial networks (GANs), and deep Q networks.

[0068] The learning process is a method of training a predetermined target device (e.g., a robot) using a plurality of learning data, causing the target device to make a determination or prediction, granting permission, or controlling it. Examples of the learning process include, but are not limited to, supervised learning, unsupervised learning, semi-supervised learning, or reinforcement learning.

[0069] FIG. 3B shows various hardware components of the IP domain controller (200), but it should be understood that other embodiments are not limited thereto. In other embodiments, the IP domain controller (200) can include fewer or more components. Further, the labels or names of the components are used for illustrative purposes only and do not limit the scope of the present invention. One or more components can be combined to perform the same or substantially similar functions as managing the application log based on various events.

[0070] FIG. 4 is a flowchart (400) showing a method for automatically informing SRLG information between multiple layers of a communication network according to the embodiments disclosed herein.

[0071] Referring to FIG. 4, in step 402, the method includes the step of the optical domain controller (100) determining the SRLG information associated with the optical domain to be shared with the IP domain controller (200) and the SRLG information associated with the IP domain. For example, in the optical domain controller (100) shown in FIG. 3A, the optical domain SRLG manager (180) is configured to determine the SRLG information associated with the optical domain to be shared with the IP domain controller (200) and the SRLG information associated with the IP domain.

[0072] In step 404, the method includes the step of the optical domain controller (100) determining a layer identifier for establishing a multiprotocol enabled BGP session between the optical domain and the IP domain. For example, in the optical domain controller (100) shown in FIG. 3A, the optical domain SRLG manager (180) is configured to determine a layer identifier for establishing a multiprotocol enabled BGP session between the optical domain and the IP domain.

[0073] In step 406, the method includes a step in which the optical domain controller (100) establishes a multiprotocol-enabled BGP session between the optical domain controller (100) and the IP domain controller (200) based on a layer identifier. For example, in the optical domain controller (100) shown in FIG. 3A, the optical domain SRLG manager (180) is configured to establish a multiprotocol-enabled BGP session between the optical domain controller (100) and the IP domain controller (200) based on a layer identifier.

[0074] In step 408, the method includes a step in which the optical domain controller (100) notifies the IP domain controller (200) of SRLG information associated with the optical domain and SRLG information associated with the IP domain via the established multiprotocol-enabled BGP session. For example, in the optical domain controller (100) shown in FIG. 3A, the optical domain SRLG manager (180) is configured to notify the IP domain controller (200) of SRLG information associated with the optical domain and SRLG information associated with the IP domain via the established multiprotocol-enabled BGP session.

[0075] The various actions, operations, blocks, steps, etc. of the flowchart (400) may be executed in the presented order, in a different order, or simultaneously. Further, in some embodiments, some of the actions, operations, blocks, steps, etc. may be omitted, added, modified, skipped, etc. without departing from the scope of the present invention.

[0076] FIG. 5 shows a BGP extension for transporting SRLG information between an optical domain controller (100) and an IP domain controller (200) according to an embodiment disclosed herein.

[0077] Referring to FIG. 5, the dedicated controllers within each domain of the transport domain include an optical domain controller (100) and an IP domain controller (200). In the method proposed in the present disclosure, the existing Multiprotocol Label Switching Border Gateway Protocol (BGP) session is modified and used for automatic detection of Shared Risk Link Group (SRLG) information between the optical domain controller (100) and the IP domain controller (200) and for communication, that is, for transporting SRLG information from the (L0 / L1) layer to the (L3) layer.

[0078] The optical domain controller (100) holds the SRLG information associated with the optical domain and the SRLG information associated with the IP domain. Further, the optical domain controller (100) uses the Link Layer Discovery Protocol (LLDP) protocol (Ethernet type - 0x88cc) to obtain details such as the connection between the transponder and the layer 3 router, whereby the optical domain controller (100) transfers the SRLG information associated with the IP domain.

[0079] The SRLG information associated with the optical domain includes, but is not limited to, the SRLG number associated with the optical domain and the information of the UNI interface. The information received from the LLDP includes, but is not limited to, the information associated with the IP domain router interface, the router identifier (ID) (management address) discovered using the neighbor exchange protocol, the link aggregation, the Virtual Local Area Network identifier (VLAN ID), and the VLAN details providing related information about the connected IP network. The BGP protocol can use the related information to announce the SRLG information of both layers.

[0080] FIG. 6 shows the BGP negotiation function between the optical domain controller and the IP domain controller according to the embodiment disclosed in the present specification.

[0081] FIG. 7 shows the BGP NLRI encoding for route advertisements between an optical domain controller and an IP domain controller according to the embodiments disclosed herein.

[0082] Referring to FIG. 6, when a BGP session is formed, first, the optical domain controller (100) and the IP domain controller (200) exchange functions. In the method proposed in the present disclosure, the multi-protocol BGP protocol is modified to include a layer identifier indicating a SRLG specific purpose. The layer identifier is, for example, but not limited to, the AFI and SAFI in the existing multi-protocol BGP.

[0083] When the IP domain controller (200) receives an MP BGP protocol request, the IP domain controller (200) can determine that the information to be shared is SRLG information. Therefore, since the IP domain controller (200) directly receives SRLG information from the optical domain controller (100), the IP domain controller (200) does not need to obtain SRLG information from the L3 layer. The IP domain controller (200) can automatically consider the SRLG information shared by the optical domain controller (100) for route calculation.

[0084] In step 1 of MP BGP session establishment, an initial Session Negotiation is performed. This includes the following exchanges in the BGP protocol. 1. SRLG information of L1 including SRLG numbers and UNI interfaces. 2. Details of the L3 router interface and the router ID discovered using the Link Layer Discovery Protocol (LLDP).

[0085] During the negotiation of the initial BGP session, the optical domain controller (100) and the IP domain controller (200) exchange multiprotocol capabilities as part of the OPEN message, indicating that the optical domain controller (100) and the IP domain controller (200) want to exchange SRLG information. The extensions are shown in FIG. 6.

[0086] In step 2, when the optical domain controller (100) and the IP domain controller (200) agree on the multiprotocol capabilities, the optical domain controller (100) sends a BGP update regarding the SRLG information. The IP domain controller (200) that receives the SRLG information from the optical domain controller (100) creates a local SRLG-specific database. As a result, the IP domain controller (200) becomes independent of the SRLG information arriving from the IP layer. In all further path calculations / path updates, the SRLG-specific information available for calculating the required disjoint paths in the transport domain can be used. Any new addition of SRLGs in the network becomes seamlessly available to the IP domain controller (200). Thus, the optical domain controller (100) avoids repeating the setting and notification of the SRLG information from the IP layer, and thus simplifies its deployment.

[0087] FIG. 8 shows the automatic exchange of SRLG information between the optical domain controller (100) and the IP domain controller (200) via a BGP session according to the embodiments disclosed herein. Referring to FIG. 8, in step 1, the SRLG is configured in the L0 / L1 network. In step 2, the SRLG information is available at the optical domain controller (100) or any element that enables BGP signaling and provides seamless BGP NLRI advertisement. In step 3, an MP-BGP session is established between the optical domain controller (100) and the IP domain controller (200). In step 4, the SRLG information is advertised via the established MP-BGP session. Therefore, in the method proposed in the present disclosure, manual intervention in the SRLG advertisement procedure is eliminated. Thereby, forgery prevention, error prevention, and seamless synchronization in the SRLG advertisement procedure can also be performed. The following terms are used throughout this specification. SRLG Shared Risk Link Group L0 / L1 Layers 0 and 1 indicate optical layers. L3 IP layer L1 controller Path computation engine within the optical layer L3 controller Path computation engine within the IP layer PCEP Path computation engine BGP-LS BGP link state protocol that exports the transport network topology Disjoint paths A method of providing different paths, different routers, and resources for two sets of services to which a customer subscribes LLDP Link layer discovery protocol AFI Address family identifier SAFI Subsequent address family identifier RTR Router NLRI Network layer reachability information

[0088] The foregoing description of specific embodiments fully discloses the general nature of the embodiments herein, so that others, by applying current knowledge, can readily modify and / or adapt such specific embodiments for various applications without departing from the upper concept. Therefore, such adaptations and modifications should be understood to be within the meaning and scope of the equivalents of the disclosed embodiments and are so intended. It should be understood that the expressions or terms used herein are for the purpose of description and not for limitation. Therefore, although the embodiments herein have been described with respect to the preferred embodiments, those skilled in the art will recognize that the embodiments herein can be practiced with modifications within the scope of the embodiments described herein.

Claims

1. A method for informing Shared Risk Link Group (SRLG) information among multiple layers of a communication network, the method comprising: a step in which an optical domain controller (100) determines SRLG information associated with an optical domain to be shared with an IP domain controller (200) and SRLG information associated with the IP domain; a step in which the optical domain controller (100) determines a layer identifier for establishing a Multiprotocol Label Switching Border Gateway Protocol (BGP) session between the optical domain and the IP domain, the layer identifier indicating the informing of the SRLG information associated with the optical domain and the SRLG information associated with the IP domain; The method further comprises: a step in which the optical domain controller (100) establishes the Multiprotocol Label Switching BGP session between the optical domain controller (100) and the IP domain controller (200) based on the layer identifier; a step in which the optical domain controller (100) informs the IP domain controller (200) of the SRLG information associated with the optical domain and the SRLG information associated with the IP domain via the established Multiprotocol Label Switching BGP session.

2. a step in which the IP domain controller (200) receives the SRLG information associated with the optical domain and the SRLG information associated with the IP domain via the established Multiprotocol Label Switching BGP session; a step in which the IP domain controller (200) locally creates an SRLG-specific database; a step in which the IP domain controller (200) stores the received SRLG information associated with the optical domain and the SRLG information associated with the IP domain in the SRLG-specific database. The step in which the IP domain controller (200) executes at least one of path calculation and path update by using at least one of the SRLG information associated with the optical domain stored in the SRLG specific database and the SRLG information associated with the IP domain; The method according to claim 1, further comprising:

3. The step in which the optical domain controller (100) establishes the multi-protocol enabled BGP session between the optical domain controller (100) and the IP domain controller (200) based on the request to the IP domain controller (200) is: The step in which the optical domain controller (100) transmits a request including the layer identifier for establishing the multi-protocol enabled BGP session between the optical domain controller (100) and the IP domain controller (200) to the IP domain controller (200); The step in which the optical domain controller (100) receives a response accepting the establishment of the multi-protocol enabled BGP session between the optical domain controller (100) and the IP domain controller (200); The step in which the optical domain controller (100) exchanges functions associated with the multi-protocol enabled BGP session with the IP domain controller (200); The method according to claim 1, comprising: the step in which the optical domain controller (100) establishes the multi-protocol enabled BGP session between the optical domain controller (100) and the IP domain controller (200).

4. The method according to claim 1, wherein the SRLG information associated with the optical domain includes at least one of an SRLG number associated with the optical domain and information of a UNI interface.

5. The method according to claim 1, wherein the SRLG information associated with the IP domain includes information associated with an IP domain router interface, a router identifier (ID) discovered by using a neighbor exchange protocol, a link set, a virtual local area network identifier (VLAN ID), and VLAN details.

6. The method according to claim 1, wherein the layer identifier is at least one of an address family identifier (AFI) and a subsequent address family identifier (SAFI).

7. A system for notifying shared risk link group (SRLG) information between multiple layers of a communication network, the system comprising: an optical domain controller (100) for an optical domain and an IP domain controller (200) for an IP domain; The optical domain controller (100) is: configured to determine SRLG information associated with an optical domain to be shared with the IP domain controller (200) and SRLG information associated with the IP domain; configured to determine a layer identifier for establishing a multi-protocol enabled Border Gateway Protocol (BGP) session between the optical domain and the IP domain, the layer identifier indicating the notification of the SRLG information associated with the optical domain and the SRLG information associated with the IP domain; The optical domain controller (100) further: is configured to establish the multi-protocol enabled BGP session between the optical domain controller (100) and the IP domain controller (200) based on the layer identifier; A system configured to notify the IP domain controller (200) of the SRLG information associated with the optical domain and the SRLG information associated with the IP domain via the established multi-protocol enabled BGP session.

8. Receiving SRLG information associated with the optical domain and SRLG information associated with the IP domain via the established multi-protocol enabled BGP session; configured to locally create an SRLG specific database; configured to store the received SRLG information associated with the optical domain and the SRLG information associated with the IP domain in the SRLG specific database. The system according to claim 7, further comprising the optical domain controller (100) configured to perform at least one of path calculation and path update using at least one of the SRLG information associated with the optical domain stored in the SRLG native database and the SRLG information associated with the IP domain.

9. The optical domain controller (100) is configured to establish the multi-protocol enabled BGP session between the optical domain controller (100) and the IP domain controller (200) based on the request to the IP domain controller (200), send a request including the layer identifier for establishing the multi-protocol enabled BGP session between the optical domain controller (100) and the IP domain controller (200) to the IP domain controller (200), receive a response accepting the establishment of the multi-protocol enabled BGP session between the optical domain controller (100) and the IP domain controller (200), exchange functions associated with the multi-protocol enabled BGP session with the IP domain controller (200), The system according to claim 7, comprising establishing the multi-protocol enabled BGP session between the optical domain controller (100) and the IP domain controller (200).

10. The SRLG information associated with the optical domain includes at least one of an SRLG number associated with the optical domain and information on the UNI interface. The system according to claim 7.

11. The SRLG information associated with the IP domain includes information associated with the IP domain router interface, a router identifier (ID) discovered using the neighbor exchange protocol, a link set, a virtual local area network identifier (VLAN ID), and VLAN details. The system according to claim 7.

12. The layer identifier is at least one of an address family identifier (AFI) and a subsequent address family identifier (SAFI). The system according to claim 7.

13. An optical domain controller (100) for informing shared risk link group (SRLG) information between multiple layers of a communication network, wherein the optical domain controller (100) comprises: a memory (120); a processor (140) coupled to the memory (120); a communication unit (160) coupled to the memory (120) and the processor (140); and an optical domain SRLG manager (180) coupled to the memory (120), the processor (140), and the communication unit (160), wherein the optical domain SRLG manager (180) is configured to: determine SRLG information associated with an optical domain to be shared with an IP domain controller (200) and SRLG information associated with the IP domain; determine a layer identifier for establishing a multi-protocol enabled Border Gateway Protocol (BGP) session between the optical domain and the IP domain, the layer identifier indicating the informing of the SRLG information associated with the optical domain and the SRLG information associated with the IP domain; furthermore, the optical domain SRLG manager (180) is configured to: establish the multi-protocol enabled BGP session between the optical domain controller (100) and the IP domain controller (200) based on the layer identifier; and inform the IP domain controller (200) of the SRLG information associated with the optical domain and the SRLG information associated with the IP domain via the established multi-protocol enabled BGP session. An optical domain controller (100).

14. The optical domain SRLG manager (180) is configured to establish the multi-protocol enabled BGP session between the optical domain controller (100) and the IP domain controller (200) based on a request to the IP domain controller (200); and transmit a request comprising the layer identifier for establishing the multi-protocol enabled BGP session between the optical domain controller (100) and the IP domain controller (200) to the IP domain controller (200). Receive a response accepting the establishment of the multi - protocol enabled BGP session between the optical domain controller (100) and the IP domain controller (200), Exchange functions associated with the multi - protocol enabled BGP session with the IP domain controller (200), The optical domain controller (100) according to claim 13, comprising establishing the multi - protocol enabled BGP session between the optical domain controller (100) and the IP domain controller (200).

15. The optical domain controller (100) according to claim 13, wherein the SRLG information associated with the optical domain includes at least one of an SRLG number associated with the optical domain and information of a UNI interface.

16. The optical domain controller (100) according to claim 13, wherein the SRLG information associated with the IP domain includes information associated with an IP domain router interface, a router identifier (ID) discovered using a neighbor exchange protocol, a link set, a virtual local area network identifier (VLAN ID), and VLAN details.

17. The optical domain controller (100) according to claim 13, wherein the layer identifier is at least one of an address family identifier (AFI) and a subsequent address family identifier (SAFI).

18. An IP domain controller (200) for informing shared risk link group (SRLG) information between multiple layers of a communication network, wherein the IP domain controller (200) comprises A memory (220), A processor (240) coupled to the memory (220), A communication unit (260) coupled to the memory (220) and the processor (240), An IP domain SRLG manager (280) coupled to the memory (220), the processor (240), and the communication unit (260), wherein the IP domain SRLG manager (280) Accepts a multi - protocol enabled BGP session between the optical domain controller (100) and the IP domain controller (200), Receive SRLG information associated with the optical domain and SRLG information associated with the IP domain from the optical domain controller (100) via the established multi - protocol enabled BGP session, Create a local SRLG specific database, Store the received SRLG information associated with the optical domain and the SRLG information associated with the IP domain in the SRLG specific database, An IP domain controller (200) configured to perform at least one of path calculation and path update using at least one of the SRLG information associated with the optical domain and the SRLG information associated with the IP domain stored in the SRLG specific database.

19. The IP domain SRLG manager (280) is configured to accept the multi - protocol enabled BGP session between the optical domain controller (100) and the IP domain controller (200), Receive a request from the optical domain controller (100) comprising a layer identifier for establishing the multi - protocol enabled BGP session between the optical domain controller (100) and the IP domain controller (200), Send a response accepting the establishment of the multi - protocol enabled BGP session between the optical domain controller (100) and the IP domain controller (200), Exchange functions associated with the multi - protocol enabled BGP session with the optical domain controller (100), The IP domain controller (200) according to claim 18, comprising accepting the multi - protocol enabled BGP session between the optical domain controller (100) and the IP domain controller (200).

20. The IP domain controller (200) according to claim 18, wherein the SRLG information associated with the optical domain includes at least one of an SRLG number associated with the optical domain and information of a UNI interface.

21. The SRLG information associated with the IP domain includes information associated with an IP domain router interface, a router identifier (ID) discovered using a neighbor exchange protocol, a link set, a virtual local area network identifier (VLAN ID), and VLAN details, for the IP domain controller (200) according to claim 18.

22. The layer identifier is at least one of an address family identifier (AFI) and a subsequent address family identifier (SAFI), for the IP domain controller (200) according to claim 19.

23. A computer program product (CPP: Computer Program Product) for informing shared risk link group (SRLG) information between multiple layers of a communication network, the CPP comprises computer-executable program code recorded on a computer-readable non-transitory storage medium, the computer-executable program code, when executed, causes operations including determining SRLG information associated with an optical domain and SRLG information associated with an IP domain to be shared with an IP domain controller (200), and determining a layer identifier for establishing a multi-protocol enabled Border Gateway Protocol (BGP) session between the optical domain and the IP domain, wherein the layer identifier indicates the informing of the SRLG information associated with the optical domain and the SRLG information associated with the IP domain, the computer-executable program code, when executed, further causes operations including establishing the multi-protocol enabled BGP session between the optical domain controller (100) and the IP domain controller (200) based on the layer identifier, and informing the IP domain controller (200) of the SRLG information associated with the optical domain and the SRLG information associated with the IP domain via the established multi-protocol enabled BGP session, a CPP.

24. Receiving the SRLG information associated with the optical domain and the SRLG information associated with the IP domain via the established multi-protocol enabled BGP session; Locally creating an SRLG specific database; Storing the received SRLG information associated with the optical domain and the SRLG information associated with the IP domain in the SRLG specific database; Executing at least one of path calculation and path update using at least one of the SRLG information associated with the optical domain and the SRLG information associated with the IP domain stored in the SRLG specific database; The CPP according to claim 23, further comprising.

25. The step of establishing the multi-protocol enabled BGP session between the optical domain controller (100) and the IP domain controller (200) based on the request to the IP domain controller (200) is: Sending a request comprising the layer identifier for establishing the multi-protocol enabled BGP session between the optical domain controller (100) and the IP domain controller (200) to the IP domain controller (200); Receiving a response accepting the establishment of the multi-protocol enabled BGP session between the optical domain controller (100) and the IP domain controller (200); Exchanging functions associated with the multi-protocol enabled BGP session with the IP domain controller (200); Establishing the multi-protocol enabled BGP session between the optical domain controller (100) and the IP domain controller (200); The CPP according to claim 23, including.

26. The CPP according to claim 23, wherein the SRLG information associated with the optical domain includes at least one of an SRLG number associated with the optical domain and information of a UNI interface.

27. The SRLG information associated with the IP domain is the CPP according to claim 23, including information associated with an IP domain router interface, a router identifier (ID) discovered using a neighbor exchange protocol, a link set, a virtual local area network identifier (VLAN ID), and VLAN details.

28. The CPP according to claim 23, wherein the layer identifier is at least one of an address family identifier (AFI) and a subsequent address family identifier (SAFI).

Images