Method and system for communicating SRLG information across 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, the disclosure of which is incorporated herein by reference in its entirety.

[0002] The present invention relates to a communication network, and more particularly, 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, i.e., the L0 / L1 layer, of the transport domain 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 further calculation methods based on the configured SRLG information. SRLG information includes data links that are routed through the same fiber path or that cause multiple outage states, such as fiber cuts, in scenarios.

[0004] Therefore, defining SRLG information at both layers is essential. However, if the telecommunications carriers managing the optical and IP layers are not the same, coordination problems may arise due to inefficient configuration of SRLG information, ultimately leading to diversity issues that affect the user experience. Furthermore, manual sharing of SRLG information can lead to human error and time lapses that reduce the efficiency of the communication network. Therefore, it is desirable to address the aforementioned disadvantages or other shortcomings, or at least provide a useful alternative.

[0005] Purpose of the invention The primary objective of the embodiments described herein is to provide a method and system for advertising shared risk link group (SRLG) information across multiple layers of a communication network. The proposed method includes the automatic detection and advertising of SRLG information from the optical domain layer (L1 / L0) to the IP domain (L3) layer in the transport domain. Thus, the proposed method automates the process, thereby making it faster, more efficient, and resource-effective while reducing the likelihood of human error. [Overview of the Initiative]

[0006] Accordingly, embodiments of this specification provide a method for advertising shared risk link group (SRLG) information across multiple layers of a communication network. The method includes the steps of: an optical domain controller determining SRLG information associated with an optical domain and SRLG information associated with an IP domain to be shared with an IP domain controller; and the optical domain controller determining a layer identifier for establishing a multiprotocol-enabled border gateway protocol (BGP) session between the optical domain and the IP domain. The layer identifier indicates advertising for SRLG information associated with an optical domain and SRLG information associated with an IP domain. The method also includes the steps of: an optical domain controller establishing a multiprotocol-enabled BGP session between the optical domain controller and the IP domain controller based on the layer identifier; and the optical domain controller advertising the SRLG information associated with the optical domain and SRLG information associated with the IP domain to the IP domain controller via the established multiprotocol-enabled BGP session.

[0007] In one embodiment, the method further includes the steps of: an IP domain controller receiving SRLG information associated with an optical domain and SRLG information associated with an IP domain via an established multiprotocol-enabled BGP session; and the IP domain controller creating an SRLG-specific database locally. The method also includes the steps of: the IP domain controller storing the received SRLG information associated with an optical domain and SRLG information associated with an IP domain in the SRLG-specific database; and the IP domain controller using at least one of the SRLG information associated with an optical domain and SRLG information associated with an IP domain stored in the SRLG-specific database to perform at least one of route calculation and route updating.

[0008] In one embodiment, the steps of an optical domain controller establishing a multiprotocol-enabled BGP session between the optical domain controller and the IP domain controller based on a request to the IP domain controller include: the optical domain controller sending a request to the IP domain controller that includes a layer identifier for establishing a multiprotocol-enabled BGP session between the optical domain controller and the IP domain controller; and the optical domain controller receiving a response that accepts the establishment of a multiprotocol-enabled BGP session between the optical domain controller (100) and the IP domain controller. The method also includes the steps of 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 UNI interface information.

[0010] In one embodiment, the SRLG information associated with an 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.

[0011] In one embodiment, the layer identifier is at least one of an Address Family Identifier (AFI) and a Subsequent Address Family Identifier (SAFI).

[0012] Accordingly, embodiments of this specification provide a system for communicating shared risk link group (SRLG) information across multiple layers of a communication network. The system includes an optical domain controller for optical domains and an IP domain controller for IP domains. The optical domain controller is configured to determine the SRLG information associated with the optical domain and the SRLG information associated with the IP domain to be shared with the IP domain controller, 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 that the information is a 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 communicate 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.

[0013] Accordingly, embodiments of this specification provide an optical domain controller for announcing shared risk link group (SRLG) information across multiple layers of a communication network. The optical domain controller includes 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 and SRLG information associated with an IP domain to be shared with an IP domain controller, and to determine a layer identifier for establishing a multiprotocol-enabled border gateway protocol (BGP) session between the optical domain and the IP domain. The layer identifier indicates that the information is an announcement of SRLG information associated with an optical domain and SRLG information associated with an IP domain. Based on the layer identifier, the optical domain SRLG manager is configured to establish a multiprotocol-enabled BGP session between the optical domain controller and the IP domain controller and to announce the SRLG information associated with the optical domain and SRLG information associated with the IP domain to the IP domain controller via the established multiprotocol-enabled BGP session.

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

[0015] Accordingly, embodiments of this specification provide a computer program product (CPP) for announcing shared risk link group (SRLG) information across multiple layers of a communication network. The CPP comprises computer executable program code recorded on a computer-readable non-transitory storage medium, which, when executed, triggers an operation comprising the following steps: determining SRLG information associated with an optical domain and SRLG information associated with an IP domain to be shared with an IP domain controller; and determining a layer identifier for establishing a multiprotocol-enabled border gateway protocol (BGP) session between the optical domain and the IP domain. The layer identifier indicates that the announcement is for SRLG information associated with an optical domain and SRLG information associated with an IP domain. The CPP also comprises the steps of establishing a multiprotocol-enabled BGP session between the optical domain controller and the IP domain controller based on the layer identifier, and announcing the SRLG information associated with the optical domain and SRLG information associated with the IP domain to the IP domain controller via the established multiprotocol-enabled BGP session.

[0016] These and other aspects of the embodiments specified herein will be better recognized and understood in conjunction with the following description and accompanying drawings. However, it should be understood that the following description, while showing preferred embodiments and numerous specific details thereof, is given as examples only and not as an limitation. Many changes and modifications can be made within the scope of the embodiments specified herein without departing from that scope, and the embodiments specified herein 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] Shows an overall view of the Internet Protocol (IP) layer of the optical layer and the transport domain according to related art (prior art).

[0019] [Figure 2] Shows the manual exchange of Shared Risk Link Group (SRLG) information between the optical layer and the IP layer in the transport domain according to related art.

[0020] [Figure 3A] It is a block diagram of an optical domain controller that automatically notifies SRLG information among multiple layers of a communication network according to the embodiments disclosed in this specification.

[0021] [Figure 3B] It is a block diagram of an IP domain controller that communicates with an optical domain controller to automatically receive SRLGs according to the embodiments disclosed in this specification.

[0022] [Figure 4] It is a flowchart showing a method for automatically notifying SRLG information among multiple layers of a communication network according to the embodiments disclosed in this specification.

[0023] [Figure 5] Shows BGP extensions (BGP extensions) for carrying SRLG information between an optical domain controller and an IP domain controller according to the embodiments disclosed in this specification.

[0024] [Figure 6]Shows the BGP negotiation function between an optical domain controller and an IP domain controller according to the embodiments disclosed in this specification.

[0025] [Figure 7] Shows the BGP NLRI encoding for route advertisement between an optical domain controller and an IP domain controller according to the embodiments disclosed in this specification.

[0026] [Figure 8] Shows the automatic exchange of SRLG information between an optical domain controller and an IP domain controller via a BGP session according to the embodiments disclosed in this specification. **DETAILED DESCRIPTION OF THE INVENTION**

[0027] The embodiments of this specification and their various features and advantageous details are shown in the accompanying drawings and will be more fully described by 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" used in this specification means "non-exclusive or" unless otherwise specified. The examples used in this specification are only intended to facilitate understanding of the ways in 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 in terms of blocks that perform one or more of the functions described herein. 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, and hardwired circuits, and may optionally be driven by firmware. The circuits may be embodied, for example, in one or more semiconductor chips or on a substrate support such as a printed circuit board. The circuits constituting 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 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 disclosure of the present invention. Similarly, the blocks of an embodiment may be physically coupled into more complex blocks without departing from the scope of the disclosure of the present invention.

[0029] The accompanying drawings are provided to facilitate understanding of various technical features, and it should be understood that the embodiments presented herein are not limited by the accompanying drawings. Therefore, the disclosure of the present invention should be interpreted as extending to any modifications, equivalents, and substitutions in addition to those specifically described in the accompanying drawings. While various elements may be described herein using terms such as "first," "second," etc., 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 this specification provide a method for announcing shared risk link group (SRLG) information across multiple layers of a communication network. The method includes the steps of: an optical domain controller determining SRLG information associated with an optical domain and SRLG information associated with an IP domain to be shared with an IP domain controller; and the optical domain controller determining a layer identifier for establishing a multiprotocol-enabled border gateway protocol (BGP) session between the optical domain and the IP domain. The layer identifier indicates that the announcement is for SRLG information associated with an optical domain and SRLG information associated with an IP domain. The method also includes the steps of: an optical domain controller establishing a multiprotocol-enabled BGP session between the optical domain controller and the IP domain controller based on the layer identifier; and the optical domain controller announcing the SRLG information associated with the optical domain and SRLG information associated with the IP domain to the IP domain controller via the established multiprotocol-enabled BGP session.

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

[0032] Accordingly, embodiments of this specification provide a computer program product (CPP) for announcing shared risk link group (SRLG) information across multiple layers of a communication network. The CPP comprises computer executable program code recorded on a computer-readable non-temporary storage medium, which, when executed, triggers an operation comprising the following steps: determining SRLG information associated with an optical domain and SRLG information associated with an IP domain to be shared with an IP domain controller; and determining a layer identifier for establishing a multiprotocol-enabled border gateway protocol (BGP) session between the optical domain and the IP domain. The layer identifier indicates that the announcement is for SRLG information associated with an optical domain and SRLG information associated with an IP domain. The CPP also comprises the steps of establishing a multiprotocol-enabled BGP session between the optical domain controller and the IP domain controller based on the layer identifier, and announcing the SRLG information associated with the optical domain and SRLG information associated with the IP domain to the IP domain controller via the established multiprotocol-enabled BGP session.

[0033] Conventional methods and systems manually supply SRLG information from optical domains (L0 / L1) to IP domains (L3). This requires significant human resources and can lead to synchronization errors. Unlike conventional methods and systems, the method proposed in this disclosure includes automatic synchronization of SRLG information across domains.

[0034] Conventional methods and systems, which involve the manual configuration of SRLG information in an IP domain, can lead to human error and time lapses 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 and SAFI values ​​that indicate SRLG information in the MP BGP protocol, which automates the process of communicating SRLG information across layers.

[0036] Referring here to the drawings, more specifically Figures 1 to 8, similar reference numerals consistently indicate corresponding features throughout the drawings, illustrating preferred embodiments.

[0037] Figure 1 shows a comprehensive diagram of the optical layer and Internet Protocol (IP) layer of the transport domain using related technologies.

[0038] Referring to Figure 1, in existing network architectures, the IP layer, i.e., Layer 3 (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), optical domain controllers and IP domain controllers are used to define routes in the optical and IP layers, respectively.

[0039] When two links share a common fiber path, the two links are part of the SRLG (Service-Linked Link). SRLG information is important in transport domains that provide various services, such as, but not limited to, disjoint path management scenarios during fiber closure. SRLG information is generally propagated from the optical layer (L0 / L1 layers) to the IP layer (L3 layers) via a manual process in which the optical and IP layers operate independently of each other. Each of the optical and IP layers is managed by an administrator that works in conjunction with each other to share and configure SRLG information. Furthermore, the configured SRLG information is passed to an IP domain controller that determines further calculation methods based on the configured SRLG information. However, if the network operators managing the optical and IP layers are not the same, coordination issues can arise due to inefficient configuration of SRLG information, potentially leading to diversity issues that ultimately affect the user experience. Additionally, manual sharing of SRLG information can lead to human error, time-lapse issues that reduce the efficiency of the communication network, and synchronization issues.

[0040] Figure 2 illustrates the manual exchange of SRLG information between the optical layer and the IP layer of the transport domain using related technology.

[0041] Referring to Figure 2, an existing mechanism for manually sharing SRLG information is described. In step 1, the SRLG information is configured as an L0 / L1 network at the optical layer. In step 2, the SRLG information is manually coordinated between the optical layer and the IP layer by the optical domain administrator and the IP domain administrator, respectively. Furthermore, in step 3, the IP domain administrator configures the SRLG information received from the optical domain administrator as SRLG information configured as an L3 / IP network at the IP layer of the transport domain. In step 4, the SRLG is then announced to the IP / SDN controller for route calculation.

[0042] However, existing methods for manually configuring SRLG information in IP domains can lead to human error, reduced network efficiency between optical and IP domains, and time-lapse or synchronization problems.

[0043] Figure 3A is a block diagram of an optical domain controller (100) that automatically announces 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 optical domains and SRLG information associated with IP domains. The memory (120) is also configured to store layer identifiers determined by the optical domain controller (100). Furthermore, the memory (120) also stores instructions executed by the processor (140). The memory (120) may include non-volatile memory elements. Examples of such non-volatile memory elements may include magnetic hard disks, optical disks, floppy disks, flash memory, or electrically programmable memory (EPROM) or electrically erasable programmable memory (EEPROM). Furthermore, in some examples, the memory (120) can be considered a non-transitory storage medium. The term "non-transitory" may indicate that the storage medium is not embodied in a carrier wave or propagating signal. However, the term "non-transitory" should not be interpreted as meaning that the memory (120) is non-movable. In some examples, the memory (120) may be configured to store larger amounts of information. In certain cases, non-temporary storage media can store data that may change over time (for example, in random-access memory (RAM) or a cache).

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

[0046] The communication unit (160) includes electronic circuits specific to standards that enable wired or wireless communication. The communication unit (160) is configured to communicate internally between 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 processing circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, and hardwired circuits, and can optionally be driven by firmware. The circuits 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 an optical domain and SRLG information associated with an IP domain to be shared with the IP domain controller (200). The SRLG information associated with an optical domain includes the SRLG number associated with the optical domain and information about the UNI interface. The SRLG information associated with an IP domain includes information associated with the IP domain router interface, a router identifier (ID) discovered using the neighbor exchange protocol, a link aggregation, a virtual local area network identifier (VLAN ID), and VLAN details.

[0049] In one embodiment, a layer identifier manager (184) is configured to determine a layer identifier for establishing a Multiprotocol Enabled Border Gateway Protocol (BGP) session between an optical domain and an 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 layer identifier is, for example, 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 the IP domain controller (200) to establish a multiprotocol-enabled BGP session between the optical domain controller (100) and the IP domain controller (200), and to receive a response from the IP domain controller (200) accepting the establishment of a multiprotocol-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 multiprotocol-enabled BGP session with the IP domain controller (200) and to establish a multiprotocol-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 SRLG information associated with optical domains and SRLG information associated with IP domains to the IP domain controller (200) via an established multiprotocol-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. Functions associated with the AI ​​model can be performed by memory (120) and a processor (140). One or more processors control the processing of input data according to predetermined operating rules or AI models stored in non-volatile memory and volatile memory. The predetermined operating rules or artificial intelligence models are provided by training or learning.

[0053] Here, "provided by learning" means that a predetermined set of behavioral rules or an AI model with desired characteristics is created by applying a learning process to multiple training data sets. Learning may be performed on the device on which the AI ​​according to the embodiment is run, and / or may be implemented by a separate server / system.

[0054] An AI model may consist of multiple neural network layers. Each layer has multiple weight values ​​and performs layer operation through calculation of a previous layer and calculation of the multiple 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] A learning process is a method of training a given target device (e.g., a robot) using multiple training data sets, enabling the device to make decisions or predictions, permit actions, or control actions. Examples of learning processes include, but are not limited to, supervised learning, unsupervised learning, semi-supervised learning, or reinforcement learning.

[0056] Figure 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) may include fewer or more components. Furthermore, the labels or names of the components are for illustrative purposes only and do not limit the scope of the invention. One or more components can be combined to perform the same or substantially similar functions as managing application logs based on various events.

[0057] Figure 3B is a block diagram of an IP domain controller (200) that communicates with an optical domain controller to automatically receive SRLGs, according to an embodiment 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 optical domains and SRLG information associated with IP domains received from the optical domain controller (100). The memory (220) is also configured to store layer identifiers. Furthermore, the memory (220) also stores instructions executed by the processor (240). The memory (220) may include non-volatile memory elements. Examples of such non-volatile memory elements may include magnetic hard disks, optical disks, floppy disks, flash memory, or electrically programmable memory (EPROM) or electrically erasable programmable memory (EEPROM). Furthermore, in some examples, the memory (220) can be considered a non-temporary storage medium. The term "non-temporary" may indicate that the storage medium is not embodied in a carrier wave or propagating signal. However, the term "non-temporary" should not be interpreted as meaning that the memory (220) is immovable. In some examples, the memory (220) may be configured to store larger amounts of information. In certain cases, non-temporary storage media can store data that may change over time (for example, in random-access memory (RAM) or a cache).

[0059] The processor (240) communicates with memory (220), a communication unit (260), and an IP domain SRLG manager (280). The processor (140) is configured to execute instructions stored in memory (220) and run various processes. The processor may include one or more processors, possibly including general-purpose processors such as a central processing unit (CPU) and application processors (AP), graphics-only processing units such as graphics processing units (GPUs) and visual processing units (VPUs), and / or artificial intelligence (AI) dedicated processors such as neural processing units (NPUs).

[0060] The communications unit (260) includes electronic circuits specific to standards that enable wired or wireless communication. The communications unit (260) is configured to communicate internally between 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 processing circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, and hardwired circuits, and can optionally be driven by firmware. The circuits 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 requests 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, the BGP session manager (284) is configured to receive a request from the optical domain controller (100) including a layer identifier requesting the establishment of a multiprotocol-enabled BGP session between the optical domain controller (100) and the IP domain controller (200), and to send a response accepting the establishment of a multiprotocol-enabled BGP session between the optical domain controller (100) and the IP domain controller (200). Furthermore, the BGP session manager (284) is configured to exchange functions associated with the multiprotocol-enabled BGP session with the optical domain controller (100) and to accept the multiprotocol-enabled BGP session between the optical domain controller (100) and the IP domain controller (200). The BGP session manager (284) is configured to 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 multiprotocol-enabled BGP session.

[0064] The SRLG information manager (282) is also configured to locally create an SRLG-specific database and store the SRLG information associated with the received optical domain and the SRLG information associated with the IP domain in the SRLG-specific database. Furthermore, the SRLG information manager (282) is configured to perform at least one of path computation and path updating 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 multiple modules / components of the IP domain SRLG manager (280) may be implemented by an AI model. Functions associated with the AI ​​model can be performed by memory (220) and a processor (240). One or more processors control the processing of input data according to predetermined operating rules or AI models stored in non-volatile memory and volatile memory. The predetermined operating rules or artificial intelligence models are provided by training or learning.

[0066] Here, "provided by learning" means that a predetermined set of behavioral rules or an AI model with desired characteristics is created by applying a learning process to multiple training data sets. Learning may be performed on the device on which the AI ​​according to the embodiment is run, and / or may be implemented by a separate server / system.

[0067] An AI model may consist of multiple neural network layers. Each layer has multiple weight values ​​and performs layer operations based on calculations from the previous layer, as well as operations on the multiple 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.

[0068] A learning process is a method of training a given target device (e.g., a robot) using multiple training data sets, enabling the device to make decisions or predictions, permit actions, or control actions. Examples of learning processes include, but are not limited to, supervised learning, unsupervised learning, semi-supervised learning, or reinforcement learning.

[0069] Figure 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) may include fewer or more components. Furthermore, the labels or names of the components are for illustrative purposes only and do not limit the scope of the invention. One or more components can be combined to perform the same or substantially similar functions as managing application logs based on various events.

[0070] Figure 4 is a flowchart (400) illustrating a method for automatically disseminating SRLG information between multiple layers of a communication network according to embodiments disclosed herein.

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

[0072] In step 404, the method includes the step of determining a layer identifier for establishing a multiprotocol-enabled BGP session between the optical domain and the IP domain, which is performed by the optical domain controller (100). For example, in the optical domain controller (100) shown in Figure 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 the optical domain controller (100) establishing 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 Figure 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 the optical domain controller (100) informing the IP domain controller (200) of SRLG information associated with the optical domain and SRLG information associated with the IP domain via an established multiprotocol-enabled BGP session. For example, in the optical domain controller (100) shown in Figure 3A, the optical domain SRLG manager (180) is configured to inform the IP domain controller (200) of SRLG information associated with the optical domain and SRLG information associated with the IP domain via an established multiprotocol-enabled BGP session.

[0075] The various actions, operations, blocks, steps, etc. in the flowchart (400) may be executed in the order presented, in a different order, or simultaneously. Furthermore, 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] Figure 5 shows a BGP extension for carrying SRLG information between an optical domain controller (100) and an IP domain controller (200) according to an embodiment disclosed herein.

[0077] Referring to Figure 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 this disclosure, an existing multiprotocol-enabled border gateway protocol (BGP) session is modified and used for the automatic detection and communication of SRLG information between the optical domain controller (100) and the IP domain controller (200), i.e., for transporting SRLG information from the (L0 / L1) layer to the (L3) layer.

[0078] The optical domain controller (100) holds SRLG information associated with optical domains and SRLG information associated with IP domains. Furthermore, the optical domain controller (100) uses the Link Layer Discovery Protocol (LLDP) protocol (EtherType-0x88cc) to obtain details such as the connection between the transponder and the Layer 3 router, thereby enabling the optical domain controller (100) to forward SRLG information associated with IP domains.

[0079] SRLG information associated with an optical domain includes, but is not limited to, the SRLG number associated with the optical domain and information about the UNI interface. Information received from LLDP includes, but is not limited to, information associated with the IP domain router interface, the router identifier (ID) (management address) discovered using the Neighbor Exchange protocol, the link set, the virtual local area network identifier (VLAN ID), and VLAN details that provide relevant information about the connected IP network. The BGP protocol can use relevant information to advertise SRLG information at both layers.

[0080] Figure 6 shows the BGP negotiation function between an optical domain controller and an IP domain controller according to the embodiments disclosed herein.

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

[0082] Referring to Figure 6, when a BGP session is formed, the optical domain controller (100) and the IP domain controller (200) first exchange functions. In the method proposed in this disclosure, the multiprotocol BGP protocol is modified to include layer identifiers that indicate SRLG-specific purposes. Layer identifiers are, for example, AFI and SAFI in existing multiprotocol BGP, but are not limited to these.

[0083] When the IP domain controller (200) receives an MP BGP protocol request, it can determine that the information to be shared is SRLG information. Therefore, since the IP domain controller (200) receives SRLG information directly 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, initial session negotiation takes place. This includes the following exchanges in the BGP protocol: 1. L1 SRLG information, including SRLG number and UNI interface. 2. Details of the L3 router interface, and the router ID discovered using the Neighbor Switching Protocol (LLDP).

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

[0086] In Step 2, once the optical domain controller (100) and the IP domain controller (200) agree on multiprotocol functionality, the optical domain controller (100) sends a BGP update regarding SRLG information. Upon receiving the SRLG information from the optical domain controller (100), the IP domain controller (200) creates a local SRLG-specific database. As a result, the IP domain controller (200) no longer relies on SRLG information arriving from the IP layer. All further route calculations / updates can use the available SRLG-specific information to calculate the required disjoint paths in the transport domain. The addition of any new SRLGs in the network becomes seamlessly available to the IP domain controller (200). Thus, the optical domain controller (100) avoids the repeated configuration and announcement of SRLG information from the IP layer, and therefore simplifies its deployment.

[0087] Figure 8 illustrates the automatic exchange of SRLG information between an optical domain controller (100) and an IP domain controller (200) via a BGP session according to an embodiment disclosed herein. Referring to Figure 8, in step 1, the SRLG is configured in an L0 / L1 network. In step 2, the SRLG information is available to the optical domain controller (100) or any element enabling BGP signaling and provides seamless BGP NLRI announcements. 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 announced via the established MP-BGP session. Thus, the method proposed herein eliminates manual intervention in the SRLG announcement procedure. This also enables tamper-proofing, error-proofing, and seamless synchronization in the SRLG announcement procedure. The following terms will be used throughout this specification. SRLG (Shared Risk Link Group) L0 / L1: Layer 0 and Layer 1 represent optical layers. L3 IP Layer L1 Controller: Path calculation engine within the optical layer L3 Controller IP Layer Routing Engine PCEP Path Calculation Engine BGP Link State Protocol exports BGP-LS transport network topology Discontinuous routing: A method of providing different routes, routers, and resources for two sets of services a customer subscribes to. LLDP (Link Layer Discovery Protocol) AFI Address Family Identifier SAFI Successor Address Family Identifier RTR Router NLRI Network Layer Reachability Information

[0088] The foregoing description of specific embodiments fully illustrates the general nature of the embodiments herein so that others can readily modify and / or adapt such specific embodiments to various uses without departing from the higher concepts by applying their current knowledge, and such adaptations and modifications should and are intended to be understood within the meaning and scope of the equivalents of the disclosed embodiments. It should be understood that any expressions or terms used herein are for illustrative purposes only and not for limitation. Thus, although the embodiments herein have been described in relation to preferred embodiments, those skilled in the art will recognize that the embodiments herein can be modified and implemented within the scope of the embodiments described herein.

Claims

1. A method for communicating Shared Risk Link Group (SRLG) information between multiple layers of a communication network, wherein the method is: The optical domain controller determines the SRLG information associated with the optical domain and the SRLG information associated with the IP domain that should be shared with the IP domain controller. The optical domain controller has the step of determining a layer identifier for establishing a multiprotocol-enabled border gateway protocol (BGP) session between the optical domain and the IP domain, wherein the layer identifier indicates the SRLG information associated with the optical domain and the notification of the SRLG information associated with the IP domain. The above method further, The optical domain controller establishes the multiprotocol-enabled BGP session between the optical domain controller and the IP domain controller based on the layer identifier. A method comprising the steps of: the optical domain controller notifying 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 multiprotocol-enabled BGP session.

2. 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 multiprotocol-enabled BGP session. The aforementioned IP domain controller performs the step of creating an SRLG-specific database locally, 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. The steps include: the IP domain controller performing at least one of route calculation and route 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 method according to claim 1, further comprising:

3. The step of the optical domain controller establishing the multiprotocol-enabled BGP session between the optical domain controller and the IP domain controller based on the layer identifier is: The optical domain controller sends a request to the IP domain controller that includes the layer identifier for establishing the multiprotocol-enabled BGP session between the optical domain controller and the IP domain controller. The optical domain controller receives a response accepting the establishment of the multiprotocol-enabled BGP session between the optical domain controller and the IP domain controller. The optical domain controller exchanges functions associated with the multiprotocol-enabled BGP session with the IP domain controller. The method according to claim 1, further comprising the step of the optical domain controller establishing the multiprotocol-enabled BGP session between the optical domain controller and the IP domain controller.

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

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 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 disseminating shared risk link group (SRLG) information across multiple layers of a communication network, wherein the system It includes an optical domain controller for optical domains and an IP domain controller for IP domains. The aforementioned optical domain controller, It is configured to determine the SRLG information associated with the optical domain and the SRLG information associated with the IP domain that should be shared with the IP domain controller. It is configured to determine a layer identifier for establishing a multiprotocol-enabled border gateway protocol (BGP) session between the optical domain and the IP domain, wherein the layer identifier indicates the SRLG information associated with the optical domain and the notification of the SRLG information associated with the IP domain. The optical domain controller further, The system is configured to establish the multiprotocol-enabled BGP session between the optical domain controller and the IP domain controller based on the layer identifier, A system configured 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 multiprotocol-enabled BGP session.

8. The optical domain controller further: It is configured to receive SRLG information associated with the optical domain and SRLG information associated with the IP domain via the established multiprotocol-enabled BGP session. It is configured to create an SRLG-specific database locally. The system is 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, configured to perform at least one of route calculation and route updating 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.

9. The optical domain controller is configured to establish the multiprotocol-enabled BGP session between the optical domain controller and the IP domain controller based on the layer identifier, A request including the layer identifier for establishing the multiprotocol-enabled BGP session between the optical domain controller and the IP domain controller is sent to the IP domain controller. Upon receiving a response accepting the establishment of the multiprotocol-enabled BGP session between the optical domain controller and the IP domain controller, The IP domain controller and the functions associated with the multiprotocol-enabled BGP session are exchanged. The system according to claim 7, comprising establishing the multiprotocol-enabled BGP session between the optical domain controller and the IP domain controller.

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

11. The system according to claim 7, 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.

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

13. An optical domain controller that communicates shared risk link group (SRLG) information between multiple layers of a communication network, wherein the optical domain controller Communications Department and, The system comprises an optical domain SRLG manager, and the optical domain SRLG manager is It is configured to determine the SRLG information associated with the optical domain and the SRLG information associated with the IP domain that should be shared with the IP domain controller. It is configured to determine a layer identifier for establishing a multiprotocol-enabled border gateway protocol (BGP) session between the optical domain and the IP domain, wherein the layer identifier indicates the SRLG information associated with the optical domain and the notification of the SRLG information associated with the IP domain. The aforementioned optical domain SRLG manager further, The system is configured to establish the multiprotocol-enabled BGP session between the optical domain controller and the IP domain controller based on the layer identifier, An optical domain controller configured to inform 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 multiprotocol-enabled BGP session.

14. The optical domain SRLG manager is configured to establish the multiprotocol-enabled BGP session between the optical domain controller and the IP domain controller based on the layer identifier. A request containing the layer identifier for establishing the multiprotocol-enabled BGP session between the optical domain controller and the IP domain controller is sent to the IP domain controller. Upon receiving a response accepting the establishment of the multiprotocol-enabled BGP session between the optical domain controller and the IP domain controller, The IP domain controller and the functions associated with the multiprotocol-enabled BGP session are exchanged. The optical domain controller according to claim 13, comprising establishing the multiprotocol-enabled BGP session between the optical domain controller and the IP domain controller.

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

16. The optical domain controller 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. An IP domain controller that communicates shared risk link group (SRLG) information across multiple layers of a communication network, wherein the IP domain controller Communications Department and, The system comprises an IP domain SRLG manager, and the IP domain SRLG manager is Accepts multiprotocol enabled BGP sessions between optical domain controllers and IP domain controllers. The optical domain controller receives SRLG information associated with the optical domain and SRLG information associated with the IP domain via the established multiprotocol-enabled BGP session. Create an SRLG-specific database locally, The SRLG information associated with the received optical domain and the SRLG information associated with the IP domain are stored in the SRLG-specific database. An IP domain controller configured to perform at least one of route calculation and route updating using at least one of the SRLG information associated with the optical domain and the SRLG information associated with the IP domain, which are stored in the SRLG-specific database.

18. The IP domain SRLG manager is configured to accept the multiprotocol-enabled BGP session between the optical domain controller and the IP domain controller. Between the optical domain controller and the IP domain controller, the multiprocessor A request containing a layer identifier for establishing a valid BGP session is received from the optical domain controller. Send a response accepting the establishment of the multiprotocol-enabled BGP session between the optical domain controller and the IP domain controller. The functions associated with the multiprotocol-enabled BGP session are exchanged with the optical domain controller. The IP domain controller according to claim 17, comprising accepting the multiprotocol-enabled BGP session between the optical domain controller and the IP domain controller.

19. The IP domain controller according to claim 17, wherein the SRLG information associated with the optical domain includes at least one of the SRLG number and UNI interface information associated with the optical domain.

20. The IP domain controller according to claim 17, wherein the SRLG information associated with the IP domain includes information associated with the 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.

Images