Pipeline configuration method and device, equipment, storage medium

Abstract

This application provides a pipeline configuration method, apparatus, device, and storage medium; wherein, the method includes: determining at least the following routing OTN network elements of the edge device based on the location of the edge device requesting the service and the location of the corresponding target service gateway: a first network element connected to the edge device, a second network element connected to the target service gateway, and an aggregation network element; determining the available shared pipeline corresponding to the regional network where the edge device is located; configuring a dedicated pipeline for the edge device from the first network element to the aggregation network element, and mapping the dedicated pipeline to the shared pipeline to form a first target pipeline; configuring a device label for the edge device on the first network element, the device label uniquely identifying the edge device within the regional network; thereby reducing the number of ports of the OTN network elements connected to the service gateway.

Description

Technical Field

[0001] This application relates to optical communication technology, including but not limited to pipe configuration methods and apparatus, equipment, and storage media. Background Technology

[0002] Currently, users' cloud access services are typically carried using Internet Protocol (IP) networks. Some users require operators to provide low-latency, high-reliability cloud access services. However, router networks have higher latency and poorer isolation compared to Optical Transport Networks (OTN), thus failing to meet the requirements for low latency and high reliability. Therefore, OTN networks are needed to provide cloud access services for high-level users.

[0003] However, as the number of users increases, the number of ports of OTN network elements connected to the service gateway also increases in the OTN network. Summary of the Invention

[0004] In view of this, the pipeline configuration method, apparatus, equipment, and storage medium provided in this application can reduce the number of interfaces of OTN network elements connected to the service gateway while supporting cloud access services.

[0005] According to one aspect of the embodiments of this application, a pipeline configuration method is provided, comprising: determining a routing OTN network element for the edge device based on the location of an edge device requesting a service and the location of a target service gateway corresponding to the service, wherein the routing OTN network element includes at least an aggregation network element, a first network element connected to the edge device, and a second network element connected to the target service gateway; determining an available shared pipeline corresponding to the regional network where the edge device is located, wherein one end of the shared pipeline is connected to the aggregation network element and the other end is connected to the second network element; configuring a dedicated pipeline for the edge device from the first network element to the aggregation network element, and mapping the dedicated pipeline to the shared pipeline to form a first target pipeline; the first target pipeline is used to transmit service packets sent by the edge device sequentially through the first network element, the aggregation network element, and the second network element to the target service gateway; configuring a device tag for the edge device for the first network element, so that the first network element encapsulates the device tag into the service packet and transmits it to the target service gateway through the first target pipeline, thereby the target service gateway identifies the edge device based on the device tag; wherein the device tag uniquely identifies the edge device within the regional network.

[0006] The pipeline configuration device provided in this application includes: a route determination module, configured to determine the routing OTN network element of the edge device based on the location of the edge device requesting the service and the location of the target service gateway corresponding to the service, wherein the routing OTN network element includes at least: an aggregation network element, a first network element connected to the edge device, and a second network element connected to the target service gateway; a pipeline determination module, configured to determine the available shared pipeline corresponding to the regional network where the edge device is located, wherein one end of the shared pipeline is connected to the aggregation network element and the other end is connected to the second network element; and a pipeline configuration module, configured to configure the edge device from the first network element to the aggregation network element. A dedicated pipeline; a pipeline mapping module, used to map the dedicated pipeline to the shared pipeline to form a first target pipeline; the first target pipeline is used to transmit the service packets sent by the edge device sequentially through the first network element, the aggregation network element, and the second network element to the target service gateway; a tag configuration module, used to configure a device tag for the edge device on the first network element, so that the first network element encapsulates the device tag into the service packet and transmits it to the target service gateway through the first target pipeline, thereby the target service gateway identifies the edge device based on the device tag; wherein, the device tag uniquely identifies the edge device within the regional network.

[0007] The electronic device provided in this application includes a memory and a processor. The memory stores a computer program that can run on the processor. When the processor executes the program, it implements the method described in this application.

[0008] The computer-readable storage medium provided in this application embodiment stores a computer program thereon, which, when executed by a processor, implements the method described in this application embodiment.

[0009] In this embodiment, the dedicated pipes of edge devices are aggregated into a shared pipe at the aggregation network element, thereby forming a first target pipe from the first network element to the second network element, which is used to transmit interactive data between the corresponding edge devices and the server connected to the target service gateway. Thus, since the transmission pipe of the edge devices between the aggregation network element and the second network element is not a dedicated pipe for that device, but a shared pipe for multiple edge devices, it can save the number of ports of the second network element, thereby saving hardware costs. On the other hand, it can improve the resource utilization of the shared pipe.

[0010] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not limit this application. Attached Figure Description

[0011] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the specification, serve to explain the technical solutions of this application. Obviously, the drawings described below are merely some embodiments of this application, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort.

[0012] The flowcharts shown in the accompanying drawings are merely illustrative and do not necessarily include all content and operations / steps, nor do they necessarily have to be performed in the described order. For example, some operations / steps can be broken down, while others can be combined or partially combined; therefore, the actual execution order may change depending on the specific circumstances.

[0013] Figure 1 This is a schematic diagram of a network architecture that may be applicable to embodiments of this application;

[0014] Figure 2 This is a schematic diagram of another network architecture that may be applicable to the embodiments of this application;

[0015] Figure 3 A schematic diagram illustrating the implementation process of a pipeline configuration method provided in this application embodiment;

[0016] Figure 4 Example schematic diagrams of converged network elements, dedicated pipes, and shared pipes provided in the embodiments of this application;

[0017] Figure 5 This is a schematic diagram illustrating examples of aggregation network elements and local area networks provided in embodiments of this application.

[0018] Figure 6 This is a schematic diagram of an end-to-end OTN network;

[0019] Figure 7 A schematic diagram illustrating the implementation flow of another pipeline configuration method provided in an embodiment of this application;

[0020] Figure 8 A schematic diagram of the networking scheme of the OTN network provided in the embodiments of this application;

[0021] Figure 9 A schematic diagram illustrating the implementation process of another pipeline configuration method provided in this application embodiment;

[0022] Figure 10 A schematic diagram illustrating the implementation process of another pipeline configuration method provided in this application embodiment;

[0023] Figure 11 A schematic diagram of an OTN network provided in an embodiment of this application;

[0024] Figure 12This is a schematic diagram of the pipe configuration device according to an embodiment of this application;

[0025] Figure 13 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0026] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the specific technical solutions of this application will be further described in detail below with reference to the accompanying drawings of the embodiments of this application. The following embodiments are used to illustrate this application, but are not intended to limit the scope of this application.

[0027] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of this application only and is not intended to limit this application.

[0028] In the following description, references are made to “some embodiments,” which describe a subset of all possible embodiments. However, it is understood that “some embodiments” may be the same subset or different subsets of all possible embodiments and may be combined with each other without conflict.

[0029] The network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. Those skilled in the art will understand that, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0030] Figure 1 This paper illustrates a network architecture that may be applicable to embodiments of this application. The figure shows some network elements, such as... Figure 1 As shown, the network architecture provided in this embodiment includes: a Customer Edge (CE) 101, a user-side OTN network element 102, a metropolitan area network-side OTN network element 103, a backbone network-side OTN network element 104, a cloud-side OTN network element 105, and a service gateway (GW) 106; wherein, the CE 101 can be connected to the OTN network element 102 through a Gigabit Ethernet (GE) interface, and the OTN network element 105 can also be connected to the GW 106 through a GE interface.

[0031] CE 101 outputs service messages (such as service requests) to network element 102. Network element 102 forwards the message to the backbone network element via the OTN network element on the metropolitan area network side. The backbone network OTN network element then forwards the service message to the cloud-side OTN network element 105, which transmits it to GW 106. GW 106 then sends the service message to the server providing the corresponding cloud access service, so that the server can return the corresponding service data to the CE 101 based on the received service message.

[0032] It should be noted that, for the sake of brevity, Figure 1 The different CEs shown are all labeled 101, the different user-side OTN network elements are all labeled 102, the different OTN network elements on the metropolitan area network side are all labeled 103, and the different OTN network elements on the backbone network side are all labeled 104.

[0033] In some embodiments, such as Figure 2 As shown, the network architecture that may be applicable to the embodiments of this application also includes an OTN controller 201, and some network elements are shown in the figure. The OTN controller 201 plans the device tags used to identify edge devices and configures the forwarding scheme for service packets output by the edge devices, etc. The following uses... Figure 2 The network architecture shown illustrates the technical solutions of the embodiments of this application, but does not limit the corresponding steps to be implemented by the OTN controller. That is to say, the corresponding functions of the OTN controller can also be implemented by a certain OTN network element, so that there is no need to deploy a separate OTN controller.

[0034] Figure 3 This is a schematic diagram illustrating the implementation process of a pipeline configuration method provided in an embodiment of this application, such as... Figure 3 As shown, the method includes steps 301 to 305:

[0035] Step 301: The OTN controller determines the routing OTN element of the edge device based on the location of the edge device requesting the service and the location of the target service gateway corresponding to the service. The routing OTN element includes at least: a convergence network element, a first network element connected to the edge device, and a second network element connected to the target service gateway.

[0036] In some embodiments, the location of the edge device can be port information connected to the first network element, and the location of the target service gateway can be port information on the target service gateway used to forward service data / service packets of the edge device. The edge device can send a service request to the first network element connected to it. The first network element sends the port information connected to the edge device and the service request to the OTN controller. The OTN controller queries the target service gateway corresponding to the service type and the gateway port information used to forward the service data / service packets of the edge device based on the service type requested in the service request and the port information.

[0037] Understandably, an OTN routing element refers to an OTN network element used to forward data, that is, an OTN device.

[0038] Step 302: The OTN controller determines the available shared pipe corresponding to the regional network where the edge device is located. One end of the shared pipe is connected to the aggregation network element, and the other end is connected to the second network element.

[0039] Step 303: The OTN controller configures a dedicated pipeline from the first network element to the edge device of the aggregation network element.

[0040] It should be noted that in this application, the execution order of steps 302 and 303 is not limited. They can be executed in parallel, or steps 302 can be executed first and then steps 303 can be executed, or steps 303 can be executed first and then steps 302 can be executed.

[0041] In this application, the coverage area of ​​the regional network is not limited; it can be a metropolitan area network (MAN), a portion of a MAN, a part of the backbone network and the MAN, etc. In short, the network scope of the regional network can be any pre-defined area. Correspondingly, the aggregation network element is related to the coverage area of ​​the regional network. For example, such as... Figure 4 As shown, the edge device mentioned in step 301 is CE 401, and its local area network is a metropolitan area network 402. Therefore, the aggregation network element is the backbone OTN network element 403. For example, Figure 5 As shown, the edge device mentioned in step 301 is CE 501, and the local area network it is in is part of network 503 in metropolitan area network 502 (such as county area network), so the aggregation network element is OTN network element 504.

[0042] A shared pipeline is, in contrast to a dedicated point-to-point pipeline. For example, such as... Figure 4As shown, pipe 404 from point A to point B is a dedicated pipe. One end of pipe 404 is connected to the user-side OTN network element 405, and the other end is connected to the aggregation network element 406. Pipe 407 from point B to point C is a backbone pipe, and its sub-pipes are shared pipes. One end of pipe 407 is connected to the aggregation network element 406, and the other end is connected to the cloud-side OTN network element 408.

[0043] As can be seen, a shared pipeline is not a dedicated pipeline for a single edge device (also known as a private pipeline), but rather a shared pipeline that can be used by multiple edge devices (i.e., a common pipeline). In some embodiments, the bandwidth of the dedicated pipeline is less than the bandwidth of the backbone pipeline; that is, the dedicated pipeline is a small-granularity pipeline, while the backbone pipeline is a large-granularity pipeline. For example, the dedicated pipeline is Optical Channel Data Unit (ODU) 0, and the backbone pipeline is ODU2 or ODU4, etc.

[0044] Step 304: The OTN controller maps the dedicated pipe to the shared pipe to form a first target pipe; wherein, the first target pipe is used to transmit the service packets sent by the edge device to the target service gateway in sequence through the first network element, the aggregation network element and the second network element;

[0045] Step 305: The OTN controller configures the device tag of the edge device for the first network element, so that the first network element encapsulates the device tag into the service message and transmits it to the target service gateway through the first target pipe, thereby the target service gateway identifies the edge device based on the device tag; wherein, the device tag uniquely identifies the edge device within the local area network.

[0046] In this application, the execution order of step 305 is not limited. It can be executed before or after any of steps 302 to 304, or it can be executed in parallel with any of steps 302 to 304.

[0047] After receiving the service message sent by the edge device, the first network element encapsulates the device tag configured for it in the service message from the edge device, and then maps the service message carrying the device tag to the first target pipeline.

[0048] In some embodiments, such as Figure 6As shown, the OTN system provides end-to-end leased lines for users, meaning that edge devices and cloud-side service gateways (GWs) connect to OTN network elements via GE interfaces. OTN provides these point-to-point leased lines. If K edge devices connect to the same service gateway, the OTN network element connected to the service gateway needs to provide K ports, with each edge device occupying one port. The service gateway distinguishes edge devices by port number; this requires a significant amount of port resources.

[0049] In this embodiment, the dedicated pipes of edge devices are aggregated into a shared pipe at the aggregation network element, thereby forming a first target pipe from the first network element to the second network element, which is used to transmit interactive data between the corresponding edge devices and the server connected to the target service gateway. Thus, since the transmission pipe of the edge devices between the aggregation network element and the second network element is not a dedicated pipe for that device, but a shared pipe for multiple edge devices, it can save the number of ports of the second network element, thereby saving hardware costs. On the other hand, it can improve the resource utilization of the shared pipe.

[0050] Understandably, when the number of edge devices is large, situations may arise such as insufficient device tags or device tag conflicts. Therefore, in this embodiment, it is necessary to plan device tags and transmission channels through the OTN controller. After a service packet enters the OTN network, the OTN controller can perform scheduling within the OTN network based on the planned device tags and transmission channels.

[0051] In some embodiments, the OTN controller maintains a first mapping table between regional networks and backbone pipelines; wherein, edge devices under the same regional network are bound to one or more backbone pipelines; thus, the OTN controller can determine whether there are available sub-pipes in the backbone pipelines corresponding to the regional network where the edge device requesting service is located by querying the first mapping table; if so, the available sub-pipes are used as available shared pipelines.

[0052] In some embodiments, the OTN controller configures and maintains a second mapping table between configured device tags and regional networks; wherein the configured device tags under the same regional network are different and are used to uniquely identify the corresponding edge devices within the same regional network; in this way, the OTN controller can configure the device tag for the requesting service to the first network element according to the usage of device tags in the regional network where the edge device (referring to the edge device requesting service as described in step 101) is located, as recorded in the second mapping table.

[0053] It should be noted that the first mapping table is used to record the mapping relationship between the regional network and the backbone pipeline, as well as the information on the available sub-pipelines in the backbone pipeline. Furthermore, the first mapping table can record the status (including available or unavailable) of the sub-pipelines included in the backbone pipeline; the second mapping table is used to record the mapping relationship between the regional network and device tags, that is, which device tags are currently configured for each regional network.

[0054] Furthermore, in some embodiments, the device label is an SVLAN label. The planning scheme includes two aspects: (1) As shown in Table 1, which is an example of the first mapping table, the ODU pipelines of the backbone network are divided based on the metropolitan area network. User services under the same metropolitan area network are bound to one / a group of ODU pipelines (ODU2 or ODU4). At the same time, each ODU pipeline corresponds to a UNI interface of a cloud-side OTN network element; (2) As shown in Table 2, which is an example of the second mapping table, in one / a group of ODU pipelines of the backbone network, each CE device is assigned a unique SVLAN label. The SVLAN labels corresponding to different CEs under the same / group of ports cannot be repeated.

[0055] Table 1

[0056]

[0057] Table 2

[0058]

[0059] In some embodiments, the OTN controller maintains a third mapping table corresponding to the second network element. The third mapping table includes a mapping relationship between each regional network connected to the second network element and its corresponding configured device tag, as well as one or more shared pipes and client-side ports bound to it. The client-side port is a port on the OTN network element connected to the service gateway. The OTN controller sends the third mapping table to the second network element so that, after receiving the service packet, the second network element can look up the corresponding target client-side port in the third mapping table based on the shared pipe and regional network from which the service packet was output, and the new device tag carried by the service packet, thereby outputting the service packet from the target client-side port to the target service gateway.

[0060] The third mapping table, such as Table 3, records the mapping relationship between the line-side ODU pipe ID, metropolitan area network ID, SVLAN ID, and customer-side port ID. The second network element can forward service packets carrying SVLAN tags to the corresponding ODU pipe based on this mapping table.

[0061] Table 3

[0062]

[0063] Of course, the OTN controller not only maintains the third mapping table corresponding to the second network element, but also maintains the third mapping table corresponding to other OTN network elements connected to the service gateway.

[0064] This application embodiment further provides a pipeline configuration method. Figure 7 This is a schematic diagram illustrating the implementation flow of another pipeline configuration method provided in an embodiment of this application, such as... Figure 7 As shown, the method includes steps 701 to 710:

[0065] Step 701: The OTN controller queries the first network element connected to the edge device based on the location of the edge device requesting the service.

[0066] In some embodiments, the OTN controller can query a maintained list of first network elements connected to the edge device based on the port information of the edge device; wherein the list records the mapping relationship between the port information of the edge device and the OTN network elements on the edge side.

[0067] Step 702: The OTN controller queries the second network element connected to the target service gateway based on the location of the target service gateway.

[0068] In some embodiments, the OTN controller can query a maintained list of second network elements connected to the target service gateway based on the port information of the target service gateway; wherein the list records the mapping relationship between the port information of the service gateway and the OTN network elements on the gateway side.

[0069] Step 703: The OTN controller queries the aggregation network element connected between the first network element and the second network element based on the location of the first network element and the location of the second network element.

[0070] In some embodiments, the OTN controller can query the regional network connected to the first network element based on the location of the first network element, query the backbone network connected to the second network element based on the location of the second network element, and then query the network element that connects the regional network to the backbone network. This network element is the aggregation network element.

[0071] Step 704: The OTN controller configures a dedicated pipeline from the first network element to the edge device of the aggregation network element.

[0072] For example, the OTN controller configures the ODU cross to form this dedicated pipeline.

[0073] Step 705: The OTN controller queries the first mapping table to determine whether there is an available sub-pipe in the backbone pipeline corresponding to the local area network where the edge device is located; if so, proceed to step 706; otherwise, proceed to step 707.

[0074] One end of the backbone pipeline is connected to the aggregation network element, and the other end is connected to the second network element;

[0075] In step 706, the OTN controller designates any one of the available sub-pipes as an available shared pipe and maps the private pipe to the available shared pipe to form a first target pipe, and then proceeds to step 710.

[0076] The first target pipeline is used to transmit the service messages sent by the edge device to the target service gateway in sequence through the first network element, the aggregation network element and the second network element.

[0077] Understandably, in this embodiment of the application, the OTN controller does not directly create new backbone pipes, but first queries the first mapping table to determine whether there are available sub-pipes in the existing backbone pipes. If so, it directly maps the dedicated pipe to one of the available sub-pipes. In this way, the complexity of pipe configuration is reduced and the overall transmission efficiency of service packets is improved.

[0078] Step 707: The OTN controller configures a new backbone pipeline, one end of which is connected to the aggregation network element and the other end is connected to the second network element.

[0079] Step 708: The OTN controller maps the dedicated pipeline to any sub-pipeline in the new backbone pipeline to form a second target pipeline;

[0080] The second target pipeline is used to transmit the service messages sent by the edge device to the target service gateway in sequence through the first network element, the aggregation network element and the second network element.

[0081] In this embodiment, if there are no available sub-pipes in the currently created backbone pipeline, the OTN controller configures a new backbone pipeline and then maps the special pipeline to any sub-pipe in the new backbone pipeline; thereby ensuring that the edge device can enjoy service.

[0082] Step 709: The OTN controller adds the mapping relationship between the new backbone pipeline and the local area network where the edge device is located, as well as the information of the available sub-pipelines in the new backbone pipeline to the first mapping table;

[0083] Step 710: The OTN controller configures a device label for the edge device requesting the service on the first network element according to the device label usage information in the regional network where the edge device is located, as recorded in the second mapping table. This allows the first network element to encapsulate the device label into the service message and transmit it to the target service gateway through the first target pipe. The target service gateway then identifies the edge device based on the device label. The device label uniquely identifies the edge device within the regional network.

[0084] Understandably, the second mapping table records the usage of device tags in each regional network. When the OTN controller assigns a device tag to an edge device, it can find out the usage of device tags in the regional network where the edge device is located by querying the second mapping table. This allows it to assign a new tag to the edge device that is not repeated with any of the already configured device tags, so as to uniquely identify the edge device in its regional network.

[0085] In some embodiments, the second network element can identify the shared pipe ID of the service packets output from the line side and the device tag carried in the service packets. Based on this, it can query the third mapping table to determine the corresponding client-side port and forward the service packets to the target service gateway through the client-side port. In this way, since the target service gateway distinguishes edge devices by device tags, the number of ports of the target service gateway can be less than the number of edge devices. Service forwarding is achieved through the third mapping table, thereby saving the number of ports of the target service gateway.

[0086] In some embodiments, the regional network is a metropolitan area network (MAN), the backbone pipeline is the trunk pipeline of the backbone MAN, and the granularity of the trunk pipeline is greater than that of the dedicated pipeline.

[0087] Understandably, the regional network is a metropolitan area OTN, and the backbone pipeline is the trunk pipeline of the backbone OTN; thus, upgrading the existing network greatly reduces the implementation cost.

[0088] OTN networks are mostly used to carry high-value end-to-end leased lines. When carrying cloud services, the following problems exist: (1) In OTN networks, although the granularity of the User Network Interface (UNI) interface is diverse, the granularity of the pipeline is relatively large. Therefore, when carrying small-granular cloud services, the resource utilization rate is low; (2) If end-to-end small-granular leased lines are opened, the cloud-side OTN network element and the cloud GW need to be distinguished by ports, which requires a large amount of port resources.

[0089] Based on this, the following will describe an exemplary application of the embodiments of this application in a practical application scenario.

[0090] In this embodiment of the application, by introducing a VLAN identification and mapping scheme into the OTN, the OTN network can achieve point-to-multipoint connection, which improves the resource utilization of the metro / backbone OTN network on the one hand, and saves the port resources of the OTN network elements on the cloud GW side on the other hand.

[0091] The technical issues include:

[0092] (1) OTN network topology scheme;

[0093] (2) OTN network elements support VLAN identification and mapping;

[0094] (3) The OTN centralized management and control system supports VLAN planning and end-to-end service configuration.

[0095] Among them, regarding the networking scheme of OTN network, such as Figure 8 As shown:

[0096] Deploy user-side OTN network elements on the user side: (1) The user side uses small-granularity GE ports, for example, it is connected to the user CE equipment through a small-bandwidth UNI (Ethernet interface, such as GE interface); (2) The line side is connected to the metropolitan area OTN network elements through a gray optical network node interface (Network to Network Interface, NNI); (3) It supports adding VLAN tags.

[0097] Deploy cloud-side OTN network elements on the cloud side (this device can be deployed separately in the cloud GW data center or it can be an already deployed trunk OTN network element): (1) it is connected to the cloud GW device through a high-bandwidth UNI (Ethernet interface, such as 10GE, 100GE); (2) it is connected to the trunk OTN network element through a colored light NNI; (3) it supports VLAN number identification and forwarding.

[0098] Deploy an OTN controller to centrally manage all OTN network elements and perform end-to-end service configuration. This includes (1) planning and configuring VLAN forwarding schemes; and (2) configuring ODU and Optical Service Unit (OSU) pipelines.

[0099] Regarding the device's functions, including:

[0100] The functions of the OTN network element on the user side include: (1) supporting the addition, stripping, and identification of Ethernet service VLAN tags (i.e., an example of a device tag), with the VLAN tag configured by the controller; (2) customer-side services are accessed through the GE interface, and can be mapped and encapsulated to a specified ODU pipe based on the VLAN tag and forwarded from the line-side port.

[0101] The functions of the cloud-side OTN network element include: (1) maintaining a VLAN mapping table, including the mapping relationship between VLAN tags and ODU pipes, which is configured by the controller; (2) supporting the identification of service VLAN tags entered by the client side through the 10GE / 100GE port, and forwarding them to the corresponding ODU pipes based on the VLAN tags. The contents of the mapping table are shown in Table 4 below:

[0102] Table 4

[0103]

[0104] Regarding the service configuration scheme, the OTN controller is configured with ODU cross-connection to form an ODU channel. Simultaneously, a VLAN mapping mechanism is configured for both the user-side and cloud-side OTN network elements to achieve end-to-end connection activation. The overall process is as follows: Figure 9 As shown, the process includes the following steps 901 to 904:

[0105] Step 901: The controller determines the customer's CE location and the cloud GW location to be accessed based on the cloud access requirements.

[0106] Step 902: The controller configures the VLAN mapping table and sends it to the cloud-side OTN network element; the mapping table includes the mapping relationship between port ID, VLAN ID and pipe ID;

[0107] Step 903: The controller calculates the ODU pipeline route based on the customer-side CE connection port (obtained based on the customer CE location) and the cloud GW connection port (obtained based on the cloud GW location to be accessed);

[0108] Step 904: Configure the cross-connection of metro / backbone OTN network elements in the controller to enable ODU pipeline connection between the customer-side OTN network element (i.e., the first network element) and the cloud-side OTN network element (i.e., the second network element).

[0109] Regarding the VLAN planning scheme (optional), when the number of users is large, there may be insufficient VLANs or VLAN conflicts. In this case, VLAN / ODU planning needs to be performed through the OTN controller. After the service enters the OTN network, scheduling is performed based on VLANs in the OTN network.

[0110] The planning scheme is as follows:

[0111] (1) The ODU pipeline of the backbone network is divided based on the metropolitan area network. User services under the same metropolitan area network are bound to one or a group of ODU pipelines (ODU2 or ODU4). At the same time, each ODU pipeline corresponds to a cloud-side OTN network element UNI interface.

[0112] (2) In one or a group of ODU pipes of the trunk network, each CE device is assigned a unique SVLAN tag. The VLAN tags corresponding to different CEs under the same or group of ports cannot be repeated.

[0113] The controller uses a mapping table between the metropolitan area network and the backbone large-granularity ODU, as shown in Table 5:

[0114] Table 5

[0115]

[0116] In addition, the controller also needs to maintain a mapping table between the metropolitan area where the user's CE is located and the VLAN it uses, as shown in Table 6:

[0117] Table 6

[0118]

[0119] Business configuration process as follows Figure 10 As shown, the process includes steps 1001 to 1009:

[0120] Step 1001: The OTN controller determines the service GW location and user CE location based on the cloud access requirements.

[0121] Step 1002: The OTN controller queries the corresponding cloud-side OTN network element (i.e., the second network element) based on the location of the service GW; and queries the corresponding user-side OTN network element (i.e., the first network element) based on the location of the user CE.

[0122] Step 1003: The OTN controller queries the corresponding aggregation network element based on the user's CE location and the location of its cloud-side GW.

[0123] Step 1004: The OTN controller searches the "Metropolitan Area Network-Pipeline Mapping Table" to determine if there are available resources for the trunk ODU pipeline corresponding to the metropolitan area network; if so, proceed to step 1005; otherwise, proceed to step 1006.

[0124] Step 1005: The OTN controller creates a small-granular pipeline (i.e., an example of a dedicated pipeline) between the user-side OTN network element and the cloud-side OTN network element, and maps it to the available trunk ODU pipeline.

[0125] Step 1006: The OTN controller creates a new ODU large-granular pipeline (i.e., an example of a new backbone pipeline) on the trunk line, and creates a small-granular pipeline between the user-side OTN network element and the cloud-side OTN network element, and maps it into the newly created large-granular pipeline.

[0126] Step 1007: The OTN controller adds the newly created ODU large-particle pipeline to the "Metropolitan Area Network-Pipeline Mapping Table";

[0127] Step 1008: The OTN controller assigns VLAN tags to users based on the current VLAN tag usage in the metropolitan area network and writes them into the "User VLAN Mapping Table".

[0128] Step 1009: The OTN controller configures the user-side OTN network element and the cloud-side OTN network element according to the assigned VLAN tag so that each network element maps the service of this VLAN to the corresponding ODU pipe.

[0129] Regarding the service forwarding mechanism, the following is included:

[0130] For the upward direction:

[0131] (1) User-side OTN network element, used to filter service VLANs input from the customer-side port and forward specific VLANs to the line-side ODU pipe;

[0132] (2) Metro / backbone OTN network elements are used to forward signals input from user-side OTN network elements to cloud-side OTN network elements based on the configured ODU cross-connection.

[0133] (3) Cloud-side OTN network element, used to identify the input ODU pipe ID and service VLAN ID on the line side, and forward the service to the corresponding customer-side port according to the "VLAN mapping table";

[0134] Regarding the downward direction:

[0135] (1) Cloud-side OTN network element, used to identify customer-side port ID and service VLAN, and encapsulate services into the corresponding ODU pipes according to the VLAN mapping table;

[0136] (2) Metro / backbone OTN network elements are used to forward signals input from cloud-side OTN network elements to user-side OTN network elements based on the configured ODU cross-connection.

[0137] (3) User-side OTN network elements are used to filter input service VLANs and output services of specific VLANs from the customer-side ports.

[0138] In the embodiments of this application, such as Figure 11 As shown, compared to OTN using point-to-point leased lines, VLAN scheduling is used to map small-granularity ODU pipelines, and small-granularity pipelines are aggregated into large-granularity pipelines on the trunk line. This can significantly reduce the port occupancy of cloud-side OTN network elements when carrying user cloud services, thus saving network construction costs.

[0139] It should be noted that although the steps of the method in this application are described in a specific order in the accompanying drawings, this does not require or imply that the steps must be performed in that specific order, or that all the steps shown must be performed to achieve the desired result. Additional or alternative steps may be omitted, multiple steps may be combined into one step, and / or one step may be broken down into multiple steps; or steps from different embodiments may be combined into a new technical solution.

[0140] Based on the foregoing embodiments, this application provides a pipeline configuration device, which includes various modules and units included in each module, and can be implemented by a processor; of course, it can also be implemented by specific logic circuits; in the implementation process, the processor can be a central processing unit (CPU), microprocessor (MPU), digital signal processor (DSP) or field programmable gate array (FPGA), etc.

[0141] Figure 12 This is a schematic diagram of the pipe configuration device according to an embodiment of this application, as shown below. Figure 12 As shown, the device 120 includes:

[0142] The routing determination module 121 is used to determine the routing OTN network element of the edge device based on the location of the edge device requesting the service and the location of the target service gateway corresponding to the service. The routing OTN network element includes at least an aggregation network element, a first network element connected to the edge device, and a second network element connected to the target service gateway.

[0143] The pipeline determination module 122 is used to determine the available shared pipelines corresponding to the area network where the edge device is located, wherein one end of the shared pipeline is connected to the aggregation network element and the other end is connected to the second network element;

[0144] Pipeline configuration module 123 is used to configure the dedicated pipeline of the edge device from the first network element to the aggregation network element;

[0145] The pipeline mapping module 124 is used to map the dedicated pipeline to the shared pipeline to form a first target pipeline; the first target pipeline is used to transmit the service packets sent by the edge device to the target service gateway in sequence through the first network element, the aggregation network element and the second network element;

[0146] The tag configuration module 125 is used to configure a device tag for the edge device for the first network element, so that the first network element encapsulates the device tag into the service message and transmits it to the target service gateway through the first target pipeline, thereby the target service gateway identifies the edge device based on the device tag; wherein, the device tag uniquely identifies the edge device within the regional network.

[0147] In some embodiments, the routing determination module 121 is configured to: query a first network element connected to the edge device based on the location of the edge device; query a second network element connected to the target service gateway based on the location of the target service gateway; and query a convergence network element connected between the first network element and the second network element based on the locations of the first network element and the second network element.

[0148] In some embodiments, the pipeline configuration device further includes a maintenance module that maintains a first mapping table between the local area network and the backbone pipeline; wherein, an edge device under the same local area network is bound to one or more backbone pipelines; the first mapping table is used to record the mapping relationship between the local area network and the backbone pipeline, as well as information on available sub-pipelines included in the backbone pipeline; correspondingly, the pipeline determination module 122 is used to: query the first mapping table to determine whether there are available sub-pipelines in the backbone pipeline corresponding to the local area network where the edge device is located; if there are available sub-pipelines in the backbone pipeline, any one of the available sub-pipelines is used as an available shared pipeline.

[0149] In some embodiments, the pipeline determination module 122 is further configured to: if there are no available sub-pipes in the backbone pipeline corresponding to the regional network where the edge device is located, configure a new backbone pipeline, one end of which is connected to the aggregation network element and the other end of which is connected to the second network element; and the pipeline mapping module 124 is further configured to map the dedicated pipeline to any sub-pipe in the new backbone pipeline to form a second target pipeline; wherein the second target pipeline is used to transmit the service packets sent by the edge device to the target service gateway in sequence through the first network element, the aggregation network element and the second network element.

[0150] In some embodiments, the maintenance module is further configured to maintain a second mapping table between configured device tags and regional networks; wherein the configured device tags under the same regional network are all different and are used to uniquely identify the corresponding edge device within the same regional network; the second mapping table is used to record the mapping relationship between regional networks and device tags; correspondingly, the tag configuration module 125 is configured to configure the device tag of the edge device for the first network element according to the usage of device tags in the regional network where the edge device is located, as recorded in the second mapping table.

[0151] In some embodiments, the maintenance module is further configured to maintain at least a third mapping table corresponding to the second network element. The third mapping table includes a mapping relationship between each regional network connected to the second network element and its corresponding configured device tag, as well as one or more shared pipes and client-side ports bound to it. The client-side port is a port on an OTN network element connected to a service gateway. The pipe configuration device further includes a sending module configured to send the third mapping table to the second network element, so that after receiving the service packet, the second network element can look up the corresponding target client-side port in the third mapping table according to the shared pipe that outputs the service packet, the regional network, and the device tag carried by the service packet, thereby outputting the service packet from the target client-side port to the target service gateway.

[0152] In some embodiments, the regional network is a metropolitan area network (MAN), the backbone pipeline is the trunk pipeline of the backbone MAN, and the granularity of the trunk pipeline is greater than that of the dedicated pipeline.

[0153] The descriptions of the above device embodiments are similar to those of the above method embodiments, and have similar beneficial effects. For technical details not disclosed in the device embodiments of this application, please refer to the descriptions of the method embodiments of this application for understanding.

[0154] It should be noted that, in the embodiments of this application... Figure 12 The module division shown in the pipeline configuration device is illustrative and represents only one logical functional division; in actual implementation, other division methods may be used. Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, exist as separate physical units, or be integrated into one unit by two or more units. The integrated units can be implemented in hardware, as software functional units, or a combination of both.

[0155] It should be noted that, in the embodiments of this application, if the above-described methods are implemented as software functional modules and sold or used as independent products, they can also be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the embodiments of this application, or the parts that contribute to related technologies, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause an electronic device to execute all or part of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), magnetic disks, or optical disks. Thus, the embodiments of this application are not limited to any specific hardware and software combination.

[0156] This application provides an electronic device. Figure 13 This is a schematic diagram of the hardware entity of the electronic device according to an embodiment of this application, such as... Figure 13 As shown, the electronic device 130 includes a memory 131 and a processor 132. The memory 131 stores a computer program that can run on the processor 132. When the processor 132 executes the program, it implements the steps in the method provided in the above embodiments.

[0157] It should be noted that the memory 131 is configured to store instructions and applications executable by the processor 132, and can also cache data to be processed or already processed (e.g., image data, audio data, voice communication data and video communication data) in the various modules of the processor 132 and the electronic device 130, which can be implemented by flash memory or random access memory (RAM).

[0158] This application provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the steps of the method provided in the above embodiments.

[0159] This application provides a computer program product containing instructions that, when run on a computer, cause the computer to perform the steps in the method provided in the above-described method embodiments.

[0160] It should be noted that the descriptions of the storage medium and device embodiments above are similar to the descriptions of the method embodiments above, and have similar beneficial effects. For technical details not disclosed in the storage medium, storage medium, and device embodiments of this application, please refer to the descriptions of the method embodiments of this application for understanding.

[0161] It should be understood that the phrases "one embodiment," "an embodiment," or "some embodiments" mentioned throughout the specification mean that a specific feature, structure, or characteristic related to an embodiment is included in at least one embodiment of this application. Therefore, "in one embodiment," "in one embodiment," or "in some embodiments" appearing throughout the specification do not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. It should be understood that in the various embodiments of this application, the sequence numbers of the above-described processes do not imply a sequential order of execution; the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application. The sequence numbers of the above-described embodiments are merely for descriptive purposes and do not represent the superiority or inferiority of the embodiments. The descriptions of the various embodiments above tend to emphasize the differences between the various embodiments; their similarities or commonalities can be referred to mutually, and for the sake of brevity, they will not be repeated here.

[0162] In this article, the term "and / or" is merely a description of the relationship between related objects, indicating that there can be three kinds of relationships. For example, object A and / or object B can represent three situations: object A exists alone, object A and object B exist simultaneously, and object B exists alone.

[0163] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0164] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. The embodiments described above are merely illustrative. For example, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods, such as: multiple modules or components can be combined, or integrated into another system, or some features can be ignored or not executed. In addition, the coupling, direct coupling, or communication connection between the various components shown or discussed can be through some interfaces, and the indirect coupling or communication connection between devices or modules can be electrical, mechanical, or other forms.

[0165] The modules described above as separate components may or may not be physically separate. The components shown as modules may or may not be physical modules. They may be located in one place or distributed across multiple network units. Some or all of the modules may be selected to achieve the purpose of this embodiment according to actual needs.

[0166] In addition, each functional module in the various embodiments of this application can be integrated into one processing unit, or each module can be a separate unit, or two or more modules can be integrated into one unit; the integrated modules can be implemented in hardware or in the form of hardware plus software functional units.

[0167] Those skilled in the art will understand that all or part of the steps of the above method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, it performs the steps of the above method embodiments. The aforementioned storage medium includes various media that can store program code, such as mobile storage devices, read-only memory (ROM), magnetic disks, or optical disks.

[0168] Alternatively, if the integrated units described above are implemented as software functional modules and sold or used as independent products, they can also be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the embodiments of this application, or the parts that contribute to related technologies, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause an electronic device to execute all or part of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as mobile storage devices, ROMs, magnetic disks, or optical disks.

[0169] The methods disclosed in the several method embodiments provided in this application can be arbitrarily combined without conflict to obtain new method embodiments.

[0170] The features disclosed in the several product embodiments provided in this application can be arbitrarily combined without conflict to obtain new product embodiments.

[0171] The features disclosed in the several method or device embodiments provided in this application can be arbitrarily combined without conflict to obtain new method or device embodiments.

[0172] The above description is merely an embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A pipeline configuration method, characterized in that, The method includes: Based on the location of the edge device requesting the service and the location of the target service gateway corresponding to the service, the routing optical transport network (OTN) element of the edge device is determined. The routing OTN element includes at least: a convergence network element, a first network element connected to the edge device, and a second network element connected to the target service gateway. Determine the available shared pipe corresponding to the area network where the edge device is located. One end of the shared pipe is connected to the aggregation network element, and the other end is connected to the second network element. Configure a dedicated pipeline for the edge device from the first network element to the aggregation network element, and map the dedicated pipeline to the shared pipeline to form a first target pipeline; the first target pipeline is used to transmit the service packets sent by the edge device to the target service gateway in sequence through the first network element, the aggregation network element and the second network element; The first network element is configured with a device tag for the edge device, so that the first network element encapsulates the device tag into the service message and transmits it to the target service gateway through the first target pipeline, thereby the target service gateway identifies the edge device based on the device tag; wherein, the device tag uniquely identifies the edge device within the regional network.

2. The method according to claim 1, characterized in that, The step of determining the routing OTN network element of the edge device based on the location of the edge device requesting the service and the location of the target service gateway corresponding to the service, wherein the routing OTN network element includes at least: a first network element connected to the edge device, a second network element connected to the target service gateway, and an aggregation network element, including: Based on the location of the edge device, query the first network element connected to the edge device; Based on the location of the target service gateway, query the second network element connected to the target service gateway; Based on the location of the first network element and the location of the second network element, query the aggregation network element connected between the first network element and the second network element.

3. The method according to claim 1, characterized in that, The method further includes: maintaining a first mapping table between the regional network and the backbone pipeline; wherein, edge devices under the same regional network are bound to one or more backbone pipelines; the first mapping table is used to record the mapping relationship between the regional network and the backbone pipeline, as well as information on the available sub-pipelines included in the backbone pipeline; Accordingly, determining the available shared pipeline corresponding to the local area network where the edge device is located includes: Query the first mapping table to determine whether there are available sub-pipes in the backbone pipeline corresponding to the local area network where the edge device is located; if there are available sub-pipes in the backbone pipeline, use any one of the available sub-pipes as an available shared pipeline.

4. The method according to claim 3, characterized in that, The method further includes: If there are no available sub-pipes in the backbone pipeline corresponding to the area network where the edge device is located, a new backbone pipeline is configured, with one end connected to the aggregation network element and the other end connected to the second network element; and The dedicated pipeline is mapped to any sub-pipe in the new backbone pipeline to form a second target pipeline; wherein, the second target pipeline is used to transmit the service packets sent by the edge device to the target service gateway in sequence through the first network element, the aggregation network element and the second network element.

5. The method according to claim 3, characterized in that, The method further includes: maintaining a second mapping table between configured device tags and regional networks; wherein the configured device tags under the same regional network are all different and are used to uniquely identify the corresponding edge devices within the same regional network; the second mapping table is used to record the mapping relationship between regional networks and device tags; Accordingly, configuring the device label of the edge device for the first network element includes: Based on the usage of device tags in the regional network where the edge device is located, as recorded in the second mapping table, the device tag of the edge device is configured for the first network element.

6. The method according to claim 5, characterized in that, The method further includes: At least maintain a third mapping table corresponding to the second network element. The third mapping table includes the mapping relationship between each regional network accessing the second network element and the corresponding configured device tag, as well as the mapping relationship between the corresponding one or more shared pipes and client-side ports bound to it; wherein, the client-side port is a port on the OTN network element connected to the service gateway. The third mapping table is sent to the second network element so that after receiving the service message, the second network element can look up the corresponding target client-side port in the third mapping table according to the shared pipe through which the service message was output, the regional network, and the device tag carried by the service message, and then output the service message from the target client-side port to the target service gateway.

7. The method according to any one of claims 3 to 6, characterized in that, The regional network is a metropolitan area OTN, and the backbone pipeline is the trunk pipeline of the backbone OTN. The granularity of the trunk pipeline is greater than that of the dedicated pipeline.

8. A pipe configuration device, characterized in that, include: The routing determination module is used to determine the routing optical transport network (OTN) element of the edge device based on the location of the edge device requesting the service and the location of the target service gateway corresponding to the service. The routing OTN element includes at least: a convergence network element, a first network element connected to the edge device, and a second network element connected to the target service gateway. The pipeline determination module is used to determine the available shared pipelines corresponding to the area network where the edge device is located. One end of the shared pipeline is connected to the aggregation network element, and the other end is connected to the second network element. The pipeline configuration module is used to configure the dedicated pipeline from the first network element to the edge device of the aggregation network element; The pipeline mapping module is used to map the dedicated pipeline to the shared pipeline to form a first target pipeline; the first target pipeline is used to transmit the service packets sent by the edge device to the target service gateway in sequence through the first network element, the aggregation network element and the second network element; The tag configuration module is used to configure a device tag for the edge device for the first network element, so that the first network element encapsulates the device tag into the service message and transmits it to the target service gateway through the first target pipeline, thereby the target service gateway identifies the edge device based on the device tag; wherein, the device tag uniquely identifies the edge device within the regional network.

9. An electronic device comprising a memory and a processor, the memory storing a computer program executable on the processor, characterized in that, When the processor executes the program, it implements the method according to any one of claims 1 to 7.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the method as described in any one of claims 1 to 7.

Images