TWI635728B - System and method for mapping transmission network resources in software defined network - Google Patents

Abstract

The present invention provides a system and method for mapping transmission network resources in a software-defined network, the system comprising a requirement management module, an available path management module, an access and transmission device endpoint mapping relationship management module, and a mapping The mechanism uses modules. The demand management module stores and maintains service path requirements. The available path management module stores and maintains an available path table. The access and transmission device endpoint mapping relationship management module stores and maintains the mapping relationship table. The mapping mechanism uses the module to query the mapping relationship between the access device endpoint and the transmission device endpoint that meets the service path requirement, and query the available path table to meet the mapping relationship and the service path requirement. The available path and the services required to provide the service path requirements with that available path.

Description

 System and method for mapping transmission network resources in software defined network  

The present invention relates to a network transmission system, and more particularly to a system and method for mapping a transportable network resource in a software-defined network.

Software-Defined Network (SDN) enables telecom operators to build highly flexible networks and provide a variety of new forms of telecommunications, network and information services. However, the transmission network equipment mainly used by telecom operators at this stage includes NGSDH (next generation synchronous digital hierarchy network), PTN (packet transmission network), ROADM (reconfigurable optical plug-in multiplexer), OTN ( Optical transmission networks and other types of transmission equipment are mostly designed before the SDN standard and technology are mature. Most of these equipments do not support OpenFlow (open flow) protocol when they are shipped from the factory, and they cannot be directly used on SDN. In order to invest in SDN, new SDN network equipment will usually be purchased without considering the use of these existing transmission equipment, which will result in waste of resources and reduce the flexibility of the overall network operation.

From the above, a novel method is needed to assist the user in properly solving the existing problems.

One of the objects of the present invention is to provide a system and method for mapping transmission network resources in a software-defined network to solve the above problems.

Another object of the present invention is to enable a transmission device that does not originally support SDN to be used in an SDN environment without upgrading software or hardware. In addition, after the resource configuration is completed according to the mapping content, the transmission device only needs to operate according to the current mode, and the service can be provided in the SDN environment, so that the old device can continue to be used, thereby reducing resource waste.

Another object of the present invention is to apply to a variety of transmission network devices, so that resources of multiple transmission networks can be combined and used in an SDN environment. In the traditional transmission network, whether it is NGSDH (next generation synchronous digital network), PTN (packet transmission network), ROADM (reconfigurable optical plug-in multiplexer), OTN (optical transport network), etc. Types of transmission network equipment, equipment vendors usually provide network management (NMS, Network Management System) and network management northbound interface (NBI, North-Bound Interface) power supply provider. With the mapping method proposed by the present invention, the resources of multiple transmission networks can be combined and used, and the application scope is not limited to a specific type of transmission network device, but can be extended and transmitted in various new and old types. Network equipment to improve flexibility.

An embodiment of the present invention provides a system for mapping a transmission network resource in a software-defined network, where the system includes a requirement management module, an available path management module, and an access device and an endpoint mapping management module of the transmission device. And the mapping mechanism uses modules. The demand management module stores and maintains service path requirements. The available path management module stores and maintains an available path table. The access and transmission device endpoint mapping relationship management module stores and maintains the mapping relationship table. The mapping mechanism uses the module to query the mapping relationship table from the mapping relationship table to the mapping relationship between the access device endpoint and the transmission device endpoint, and query the available routing table to meet the mapping relationship and the service path requirement. The available path and the services required to provide the service path requirements with that available path.

Another embodiment of the present invention provides a method for mapping a transport network resource in a software-defined network, including: receiving a service path requirement, and obtaining a first demand endpoint and a second demand end from the service path requirement Point and demand rate; querying the mapping relationship between the access device endpoint and the transport device endpoint that meets the service path requirement in the self-mapping relationship table; and querying the available path from the available path table that meets the mapping relationship and the service path requirement And provide the services required for the service path requirement with this available path.

The detailed description of the preferred embodiments of the present invention is intended to be limited to the scope of the invention, and is not intended to limit the scope of the invention. The patent scope of this case.

1‧‧‧Equipment network management system

11‧‧‧Northbound interface

12‧‧‧Transmission equipment

2‧‧‧Integrated network management system

21‧‧‧NGSDH transmission network

22‧‧‧PTN transmission network

23‧‧‧ROADM transmission network

24‧‧‧OTN transmission network

25‧‧‧Other technology transmission networks

26‧‧‧Transmission network consisting of transmission equipment supporting OpenFlow

3‧‧‧Systems that map transmission network resources to software-defined networks

31‧‧‧ Demand Management Module

32‧‧‧Available path management module

33‧‧‧Access and transmission equipment endpoint mapping management module

34‧‧‧ Mapping mechanism application module

35‧‧‧Equipment transmission network management interface module

36‧‧‧Transmission device interface module

4‧‧‧ Source of demand

S01~S14‧‧‧Step procedure

1 is a schematic diagram of a device network management system according to an embodiment of the present invention.

2 is a schematic diagram of an integrated network management system in accordance with an embodiment of the present invention.

3 is a schematic diagram of a network system in accordance with an embodiment of the present invention.

4 is a schematic diagram of a network system in accordance with an embodiment of the present invention.

FIG. 5 is a schematic diagram of a network system according to an embodiment of the present invention.

6 is a schematic diagram of a network system in accordance with an embodiment of the present invention.

FIG. 7 is a demand table, a mapping relationship table, and an available path table according to an embodiment of the present invention.

8 is a flow chart of a method for mapping transport network resources in a software-defined network according to an embodiment of the present invention.

9 is a block diagram of a system for mapping transport network resources in a software-defined network in accordance with an embodiment of the present invention.

The spirit and scope of the present invention will be described in the following detailed description of the preferred embodiments of the present invention, which can be modified and modified by the teachings of the present invention. The spirit and scope of the present invention.

The terms “first”, “second”, etc. used in this document are not specifically intended to refer to the order or order, nor are they used to limit the case. They are only used to distinguish between components or operations described in the same technical terms. .

The terms used in this document, unless otherwise specified, generally have the usual meaning of each term used in the art, in the context of the disclosure, and in the particular content. Certain terms used to describe the disclosure are discussed below or elsewhere in this specification to provide additional guidance to those skilled in the art in the description of the disclosure.

Please refer to FIG. 1. FIG. 1 is a schematic diagram of a device network management system according to an embodiment of the present invention. As shown in Figure 1, the Network Management System (NMS) used by the general telecommunications industry can be used to uniformly manage multiple transmission devices 12 (NEs, Network Elements) and other networks that need to be used. Equipment and information equipment. The equipment vendor network management system 1 usually provides a North-Bound Interface (NBI) that supports standard or vendor-defined functions, which are operated by telecom operators through programs developed by equipment vendors or telecom operators. Includes new, modified, deleted virtual circuits, and other features. In this network, the possible technical types of the NE include at least NGSDH, PTN, ROADM, OTN, OpenFlow, and other technologies. However, a device network management system cannot usually manage multiple NEs of different technical types, or cannot manage multiple types. NEs manufactured by different equipment manufacturers, so an integrated network management system (Integrated NMS) is needed to meet this demand.

Please refer to FIG. 2. FIG. 2 is a schematic diagram of an integrated network management system according to an embodiment of the present invention. As shown in FIG. 2, the integrated network management system 2 can support a network of equipment vendors in various technical categories. That is to say, the integrated network management system 2 can send a corresponding northbound interface (NBI, North-Bound Interface) instruction or device (NE) instruction according to the type of the transmission network of the equipment provider, and the instruction may be in accordance with the OpenFlow protocol. Instructions, or other instructions supported by the transmission device. Supported transport network equipment technology categories may include (but are not limited to): NGSDH transport network 21, PTN transport network 22, ROADM transport network 23, OTN transport network 24, other technology transport network 25 and support A transmission network 26 consisting of OpenFlow's transmission equipment.

It should be appreciated that the present invention relates to a system and method for mapping transport network resources in a software-defined network, which can convert a transport network device without SDN function into a virtual resource in an SDN network, and have The transmission network devices of the SDN function work together. In addition, the system for mapping transmission network resources in a software-defined network as shown in the embodiment of the present invention is a system with integrated NMS functions and features, which can be implemented as an SDN controller (controller)/ Part of the SDN coordinator (orchestrator) or another device operating in parallel with the SDN controller/SDN orchestrator.

For example, a system for mapping transmission network resources in a software-defined network as shown in an embodiment of the present invention can be used to manage three types of networks: (1) one or more devices having a network management system and a northbound interface. A network consisting of transmission equipment (2) one or more networks (3) consisting of transmission equipment without a network equipment system and a northbound interface, and a hybrid network consisting of one or more of the above two networks. The above three network embodiments will be described in detail as follows: Please refer to FIG. 3, which is a schematic diagram of a network system according to an embodiment of the present invention. As shown in FIG. 3, the system 3 (hereinafter referred to as system 3) that maps transmission network resources in a software-defined network is applicable to the first network described above (that is, has one or more A network consisting of a device network management system and a northbound interface transmission device uses a device network management system 1 and a north interface 11 to uniformly manage a plurality of transmission devices 12. On the one hand, the system 3 communicates with the source of demand (SDN controller, SDN orchestrator or other information system) 4, and communicates with the transmission network on the other hand, and needs the virtual circuit service demanded by the source 4 (either newly added, modified, deleted). The virtual circuit or the like is converted into a command that the device manufacturer transmits the network management system 1 or the transmission device 12 can accept, and then sends the command to the north interface 11 of the device network management system 1 or sends the command to the transmission device 12 The interface changes the configuration of the devices in the transport network to meet the virtual circuit service requirements. In this embodiment, the command sent by the system 3 may be (but is not limited to) an instruction conforming to the MTNM TMF 814 standard, an instruction compatible with the OpenFlow protocol, or an instruction defined by the device vendor, or other Instructions provided by NBI, or instructions acceptable to the transmission device.

Please refer to FIG. 4. FIG. 4 is a schematic diagram of a network system according to an embodiment of the present invention. As shown in FIG. 4, the system 3 (hereinafter referred to as system 3) that maps transmission network resources in a software-defined network is applicable to the foregoing second network (that is, by one or more There is no network consisting of the equipment network management system and the northbound interface transmission equipment). In this embodiment, since there is no equipment vendor network management system and northbound interface, system 3 must communicate directly or indirectly with transmission device 12. In this embodiment, the command sent by the system 3 may be (but is not limited to) an instruction conforming to the OpenFlow protocol or another instruction supported by the transmission device 12.

Please refer to FIG. 5. FIG. 5 is a schematic diagram of a network system according to an embodiment of the present invention. As shown in FIG. 5, the system 3 (hereinafter referred to as system 3) that maps transmission network resources in a software-defined network is applicable to the above-mentioned third network (that is, by one or more of the above). A hybrid network of the first and second networks). As shown in FIG. 5, the system 3 can aggregate the information of the transmission network A and the transmission network B and describe them in the same manner, and combine them when necessary, so the system 3 can support the above two networks (for example, 3 and the network shown in Figure 4).

Please refer to FIG. 6. FIG. 6 is a schematic diagram of a network system according to an embodiment of the present invention. As shown in FIG. 6, it describes a configuration manner of a carrier's transmission network. The system 3 for mapping transmission network resources in a software-defined network in this embodiment can be applied to a plurality of transmission networks of different technology types. The path is, for example, an NGSDH transmission network 21, a PTN transmission network 22, a ROADM transmission network 23, an OTN transmission network 24, and an access device 27 and an access device 28. The transmission device 27, the access device 28, and each of the NGSDH transmission network 21, the PTN transmission network 22, the ROADM transmission network 23, and the OTN transmission network 24 may each include two ( Or more than two ports, such as Port1 and Port2. Therefore, the access device 27, the access device 28, and the NGSDH transmission network 21, the PTN transmission network 22, the ROADM transmission network 23, and the OTN transmission network 24 all have physical connections, and the NGSDH transmission network 21 and PTN. The transport network 22, the ROADM transport network 23, and the OTN transport network 24 all have virtual paths for providing services.

Please refer to FIG. 7. FIG. 7 is a demand table, a mapping relationship table, and an available path table according to an embodiment of the present invention. As shown in FIG. 7, it describes possible service requirements and path selection conditions for satisfying the service requirements in the above transmission network, and a system for mapping transmission network resources in a software-defined network by using the present invention and The results presented by one of the mapping mechanisms used by the method are presented here in three tables with mapping relationships:

(1) Table 1 "Requirements Table" can be used to describe the demand path, which includes the first demand endpoint, the second demand endpoint, and the demand rate. For example, the requirement S1 is required to be connected from the port 2 of the access device A1 to the port 1 of the access device A2, and the rate is 100 Mbps.

(2) Table 2 "Mapping Relationship Table" can be used to describe the mapping relationship between the access device endpoint and the docked transport device endpoint. For example, Port 2 of the access device A1 is Port1 corresponding to the transmission device NE1 in the NGSDH transmission network, and is currently being used to satisfy the demand path S1.

(3) Table 3 "Available Path Table" can be used to describe the path in the transport network that has been established for scheduling. For example, P1 is a path from Port 1 of the transmission device NE1 in the NGSDH network to Port 2 of the transmission device NE3 at a rate of 100 Mbps, which is currently being used to satisfy the demand path S1.

The above table may be used by the system 3 for mapping the transmission network resources in the software-defined network according to the embodiment of the present invention, periodically through the NBI or other means, from the device network management device, the transmission device, the access device or the transmission network of the transmission network. Obtained from other sources and used after consolidation.

In an embodiment, when the correspondence between the access device endpoint and the transport device endpoint is relatively simple, the access device endpoint information in the Table 2 "Mapping Relationship Table" may be merged into Table 3 "Available. Path table."

Please refer to FIG. 8. FIG. 8 is a flowchart of a method for mapping transmission network resources in a software-defined network according to an embodiment of the present invention. The method for mapping transmission network resources in a software-defined network is applicable to the system 3 for mapping transmission network resources in a software-defined network in the above embodiment. The method is as follows:

In step S01, the flow starts.

In step S02, information of the path requirement (S1) is obtained from the service path request. In other words, the first demand endpoint, the second demand endpoint, and the demand rate are obtained from the service path requirements. In this step, the service path requirements can be stored in the “requirements table” in Table 1, and the system 3 can obtain the information of the path requirements (S1) from the “requirements table” in the table.

In step S03, the mapping relationship between the access device endpoint and the transmission device endpoint that meets the service path requirement is queried from the mapping relationship table. In an embodiment, the system 3 can find two transmission device endpoints in the table 2 "mapping relationship table" that meet the following conditions: (a) the endpoints of the access device and the endpoints of the requirement (S1) Endpoint 2 is the same. (b) The network type is the same as the network type of demand (S1). (c) The rate is the same as the demand (S1). (d) The status is not "in use".

In step S04, it is determined whether an endpoint that meets the condition is found. If no matching endpoint is found, then step S05 is reached. If there is a matching endpoint found, then step S07 is reached.

In step S05, an attempt is made to establish a new endpoint mapping relationship. In this step, automatic or manual routing changes, card swapping, plugging and unplugging, etc. may be required.

In step S06, it is determined whether a new endpoint mapping relationship is successfully established. If it is successfully established, it proceeds to step S07. If the establishment fails, the process proceeds to step S08, and the process ends.

In step S07, the service is provided by the qualified endpoint. In this step, System 3 can note the status of the endpoint as "in use."

In step S09, the available paths of the conditions are queried from the available path table, such as the available paths that conform to the mapping relationship and the service path requirements. For example, System 3 can look for a transmission path that satisfies the following conditions in Table 3 "Available Paths": (a) Endpoint 1, Endpoint 2, and the endpoints found in the previous step are the same. (b) The network type is the same as the one found in the previous step. (c) The rate is the same as the endpoint found in the previous step. (d) The status is not "in use".

In step S10, it is determined whether a path that meets the condition is found. If no matching path is found, the process proceeds to step S11. Otherwise, the process proceeds to step S13.

In step S11, an attempt is made to establish a new path.

In step S12, it is determined whether a new path is successfully established. If the new path is successfully established, the process proceeds to step S13. Otherwise, the process proceeds to step S08, and the flow ends.

In step S13, the service is provided with the path that meets the condition.

In step S14, the status of the path providing the service is described as "in use".

Incidentally, when the correspondence between the access device endpoint and the transport device endpoint is relatively simple, or for other reasons, the access device endpoint information in the Table 2 "Mapping Relationship Table" is merged into Table 3" When the path table is available, steps S03 to S07 can be omitted, and the available paths that meet the conditions can be directly searched in Table 3 "Available Path Table".

Please refer to FIG. 9. FIG. 9 is a block diagram of a system for mapping transmission network resources in a software-defined network according to an embodiment of the present invention. As shown in FIG. 9, the system 3 for mapping transmission network resources in a software-defined network may include: a requirement management module 31, an available path management module 32, and an access and transmission device endpoint mapping relationship management module 33. The mapping mechanism uses the module 34, the device provider transmission network management interface module 35, and the transmission device interface module 36. The function of each module will be described separately below.

The requirements management module 31 can be used to store and maintain the service path requirements that the system needs to provide, and is usually stored in an associated database or other digital manner, and may periodically query external requirements or provide an interface to input requirements automatically or manually.

The available path management module 32 can be used to store and maintain the available path level transmission network resources, usually stored in an associated database or other digital manners, and may periodically query the available paths of each transmission network via the interface module. Resources, or provide an interface to enter available path resources either automatically or manually. When the mapping mechanism of the present invention is applied, a new path may be established at the time of operation to meet the service requirement due to the lack of available paths, and the new path established at this time is also stored in the available path management module.

The access and transfer device endpoint mapping relationship management module 33 can be used to store and maintain the mapping relationship between the access device endpoint and the transport device endpoint, and is usually stored in an associated database or other digital manner, and may be periodically accessed. The interface module queries the endpoint mapping relationship between each transport network and the access device, or provides an interface to input the endpoint mapping relationship automatically or manually. When using the mapping mechanism of the present invention, a new endpoint mapping relationship may be established because the available endpoints are not found, to meet the service requirements, and the new mapping relationship established at this time also stores the access and transmission device. Endpoint mapping relationship management module.

The mapping mechanism application module 34 can be used to perform the mapping of the transmission network resources in the software-defined network according to the information of the available path management module and the access and transmission device endpoint mapping relationship management module. The method is to meet the service requirements in the demand management module by using the device provider to transmit the network management interface module 35 and the transmission device interface module.

The device network transmission network management module 35 can be used to obtain information or issue instructions through the device network management system. For the network management NBI of different equipment vendors or the network management NBI of different transmission network technologies (eg, NGSDH, NGSDH, PTN, ROADM, OTN), the equipment provider transmission network management interface module 35 can be respectively transmitted in an appropriate manner. Standard interface or other means to exchange information through the NBI. The information about the device and the entity link information transmitted by each device vendor will be stored in the device network transmission network management module 35. When querying the available path, issuing the command, and updating the mapping relationship, the related device and entity link information will be referred to first. Planning and execution.

The transmission device interface module 36 can be used to obtain information from each transmission network device or to issue an instruction. For devices of different equipment vendors, or devices of different transmission network technologies (eg, NGSDH, NGSDH, PTN, ROADM, OTN), the transmission device interface module 36 can be respectively passed through a standard interface or Other ways to exchange information. Since the device and entity link information of each device vendor is stored in this module, when querying the available path, issuing the command, and updating the mapping relationship, the related device and entity link/segment information will be referred to before planning and carried out.

Accordingly, by using the system and method for mapping transmission network resources in a software-defined network as shown in the embodiments of the present invention, the resources of these transmission networks can be properly utilized in the SDN due to the old equipment and the new The purchased SDN transmission equipment can provide services together, which not only improves the flexibility of application, but also makes the previous investment not wasted. If the method and system of the present invention are not used, when the transmission network evolves to SDN, the existing transmission equipment may be eliminated and completely used by the newly purchased SDN transmission equipment, which not only wastes the investment in the equipment in the past. It also reduces the flexibility of application.

To sum up, this case is not only innovative in terms of technical thinking, but also has many of the above-mentioned functions that are not in the traditional methods of the past. It has fully complied with the statutory invention patent requirements of novelty and progressiveness, and applied for it according to law. Approved this invention patent application, in order to invent invention, to the sense of virtue.

Claims (9)

A method for mapping a transport network resource in a software-defined network, comprising: receiving a service path requirement, and obtaining a first demand endpoint, a second demand endpoint, and a demand rate from the service path requirement Querying a mapping relationship between the device endpoint and a transmission device endpoint in response to one of the service path requirements; querying from the available path table that the mapping relationship and the service path requirement are available a path, and providing the service required by the service path requirement by the available path; and if the mapping relationship does not meet the mapping requirement of the service path, the mapping relationship is established in the mapping relationship table. The method for mapping a transmission network resource in a software-defined network, as described in claim 1, wherein the mapping relationship table includes an in-use field, an access device endpoint field, and a transmission device. An endpoint field, a network type field, and a rate field, wherein the step of querying the mapping relationship between the access device endpoint and the transmission device endpoint that meets the service path requirement from the mapping relationship table The method includes: querying, according to the access device endpoint field, the transmission device endpoint field, and the rate field, the access device corresponding to the first demand endpoint, the second demand endpoint, and the demand rate The endpoint is the endpoint of the transport device. A method for mapping a transport network resource in a software-defined network as described in claim 1, wherein the access device endpoint and the in-use field of the transport device endpoint are marked as in use. A method for mapping transport network resources in a software-defined network, comprising: Receiving a service path requirement, and obtaining a first demand endpoint, a second demand endpoint, and a demand rate from the service path requirement; querying one of the service path requirements from a mapping relationship table to access the device end a mapping relationship between a point and a transmission device endpoint; querying an available path that meets the mapping relationship and the service path requirement from an available path table, and providing the service required by the service path requirement by the available path; The available path table queries the available path that does not meet the mapping relationship and the service path requirement, and the available path is established in the available path table. A system for mapping transmission network resources in a software-defined network, comprising: a demand management module for storing and maintaining a service path requirement; and an available path management module for storing and maintaining an available path table; An access and mapping device endpoint mapping relationship management module stores and maintains a mapping relationship table; and a mapping mechanism application module, which is configured to query one of the service path requirements from the mapping relationship table to access the device end Pointing a mapping relationship with a transport device endpoint, and querying from the available path table an available path that meets the mapping relationship and the service path requirement, and provides the service required by the service path requirement by the available path; If the mapping relationship table does not meet the mapping relationship of the service path requirement that is queried by the mapping mechanism, the access and transmission device endpoint mapping relationship management module establishes the mapping relationship in the mapping relationship table. A system for mapping transmission network resources in a software-defined network, as described in claim 5, wherein the service path requirements include a first demand endpoint, a second demand endpoint, and a demand rate. The system for mapping transmission network resources in a software-defined network, as described in claim 5, wherein the mapping relationship table includes an in-use field, an access device endpoint field, and a transmission device. Endpoint field, a network type field, and a rate field. The system for mapping transmission network resources in a software-defined network, as described in claim 5, wherein the available path table includes an in-use field, a network type field, and a first end. A point field, a second endpoint field, a path field, and a rate field. The system for mapping transmission network resources in a software-defined network, as described in claim 5, further comprising a device network transmission network management module and a transmission device interface module, wherein the device transmits The network management interface module communicates with a device network management system, and the transmission device interface module communicates with a transmission network device.