CN109120657B - Service configuration method and node - Google Patents
Service configuration method and node Download PDFInfo
- Publication number
- CN109120657B CN109120657B CN201710488310.6A CN201710488310A CN109120657B CN 109120657 B CN109120657 B CN 109120657B CN 201710488310 A CN201710488310 A CN 201710488310A CN 109120657 B CN109120657 B CN 109120657B
- Authority
- CN
- China
- Prior art keywords
- service
- node
- service path
- information
- message
- Prior art date
- Legal status (The legal status 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 status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/565—Conversion or adaptation of application format or content
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0876—Aspects of the degree of configuration automation
- H04L41/0886—Fully automatic configuration
-
- 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/74—Address processing for routing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/22—Parsing or analysis of headers
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Automation & Control Theory (AREA)
- Computer Security & Cryptography (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses a service configuration method and a node, comprising the following steps: the intermediate node receives the message sent by the adjacent node, and determines the type of the received message according to the received message information; if the received message is a service path request message, the intermediate node adds the path parameters of the intermediate node to the service path information of the service path request message and forwards the service path request message to the adjacent node of the intermediate node; and if the received message is a service path response message, configuring self service information according to the service path response message, adding the self service information into the service path response message, and forwarding the self service information to a previous hop node in the service path information carried by the service path response message. The invention improves the service configuration efficiency and accuracy of the flexible Ethernet by carrying the service configuration information and the service path information in the service path request message and the service path response message.
Description
Technical Field
The present invention relates to the field of flexible ethernet technologies, and in particular, to a service configuration method and a node.
Background
Currently, the Optical Internet Forum (OIF) is discussing and expanding the application scenario of the conventional Ethernet to support the functions of subrate, channelization, inverse multiplexing, etc. for the Ethernet service, and the Ethernet technology is called Flexible Ethernet (FlexE). For example, for a subrate application scenario of an ethernet service, the flexible ethernet can support that 250G of ethernet service (Media Access Control (MAC) code stream) is transmitted by using 3 existing 100GE Physical Media Dependent sublayers (PMD). Aiming at the application scene of the inverse multiplexing of the Ethernet service, the flexible Ethernet can support that the 200G Ethernet service is transmitted by adopting 2 paths of the existing PMD of 100 GE. Aiming at the channelized application scene of the Ethernet service, the flexible Ethernet can support multiplexing of a plurality of paths of low-rate Ethernet services into a high-rate flexible Ethernet similar to the multiplexing function of an Optical Transport Network (OTN).
With the development of 5G network services, both a mobile backhaul network (a network from a mobile base station to a mobile base station) and a mobile backhaul network (a network from a mobile base station to a base station controller) will use service configuration based on a FlexE protocol, and application scenarios of FlexE will become more and more extensive. However, the service configuration of the existing FlexE requires manual configuration from node to node through a command line, and the situations of missing configuration and mismatching are easy to occur. As the networking of the device units is more and more complex, the service configuration of the FlexE is more and more complex, the configuration workload is larger and the maintenance work is heavier and heavier. Meanwhile, if a problem occurs in the FlexE service, communication interruption will occur.
Disclosure of Invention
In order to solve the technical problem, the invention provides a service configuration method, a source node, a destination node and an intermediate node, which can improve the service configuration efficiency and accuracy of the flexible ethernet.
In order to achieve the purpose of the invention, the technical scheme of the embodiment of the invention is realized as follows:
the embodiment of the invention provides a service configuration method, which comprises the following steps:
the intermediate node receives the message sent by the adjacent node, and determines the type of the received message according to the received message information;
if the received message is a service path request message, the intermediate node adds the path parameters of the intermediate node to the service path information of the service path request message and forwards the service path request message to the adjacent node of the intermediate node;
if the received message is a service path response message, the intermediate node configures the service information of itself according to the service path response message, adds the service information of itself into the service path response message, and forwards the service path response message to the previous hop node in the service path information carried by the service path response message.
Further, the intermediate node receives the message sent by the neighboring node through a data communication network DCN channel, and forwards the service path request message or the service path response message through the data communication network DCN channel.
Further, the determining the type of the received packet according to the received packet information specifically includes:
and determining the type of the received message as a service path request message or a service path response message according to the flag bit value in the received message.
Further, the determining the type of the received packet according to the received packet information specifically includes:
if the MAC address of the source medium access control layer in the received message is different from the MAC address of the message, the MAC address of the destination medium access control layer in the received message is different from the MAC address of the message and the source MAC address is different from the destination MAC address, the received message is a service path request message;
if the source MAC address in the received message is different from the MAC address of the message, the destination MAC address is different from the MAC address of the message and the source MAC address is the same as the destination MAC address, the received message is a service path response message.
Further, the service path response message includes a source node of the service to be configured, a destination node, service configuration information of the service to be configured, and service path information;
the service configuration information comprises service bandwidth, a flexible Ethernet Flexe group, a flexible Ethernet Flexe client and a time slot sequence occupied by the flexible Ethernet Flexe client in the service bandwidth;
the service path information comprises MAC addresses of passing nodes and access ports of passing nodes.
Further, the service path response packet further includes the number of node hops passed through and the remaining bandwidth of each port passed through.
The embodiment of the invention also provides a service configuration method, which comprises the following steps:
a source node sends a service path request message to a neighboring node;
and the source node receives the service path response message sent by the adjacent node and configures the service information of the source node according to the service path response message.
The embodiment of the invention also provides a service configuration method, which comprises the following steps:
a host node receives a service path request message sent by a neighboring node;
the host node determines a service path according to the service path request message information, configures the service information of the host node, and sends a service path response message according to the determined service path and the configured service information of the host node.
The embodiment of the present invention further provides a node, including a second receiving module, a second sending module, and a second configuration module, where:
the second receiving module is used for receiving a service path request message or a service path response message sent by a neighboring node and determining the type of the received message according to the received message information; if the received message type is a service path response message, informing a second configuration module; if the received message type is a service path request message, notifying a second sending module;
the second configuration module is used for receiving the notification of the second receiving module, configuring the node service information according to the service configuration information in the service path response message and notifying the second sending module;
a second sending module, configured to receive a notification from the second receiving module, add the node path parameter to a service path request packet, and forward the service path request packet to a neighboring node of the node; and receiving the notification of the second configuration module, adding the node service information into a service path response message, and forwarding the service path response message to the previous hop node in the service path information carried by the service path response message.
The embodiment of the present invention further provides a node, including a first sending module, a first receiving module, and a first configuration module, where:
the first sending module is used for sending a service path request message to the adjacent node;
the first receiving module is used for receiving a service path response message returned by the adjacent node and informing the first configuration module;
and the first configuration module is used for receiving the notification of the first receiving module and configuring the node service information according to the service path response message.
The embodiment of the present invention further provides a node, including a third sending module, a third receiving module and a third configuration module, where:
the third receiving module is configured to receive a service path request packet sent by a neighboring node, and notify the third configuration module;
the third configuration module is used for receiving the notification of the third receiving module, determining a service path according to the service path request message information, configuring the node service information and notifying the third sending module;
and the third sending module is used for receiving the notification of the third configuration module and sending a service path response message according to the determined service path and the configured node service information.
The technical scheme of the invention has the following beneficial effects:
according to the service configuration method and the nodes provided by the invention, after the source node and the destination node of the Flexe service are determined, the configuration of the subsequent whole service can be automatically established between the devices through the service path request message and the service path response message carrying the service configuration information and the service path information, manual configuration on each node one by one is not needed, the situations of mismatch and missing of manual configuration are prevented, and the effectiveness and the correctness of service configuration are enhanced.
Drawings
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the invention and together with the description serve to explain the invention without limiting the invention. In the drawings:
fig. 1 is a schematic flow chart of a service configuration method according to a first embodiment of the present invention;
fig. 2 is a schematic diagram illustrating a format of a service path request message or a service path response message according to an embodiment of the present invention;
fig. 3 is a schematic diagram of service configuration information of a source node or a sink node in a service path request message or a service path response message according to an embodiment of the present invention;
fig. 4 is a schematic diagram of service configuration information of an intermediate node in a service path request message or a service path response message according to an embodiment of the present invention;
fig. 5 is a flowchart illustrating a service configuration method according to a second embodiment of the present invention;
fig. 6 is a flowchart illustrating a service configuration method according to a third embodiment of the present invention;
FIG. 7 is a schematic structural diagram of a node according to a first embodiment of the present invention;
FIG. 8 is a schematic structural diagram of a node according to a second embodiment of the present invention;
fig. 9 is a schematic structural diagram of a node according to a third embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, embodiments of the present invention will be described in detail below with reference to the accompanying drawings. It should be noted that the embodiments and features of the embodiments in the present application may be arbitrarily combined with each other without conflict.
As shown in fig. 1, a service configuration method according to the present invention includes the following steps:
step 101: the intermediate node receives the message sent by the adjacent node, and determines the type of the received message according to the received message information;
further, the node receives the message sent by the neighboring node through a data communication network DCN channel.
It should be noted that a Data Communication Network (DCN) is an integrated Data Communication Network constructed on a telecommunication Network to meet the needs of maintenance, administration, management and service of telecommunication enterprises. With the development of ethernet technology, operators have further explored the potential of DCNs, and with the continuous improvement of enterprise informatization degree, newly-built and reconstructed DCNs have gradually become enterprise networks inside operators, and besides bearing traditional various special network management information, DCNs also take on the functions of charging systems, user credit control and management systems, and reporting of service income, etc. In addition, the DCN also carries Office Automation (OA) Office inside the operator, a mail system, document circulation, an Enterprise website application and management support system, including an Enterprise Resource Planning (ERP) system, a data warehouse, and the like. The DCN plays an extremely important role in adapting to increasingly severe market competition for operators, promoting service development and meeting increasingly higher management requirements. The adjacent node refers to a node connected with the current node through a DCN channel, and the adjacent node of the source node may be an intermediate node or a sink node; the adjacent nodes of the intermediate nodes can be source nodes, can be sink nodes and can also be other intermediate nodes; the neighboring nodes of the sink node may be intermediate nodes or may be source nodes.
Further, the determining the type of the received packet according to the received packet information specifically includes:
and determining the type of the received message as a service path request message or a service path response message according to the flag bit value in the received message.
Further, the determining the type of the received packet according to the received packet information specifically includes:
if the MAC address of a source medium access control layer in the received message is different from the MAC address of the message, the MAC address of a target medium access control layer in the received message is different from the MAC address of the message and the source MAC address is different from the target MAC address, the received message is a service path request message;
if the source MAC address in the received message is different from the MAC address of the message, the destination MAC address is different from the MAC address of the message and the source MAC address is the same as the destination MAC address, the received message is a service path response message.
Further, the intermediate node determines its own node attribute and the type of the received packet according to the received packet information.
In an embodiment of the present invention, the determining, by the intermediate node, the node attribute of the intermediate node and the type of the received packet according to the received packet information specifically includes:
comparing the source MAC address and the destination MAC address in the received message with the MAC address of the node, and determining that the node attribute is a source node, an intermediate node or a destination node;
and determining the type of the received message as a service path request message or a service path response message according to the flag bit value in the received message.
Further, the comparing the source MAC address and the destination MAC address in the received message with the MAC address of the node itself, and determining that the node attribute is a source node, an intermediate node, or a sink node specifically includes:
if the source MAC address is different from the MAC address of the node and the target MAC address is different from the MAC address of the node, the node is an intermediate node;
if the source MAC address is the same as the MAC address of the node and the destination MAC address is the same as the MAC address of the node, the node is a source node;
and if the source MAC address is different from the MAC address of the node and the destination MAC address is the same as the MAC address of the node, the node is a destination node.
In another embodiment of the present invention, the determining, by the intermediate node, the node attribute of the intermediate node and the type of the received packet according to the received packet information specifically includes:
if the source MAC address in the received message is different from the MAC address of the node, the destination MAC address in the received message is different from the MAC address of the node and the source MAC address is different from the destination MAC address, the node is an intermediate node, and the received message is a service path request message;
if the source MAC address in the received message is different from the MAC address of the message, the destination MAC address in the received message is different from the MAC address of the message and the source MAC address is the same as the destination MAC address, the node is an intermediate node, and the received message is a service path response message;
if the source MAC address in the received message is the same as the MAC address of the node and the destination MAC address in the received message is the same as the MAC address of the node, the node is a source node, and the received message is a service path response message;
and if the source MAC address in the received message is different from the MAC address of the node, and the destination MAC address in the received message is the same as the MAC address of the node, the node is a host node, and the received message is a service path request message.
102, if the received message is a service path request message, the intermediate node adds the path parameters of the intermediate node to the service path information of the service path request message and forwards the service path request message to the adjacent node of the intermediate node;
if the received message is a service path response message, the intermediate node configures the service information of the intermediate node according to the service configuration information of the next hop node in the service path response message, adds the service information of the intermediate node into the service path response message, and forwards the service path response message to the previous hop node in the service path information carried by the service path response message.
It should be noted that, if the node is a source node, the received packet is a service path response packet, and the source node configures the service information of the source node according to the service path response packet;
if the node is a host node, the received message is a service path request message, the host node determines service path information according to the service path request message information and configures the service information of the host node, and then sends a service path response message according to the determined service path information and the configured service information of the host node.
Further, the service path response packet includes a source node of the service to be configured, a destination node, service configuration information of the service to be configured, and service path information.
Specifically, the service configuration information includes, but is not limited to, a service bandwidth, a FlexE Group (Group), a FlexE Client (Client), and a time slot sequence occupied by the Client on a FlexE port.
In an embodiment of the present invention, the service configuration information includes service bandwidth, a FlexE Group serial Number, a FlexE Group Number, a FlexE Client serial Number, two FlexE clients occupying time slots and intersecting the time slots, and service Client-side port information of the source node and the sink node.
Specifically, the traffic path information includes, but is not limited to, a MAC address of a passing node, and an ingress and egress port of the passing node.
In an embodiment of the present invention, the service path response message further includes the number of node hops passed through and the remaining bandwidth of each port passed through.
It should be noted that, the service path request packet and the service path response packet may adopt the same structure, but when the source node sends the service path request packet, except that the source node, the sink node, the service bandwidth, the service client side interface attribute of the source node, the service client side interface attribute of the sink node, and the output port number information of the source node to be configured with the service are known, the values of other service configuration information and the service path information are preset NULL values (NULL). After the source node receives the service path response message, the configured service information of the node has the same structure as the service information configured by the sink node.
Furthermore, the host node compares the path information of all the received service path request messages, selects a path with the bandwidth meeting and the fewest hops, extracts message configuration data, configures the service information of the host node, and then sends a service path response message according to the finally selected path and the configured service information of the host node.
Specifically, the extracting of the message configuration data and the configuring of the service information of the sink node specifically include determining a time slot sequence occupied by a Flexe Client according to the service bandwidth; generating a Flexe Group serial Number and a Number (Number), adding a Flexe port on a service network side of a host node into the Flexe Group, and generating a physical layer Number (PHY Number); the Flexe Client is also added to the Flexe Group, and the Flexe Client is bound to the Client-side port.
In an embodiment of the present invention, before the sink node sends the service path response packet, the sink node service information shown in fig. 4 is added to the service path response packet, and the determined service path information is added to the service path response packet, where a source MAC address and a destination MAC address in the service path response packet are both source MAC addresses of the service path request packet.
Further, the sink node may generate a traffic path response packet by the following method:
adding the service information of the host node into the service path request message;
directly modifying the target MAC in the service path request message into the MAC address of the source node;
and taking the modified service path request message as a service path response message.
It should be noted that, after receiving the service path response packet, the intermediate node (P node) configures the service information of this node, first generates two FlexE clients, where the bound network-side FlexE port time slot sequences have the same configuration, adds both FlexE clients to a FlexE Group, where PHY numbers are the same, and then generates two FlexE Client time slot cross attributes.
In an embodiment of the present invention, a format of the service path request packet or the service path response packet is shown in fig. 2, service configuration information of the source node or the sink node is shown in fig. 3, and service configuration information of the intermediate node is shown in fig. 4.
As shown in fig. 5, a service configuration method according to the present invention includes the following steps:
step 501: a source node sends a service path request message to a neighboring node;
further, the source node sends a service path request message to the neighboring node through a data communication network DCN channel.
It should be noted that the neighboring node of the source node may be an intermediate node or a sink node.
Further, the service path request packet includes a source node, a sink node, a service bandwidth, a source node service client side interface attribute, a sink node service client side interface attribute, and an egress port number of the source node, where the service is to be configured.
The source node service client side Interface attribute may be an ethernet Interface mode or a Common Public Radio Interface (CPRI) mode; the sink node service client side interface attribute may be an ethernet interface mode or a common public radio interface CPRI mode.
Further, the ethernet interface mode includes 1GE, 10GE, 25GE, 40GE interfaces, and the like.
Step 502: and the source node receives the service path response message sent by the adjacent node and configures the service information of the source node according to the service path response message.
It should be noted that the source node compares whether a source MAC address in the received message is the same as its own MAC address, and whether a destination MAC address in the received message is the same as its own MAC address, and if the source MAC address and the destination MAC address are the same as their own MAC address, the source node determines that the received message is a service path response message.
As shown in fig. 6, a service configuration method according to the present invention includes the following steps:
step 601: a host node receives a service path request message sent by a neighboring node;
further, the sink node receives a service path request message sent by a neighboring node through a data communication network DCN channel.
It should be noted that the neighboring node of the sink node may be the source node, and may also be other intermediate nodes.
Furthermore, the destination node compares the path information of all received service path request messages, selects a path with the minimum bandwidth and hop count, extracts message configuration data, configures destination node service information, and sends a service path response message according to the finally selected path and the configured destination node service information.
Specifically, the extracting of the message configuration data and the configuring of the service information of the sink node specifically include determining a time slot sequence occupied by a Flexe Client according to the service bandwidth; generating a Flexe Group serial Number and a Number (Number), adding a Flexe port on a service network side of a host node into the Flexe Group, and generating a physical layer Number (PHY Number); the Flexe Client is also added to the Flexe Group, and the Flexe Client is bound to the Client-side port.
In an embodiment of the present invention, before the sink node sends the service path response packet, the sink node adds the service information of the sink node shown in fig. 4 to the service path response packet, and adds the determined service path information to the service path response packet, where the source MAC address and the destination MAC address in the service path response packet are both the source MAC address of the service path request packet.
Further, the sink node may generate a traffic path response packet by:
adding the service information of the host node into the service path request message;
directly modifying the target MAC in the service path request message into the MAC address of the source node;
and taking the modified service path request message as a service path response message.
As shown in fig. 7, a node according to the present invention includes a second receiving module, a second sending module, and a second configuring module, wherein:
the second receiving module is used for receiving a service path request message or a service path response message sent by a neighboring node and determining the type of the received message according to the received message information; if the received message type is a service path response message, informing a second configuration module; if the received message type is a service path request message, notifying a second sending module;
the second configuration module is used for receiving the notification of the second receiving module, configuring the node service information according to the service configuration information in the service path response message and notifying the second sending module;
the second sending module is used for receiving the notification of the second receiving module, adding the node path parameter into the service path request message and forwarding the service path request message to the adjacent node of the node; and receiving the notification of the second configuration module, adding the node service information into a service path response message, and forwarding the service path response message to the previous hop node in the service path information carried by the service path response message.
It should be noted that the neighboring node of the source node may be an intermediate node or a sink node; the adjacent nodes of the intermediate nodes can be source nodes, can be sink nodes and can also be other intermediate nodes; the neighboring nodes of the sink node may be intermediate nodes or may be source nodes.
Further, the second receiving module receives a service path request message or a service path response message sent by a neighboring node through a DCN channel of a data communication network.
Further, the determining the type of the received packet according to the received packet information specifically includes:
if the source MAC address in the received message is different from the MAC address of the node, the destination MAC address in the received message is different from the MAC address of the node and the source MAC address is different from the destination MAC address, the node is an intermediate node, and the received message is a service path request message;
if the source MAC address is different from the MAC address of the node, the destination MAC address is different from the MAC address of the node and the source MAC address is the same as the destination MAC address, the node is an intermediate node, and the received message is a service path response message;
if the source MAC address is the same as the MAC address of the node and the destination MAC address is the same as the MAC address of the node, the node is the source node, and the received message is a service path response message;
if the source MAC address is different from the own MAC address and the destination MAC address is the same as the own MAC address, the node is a host node, and the received message is a service path request message.
It should be noted that, when the second configuration module configures the node service information, first two FlexE clients are generated, the time slot sequences of the FlexE ports on the bound network side are configured identically, and both the two FlexE clients are added to a FlexE Group, and the PHY numbers are identical, and then two FlexE Client time slot cross attributes are generated.
As shown in fig. 8, a node according to the present invention includes a first sending module, a first receiving module, and a first configuration module, wherein:
the first sending module is used for sending a service path request message to the adjacent node;
the first receiving module is configured to receive a service path response packet sent by a neighboring node, and notify the first configuration module;
and the first configuration module is used for receiving the notification of the first receiving module and configuring the node service information according to the service path response message.
Further, the first sending module sends a service path request message to a neighboring node through a data communication network DCN channel; and the first receiving module receives a service path response message sent by the adjacent node through a DCN channel of the data communication network.
Further, the service path request packet includes a source node, a sink node, a service bandwidth, a source node service client side interface attribute, a sink node service client side interface attribute, and an egress port number of the source node, where the service is to be configured.
Specifically, The source node service client side Interface attribute may be an ethernet Interface mode or a Common Public Radio Interface (CPRI) mode; the sink node service client side interface attribute may be an ethernet interface mode or a CPRI mode.
Further, the ethernet interface mode includes 1GE, 10GE, 25GE, 40GE interfaces, and the like.
Further, the service path response packet includes a source node of the service to be configured, a destination node, service configuration information of the service to be configured, and service path information.
Specifically, the service configuration information includes, but is not limited to, a service bandwidth, a FlexE Group (Group), a FlexE Client (Client), and a time slot sequence occupied by the Client on a FlexE port.
In an embodiment of the present invention, the service configuration information includes service bandwidth, a FlexE Group serial Number, a FlexE Group Number, a FlexE Client serial Number, two FlexE clients occupying time slots and intersecting the time slots, and service Client-side port information of the source node and the sink node.
Specifically, the traffic path information includes, but is not limited to, a MAC address of a passing node, and an ingress and egress port of the passing node.
In an embodiment of the present invention, the service path response message further includes the number of node hops passed through and the remaining bandwidth of each port passed through.
It should be noted that, the service path request message and the service path response message may adopt the same structure, but when the source node sends the service path request message, except that the source node, the sink node, the service bandwidth, the service client side interface attribute of the source node, the service client side interface attribute of the sink node, and the output port number information of the source node to be configured with the service are known, the values of other service configuration information and the service path information are all preset NULL values (NULL). After the source node receives the service path response message, the configured service information of the node has the same structure as the service information configured by the sink node.
In an embodiment of the present invention, a format of the service path request packet or the service path response packet is shown in fig. 2, service configuration information of the source node or the sink node is shown in fig. 3, and service configuration information of the intermediate node is shown in fig. 4.
As shown in fig. 9, a node according to the present invention includes a third sending module, a third receiving module, and a third configuring module, wherein:
the third receiving module is configured to receive a service path request packet sent by a neighboring node, and notify the third configuration module;
the third configuration module is used for receiving the notification of the third receiving module, determining a service path according to the service path request message information, configuring the node service information and notifying the third sending module;
and the third sending module is used for receiving the notification of the third configuration module and sending a service path response message according to the determined service path and the configured node service information.
Further, the third receiving module receives a service path request message sent by a neighboring node through a DCN channel of a data communication network.
Further, the third configuration module is specifically configured to: and comparing the path information of all the received service path request messages, selecting the path with the bandwidth meeting and the fewest hops, extracting message configuration data, and configuring the node service information.
Specifically, the extracting, by the third configuration module, packet configuration data and configuring the node service information specifically include: determining a time slot sequence occupied by a Flexe Client according to the service bandwidth, wherein 1 time slot is 5G in size; generating a Flexe Group serial Number and a Number, adding a Flexe port on a service network side of a host node into the Flexe Group, and generating a PHY Number; the Flexe Client is also added to the Flexe Group, and the Flexe Client is bound to the Client-side port.
The following describes how to apply the service configuration method, the source node, the intermediate node and the sink node of the present invention by a preferred embodiment. It should be noted that the following preferred embodiments are only for better describing the present invention and should not be construed as unduly limiting the present invention.
Step 1001: determining a source node, a destination node, service parameters and path parameters of a service to be configured;
it should be noted that, here, the source node, the sink node, the service parameter, and the path parameter of the service to be configured are determined according to the actual information of the service to be configured.
Step 1002, a source node sends a service path request message to a neighboring node through a DCN channel;
the parameters carried by the service path request message include, but are not limited to: destination MAC, source MAC, service parameter, path parameter.
It should be noted that the neighboring node refers to a node connected to the current node through a DCN channel, the format of the service path request packet is shown in fig. 2, and the service path request packet further includes a number of node hops passed and a port residual bandwidth passed.
Step 1003, the adjacent node determines that the node attribute is an intermediate node or a host node according to the service path request message information, if the node attribute is the intermediate node, the adjacent node adds the node path parameter and the service parameter to the service path request message and forwards the service path parameter and the service parameter to other adjacent nodes; if the node is a host node, the adjacent node determines a service path according to the service path request message information and configures the service information of the host node, and then sends a service path response message according to the determined service path;
further, the neighboring node judges whether the destination node MAC in the service path request message is consistent with the MAC of the node, and if so, the node is a host node; if not, the node is an intermediate node.
Further, if the adjacent node is an intermediate node, the path information of the node is added to the service path request message and forwarded to other adjacent nodes.
Further, if the adjacent node is a sink node, the path information in the service path request message is taken out, compared with the path information of all received service path request messages, the path with the bandwidth meeting and the fewest hops is selected, then the configuration data of the service path request message is extracted, the service information of the sink node is configured, and then the service path response message is sent according to the finally selected path and the configured service information of the sink node.
Specifically, the extracting of the message configuration data and the configuring of the service information of the sink node specifically include determining a time slot sequence occupied by a Flexe Client according to the service bandwidth, wherein 1 time slot is 5G in size; generating a Flexe Group serial Number and a Number, adding a Flexe port on a service network side of a host node into the Flexe Group, and generating a PHY Number; the Flexe Client is also added to the Flexe Group, and the Flexe Client is bound to the Client-side port.
And step 1004, after receiving the service path response message, the nodes on the path configure the service information of the nodes according to the service path response message.
It should be noted that the path information in the service path response message includes all node MACs and ports in the path, and the service information includes a FlexE Group, a FlexE Client, and a time slot sequence occupied by the FlexE Client. After receiving the service path response message, the PE source node configures the service information of the node with the same structure as the service information configured by the PE sink node; however, after the P node receives the response message, when configuring the service information of the P node, firstly generating two Flexe clients, wherein the time slot sequences of the bound Flexe ports on the network side are configured identically, and adding the two Flexe clients into a Flexe Group, wherein the PHY numbers are identical, and then generating two Flexe Client time slot cross attributes.
After the service configuration is completed, the configured service information can be checked on each node to check whether the service information is correct or not.
According to the service configuration method and the nodes provided by the invention, the automatic generation of the service of the whole network equipment can be completed after the source nodes, the destination nodes and the corresponding service information are confirmed manually, the single network elements are not required to be configured one by one through a command line, the operation steps are simple and convenient, the method is very close to engineering application, pure software is automatically operated, manual missing configuration and mismatching are prevented, and particularly, when the service path is longer, the difficulty, the cost and the risk of engineering field maintenance are greatly reduced;
furthermore, the DCN channel is used for sending or receiving the service path request message and the service path response message, extra occupied bandwidth is not needed, and on the premise that all nodes in the network start the DCN channel function, no matter which service between two points is created, the DCN channel can be quickly and effectively completed.
It will be understood by those skilled in the art that all or part of the steps of the above methods may be implemented by a program instructing relevant hardware, and the program may be stored in a computer-readable storage medium, such as a read-only memory, a magnetic or optical disk, and the like. Alternatively, all or part of the steps of the foregoing embodiments may also be implemented by using one or more integrated circuits, and accordingly, each module/unit in the foregoing embodiments may be implemented in the form of hardware, and may also be implemented in the form of a software functional module. The present invention is not limited to any specific form of combination of hardware and software.
The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (10)
1. A method for service configuration, comprising:
the intermediate node receives the message sent by the adjacent node, and determines the type of the received message according to the received message information; wherein, the message is a flexible Ethernet Flexe message;
if the received message is a service path request message, the intermediate node adds the path parameters of the intermediate node to the service path information of the service path request message and forwards the service path request message to the adjacent node of the intermediate node;
if the received message is a service path response message, the intermediate node configures own service information according to the service path response message, adds the own service information into the service path response message, and forwards the service path response message to a previous hop node in the service path information carried by the service path response message;
the service path response message comprises a source node and a destination node of the service to be configured, service configuration information of the service to be configured and service path information;
the service configuration information comprises service bandwidth, a flexible Ethernet Flexe group, a flexible Ethernet Flexe client and a time slot sequence occupied by the flexible Ethernet Flexe client in the service bandwidth;
the service path information comprises MAC addresses of passing nodes and access ports of passing nodes.
2. The service configuration method according to claim 1, wherein the intermediate node receives the packet sent by the neighboring node through a data communication network DCN channel, and forwards the service path request packet or the service path response packet through the data communication network DCN channel.
3. The service configuration method according to claim 1, wherein the determining the type of the received packet according to the received packet information specifically includes:
and determining the type of the received message as a service path request message or a service path response message according to the flag bit value in the received message.
4. The service configuration method according to claim 1, wherein the determining the type of the received packet according to the received packet information specifically includes:
if the MAC address of a source medium access control layer in the received message is different from the MAC address of the message, the MAC address of a target medium access control layer in the received message is different from the MAC address of the message and the source MAC address is different from the target MAC address, the received message is a service path request message;
if the source MAC address in the received message is different from the MAC address of the message, the destination MAC address is different from the MAC address of the message and the source MAC address is the same as the destination MAC address, the received message is a service path response message.
5. The traffic configuration method according to claim 1, wherein the traffic path response message further includes a number of node hops passed and a remaining bandwidth of each port passed.
6. A method for service configuration, comprising:
a source node sends a service path request message to a neighboring node;
a source node receives a service path response message sent by an adjacent node, and configures service information of the source node according to the service path response message; the service path request message and the service path response message are flexible Ethernet Flexe messages;
the service path response message comprises a source node and a destination node of the service to be configured, service configuration information of the service to be configured and service path information;
the service configuration information comprises service bandwidth, a flexible Ethernet Flexe group, a flexible Ethernet Flexe client and a time slot sequence occupied by the flexible Ethernet Flexe client in the service bandwidth;
the service path information comprises MAC addresses of passing nodes and access ports of passing nodes.
7. A service configuration method, comprising:
a host node receives a service path request message sent by a neighboring node;
the host node determines a service path according to the service path request message information, configures the service information of the host node, and sends a service path response message according to the determined service path and the configured service information of the host node; the service path request message and the service path response message are flexible Ethernet Flexe messages;
the service path response message comprises a source node and a destination node of the service to be configured, service configuration information of the service to be configured and service path information;
the service configuration information comprises service bandwidth, a flexible Ethernet Flexe group, a flexible Ethernet Flexe client and a time slot sequence occupied by the flexible Ethernet Flexe client in the service bandwidth;
the service path information comprises MAC addresses of passing nodes and access ports of passing nodes.
8. A node comprising a second receiving module, a second sending module, and a second configuration module, wherein:
the second receiving module is used for receiving a service path request message or a service path response message sent by a neighboring node and determining the type of the received message according to the received message information; if the received message type is a service path response message, informing a second configuration module; if the received message type is a service path request message, notifying a second sending module; the service path request message and the service path response message are flexible Ethernet Flexe messages;
the second configuration module is used for receiving the notification of the second receiving module, configuring the node service information according to the service configuration information in the service path response message and notifying the second sending module;
a second sending module, configured to receive the notification from the second receiving module, add the node path parameter to the service path request packet, and forward the node path parameter to a node adjacent to the node; receiving the notification of a second configuration module, adding the node service information into a service path response message, and forwarding the service path response message to a previous hop node in the service path information carried by the service path response message;
the service path response message comprises a source node and a destination node of the service to be configured, service configuration information of the service to be configured and service path information;
the service configuration information comprises service bandwidth, a flexible Ethernet Flexe group, a flexible Ethernet Flexe client and a time slot sequence occupied by the flexible Ethernet Flexe client in the service bandwidth;
the service path information comprises MAC addresses of passing nodes and access ports of passing nodes.
9. A node comprising a first sending module, a first receiving module, and a first configuration module, wherein:
the first sending module is used for sending a service path request message to the adjacent node;
the first receiving module is used for receiving a service path response message returned by the adjacent node and informing the first configuration module; the service path request message and the service path response message are flexible Ethernet Flexe messages;
the first configuration module is used for receiving the notification of the first receiving module and configuring the node service information according to the service path response message;
the service path response message comprises a source node and a destination node of the service to be configured, service configuration information of the service to be configured and service path information;
the service configuration information comprises service bandwidth, a flexible Ethernet Flexe group, a flexible Ethernet Flexe client and a time slot sequence occupied by the flexible Ethernet Flexe client in the service bandwidth;
the service path information comprises a passing node MAC address and a passing node access port.
10. A node comprising a third sending module, a third receiving module, and a third configuration module, wherein:
the third receiving module is configured to receive a service path request packet sent by a neighboring node, and notify the third configuration module;
the third configuration module is configured to receive the notification from the third receiving module, determine a service path according to the service path request message information, configure node service information, and notify the third sending module;
the third sending module is configured to receive the notification from the third configuration module, and send a service path response packet according to the determined service path and the configured node service information; the service path request message and the service path response message are flexible Ethernet Flexe messages;
the service path response message comprises a source node and a destination node of the service to be configured, service configuration information of the service to be configured and service path information;
the service configuration information comprises service bandwidth, a flexible Ethernet Flexe group, a flexible Ethernet Flexe client and a time slot sequence occupied by the flexible Ethernet Flexe client in the service bandwidth;
the service path information comprises MAC addresses of passing nodes and access ports of passing nodes.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710488310.6A CN109120657B (en) | 2017-06-23 | 2017-06-23 | Service configuration method and node |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710488310.6A CN109120657B (en) | 2017-06-23 | 2017-06-23 | Service configuration method and node |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109120657A CN109120657A (en) | 2019-01-01 |
| CN109120657B true CN109120657B (en) | 2022-08-16 |
Family
ID=64733297
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710488310.6A Active CN109120657B (en) | 2017-06-23 | 2017-06-23 | Service configuration method and node |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109120657B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112532522B (en) * | 2019-09-19 | 2023-09-05 | 中兴通讯股份有限公司 | Service path establishing method and device and electronic equipment |
| CN113055210A (en) * | 2019-12-27 | 2021-06-29 | 中国移动通信有限公司研究院 | Method and equipment for sending interface information |
| CN113965454A (en) * | 2020-07-03 | 2022-01-21 | 华为技术有限公司 | Method and device for automatically configuring flexible Ethernet Flexe |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105515816A (en) * | 2014-10-20 | 2016-04-20 | 中兴通讯股份有限公司 | Processing method and apparatus for detection level information |
| CN106850465A (en) * | 2016-12-27 | 2017-06-13 | 深圳市海思半导体有限公司 | A kind of Flex E method for interchanging data and switching equipment |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103546376B (en) * | 2012-07-09 | 2019-07-30 | 中兴通讯股份有限公司 | A kind of transfer approach and node of response message |
| EP4266632A1 (en) * | 2013-09-13 | 2023-10-25 | Huawei Technologies Co., Ltd. | Data transmission method and apparatus |
| CN104579728B (en) * | 2013-10-17 | 2019-02-26 | 中兴通讯股份有限公司 | Network element device configuration and management method, device and network element device |
| CN106803814B (en) * | 2015-11-26 | 2021-01-22 | 中兴通讯股份有限公司 | Method, device and system for establishing flexible Ethernet path |
-
2017
- 2017-06-23 CN CN201710488310.6A patent/CN109120657B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105515816A (en) * | 2014-10-20 | 2016-04-20 | 中兴通讯股份有限公司 | Processing method and apparatus for detection level information |
| CN106850465A (en) * | 2016-12-27 | 2017-06-13 | 深圳市海思半导体有限公司 | A kind of Flex E method for interchanging data and switching equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109120657A (en) | 2019-01-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10158558B1 (en) | Segment routing of packets according to a multicast distribution tree in a network | |
| CN110719185B (en) | Network slice control method and device and computer readable storage medium | |
| US11050657B2 (en) | Method, device and node for message transmission, and computer storage medium | |
| US20200396162A1 (en) | Service function chain sfc-based communication method, and apparatus | |
| US20210274418A1 (en) | Information Transmission Method and Apparatus | |
| CN107370673B (en) | Method, controller and system for establishing forwarding path in network | |
| CN109660442B (en) | Method and device for multicast replication in Overlay network | |
| US20210289436A1 (en) | Data Processing Method, Controller, and Forwarding Device | |
| EP3888280B1 (en) | Methods, apparatus and computer-readable mediums relating to configuration of redundant paths | |
| CN110324159B (en) | Link configuration method, controller and storage medium | |
| US9049030B1 (en) | Methods and apparatus for efficient multicast | |
| EP4002767A1 (en) | Message sending method, device and system applied to distributed router networking | |
| US11616724B2 (en) | Packet transmission method and apparatus | |
| CN107612809A (en) | A kind of multicast list synchronous method and equipment | |
| US20190014035A1 (en) | Information transmission method and device | |
| CN109120657B (en) | Service configuration method and node | |
| WO2022143395A1 (en) | Redundant path creating method, apparatus, and system | |
| CN104754521A (en) | Message transmitting method, wireless access point, wireless controller and system | |
| CN108601055B (en) | Method and system for deploying L3 VPN in L TE mobile backhaul network | |
| CN112312481B (en) | Communication method and system for MEC and multi-operator core network | |
| CN112436990B (en) | Data forwarding method, data forwarding equipment and computer-readable storage medium | |
| CN110830295B (en) | Equipment management method and system | |
| CN115242713A (en) | IPV 6-based segmented routing message forwarding method, configuration method and equipment | |
| WO2023019874A1 (en) | Distributed service forwarding method, apparatus and system, storage medium, and electronic device | |
| CN107579928B (en) | flow forwarding method and system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |