CN114615136A - Flexe interface management method for 5G smart power grid slice - Google Patents
Flexe interface management method for 5G smart power grid slice Download PDFInfo
- Publication number
- CN114615136A CN114615136A CN202210209165.4A CN202210209165A CN114615136A CN 114615136 A CN114615136 A CN 114615136A CN 202210209165 A CN202210209165 A CN 202210209165A CN 114615136 A CN114615136 A CN 114615136A
- Authority
- CN
- China
- Prior art keywords
- flexe
- field
- management
- network
- configuration
- 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.)
- Granted
Links
- 238000007726 management method Methods 0.000 title claims abstract description 112
- 230000005540 biological transmission Effects 0.000 claims abstract description 23
- 230000003068 static effect Effects 0.000 claims abstract description 19
- 238000000034 method Methods 0.000 claims abstract description 15
- 230000002457 bidirectional effect Effects 0.000 claims abstract description 10
- 230000008569 process Effects 0.000 claims abstract description 10
- 230000001360 synchronised effect Effects 0.000 claims abstract description 9
- 238000012795 verification Methods 0.000 claims description 8
- 230000011664 signaling Effects 0.000 claims description 7
- 238000004891 communication Methods 0.000 claims description 6
- 239000000284 extract Substances 0.000 claims description 6
- 238000013507 mapping Methods 0.000 claims description 6
- 230000003993 interaction Effects 0.000 abstract description 4
- 238000005516 engineering process Methods 0.000 description 26
- 239000010410 layer Substances 0.000 description 23
- 238000002955 isolation Methods 0.000 description 6
- 238000004458 analytical method Methods 0.000 description 4
- 230000006855 networking Effects 0.000 description 4
- 239000003795 chemical substances by application Substances 0.000 description 3
- 238000011161 development Methods 0.000 description 3
- 238000012217 deletion Methods 0.000 description 2
- 230000037430 deletion Effects 0.000 description 2
- 239000012634 fragment Substances 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 239000000853 adhesive Substances 0.000 description 1
- 230000001070 adhesive effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 239000012792 core layer Substances 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000012827 research and development Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Images
Classifications
-
- 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/0803—Configuration setting
-
- 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/0893—Assignment of logical groups to network elements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/02—Arrangements for optimising operational condition
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses a Flexe interface management method for a 5G smart grid slice, which defines the format and significance of Flexe management frame parameters; specifically, device management of a FlexE interface is optimized, and a control field related to static/configurable parameters in a FlexE management frame is extended to acquire the state of the FlexE interface, so that network devices which do not need to be configured maintain static interfaces, and FlexE interface parameters of the network devices which need to be configured are configured; the implementation scheme of the dynamic negotiation protocol is optimized, the control field about the parameters of the dynamic negotiation protocol in the Flexe management frame is expanded, the bidirectional transmission configuration is flexibly improved, and the configuration parameters are better and faster obtained; the management of a Flexe client is optimized, an operation character segment is added, and synchronous switching from active calendar configuration to backup calendar configuration is not needed when a negotiation protocol is not started; and a security management process of bidirectional transmission interaction is added, so that the safe and efficient management of the FlexE interface is ensured.
Description
Technical Field
The invention relates to the technical field of communication, in particular to a Flexe interface management method for a 5G smart grid slice.
Background
5G application scenarios can be divided into three categories: enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable low latency communication (uRLLC). Diverse services place different key requirements on the bearer network. The 5G has the requirements for solving the contradiction between the differentiated SLA and the networking cost, needs a bandwidth promotion scheme which can be smoothly upgraded and has cost competitiveness, has the requirements for a telecommunication network with low time delay, has the requirements for realizing service physical isolation and realizing resource 5G slicing by the same network.
The 5G network slice cuts the shared physical infrastructure into a plurality of independent virtual networks, provides customized special network services which run independently and are isolated from each other for different services, and is a key entry point of the 5G service vertical industry. The network slices divide a single physical network into a plurality of virtual networks by utilizing an SDN/NFV technology, each slice represents an independent and virtualized end-to-end network from a wireless access network to a bearer network and a core network, and the slices are insulated from each other so as to meet different requirements of various service scenes on the network. 5G network slices allow operators to split multiple virtual logical end-to-end networks on the same hardware infrastructure. Each network slice is logically isolated from the access network to the transmission network and then to the core network, can adapt to various characteristic requirements of different services 3, and meets the requirements of high capacity, low delay, large connection and multi-service support.
The 5G network slice integrally comprises 4 key technologies of access, transmission, core network domain slice enabling technology, 5G network slice identification and access technology, 5G network slice end-to-end management technology and 5G network slice end-to-end SLA guarantee technology. The access, transmission and core network domain slice enabling technology is used as a basic supporting technology to realize the network slice examples of the access, transmission and core network; the network slice identification and access technology realizes the mapping between the network slice example and the terminal service type, and registers the terminal to the correct network slice example; the 5G network slice end-to-end management technology realizes the arrangement and management of end-to-end network slices; the network slice end-to-end SLA guarantee technology can carry out acquisition analysis and quasi real-time processing on network performance indexes of each domain, and ensures that the performance of the system meets the SLA requirements of users.
And the Flexe technology can meet the requirement of 5G slices. One of the characteristics is to realize decoupling of service bandwidth requirement and physical interface bandwidth. The gradual evolution of the service bandwidth 25G → 50G → 100G → 200G → 400G → xT is easily realized through the port binding and time slot crossing technology through the standard 25GE/100GE rate interface, and the 400G large bandwidth is realized by utilizing the 100GE interface. The 5G era will center on "user experience", and need to provide a user experience rate of 100Mbps or more for a user anytime and anywhere, and in hot spot high capacity areas, even need to provide a user experience rate of 1Gbps and a peak rate of dozens G per base station. In the future, the bearer equipment of the access stratum needs to provide 10GE and 25GE interfaces for base station access, a 100GE interface high-rate interface is used on the network side, and the convergence core layer will adopt 400G or even T level rate networking with higher rate.
The Flexe bandwidth expansion technology ensures that services are strictly and uniformly distributed on each physical interface of a Flexe Group through time slot control, and can adjust the occupation of network bandwidth resources in real time by dynamically increasing or reducing the number of time slots so as to deal with the real-time change of service flow. The Flexe technology is based on an IEEE 802.3 standard, a Flexe Shim layer is introduced between an MAC layer and a PHY layer, and the MAC layer and the PHY layer are decoupled, so that flexible rate matching is realized. Flexe adopts a client/Group structure, wherein Clients is an MAC layer, Group is a PHY layer, and the Flexe layer is used as a transfer station and plays a role of an adhesive. In brief, the PHY layer is divided downwards, the PHY layer is used as a resource pool, and the MAC layer is recoded upwards to adapt to the PHY layer, which is that the traditional packet device, which is a matter done by the FlexE Shim layer, uses a hop-by-hop forwarding strategy for a client service packet, each node device in the network needs to perform MAC layer and MPLS layer analysis on a data packet, the analysis consumes a large amount of time, and the forwarding delay of a single device is up to tens of microseconds. In the LTE mobile backhaul network, the unidirectional delay of the S1 transmission is required to exceed 10ms, ideally 5ms, and X2 is 2 times of S1. In the 5G era, the vertical industries of car networking, industrial control and the like have very strict requirements on time delay, according to the definition of 3GPP, the air interface time delay in the uRLLC scene is as low as 0.5ms, and the one-way end-to-end time delay does not exceed 1ms, and for the backhaul network, the time delay index is about 1/3 of the processing time delay of the core network, namely 100-150 μ s. In order to meet the requirement of ultra-low delay, the bearer network must simultaneously start from two aspects of equipment architecture and network design, and provide microsecond-level equipment forwarding delay and a more effective network forwarding model. Compared with the MPLS technology, the Flexe technology is closer to the physical layer bit stream transmission, so that the Flexe technology is easier to realize ultra-low time delay forwarding, and the requirements of a 5G bearer network can be met. The Flexe technology realizes user service flow forwarding based on a physical layer through a time slot crossing technology, a user message does not need to be analyzed at a network intermediate node, the service flow forwarding process is completed almost in real time, the forwarding time delay of single-hop equipment is realized to be less than 1 mu s, and a foundation is laid for bearing ultra-low time delay service.
The Flexe technology can realize large bandwidth expansion, can realize fine division of high-speed interfaces, and realizes transmission of different low-speed services in different time slots and physical isolation among the different services. The characteristics of the Flexe sub-pipeline and the time slot crossing characteristics of the physical layer are fused, an end-to-end Flexe Tunnel rigid pipeline crossing the network elements can be constructed on the bearing network, and the intermediate node does not need to analyze the service message, so that strict physical layer service isolation is formed. Therefore, the traffic is isolated at the physical layer, and the service is sliced on the whole network, which becomes one of the key requirements for meeting the bearing of 5G diversified scenes.
In general, under different infrastructure conditions, the FlexE supports different 5G service bandwidths. This is called "flexibility". Based on the FlexE channelization function, operators can build end-to-end pipelines on the existing lines. The service levels of these pipes may be different. The Flexe technology has the characteristics that the interface rate is flexible and variable, the interface is decoupled from the optical transmission capability, the QOS of multi-service channelization isolation is met, the channelization isolation of the 5G service is realized, the capacity expansion of the 5G according to the requirement is realized, the functions of 5G fragment bearing and the like are supported, and various requirements of the 5G fragment are flexibly met. Therefore, Flexe is already one of the accepted key technologies of the 5G bearer network and is also the core of the third generation Ethernet technology. The development of 5G is a technological innovation process, the diversity of the requirements also brings a plurality of challenges to the aspects of bandwidth, time delay, service isolation, virtualization and the like of mobile bearing, and the technology of the inventor is based on strong research and development strength and deep understanding of the 5G technology and the development trend of a bearing network to provide a flexE solution for the bearing of 5G and meet the brand-new development opportunity in the 5G era.
Although, much work has been constantly expanding and redefining the sub-protocols of FlexE, this has made the FlexE protocol stack and its interfaces tedious and unmanageable. A flexible overhead frame is defined in FLEXE for conveying flexible group specific information from PE1 to PE2, including configuration information (flexible group number, flexible map, flexible PHY/instance number, CCA, and CCB), status information RPF, and signaling information (CC, CR, and CA). The receiving end uses the configuration information in the overhead frame to verify whether the two ends in the FlexE group are correctly configured with the same value set. If PE2 finds that the information in the overhead sent from PE1 does not match its own configuration, a no match alarm should be raised.
The IETF is currently beginning work on the management of the FlexE interface. draft-jiang-ccamp-FlexE-ifmps-00 draft is some of the necessary considerations that the IETF proposes for FlexE interface management. This draft is used to summarize the problem presentation for FlexE interface management, and also to analyze the configuration requirements for flexible ethernet FlexE interface management. Finally the requirements for the management of the FlexE interface are summarized.
However, the work of the draft working group still stays at the first step, and only the requirement analysis is provided for the interface management configuration of FlexE, and the draft also has the following problems:
(1) the state of the FlexE interface is difficult to obtain through a management frame, so that some simple devices/devices which do not need to be configured are difficult to maintain a static interface, and an SDN controller or a network management system cannot configure interface parameters through the management frame;
(2) the FlexE management frame is difficult to obtain about the parameters of the dynamic negotiation protocol, and the receiving peer can not extract the configuration information related to the dynamic negotiation from the FlexE management frame sent by the sending peer;
(3) the FlexE management frame is not in place for managing the flexible client, firstly, the FlexE management frame is influenced by a dynamic negotiation protocol, and secondly, operations such as adding, deleting, resizing, slot position adjusting and the like are difficult to reflect in the management frame;
(4) the FlexE interface management requirements summarized in the existing draft do not take into account security precautions. The security of the bidirectional transmission interactive process is difficult to guarantee.
Disclosure of Invention
In order to solve the defects in the prior art, the invention aims to provide a method for managing a Flexe interface of a 5G smart grid slice, which defines the format and the meaning of a Flexe management frame parameter and increases a security management process of bidirectional transmission interaction, thereby ensuring the safe and efficient management of the Flexe interface.
In order to realize the purpose of the invention, the technical scheme adopted by the invention is as follows:
A5G smart grid sliced Flexe interface management method is characterized in that an SDN controller or a network management system NMS is connected with a management agent on each network device through a network configuration protocol to configure Flexe interface parameters of the network devices;
extending a control field related to static/configurable parameters in a Flexe management frame, wherein the control field is used for acquiring the state of a Flexe interface, so that network equipment which does not need to be configured keeps the static interface, and the Flexe interface parameters of the network equipment which needs to be configured are configured;
control fields for static/configurable parameters, including SoC _ state field, to indicate current FlexE configuration state; a SoC _ need _ config field for indicating whether the current interface needs to be configured; a Parameter _ control field for representing a Parameter control; a Control _ data field for indicating Control information of the controller.
Further, the length of the SoC _ state field is 2 bits, 00-static state, 01-configurable state; a SoC _ need _ config field with a length of 1bit, combined with the SoC _ state field to dynamically manage the FlexE interface; a Parameter _ control field with a length of 1B for indicating whether the Parameter control is SDN controller control or network management system NMS; a Control _ data field with a length of 2B, the first byte for indicating the controller's own information, and the second byte controller for 8 different controls.
Furthermore, the network device with configured FlexE interface parameters is used as a sending peer, and the other network device is used as a receiving peer to extract configuration information from a FlexE management frame sent by the sending peer; a control field D _ N _ P related to the dynamic negotiation protocol parameter in the extended Flexe management frame is used for indicating whether the dynamic negotiation protocol is enabled and realizing related functions; a D _ N _ P field including an Enable field indicating whether the dynamic negotiation protocol is enabled; a Configuration _ Information field indicating Configuration Information of FlexE; FlexE _ group _ binding _ PHY field, representing the flexible client and its binding PHYs.
Further, the length of the Enable field is 1bit, 0 indicates that the dynamic negotiation is not started, and 1 indicates that the dynamic negotiation is started; a Configuration _ Information field with the length of 2B, which indicates that the receiving peer extracts Configuration Information from a Flexe management frame sent by the sending peer after the dynamic negotiation protocol is enabled; and the length of the Flexe _ group _ binding _ PHY field is 4B, which represents that the flexible client and the binding PHYs thereof are configured, and a flexible overhead channel is established for the correct work of the signaling protocol.
Further, aiming at Flexible management of network equipment, a field Flexible _ client _ management about Flexible client management parameters is added in a Flexe management frame; if the negotiation protocol is not enabled, synchronous switching from the active calendar configuration to the backup calendar configuration is not required; if the negotiation protocol is started, sequentially operating the backup calendar of each network device;
a Flexible _ client _ management field comprising an FCM _ Operator field indicating a specific Operator; FCM _ Parameter field, indicating operand and number.
Further, the FCM _ Operator field, length 1B, 01 — indicates that one or more clients are added; 02 — represents the deletion of one or more clients; 03-denotes resizing one or more clients; 04 — represents adjusting one or more client slot positions; 05 to subsequent operators are temporarily reserved for subsequent expansion operations;
FCM _ Parameter field, length 1B + nB +1B, first byte representing the number of operands, second to fifth bytes representing the IDs of the operands, and sixth byte representing the operation Parameter, i.e., the adjusted size.
Further, the network device reserves the same number of time slots or bandwidths in both directions through the same FlexE link, the expected value of the FlexE parameter received for the network device will be the same as the parameter value configured in the same transmission direction, and if the received parameter value is different from the locally configured parameter value, the network device reports a mismatch to the SDN controller/NMS.
Further, the specific steps of the secure communication flow during bidirectional transmission between the network devices are as follows:
(6) a sending peer A and a receiving peer B initialize an all-zero field BF of three bytes;
(7) the two parties are divided into three groups according to the local configuration parameter values and Flexe group numbers, PHY numbers and calendar configurations, and each group is mapped into BF fields according to specific three HASH functions; namely:
BF(Hi(x))＝1(i＝1、2、3)
(8) both parties thus get BF', and the sending peer A handles BFa' add to the end of management frame;
(9) reception of BF by receiving Peer Ba' calculating BF according to step (2)abWhich fields are not matched can be found in the process of (2);
(10) if no unmatched content appears in the step (4), representing that the security verification is passed; otherwise the receiving peer sends a mismatch report to the SDN controller/NMS.
Further, taking the Flexe group number as an example, assume that any of three values of the set of computation mappings are 0, 1 and the received BFa' no match, i.e. no match of the numbers of the FlexE groups of both parties; the verification method of the PHY number and calendar configuration is the same.
Compared with the prior art, the invention has the following advantages:
first, device management of the FlexE interface is optimized, some simple devices/devices that do not need to be configured may keep a static interface through management frames, while interface parameters that need to be configured are configured by the SDN controller or the network management system. Therefore, the traffic is isolated at the physical layer, and the service is sliced on the whole network, which becomes one of the key requirements for meeting the bearing of 5G diversified scenes.
And secondly, the implementation scheme of the dynamic negotiation protocol is optimized, the newly added dynamic negotiation protocol parameters are utilized, the bidirectional transmission configuration is flexibly improved, and the configuration parameters are better and faster obtained.
And thirdly, the management of a Flexe client is optimized, an operation character segment is added, and synchronous switching from active calendar configuration to backup calendar configuration is not needed when a negotiation protocol is not started.
Fourthly, the safety interaction process of the Flexe interface is optimized, so that the safety and the high efficiency of the Flexe interface are guaranteed, and the correctness and the high efficiency of the configuration of each parameter of the Flexe interface are ensured.
Drawings
FIG. 1 is a Flexe management overview;
fig. 2 is a schematic diagram of the key steps of the FlexE client two-way transmission security verification.
Detailed Description
The technical solution of the present invention is further described below with reference to the accompanying drawings and examples. The following examples are only for illustrating the technical solutions of the present invention more clearly, and the protection scope of the present application is not limited thereby.
As shown in fig. 1, the present invention describes FlexE interface management of a FlexE group between a first device PE1 and a second device PE2, where PE1 and PE2 are network devices, such as routers or OTN products. The SDN controller/network management system NMS may manage the FlexE group between PE1 and PE2 by interacting with PE1 and PE2, respectively, by interfacing with management agents on each PE node using network configuration protocols Netconf or Restconf.
Netconf provides mechanisms for installing, manipulating, and deleting configurations of network devices, the manipulation of which is implemented on top of a simple remote call layer (RPC). Restconf is Netconf using XML messages over HTTP/HTTPS.
A Network Management System (NMS), a Network Management System in a mobile communication Network, whose Management objects may include all entities in the Network, such as: network devices, applications, server systems, routers, switches, auxiliary devices, etc., provide a system-wide view of the network to the network system administrator.
Software Defined Networking (SDN), a novel Network innovation architecture, is an implementation of Network virtualization, and separates a control plane and a data plane of a Network device, thereby implementing flexible control of Network traffic and making a Network as a pipeline more intelligent.
The Flexe interface parameters of the network device are configured by the SDN controller or the NMS, so that the control field of the Flexe management frame is extended, and the state of the Flexe interface is better acquired, so that some simple network devices and network devices which do not need to be configured keep static interfaces, and the Flexe interface parameters of the network devices which need to be configured are configured by the SDN controller or the NMS.
Control field definitions for static/configurable parameters added in the FlexE management frame include SoC _ state, SoC _ need _ configuration, Parameter _ Control, Control _ data fields for describing whether the state of the FlexE interface is in a static or configurable state, and corresponding Control information.
Wherein, the length of the SoC _ state field is 2 bits, and the SoC _ state field is used for indicating the current FlexE configuration state; 00 — static, if FlexE is static, a FlexE group consists of a fixed number of FlexE entities, e.g., a simple binding of a single fixed client or a fixed calendar configuration. Some simple devices may only support static configurations. 01-configurable State. 10. And 11, reserving the subsequent state for expansion in consideration of protocol expandability.
A SoC _ need _ config field, with a length of 1bit, for indicating whether the current interface needs to be configured to dynamically manage the FlexE interface (or configuration is not possible), which, in combination with the previous SoC _ state field, may take into account all situations, e.g. a static interface may need to be configured or may already be configured without reconfiguration.
A Parameter _ control field with a length of 1B is used to indicate the Parameter control, if FlexE is configurable, the FlexE interface parameters may be controlled by the SDN controller or may be configured by the network management system NMS.
A Control _ data field having a length of 2B for indicating Control information of the controller, a first byte for indicating information of the controller itself, and a second byte controller for selecting 8 different controls.
In summary, the SDN controller/network management system NMS is connected to the management agent of each network device node PE through a network configuration protocol to configure the FlexE interface parameters of the network device; and extending a control field of the Flexe management frame, wherein the control field is used for acquiring the state of a Flexe interface, so that the network equipment which does not need to be configured keeps a static interface, and the Flexe interface parameters of the network equipment which needs to be configured are configured.
The first device PE1 configured with the FlexE interface parameters may act as a sending peer, and the second device PE2 acting as a receiving peer may extract configuration information from the FlexE management frame sent by the sending peer, thereby extending a dynamic negotiation protocol by adding the control field of the FlexE management frame. From the perspective of bi-directional transmission, a receiving peer in one direction also acts as a sending peer in the other direction.
Two calendar configurations are used in the FlexE data plane to facilitate reconfiguration, namely CCA and CCB. They are actually two lists; for example, for a PHY of 100GBASE-R, each list is 20 x2 bytes; or 4 x 20 x2 bytes for a PHY of 400GBASE-R, where each list entry indicates the client number carried in the calendar slot.
At any given time, only one calendar configuration is active for mapping and demapping the elastic clients to and from the elastic group. When a switch of calendar configuration adds/deletes/adjusts a flexible client in the flexible group, the switch does not affect existing clients whose size and calendar slot allocation are not changed.
The status information indicates the status of the bound physical device, and only RPF (remote PHY failure) is currently defined in the established RFC and draft, and if set to 1, the remote end is notified of the local detection of PHY failure. Signaling information may be used to coordinate the switch between PE1 and PE2 from the active calendar configuration CCA to the standby calendar configuration CCB. CC. CR and CA are used to coordinate the switching of calendar A to calendar B between the FLEXE mux and the FlexE demux (i.e., the source and sink of the FlexE group), and vice versa. The protocol may be implemented at will. The existing RFC and draft define a dynamic negotiation protocol for automatically switching calendars in a flexible group by signaling in the flexible group overhead.
The invention adds a control field D _ N _ P field (Dynamic Negotiation Protocol) related to the Dynamic Negotiation Protocol parameter in the Flexe management frame to indicate whether the Dynamic Negotiation Protocol is enabled and the related function is realized, wherein the D _ N _ P field comprises Enable, Configuration _ Information and Flexe _ group _ binding _ PHY.
The key point is that after the dynamic negotiation is started when the field is 1, the latter two pieces of configuration information are used.
Configuration _ Information field, length 2B, represents the Configuration Information of FlexE, if the dynamic negotiation protocol is enabled, if one peer enables negotiation, the other peer must also enable negotiation; the receiving peer may further extract configuration information (in particular CCA and CCB) from the FlexE management frame sent by the sending peer. If the negotiation protocol is enabled, the receiving peer does not need to configure any Flexe parameters.
The FlexE _ group _ binding _ PHY field, with a length of 4B, represents a flexible client and its binding PHYs, and must first configure a flexible group (flexible client) and its binding PHYs in order to establish a flexible overhead channel for the signaling protocol to work properly. Thus, both ends of PEs require FlexE configuration even if negotiation is enabled.
Since the dynamic signaling of CC, CR and CA is done automatically in the data plane; in particular, CR and CA are requests and acknowledgments that are dynamically exchanged through the FlexE overhead, CC decides whether CCA or CCB is active, and the mechanism works on the FlexE data plane independently of the management plane.
In summary, the first device PE1 configured with the FlexE interface parameters may serve as a sending peer, and the second device PE2 serving as a receiving peer may extract configuration information from a FlexE management frame sent by the sending peer, so that a control field of the FlexE management frame is added, and a dynamic negotiation protocol is extended; to indicate whether the dynamic negotiation protocol is enabled and the related function is implemented.
If the negotiation protocol is not enabled, synchronous switching from the active calendar configuration to the backup calendar configuration is not required; to enable flexible management of clients (network devices), definitions on flexible client management parameters are added in the FlexE management frame.
If the dynamic negotiation protocol is not enabled, the management of the FlexE client (add/delete/resize slot locations) is typically a sequential operation on the current calendar of each FlexE PE, and the retrieval of the calendar configuration values is also based on the active calendar. Thus, a synchronous switch from the active calendar configuration to the backup calendar configuration is not required. However, some client traffic may be lost during reconfiguration.
Management of the FlexE client (add/delete/resize slot location) is typically a sequential operation to the backup calendar of each FlexE PE if the negotiation protocol is enabled.
The invention adds a field Flexible _ client _ management in a FlexiE management frame to support Flexible client (network equipment) management, comprising an FCM _ Operator and an FCM _ Parameter.
The FCM _ Operator field has the length of 1B, indicates a specific Operator, and 01-indicates that one or more clients are added; 02 — represents the deletion of one or more clients; 03-denotes resizing one or more clients; 04 — represents adjusting one or more client slot positions; 05 to subsequent operators are temporarily reserved for subsequent expand operations.
The FCM _ Parameter field, length 1B + nB +1B, indicates the operands and number, and the first byte represents the number of operands. Here we assume that three objects are operated on simultaneously. The second to fifth bytes represent the ID of the operated object. Assuming that three objects are operated at the same time, the sixth byte represents an operation parameter, i.e., a post-call size.
If the negotiation protocol is not enabled, a synchronous switch from the active calendar configuration to the backup calendar configuration is not required. If the negotiation protocol is enabled, the management of the Flexe client is typically a sequential operation of the backup calendar for each Flexe PE.
The dynamic negotiation control peer then synchronously switches the backup calendar configuration to the active calendar configuration. Since client traffic is not lost during reconfiguration, it is recommended as a default mode of operation, so the switch is not interrupted. In addition, the retrieval of calendar configuration values should be based on the new active calendar after protocol convergence (calculated according to [ FLEXE ], convergence time is expected to be about 10 ms). In both cases, the management plane only needs to handle a single calendar, and does not need to monitor whether the calendar is CCA or CCB from the SDN/NMS perspective.
In summary, to achieve Flexible management of clients (network devices), a field Flexible _ client _ management about Flexible client management parameters is added to a FlexE management frame, which includes FCM _ Operator and FCM _ Parameter. If the negotiation protocol is not enabled, a synchronous switch from the active calendar configuration to the backup calendar configuration is not required. Management of the FlexE client (network device) is typically a sequential operation of the backup calendar for each FlexE PE if the negotiation protocol is enabled.
Flexible links (including each bonded physical link) are always bidirectional, and flexible clients (network devices) typically reserve the same amount of time slots or bandwidth in both directions over the same FlexE link. For a FlexE client, the expected values of the received FlexE parameters will be the same as those configured in the transmission direction on the same PE. If the received parameter values are different from the locally configured parameter values, the peer should report a mismatch to the SDN controller/NMS. Examples of mismatches may include: FlexE group number mismatch, FlexE PHY number mismatch, calendar configuration mismatch.
This embodiment specifies a secure communication flow between network devices during bidirectional transmission, which is specifically as follows:
(11) a Flexe sender and a Flexe receiver initialize an all-zero field BF of three bytes;
(12) as shown in fig. 2, two parties are divided into three groups according to local configuration parameter values and FlexE group numbers, PHY numbers and calendar configurations, and each group is mapped into BF fields according to specific three (or more, but not too many, which may cause too many BF HASH collisions and thus losing meaning); namely:
BF(Hi(x))＝1(i＝1、2、3)
note: the three hash functions are built in each hardware, so long as the consistency of the sender and the receiver is kept, and no special requirement is required. I.e., three sets of at most 9 1 maps that are appropriately sized relative to a 3-byte 24-bit BF, and that minimize hash collisions.
(13) Both parties thus obtain BF'; assuming now that A is the sender and B is the receiver, A will BFa' add to the end of management frame;
(14) receiving party B receives BFa', calculating BF in accordance with step (2)abWhich fields are not matched can be found in the process of (2); taking the FlexE group number as an example: assume that any 0, 1 of the three values of the set of computation mappings and the received BFa' mismatch, i.e. representing both FlexE group numbers do not match;
the verification method of the PHY number and calendar configuration is the same.
(15) If no mismatching content appears in the step (4), representing that the security verification is passed; otherwise the receiver sends a mismatch report to the SDN controller/NMS.
In summary, the network devices typically reserve the same number of slots or bandwidth in both directions through the same FlexE link. The expected values for the FlexE parameters received by the network device will be the same as those configured in the transmission direction on the same PE. If the received parameter values are different from the locally configured parameter values, the peer should report a mismatch to the SDN controller/NMS.
The two parties can obtain a group of specific bit streams by a method of Hash mapping and privacy enhancement. Both parties can perform security verification on the group number of Flex, the number of the group PHY, and the group calendar configuration number by comparing the group bit streams. The embodiment ensures the safety and the high efficiency of the Flexe interface and ensures the correctness of the configuration of each parameter of the Flexe interface.
Compared with the prior art, the invention has the following advantages:
first, device management of the FlexE interface is optimized, some simple devices/devices that do not need to be configured may keep a static interface through management frames, while interface parameters that need to be configured are configured by the SDN controller or the network management system. Therefore, the traffic is isolated at the physical layer, and the service is sliced on the whole network, which becomes one of the key requirements for meeting the bearing of 5G diversified scenes.
And secondly, the implementation scheme of the dynamic negotiation protocol is optimized, the newly added dynamic negotiation protocol parameters are utilized, the bidirectional transmission configuration is flexibly improved, and the configuration parameters are better and faster obtained.
And thirdly, the management of a Flexe client is optimized, an operation character segment is added, and synchronous switching from active calendar configuration to backup calendar configuration is not needed when a negotiation protocol is not started.
Fourthly, the safety interaction process of the Flexe interface is optimized, so that the safety and the high efficiency of the Flexe interface are guaranteed, and the correctness and the high efficiency of the configuration of each parameter of the Flexe interface are ensured.
The present applicant has described and illustrated embodiments of the present invention in detail with reference to the accompanying drawings, but it should be understood by those skilled in the art that the above embodiments are merely preferred embodiments of the present invention, and the detailed description is only for the purpose of helping the reader to better understand the spirit of the present invention, and not for limiting the scope of the present invention, and on the contrary, any improvement or modification made based on the spirit of the present invention should fall within the scope of the present invention.
Claims (9)
1. A Flexe interface management method for 5G smart grid slices is characterized in that an SDN controller or a network management system NMS is connected with a management agent on each network device through a network configuration protocol to configure Flexe interface parameters of the network devices;
extending a control field related to static/configurable parameters in a Flexe management frame, wherein the control field is used for acquiring the state of a Flexe interface, so that network equipment which does not need to be configured keeps the static interface, and the Flexe interface parameters of the network equipment which needs to be configured are configured;
control fields for static/configurable parameters, including SoC _ state field, to indicate current FlexE configuration state; a SoC _ need _ config field for indicating whether the current interface needs to be configured; a Parameter _ control field for indicating a Parameter control; a Control _ data field for indicating Control information of the controller.
2. The Flexe interface management method for 5G smart grid slices of claim 1,
the length of the SoC _ state field is 2 bits, 00-static state, 01-configurable state; the SoC _ need _ config field is 1bit in length and is combined with the SoC _ state field to dynamically manage a Flexe interface; a Parameter _ control field with a length of 1B for indicating whether the Parameter control is SDN controller control or network management system NMS; a Control _ data field with a length of 2B, the first byte for indicating the controller's own information, and the second byte controller for 8 different controls.
3. The Flexe interface management method for 5G smart grid slices of claim 1,
the network equipment with the configured Flexe interface parameters is used as a sending peer, and the other network equipment is used as a receiving peer to extract configuration information from a Flexe management frame sent by the sending peer; a control field D _ N _ P related to the dynamic negotiation protocol parameter in the extended Flexe management frame is used for indicating whether the dynamic negotiation protocol is enabled and realizing related functions; a D _ N _ P field including an Enable field indicating whether the dynamic negotiation protocol is enabled; a Configuration _ Information field indicating Configuration Information of FlexE; FlexE _ group _ binding _ PHY field, representing the flexible client and its binding PHYs.
4. The Flexe interface management method for 5G smart grid slices of claim 3,
an Enable field with the length of 1bit, wherein 0 represents that the dynamic negotiation is not started, and 1 represents that the dynamic negotiation is started; a Configuration _ Information field with the length of 2B indicates that the receiving peer extracts Configuration Information from a Flexe management frame sent by the sending peer after the dynamic negotiation protocol is enabled; and the length of the Flexe _ group _ binding _ PHY field is 4B, which represents that the flexible client and the binding PHYs thereof are configured, and a flexible overhead channel is established for the correct work of the signaling protocol.
5. The Flexe interface management method for 5G smart grid slices of claim 3,
aiming at the Flexible management of network equipment, a field Flexible _ client _ management about Flexible client management parameters is added in a Flexe management frame; if the negotiation protocol is not enabled, synchronous switching from the active calendar configuration to the backup calendar configuration is not required; if the negotiation protocol is started, sequentially operating the backup calendar of each network device;
a Flexible _ client _ management field comprising an FCM _ Operator field indicating a specific Operator; FCM _ Parameter field, indicating operand and number.
6. The Flexe interface management method for 5G smart grid slices of claim 5, wherein,
an FCM _ Operator field, 1B, 01 — indicating the addition of one or more clients; 02-denotes deleting one or more clients; 03-denotes resizing one or more clients; 04 — represents adjusting one or more client slot positions; 05 to the subsequent operator is temporarily reserved for the subsequent expansion operation;
FCM _ Parameter field, length 1B + nB +1B, first byte representing the number of operands, second to fifth bytes representing the IDs of the operands, and sixth byte representing the operation Parameter, i.e., the adjusted size.
7. The Flexe interface management method for 5G smart grid slices of claim 3,
the network device reserves the same number of time slots or bandwidths in two directions through the same Flexe link, the expected value of a Flexe parameter received by the network device is the same as the parameter value configured in the same transmission direction, and if the received parameter value is different from the locally configured parameter value, the network device reports the mismatch to the SDN controller/NMS.
8. The Flexe interface management method for 5G smart grid slices of claim 7,
the safety communication flow during the bidirectional transmission between the network devices comprises the following specific steps:
(1) a sending peer A and a receiving peer B initialize an all-zero field BF of three bytes;
(2) the two parties are divided into three groups according to the local configuration parameter values and Flexe group numbers, PHY numbers and calendar configurations, and each group is mapped into BF fields according to specific three HASH functions; namely:
BF(Hi(x))＝1(i＝1、2、3)
(3) both parties thus get BF', and the sending peer A handles BFa' add to the end of management frame;
(4) reception of BF by receiving Peer Ba' calculating BF according to step (2)abWhich fields are not matched can be found in the process of (2);
(5) if no unmatched content appears in the step (4), representing that the security verification is passed; otherwise the receiving peer sends a mismatch report to the SDN controller/NMS.
9. The Flexe interface management method for 5G smart grid slices according to claim 8,
taking the Flexe group number as an example, assume that any of the three values of the set of computation mappings are 0, 1 and BF receiveda' no match, i.e. no match of the numbers of the FlexE groups of both parties; the verification method of the PHY number and calendar configuration is the same.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210209165.4A CN114615136B (en) | 2022-03-04 | 2022-03-04 | FlexE interface management method for 5G smart grid slice |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210209165.4A CN114615136B (en) | 2022-03-04 | 2022-03-04 | FlexE interface management method for 5G smart grid slice |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114615136A true CN114615136A (en) | 2022-06-10 |
| CN114615136B CN114615136B (en) | 2023-10-27 |
Family
ID=81860556
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210209165.4A Active CN114615136B (en) | 2022-03-04 | 2022-03-04 | FlexE interface management method for 5G smart grid slice |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114615136B (en) |
Citations (21)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106612220A (en) * | 2015-10-27 | 2017-05-03 | 中兴通讯股份有限公司 | Flexible Ethernet lane management method and apparatus |
| CN106612203A (en) * | 2015-10-27 | 2017-05-03 | 中兴通讯股份有限公司 | Method and apparatus for processing data flow of flexible Ethernet client |
| WO2017070851A1 (en) * | 2015-10-27 | 2017-05-04 | Zte Corporation | Channelization for flexible ethernet |
| CN106792820A (en) * | 2016-12-27 | 2017-05-31 | 南京邮电大学 | The small base station control protocol and method of a kind of use SDN controllers |
| CN108243035A (en) * | 2016-12-26 | 2018-07-03 | 华为技术有限公司 | DCN message processing methods, the network equipment and network system |
| CN108631873A (en) * | 2017-03-21 | 2018-10-09 | 中兴通讯股份有限公司 | Receiving/transmission method, device, sending device and the receiving device of network management information |
| CN109995588A (en) * | 2019-03-29 | 2019-07-09 | 烽火通信科技股份有限公司 | A kind of flexible ethernet link management method and system |
| US20190319742A1 (en) * | 2016-12-27 | 2019-10-17 | Huawei Technologies Co., Ltd. | Radio fronthaul interface signal transmission method, network device, and system |
| CN110557217A (en) * | 2018-06-01 | 2019-12-10 | 华为技术有限公司 | Service data processing method and device |
| US20200007255A1 (en) * | 2015-06-30 | 2020-01-02 | Ciena Corporation | Flexible Ethernet switching systems and methods |
| CN110677918A (en) * | 2018-07-03 | 2020-01-10 | 中国电信股份有限公司 | Link state information forwarding method, system and device |
| CN111082957A (en) * | 2018-10-22 | 2020-04-28 | 中兴通讯股份有限公司 | Port configuration detection method, terminal and computer-readable storage medium |
| US20200228458A1 (en) * | 2017-09-28 | 2020-07-16 | Huawei Technologies Co., Ltd. | Data transmission method, apparatus, and system |
| CN111565113A (en) * | 2019-02-13 | 2020-08-21 | 烽火通信科技股份有限公司 | Flexible Ethernet network topology abstraction method and system for SDN controller |
| US20210044482A1 (en) * | 2018-04-23 | 2021-02-11 | Huawei Technologies Co., Ltd. | System, Function and Interface for Interconnecting Multi-Domain Network Slice Control and Management |
| CN112491492A (en) * | 2019-09-12 | 2021-03-12 | 华为技术有限公司 | Method and device for time slot negotiation |
| WO2021047538A1 (en) * | 2019-09-12 | 2021-03-18 | 华为技术有限公司 | Timeslot negotiation method and device |
| CN112929199A (en) * | 2019-12-06 | 2021-06-08 | 华为技术有限公司 | Method, apparatus and computer readable storage medium for managing flexible Ethernet group |
| CN113055210A (en) * | 2019-12-27 | 2021-06-29 | 中国移动通信有限公司研究院 | Method and equipment for sending interface information |
| CN113839870A (en) * | 2020-06-24 | 2021-12-24 | 华为技术有限公司 | Path creation method, device and system |
| CN113973051A (en) * | 2020-07-25 | 2022-01-25 | 华为技术有限公司 | Interface configuration method and device |
-
2022
- 2022-03-04 CN CN202210209165.4A patent/CN114615136B/en active Active
Patent Citations (21)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20200007255A1 (en) * | 2015-06-30 | 2020-01-02 | Ciena Corporation | Flexible Ethernet switching systems and methods |
| CN106612203A (en) * | 2015-10-27 | 2017-05-03 | 中兴通讯股份有限公司 | Method and apparatus for processing data flow of flexible Ethernet client |
| WO2017070851A1 (en) * | 2015-10-27 | 2017-05-04 | Zte Corporation | Channelization for flexible ethernet |
| CN106612220A (en) * | 2015-10-27 | 2017-05-03 | 中兴通讯股份有限公司 | Flexible Ethernet lane management method and apparatus |
| CN108243035A (en) * | 2016-12-26 | 2018-07-03 | 华为技术有限公司 | DCN message processing methods, the network equipment and network system |
| CN106792820A (en) * | 2016-12-27 | 2017-05-31 | 南京邮电大学 | The small base station control protocol and method of a kind of use SDN controllers |
| US20190319742A1 (en) * | 2016-12-27 | 2019-10-17 | Huawei Technologies Co., Ltd. | Radio fronthaul interface signal transmission method, network device, and system |
| CN108631873A (en) * | 2017-03-21 | 2018-10-09 | 中兴通讯股份有限公司 | Receiving/transmission method, device, sending device and the receiving device of network management information |
| US20200228458A1 (en) * | 2017-09-28 | 2020-07-16 | Huawei Technologies Co., Ltd. | Data transmission method, apparatus, and system |
| US20210044482A1 (en) * | 2018-04-23 | 2021-02-11 | Huawei Technologies Co., Ltd. | System, Function and Interface for Interconnecting Multi-Domain Network Slice Control and Management |
| CN110557217A (en) * | 2018-06-01 | 2019-12-10 | 华为技术有限公司 | Service data processing method and device |
| CN110677918A (en) * | 2018-07-03 | 2020-01-10 | 中国电信股份有限公司 | Link state information forwarding method, system and device |
| CN111082957A (en) * | 2018-10-22 | 2020-04-28 | 中兴通讯股份有限公司 | Port configuration detection method, terminal and computer-readable storage medium |
| CN111565113A (en) * | 2019-02-13 | 2020-08-21 | 烽火通信科技股份有限公司 | Flexible Ethernet network topology abstraction method and system for SDN controller |
| CN109995588A (en) * | 2019-03-29 | 2019-07-09 | 烽火通信科技股份有限公司 | A kind of flexible ethernet link management method and system |
| CN112491492A (en) * | 2019-09-12 | 2021-03-12 | 华为技术有限公司 | Method and device for time slot negotiation |
| WO2021047538A1 (en) * | 2019-09-12 | 2021-03-18 | 华为技术有限公司 | Timeslot negotiation method and device |
| CN112929199A (en) * | 2019-12-06 | 2021-06-08 | 华为技术有限公司 | Method, apparatus and computer readable storage medium for managing flexible Ethernet group |
| CN113055210A (en) * | 2019-12-27 | 2021-06-29 | 中国移动通信有限公司研究院 | Method and equipment for sending interface information |
| CN113839870A (en) * | 2020-06-24 | 2021-12-24 | 华为技术有限公司 | Path creation method, device and system |
| CN113973051A (en) * | 2020-07-25 | 2022-01-25 | 华为技术有限公司 | Interface configuration method and device |
Non-Patent Citations (1)
| Title |
|---|
| 姜文;刘立康;: "基于持续集成的PC-Lint静态检查", 计算机技术与发展, vol. 26, no. 11 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114615136B (en) | 2023-10-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20240040018A1 (en) | Communication method, communications device, and storage medium | |
| CN110049512B (en) | Forward-transmission network data processing device and method | |
| WO2018127144A1 (en) | Method, device and system for managing network slice instance | |
| WO2019228428A1 (en) | Method and device for adjusting bandwidth of transmission channel in flexible ethernet | |
| WO2018219229A1 (en) | Communication method and network device | |
| CN1246024A (en) | Method for providing wireless communication by means of loading circuit in a radio communication system | |
| WO2022016831A1 (en) | Method and device for flexe low-speed service processing | |
| CN109996296B (en) | Method and equipment for adjusting bandwidth | |
| US11729104B1 (en) | Apparatus and method for providing hybrid access coordination | |
| WO2005011302A1 (en) | A method of transformation between permanent connection and switched connection in optical network | |
| EP3614626A1 (en) | Potn system, potn intercommunication module, and packet intercommunication method | |
| CN104685959B (en) | Passive radio link control entity with unified interface | |
| CN107277861A (en) | A kind of distributed cut-in method of mobile whole network | |
| US10869222B2 (en) | Data frame transmission method and apparatus for virtual elastic CPRI interface | |
| CN109246756A (en) | data distribution method and device | |
| CN113596917A (en) | Method and device for realizing GTP communication data message processing based on signaling assistance | |
| CN114615136B (en) | FlexE interface management method for 5G smart grid slice | |
| CN114173383A (en) | Channel bandwidth adjusting method, device and node | |
| Habetha et al. | Central controller handover procedure for ETSI-BRAN HiperLAN/2 ad hoc networks and clustering with quality of service guarantees | |
| CN101296143B (en) | Method for multiplying band width of wireless communication system | |
| CN104052569B (en) | Method and device for switching MCS | |
| JP2013179494A (en) | Virtual network infrastructure control system and method | |
| CN109586886A (en) | A kind of data transmission system | |
| WO2020207429A1 (en) | Message processing method and apparatus, and computer-readable storage medium | |
| WO2023082087A1 (en) | Control signaling transmission method, communication node, and base station |
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 |