WO2022063196A1 - 一种数据帧的发送方法和网络设备 - Google Patents

一种数据帧的发送方法和网络设备 Download PDF

Info

Publication number
WO2022063196A1
WO2022063196A1 PCT/CN2021/120063 CN2021120063W WO2022063196A1 WO 2022063196 A1 WO2022063196 A1 WO 2022063196A1 CN 2021120063 W CN2021120063 W CN 2021120063W WO 2022063196 A1 WO2022063196 A1 WO 2022063196A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
node
path
data frame
label stack
Prior art date
Application number
PCT/CN2021/120063
Other languages
English (en)
French (fr)
Inventor
谢刚
李�浩
林毅
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP21871565.4A priority Critical patent/EP4207794A4/en
Publication of WO2022063196A1 publication Critical patent/WO2022063196A1/zh
Priority to US18/189,401 priority patent/US20230254245A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q11/00—Selecting arrangements for multiplex systems
    • H04Q11/0001—Selecting arrangements for multiplex systems using optical switching
    • H04Q11/0062—Network aspects
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B10/00—Transmission systems employing electromagnetic waves other than radio-waves, e.g. infrared, visible or ultraviolet light, or employing corpuscular radiation, e.g. quantum communication
    • H04B10/27—Arrangements for networking
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/22—Alternate routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/50—Routing or path finding of packets in data switching networks using label swapping, e.g. multi-protocol label switch [MPLS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/72—Admission control; Resource allocation using reservation actions during connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/72—Admission control; Resource allocation using reservation actions during connection setup
    • H04L47/724—Admission control; Resource allocation using reservation actions during connection setup at intermediate nodes, e.g. resource reservation protocol [RSVP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q11/00—Selecting arrangements for multiplex systems
    • H04Q11/0001—Selecting arrangements for multiplex systems using optical switching
    • H04Q11/0062—Network aspects
    • H04Q2011/0064—Arbitration, scheduling or medium access control aspects
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q11/00—Selecting arrangements for multiplex systems
    • H04Q11/0001—Selecting arrangements for multiplex systems using optical switching
    • H04Q11/0062—Network aspects
    • H04Q2011/0077—Labelling aspects, e.g. multiprotocol label switching [MPLS], G-MPLS, MPAS

Definitions

  • the present invention relates to the technical field of optical networks, in particular to a data frame sending method and network equipment.
  • the Automatically Switched Optical Network is an optical network defined by the International Telecommunication Union (ITU) that is based on a distributed control plane and supports dynamically switched connections.
  • ASON utilizes an independent control plane to implement automatic connection management through various transport networks.
  • ASON supports dynamic allocation of network bandwidth and scheduling connections, and can effectively optimize the network according to changes in client layer information such as IP data traffic.
  • client layer information such as IP data traffic.
  • ASON can greatly reduce network construction costs, improve bandwidth utilization, and provide distributed network recovery for the same network service requirements, greatly improving network reliability.
  • ASON network has basically covered the wavelength division network such as metropolitan area and core backbone at present.
  • each ASON node obtains the information of other nodes in the whole network through the Open Shortest Path First (OSPF) protocol, including node data and link data, etc., and then uses the constraint-based shortest path first algorithm ( Constrained Shortest Path First, CSPF) calculates the end-to-end service path, and finally completes the establishment of the end-to-end service path through RSVP-TE.
  • OSPF Open Shortest Path First
  • CSPF Constrained Shortest Path First
  • RSVP-TE Resource Reservation Protocol-Traffic Engineering
  • the RSVP Path message is first encapsulated into an IP packet, and then the IP packet is mapped to the overhead bytes of the data frame.
  • Each intermediate node needs to decipher IP packets one by one, which takes a long time, occupies a lot of overhead, and slows road construction.
  • the embodiments of the present application provide a data frame sending method and network device.
  • an embodiment of the present application provides a method for sending a data frame, the method includes: a first node obtains routing label stack information of a first path, the first path is used for transmitting services, and the routing label stack information is used to indicate Each node on the first path establishes a service channel on each node on the first path; the first node inserts routing label stack information and service attribute information into the first data frame, and the service attribute information is used to indicate that each node on the first path is a service Configure resources; the first node sends the first data frame.
  • the solution provided by this application by carrying the routing label stack information and service attribute information in the flexible data frame, can quickly transmit the service routing information to each node of the service path, which is used for each node to establish a service channel and configure resources for the service. , thereby shortening the routing time, and completing the data frame sending process only through the OSU frame control signaling, without occupying too much overhead of high-order data frames, thereby improving the transmission efficiency of the network.
  • the routing label stack information includes multiple labels, and each label in the multiple labels corresponds to a channel through which each node on the first path transmits services, and the corresponding relationship is pre-configured. in each node on the first path.
  • the routing label stack information may only include a global label, and after the first node or other nodes on the first path acquire the global label, complete services according to the global label. channel establishment.
  • the service attribute information includes one or more of the following information: service identification ID, bandwidth, delay, source node identification ID, sink node identification ID, service path Attributes.
  • the service path attribute information may include working path attributes, protection path attributes, and rerouting path attributes.
  • the first data frame is a flexible optical service unit frame with a length of 192 bytes.
  • the payload area further includes the number of labels, where the number of labels is used to identify the number of nodes on the first path that receive the routing label stack information and service attribute information. Carrying the number of labels in the payload area enables each node to know the remaining number of nodes to be forwarded. When the first data frame is forwarded to the last node, it can be judged that it is not necessary to continue forwarding, thereby saving routing time.
  • the overhead area of the first data frame further includes a signaling type Type field, where the Type field is used to indicate that the first data frame is a control frame and a specific control type.
  • the signaling type Type field By reserving the signaling type Type field in the overhead area, the current first data frame can be identified as a control frame, which is used for the transmission process of the data frame. Specifically, it can include scenarios such as road construction, 1+1 protection, and rerouting, which is consistent with the transmission process.
  • the data frames of the services are distinguished to facilitate network management.
  • the Type field is used to indicate that the first data frame is a service creation control frame; or, the Type field is used to indicate that the first data frame is a service 1+1 protection Create a control frame; or, the Type field is used to indicate that the first data frame is a service rerouting control frame.
  • the Type field may also be used to indicate that the first data frame is a service deletion control frame.
  • the first data frame may only carry a service deletion control signaling identifier (Type field) and a service ID, and the routing label stack information may be selected;
  • the first data frame can be directly forwarded along with the service data flow, and it is not necessary to obtain the outbound port for forwarding according to the routing label stack information carried in the first data frame.
  • the Type field is used to instruct the first data frame to create a control frame for service 1+1 protection, which may specifically include: the Type field is used to indicate that the first data frame is Create a control frame for the primary path of the service; or, the Type field is used to instruct the first data frame to create a control frame for the backup path of the service.
  • the method before the first node acquires the routing label stack information of the first path, the method further includes: the first node receiving a request for sending a data frame; calculating the first node of the transmission service according to the routing request a path; converting the first path into the routing label stack information.
  • complex identification numbers such as subracks, boards, ports, and channels can be simplified into labels, which facilitates device acquisition and identification, and simplifies the sending process of data frames.
  • the method further includes that, according to the first label in the routing label stack information, the first node is The physical layer establishes a cross-connection for the service; and the first node configures resources for the service at the physical layer according to the service attribute information.
  • the physical layer described in this application can be understood as the data plane, and the cross-connection is established for the service at the physical layer, that is, the cross-connection is established for the service by occupying the software or hardware resources of the equipment, such as the establishment of subracks, single boards. , the cross-connection of ports.
  • the first node preconfigures the mapping relationship between the first data frame and the first optical data unit frame.
  • the sending process of the data frame can be simplified into the establishment of the cross-connection and the resource configuration, and the routing time can be shortened.
  • an embodiment of the present application provides a method for sending a data frame, including: a second node receives a first data frame, and a payload area of the first data frame carries routing label stack information and service attribute information, and routing label stack information It is used to instruct each node on the first path to establish a service channel on each node, and the service attribute information is used to instruct each node on the first path to configure resources for the service, where the first path is used to transmit services;
  • the routing label stack information and service attribute information are obtained in a data frame; the second node establishes a channel for the second node to transmit services according to the routing label stack information; and configures resources for the service according to the service attribute information.
  • the service routing information can be quickly transmitted to each node of the service path, and the routing label stack information and service attribute information of each node can establish a transmission service and configure resources for the service, thereby shortening the routing time, and completing the data frame sending process only through the first data frame control signaling, without occupying too much overhead of high-order data frames, thereby improving the transmission efficiency of the network.
  • the routing label stack information includes multiple labels, each of the multiple labels corresponds to a channel through which each node on the first path transmits services, and the corresponding relationship is preconfigured in in each node on the first path.
  • the content of packets can be reduced and the transmission efficiency can be improved.
  • the corresponding relationship between the label and the service channel completes the establishment of the cross-connection and improves the transmission speed of the data frame.
  • the service attribute information includes one or more of the following information: service identification ID, bandwidth, delay, source node identification ID, sink node identification ID, service path Attributes.
  • the first data frame is a flexible optical service unit frame
  • the length of the flexible optical service unit frame is 192 bytes.
  • the payload area further includes the number of labels, where the number of labels is used to identify the number of nodes on the first path that receive the routing label stack information and service attribute information. Carrying the number of labels in the payload area enables each node to know the remaining number of nodes to be forwarded. When the OSU really forwards to the end node, it can judge that it is not necessary to continue forwarding, thereby saving routing time.
  • the overhead area of the first data frame further includes a signaling type Type field, where the Type field is used to indicate that the first data frame is a control frame and a specific control type.
  • the signaling type Type field By reserving the signaling type Type field in the overhead area, the current first data frame can be identified as a control frame, which is used for the transmission process of the data frame. Specifically, it can include scenarios such as road construction, 1+1 protection, and rerouting, which is consistent with the transmission process.
  • the data frames of the services are distinguished to facilitate network management.
  • the Type field is used to indicate that the first data frame is a service creation control frame; or, the Type field is used to indicate that the first data frame is a service 1+1 protection Create a control frame; or, the Type field is used to indicate that the first data frame is a service rerouting control frame.
  • the Type field is used to instruct the first data frame to create a control frame for service 1+1 protection, which may specifically include: the Type field is used to indicate that the first data frame is Create a control frame for the primary path of the service; or, the Type field is used to instruct the first data frame to create a control frame for the backup path of the service.
  • the method before the first node acquires the routing label stack information of the first path, the method further includes: the first node receives a routing request of the service; path; converting the first path into the routing label stack information.
  • complex identification numbers such as subracks, boards, ports, and channels can be simplified into labels, which facilitates device acquisition and identification, and simplifies the sending process of data frames.
  • the method further includes that, according to the first label in the routing label stack information, the first node is The physical layer establishes a cross-connection for the service; and the first node configures resources for the service at the physical layer according to the service attribute information.
  • the second node obtains routing label stack information from the first data frame, including:
  • the second node obtains the second label from the first data frame by stacking, and the second label is specifically used to instruct the second node to establish a channel for transmitting the service; or, the second node obtains the second label from the The second label is obtained from the first data frame.
  • the method further includes: the second node forwards the first data frame to other nodes, and the other nodes are the second nodes downstream nodes on the first path.
  • the second node establishes a channel for the second node to transmit the service according to the routing label stack information, including: the second node is, according to the second label, at the physical level: business connection.
  • the method further includes: the second node configures a bandwidth for the service at the physical level according to the service attribute information.
  • the second node first forwards the first data frame to the downstream node, and then establishes a connection for the service at the physical level according to the second label and establishes a connection for the service at the physical level according to the second label, so that the service routing information can be transmitted to the path's router as soon as possible.
  • each node on the path can complete the establishment of cross-connection and resource configuration in parallel, thereby realizing fast routing of services.
  • the second node preconfigures the mapping relationship between the first data frame and the second optical data unit frame.
  • the sending process of the data frame can be simplified into the establishment of the cross-connection and the resource configuration, and the routing time can be shortened.
  • an embodiment of the present application provides a network device, including: a processing unit configured to obtain routing label stack information of a first path, where the first path is used to transmit services, and the routing label stack information is used to indicate that the first path is on the first path.
  • a processing unit configured to obtain routing label stack information of a first path, where the first path is used to transmit services, and the routing label stack information is used to indicate that the first path is on the first path.
  • Each node establishes a channel for transmitting services; the processing unit is further configured to insert routing label stack information and service attribute information into the first data frame of the optical service unit, and the service attribute information is used to indicate that each node on the first path is configured for the service resource; a sending unit, used for sending the first data frame.
  • the routing label stack information includes multiple labels, and each of the multiple labels corresponds to a channel through which each network device on the first path transmits the service, and the Correspondence is pre-configured in each of the network devices.
  • the service attribute information includes one or more of the following information: service identification ID, bandwidth, delay, source node identification ID, and sink node identification ID.
  • the first data frame includes a payload area, and the routing label stack information and the service attribute information are carried in the payload area.
  • the payload area further includes a label quantity field, and the label quantity is used to identify the number of nodes on the first path that receive the routing label stack information and the service attribute information. .
  • the first data frame further includes a signaling type Type field, where the Type field is used to indicate that the first data frame is a control frame and a specific control type.
  • the signaling type Type field By reserving the signaling type Type field in the overhead area, the current first data frame can be identified as a control frame, which is used for the transmission process of the data frame. Specifically, it can include scenarios such as road construction, 1+1 protection, and rerouting, which is consistent with the transmission process.
  • the data frames of the services are distinguished to facilitate network management.
  • the Type field is used to indicate that the first data frame is a service creation control frame; or, the Type field is used to indicate that the first data frame is a service 1+1 protection Create a control frame; or, the Type field is used to indicate that the first data frame is a service rerouting control frame.
  • the Type field is used to indicate that the first data frame creates a control frame for service 1+1 protection, which may specifically include: the Type field is used to indicate that the first data frame is Create a control frame for the primary path of the service; or, the Type field is used to instruct the first data frame to create a control frame for the backup path of the service.
  • the network device further includes a receiving unit, and before the processing unit acquires the routing label stack information of the first path, the receiving unit is configured to receive a data frame sending request; the processing unit, It is also used to calculate the first path of the transmission service according to the routing request; and convert the first path into routing label stack information.
  • the processing unit is further configured to establish a connection for the service at the physical level according to the first label in the routing label stack information; and , and is also used to configure resources for the service at the physical level according to the service attribute information.
  • the processing unit preconfigures the mapping relationship between the first data frame and the first optical data unit frame.
  • an embodiment of the present application provides a network device, including: a receiving unit configured to receive a first data frame, where the first data frame carries routing label stack information, and the routing label stack information is used to indicate that the first path is on the first path.
  • Each node establishes a channel for transmitting services; a processing unit is used to obtain routing label stack information and the service attribute information from the first data frame; it is also used to establish a channel for the second node to transmit services according to the routing label stack information; for configuring resources for the service according to the service attribute information.
  • the routing label stack information includes multiple labels, and each of the multiple labels corresponds to a channel through which each network device on the first path transmits the service, The correspondence is preconfigured in each of the network devices.
  • the service attribute information includes one or more of the following information: service identification ID, bandwidth, delay, source node identification ID, and sink node identification ID.
  • the first data frame is a flexible optical service unit frame, and its length is 192 bytes.
  • the payload area further includes the number of labels, where the number of labels is used to identify the number of nodes on the first path that receive the routing label stack information and the service attribute information.
  • the first data frame further includes a signaling type Type field, where the Type field is used to indicate that the first data frame is a control frame and a specific control type.
  • the signaling type Type field By reserving the signaling type Type field in the overhead area, the current first data frame can be identified as a control frame, which is used for the transmission process of the data frame. Specifically, it can include scenarios such as road construction, 1+1 protection, and rerouting, which is consistent with the transmission process.
  • the data frames of the services are distinguished to facilitate network management.
  • the Type field is used to indicate that the first data frame is a service creation control frame; or, the Type field is used to indicate that the first data frame is a service 1+1 protection Create a control frame; or, the Type field is used to indicate that the first data frame is a service rerouting control frame.
  • the Type field is used to indicate that the first data frame is a service 1+1 protection creation control frame, which may specifically include: the Type field is used to indicate that the first data frame is a service The primary path creates a control frame; or, the Type field is used to indicate that the first data frame creates a control frame for the backup path of the service.
  • the processing unit acquiring the routing label stack information from the first data frame means: the processing unit acquires the routing label stack information from the first data frame in a stack manner. Two labels, the second label is specifically used to instruct the network device to establish a channel for transmitting services; or, the processing unit obtains the second label from the first data frame in a pointer manner.
  • the network device further includes a sending unit, and after the processing unit obtains the second label from the first data frame, the sending unit is configured to: forward the first data to other network devices frame, and other network devices are downstream network devices of the network device on the first path.
  • the processing unit is specifically configured to establish a connection for the service at the physical level according to the second label.
  • the processing unit is further configured to configure bandwidth for the service at the physical level according to the service attribute information.
  • the processing unit preconfigures the mapping relationship between the first data frame and the second optical data unit frame.
  • an embodiment of the present application provides a computer program product.
  • the computer program When the computer program is executed by a computer, the computer can implement the above-mentioned first aspect and any possible implementation manner in combination with the first aspect and the second aspect, respectively. and combining with the method in any possible implementation manner of the second aspect.
  • the real-time example of the present application also provides a computer-readable storage medium, which stores a computer program or instruction, and when the program or instruction is run, it will drive the device to execute the first aspect and any possibility in combination with the first aspect.
  • a computer-readable storage medium which stores a computer program or instruction, and when the program or instruction is run, it will drive the device to execute the first aspect and any possibility in combination with the first aspect.
  • an embodiment of the present application further provides a communication system, where the communication system includes the network device and the node in the above embodiment.
  • FIG. 1 is a schematic diagram of an ASON network architecture according to an embodiment of the application.
  • FIG. 2 is a schematic diagram of an OSU frame structure according to an embodiment of the present application.
  • FIG. 3 is a schematic diagram of a method for sending a data frame
  • FIG. 4 is a schematic diagram of a node configuration of an ASON network according to an embodiment of the present application.
  • FIG. 5 is a system sequence diagram of a method for sending a data frame provided by an embodiment of the present application.
  • FIG. 6 is a schematic diagram of a signaling format of an OSU frame provided by an embodiment of the present application.
  • FIG. 7 is a schematic flowchart of obtaining a label by stacking according to an embodiment of the present application.
  • FIG. 8 is a schematic flowchart of obtaining a label by a pointer according to an embodiment of the present application.
  • FIG. 9 is a flowchart of a service routing method provided by an embodiment of the present application.
  • FIG. 10 is a flowchart of another service routing method provided by an embodiment of the present application.
  • FIG. 11 is a scene diagram in which a service routing method provided by an embodiment of the present application can be applied.
  • FIG. 12 is a scene diagram to which another service routing method provided by an embodiment of the present application can be applied.
  • FIG. 13 is a scene diagram to which another service routing method provided by an embodiment of the present application can be applied.
  • FIG. 14 is a scene diagram to which another service routing method provided by an embodiment of the present application can be applied.
  • FIG. 15 is a schematic structural diagram of a service routing apparatus provided by an embodiment of the present application.
  • FIG. 16 is a schematic structural diagram of another service routing apparatus provided by an embodiment of the present application.
  • FIG. 17 is a schematic structural diagram of another service routing apparatus provided by an embodiment of the present application.
  • node 1 node 1, node 2, node 3, and node 4 respectively.
  • the number of nodes included in the ASON may be more than 4 nodes, or the number of nodes included in the ASON may also be greater than or equal to 2.
  • interface #1 and interface #8 are the physical ports of node #1
  • interface #2 and interface #3 are the physical ports of node #2
  • interface #4 and interface #5 are the physical ports of node #3
  • interface #6 and interface #7 is the physical port of node #4.
  • an interface may also be referred to as a port, such as an ingress port, an egress port, and the like.
  • the port on the node in this application has three layers of meanings: 1) Channel, for example, the ingress port 1 - the egress port 1 means that the data enters the node from the ingress port 1, and then is sent out from the egress port 1, which represents the channel of the data 2) wavelength, the data is sent from a specific port to indicate that the data is sent out with the wavelength corresponding to the port; 3) the mapping relationship with the OTN frame, the flexible data frame needs to be mapped to the optical data unit ODUk in a certain way before sending The data is sent from a specific port, indicating that the flexible data frame carrying the data is mapped to a specific position in the payload area of the ODUk frame with a specific mapping relationship, and then sent through the ODUk frame.
  • connection between two adjacent nodes is called a link.
  • a link can be represented by a link (node-interface, node-interface), whether there is a link between two adjacent nodes can be used to indicate whether information such as network protocol messages and/or traffic data can be transmitted between the two nodes. Forwarding between adjacent nodes, for example, if there is a link between two adjacent nodes, information such as network protocol messages and/or traffic data can be forwarded between the two adjacent nodes; similarly, If there is no link between two adjacent nodes, information such as network protocol messages and/or traffic data cannot be forwarded between the two adjacent nodes.
  • a link (node 1-interface 1, node 2-interface 2) indicates that information such as network protocol messages and/or traffic data can be sent from interface 1 of node 1 and then received on node 2 and interface 2.
  • link 1-2 node 1-interface 1->node 2-interface 1
  • link 1-4 node 1-interface 8->node 4-interface 7
  • link 2-1 node 2-interface 2->node 1-interface 1
  • link 2-3 node 2-interface 3->node 3-interface 4
  • link 3-2 node 3-interface 4->node 2-interface 3
  • link 3-4 node 3-interface 5->node 4-interface 6
  • link 4-3 node 4-interface 6->node 3-interface 5
  • link 4-1 node 4-interface 7->node 1-interface 8).
  • a channel generally refers to a physical channel.
  • a service channel refers to a physical channel between a service source node and a service sink node.
  • the cross-connection relationship between the ingress port and the egress port may represent the wavelength channel of the optical layer, which is not limited in this application.
  • ASON network can provide fast end-to-end establishment, query, deletion, attribute modification and recovery functions of services through RSVP-TE protocol.
  • the network management sends the service creation command to the source node NE, and then the source node NE implements route calculation and initiates the service configuration process through the RSVP-TE signaling protocol, and establishes a cross-connection point by point from the source node to the downstream node to complete the service creation. .
  • This method makes full use of the routing and signaling functions of each network element and shortens the service configuration time.
  • Source node 1 calculates the service path through CSPF (Constrained Shortest Path First, constraint-based shortest path first): node 1-node 2 -Node 3, the source node carries the end-to-end path information along the calculated path, and the designated link 1-2 interface sends a Path message (a type of RSVP-TE protocol packet) to the intermediate node 2, and node 2 receives After the signaling message is received, the cross-configuration association information of the current node is solved and a reverse cross-connection is established, and then the intermediate node 2 carries the end-to-end path message to designate the link 2-3 interface to send the Path message to the sink node 3 direction.
  • CSPF Consstrained Shortest Path First, constraint-based shortest path first
  • the corresponding cross-configuration message is resolved at the sink node 3 and the reverse cross-connection is established; A forward cross connection is established; in the same process, the source node 1 sends a Path message to the sink node 3 via the intermediate node 2, and turns on the alarm monitoring of the service along the way.
  • the sink node 3 sends a Resv message to the source node 1 via the intermediate node 2 for confirmation.
  • the whole process automatically completes the end-to-end configuration establishment of services 1-3 by RSVP-TE signaling.
  • the service path may include a working path, a restoration path, a protection path, etc., and is used for data transmission of the bearing service.
  • a service path is a route between the first node and the last node, and one or more nodes may exist between the first node and the last node.
  • the first node of the service path represents the sending node of the service data
  • the end node of the service path represents the receiving node of the service data.
  • a service path can be represented by service (first node-end node).
  • the service path represents the route between the first node and the last node, it can also be called an end-to-end service path, wherein "end-to-end" represents the first node to the last node.
  • ASON can provide end-to-end establishment, query, deletion, attribute modification and recovery functions of service paths through the RSVP-TE protocol.
  • the end-to-end establishment of the service path includes: the network management sends the service path creation command to the head node, and then the head node implements route calculation and initiates the service path configuration process through the RSVP-TE signaling protocol. connection to complete the end-to-end establishment of the service path.
  • the service paths in this application include both working paths and protection paths.
  • the switching (or switching) of the service path may indicate that the service is switched from the working path to the protection path, or that the service is switched back from the protection path to the working path.
  • OTN Optical transport network
  • OTN can be applied to backbone, metro core and aggregation networks, and is further extended to access networks.
  • the data frame structure used in the OTN network is an OTN frame, and the OTN frame may also be called an OTN transmission frame.
  • OTN frames are used to carry various service data and provide rich management and monitoring functions.
  • OTN also needs to have transmission capabilities as low as several megabits per second in the future.
  • Liquid OTN introduces a service-oriented flexible container based on the traditional OTN frame structure - flexible optical service unit frame (flexible optical service unit, OSUflex), which is defined by flexible pipe bandwidth (such as n*2.4Mbit/s, n Indicates the number of pipes) to efficiently carry small particle signals.
  • the OTN frame may be an OSUflex frame, and the OSUflex frame may also be referred to as an OSU frame for short.
  • FIG. 2 is a schematic structural diagram of an OSU frame provided by an embodiment of the present application.
  • an optical payload unit-k optical payload unit-k, OPUk
  • OPUflex is divided into multiple payload blocks (Payload Block, PB), each PB contains an OSU frame and its corresponding index number TPN.
  • TPN can be used as the unique channel identifier of OSU frames at the service layer.
  • Each OSU frame includes an overhead area and a payload area.
  • the overhead area includes but is not limited to overhead information such as signaling type, version identifier, and check bit, and the payload area is used to carry service data information.
  • the length of the OSU frame is generally a fixed size, for example, the length is 192 bytes, 240 bytes, 128 bytes, or 64 bytes.
  • words such as “first” and “second” are used to distinguish the same or similar items with basically the same function and effect.
  • words “first”, “second” and the like do not limit the quantity and execution order, and the words “first”, “second” and the like are not necessarily different.
  • the network architecture and service scenarios described in the embodiments of the present application are for the purpose of illustrating the technical solutions of the embodiments of the present application more clearly, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application.
  • the evolution of the architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.
  • scenarios such as VR games and video services have higher and higher requirements for network performance.
  • the user obtains the VR rendering cloud service address in advance through the public network, and then initiates the establishment of a pipeline connection as needed when starting the game/video.
  • the time for establishing the pipe connection should be as short as possible.
  • Figure 3 is a method of sending a data frame.
  • the service head node first encapsulates the RSVP Path message into an IP packet, and then maps the IP packet to a data communication network (DCN). For example, mapping IP packets to general communication channel (GCC) overhead bytes of optical transport network (OTN) data frames.
  • GCC general communication channel
  • OTN optical transport network
  • Each intermediate node needs to extract IP packets one by one, and build routes or reroute services according to the IP packets. This process takes a long time, and because the available overhead is too small, the transmission speed is slow, resulting in low service configuration efficiency and poor performance.
  • the embodiments of the present application provide a data frame sending method and network device, which implements rapid service establishment and/or rerouting based on OSU frame associated control signaling, Thereby improving network performance.
  • the method for sending data frames described in the embodiments of the present application includes not only a process of establishing a working path of a service, but also a process of establishing a 1+1 protection path of a service, and may also include a working path of a service.
  • the process of rerouting after a failure occurs. Therefore, routing in this application means the end-to-end establishment of a service path.
  • FIG. 4 is a schematic diagram of a node configuration of an ASON network according to an embodiment of the present application.
  • the architecture includes an intelligent network management (Network Cloud Engine, NCE), node A, node B, and node C.
  • NCE Network Cloud Engine
  • Each node is equipped with a service configuration control unit and a channel-associated signaling control unit.
  • the ASON architecture also includes network equipment for path computation.
  • the network device includes a path computation element (Path computation element, PCE) controller, that is, the ASON is provided with at least one PCE controller.
  • PCE path computation element
  • the network device is a node with a path calculation function, for example, at least one node in the ASON is deployed with a PCE controller; also for example, at least one node in the ASON is deployed with a path calculation function module.
  • NCE is used for automatic provision and deletion of services.
  • a PCE controller may be included.
  • the NCE or PCE controller is specifically used to: pre-configure the mapping relationship between all OSU frame pipes on the optical port of the device and the optical data unit k (ODUk) pipes, so as to simplify the OSU frame associated service as a crossover of service paths Connection and bandwidth configuration.
  • the service configuration control unit is used for establishment, deletion, update and reconstruction of service paths; it is also used for establishment and resource configuration of single-station service cross-connection.
  • the channel-associated signaling control unit is used to process the channel-associated control signaling of the OSU frame, including service creation control signaling and deletion control signaling.
  • FIG. 4 is only a schematic diagram provided for the convenience of understanding the application, and does not constitute any limitation to the protection scope of the application.
  • the names of the above-mentioned various units are only examples, and other units or modules that can realize the same function are substituted.
  • FIG. 5 is a system sequence diagram of a method for sending a data frame provided by an embodiment of the present application, which may be applied to an ASON network, and the network may include multiple nodes as shown in FIG. 4 .
  • the nodes with the path calculation function and the PCE controller are collectively referred to as network equipment, and the network equipment can obtain a working path for carrying services through path calculation.
  • the working path of the service includes a head node A, an intermediate node B, and an end node C, where the head node A and the network device can exchange information through a communication protocol.
  • the network device may be the head node of the service.
  • the method for sending a data frame in FIG. 5 includes at least all or part of the following steps:
  • S510 The network device preconfigures the OTN mapping relationship and the routing label.
  • the network device preconfigures the mapping relationship between the OSU frame and the ODUk pipe. Through the above pre-configuration, the network device can simplify the service path construction process into cross-connection and resource configuration, thereby improving service configuration efficiency.
  • the network device also allocates a routing label to the OSU frame channels on different subracks, boards, and ports. into the node.
  • the attribute of each routing label is 4 bytes, which corresponds to the subrack, board position, port and channel number in the node one-to-one.
  • the network device can store the routing labels of each node in the device.
  • Node A is the first node of the service. After node A receives the service creation request, it requests the network device to calculate the bearer path of the service.
  • the network device calculates and obtains the working path of the service, and converts the working path into routing label stack information.
  • the network device can acquire the services and topology in the network, then determine the working path carrying the service according to the network-wide route TE and bandwidth information, and then convert the working path into routing label stack information.
  • the routing label stack information is used to instruct each node on the working path to establish a channel for transmitting services.
  • the routing label stack information represents a sorted set of labels, which may include one or more labels, and the plurality of labels are arranged in a certain order, for example, according to the order in which each label is acquired.
  • Each of the labels corresponds one-to-one with the service transmission channel in the nodes of the working path.
  • the network device determines that the path carrying the first service is the first path, where the first path includes the node through which the service passes and the service channel information in the node, for example, the first path is: node A (subrack 1-slab 1 - Port 1 - Channel 1) - Node B (Subrack 2 - Board Position 2 - Port 2 - Channel 2) - Node C (Subrack 3 - Board Position 3 - Port 3 - Channel 3). Then, the network device converts the first path into routing label stack information, eg, node A (first label) - node B (second label) - node C (third label).
  • routing label stack information eg, node A (first label) - node B (second label) - node C (third label).
  • the establishment in the embodiment of the present application indicates that the service channel in the node is available/activated, or more specifically, the establishment indicates that the crossover of the channel for transmitting the service in the node has been established.
  • S540 The network device delivers the routing label stack information to node A.
  • the network device sends the routing label stack information to node A through a path computation element communication protocol (Path Computation Element Communication Protocol, PCEP) message.
  • PCEP Path Computation Element Communication Protocol
  • the network device delivers the routing label stack information to node A through a protocol message having the same function as PCEP.
  • the network device delivers the routing label stack information to the node A through a newly added field (for example, an extended PCEP field) in the original signaling between the network device and the node A.
  • Method 1 The network device is PCE
  • a PCE controller set in a network device network and the PCE controller is a device deployed independently of the first node of the above-mentioned working path. Then in the first mode, after the network device converts the working path into the routing label stack information, it needs to deliver the routing label stack information to the service head node A.
  • the above routing label stack information may be a single message or a collective term for multiple messages, that is, the routing label stack information may be sent to the head node A through one message, or may be sent to the head node A through multiple messages.
  • Mode 2 The network device is the first node of the service.
  • the node A can calculate and obtain the routing information of the working path by itself, and convert the routing information of the working path into routing label stack information.
  • the difference from the above-mentioned first mode is that in the second mode, the network device does not need to send the routing label stack information to the head node, that is, it is not necessary to execute S540.
  • Node A acquires the routing label stack information of the service path, and inserts the routing label stack information and service attribute information into the payload area of the first data frame.
  • Node A obtains the routing label stack information from the protocol message, and inserts the routing label stack information into the payload area field of the first data frame.
  • node A may also insert service attribute information into the payload area field of the first data frame, to instruct the nodes on the service path to configure physical resources for the service.
  • the service attribute information includes at least one of the following information: service identification ID, bandwidth, delay, source node identification ID, sink node identification ID, and service path attributes.
  • the service path attribute represents the control type of the first data frame, for example, the path currently established through the first data frame is a service working path, or a service protection path, or a rerouting path.
  • the first data frame may specifically be a flexible optical service unit OSU frame with a length of 192 bytes.
  • the signaling format of the OSU frame may refer to FIG. 6 .
  • the length of the OSU frame is 192 bytes, wherein the overhead area includes 7 bytes, and the payload area includes 185 bytes.
  • a 12-bit Label is reserved in the overhead area of the OSU frame to identify the channel number of the OSU frame. For example, the Label identifies the channel of the service on node A: ingress port 1 - egress port 1, node A can directly Send the OSU frame on outgoing port 1.
  • node A when node A sends an OSU frame on egress port 1, it can be understood that the OSU frame is sent on the wavelength corresponding to the egress port, and the OSU frame is first mapped to the high-order ODUk data preconfigured on the egress port. frame, and then sent out from this outgoing port 1. Therefore, the process of building a service route is simplified into cross-connection and resource configuration, which can improve service configuration efficiency.
  • a 12-bit Type is also reserved in the overhead area of the OSU frame, and Type identifies the type of the OSU frame as a control frame and a specific control type.
  • the upper 4 bits of Type, 1000 indicate that the OSU frame is a large type of control signaling
  • the lower 8 bits, 00000010 indicate that the OSU frame is a service path establishment control type.
  • the payload area Payload is a custom field, including routing label stack information and service attribute information.
  • the payload area may include service attribute information such as Label Num, Label(list), Source Node ID, Dest Node ID, Service ID, Bandwidth, and Latency.
  • service attribute information such as Label Num, Label(list), Source Node ID, Dest Node ID, Service ID, Bandwidth, and Latency.
  • a 32-bit value Bandwidth Service Bandwidth Properties A 32-bit value Latency Service Delay Attribute
  • the custom fields in the payload area can include label quantity Label Num, routing label stack information (list) Label (list), source node ID Source Node ID, sink node ID Dest Node ID, service ID ID Service ID , Bandwidth, Latency and other attribute information.
  • the number of labels represents the number of nodes on the service path that receive the routing label stack information and the service attribute information.
  • the remaining bytes are reserved bytes for writing other extended attributes of the service.
  • the other extended attribute of the service may be a service path attribute, and the service path attribute represents the specific control type of the current OSU frame.
  • Each label in the routing label stack information corresponds to the channel through which the node transmits services.
  • the first label in the routing label stack information corresponds to the channel subrack 1-slab 1-port 1-channel 1 in node A that transmits services, and is used to instruct node A to establish a cross-connection for the service at the physical layer.
  • the second label in the routing label stack information corresponds to the channel subrack 2-slab 2-port 2-channel 2 in the node B that transmits the service, and is used to instruct the node B to establish a cross-connection for the service at the physical level.
  • the correspondence between labels and channels needs to be pre-configured in each node.
  • both the Type of the overhead area and the service path attribute of the payload area in this embodiment can be used to identify the specific control type of the OSU frame, and which field is used to identify the specific control type.
  • this embodiment does not limit this.
  • Node A sends the first data frame to Node B.
  • Node A sends the first data frame to Node B.
  • the payload area of the first data frame carries routing label stack information and service attribute information, and the routing label stack information may be a label list, including multiple labels, each of which is associated with each node on the working path.
  • the method further includes: mapping the first data frame to the high-order ODUk frame, and then sending the ODUk frame to the node B.
  • the method further includes: the node A establishes a cross-connection for the service at the physical layer according to the first label in the routing label stack information; and, configures resources at the physical layer for the service according to the service attribute information, For example, allocating bandwidth for services.
  • the reason why the first data frame is sent to Node B first, and then cross-connection and resource configuration are performed, is to transmit the first data frame to the opposite end of the working path as soon as possible, and each node completes the cross-connection and resource configuration of the service channel in parallel, thereby Reduce routing time.
  • Node B acquires the routing label stack information and service attribute information in the first data frame, and forwards the routing label stack information and service attribute information to node C.
  • This step specifically includes:
  • Node B acquires routing label stack information and service attribute information in the first data frame
  • Node B forwards the second data frame containing the label attribute information and service attribute information to node C;
  • Node B establishes a cross-connection for the service at the physical layer according to the routing label stack information, and configures resources for the service according to the service attribute information.
  • Node B After acquiring the routing label stack information and service attribute information, Node B directly forwards the second data frame containing the label attribute information and service attribute information to its downstream node, that is, Node C, and then performs processing by this node.
  • the reason for this is to transmit the first data frame containing routing information to the opposite end of the working path as soon as possible, and each node completes the cross-connection and resource configuration of the service channel in parallel, thereby shortening the routing time.
  • the content of the second data frame may be the same as that of the first data frame, or the second data frame may have one less second tag than the first data frame.
  • the data frame forwarded by the node B to the node C is called the second data frame.
  • the routing label stack information includes multiple labels
  • the Node B acquiring the routing label stack information may be understood as acquiring the second label corresponding to the channel through which the Node B transmits the service among the multiple labels.
  • a label is popped up, for example, the first label is popped up each time, which is used for the cross establishment of the service channel of the current node and the forwarding of the control signaling of the first data frame. port.
  • FIG. 7 is a schematic flowchart of a node acquiring a label through a stack.
  • the first data frame sent by node A to node B includes an overhead area and a payload area, wherein the overhead area is used to identify the first data frame as a control frame, and the payload area is used to carry the data used for establishing services
  • the routing label stack information of the channel such as label number-Label 11-Label 22-Label 33.
  • the number of labels indicates the total number of Labels included in the routing label stack information.
  • Label 11 corresponds to the service channel of node A
  • Label 22 corresponds to the service channel of node B
  • Label 33 corresponds to the service channel of node C.
  • the initial first data frame of node A carries three Labels, namely Label 11, Label 22, and Label 33.
  • the initial first data frame pops up the first Label 11 at node A, which is used for node A to establish a service channel. Cross-connect, and the Label 11 is also used to indicate the forwarding port of the first data frame.
  • Label 22 becomes the first Label of the routing label stack information, and Node A continues to forward the first data frame to Node B.
  • the first data frame arrives at the node B, and the current first Label 22 is popped up, which is used for the node B to establish a cross-connection of the service channel, and is also used to indicate the forwarding port of the first data frame.
  • Label 33 is called the first Label and is the only label left.
  • Node B continues to forward the first data frame to node C, and after reaching node C, a unique Label 33 is popped up for node C to establish a cross-connection of the service channel. Since Label 33 is the last label, node C recognizes that there is no remaining Label in the first data frame after the pop-up, and judges that it is no longer necessary to continue forwarding.
  • each node needs to re-edit the packet before forwarding it after obtaining the label.
  • first data frame first data frame first data frame.
  • the node obtains the label by stacking, and the packets in the first data frame gradually decrease with the forwarding, and the transmission speed is faster.
  • the routing label stack information includes a label pointer field, which is used to indicate the label that the current node needs to acquire.
  • the first data frame sent by node A to node B includes an overhead area and a payload area, wherein the overhead area is used to identify the first data frame as a control frame, and the payload area is used to carry the data used for establishing services
  • the routing label stack information of the channel such as label number-Label 11-Label 22-Label 33.
  • the number of labels indicates the total number of Labels included in the routing label stack information.
  • Label 11 corresponds to the service channel of node A
  • Label 22 corresponds to the service channel of node B
  • Label 33 corresponds to the service channel of node C.
  • the routing label stack information in this mode includes a Pointer, which is used to indicate the label that the current node needs to acquire. Each time a node passes through, the routing label stack information remains unchanged, and the pointer Pointer increases by 1.
  • the first data frame is the first data frame.
  • the node obtains the label through the pointer method, and the information structure of the routing label stack remains unchanged, only the pointer value needs to be changed, and the processing is simple.
  • the Node B After the Node B forwards the second data frame to its downstream node, it establishes a cross-connection for the service at the physical layer according to the routing label stack information, establishes a channel for transmitting the service, and configures resources for the service according to the service attribute information, such as allocating bandwidth for the service.
  • the routing information can be transmitted to the opposite end of the working path as soon as possible, and each node can complete the cross-connection and resource configuration of the service channel in parallel, thereby shortening the routing time.
  • Node C acquires the routing label stack information and service attribute information in the second data frame, and completes the establishment of the cross-connection and resource configuration.
  • node C is the end node of the service, and when it is recognized that there is only the last label left in the routing label stack information, it is judged that it is no longer necessary to continue forwarding. Node C separately completes the establishment of the cross-connection and the resource configuration according to the routing label stack information and the service attribute information. For the specific process, refer to the foregoing steps, which will not be repeated here.
  • Node C sends a response message to node A, indicating that the service is successfully created.
  • node C can also send a response message to the other device.
  • node C sends a response message to the NCE.
  • FIG. 9 is a flowchart of a service routing method provided by an embodiment of the present application.
  • the execution body of the method may be node A in FIG. 5 , that is, the head node of the service.
  • the method includes at least the following steps:
  • the first node acquires the routing label stack information of the first path.
  • the first path is used to transmit the first service
  • the routing label stack information is used to instruct each node on the first path to establish a channel for the first service on each node.
  • the method may further include: the first node receives a routing request of the first service.
  • the first node requests the network device to calculate the working path for transmitting the first service; or, the first node calculates the working path for transmitting the first service by itself.
  • the method may further include that the first node converts the first path into routing label stack information.
  • S920 The first node inserts the routing label stack information and the service attribute information into the payload area of the first data frame.
  • the service attribute information is used to indicate that each node on the first path configures resources for the first service, including one or more of the following information: service ID, bandwidth, delay, source node ID, sink node ID ID, business path attribute.
  • the routing label stack information includes a plurality of labels, each of the plurality of labels corresponds to a channel through which each node on the first path transmits the first service, and the corresponding relationship is pre-configured in each node on the first path .
  • the first data frame may be a flexible optical service unit OSU frame, for example, the OSU frame includes an overhead area and a payload area, both of which can be customized. For example, routing label stack information and service attribute information are carried in the payload area.
  • the payload area of the OSU frame further includes the number of labels, which are used to identify the number of nodes on the first path that receive the routing label stack information and the service attribute information.
  • the overhead area of the OSU frame includes a signaling type Type field, where the Type field is used to indicate that the OSU frame is a control frame and a specific control type.
  • the Type field includes 12 bits, the upper 4 bits of 1000 indicate that the OSU frame is a large type of control signaling, and the lower 8 bits of 00000010 indicate that the OSU frame is a service path establishment control type.
  • the Type field may be used to instruct the OSU frame to create a control frame for the first service.
  • the Type field may be used to instruct the OSU frame to create a control frame for the first service 1+1 protection.
  • the Type field may also It is used to indicate that the OSU frame is the first service rerouting control frame.
  • the Type field is used to instruct the OSU frame to create a control frame for service 1+1 protection
  • two cases are included: the Type field is used to instruct the OSU frame to create a control frame for the primary path of the first service; Alternatively, the Type field is used to indicate that the OSU frame creates a control frame for the backup path of the first service.
  • S930 The first node sends the first data frame.
  • the method further includes that the first node establishes a connection for the service at the physical level according to the first label in the routing label stack information;
  • the service attribute information configures resources at the physical level for the service.
  • FIG. 10 is a flowchart of another service routing method provided by an embodiment of the present application.
  • the execution body of the method may be node B and node C in FIG. 5 .
  • the method includes at least the following steps:
  • S1010 The second node receives the first data frame.
  • the payload area of the first data frame carries routing label stack information and service attribute information, the routing label stack information is used to instruct each node on the first path to establish a channel for transmitting the first service, and the service attribute information is used for Instructing each node on the first path to configure resources for the first service, where the first path is a path calculated by the network device for transmitting the first service.
  • the first data frame is an OSU frame
  • the routing label stack information and service attribute information are carried in the payload area of the OSU frame.
  • the routing label stack information includes a plurality of labels, each of the plurality of labels corresponds to a channel through which each node on the first path transmits the first service, and the corresponding relationship is pre-configured in each node on the first path. .
  • the service attribute information includes one or more of the following information: service identification ID, bandwidth, delay, source node identification ID, sink node identification ID, and service path attributes.
  • the payload area further includes the number of labels, where the number of labels is used to identify the number of nodes on the first path that receive the routing label stack information and the service attribute information.
  • the overhead area of the OSU frame includes a signaling type Type field, where the Type field is used to indicate that the OSU frame is a control frame and a specific control type.
  • the Type field includes 12 bits, the upper 4 bits of 1000 indicate that the OSU frame is a large type of control signaling, and the lower 8 bits of 00000010 indicate that the OSU frame is a service path establishment control type.
  • the Type field can be used to instruct the OSU frame to create a control frame for the first service.
  • the Type field can be used to instruct the OSU frame to create a control frame for the 1+1 protection of the first service.
  • the Type field can also be used to create a control frame for the first service. It is used to indicate that the OSU frame is the first service rerouting control frame.
  • the Type field is used to instruct the OSU frame to create a control frame for service 1+1 protection
  • two cases are included: the Type field is used to instruct the OSU frame to create a control frame for the primary path of the first service; Alternatively, the Type field is used to indicate that the OSU frame creates a control frame for the backup path of the first service.
  • both the Type of the overhead area and the service path attribute of the payload area in this embodiment can be used to identify the specific control type of the OSU frame, and which field is used to identify the specific control type.
  • this embodiment does not limit this.
  • the second node receiving the OSU frame may include: the second node receiving the ODUk frame including the OSU frame, and demapping the ODUk frame to obtain the OSU frame.
  • S1020 The second node acquires routing label stack information and service attribute information from the first data frame.
  • routing label stack information includes multiple labels
  • acquiring the routing label stack information by the second node may be understood as acquiring a second label corresponding to the channel through which the second node transmits the first service among the multiple labels.
  • the second node establishes a channel for the second node to transmit the first service according to the routing label stack information; configures resources for the first service according to the service attribute information.
  • the channel-associated signaling control unit of the second node uploads the routing label stack information and the service attribute information to the service configuration control unit, and the service configuration control unit finds the corresponding channel information according to the second label of the routing label stack information: Board-port-channel number, and outgoing board-port-channel number, and then establish a single-site service cross-connection.
  • the bandwidth is delivered to the device hardware based on the basic service attribute information.
  • FIG. 11 is a scene diagram to which the service routing method provided by the embodiment of the present application can be applied.
  • the application network in this scenario is a GMPLS/ASON network with ASON automation functions.
  • nodes A, B, and C all enable the ASON function, and each node deploys a channel-associated signaling control device and a service configuration control device.
  • Network information such as nodes and links on the entire network are automatically obtained through OSPF of ASON protocol or Open Shortest Path First-Traffic Engineering (OSPF-TE) based on traffic engineering, and end-to-end service paths are established and restored through ASON protocol RSVP-TE is automatically established.
  • OSPF-TE Open Shortest Path First-Traffic Engineering
  • the PCE automatically obtains the node, link, and service information of the entire network according to OSPF or the Path Computation Element Communication Protocol (PCEP).
  • PCEP Path Computation Element Communication Protocol
  • the PCE mainly deals with end-to-end path calculation of network services and can be deployed in server network management or similar devices. If there is no PCE in the network, the end-to-end paths of network services can be calculated by each node in a distributed manner.
  • FIG. 11 is described by taking the establishment of an end-to-end single service through OSU frame control signaling as an example.
  • the service routing method provided by the embodiment of the present application includes the following steps:
  • the network device preconfigures the mapping relationship between the OSU frame and the ODUk pipe. Through the above pre-configuration, the network device can simplify the service path construction process into cross-connection and resource configuration, thereby improving service configuration efficiency.
  • the network device also allocates a routing label to the OSU frame channels on different subracks, boards, and ports. into the node.
  • the attribute of each routing label is 4 bytes, which corresponds to the subrack, board position, port and channel number in the node one-to-one.
  • the network device can store the routing labels of each node in the device.
  • Node A receives the creation request of the first service, and then requests the network device to calculate the service path.
  • the creation request includes bandwidth information of the first service.
  • the network device can obtain the services and topology in the network, then determine the working path carrying the first service based on the TE and bandwidth information of the entire network, and then convert the working path into routing label stack information.
  • the routing label stack information is used to instruct each node on the working path to establish a channel for transmitting the first service. After that, the network device delivers the routing label stack information to node A.
  • the network device determines, through calculation, that the path carrying the first service is the first path, where the first path includes the nodes that the service passes through and the service channel information in the nodes.
  • the first path is: node A (subrack 1- Board 1 - Port 1 - Channel 1) - Node B (Subrack 2 - Board 2 - Port 2 - Channel 2) - Node C (Subrack 3 - Board 3 - Port 3 - Channel 3).
  • the network device converts the first path into routing label stack information, eg, node A (first label) - node B (second label) - node C (third label).
  • the establishment in the embodiment of the present application indicates that the service channel in the node is available/activated, or more specifically, the establishment indicates that the crossover of the channel for transmitting the service in the node has been established.
  • the node A can also calculate the service path by itself after receiving the request for creating the first service.
  • Node A receives the routing label stack information delivered by the network device. According to the creation request of the first service, the head node A identifies that the service creation needs to be performed through the OSU frame control signaling.
  • Node A inserts the routing label stack information into the field of the OSU frame.
  • node A may also insert service attribute information into the field of the OSU frame, to instruct the nodes on the service path to configure resources for the service.
  • the service attribute information includes the following information: service identification ID, bandwidth, delay, source node identification ID, and sink node identification ID. Then, node A sends the OSU frame to node B.
  • the method further includes: encapsulating and mapping the signaling message of the OSU frame, mapping it to a high-order ODUk frame, and then sending the ODUk frame to the node B.
  • node A After node A sends the OSU frame to node B, it also includes: node A establishes a cross-connection for the service at the physical layer according to the first label in the routing label stack information; and, configures resources at the physical layer for the service according to the service attribute information, for example, Allocate bandwidth for services.
  • the reason why the OSU frame is sent to Node B first, and then cross-connection and resource configuration are performed, is to transmit the OSU frame control signaling to the opposite end of the working path as soon as possible. routing time.
  • the overhead area of the OSU frame includes a 12-byte Type, which is used to identify the type of the OSU frame as a control frame and a specific control type.
  • Type the upper 4 bits of Type, 1000, indicate that the OSU frame is a large type of control signaling, and the lower 8 bits, 00000010, indicate that the OSU frame is specifically to create the first service control type.
  • the payload area Payload is a custom field that carries routing label stack information and service attribute information. For the message format of the OSU frame and the specific field meanings of the custom fields in the payload area, reference may be made to the foregoing embodiment shown in FIG. 5 , which will not be repeated here.
  • node B After node B obtains the routing label stack information and service attribute information, it directly forwards the OSU frame to its downstream node, that is, node C, and then processes the node.
  • the reason for this is to transmit the OSU frame control signaling to the opposite end of the working path as soon as possible, and each node completes the cross-connection and resource configuration of the service channel in parallel, thereby shortening the routing time.
  • the routing label stack information includes multiple labels
  • the Node B acquiring the routing label stack information may be understood as acquiring the second label corresponding to the channel through which the Node B transmits the service among the multiple labels.
  • there are two implementation manners for Node B to acquire the second label namely, a stack manner and a pointer manner. The implementation details of the two manners have been described in detail in the aforementioned FIG. 6 and FIG.
  • the Node B After the Node B forwards the OSU frame to its downstream node, it establishes a cross-connection for the service at the physical layer according to the routing label stack information, establishes a channel for transmitting the service, and allocates resources for the service according to the service attribute information, such as allocating bandwidth for the service.
  • Node C acquires the routing label stack information and service attribute information in the OSU frame, and completes the establishment of the cross-connect and resource configuration.
  • Node C is the end node of the service. When it is recognized that there is only the last label left in the routing label stack information, it is judged that it is no longer necessary to continue forwarding. Node C separately completes the establishment of the cross-connection and the resource configuration according to the routing label stack information and the service attribute information. For the specific process, refer to the foregoing steps, which will not be repeated here.
  • Node C sends a response message to node A, indicating that the service is successfully created.
  • node C can also send a response message to the other device.
  • node C sends a response message to the NCE.
  • the data frame sending method shown in Figure 11 mainly includes the following two key points: 1) The single-station OTN data frame mapping relationship and routing label pre-configuration, configure the mapping relationship between the OSU frame pipeline and the ODUk pipeline in advance, and at the same time, the OSU frame The pipeline bandwidth is set to 0, which simplifies the sending process of data frames to cross-connection and resource configuration, thereby improving the efficiency of service configuration. Correspondence between single station configuration labels and service pipelines. 2) The OSU frame control signaling message is forwarded along with the channel first, and the end-to-end establishment of the service is established. After the end-to-end service is established successfully, the data frame is sent, and the control frame is not sent any more.
  • FIG. 12 is an application scenario diagram of another service routing method provided by an embodiment of the present application.
  • the application network in this scenario is a GMPLS/ASON network with ASON automation functions.
  • nodes A, B, C, and D all enable the ASON function, and each node deploys a channel-associated signaling control device and a service configuration control device.
  • Network information such as nodes and links on the entire network are automatically obtained through OSPF of the ASON protocol or based on OSPF-TE, and the establishment and restoration of end-to-end service paths are automatically established through RSVP-TE of the ASON protocol.
  • PCE automatically obtains node, link, and service information on the entire network according to OSPF or PCEP.
  • the PCE mainly deals with end-to-end path calculation of network services and can be deployed in server network management or similar devices. If there is no PCE in the network, the end-to-end paths of network services can be calculated by each node in a distributed manner.
  • FIG. 12 is described by taking the establishment of a 1+1 service through OSU frame control signaling as an example.
  • the principle of quickly creating a 1+1 service is basically the same as that of creating a single service as shown in Figure 11.
  • the primary working path is created through OSU frame control signaling to quickly open the service, and then the backup protection path is created.
  • the path attribute is associated with the unique service ID to realize the configuration of the service protection group of the aggregation point (ie the first and last node) of the active/standby path.
  • the service routing method provided by the embodiment of the present application includes the following steps:
  • the network device preconfigures the mapping relationship between the OSU frame and the ODUk pipe.
  • the mapping relationship between the OSU frame and the ODUk pipe For the specific configuration process, reference may be made to the foregoing embodiments, which will not be repeated here.
  • Node A receives the 1+1 creation request of the first service, and then requests the network device to calculate the primary and secondary paths of the first service. For example, the network device determines through calculation that the working path of the first service is: node A (subrack 1 - board position 1 - port 1 - channel 1) - node B (subrack 2 - board position 2 - port 2 - channel 2 )—node C (subrack 3-board position 3-port 3-channel 3), determine the protection path of the first service as: node A (subrack 2-board position 1-port 1-channel 1)—node B ( Subrack 3-Board 2-Port 2-Channel 2)—Node C (Subrack 4-Board 4-Port 3-Channel 3).
  • the network device converts the working path into routing label stack information: Node A+ Label 1—Node B+ Label 2—Node C+ Label 3; converts the protection path into routing label stack information: Node A+ Label 4—Node B+ Label 5—Node C+ Label 6.
  • the network device delivers the routing label stack information of the working path of the first service and the routing label stack information of the protection path to node A.
  • the above routing label stack information may be a single message or a collective term for multiple messages, that is, the routing label stack information of the working path and the routing label stack information of the protection path can be sent to node A through one message, or through two or more.
  • a message is sent to node A.
  • the network device first delivers the routing label stack information of the working path to node A, and then delivers the routing label stack information of the protection path to node A.
  • Node A receives the routing label stack information of the working path and the routing label stack information of the protection path. According to the creation request of the first service, the node A identifies that the 1+1 service creation needs to be performed through the OSU frame control signaling.
  • Node A first inserts the routing label stack information of the working path into the Payload field of the first OSU frame.
  • node A may also insert service attribute information into the Payload field of the first OSU frame to indicate that the node on the working path is The first business configures resources.
  • the service attribute information includes the following information: service identification ID, bandwidth, delay, source node identification ID, and sink node identification ID.
  • Node B inserts the routing label stack information of the protection path into the field of the second OSU frame.
  • the second OSU frame may also carry service attribute information. Then. Node A sends the first OSU frame and/or the second OSU frame to the downstream node.
  • the service attribute information in this embodiment further includes path attribute information, which is used to identify the specific control type of the current OSU frame.
  • the service attribute information carried in the first OSU frame includes path attribute information, which is used to identify that the first OSU frame creates a control frame for the first service working path.
  • the service attribute information carried in the second OSU frame includes path attribute information, which is used to identify that the second OSU frame creates a control frame for the first service protection path.
  • a 32-bit value Source Node ID The source node ID of the service, which identifies the first node of the service
  • Dest Node ID The end node ID of the service, which identifies the end node of the service (optional)
  • a 32-bit value Service ID Service ID the unique ID of the end-to-end path
  • a 32-bit value Bandwidth Service Bandwidth Properties A 32-bit value Latency Service Delay Attribute
  • Type in the overhead area of the OSU frame can also be used to identify the specific control type of the OSU frame, occupying 12 bits in the overhead area, of which the upper 4 bits are used to identify the large type of the control frame, and the lower 8 bits are used to identify specific control type.
  • the method further includes: encapsulating and mapping the signaling messages of the first OSU frame and/or the second OSU frame, and mapping them to the high-order ODUk frame, The ODUk frame is then sent to Node B.
  • node A first sends the first OSU frame to node B, and then sends the second OSU frame after the working path of the first service is established.
  • node A After node A first sends the first OSU frame to node B, it also includes: node A establishes a cross-connection for the service at the physical layer according to the first label in the routing label stack information of the working path; and, node A is the service according to the service attribute information. Configure working path resources at the physical layer, for example, allocate working bandwidth for services.
  • the reason why the first OSU frame is sent to Node B is to quickly establish a service.
  • node A After the service is established, node A sends a second OSU frame to establish a protection path for the first service.
  • node A as the head node of the first service, can perform local search and association through a unique service ID when creating a cross-connection of a protection path, and start to create a protection path when a cross-connection of an established working path is found. , that is, create a service protection group and deliver it to the hardware to take effect.
  • Steps 4 to 6 in this scenario are the same as steps 4 to 6 in the scenario of FIG. 11 , and reference may be made to the descriptions of the foregoing embodiments, which will not be repeated here.
  • FIG. 13 is an application scenario diagram of another service routing method provided by an embodiment of the present application.
  • the application network in this scenario is a GMPLS/ASON network with ASON automation functions.
  • nodes A, B, C, and D all enable the ASON function, and each node deploys a channel-associated signaling control device and a service configuration control device.
  • Network information such as nodes and links on the entire network are automatically obtained through OSPF of the ASON protocol or based on OSPF-TE, and the establishment and restoration of end-to-end service paths are automatically established through RSVP-TE of the ASON protocol.
  • PCE automatically obtains node, link, and service information on the entire network according to OSPF or PCEP.
  • the PCE mainly deals with end-to-end path calculation of network services and can be deployed in server network management or similar devices. If there is no PCE in the network, the end-to-end paths of network services can be calculated by each node in a distributed manner.
  • This embodiment is described by taking the rerouting of services through OSU frame control signaling as an example.
  • the service routing method provided by the embodiment of the present application includes the following steps:
  • the network device preconfigures the mapping relationship between the OSU frame and the ODUk pipe.
  • the mapping relationship between the OSU frame and the ODUk pipe For the specific configuration process, reference may be made to the foregoing embodiments, which will not be repeated here.
  • the current working path of the first service is ABC.
  • the network device or NCE calculates the restoration path ADC of the first service based on the nodes and topology of the entire network, and converts the restoration path into routing label stack information and delivers it to the head node.
  • the first node A stores the routing label stack information.
  • A-B is faulty on the working path of the first service, for example, the fiber is disconnected, and the head node A senses that the working path of the first service is faulty, it directly activates the local end-to-end recovery path for service recovery, and restores paths A-D-C.
  • the head node A inserts the routing label stack information of the restoration path into the Payload field of the OSU frame.
  • the node A may also insert service attribute information into the Payload field of the OSU frame to indicate that the node on the restoration path is the first 1.
  • Service configuration resources For example, the service attribute information includes the following information: service identification ID, bandwidth, delay, source node identification ID, and sink node identification ID. Then, node A sends the OSU frame to node D.
  • the service attribute information in this embodiment also includes path attribute information, which is used to identify the specific control type of the current OSU frame.
  • path attribute information is used to identify that the OSU frame creates a control frame for the first service restoration path, that is, the first service rerouting control frame.
  • Dest Node ID The end node ID of the service which identifies the end node of the service (optional)
  • a 32-bit value Bandwidth Service Bandwidth Properties A 32-bit value Latency Service Delay Attribute
  • Type in the overhead area of the OSU frame can also be used to identify the specific control type of the OSU frame, occupying 12 bits in the overhead area, of which the upper 4 bits are used to identify the large type of the control frame, and the lower 8 bits are used to identify specific control type.
  • node A After node A sends the OSU frame to node B, it also includes: node A establishes a cross-connection for service restoration at the physical layer according to the first label in the routing label stack information of the restoration path; Layer configuration recovery path resources, for example, allocating recovery bandwidth for services.
  • Layer configuration recovery path resources for example, allocating recovery bandwidth for services.
  • Steps 4 to 6 in this scenario are the same as steps 4 to 6 in the scenario of FIG. 11 , and reference may be made to the descriptions of the foregoing embodiments, which will not be repeated here.
  • FIG. 14 is an application scenario diagram of another service routing method provided by an embodiment of the present application.
  • the application network in this scenario is a GMPLS/ASON network with ASON automation functions.
  • nodes A, B, C, and D all enable the ASON function, and each node deploys a channel-associated signaling control device and a service configuration control device.
  • Network information such as nodes and links on the entire network are automatically obtained through OSPF of the ASON protocol or based on OSPF-TE, and the establishment and restoration of end-to-end service paths are automatically established through RSVP-TE of the ASON protocol.
  • PCE automatically obtains node, link, and service information on the entire network according to OSPF or PCEP.
  • the PCE mainly deals with end-to-end path calculation of network services and can be deployed in server network management or similar devices. If there is no PCE in the network, the end-to-end paths of network services can be calculated by each node in a distributed manner.
  • FIG. 14 is described by taking the segment recovery of the service through OSU frame control signaling as an example.
  • the service routing method provided by the embodiment of the present application includes the following steps:
  • the network device preconfigures the mapping relationship between the OSU frame and the ODUk pipe.
  • the mapping relationship between the OSU frame and the ODUk pipe For the specific configuration process, reference may be made to the foregoing embodiments, which will not be repeated here.
  • the current working path of the first service is ABC.
  • the network device or NCE calculates the restoration path ABDC of the first service based on the entire network node and topology, and converts the restoration path into routing label stack information and sends it to the head node.
  • the first node A stores the routing label stack information.
  • Node B senses the working path of the first service is faulty, finds the affected service, and advertises it to the head node A of the first service.
  • the head node A senses that the link B-C is faulty, searches locally and matches the recovery path A-B-D-C corresponding to the first service, and directly activates the local end-to-end recovery path A-B-D-C for service recovery.
  • the head node A inserts the routing label stack information of the restoration path into the Payload field of the OSU frame.
  • the node A may also insert service attribute information into the Payload field of the OSU frame to indicate that the node on the restoration path is the first 1.
  • Service configuration resources For example, the service attribute information includes the following information: service identification ID, bandwidth, delay, source node identification ID, and sink node identification ID. Node A then sends the OSU frame to Node B.
  • the service attribute information in this embodiment also includes path attribute information, which is used to identify the specific control type of the current OSU frame.
  • the path attribute information carried in the OSU frame is used to identify that the OSU frame creates a control frame for the first service restoration path, that is, a first service rerouting control frame.
  • the working path and the restoration path share the A-B link segment, so the cross-connection and bandwidth of node A have already been configured, and there is no need to repeat the configuration.
  • Steps 4 to 6 in this scenario are the same as steps 4 to 6 in the scenario of FIG. 11 , and reference may be made to the descriptions of the foregoing embodiments, which will not be repeated here.
  • the removal process includes at least the following steps:
  • the NCE delivers a service deletion request to the service head node, for example, the deletion request carries information such as a service ID, a source node ID, and a sink node ID.
  • the head node A receives the above deletion request, locally obtains the sending label stack information of the data frame according to the service ID, and inserts the routing label stack information into the custom field of the payload area of the OSU frame.
  • node A also inserts service attribute information into the custom field of the payload area of the OSU frame.
  • the business attribute information may include only the business ID.
  • a 12-bit Type is reserved in the overhead area of the OSU frame to identify the control type of the OSU frame. For example, the upper 4 bits of 1000 are used to identify the large type of control frame, and the lower 8 bits of 00000011 are used to identify the specific control type of service deletion.
  • the head node A sends the OSU frame to the downstream node. Since the service already exists, it can be directly forwarded with the data flow. From this point of view, the routing label stack information can be selected.
  • the service configuration control unit in node A finds the service cross-connection that matches with the service ID according to the service ID, and sends a message to the data plane to delete the cross-connection of the service channel.
  • the OSU frame can only carry the service deletion control signaling identifier and the service ID, namely Yes, the routing label stack information can be selected; 2) OSU frames can be directly forwarded along with the service data flow, and there is no need to obtain outbound ports for forwarding according to the routing label stack information carried in the OSU frames.
  • the service routing method provided by the present application is described in detail above with reference to FIG. 5 to FIG. 14 , and the service routing apparatus provided by the embodiment of the present application is described in detail below with reference to FIG. 15 to FIG. 17 .
  • FIG. 15 is a schematic diagram of an apparatus 1500 for service routing provided by the present application.
  • the apparatus 1500 includes a processing unit 1510 and a sending unit 1520 .
  • a processing unit 1510 configured to obtain routing label stack information of a service path, where the service path is used to transmit the service, and the routing label stack information is used to instruct each node on the service path to establish a channel for transmitting the service;
  • the processing unit 1510 is further configured to insert the routing label stack information and service attribute information into the OSU frame, where the service attribute information is used to instruct each node on the service path to configure resources for the service.
  • the sending unit 1520 is used for sending the OSU frame.
  • the apparatus 1500 may further include a receiving unit 1530, and before the processing unit 1510 obtains the routing label stack information of the service path, the receiving unit 1530 is configured to receive the sending request of the data frame;
  • the processing unit 1510 is further configured to calculate a path for transmitting the service according to the routing request, which may include a service path, a protection path, and a restoration path.
  • the processing unit 1510 is further configured to convert the first path into the routing label stack information.
  • the processing unit 1510 is further configured to establish a connection for the service at the physical level according to the first label in the routing label stack information; and, according to the service attribute information: The service configures resources at the physical level.
  • the processing unit 1510 is further configured to preconfigure the mapping relationship between the OSU frame and the optical data unit frame ODUk.
  • the apparatus 1500 corresponds to the node A in FIG. 5 , and specifically may be a service head node, and may perform the actions performed by the node A in FIG. 5 and the method flowchart shown in FIG. 9 .
  • the apparatus 1500 corresponds to the node A in FIG. 5 , and specifically may be a service head node, and may perform the actions performed by the node A in FIG. 5 and the method flowchart shown in FIG. 9 .
  • the sending unit 1520 and the receiving unit 1530 of the apparatus 1600 can form a transceiver unit, and have the functions of receiving and sending at the same time.
  • the processing unit 1510 may specifically include a channel-associated signaling control unit and a service configuration control unit, and the processing unit may be at least one processor.
  • the sending unit 1520 may be a transmitter or an interface circuit
  • the receiving unit 1530 may be a receiver or an interface circuit. The receiver and transmitter can be integrated together to form a transceiver or interface circuit.
  • the apparatus 1500 may further include a storage unit for storing data and/or signaling.
  • the processing unit 1510, the sending unit 1520, and the receiving unit 1530 may interact or couple with the storage unit, for example, read or call the data in the storage unit. data and/or signaling so that the methods of the above-described embodiments are performed.
  • the above units may exist independently, or may be integrated in whole or in part.
  • FIG. 16 is a schematic diagram of an apparatus 1600 for service routing provided by the present application.
  • the apparatus 1600 includes a receiving unit 1610 and a processing unit 1620 . in,
  • the receiving unit 1610 is configured to receive an OSU frame, where the OSU frame carries routing label stack information, and the routing label stack information is used to instruct each node on the service path to establish a channel for transmitting the service.
  • the processing unit 1620 is configured to obtain the routing label stack information and the service attribute information from the OSU frame, and specifically, obtain a second label from the OSU frame in a stack manner, and the second label is specifically used. instructing the network device to establish a channel for transmitting the service; or, the processing unit 1620 obtains the second label from the OSU frame in a pointer manner;
  • routing label stack information for example, establishing a connection for the service at the physical level according to the second label
  • the apparatus 1600 may further include a sending unit 1630, configured to forward the OSU frame to other network devices after the processing unit 1620 obtains the second label from the OSU frame, where the other network device is the network device in the service path. on the downstream network devices.
  • a sending unit 1630 configured to forward the OSU frame to other network devices after the processing unit 1620 obtains the second label from the OSU frame, where the other network device is the network device in the service path. on the downstream network devices.
  • the processing unit 1620 is further configured to preconfigure the mapping relationship between the OSU frame and the second optical data unit frame.
  • the apparatus 1600 corresponds to the node B in FIG. 5 , and may specifically be an intermediate node or an end node of a service path, and can perform the actions performed by the node B and the node C in FIG. 5 and the method flowchart shown in FIG. 10 .
  • the apparatus 1600 corresponds to the node B in FIG. 5 , and may specifically be an intermediate node or an end node of a service path, and can perform the actions performed by the node B and the node C in FIG. 5 and the method flowchart shown in FIG. 10 .
  • the receiving unit 1610 and the sending unit 1630 of the apparatus 1600 may form a transceiver unit, and have the functions of receiving and sending at the same time.
  • the processing unit 1620 may specifically include a channel-associated signaling control unit and a service configuration control unit, and the processing unit 1620 may be at least one processor.
  • the sending unit 1630 may be a transmitter or an interface circuit, and the receiving unit 1610 may be a receiver or an interface circuit. The receiver and transmitter can be integrated together to form a transceiver or interface circuit.
  • the apparatus 1600 may further include a storage unit for storing data and/or signaling.
  • the receiving unit 1610, the processing unit 1620, and the sending unit 1630 may interact or couple with the storage unit, for example, read or call the data in the storage unit. data and/or signaling so that the methods of the above-described embodiments are performed.
  • the above units may exist independently, or may be integrated in whole or in part.
  • FIG. 17 is a schematic structural diagram of an apparatus 1700 for service routing provided by an embodiment of the present application.
  • the apparatus 1700 includes a processor 1710, the processor 1710 is coupled with a memory 1720, the memory 1720 can be used to store computer programs or instructions or/or data, the processor 1710 is used to execute the computer programs or instructions and/or data stored in the memory 1720, The methods in the above method embodiments are caused to be executed.
  • the traffic routing apparatus 1700 further includes a transceiver 1730 for receiving and/or transmitting signaling.
  • the apparatus 1700 includes one or more processors 1710 .
  • the apparatus 1500 further includes a memory 1720 .
  • the number of memories 1720 included in the service protection apparatus 1700 may be one or more.
  • the memory 1720 may be integrated with the processor 1710, or provided separately.
  • the processor 1710 is configured to implement the relevant operations performed by the node processing unit in the above method embodiments.
  • Embodiments of the present application further provide a computer program product, which, when executed by a computer, enables the computer to implement the methods executed by the first node, the intermediate node, or the last node in the above method embodiments, respectively.
  • Embodiments of the present application further provide a communication system, where the communication system includes the network devices and nodes in the above embodiments.
  • Computer-readable storage media corresponds to tangible media, such as data storage media, or communication media including any medium that facilitates transfer of a computer program from one place to another (e.g., according to a communication protocol).
  • a computer-readable storage medium may generally correspond to (1) a non-transitory, tangible computer-readable storage medium, or (2) a communication medium, such as a signal or carrier wave.
  • Data storage media can be any available media that can be accessed by one or more computers or one or more processors to retrieve instructions, code and/or data structures for implementing the techniques described in this application.
  • the computer program product may comprise a computer-readable storage medium.
  • such computer-readable storage media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage devices, magnetic disk storage devices or other magnetic storage devices, flash memory, or other forms of memory that may be used to store instructions or data structures. desired program code and any other medium that can be accessed by a computer. Also, any connection is properly termed a computer-readable medium. For example, if a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave are used to transmit instructions from a website, server, or other remote source, then the coaxial cable Wire, fiber optic cable, twisted pair, DSL or wireless technologies such as infrared, radio and microwave are included in the definition of media.
  • DSL digital subscriber line
  • computer-readable storage media and data storage media do not include connections, carrier waves, signals, or other transitory media, but are instead directed to non-transitory, tangible storage media.
  • magnetic disks and optical disks include compact disks (CDs), laser disks, optical disks, digital versatile disks (DVDs), and Blu-ray disks, where disks typically reproduce data magnetically, while disks reproduce optically with lasers data. Combinations of the above should also be included within the scope of computer-readable media.
  • DSPs digital signal processors
  • ASICs application specific integrated circuits
  • FPGAs field programmable logic arrays
  • DSPs digital signal processors
  • ASSICs application specific integrated circuits
  • FPGAs field programmable logic arrays
  • processor may refer to any of the foregoing structure or any other structure suitable for implementation of the techniques described herein.
  • functionality described by the various illustrative logical blocks, modules, and steps described herein may be provided within dedicated hardware and/or software modules configured for encoding and decoding, or incorporated in a combined codec in the device.
  • the techniques may be fully implemented in one or more circuits or logic elements.
  • the term "and/or” in this application is only an association relationship to describe associated objects, which means that there can be three kinds of relationships, for example, A and/or B, which can mean that A exists alone, and A and B exist at the same time. , there are three cases of B alone.
  • the character "/" in this document generally indicates that the contextual object is an "or” relationship; the term “at least one” in this application can mean “one” and "two or more", for example, A At least one of , B, and C can mean: A alone exists, B exists alone, C exists alone, A and B exist simultaneously, A and C exist simultaneously, C and B exist simultaneously, and A and B and C exist simultaneously. seven situations.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computing Systems (AREA)
  • Physics & Mathematics (AREA)
  • Electromagnetism (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请实施例提供一种数据帧的发送方法和网络设备，包括：第一节点获取第一路径的路由标签栈信息，第一路径用于传输业务，路由标签栈信息用于指示第一路径上各节点建立业务在第一路径各节点上的通道；第一节点将路由标签栈信息和业务属性信息插入第一数据帧的净荷区，业务属性信息用于指示所述第一路径上各节点为所述业务配置资源；第一节点发送第一数据帧。上述方法通过在数据帧的净荷区中携带路由标签栈信息和业务属性信息，可以将业务路由信息快速传至业务路径的各个节点，用于各个节点快速建立传输业务的通道并且为业务配置资源，从而缩短路由时间。

Description

一种数据帧的发送方法和网络设备
本申请要求于2020年9月27日提交中国国家知识产权局、申请号为202011032653.X、申请名称为“一种数据帧的发送方法和网络设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明涉及光网络技术领域，特别涉及一种数据帧的发送方法和网络设备。
发明背景
自动交换光网络(ASON)是由国际电信联盟(ITU)定义的基于分布控制平面且支持动态交换连接的光网络。ASON利用独立的控制平面，通过各种传送网来实施自动连接管理。ASON支持网络带宽的动态分配和调度连接，可依据客户层信息如：IP数据业务量等的变化，有效地优化网络。与传统光网络相比，对于同样的网络业务需求，ASON可以大大降低建网成本，提高带宽利用率，还可以提供分布式的网络恢复，极大地提高网络的可靠性。
ASON网络目前已基本覆盖城域、核心骨干等波分网络。在ASON网络中，每个ASON节点通过开放最短路径优先(Open Shortest Path First，OSPF)协议获取全网其它节点的信息，包括节点数据和链路数据等，然后通过基于约束的最短路径优先算法(Constrained Shortest Path First，CSPF)计算端到端的业务路径，最后再通过RSVP-TE完成端到端业务路径的建立。网络断纤后可通过通用多协议标签交换(Generalized Multi-Protocol Label Switching，GMPLS)以及基于流量工程扩展的资源预留协议(Resource Reservation Protocol-Traffic Engineering，RSVP-TE)自动建立端到端恢复路径，为业务提供实时重路由保护恢复能力。
对于城域/核心ASON网络，当需要通过RSVP-TE协议建立业务，首先将RSVP Path消息封装成IP报文，再将IP报文映射到数据帧的开销字节。每个中间节点需要逐个节点解出IP报文，耗时长，且占用开销多，建路速度慢。
发明内容
为了解决业务路由速度慢，占用开销多的问题，本申请实施例提供一种数据帧的发送方法和网络设备。
第一方面，本申请实施例提供一种数据帧的发送方法，所述方法包括：第一节点获取第一路径的路由标签栈信息，第一路径用于传输业务，路由标签栈信息用于指示第一路径上各节点建立业务在第一路径各节点上的通道；第一节点将路由标签栈信息和业务属性信息插入第一数据帧，业务属性信息用于指示第一路径上各节点为业务配置资源；第一节点发送第一数据帧。
本申请提供的方案，通过在灵活的数据帧中携带路由标签栈信息和业务属性信息，可以将业务路由信息快速传至业务路径的各个节点，用于各个节点建立业务的通道并且为业务配置资源，从而缩短路由时间，并且仅通过OSU帧控制信令完成数据帧的发送过程，无需占用 高阶数据帧的过多开销，从而提高网络的传输效率。
结合第一方面，在一种可能的实现方式中，路由标签栈信息包括多个标签，多个标签中的每一个标签与第一路径上各节点传输业务的通道一一对应，对应关系预先配置在第一路径上各节点中。通过将路由标签与各节点上业务的通道一一对应，并将对应关系预先配置在各节点中，可以减少报文内容，提高传输效率，同时各节点在获取路由标签栈信息后，可以根据本节点的标签与业务通道的对应关系完成交叉连接的建立，提高数据帧的发送速度。
结合第一方面，在一种可能的实现方式中，所述路由标签栈信息可以只包含一个全局标签，第一节点或者第一路径上的其他节点获取该全局标签后，根据该全局标签完成业务通道的建立。
结合第一方面，在另一种可能的实现方式中，业务属性信息包括以下信息中的一项或多项：业务标识ID、带宽、时延、源节点标识ID、宿节点标识ID、业务路径属性。其中，业务路径属性信息可以包括工作路径属性、保护路径属性、重路由路径属性。
结合第一方面，在一种可能的实现方式中，该第一数据帧为灵活光业务单元帧，长度为192字节。
结合第一方面，在一种可能的实现方式中，净荷区还包括标签数量，标签数量用于标识第一路径上接收路由标签栈信息和业务属性信息的节点数。在净荷区携带标签数量，可以使每个节点知道剩余待转发的节点数，当第一数据帧转发至末节点时，可以判断不需继续进行转发，从而节省路由时间。
结合第一方面，在一种可能的实现方式中，第一数据帧的开销区还包括信令类型Type字段，Type字段用于指示所述第一数据帧为控制帧及具体控制类型。通过在开销区预留信令类型Type字段，可以标识当前第一数据帧为控制帧，用于数据帧的发送过程，具体可以包括建路、1+1保护、重路由等情景，从而与传输业务的数据帧区别开来，方便网络管理。
结合第一方面，在一种可能的实现方式中，Type字段用于指示所述第一数据帧为业务创建控制帧；或者，Type字段用于指示所述第一数据帧为业务1+1保护创建控制帧；或者，Type字段用于指示所述第一数据帧为业务重路由控制帧。
需要说明的是，Type字段还可以用于指示所述第一数据帧为业务删除控制帧。当Type字段用于指示所述第一数据帧为业务删除控制帧时，第一数据帧可以仅携带业务删除控制信令标识(Type字段)和业务ID即可，路由标签栈信息可以选带；而且第一数据帧可以随业务数据流直接转发，不需要根据第一数据帧携带的路由标签栈信息获取出端口进行转发。
结合第一方面，在一种可能的实现方式中，Type字段用于指示所述第一数据帧为业务1+1保护创建控制帧，具体可以包括：Type字段用于指示所述第一数据帧为所述业务的主用路径创建控制帧；或者，所述Type字段用于指示所述第一数据帧为所述业务的备用路径创建控制帧。
结合第一方面，在一种可能的实现方式中，第一节点获取第一路径的路由标签栈信息之前，还包括：第一节点接收数据帧的发送请求；根据路由请求计算出传输业务的第一路径；将第一路径转化为所述路由标签栈信息。这样，可以将复杂的子架、单板、端口、通道等标识号简化为标签，方便设备获取和识别，简化数据帧的发送过程。
结合第一方面，在一种可能的实现方式中，第一节点在所述第一路径上发送所述第一数据帧后，还包括，第一节点根据路由标签栈信息中的第一标签在物理层面为业务建立交叉连接；以及，第一节点根据业务属性信息为业务在物理层面配置资源。
需要说明的是，本申请中所述的物理层面可以理解为数据平面，在物理层面为业务建立 交叉连接，即通过占用设备的软件或者硬件资源为业务建立交叉连接，例如建立子架、单板、端口的交叉连接。
结合第一方面，在一种可能的实现方式中；第一节点预先配置所述第一数据帧与第一光数据单元帧的映射关系。这样，可以将数据帧的发送过程简化为交叉连接的建立和资源配置，缩短路由时间。
第二方面，本申请实施例提供一种数据帧的发送方法，包括：第二节点接收第一数据帧，第一数据帧的净荷区携带路由标签栈信息和业务属性信息，路由标签栈信息用于指示第一路径上各节点建立业务在各节点上的通道，业务属性信息用于指示第一路径上各节点为业务配置资源，其中，第一路径用于传输业务；第二节点从第一数据帧中获取路由标签栈信息和业务属性信息；第二节点根据路由标签栈信息建立第二节点传输业务的通道；根据业务属性信息为业务配置资源。
本申请提供的方案，通过在第一数据帧中携带路由标签栈信息和业务属性信息，可以将业务路由信息快速传至业务路径的各个节点，各个节点路由标签栈信息和业务属性信息建立传输业务的通道并且为业务配置资源，从而缩短路由时间，并且仅通过第一数据帧控制信令完成数据帧的发送过程，无需占用高阶数据帧的过多开销，从而提高网络的传输效率。
结合第二方面，在一种可能的实现方式中，路由标签栈信息包括多个标签，多个标签中的每一个与第一路径上各节点传输业务的通道一一对应，对应关系预先配置在第一路径上各节点中。通过将路由标签与传输业务的通道一一对应，并将对应关系预先配置在各节点中，可以减少报文内容，提高传输效率，同时各节点在获取路由标签栈信息后，可以根据本节点的标签与业务通道的对应关系完成交叉连接的建立，提高数据帧的发送速度。
结合第二方面，在另一种可能的实现方式中，业务属性信息包括以下信息中的一项或多项：业务标识ID、带宽、时延、源节点标识ID、宿节点标识ID、业务路径属性。
结合第二方面，在一种可能的实现方式中，第一数据帧为灵活光业务单元帧，该灵活光业务单元帧的长度为192字节。
结合第二方面，在一种可能的实现方式中，净荷区还包括标签数量，标签数量用于标识第一路径上接收路由标签栈信息和业务属性信息的节点数。在净荷区携带标签数量，可以使每个节点知道剩余待转发的节点数，当OSU真转发至末节点时，可以判断不需继续进行转发，从而节省路由时间。
结合第二方面，在一种可能的实现方式中，第一数据帧的开销区还包括信令类型Type字段，Type字段用于指示所述第一数据帧为控制帧及具体控制类型。通过在开销区预留信令类型Type字段，可以标识当前第一数据帧为控制帧，用于数据帧的发送过程，具体可以包括建路、1+1保护、重路由等情景，从而与传输业务的数据帧区别开来，方便网络管理。
结合第二方面，在一种可能的实现方式中，Type字段用于指示所述第一数据帧为业务创建控制帧；或者，Type字段用于指示所述第一数据帧为业务1+1保护创建控制帧；或者，Type字段用于指示所述第一数据帧为业务重路由控制帧。
结合第二方面，在一种可能的实现方式中，Type字段用于指示所述第一数据帧为业务1+1保护创建控制帧，具体可以包括：Type字段用于指示所述第一数据帧为所述业务的主用路径创建控制帧；或者，所述Type字段用于指示所述第一数据帧为所述业务的备用路径创建控制帧。
结合第二方面，在一种可能的实现方式中，第一节点获取第一路径的路由标签栈信息之前，还包括：第一节点接收业务的路由请求；根据路由请求计算出传输业务的第一路径；将 第一路径转化为所述路由标签栈信息。这样，可以将复杂的子架、单板、端口、通道等标识号简化为标签，方便设备获取和识别，简化数据帧的发送过程。
结合第二方面，在一种可能的实现方式中，第一节点在所述第一路径上发送所述第一数据帧后，还包括，第一节点根据路由标签栈信息中的第一标签在物理层面为业务建立交叉连接；以及，第一节点根据业务属性信息为业务在物理层面配置资源。
结合第二方面，在一种可能的实现方式中，第二节点从第一数据帧中获取路由标签栈信息，包括：
第二节点通过堆栈方式从第一数据帧中获取第二标签，第二标签具体用于指示所述第二节点建立传输所述业务的通道；或者，所述第二节点通过指针方式从所述第一数据帧中获取所述第二标签。
结合第二方面，在一种可能的实现方式中，第二节点从第一数据帧种获取第二标签之后，还包括：第二节点向其他节点转发第一数据帧，其他节点为第二节点在第一路径上的下游节点。
结合第二方面，在一种可能的实现方式中，第二节点根据所述路由标签栈信息建立所述第二节点传输所述业务的通道，包括：第二节点根据第二标签在物理层面为业务建立连接。
结合第二方面，在一种可能的实现方式中，所述方法还包括：第二节点根据业务属性信息在所述物理层面为所述业务配置带宽。第二节点先将第一数据帧转发给下游节点，再根据第二标签在物理层面为业务建立连接以及根据第二标签在物理层面为业务建立连接，这样可以尽快将业务路由信息传输至路径的对端，路径上各节点可以并行完成交叉连接的建立和资源配置，从而实现业务的快速路由。
结合第二方面，在一种可能的实现方式中，第二节点预先配置所述第一数据帧与第二光数据单元帧的映射关系。这样，可以将数据帧的发送过程简化为交叉连接的建立和资源配置，缩短路由时间。
第三方面，本申请实施例提供一种网络设备，包括：处理单元，用于获取第一路径的路由标签栈信息，第一路径用于传输业务，路由标签栈信息用于指示第一路径上各节点建立传输业务的通道；处理单元还用于将路由标签栈信息和业务属性信息插入光业务单元第一数据帧，业务属性信息用于指示所述第一路径上各节点为所述业务配置资源；发送单元，用于发送第一数据帧。
结合第三方面，在一种可能的实现方式中，路由标签栈信息包括多个标签，多个标签中的每一个与第一路径上各网络设备传输所述业务的通道一一对应，所述对应预先配置在所述各网络设备中。通过将路由标签与传输业务的通道一一对应，并将对应关系预先配置在各节点中，可以减少报文内容，提高传输效率，同时各节点在获取路由标签栈信息后，可以根据本节点的标签与业务通道的对应关系完成交叉连接的建立，提高数据帧的发送速度。
结合第三方面，在一种可能的实现方式中，业务属性信息包括以下信息中的一项或多项：业务标识ID、带宽、时延、源节点标识ID、宿节点标识ID。
结合第三方面，在一种可能的实现方式中，第一数据帧包括净荷区，所述路由标签栈信息和所述业务属性信息携带于所述净荷区中。通过在第一数据帧的净荷区携带路由标签栈信息和业务属性信息，可以避免占用过多开销，减少设备的提取代价，快速完成数据帧的发送。
结合第三方面，在一种可能的实现方式中，净荷区还包括标签数量字段，标签数量用于标识所述第一路径上接收所述路由标签栈信息和所述业务属性信息的节点数。
结合第三方面，在一种可能的实现方式中，第一数据帧还包括信令类型Type字段，Type 字段用于指示所述第一数据帧为控制帧及具体控制类型。通过在开销区预留信令类型Type字段，可以标识当前第一数据帧为控制帧，用于数据帧的发送过程，具体可以包括建路、1+1保护、重路由等情景，从而与传输业务的数据帧区别开来，方便网络管理。
结合第三方面，在一种可能的实现方式中，Type字段用于指示所述第一数据帧为业务创建控制帧；或者，Type字段用于指示所述第一数据帧为业务1+1保护创建控制帧；或者，Type字段用于指示所述第一数据帧为业务重路由控制帧。
结合第三方面，在一种可能的实现方式中，Type字段用于指示所述第一数据帧为业务1+1保护创建控制帧，具体可以包括：Type字段用于指示所述第一数据帧为所述业务的主用路径创建控制帧；或者，所述Type字段用于指示所述第一数据帧为所述业务的备用路径创建控制帧。
结合第三方面，在一种可能的实现方式中，所述网络设备还包括接收单元，处理单元获取第一路径的路由标签栈信息之前，接收单元用于接收数据帧的发送请求；处理单元，还用于根据路由请求计算出传输业务的第一路径；将第一路径转化为路由标签栈信息。
结合第三方面，在一种可能的实现方式中，发送单元发送所述第一数据帧后，处理单元，还用于根据路由标签栈信息中的第一标签在物理层面为业务建立连接；以及，还用于根据业务属性信息为所述业务在物理层面配置资源。
结合第三方面，在一种可能的实现方式中，处理单元预先配置所述第一数据帧与第一光数据单元帧的映射关系。
第四方面，本申请实施例提供一种网络设备，包括：接收单元，用于接收第一数据帧，第一数据帧携带路由标签栈信息，路由标签栈信息用于指示所述第一路径上各节点建立传输业务的通道；处理单元，用于从第一数据帧中获取路由标签栈信息和所述业务属性信息；还用于根据路由标签栈信息建立第二节点传输业务的通道；还用于根据业务属性信息为所述业务配置资源。
结合第四方面，在一种可能的实现方式中，路由标签栈信息包括多个标签，多个标签中的每一个与所述第一路径上各网络设备传输所述业务的通道一一对应，所述对应预先配置在所述各网络设备中。
结合第四方面，在一种可能的实现方式中，业务属性信息包括以下信息中的一项或多项：业务标识ID、带宽、时延、源节点标识ID、宿节点标识ID。
结合第四方面，在一种可能的实现方式中，第一数据帧为灵活光业务单元帧，其长度为192字节。
结合第四方面，在一种可能的实现方式中，净荷区还包括标签数量，标签数量用于标识所述第一路径上接收所述路由标签栈信息和所述业务属性信息的节点数。
结合第四方面，在一种可能的实现方式中，第一数据帧还包括信令类型Type字段，Type字段用于指示所述第一数据帧为控制帧及具体控制类型。通过在开销区预留信令类型Type字段，可以标识当前第一数据帧为控制帧，用于数据帧的发送过程，具体可以包括建路、1+1保护、重路由等情景，从而与传输业务的数据帧区别开来，方便网络管理。
结合第四方面，在一种可能的实现方式中，Type字段用于指示所述第一数据帧为业务创建控制帧；或者，Type字段用于指示所述第一数据帧为业务1+1保护创建控制帧；或者，Type字段用于指示所述第一数据帧为业务重路由控制帧。
结合第四方面，在一种可能的实现方式中，Type字段用于指示所述第一数据帧为业务1+1保护创建控制帧，具体可以包括：Type字段用于指示第一数据帧为业务的主用路径创建控制 帧；或者，Type字段用于指示第一数据帧为业务的备用路径创建控制帧。
结合第四方面，在一种可能的实现方式中，所述处理单元从所述第一数据帧中获取所述路由标签栈信息，是指：处理单元通过堆栈方式从第一数据帧中获取第二标签，所述第二标签具体用于指示网络设备建立传输业务的通道；或者，处理单元通过指针方式从第一数据帧中获取所述第二标签。
结合第四方面，在一种可能的实现方式中，网络设备还包括发送单元，处理单元从所述第一数据帧中获取第二标签之后，发送单元用于：向其他网络设备转发第一数据帧，其他网络设备为所述网络设备在第一路径上的下游网络设备。
结合第四方面，在一种可能的实现方式中，处理单元具体用于，根据第二标签在物理层面为所述业务建立连接。处理单元还用于，根据业务属性信息在物理层面为业务配置带宽。
结合第四方面，在一种可能的实现方式中，处理单元预先配置第一数据帧与第二光数据单元帧的映射关系。
第五方面，本申请实施例提供一种计算机程序产品，该计算机程序被计算机执行时，使得该计算机可以分别实现上述如第一方面及结合第一方面任一种可能的实现方式、第二方面及结合第二方面任一种可能的实现方式中的方法。
第六方面，本申请实时例还提供一种计算机可读存储介质，存储有计算机程序或指令、所述程序或指令被运行时会驱动设备执行如第一方面及结合第一方面任一种可能的实现方式、第二方面及结合第二方面任一种可能的实现方式中所述的方法。
第七方面，本申请实施例还提供一种通信系统，该通信系统包括上文实施例中的网络设备和节点。
附图说明
为了更清楚地说明本申请实施例或背景技术中的技术方案，下面将对本申请实施例或背景技术中所需要使用的附图进行说明。
图1为本申请实施例的ASON网络架构示意图；
图2为本申请实施例的一种OSU帧结构示意图；
图3为一种数据帧的发送方法示意图；
图4为本申请实施例提供的一种ASON网络的节点配置示意图；
图5为本申请实施例提供的一种数据帧的发送方法的系统时序图；
图6为本申请实施例提供的一种OSU帧的信令格式示意图；
图7为本申请实施例提供的一种通过堆栈方式获取标签的流程示意图；
图8为本申请实施例提供的一种通过指针方式获取标签的流程示意图；
图9为本申请实施例提供的一种业务路由方法的流程图；
图10为本申请实施例提供的另一种业务路由方法的流程图；
图11为本申请实施例提供的一种业务路由方法能够应用的场景图；
图12为本申请实施例提供的另一种业务路由方法能够应用的场景图；
图13为本申请实施例提供的又一种业务路由方法能够应用的场景图；
图14为本申请实施例提供的又一种业务路由方法能够应用的场景图；
图15为本申请实施例提供的一种业务路由装置的结构示意图；
图16为本申请实施例提供的另一种业务路由装置的结构示意图；
图17为本申请实施例提供的另一种业务路由装置的结构示意图。
具体实施方式
本申请实施例的技术方案可以应用于ASON中，为了方便理解本申请实施例的技术方案，以下对本申请实施例中使用的部分术语和技术作简单介绍。
1、节点
用于表示网络中一个独立的硬件实体，一般为一个传送网设备，如在图1中有四个节点：分别为节点1、节点2、节点3、节点4。
应理解，图1所示的ASON只是一种举例，对本申请的保护范围不构成任何的限定。ASON中包括的节点个数可以为4个节点以上，或者ASON中包括的节点个数还可以为大于或者等于2个。
2、接口
节点上用于发送并接收网络协议消息和流量数据的物理端口，如在图1中有8个接口：分别为接口1、接口2、接口3、接口4、接口5、接口6、接口7和接口8。其中，接口#1和接口#8为节点#1的物理端口、接口#2和接口#3为节点#2的物理端口、接口#4和接口#5为节点#3的物理端口、接口#6和接口#7为节点#4的物理端口。
本申请中，接口也可以称为端口，例如入端口、出端口等。需要说明的是，本申请中的节点上的端口具有三层含义：1)通道，例如入端口1—出端口1表示数据从入端口1进入节点，然后从出端口1发出，表示数据的通道；2)波长，数据从特定端口发出表示该数据以与该端口对应的波长发出；3)与OTN帧的映射关系，灵活的数据帧在发送前需要先以一定的方式映射到光数据单元ODUk的净荷区，数据从特定端口发出表示承载该数据的灵活数据帧以特定的映射关系映射到ODUk帧净荷区的特定位置，然后通过该ODUk帧发出。
3、链路
本申请实施例中，相邻的两个节点之间的连接称为链路。一个链路可以用链路(节点-接口，节点-接口)表示，相邻的两个节点之间是否存在链路可以用于表明网络协议消息和/或流量数据等信息是否能够在该两个相邻的节点之间转发，例如，若相邻的两个节点之间存在链路，则网络协议消息和/或流量数据等信息能够在该两个相邻的节点之间转发；同理，若相邻的两个节点之间不存在链路，则网络协议消息和/或流量数据等信息不能够在该两个相邻的节点之间转发。
例如，链路(节点1-接口1，节点2-接口2)表示网络协议消息和/或流量数据等信息能够从节点1的接口1发出后，在节点2和接口2上被收到。
图1所示的ASON中有8条链路：链路1-2(节点1-接口1->节点2-接口1)、链路1-4(节点1-接口8->节点4-接口7)、链路2-1(节点2-接口2->节点1-接口1)、链路2-3(节点2-接口3->节点3-接口4)、链路3-2(节点3-接口4->节点2-接口3)、链路3-4(节点3-接口5->节点4-接口6)、链路4-3(节点4-接口6->节点3-接口5)、链路4-1(节点4-接口7->节点1-接口8)。
4、业务
用于表示两个节点之间的物理通道连接建立，数据流量能够从源节点发送并在宿节点收到。如在图1中有业务1-3，表示节点1到节点3之间有一条可连接的数据通道。
需要说明的是，在本申请中除特殊说明，通道一般表示物理通道，例如业务通道表示业 务源节点和业务宿节点之间的物理通道，业务在节点上的通道可以表示业务在该节点上从入端口到出端口之间的交叉连接关系，或者可以表示光层的波长通道，本申请对此不进行限定。
ASON网络通过RSVP-TE协议可提供业务的快速端到端建立、查询、删除、属性修改和恢复功能。网管下发业务创建命令到源节点网元，然后源节点网元实现路由计算并通过RSVP-TE信令协议发起业务配置过程，从源节点到下游节点逐点建立交叉连接，从而完成业务的创建。该方式充分利用了各个网元的路由和信令功能，缩短了业务配置时间。如在图1中，业务1-3信令RSVP-TE建路的具体步骤如下：源节点1通过CSPF(Constrained Shortest Path First,基于约束的最短路径优先)计算好业务路径：节点1-节点2-节点3，源节点沿着计算好的路径，携带着端到端的路径信息，指定链路1-2接口向中间节点2发送Path消息(RSVP-TE协议报文的一种)，节点2收到信令消息后，解出本节点交叉配置关联信息并建立反向交叉连接，再由中间节点2携带端到端路径消息指定链路2-3接口向宿节点3方向发送Path消息，同理在宿节点3解出对应交叉配置消息并建立本站反向交叉连接；宿节点3经由中间节点2向源节点1方向发送Resv消息(RSVP-TE协议报文的一种)，在沿途各节点建立正向交叉连接；同样过程源节点1经由中间节点2向宿节点3方向发送Path消息，沿途打开对业务的告警监视，宿节点3经由中间节点2向源节点1方向发送Resv消息进行确认。整个过程由RSVP-TE信令自动完成业务1-3的端到端配置建立。
在静态网络中，业务的建立是通过网管进行手工单站配置建立、删除、查询和属性修改，无法做到端到端自动化过程。如图1所示，如果通过网管创建业务1-3，首先需要人工规划出业务路径节点1-节点2-节点3，然后逐个节点进行单站交叉配置，待所有节点交叉配置完成后，业务1-3完成端到端建立。整个过程需要人工分别进行单站配置以建立业务，效率很低。
5、业务路径
业务路径可以包括工作路径、恢复路径、保护路径等，用于承载业务的数据传输。业务路径为首节点到末节点之间的路由，首节点和末节点之间可能存在一个或多个节点。其中，业务路径的首节点表示业务数据的发送节点、业务路径的末节点表示业务数据的接收节点。一个业务路径可以用业务(首节点-末节点)表示。
由于业务路径表示首节点到末节点之间的路由，也可以称之为端到端业务路径，其中，“端到端”表示首节点到末节点。
另外，ASON通过RSVP-TE协议可提供业务路径的端到端建立、查询、删除、属性修改和恢复功能。业务路径的端到端建立包括：网管下发业务路径创建命令到首节点，然后首节点实现路由计算并通过RSVP-TE信令协议发起业务路径配置过程，从首节点到下游节点逐点建立交叉连接，从而完成业务路径的端到端建立。
本申请中的业务路径既包括工作路径，也包括保护路径。业务路径的切换(或者倒换)可以表示业务从工作路径切换到保护路径，或者，表示业务从保护路径重新切换回工作路径。
6、灵活光业务单元帧
光传送网络(optical transport network，OTN)由于具备高带宽，大容量，高可靠，低时延等特性，已经成为传送网采用的主流技术。OTN可以应用于骨干、城域核心及汇聚等网络，也进一步向接入网扩展。OTN网络中使用的数据帧结构是OTN帧，OTN帧也可以称为OTN传输帧。OTN帧用于承载各种业务数据，并提供丰富的管理和监控功能。OTN除了能够提供n*1.25Gbps、n*5Gbps等大带宽传送能力外，未来还需要具备低至几兆比特每秒的传送能力。
Liquid OTN是在传统的OTN帧结构基础上引入了面向业务的灵活容器——灵活光业务单元帧(flexible optical service unit，OSUflex)，通过灵活的管道带宽定义(如n*2.4Mbit/s，n 表示管道个数)，实现高效承载小颗粒信号。OSUflex改变了原有的封装大小，能够直接映射到高阶光数据单元(optical data unit k，ODUk)管道上，其中k代表了不同的速率等级，例如，k＝1表示2.5Gbps，k＝4表示100Gbps。
在本申请实施例中，OTN帧可以是OSUflex帧，OSUflex帧也可以简称为OSU帧。图2是本申请实施例提供的一种OSU帧的结构示意图。如图2所示，光净荷单元帧(optical payload unit-k，OPUk)或OPUflex被划分为多个净荷块(Payload Block，PB)，每个PB包含OSU帧和与之对应的索引号TPN。当多路OSU帧映射到OPUk/Flex帧时，TPN可以作为OSU帧在服务层的唯一通道标识。每个OSU帧包括开销区和净荷区两部分，开销区包括但不限于信令类型、版本标识、校验比特等开销信息，净荷区用于承载业务数据信息。OSU帧的长度一般为固定大小，例如长度为192字节、240字节、128字节或者64字节等。
下面将进一步结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述。其中，在本申请的描述中，除非另有说明，“/”表示或的意思，例如，A/B可以表示A或B；本文中的“和/或”仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。并且，在本申请的描述中，除非另有说明，“多个”是指两个或多于两个。另外，为了便于清楚描述本申请实施例的技术方案，在本申请的实施例中，采用了“第一”、“第二”等字样对功能和作用基本相同的相同项或相似项进行区分。本领域技术人员可以理解“第一”、“第二”等字样并不对数量和执行次序进行限定，并且“第一”、“第二”等字样也并不限定一定不同。
本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
随着网络业务的多元化发展，VR游戏、视频业务等场景对网络性能的要求越来越高。针对VR游戏、视频业务等场景，用户通过公网预先获得VR渲染云服务地址，然后启动游戏/视频时按需发起建立管道连接。为了减少等待时间，从而提升用户体验，通常建立管道连接的时间应该越短越好。
图3是一种数据帧的发送方法。业务首节点首先将RSVP Path消息封装为IP报文，然后将IP报文映射到数据通信网络(Data communication network，DCN)。例如，将IP报文映射到光传送网(optical transport network，OTN)数据帧的通用通信信道(general communication channel，GCC)开销字节。每个中间节点均需要逐个节点解出IP报文，并根据IP报文为业务建路或者进行重路由。此过程耗时长，同时由于可用开销太少，因此传输速度较慢，导致业务配置效率低，性能差。
为了提高网络的业务建立和恢复速度，提升用户体验，本申请实施例提供了一种数据帧的发送方法和网络设备，基于OSU帧随路控制信令实现业务的快速建立和/或重路由，从而提升网络性能。
需要说明的是，本申请实施例中所述的数据帧的发送方法，既包括业务的工作路径建路过程，也可以包括业务的1+1保护路径的建立过程，还可以包括业务的工作路径出现故障后进行重路由的过程。因此，本申请中的路由表示业务路径的端到端建立。
图4是本申请实施例的一种ASON网络的节点配置示意图。如图4所示，该架构包括智能化网管(Network Cloud Engine，NCE)、节点A、节点B及节点C。其中每个节点均部署业务配置控制单元和随路信令控制单元。
该ASON架构还包括用于路径计算的网络设备。示例性地，该网络设备包括路径计算单元(Path computation element，PCE)控制器，即该ASON中设置有至少一个PCE控制器。或者，该网络设备为具备路径计算功能的节点，例如，该ASON中至少一个节点部署有PCE控制器；还例如，该ASON中至少一个节点部署有路径计算功能模块。
其中，NCE用于业务的自动发放和删除。
当节点A为业务首节点时，可以包括PCE控制器。NCE或者PCE控制器具体用于：预先将设备光口上所有OSU帧管道与光通道数据单元(optical data unit k，ODUk)管道映射关系配置完成，从而将OSU帧随路业务简化为业务路径的交叉连接和带宽配置。
业务配置控制单元用于业务路径的建立、删除、更新及重建；还用于单站业务交叉连接的建立和资源配置。
随路信令控制单元用于对OSU帧的随路控制信令进行处理，包括业务的创建控制信令和删除控制信令。
应理解，图4只是为了便于理解本申请而提供的一种示意图，对本申请的保护范围不构成任何的限定，上述的各种单元的名称也只是举例，其他能够实现相同功能的单元或模块替代图4中所示的单元。
图5是本申请实施例提供的一种数据帧的发送方法的系统时序图，可以应用于ASON网络中，该网络可以包括如图4所示的多个节点。
本实施例以单条业务通过OSU帧随路控制信令建路为例进行说明。本实施例将具有路径计算功能的节点和PCE控制器统称为网络设备，网络设备可以通过路径计算获得承载业务的工作路径。例如，业务的工作路径包括首节点A、中间节点B以及末节点C，其中首节点A与网络设备之间可以通过通信协议进行信息交互。需要说明的是，网络设备可以是业务的首节点。
图5中数据帧的发送方法至少包括以下步骤中的全部或者部分步骤：
S510：网络设备进行OTN映射关系和路由标签预配置。
具体地，在业务创建之前，网络设备预先配置OSU帧与ODUk管道的映射关系。通过上述预配置，网络设备可以将业务的建路过程简化为交叉连接和资源配置，从而提高业务的配置效率。
此外，网络设备还为不同子架、单板、端口上的OSU帧通道分别分配一个路由标签，该标签用于在站节点内唯一标识传输第一业务的通道，然后将所有的路由标签分别配置到节点内。例如，每个路由标签属性为4个字节，与节点内子架、板位、端口及通道号一一对应。同时，网络设备可以将各节点的路由标签存储在设备内。
S520：节点A向网络设备发送路径计算请求，
节点A为业务的首节点，当节点A接收到业务的创建请求后，请求网络设备计算业务的承载路径。
S530：网络设备计算得到业务的工作路径，并将工作路径转换为路由标签栈信息。
本申请实施例中，网络设备能够获取网络中的业务和拓扑，然后根据全网路由TE和带宽信息确定承载业务的工作路径，之后再将所述工作路径转化为路由标签栈信息。所述路由标签栈信息用于指示所述工作路径上各节点建立传输业务的通道。具体地，所述路由标签栈信息表示标签的排序集合，可以包括一个或者多个标签，多个标签按照一定的顺序进行排列，例如可以按照每个标签的获取顺序进行排列。其中每个标签均与工作路径的节点中传输业务的通道一一对应。
示例地，网络设备确定承载第一业务的路径为第一路径，其中第一路径包括业务所经过的节点和节点内的业务通道信息，例如第一路径为：节点A(子架1-板位1-端口1-通道1)—节点B(子架2-板位2-端口2-通道2)—节点C(子架3-板位3-端口3-通道3)。然后，网络设备将所述第一路径转化为路由标签栈信息，例如，节点A(第一标签)—节点B(第二标签)—节点C(第三标签)。
需要说明的是，本申请实施例中的建立表示节点中的业务通道为可用/激活状态，或者更具体地，建立表示节点内传输业务的通道的交叉已建立完成。
S540：网络设备将路由标签栈信息下发给节点A。
示例地，网络设备通过路径计算单元通信协议(Path Computation Element Communication Protocol，PCEP)消息将路由标签栈信息下发给节点A。或者，网络设备通过与PCEP具有相同功能的协议消息将路由标签栈信息下发给节点A。具体地，网络设备通过与节点A之间原有信令中新增的字段(例如，扩展PCEP字段)将路由标签栈信息下发给节点A。
基于网络设备在网络中的身份，分为以下两种方式：
方式一：网络设备为PCE
网络设备网络中设置的PCE控制器，并且该PCE控制器为独立于上述的工作路径的首节点部署的设备。则在方式一中，网络设备将工作路径转换为路由标签栈信息后，需要将该路由标签栈信息下发给业务首节点A。
示例地，上述路由标签栈信息可以是一条消息也可以是多条消息的统称，即路由标签栈信息可以通过一条消息发送给首节点A，也可以通过多条消息发送给首节点A。
方式二：网络设备是业务的首节点。
上述网络设备如果是业务的首节点A，那么节点A可以自行计算获得工作路径的路由信息，并将工作路径的路由信息转换为路由标签栈信息。与上述方式一不同的是方式二中网络设备无需向首节点发送路由标签栈信息，即无需执行S540。
S550：节点A获取业务路径的路由标签栈信息，并将路由标签栈信息和业务属性信息插入第一数据帧的净荷区。
节点A从协议消息中获取路由标签栈信息，并将该路由标签栈信息插入第一数据帧的净荷区字段中。此外，节点A还可以将业务属性信息插入第一数据帧的净荷区字段中，用于指示业务路径上的节点为业务配置物理资源。所述业务属性信息包括以下至少一项信息：业务标识ID、带宽、时延、源节点标识ID、宿节点标识ID、业务路径属性。其中，业务路径属性表示第一数据帧帧的控制类型，例如，当前通过第一数据帧建立的路径为业务工作路径，或者是业务保护路径，或者是重路由路径。
例如，第一数据帧具体可以是灵活光业务单元OSU帧，长度为192字节。
作为一个示例，OSU帧的信令格式可以参考图6。如图6所示，该OSU帧的长度为192字节，其中开销区包含7个字节，净荷区包含185个字节。在OSU帧的开销区预留12比特Label，用于标识该OSU帧的通道号，例如，Label标识该业务在节点A上的通道：入端口1—出端口1，节点A根据通道号可以直接将OSU帧在出端口1发出。需要说明的是，节点A将OSU帧在出端口1发出可以理解为该OSU帧以与该出端口对应的波长发出，以及该OSU帧先被被映射到该出端口预先配置的高阶ODUk数据帧中，然后再从该出端口1发出。从而，业务的建路过程被简化为交叉连接和资源配置，可以提高业务的配置效率。在OSU帧的开销区还预留12比特Type，Type标识OSU帧的类型为控制帧以及具体控制类型。例如，Type高4位比特1000标识该OSU帧为控制信令大类型，低8位比特00000010标识OSU帧具体 为业务建路控制类型。净荷区Payload为自定义字段，包含路由标签栈信息和业务属性信息。
净荷区可以包括Label Num、Label(list)、Source Node ID、Dest Node ID、Service ID、Bandwidth、Latency等业务属性信息。
净荷区自定义字段的具体字段含义可参考表1。
字段名 含义 取值
Label Num 端到端路由标签数量。 一个16bit位数值
Label(list) 路由标签栈信息，每个节点的Label标签，标识出接口 一个32bit位数值
Source Node ID 业务的源节点ID，标识业务的首节点 一个32bit位数值
Dest Node ID 业务的末节点ID，标识业务的末节点(可选) 一个32bit位数值
Service ID 业务ID，端到端路径唯一标识ID 一个32bit位数值
Bandwidth 业务带宽属性 一个32bit位数值
Latency 业务时延属性 一个32bit位数值
Reserved 预留字节，后续可扩展业务属性  
如表1所示，净荷区自定义字段可以包括标签数量Label Num、路由标签栈信息(list)Label(list)、源节点ID Source Node ID、宿节点ID Dest Node ID、业务标识ID Service ID、带宽Bandwidth、时延Latency等属性信息。其中标签数量表示业务路径上接收所述路由标签栈信息和所述业务属性信息的节点数量。剩余字节为预留字节，用于写入业务的其他扩展属性。示例地，业务的其他扩展属性可以是业务路径属性，业务路径属性表示当前OSU帧的具体控制类型。路由标签栈信息中的每个标签与节点传输业务的通道一一对应。例如，路由标签栈信息中的第一标签与节点A中传输业务的通道子架1-板位1-端口1-通道1对应，用于指示节点A在物理层为业务建立交叉连接，又如，路由标签栈信息中的第二标签与节点B中传输业务的通道子架2-板位2-端口2-通道2对应，用于指示节点B在物理层面为业务建立交叉连接。标签与通道之间的对应关系需要预先配置在各节点中。
需要说明的是，当净荷区包括业务路径属性时，本实施例中开销区的Type与净荷区的业务路径属性均可以用于标识OSU帧的具体控制类型，具体用哪个字段标识可以进行选择，本实施例对此不进行限制。
S560：节点A向节点B发送第一数据帧。
节点A向节点B发送第一数据帧。所述第一数据帧的净荷区携带路由标签栈信息和业务属性信息，所述路由标签栈信息可以是一个标签列表，包括多个标签，多个标签中的每一个与工作路径上各节点上业务的通道一一对应。
节点A在向节点B发送第一数据帧之前，还包括：将第一数据帧映射到高阶ODUk帧，然后将该ODUk帧发送给节点B。
节点A向节点B发送第一数据帧之后，还包括：节点A根据路由标签栈信息中的第一标签在物理层为业务建立交叉连接；以及，根据业务属性信息为业务在物理层配置资源，例如，为业务分配带宽。之所以先向节点B发送第一数据帧，再进行交叉建立和资源配置，是为了使第一数据帧尽快传输到工作路径的对端，各节点并行完成业务通道的交叉连接和资源配置，从而缩短路由时间。
S570：节点B获取第一数据帧中的路由标签栈信息和业务属性信息，将路由标签栈信息和业务属性信息转发给节点C。
本步骤具体包括：
S571：节点B获取第一数据帧中的路由标签栈信息和业务属性信息；
S572：节点B将包含该标签属性信息和业务属性信息的第二数据帧转发给节点C；
S573：节点B根据路由标签栈信息在物理层为业务建立交叉连接，并且根据业务属性信息为业务配置资源。
节点B获取路由标签栈信息和业务属性信息之后，直接先将包含标签属性信息和业务属性信息的第二数据帧转发给其下游节点，即C节点，然后再进行本节点的处理。这样做的理由是使包含路由信息的第一数据帧尽快传输到工作路径的对端，各节点并行完成业务通道的交叉连接和资源配置，从而缩短路由时间。
需要说明的是，第二数据帧可以与第一数据帧的内容相同，或者，第二数据帧比第一数据帧少了一个第二标签。为了与第一数据帧进行区分，将节点B向节点C转发的数据帧称为第二数据帧。
应理解，路由标签栈信息包括多个标签，节点B获取路由标签栈信息可以理解为获取多个标签中与节点B传输业务的通道对应的第二标签。具体地，节点B获取第二标签有两种实现方式。
方式一：堆栈方式
通过堆栈方式，第一数据帧每经过一个节点，便弹出一个标签，例如每次都弹出第一个标签，用于当前节点的业务通道的交叉建立和提供第一数据帧控制信令的转发出端口。
图7为节点通过堆栈方式获取标签的流程示意图。如图7所示，节点A向节点B发送的第一数据帧包括开销区和净荷区，其中开销区用于标识该第一数据帧为控制帧，净荷区用于携带用于建立业务通道的路由标签栈信息，例如标签数量-Label 11-Label 22-Label 33。其中标签数量表示路由标签栈信息中包含的Label的总数，Label 11对应节点A的业务通道，Label 22对应节点B的业务通道，Label 33对应节点C的业务通道。节点A的初始第一数据帧中携带三个Label，分别为Label 11、Label 22、Label 33，该初始第一数据帧在节点A处弹出第一个Label 11，用于节点A建立业务通道的交叉连接，同时该Label 11还用于指示第一数据帧的转发出端口。弹出Label 11后，Label 22成为路由标签栈信息的第一个Label，节点A继续转发该第一数据帧给节点B。该第一数据帧到达节点B，弹出当前的第一个Label 22，用于节点B建立业务通道的交叉连接，还用于指示第一数据帧的转发出端口。弹出Label 22后，Label 33称为第一个Label，也是剩下的唯一标签。节点B继续转发该第一数据帧给节点C，到达节点C后，弹出唯一Label 33，用于节点C建立业务通道的交叉连接。由于Label 33为最后一个标签，弹出后节点C识别到第一数据帧内没有剩余的Label，判断不再需要继续转发。
需要说明的是，通过堆栈方式获取标签，每个节点在获取标签后需要重新编辑报文再转发。第一数据帧第一数据帧第一数据帧。
节点通过堆栈方式获取标签，第一数据帧中的报文随着转发逐渐减少，传输速度更快。
方式二：指针方式
本方式中，路由标签栈信息中包含一个标签指针字段，用于指示当前节点需要获取的标签。如图8所示，节点A向节点B发送的第一数据帧包括开销区和净荷区，其中开销区用于标识该第一数据帧为控制帧，净荷区用于携带用于建立业务通道的路由标签栈信息，例如标签数量-Label 11-Label 22-Label 33。其中标签数量表示路由标签栈信息中包含的Label的总数，Label 11对应节点A的业务通道，Label 22对应节点B的业务通道，Label 33对应节点C的业务通道。与堆栈方式不同的是，本方式中的路由标签栈信息中包含一个Pointer，用于指示当前节点需要获取的标签。每经过一个节点，路由标签栈信息不变，指针Pointer加1。
例如，在节点A，Pointer＝1，表示节点A需要获取第一个标签Labe l1。在节点B，Pointer＝2， 表示节点B需要获取第二个标签Labe 22。在节点C，Pointer＝3，表示节点C需要获取第三个标签Labe 33。
需要说明的是，通过指针方式获取标签，每个节点所包含的路由标签栈信息相同，只是Pointer值有所变化第一数据帧第一数据帧。
节点通过指针方式获取标签，路由标签栈信息结构不变，仅需改变指针值，处理简单。
节点B将第二数据帧转发给其下游节点后，根据路由标签栈信息在物理层为业务建立交叉连接，建立传输业务的通道，并且根据业务属性信息为业务配置资源，例如为业务分配带宽。这样，可以使路由信息尽快传输到工作路径的对端，各节点并行完成业务通道的交叉连接和资源配置，从而缩短路由时间。
S580：节点C获取第二数据帧中的路由标签栈信息和业务属性信息，完成交叉连接的建立和资源配置。
需要说明的是，节点C为业务的末节点，在识别到路由标签栈信息中的标签仅剩最后一个时，即判断不再需要继续转发。节点C根据路由标签栈信息和业务属性信息分别完成交叉连接的建立和资源配置，具体过程可参考前述步骤，此处不再进行赘述。
S590：节点C向节点A发送响应消息，表示业务创建成功。
具体地，当网络设备为独立于节点A部署的其他设备时，例如PCE控制器，节点C也可以向其他设备发送响应消息。示例地，节点C向NCE发送响应消息。
图9为本申请实施例提供的一种业务路由方法的流程图。该方法的执行主体可以是图5中的节点A，即业务的首节点。
该方法至少包括以下步骤：
S910：第一节点获取第一路径的路由标签栈信息。
本实施例中，第一路径用于传输第一业务，路由标签栈信息用于指示所述第一路径上各节点建立所述第一业务在各节点上的通道。
示例地，在获取路由标签栈信息之前，还可以包括：第一节点接收第一业务的路由请求。
示例地，第一节点请求网络设备计算传输第一业务的工作路径；或者，第一节点自行计算传输第一业务的工作路径。
示例地，当地一节点计算得到传输第一业务的第一路径后，还可以包括，第一节点将第一路径转化为路由标签栈信息。
S920：第一节点将路由标签栈信息和业务属性信息插入第一数据帧的净荷区。
所述业务属性信息用于指示第一路径上的各节点为第一业务配置资源，包括以下信息中的一项或者多项：业务标识ID、带宽、时延、源节点标识ID、宿节点标识ID、业务路径属性。
路由标签栈信息包括多个标签，多个标签中的每一个与所述第一路径上各节点传输第一业务的通道一一对应，对应关系预先配置在所述第一路径上的各节点中。
示例地，第一数据帧可以是灵活的光业务单元OSU帧，例如，该OSU帧包括开销区overhead和净荷区Payload，二者均可以进行自定义。例如，路由标签栈信息和业务属性信息携带于净荷区中。
示例地，所述OSU帧的净荷区还包括标签数量，用于标识第一路径上接收所述路由标签栈信息和所述业务属性信息的节点数量。
示例地，OSU帧的开销区包括信令类型Type字段，所述Type字段用于指示所述OSU帧为控制帧及具体控制类型。例如，Type字段包括12个比特位，高4位比特1000标识该OSU帧为控制信令大类型，低8位比特00000010标识OSU帧具体为业务建路控制类型。例如， Type字段可以用于指示OSU帧为第一业务创建控制帧，又例如，Type字段可以用于指示所述OSU帧为第一业务1+1保护创建控制帧，再例如，Type字段还可以用于指示所述OSU帧为第一业务重路由控制帧。
示例地，当Type字段用于指示所述OSU帧为业务1+1保护创建控制帧时，包括两种情况：Type字段用于指示所述OSU帧为第一业务的主用路径创建控制帧；或者，Type字段用于指示所述OSU帧为第一业务的备用路径创建控制帧。
S930：第一节点发送所述第一数据帧。
第一节点发送所述第一数据帧后，还包括，第一节点根据所述路由标签栈信息中的第一标签在物理层面为所述业务建立连接；以及，所述第一节点根据所述业务属性信息为所述业务在所述物理层面配置资源。
图10为本申请实施例提供的一种另一种业务路由方法的流程图。该方法的执行主体可以是图5中的节点B和节点C。
该方法至少包括以下步骤：
S1010：第二节点接收第一数据帧。
所述第一数据帧的净荷区携带路由标签栈信息和业务属性信息，所述路由标签栈信息用于指示第一路径上各节点建立传输第一业务的通道，所述业务属性信息用于指示第一路径上各节点为第一业务配置资源，其中，所述第一路径为网络设备计算的用于传输第一业务的路径。
示例地，该第一数据帧为OSU帧，路由标签栈信息和业务属性信息携带于OSU帧的净荷区中。
示例地，路由标签栈信息包括多个标签，多个标签中的每一个与第一路径上各节点传输第一业务的通道一一对应，对应关系预先配置在所述第一路径上各节点中。
示例地，业务属性信息包括以下信息中的一项或多项：业务标识ID、带宽、时延、源节点标识ID、宿节点标识ID、业务路径属性。
示例地，净荷区还包括标签数量，所述标签数量用于标识第一路径上接收路由标签栈信息和业务属性信息的节点数。
示例地，OSU帧的开销区包括信令类型Type字段，所述Type字段用于指示所述OSU帧为控制帧及具体控制类型。例如，Type字段包括12个比特位，高4位比特1000标识该OSU帧为控制信令大类型，低8位比特00000010标识OSU帧具体为业务建路控制类型。例如，Type字段可以用于指示OSU帧为第一业务创建控制帧，又例如，Type字段可以用于指示所述OSU帧为第一业务1+1保护创建控制帧，再例如，Type字段还可以用于指示所述OSU帧为第一业务重路由控制帧。
示例地，当Type字段用于指示所述OSU帧为业务1+1保护创建控制帧时，包括两种情况：Type字段用于指示所述OSU帧为第一业务的主用路径创建控制帧；或者，Type字段用于指示所述OSU帧为第一业务的备用路径创建控制帧。
需要说明的是，当净荷区包括业务路径属性时，本实施例中开销区的Type与净荷区的业务路径属性均可以用于标识OSU帧的具体控制类型，具体用哪个字段标识可以进行选择，本实施例对此不进行限制。
第二节点接收OSU帧可以包括：第二节点接收包含OSU帧的ODUk帧，将该ODUk帧进行解映射，得到该OSU帧。
S1020：第二节点从所述第一数据帧中获取路由标签栈信息和业务属性信息。
应理解，路由标签栈信息包括多个标签，第二节点获取路由标签栈信息可以理解为获取多个标签中与第二节点传输第一业务的通道所对应的第二标签。
具体地，第二节点获取第二标签有两种实现方式，分别为堆栈方式和指针方式，两种方式的实现细节已在前述图6和图7中进行详细说明，此处不再进行赘述。
S1030：第二节点根据路由标签栈信息建立第二节点传输第一业务的通道；根据业务属性信息为第一业务配置资源。
示例地，第二节点的随路信令控制单元将路由标签栈信息和业务属性信息上送到业务配置控制单元，业务配置控制单元根据路由标签栈信息的第二标签找到对应的通道信息：入单板-端口-通道号，以及出单板-端口-通道号，然后进行单站业务交叉连接的建立。根据业务属性基本信息下发带宽到设备硬件生效。
图11是本申请实施例提供的业务路由方法能够应用的一种场景图。
如图11所示，该场景的应用网络为GMPLS/ASON网络，具备ASON自动化功能。图11所示的ASON网络中有A、B、C三个节点。在本实施例中，节点A、B、C均开启ASON功能，并且每个节点都部署随路信令控制装置和业务配置控制装置。全网节点、链路等网络信息通过ASON协议的OSPF或者基于流量工程的最短路径优先协议(Open Shortest Path First-Traffic Engineering，OSPF-TE)自动获取，端到端业务路径建立和恢复通过ASON协议的RSVP-TE自动建立。PCE根据OSPF或者路径计算单元通信协议(Path Computation Element Communication Protocol，PCEP)等自动获取全网节点、链路、业务信息。其中PCE主要集中处理网络业务端到端路径计算，可部署在服务器网管或类似设备中。如果网络中无PCE，网络业务端到端路径可通过分布式方式由各个节点计算。
本实施例以通过OSU帧控制信令建立端到端单条业务为例对图11进行说明。
图11所示的场景下，本申请实施例提供的业务路由方法包括以下步骤：
步骤一：
在业务创建之前，网络设备预先配置OSU帧与ODUk管道的映射关系。通过上述预配置，网络设备可以将业务的建路过程简化为交叉连接和资源配置，从而提高业务的配置效率。
此外，网络设备还为不同子架、单板、端口上的OSU帧通道分别分配一个路由标签，该标签用于在站节点内唯一标识传输第一业务的通道，然后将所有的路由标签分别配置到节点内。例如，每个路由标签属性为4个字节，与节点内子架、板位、端口及通道号一一对应。同时，网络设备可以将各节点的路由标签存储在设备内。
步骤二：
节点A收到第一业务的创建请求，于是请求网络设备计算业务路径。其中，创建请求包含第一业务的带宽信息。本申请实施例中，网络设备能够获取网络中的业务和拓扑，然后根据全网络由TE和带宽信息确定承载第一业务的工作路径，之后再将所述工作路径转化为路由标签栈信息。所述路由标签栈信息用于指示所述工作路径上各节点建立传输第一业务的通道。之后，网络设备将路由标签栈信息下发给节点A。
示例地，网络设备通过计算确定承载第一业务的路径为第一路径，其中第一路径包括业务所经过的节点和节点内的业务通道信息，例如第一路径为：节点A(子架1-板位1-端口1-通道1)—节点B(子架2-板位2-端口2-通道2)—节点C(子架3-板位3-端口3-通道3)。然后，网络设备将所述第一路径转化为路由标签栈信息，例如，节点A(第一标签)—节点B(第二标签)—节点C(第三标签)。
需要说明的是，本申请实施例中的建立表示节点中的业务通道为可用/激活状态，或者更 具体地，建立表示节点内传输业务的通道的交叉已建立完成。
还需要说明的是，如果节点A具备路径计算单元，当其收到第一业务的创建请求后，也可以自行计算业务路径。
步骤三：
节点A接收网络设备下发的路由标签栈信息。根据第一业务的创建请求，首节点A识别需要通过OSU帧控制信令进行业务创建。
节点A将该路由标签栈信息插入OSU帧的字段中。此外，节点A还可以将业务属性信息插入OSU帧的字段中，用于指示业务路径上的节点为业务配置资源。例如，所述业务属性信息包括以下信息：业务标识ID、带宽、时延、源节点标识ID、宿节点标识ID。然后，节点A向节点B发送该OSU帧。
节点A在向节点B发送OSU帧之前，还包括：对OSU帧信令报文进行封装映射，映射到高阶ODUk帧，然后将该ODUk帧发送给节点B。
节点A向节点B发送OSU帧之后，还包括：节点A根据路由标签栈信息中的第一标签在物理层为业务建立交叉连接；以及，根据业务属性信息为业务在物理层配置资源，例如，为业务分配带宽。之所以先向节点B发送OSU帧，再进行交叉建立和资源配置，是为了使OSU帧控制信令尽快传输到工作路径的对端，各节点并行完成业务通道的交叉连接和资源配置，从而缩短路由时间。
示例地，OSU帧的开销区包括12字节Type，用于标识OSU帧的类型为控制帧以及具体控制类型。例如，Type高4位比特1000标识该OSU帧为控制信令大类型，低8位比特00000010标识OSU帧具体为创建第一业务控制类型。净荷区Payload为自定义字段，携带路由标签栈信息和业务属性信息。OSU帧的报文格式及净荷区自定义字段的具体字段含义可参考前述图5所示实施例，此处不再进行赘述。
步骤四：
节点B获取路由标签栈信息和业务属性信息之后，直接先将OSU帧转发给其下游节点，即C节点，然后再进行本节点的处理。这样做的理由是使OSU帧控制信令尽快传输到工作路径的对端，各节点并行完成业务通道的交叉连接和资源配置，从而缩短路由时间。
应理解，路由标签栈信息包括多个标签，节点B获取路由标签栈信息可以理解为获取多个标签中与节点B传输业务的通道对应的第二标签。具体地，节点B获取第二标签有两种实现方式，分别为堆栈方式和指针方式，两种方式的实现细节已在前述图6和图7中进行详细说明，此处不再进行赘述。
节点B将OSU帧转发给其下游节点后，根据路由标签栈信息在物理层为业务建立交叉连接，建立传输业务的通道，并且根据业务属性信息为业务配置资源，例如为业务分配带宽。
步骤五：
节点C获取OSU帧中的路由标签栈信息和业务属性信息，完成交叉连接的建立和资源配置。节点C为业务的末节点，在识别到路由标签栈信息中的标签仅剩最后一个时，即判断不再需要继续转发。节点C根据路由标签栈信息和业务属性信息分别完成交叉连接的建立和资源配置，具体过程可参考前述步骤，此处不再进行赘述。
步骤六：
节点C向节点A发送响应消息，表示业务创建成功。
具体地，当网络设备为独立于节点A部署的其他设备时，例如PCE控制器，节点C也可以向其他设备发送响应消息。示例地，节点C向NCE发送响应消息。
图11所示的数据帧的发送方法，主要包含以下两个关键点：1)单站OTN数据帧映射关系和路由标签预配置，提前配置OSU帧管道与ODUk管道的映射关系，同时将OSU帧的管道带宽设置为0，将数据帧的发送过程简化为交叉连接和资源配置，从而提高业务的配置效率。单站配置标签与业务管道的对应关系。2)OSU帧控制信令报文先随路转发，建立业务的端到端建立，等端到端业务建立成功后，再发送数据帧，控制帧不再进行发送。
图12是本申请实施例提供的另一种业务路由方法的应用场景图。
如图12所示，该场景的应用网络为GMPLS/ASON网络，具备ASON自动化功能。图12所示的ASON网络中有A、B、C、D四个节点。在本实施例中，节点A、B、C、D均开启ASON功能，并且每个节点都部署随路信令控制装置和业务配置控制装置。全网节点、链路等网络信息通过ASON协议的OSPF或者基于OSPF-TE自动获取，端到端业务路径建立和恢复通过ASON协议的RSVP-TE自动建立。PCE根据OSPF或者PCEP等自动获取全网节点、链路、业务信息。其中PCE主要集中处理网络业务端到端路径计算，可部署在服务器网管或类似设备中。如果网络中无PCE，网络业务端到端路径可通过分布式方式由各个节点计算。
本实施例以通过OSU帧控制信令建立1+1业务为例对图12进行说明。1+1业务快速创建的原理基本同图11所示的单条业务创建基本一致，通过OSU帧控制信令先创建主工作路径使业务快速打通，然后再创建备保护路径，通过扩展业务主/备路径属性和通过唯一业务ID关联来实现主/备路径的汇聚点(即首、末节点)业务保护组的配置。
图12所示的场景下，本申请实施例提供的业务路由方法包括以下步骤：
步骤一：
在业务创建之前，网络设备预先配置OSU帧与ODUk管道的映射关系。具体配置过程可参考前述实施例，此处不再进行赘述。
步骤二：
节点A收到第一业务的1+1创建请求，于是请求网络设备计算第一业务的主备路径。示例地，网络设备通过计算确定第一业务的工作路径为：节点A(子架1-板位1-端口1-通道1)—节点B(子架2-板位2-端口2-通道2)—节点C(子架3-板位3-端口3-通道3)，确定第一业务的保护路径为：节点A(子架2-板位1-端口1-通道1)—节点B(子架3-板位2-端口2-通道2)—节点C(子架4-板位4-端口3-通道3)。
网络设备将工作路径转换为路由标签栈信息：节点A+标签1—节点B+标签2—节点C+标签3；将保护路径转换为路由标签栈信息：节点A+标签4—节点B+标签5—节点C+标签6。
网络设备将上述第一业务的工作路径路由标签栈信息和保护路径的路由标签栈信息下发给节点A。上述路由标签栈信息可以为一条消息也可以是多条消息的统称，即工作路径的路由标签栈信息以及保护路径的路由标签栈信息可以通过一条消息发送给节点A，也可以通过两条或者多条消息发送给节点A。例如，网络设备先将工作路径的路由标签栈信息下发给节点A，然后再将保护路径的路由标签栈信息下发给节点A。
步骤三：
节点A接收工作路径的路由标签栈信息以及保护路径的路由标签栈信息。节点根据第一业务的创建请求，首节点A识别需要通过OSU帧控制信令进行1+1业务创建。
节点A先将工作路径的路由标签栈信息插入第一OSU帧的Payload字段中，此外，节点A还可以将业务属性信息插入第一OSU帧的Payload字段中，用于指示工作路径上的节点为第一业务配置资源。例如，所述业务属性信息包括以下信息：业务标识ID、带宽、时延、源节点标识ID、宿节点标识ID。和/或，节点B再将保护路径的路由标签栈信息插入第二OSU 帧的字段中，同理，第二OSU帧也可以携带业务属性信息。然后。节点A将第一OSU帧和/或第二OSU帧发送至下游节点。
与前述图11所示的情景不同的是，本实施例中的业务属性信息还包括路径属性信息，用于标识当前OSU帧的具体控制类型。例如，第一OSU帧携带的业务属性信息包括路径属性信息，用于标识第一OSU帧为第一业务工作路径创建控制帧。又例如，第二OSU帧携带的业务属性信息包括路径属性信息，用于标识第二OSU帧为第一业务保护路径创建控制帧。
Payload自定义字段所包含的字段及具体含义可参考表2。
字段名 含义 取值
Label Num 端到端路由标签数量。 一个16bit位的数值
Label(list) 路由标签栈信息，每个节点的Label标签，标识出接口 一个32bit位数值
Source Node ID 业务的源节点ID，标识业务的首节点 一个32bit位数值
Dest Node ID 业务的末节点ID，标识业务的末节点(可选) 一个32bit位数值
Service ID 业务ID，端到端路径唯一标识ID 一个32bit位数值
Bandwidth 业务带宽属性 一个32bit位数值
Latency 业务时延属性 一个32bit位数值
Path Type 业务路径属性：工作/保护路径 一个8bit位数值
Reserved 预留字节，后续可扩展业务属性  
需要说明的是，OSU帧开销区中的Type也可以用于标识OSU帧的具体控制类型，占用开销区12比特，其中高4位比特用于标识控制帧大类型，低8位比特用于标识具体控制类型。
节点A在向节点B发送第一OSU帧和/或第二OSU帧之前，还包括：对第一OSU帧和/或第二OSU帧信令报文进行封装映射，映射到高阶ODUk帧，然后将该ODUk帧发送给节点B。
示例地，节点A先向节点B发送第一OSU帧，等第一业务的工作路径建立后再发送第二OSU帧。节点A先向节点B发送第一OSU帧后，还包括：节点A根据工作路径的路由标签栈信息中的第一标签在物理层为业务建立交叉连接；以及，节点A根据业务属性信息为业务在物理层配置工作路径资源，例如，为业务分配工作带宽。之所以先向节点B发送第一OSU帧，是为了快速建立业务。业务建立后，节点A再发送第二OSU帧建立第一业务的保护路径。
需要说明的是，节点A作为第一业务的首节点，在创建保护路径的交叉连接时，可以通过唯一的业务ID进行本地查找与关联，发现已建立工作路径的交叉连接，则开始创建保护路径的交叉连接，即创建业务保护组，下发至硬件生效。
本情景下的步骤四～步骤六与图11情景下的步骤四～步骤六相同，可参考前述实施例的说明，此处不再进行赘述。
图13是本申请实施例提供的另一种业务路由方法的应用场景图。
如图13所示，该场景的应用网络为GMPLS/ASON网络，具备ASON自动化功能。图13所示的ASON网络中有A、B、C、D四个节点。在本实施例中，节点A、B、C、D均开启ASON功能，并且每个节点都部署随路信令控制装置和业务配置控制装置。全网节点、链路等网络信息通过ASON协议的OSPF或者基于OSPF-TE自动获取，端到端业务路径建立和恢复通过ASON协议的RSVP-TE自动建立。PCE根据OSPF或者PCEP等自动获取全网节点、链路、业务信息。其中PCE主要集中处理网络业务端到端路径计算，可部署在服务器网管或类似设备中。如果网络中无PCE，网络业务端到端路径可通过分布式方式由各个节点计算。
本实施例以通过OSU帧控制信令进行业务的重路由为例进行说明。
图13所示的场景下，本申请实施例提供的业务路由方法包括以下步骤：
步骤一：
在业务创建之前，网络设备预先配置OSU帧与ODUk管道的映射关系。具体配置过程可参考前述实施例，此处不再进行赘述。
步骤二：
第一业务的当前工作路径为A-B-C，当第一业务创建完成，网络设备或者NCE基于全网节点和拓扑计算第一业务的恢复路径A-D-C，将恢复路径转换为路由标签栈信息下发至首节点A。首节点A存储该路由标签栈信息。
步骤三：
第一业务的工作路径上A-B出现故障，例如断纤，首节点A感知第一业务的工作路径出现故障，则直接启用本地端到端恢复路径进行业务恢复，恢复路径A-D-C。
具体地，首节点A将恢复路径的路由标签栈信息插入OSU帧的Payload字段中，此外，节点A还可以将业务属性信息插入OSU帧的Payload字段中，用于指示恢复路径上的节点为第一业务配置资源。例如，所述业务属性信息包括以下信息：业务标识ID、带宽、时延、源节点标识ID、宿节点标识ID。然后，节点A将该OSU帧发送至节点D。
需要说明的是，本实施例中的业务属性信息也包括路径属性信息，用于标识当前OSU帧的具体控制类型。与前述图12所示的情景不同的是，OSU帧携带的路径属性信息用于标识所述OSU帧为第一业务恢复路径创建控制帧，即第一业务重路由控制帧。
Payload自定义字段所包含的字段及具体含义可参考表3。
字段名 含义 取值
Label Num 端到端路由标签数量。 一个16bit位数值
Label(list) 路由标签栈信息，每个节点的Label标签，标识出接口 一个32bit位数值
Source Node ID 业务的源节点ID，标识业务的首节点 一个32bit位数值
Dest Node ID 业务的末节点ID，标识业务的末节点(可选) 一个32bit位数值
Service ID 业务ID，端到端路径唯一标识ID 一个32bit位数值
Bandwidth 业务带宽属性 一个32bit位数值
Latency 业务时延属性 一个32bit位数值
Path Type 业务路径属性：重路由路径 一个8bit位数值
Reserved 预留字节，后续可扩展业务属性  
需要说明的是，OSU帧开销区中的Type也可以用于标识OSU帧的具体控制类型，占用开销区12比特，其中高4位比特用于标识控制帧大类型，低8位比特用于标识具体控制类型。
节点A向节点B发送OSU帧后，还包括：节点A根据恢复路径的路由标签栈信息中的第一标签在物理层为业务恢复建立交叉连接；以及，节点A根据业务属性信息为业务在物理层配置恢复路径资源，例如，为业务分配恢复带宽。之所以先向节点B发送OSU帧，再进行交叉建立和资源配置，是为了使OSU帧控制信令尽快传输到恢复路径的对端，各节点并行完成业务通道的交叉连接和资源配置，从而缩短业务的重路由时间。
本情景下的步骤四～步骤六与图11情景下的步骤四～步骤六相同，可参考前述实施例的说明，此处不再进行赘述。
图14是本申请实施例提供的另一种业务路由方法的应用场景图。
如图14所示，该场景的应用网络为GMPLS/ASON网络，具备ASON自动化功能。图 14所示的ASON网络中有A、B、C、D四个节点。在本实施例中，节点A、B、C、D均开启ASON功能，并且每个节点都部署随路信令控制装置和业务配置控制装置。全网节点、链路等网络信息通过ASON协议的OSPF或者基于OSPF-TE自动获取，端到端业务路径建立和恢复通过ASON协议的RSVP-TE自动建立。PCE根据OSPF或者PCEP等自动获取全网节点、链路、业务信息。其中PCE主要集中处理网络业务端到端路径计算，可部署在服务器网管或类似设备中。如果网络中无PCE，网络业务端到端路径可通过分布式方式由各个节点计算。
本实施例以通过OSU帧控制信令进行业务的区段恢复为例对图14进行说明。
图14所示的场景下，本申请实施例提供的业务路由方法包括以下步骤：
步骤一：
在业务创建之前，网络设备预先配置OSU帧与ODUk管道的映射关系。具体配置过程可参考前述实施例，此处不再进行赘述。
步骤二：
第一业务的当前工作路径为A-B-C，当第一业务创建完成，网络设备或者NCE基于全网节点和拓扑计算第一业务的恢复路径A-B-D-C，将恢复路径转换为路由标签栈信息下发至首节点A。首节点A存储该路由标签栈信息。
步骤三：
第一业务的工作路径中的B-C链路出现故障，例如断纤，节点B感知第一业务的工作路径出现故障，查找到受影响的业务并通告至第一业务的首节点A。首节点A感知链路B-C出现故障，本地查找并匹配到第一业务对应的恢复路径A-B-D-C，则直接启用本地端到端恢复路径A-B-D-C进行业务恢复。
具体地，首节点A将恢复路径的路由标签栈信息插入OSU帧的Payload字段中，此外，节点A还可以将业务属性信息插入OSU帧的Payload字段中，用于指示恢复路径上的节点为第一业务配置资源。例如，所述业务属性信息包括以下信息：业务标识ID、带宽、时延、源节点标识ID、宿节点标识ID。然后，节点A将该OSU帧发送至节点B。
需要说明的是，本实施例中的业务属性信息也包括路径属性信息，用于标识当前OSU帧的具体控制类型。OSU帧携带的路径属性信息用于标识所述OSU帧为第一业务恢复路径创建控制帧，即第一业务重路由控制帧。
净荷区自定义字段所包含的字段及具体含义与图13场景相同，具体可参考表3，此处不再进行赘述。
需要说明的是，本实施例中工作路径与恢复路径共享A-B链路段，因此节点A的交叉连接与带宽已经配置完成，无需重复配置。
本情景下的步骤四～步骤六与图11情景下的步骤四～步骤六相同，可参考前述实施例的说明，此处不再进行赘述。
此外，本申请的业务路由方法还可以用于业务的删除。删除过程至少包括以下步骤：
步骤一：
NCE向业务首节点下发业务删除请求，例如，所述删除请求携带业务ID、源节点ID、宿节点ID等信息。
步骤二：
首节点A收到上述删除请求，根据业务ID本地获取数据帧的发送标签栈信息，将路由标签栈信息插入OSU帧的净荷区自定义字段中。此外，节点A还将业务属性信息插入OSU帧的净荷区自定义字段中。业务属性信息可以仅包括业务ID。
在OSU帧的开销区预留12比特Type，用于标识OSU帧的控制类型。例如，高4位比特1000用于标识控制帧大类型，低8位比特00000011用于标识业务删除具体控制类型。
首节点A向下游节点发送该OSU帧，由于业务已经存在，因此可以直接随数据流进行转发。从这个角度上说，路由标签栈信息可以选带。在节点A发送该OSU帧后，节点A中的业务配置控制单元根据业务ID找出与之匹配关联的业务交叉连接，下发消息至数据面删除业务通道的交叉连接。
后续步骤可参考前述业务的建路过程，主要区别在于以下两点：1)OSU帧控制信令的报文内容不同，本实施例中OSU帧可以只携带业务删除控制信令标识和业务ID即可，路由标签栈信息可以选带；2)OSU帧可以随业务数据流直接转发，不需要根据OSU帧携带的路由标签栈信息获取出端口进行转发。
上面结合图5至图14详细介绍了本申请提供的业务路由的方法，下面结合图15-图17详细介绍本申请实施例提供的业务路由的装置。
参见图15，图15为本申请提供的用于业务路由的装置1500的示意图。如图15所示，装置1500包括处理单元1510和发送单元1520。
处理单元1510，用于获取业务路径的路由标签栈信息，所述业务路径用于传输所述业务，所述路由标签栈信息用于指示所述业务路径上各节点建立传输所述业务的通道；
处理单元1510还用于将所述路由标签栈信息和业务属性信息插入OSU帧，所述业务属性信息用于指示所述业务路径上各节点为所述业务配置资源。
发送单元1520，用于发送所述OSU帧.
装置1500还可以包括接收单元1530，处理单元1510获取业务路径的路由标签栈信息之前，接收单元1530用于接收所述数据帧的发送请求；
处理单元1510，还用于根据所述路由请求计算出传输所述业务的路径，可以包括业务路径、保护路径、恢复路径。处理单元1510还用于将所述第一路径转化为所述路由标签栈信息。
发送单元1520发送所述OSU帧后，处理单元1510还用于根据所述路由标签栈信息中的第一标签在物理层面为所述业务建立连接；以及，还用于根据所述业务属性信息为所述业务在所述物理层面配置资源。
处理单元1510还用于预先配置所述OSU帧与光数据单元帧ODUk的映射关系。
装置1500与图5中的节点A对应，具体可以是业务首节点，可以执行图5中的节点A所执行的动作以及图9所示的方法流程图。具体实现细节可参考前述方法实施例，此处不再进行赘述。
装置1600的发送单元1520和接收单元1530可以组成收发单元，同时具有接收和发送的功能。其中，处理单元1510具体可以包括随路信令控制单元和业务配置控制单元，处理单元可以是至少一个处理器。发送单元1520可以是发射器或者接口电路，接收单元1530可以是接收器或者接口电路。接收器和发射器可以集成在一起组成收发器或者接口电路。
可选的，装置1500还可以包括存储单元，用于存储数据和/或信令，处理单元1510、发送单元1520以及接收单元1530可以与存储单元交互或者耦合，例如读取或者调用存储单元中的数据和/或信令，以使得上述实施例的方法被执行。
以上各个单元可以独立存在，也可以全部或者部分集成。
参见图16，图16是本申请提供的用于业务路由的装置1600的示意图。如图16所示，装置1600包括接收单元1610、处理单元1620。其中，
接收单元1610，用于接收OSU帧，所述OSU帧携带路由标签栈信息，所述路由标签栈 信息用于指示业务路径上各节点建立传输所述业务的通道。
处理单元1620，用于从所述OSU帧中获取所述路由标签栈信息和所述业务属性信息，具体地，通过堆栈方式从所述OSU帧中获取第二标签，所述第二标签具体用于指示所述网络设备建立传输所述业务的通道；或者，处理单元1620通过指针方式从所述OSU帧中获取所述第二标签；
还用于根据所述路由标签栈信息建立当前节点传输所述业务的通道，例如，根据所述第二标签在物理层面为所述业务建立连接；
还用于根据所述业务属性信息为所述业务配置资源，例如，根据所述业务属性信息在所述物理层面为所述业务配置带宽。
装置1600还可以包括发送单元1630，用于在处理单元1620从所述OSU帧中获取第二标签之后，向其他网络设备转发所述OSU帧，所述其他网络设备为所述网络设备在业务路径上的下游网络设备。
处理单元1620还用于，预先配置所述OSU帧与第二光数据单元帧的映射关系。
装置1600与图5中的节点B对应，具体可以是业务路径的中间节点或者末节点，可以执行图5中的节点B和节点C所执行的动作以及图10所示的方法流程图。具体实现细节可参考前述方法实施例，此处不再进行赘述。
装置1600的接收单元1610和发送单元1630可以组成收发单元，同时具有接收和发送的功能。其中，处理单元1620具体可以包括随路信令控制单元和业务配置控制单元，处理单元1620可以是至少一个处理器。发送单元1630可以是发射器或者接口电路，接收单元1610可以是接收器或者接口电路。接收器和发射器可以集成在一起组成收发器或者接口电路。
可选的，装置1600还可以包括存储单元，用于存储数据和/或信令，接收单元1610、处理单元1620以及发送单元1630可以与存储单元交互或者耦合，例如读取或者调用存储单元中的数据和/或信令，以使得上述实施例的方法被执行。
以上各个单元可以独立存在，也可以全部或者部分集成。
图17是本申请实施例提供的一种用于业务路由的装置1700的结构示意图。装置1700包括处理器1710、处理器1710和存储器1720耦合，存储器1720可以用于存储计算机程序或指令或者和/或数据，处理器1710用于执行存储器1720存储的计算机程序或指令和/或者数据，使得上文方法实施例中的方法被执行。
业务路由装置1700还包括收发器1730，用于信令的接收和/或发送。
可选地，该装置1700包括的处理器1710为一个或多个。
可选地，如图17所示，该装置1500还包括存储器1720。
可选地，该业务保护装置1700包括的存储器1720可以为一个或多个。
可选地，该存储器1720可以与该处理器1710集成在一起，或者分离设置。
例如，处理器1710用于实现上文方法实施例中由节点处理单元执行的相关操作。
本申请实施例还提供一种计算机程序产品，该计算机程序被计算机执行时，使得该计算机可以分别实现上述方法实施例中由首节点、中间节点或者末节点执行的方法。
本申请实施例还提供一种通信系统，该通信系统包括上文实施例中的网络设备和节点。
本领域技术人员能够领会，结合本文公开描述的各种说明性逻辑框、模块和算法步骤所描述的功能可以硬件、软件、固件或其任何组合来实施。如果以软件来实施，那么各种说明性逻辑框、模块、和步骤描述的功能可作为一或多个指令或代码在计算机可读媒体上存储或传输，且由基于硬件的处理单元执行。计算机可读存储介质对应于有形媒体，例如数据存储 媒体，或包括任何促进将计算机程序从一处传送到另一处的媒体(例如，根据通信协议)的通信媒体。以此方式，计算机可读存储介质大体上可对应于(1)非暂时性的有形计算机可读存储媒体，或(2)通信媒体，例如信号或载波。数据存储媒体可为可由一或多个计算机或一或多个处理器存取以检索用于实施本申请中描述的技术的指令、代码和/或数据结构的任何可用媒体。计算机程序产品可包含计算机可读存储介质。
作为示例，此类计算机可读存储介质可包括RAM、ROM、EEPROM、CD-ROM或其它光盘存储装置、磁盘存储装置或其它磁性存储装置、快闪存储器或可用来存储指令或数据结构的形式的所要程序代码并且可由计算机存取的任何其它媒体。并且，任何连接被恰当地称作计算机可读媒体。举例来说，如果使用同轴缆线、光纤缆线、双绞线、数字订户线(DSL)或例如红外线、无线电和微波等无线技术从网站、服务器或其它远程源传输指令，那么同轴缆线、光纤缆线、双绞线、DSL或例如红外线、无线电和微波等无线技术包含在媒体的定义中。但是，应理解，所述计算机可读存储媒体和数据存储媒体并不包括连接、载波、信号或其它暂时媒体，而是实际上针对于非暂时性有形存储媒体。如本文中所使用，磁盘和光盘包含压缩光盘(CD)、激光光盘、光学光盘、数字多功能光盘(DVD)和蓝光光盘，其中磁盘通常以磁性方式再现数据，而光盘利用激光以光学方式再现数据。以上各项的组合也应包含在计算机可读媒体的范围内。
可通过例如一或多个数字信号处理器(DSP)、通用微处理器、专用集成电路(ASIC)、现场可编程逻辑阵列(FPGA)或其它等效集成或离散逻辑电路等一或多个处理器来执行指令。因此，如本文中所使用的术语“处理器”可指前述结构或适合于实施本文中所描述的技术的任一其它结构中的任一者。另外，本文中所描述的各种说明性逻辑框、模块、和步骤所描述的功能可以提供于经配置以用于编码和解码的专用硬件和/或软件模块内，或者并入在组合编解码器中。而且，所述技术可完全实施于一或多个电路或逻辑元件中。
另外，本申请中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系；本申请中术语“至少一个”，可以表示“一个”和“两个或两个以上”，例如，A、B和C中至少一个，可以表示：单独存在A，单独存在B，单独存在C、同时存在A和B，同时存在A和C，同时存在C和B，同时存在A和B和C，这七种情况。
以上所述，仅为本申请示例性的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到的变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应该以权利要求的保护范围为准。

Claims (33)

  1. 一种数据帧的发送方法，其特征在于，包括：
    第一节点获取第一路径的路由标签栈信息，所述第一路径用于传输业务，所述路由标签栈信息用于指示所述第一路径上各节点建立所述业务在所述第一路径各节点上的通道；
    所述第一节点将所述路由标签栈信息和业务属性信息插入第一数据帧的净荷区，所述业务属性信息用于指示所述第一路径上各节点为所述业务配置资源；
    所述第一节点发送所述第一数据帧。
  2. 一种数据帧的发送方法，其特征在于，包括：
    第二节点接收第一数据帧，所述第一数据帧的净荷区携带第一路径的路由标签栈信息和业务属性信息，所述路由标签栈信息用于指示所述第一路径上各节点建立业务在所述第一路径各节点上的通道，所述业务属性信息用于指示所述第一路径上各节点为所述业务配置资源，其中，所述第一路径用于传输所述业务；
    所述第二节点从所述第一数据帧中获取所述路由标签栈信息和所述业务属性信息；
    所述第二节点根据所述路由标签栈信息建立所述业务在所述第二节点上的通道；以及，根据所述业务属性信息为所述业务配置资源。
  3. 根据权利要求1或2所述的方法，其特征在于，所述路由标签栈信息包括多个标签，所述多个标签中的每一个标签与所述第一路径上各节点的所述业务的通道一一对应，对应关系预先配置在所述第一路径上各节点中。
  4. 根据权利要求1至3任一所述的方法，其特征在于，所述业务属性信息包括以下信息中的一项或多项：业务标识ID、带宽、时延、源节点标识ID、宿节点标识ID、业务路径属性。
  5. 根据权利要求1至4任一所述的方法，其特征在于，所述第一数据帧的长度为192字节、240字节、128字节或者64字节。
  6. 根据权利要求1至5任一所述的方法，其特征在于，所述净荷区还包括标签数量，所述标签数量用于标识所述第一路径上接收所述路由标签栈信息和所述业务属性信息的节点数。
  7. 根据权利要求1至6任一所述的方法，其特征在于，所述第一数据帧的开销区还包括信令类型Type字段，所述Type字段用于指示所述第一数据帧的帧类型。
  8. 根据权利要求7所述的方法，其特征在于，
    所述Type字段用于指示所述第一数据帧为业务创建数据帧；
    或者，所述Type字段用于指示所述第一数据帧为业务1+1保护创建数据帧；
    或者，所述Type字段用于指示所述第一数据帧为业务重路由数据帧。
  9. 根据权利要求8所述的方法，其特征在于，所述Type字段用于指示所述第一数据帧为业务1+1保护创建数据帧，包括：
    所述Type字段用于指示所述第一数据帧为所述业务的主用路径创建数据帧；
    或者，所述Type字段用于指示所述第一数据帧为所述业务的备用路径创建数据帧。
  10. 根据权利要求1至9任一所述的方法，其特征在于，所述第一节点获取第一路径的路由标签栈信息，包括：
    所述第一节点接收所述业务的路由请求；
    根据所述路由请求计算出传输所述业务的所述第一路径；
    将所述第一路径转化为所述路由标签栈信息。
  11. 根据权利要求1至10任一所述的方法，所述第一节点发送所述第一数据帧后，所述方法还包括，所述第一节点根据所述路由标签栈信息中的第一标签在物理层面为所述业务建立交叉连接；以及，所述第一节点根据所述业务属性信息为所述业务在所述物理层面配置资源。
  12. 根据权利要求1至11任一所述的方法，其特征在于，所述第二节点从所述第一数据帧中获取所述路由标签栈信息，包括：
    所述第二节点通过堆栈方式从所述第一数据帧中获取第二标签，所述第二标签具体用于指示所述第二节点建立所述业务在所述第二节点上的通道；
    或者，所述第二节点通过指针方式从所述第一数据帧中获取所述第二标签。
  13. 根据权利要求12所述的方法，其特征在于，所述第二节点从所述第一数据帧中获取所述第二标签之后，所述方法还包括：所述第二节点向其他节点转发所述路由标签栈信息和所述业务属性信息，所述其他节点为所述第二节点在所述第一路径上的下游节点。
  14. 根据权利要求2至13任一所述的方法，其特征在于，所述第二节点根据所述路由标签栈信息建立所述业务在所述第二节点上的通道，包括：
    所述第二节点根据所述第二标签在物理层面为所述业务建立交叉连接。
  15. 根据权利要求14所述的方法，其特征在于，所述第二节点根据所述业务属性信息为所述业务配置资源，包括：所述第二节点根据所述业务属性信息在所述物理层面为所述业务配置带宽。
  16. 根据权利要求1至15任一所述的方法，其特征在于，所述第一节点发送所述第一数据帧，包括：
    所述第一节点通过所述业务在所述第一节点上的通道的出端口发送所述第一数据帧。
  17. 一种网络设备，其特征在于，包括：
    处理单元，用于获取第一路径的路由标签栈信息，所述第一路径用于传输业务，所述路由标签栈信息用于指示所述第一路径上各节点建立所述业务在所述第一路径各节点上的通道；
    所述处理单元还用于将所述路由标签栈信息和业务属性信息插入第一数据帧的净荷区，所述业务属性信息用于指示所述第一路径上各节点为所述业务配置资源；
    发送单元，用于发送所述第一数据帧。
  18. 一种网络设备，其特征在于，包括：
    接收单元，用于接收第一数据帧，所述第一数据帧携带第一路径的路由标签栈信息和业务属性信息，所述路由标签栈信息用于指示所述第一路径上各节点建立业务在所述第一路径各节点上的通道，所述业务属性信息用于指示所述第一路径上各节点为所述业务配置资源，其中所述第一路径用于传输所述业务；
    处理单元，用于从所述第一数据帧中获取所述路由标签栈信息和所述业务属性信息；
    还用于根据所述路由标签栈信息建立所述业务在所述网络设备上的通道；以及，还用于根据所述业务属性信息为所述业务配置资源。
  19. 根据权利要求17或18所述的网络设备，其特征在于，所述路由标签栈信息包括多个标签，所述多个标签中的每一个标签与所述第一路径上各网络设备的所述业务的通道一一 对应，所述对应预先配置在所述各网络设备中。
  20. 根据权利要求17至19任一所述的网络设备，其特征在于，所述业务属性信息包括以下信息中的一项或多项：业务标识ID、带宽、时延、源节点标识ID、宿节点标识ID、业务路径属性。
  21. 根据权利要求17至20任一所述的网络设备，其特征在于，所述第一数据帧的长度为192字节、240字节、128字节或者64字节。
  22. 根据权利要求21所述的网络设备，其特征在于，所述净荷区还包括标签数量，所述标签数量用于标识所述第一路径上接收所述路由标签栈信息和所述业务属性信息的网络设备数。
  23. 根据权利要求17至22任一所述的网络设备，其特征在于，所述第一数据帧的开销区还包括信令类型Type字段，所述Type字段用于指示所述第一数据帧的帧类型。
  24. 根据权利要求23所述的网络设备，其特征在于，
    所述Type字段用于指示所述第一数据帧为业务创建数据帧；
    或者，所述Type字段用于指示所述第一数据帧为业务1+1保护创建数据帧；
    或者，所述Type字段用于指示所述第一数据帧为业务重路由数据帧。
  25. 根据权利要求17、19至24任一所述的网络设备，其特征在于，所述网络设备还包括接收单元，所述处理单元获取第一路径的路由标签栈信息之前，
    所述接收单元用于接收所述业务的路由请求；
    所述处理单元，还用于根据所述路由请求计算出传输所述业务的所述第一路径；
    以及，还用于将所述第一路径转化为所述路由标签栈信息。
  26. 根据权利要求25所述的网络设备，其特征在于，所述发送单元发送所述第一数据帧后，所述处理单元，
    还用于根据所述路由标签栈信息中的第一标签在物理层面为所述业务建立连接；以及，以及，
    还用于根据所述业务属性信息为所述业务在所述物理层面配置资源。
  27. 根据权利要求18至24任一所述的网络设备，其特征在于，所述处理单元从所述第一数据帧中获取所述路由标签栈信息，是指：
    所述处理单元通过堆栈方式从所述第一数据帧中获取第二标签，所述第二标签具体用于指示所述网络设备建立所述业务在所述网络设备上的通道；
    或者，所述处理单元通过指针方式从所述第一数据帧中获取所述第二标签。
  28. 根据权利要求27所述的网络设备，其特征在于，所述网络设备还包括发送单元，所述处理单元从所述第一数据帧中获取第二标签之后，所述发送单元用于：
    向其他网络设备转发所述路由标签栈信息和所述业务属性信息，所述其他网络设备为所述网络设备在所述第一路径上的下游网络设备。
  29. 根据权利要求28所述的网络设备，其特征在于，所述处理单元根据所述路由标签栈信息建立所述业务在所述网络设备上的通道，具体包括，所述处理单元根据所述第二标签在物理层面为所述业务建立交叉连接。
  30. 根据权利要求29所述的网络设备，其特征在于，所述处理单元根据所述业务属性信息为所述业务配置资源，包括，所述处理单元根据所述业务属性信息在所述物理层面为所述业务配置带宽。
  31. 根据权利要求17、19至26任一所述的网络设备，其特征在于，所述发送单元通过所述业务在所述网络设备上的通道出端口发送所述第一数据帧。
  32. 根据权利要求18至24,27至30任一所述的网络设备，其特征在于，所述发送单元通过所述业务在所述网络设备上的通道出端口发送第二数据帧，所述第二数据帧携带所述路由标签栈信息和所述业务属性信息。
  33. 一种计算机可读存储介质，其特征在于，存储有计算机程序或指令、所述程序或指令被运行时会驱动设备执行如权利要求1至16任一项所述的方法。
PCT/CN2021/120063 2020-09-27 2021-09-24 一种数据帧的发送方法和网络设备 WO2022063196A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP21871565.4A EP4207794A4 (en) 2020-09-27 2021-09-24 DATA FRAME TRANSMISSION METHOD AND NETWORK APPARATUS
US18/189,401 US20230254245A1 (en) 2020-09-27 2023-03-24 Data Frame Sending Method and Network Device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202011032653.X 2020-09-27
CN202011032653.XA CN114286205B (zh) 2020-09-27 2020-09-27 一种数据帧的发送方法和网络设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/189,401 Continuation US20230254245A1 (en) 2020-09-27 2023-03-24 Data Frame Sending Method and Network Device

Publications (1)

Publication Number Publication Date
WO2022063196A1 true WO2022063196A1 (zh) 2022-03-31

Family

ID=80844955

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/120063 WO2022063196A1 (zh) 2020-09-27 2021-09-24 一种数据帧的发送方法和网络设备

Country Status (4)

Country Link
US (1) US20230254245A1 (zh)
EP (1) EP4207794A4 (zh)
CN (2) CN118200771A (zh)
WO (1) WO2022063196A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117061052A (zh) * 2022-05-05 2023-11-14 中兴通讯股份有限公司 一种业务路径控制方法、装置、存储介质及电子装置
CN115633279B (zh) * 2022-12-19 2023-04-07 北京华环电子股份有限公司 Osu交叉设备及基于osu交叉设备的数据传输方法

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040105459A1 (en) * 2002-11-30 2004-06-03 Raghu Mannam Method and a system to build efficient communications networks in which MPLS functionality is incorporated within the SONET/SDH/OTN transport equipment by performing it in the GFP layer
CN1625177A (zh) * 2003-12-03 2005-06-08 华为技术有限公司 传送多协议标签交换协议数据单元的方法
CN101860481A (zh) * 2010-05-25 2010-10-13 北京邮电大学 一种MPLS-TP over OTN多层网络中区分优先级的业务传送方法及其装置
CN105471737A (zh) * 2014-09-05 2016-04-06 华为技术有限公司 一种标签栈的压缩方法及装置、标签栈的解压缩方法及装置

Family Cites Families (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP3705222B2 (ja) * 2002-02-06 2005-10-12 日本電気株式会社 パス設定方法及びそれを用いる通信ネットワーク並びにノード装置
CN100596100C (zh) * 2006-08-29 2010-03-24 华为技术有限公司 实现多协议标签交换网络差分业务流量工程的方法和系统
US8218553B2 (en) * 2009-02-25 2012-07-10 Juniper Networks, Inc. Load balancing network traffic on a label switched path using resource reservation protocol with traffic engineering
CN101945307B (zh) * 2009-07-03 2013-04-24 华为技术有限公司 光网络中标签的分配处理方法、光通信装置及光通信系统
US8982775B2 (en) * 2010-11-02 2015-03-17 Infinera Corporation GMPLS signaling for networks having multiple multiplexing levels
US9236969B2 (en) * 2011-10-28 2016-01-12 Infinera Corporation Super optical channel data unit signal supported by multiple wavelengths
CN104144122B (zh) * 2013-05-10 2019-06-21 华为技术有限公司 建立标签交换路径的方法、设备及系统
WO2016154248A1 (en) * 2015-03-25 2016-09-29 Tevetron, Llc Communication network employing network devices with packet delivery over pre-assigned optical channels
WO2017156710A1 (zh) * 2016-03-15 2017-09-21 华为技术有限公司 一种业务路径建立的方法、节点设备和系统
CN108737269B (zh) * 2017-04-13 2021-11-26 中兴通讯股份有限公司 一种封装方法、装置和节点
CN108989210B (zh) * 2017-06-02 2021-08-24 中兴通讯股份有限公司 一种基于策略的隧道选择方法及软件定义网络控制器
EP3808042A1 (en) * 2018-06-14 2021-04-21 Nokia Solutions and Networks Oy Flexible label value encoding in label switched packet networks
CN111263250B (zh) * 2018-11-30 2021-03-23 华为技术有限公司 业务数据处理方法及设备
CN111510384B (zh) * 2019-01-31 2023-03-10 伊姆西Ip控股有限责任公司 处理服务产生的数据的方法、电子设备和计算机可读介质

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040105459A1 (en) * 2002-11-30 2004-06-03 Raghu Mannam Method and a system to build efficient communications networks in which MPLS functionality is incorporated within the SONET/SDH/OTN transport equipment by performing it in the GFP layer
CN1625177A (zh) * 2003-12-03 2005-06-08 华为技术有限公司 传送多协议标签交换协议数据单元的方法
CN101860481A (zh) * 2010-05-25 2010-10-13 北京邮电大学 一种MPLS-TP over OTN多层网络中区分优先级的业务传送方法及其装置
CN105471737A (zh) * 2014-09-05 2016-04-06 华为技术有限公司 一种标签栈的压缩方法及装置、标签栈的解压缩方法及装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP4207794A4

Also Published As

Publication number Publication date
US20230254245A1 (en) 2023-08-10
CN114286205A (zh) 2022-04-05
EP4207794A4 (en) 2024-01-24
EP4207794A1 (en) 2023-07-05
CN118200771A (zh) 2024-06-14
CN114286205B (zh) 2024-04-23

Similar Documents

Publication Publication Date Title
CN106803814B (zh) 一种灵活以太网路径的建立方法、装置及系统
WO2017156987A1 (zh) 一种灵活以太网路径建立的方法和装置
US20160373317A1 (en) Bandwidth on-demand services in multiple layer networks
US9350605B2 (en) Method and apparatus for multi-instance control plane for dynamic MPLS-TP tunnel management via in-band communication channel (G-ACH)
WO2015124026A1 (zh) 流表项生成方法以及装置
WO2022063010A1 (zh) 一种业务保护方法和网络节点
WO2022063196A1 (zh) 一种数据帧的发送方法和网络设备
JP2006527543A (ja) 光ネットワーク・トポロジ・データベースおよび光ネットワーク・オペレーション
US10374935B2 (en) Link discovery method, system, and device
JP5936603B2 (ja) マルチステージ光バーストスイッチングシステム及び方法のための制御レイヤ
WO2017193569A1 (zh) 一种路径建立方法及控制器
US8582582B2 (en) In-band control plane and management functionality in optical level one virtual private networks
WO2017088495A1 (zh) 一种路由信息的获取方法及装置
CN113015039B (zh) 一种混合网络的端到端业务的部署方法和部署装置
US10425319B2 (en) Transport software defined networking (SDN)—zero configuration adjacency via packet snooping
US20080031623A1 (en) Providing optical signal regeneration information at the control plane
WO2014205792A1 (zh) 一种建立光旁路的方法、装置和系统
CN101160929A (zh) 一种客户层链路自动发现方法及装置
JP5365434B2 (ja) ノード装置及び経路計算方法
WO2021238195A1 (zh) 业务资源预配置方法、设备和系统
US8599703B2 (en) System and method to determine resource status of end-to-end path
WO2012149777A1 (zh) 标签交换路径建立的方法、装置和系统
WO2010130177A1 (zh) 业务连接建立方法、路径计算单元设备及网络系统
US7856018B2 (en) Provisioning point-to-multipoint paths
WO2013063751A1 (zh) 转发邻居-标签交换路径的连接建立方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21871565

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2021871565

Country of ref document: EP

Effective date: 20230330

NENP Non-entry into the national phase

Ref country code: DE