CN114615136B - FlexE interface management method for 5G smart grid slice - Google Patents
FlexE interface management method for 5G smart grid slice Download PDFInfo
- Publication number
- CN114615136B CN114615136B CN202210209165.4A CN202210209165A CN114615136B CN 114615136 B CN114615136 B CN 114615136B CN 202210209165 A CN202210209165 A CN 202210209165A CN 114615136 B CN114615136 B CN 114615136B
- Authority
- CN
- China
- Prior art keywords
- flexe
- management
- field
- configuration
- network
- 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
- 238000007726 management method Methods 0.000 title claims abstract description 111
- 230000005540 biological transmission Effects 0.000 claims abstract description 22
- 230000003068 static effect Effects 0.000 claims abstract description 18
- 230000001360 synchronised effect Effects 0.000 claims abstract description 9
- 230000002457 bidirectional effect Effects 0.000 claims abstract description 8
- 238000000034 method Methods 0.000 claims description 13
- 230000027455 binding Effects 0.000 claims description 8
- 238000009739 binding Methods 0.000 claims description 8
- 230000011664 signaling Effects 0.000 claims description 7
- 238000012795 verification Methods 0.000 claims description 7
- 238000004891 communication Methods 0.000 claims description 6
- 239000000284 extract Substances 0.000 claims description 6
- 230000008569 process Effects 0.000 claims description 6
- 238000004364 calculation method Methods 0.000 claims description 2
- 230000003993 interaction Effects 0.000 abstract description 5
- 230000001965 increasing effect Effects 0.000 abstract description 4
- 238000005516 engineering process Methods 0.000 description 28
- 239000010410 layer Substances 0.000 description 23
- 238000002955 isolation Methods 0.000 description 6
- 239000003795 chemical substances by application Substances 0.000 description 3
- 238000011161 development Methods 0.000 description 3
- 238000013507 mapping Methods 0.000 description 3
- 230000007246 mechanism Effects 0.000 description 2
- 230000006855 networking Effects 0.000 description 2
- 239000000853 adhesive Substances 0.000 description 1
- 230000001070 adhesive effect Effects 0.000 description 1
- 238000004458 analytical method Methods 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 230000005465 channeling 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
- 238000010586 diagram Methods 0.000 description 1
- 230000002708 enhancing 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
- 238000012545 processing Methods 0.000 description 1
- 238000012827 research and development Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
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
Abstract
The application discloses a FlexE interface management method for 5G smart grid slices, which defines the format and meaning of FlexE management frame parameters; specifically, the device management of the FlexE interface is optimized, and the control field of the FlexE management frame about the static/configurable parameters is extended to obtain the state of the FlexE interface, so that the network device which does not need to be configured maintains the static interface, and the FlexE interface parameters of the network device which needs to be configured are configured; the implementation scheme of the dynamic negotiation protocol is optimized, the control field of the FlexE management frame about the parameters of the dynamic negotiation protocol is expanded, the bidirectional transmission configuration is flexibly improved, and the configuration parameters are better and faster acquired; 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 flow of bidirectional transmission interaction is increased, so that the secure and efficient management of the FlexE interface is ensured.
Description
Technical Field
The application relates to the technical field of communication, in particular to a FlexE interface management method for 5G smart grid slices.
Background
5G application scenarios can be divided into three categories: enhanced mobile broadband (emmbb), mass machine type communication (mctc), and ultra-reliable low latency communication (uilllc). The diversity of services puts different key demands on the bearer network. The 5G has the requirements of solving the contradiction between differentiated SLA and networking cost, needs a bandwidth lifting scheme which can be smoothly upgraded and has cost competitiveness, has the requirements of a low-delay telecommunication network, and has the requirements of realizing service physical isolation and resource 5G slicing of 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 are independently operated and isolated from each other for different services, and is a key access point of the 5G service vertical industry. The network slice divides a single physical network into a plurality of virtual networks by utilizing SDN/NFV technology, each slice represents an independent and virtualized end-to-end network from a wireless access network to a bearing network and a core network, and all the slices are mutually insulated so as to meet different requirements of various service scenes on the network. 5G network slicing allows 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 large capacity, low delay, large connection and multi-service support.
The whole 5G network slice comprises an access technology, a transmission technology, a core network domain slice enabling technology, a 5G network slice identification and access technology, a 5G network slice end-to-end management technology and a 5G network slice end-to-end SLA guarantee technology 4 key technologies. The access, transmission and core network domain slice enabling technology is used as a basic supporting technology to realize network slice examples of the access, transmission and core network; the network slice identification and the access technology realize the mapping of the network slice instance and the terminal service type, and register the terminal to the correct network slice instance; the 5G network slice end-to-end management technology realizes the arrangement and management of the end-to-end network slice; the network slice end-to-end SLA guarantee technology can collect, analyze and process the network performance indexes of each domain in a quasi-real-time mode, and ensure that the performance of the system meets the SLA requirements of users.
And FlexE technology can more meet the requirements of 5G slicing. One of the big characteristics is to realize the decoupling of the service bandwidth requirement and the physical interface bandwidth. The gradual evolution of service bandwidths 25G-50G-100G-200G-400G-xT is easily realized through a standard 25GE/100GE rate interface by port binding and time slot crossing technologies, and a 400G large bandwidth is realized by utilizing a 100GE interface. The 5G era will be centered on 'user experience', and needs to provide users with user experience rates above 100Mbps anytime and anywhere, and hot spot high capacity areas even need to provide 1Gbps user experience rate and peak rates of tens of G for a single base station. Future access layer bearer devices need to provide 10GE and 25GE interfaces for base station access, 100GE interfaces with large rate interfaces for network side, and the convergence core layer will employ higher rate 400G, even T level rate networking.
The FlexE bandwidth expansion technology ensures that the service is strictly and uniformly distributed on each physical interface of the FlexE Group through time slot control, and can adjust the network bandwidth resource occupation in real time by dynamically increasing or reducing the number of time slots so as to cope with the real-time change of the service flow. The FlexE technology introduces a FlexE shimm layer between the MAC layer and the PHY layer based on the IEEE 802.3 standard, and decouples the MAC layer and the PHY layer, thereby realizing flexible rate matching. The FlexE adopts a client/Group architecture, wherein Clients are MAC layers, groups are PHY layers, and FlexE layers serve as transfer stations to act as adhesives. In short, the PHY layer is divided downwards and is converted into a resource pool, and the MAC layer is recoded upwards to adapt to the PHY layer, that is, the conventional packet device for things done by the FlexE shimm layer adopts a hop-by-hop forwarding strategy for the client service message, each node device in the network needs to parse the data packet by the MAC layer and the MPLS layer, which consumes a lot of time, and the forwarding delay of a single device is up to tens of microseconds. The LTE mobile backhaul network requires that the S1 unidirectional transmission unidirectional delay exceeds 10ms, ideally 5ms, and x2 is 2 times that of S1. In the 5G era, the time delay requirements of the vertical industries such as the Internet of vehicles, industrial control and the like are very strict, the air interface time delay in a uRLLC scene is reduced to 0.5ms according to the 3GPP definition, the one-way end-to-end time delay is not more than 1ms, and the time delay index is about 1/3 of the processing time delay of a core network, namely 100-150 mu s for a backhaul network. In order to meet the requirement of ultra-low latency, the bearer network must start from both the device architecture and the network design, providing a device forwarding latency on the order of microseconds and a more efficient 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 delay forwarding, and can meet the requirement of a 5G bearing network. The FlexE technology realizes the forwarding of user service flow based on a physical layer through a time slot crossing technology, the user message does not need to be analyzed at a network intermediate node, the service flow forwarding process is completed in near real time, the forwarding time delay of single-hop equipment is less than 1 mu s, and a foundation is laid for bearing ultra-low time delay service.
The FlexE technology not only can realize large bandwidth expansion, but also can realize fine division of a high-rate interface, and realize transmission of different low-rate services in different time slots and physical isolation of the different low-rate services. The FlexE subducting characteristic and the physical layer time slot crossing characteristic are fused, an end-to-end FlexE Tunnel rigid pipeline crossing network elements can be constructed on the bearing network, and an intermediate node does not need to analyze service messages to form strict physical layer service isolation. Therefore, traffic is isolated at a physical layer, and the service performs network slicing on the whole network, so that the traffic becomes one of the key requirements for 5G diversified scene bearing.
In general, flexE enables support of different traffic bandwidths of 5G under different infrastructure conditions. This is the so-called "flexibility". Based on the FlexE channeling function, operators can build end-to-end pipes on existing lines. The service level of these pipes may be different. The FlexE technology has flexible and variable interface rate, the interface is decoupled with the optical transmission capability, the QOS characteristic of multi-service channelized isolation is met, 5G service channelized isolation is realized, 5G capacity expansion according to needs is realized, multiple functions such as 5G slicing bearing and the like are supported, and multiple requirements of 5G slicing are flexibly met. FlexE has been said to be one of the accepted 5G bearer gateway key technologies and is also the core of third generation ethernet technology. The development of 5G is a process of technical innovation, the diversity of requirements also brings a plurality of challenges to mobile bearing in aspects of bandwidth, time delay, service isolation, virtualization and the like, and the technology relies on strong research and development forces and deep understanding of the development trend of 5G technology and bearing network, so that a FlexE solution for 5G bearing is provided, and the brand new development opportunity in the 5G era is met.
Although, many efforts have continuously expanded and redefined the sub-protocols of FlexE, which makes the FlexE protocol stack and its interfaces cumbersome and unmanageable. Flexible overhead frames are defined in flex 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 both ends in the FlexE group are properly configured with the same set of values. If PE2 finds that the information in the overhead sent from PE1 does not match its own configuration, a mismatch alarm should be raised.
The IETF is currently beginning to work on FlexE interface management. The draft-jiang-ccamp-FlexE-ifmps-00 draft is some of the necessary considerations that IETF put forward for FlexE interface management. This draft is used to outline the problem statement of FlexE interface management and also to analyze the configuration requirements of flexible ethernet FlexE interface management. Finally the requirements for FlexE interface management are summarized.
However, the work of the draft workgroup still stays in the first step at present, and only the requirement analysis is provided for the interface management configuration of FlexE, and the following problems exist in the draft:
(1) The state of the FlexE interface is difficult to acquire through a management frame, so that some simple devices/devices not needing configuration 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 acquire about the dynamic negotiation protocol parameters, and the receiving peer cannot 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 managed in place for the flexible client, firstly, it is affected by the dynamic negotiation protocol, and secondly, operations such as adding/deleting/resizing/slot position adjustment are difficult to be embodied in the management frame;
(4) The FlexE interface management requirements of the existing draft summary do not take security precautions into account. The security of the bidirectional transmission interaction flow is difficult to guarantee.
Disclosure of Invention
In order to solve the defects existing in the prior art, the application aims to provide a FlexE interface management method for 5G smart grid slices, which defines the format and meaning of FlexE management frame parameters and increases the security management flow of bidirectional transmission interaction, thereby ensuring the safe and efficient management of the FlexE interface.
In order to achieve the purpose of the application, the technical scheme adopted by the application is as follows:
a FlexE interface management method of 5G smart grid slice, SDN controller or network management system NMS connects with management agent on each network device through network configuration protocol to configure FlexE interface parameter of network device;
the control field of the FlexE management frame about static/configurable parameters is expanded, and the control field is used for acquiring the state of a FlexE interface, so that network equipment which does not need to be configured can keep the static interface, and the FlexE interface parameters of the network equipment which needs to be configured can be configured;
control fields for static/configurable parameters, including a SoC state field, for indicating the current FlexE configuration state; a SoC_need_config field for indicating whether the current interface needs configuration; a parameter_control field for indicating a Parameter controller; a control_data field for indicating Control information of the controller.
Further, the SoC_State field has a length of 2bit, 00-static, 01-configurable state; the SoC_need_config field is 1bit in length and is combined with the SoC_state field to dynamically manage the FlexE interface; a parameter_control field with a length of 1B, which is used to indicate that the Parameter controller is an SDN controller control or network management system NMS; the control_data field has a length of 2B, the first byte is used to indicate the information of the controller itself, and the second byte is used to select 8 different controls.
Further, the network device with the configured FlexE interface parameter is used as a sending peer, and the other network device is used as a receiving peer to extract configuration information from the FlexE management frame sent by the sending peer; extending a control field D_N_P in the FlexE management frame about the dynamic negotiation protocol parameters to indicate whether the dynamic negotiation protocol is enabled and the related function implementation; a D_N_P field including an Enable field indicating whether a dynamic negotiation protocol is enabled; a configuration_information field, which represents Configuration Information of the FlexE; the flexegroup bonding PHY field indicates the flexible client and its binding PHYs.
Further, an Enable field, with a length of 1bit,0 indicates that dynamic negotiation is not enabled, and 1 indicates that dynamic negotiation is enabled; a configuration_information field, with a length of 2B, indicating that the receiving peer extracts Configuration Information from the FlexE management frame sent by the sending peer after the dynamic negotiation protocol is enabled; the flexe_group_binding_phy field, length 4B, represents the configuration of the flexible client and its binding PHYs, establishing a flexible overhead channel for the signaling protocol to work properly.
Further, for Flexible management of network devices, a field flexible_client_management related to Flexible client management parameters is added in a Flexible management frame; 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, a backup calendar sequence operation for each network device;
a flexible_client_management field, including an fcm_operator field, indicating a specific Operator; the fcm_parameter field indicates the number and number of objects operated on.
Further, fcm_operator field, length 1b,01—indicating the addition of one or more clients; 02-means deleting one or more clients; 03-means resizing one or more clients; 04-means adjusting one or more client slot positions; 05 to a subsequent operator temporary reservation for a subsequent expansion operation;
the fcm_parameter field has a length of 1b+nb+1b, the first byte indicates the number of operation objects, the second to fifth bytes indicate the IDs of the operated objects, and the sixth byte indicates the operation parameters, i.e., the adjusted size.
Further, the network device reserves the same number of timeslots or bandwidths in both directions through the same FlexE link, and for the FlexE parameter received by the network device, the expected value 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 network devices are as follows:
(6) The sending peer A and the 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, namely FlexE group numbers, PHY numbers and calendar configuration, and each group is mapped into BF fields according to specific three HASH functions; namely:
BF(H i (x))＝1(i＝1、2、3)
(8) The two parties thus obtain BF' and sending peer A handles BF a ' added to the end of the management frame;
(9) Receiving peer B receives BF a ' BF is calculated according to the step (2) ab In the process of (1), which fields are not matched can be found;
(10) If no unmatched content appears in the step (4), the representative security verification passes; otherwise the receiving peer sends a mismatch report to the SDN controller/NMS.
Further, taking the FlexE group number as an example, assume that there are any 0, 1 and received BF in the three values of the group calculation map a ' mismatch, that is, mismatch of FlexE group numbers representing both parties; the PHY number and calendar configuration verification method is the same as this.
Compared with the prior art, the application has the following advantages:
first, device management of FlexE interfaces is optimized, some simple devices/devices that do not need to be configured can maintain a static interface through management frames, while interface parameters that need to be configured are configured by SDN controllers or network management systems. Therefore, traffic is isolated at a physical layer, and the service performs network slicing on the whole network, so that the traffic becomes one of the key requirements for 5G diversified scene bearing.
Second, the implementation scheme of the dynamic negotiation protocol is optimized, and the newly added dynamic negotiation protocol parameters are utilized to flexibly improve the bidirectional transmission configuration, and better and faster obtain the configuration parameters.
Third, flexE client management is optimized, and the number of operation fields is increased, so that when the negotiation protocol is not enabled, synchronous switching from active calendar configuration to backup calendar configuration is not required.
Fourth, the safety interaction flow 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 key steps of a FlexE client bi-directional transmission security verification.
Detailed Description
The technical scheme of the application is further described below with reference to the accompanying drawings and examples. The following examples are only for more clearly illustrating the technical aspects of the present application, and are not intended to limit the scope of the present application.
As shown in fig. 1, the FlexE interface management of the FlexE group between the first device PE1 and the second device PE2 according to the present application, where the PE1 and the PE2 are network devices, such as routers or OTN products. The SDN controller/network management system NMS may manage FlexE groups between PE1 and PE2 by interacting with PE1 and PE2, respectively, in particular by connecting with management agents on each PE node using the network configuration protocol Netconf or retconf.
Netconf provides a mechanism for installing, manipulating, and deleting network device configurations, the operation of which is implemented above a simple remote call layer (RPC). Restconf is Netconf using XML messages over HTTP/HTTPS.
Network management system (Network Management System, NMS) in a mobile communications network, the management objects of which may include all entities in the network, such as: network devices, applications, server systems, routers, switches, auxiliary devices, etc., provide a system-wide network view to network system administrators.
A software defined network (Software Defined Network, SDN), a novel network innovation architecture, is an implementation of network virtualization, and by separating the control plane and the data plane of network devices, flexible control of network traffic is achieved, so that the network becomes more intelligent as a pipeline.
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 obtained, 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.
The Control field definitions added in the FlexE management frame regarding static/configurable parameters 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.
The SoC_state field has a length of 2 bits and is used for indicating the current FlexE configuration state; 00-static, if the FlexE is static, the FlexE group consists of a fixed number of FlexE entities, e.g. simple bindings for a single fixed client or a fixed calendar configuration. Some simple devices may only support static configuration. 01-configurable state. 10. 11-in view of protocol scalability, the subsequent state is left for expansion.
The soc_need_config field, which is 1bit in length, is used to indicate whether the current interface needs to be configured to dynamically manage the FlexE interface (or impossible to be configured), and in combination with the preceding soc_state field, all situations can be fully considered, for example, the static interface may need to be configured or may have been configured without being reconfigured.
The parameter_control field has a length of 1B and is used to indicate a Parameter controller, and if FlexE is configurable, flexE interface parameters may be controlled by an SDN controller or may be configured by a network management system NMS.
The control_data field has a length of 2B and is used for indicating Control information of the controller, the first byte is used for indicating information of the controller, and the second byte is used 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 FlexE interface parameters of the network device; and expanding a control field of the FlexE management frame to acquire the state of the FlexE interface, so that the network equipment which does not need to be configured maintains a static interface, and the FlexE interface parameters of the network equipment which needs to be configured are configured.
The first device PE1 with the FlexE interface parameters configured can be used as a sending peer, and the second device PE2 as a receiving peer can extract configuration information from the FlexE management frame sent by the sending peer, so that a dynamic negotiation protocol is extended by adding a control field of the FlexE management frame. From a bi-directional transmission point of view, the 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 the elastic clients to the elastic groups and for unmapping the elastic clients from the elastic groups. When a switch of calendar configuration adds/deletes/adjusts an elastic client in an elastic group, the switch does not affect the existing client whose size and calendar slot allocation are unchanged.
The status information indicates the status of the bonded physical device, and only the RPF (remote PHY failure) is currently defined in the established RFC and draft, and if set to 1, the remote is notified that a PHY failure is detected locally. The signaling information may be used to coordinate the switchover between PE1 and PE2 from the active calendar configuration CCA to the standby calendar configuration CCB. CC. CR and CA are used to coordinate calendar A to calendar B switching between Flexe mux and Flexe demux (i.e., sources and sinks of the Flexe group) and vice versa. The protocol may be implemented at will. The RFC and draft have defined a dynamic negotiation protocol for automatically switching calendars in a flexible group by signaling in the flexible group overhead.
The application adds a control field D_N_P field (Dynamic Negotiation Protocol) related to the parameters of the dynamic negotiation protocol in the FlexE management frame to indicate whether the dynamic negotiation protocol is enabled and the related functions are implemented, wherein the D_N_P field comprises Enable, configuration _ Information, flexE _group_bonding_PHY.
The enabling field has a length of 1bit, and indicates whether the dynamic negotiation protocol is enabled, and only 01 two state identifiers are needed, wherein the key is that after the dynamic negotiation is enabled when the field is 1, the following two configuration information are obtained.
A configuration_information field, length 2B, representing 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 (especially 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, length 4B, represents the flexible client and its binding PHYs, must first be configured with the flexible group (flexible client) and its binding PHYs in order to establish a flexible overhead channel for the signaling protocol to function properly. Thus, even if negotiation is enabled, flexE configuration is required at both ends of the PEs.
Since dynamic signaling of CC, CR and CA is done automatically in the data plane; in particular, CR and CA are requests and acknowledgements dynamically exchanged through FlexE overhead, CC decides whether CCA or CCB is active, and the mechanism works on FlexE data plane independently of management plane.
In summary, the first device PE1 configured with the FlexE interface parameter may be used as a sending peer, and the second device PE2 as a receiving peer may extract configuration information from the 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 associated function is implemented.
If the negotiation protocol is not enabled, a synchronous switch from the active calendar configuration to the backup calendar configuration is not required; to achieve flexible management of clients (network devices), definitions on flexible client management parameters are added in FlexE management frames.
If the dynamic negotiation protocol is not enabled, the management of the FlexE clients (add/delete/resize/slot position) is typically a sequential operation on the current calendar of each FlexE PE, and the retrieval of calendar configuration values is also based on the active calendar. Thus, a synchronous switch from an active calendar configuration to a backup calendar configuration is not required. However, during reconfiguration, some client traffic may be lost.
If the negotiation protocol is enabled, management of FlexE clients (add/delete/resize slot locations) is typically a sequential operation of the backup calendar for each FlexE PE.
The application adds a field FlexB_client_management in FlexE management frame to support Flexible client (network device) management, including FCM_operator and FCM_parameter.
Wherein the fcm_operator field, length 1B, indicates a specific Operator, 01—indicates the addition of one or more clients; 02-means deleting one or more clients; 03-means resizing one or more clients; 04-means adjusting one or more client slot positions; 05 to subsequent operators are temporarily reserved for subsequent expansion operations.
The fcm_parameter field, which has a length of 1b+nb+1b, indicates the number and number of operation objects, and the first byte indicates the number of operation objects. 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 on simultaneously, the sixth byte represents the operating parameter, i.e., the size after tuning.
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, 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 to be the default mode of operation and so switching is not interrupted. Furthermore, the retrieval of calendar configuration values should be based on the new active calendar after protocol convergence (calculated from 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 a CCA or CCB from the perspective of the SDN/NMS.
To sum up, in order to implement Flexible management on clients (network devices), fields flexible_client_management related to Flexible client management parameters, including fcm_operator and fcm_parameter, are added in a FlexE management frame. 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, management of FlexE clients (network devices) is typically a sequential operation of the backup calendar for each FlexE PE.
Flexible links (including each bonded physical link) are always bi-directional and flexible clients (network devices) typically reserve the same number of slots or bandwidths in both directions over the same FlexE link. For FlexE clients, the expected values of the received FlexE parameters will be the same as those configured in the transport 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 provides for secure communication flow between network devices during bi-directional transmission, as follows:
(11) The FlexE sender and receiver initialize an all-zero field BF of three bytes;
(12) As shown in fig. 2, according to the local configuration parameter values, the two parties are divided into three groups according to FlexE group numbers, PHY numbers and calendar configuration, and each group is mapped into BF fields according to specific three (also can be multiple, but not easy to be excessive, so that BF HASH conflicts are excessive and lose meaning); namely:
BF(H i (x))＝1(i＝1、2、3)
note that: the three hash functions are built in each hardware, so long as the consistency of a sender and a receiver is kept, and no special requirement exists. I.e. three sets of up to 9 1's are of suitable size relative to a 24 bit BF of 3 bytes, and hash collisions can be reduced as much as possible.
(13) Both sides thus get BF'; assuming now that A is the sender and B is the receiver, A will BF a ' added to the end of the management frame;
(14) Receiving party B receives BF a ' BF is calculated according to the step (2) ab In the process of (1), which fields are not matched can be found; taking FlexE group number as an example: assume that any 0, 1 and received BF are among the three values of the set of computation maps a ' mismatch, that is, mismatch of FlexE group numbers representing both parties;
the PHY number and calendar configuration verification method is the same as this.
(15) If no unmatched content appears in the step (4), the representative security verification passes; otherwise the receiver sends a non-matching report to the SDN controller/NMS.
In summary, the network devices typically reserve the same number of slots or bandwidths in both directions over the same FlexE link. The expected values for 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 hash mapping and confidentiality enhancing method. Both parties can secure the Flex group number, the group PHY number, and the group calendar configuration number by comparing the group bitstreams. 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 application has the following advantages:
first, device management of FlexE interfaces is optimized, some simple devices/devices that do not need to be configured can maintain a static interface through management frames, while interface parameters that need to be configured are configured by SDN controllers or network management systems. Therefore, traffic is isolated at a physical layer, and the service performs network slicing on the whole network, so that the traffic becomes one of the key requirements for 5G diversified scene bearing.
Second, the implementation scheme of the dynamic negotiation protocol is optimized, and the newly added dynamic negotiation protocol parameters are utilized to flexibly improve the bidirectional transmission configuration, and better and faster obtain the configuration parameters.
Third, flexE client management is optimized, and the number of operation fields is increased, so that when the negotiation protocol is not enabled, synchronous switching from active calendar configuration to backup calendar configuration is not required.
Fourth, the safety interaction flow 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.
While the applicant has described and illustrated the embodiments of the present application in detail with reference to the drawings, it should be understood by those skilled in the art that the above embodiments are only preferred embodiments of the present application, and the detailed description is only for the purpose of helping the reader to better understand the spirit of the present application, and not to limit the scope of the present application, but any improvements or modifications based on the spirit of the present application should fall within the scope of the present application.
Claims (8)
1. A FlexE interface management method of 5G smart grid slice is characterized in that SDN controller or network management system NMS is connected with management agent on each network device through network configuration protocol to configure FlexE interface parameters of the network device;
the control field of the FlexE management frame about static/configurable parameters is expanded, and the control field is used for acquiring the state of a FlexE interface, so that network equipment which does not need to be configured can keep the static interface, and the FlexE interface parameters of the network equipment which needs to be configured can be configured; control fields for static/configurable parameters, including a SoC state field, for indicating the current FlexE configuration state; a SoC_need_config field for indicating whether the current interface needs configuration; a parameter_control field for indicating a Parameter controller; a control_data field for indicating Control information of a controller;
the network equipment with the 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; extending a control field D_N_P in the FlexE management frame about the dynamic negotiation protocol parameters to indicate whether the dynamic negotiation protocol is enabled and the related function implementation; a D_N_P field including an Enable field indicating whether a dynamic negotiation protocol is enabled; a configuration_information field, which represents Configuration Information of the FlexE; the flexegroup bonding PHY field indicates the flexible client and its binding PHYs.
2. The FlexE interface management method for 5G smart grid slices of claim 1 wherein,
soc_state field with length of 2bit, 00-static, 01-configurable state; the SoC_need_config field is 1bit in length and is combined with the SoC_state field to dynamically manage the FlexE interface; a parameter_control field with a length of 1B, which is used to indicate that the Parameter controller is an SDN controller control or network management system NMS; the control_data field has a length of 2B, the first byte is used to indicate the information of the controller itself, and the second byte is used to select 8 different controls.
3. The FlexE interface management method for 5G smart grid slices of claim 1 wherein,
an Enable field, the length of which is 1bit,0 indicates that dynamic negotiation is not enabled, and 1 indicates that dynamic negotiation is enabled; a configuration_information field, with a length of 2B, indicating that the receiving peer extracts Configuration Information from the FlexE management frame sent by the sending peer after the dynamic negotiation protocol is enabled; the flexe_group_binding_phy field, length 4B, represents the configuration of the flexible client and its binding PHYs, establishing a flexible overhead channel for the signaling protocol to work properly.
4. The FlexE interface management method for 5G smart grid slices of claim 1 wherein,
for Flexible management of network devices, adding a field flexible_client_management related to Flexible client management parameters in a Flexible management frame; 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, a backup calendar sequence operation for each network device;
a flexible_client_management field, including an fcm_operator field, indicating a specific Operator; the fcm_parameter field indicates the number and number of objects operated on.
5. The method for FlexE interface management for 5G smart grid slices of claim 4 wherein,
fcm_operator field, length 1b,01—indicating the addition of one or more clients; 02-means deleting one or more clients; 03-means resizing one or more clients; 04-means adjusting one or more client slot positions; 05 to a subsequent operator temporary reservation for a subsequent expansion operation;
the fcm_parameter field has a length of 1b+nb+1b, the first byte indicates the number of operation objects, the second to fifth bytes indicate the IDs of the operated objects, and the sixth byte indicates the operation parameters, i.e., the adjusted size.
6. The FlexE interface management method for 5G smart grid slices of claim 1 wherein,
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 by 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.
7. The method for FlexE interface management for 5G smart grid slices of claim 6 wherein,
the specific steps of the secure communication flow during bidirectional transmission between network devices are as follows:
(1) The sending peer A and the 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, namely FlexE group numbers, PHY numbers and calendar configuration, and each group is mapped into BF fields according to specific three HASH functions; namely:
BF(H i (x))＝1(i＝1、2、3)
(3) The two parties thus obtain BF' and sending peer A handles BF a ' added to the end of the management frame;
(4) Receiving peer B receives BF a ' BF is calculated according to the step (2) ab In the process of (1), which fields are not matched can be found;
(5) If no unmatched content appears in the step (4), the representative security verification passes; otherwise the receiving peer sends a mismatch report to the SDN controller/NMS.
8. The method for FlexE interface management for 5G smart grid slices of claim 7 wherein,
taking the FlexE group number as an example, assume that there are any 0, 1 and received BF in the three values of the group calculation map a ' mismatch, that is, mismatch of FlexE group numbers representing both parties; the PHY number and calendar configuration verification method is the same as this.
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 CN114615136A (en) | 2022-06-10 |
| CN114615136B true 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 (17)
| 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 |
| 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 |
| 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 |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US11277217B2 (en) * | 2015-06-30 | 2022-03-15 | Ciena Corporation | Flexible Ethernet switching systems and methods |
| CN108243128B (en) * | 2016-12-27 | 2020-10-23 | 华为技术有限公司 | Method, network equipment and system for transmitting wireless interface forward signal |
| CN109586864B (en) * | 2017-09-28 | 2021-01-15 | 华为技术有限公司 | Data transmission method, device and system |
| WO2019206396A1 (en) * | 2018-04-23 | 2019-10-31 | Huawei Technologies Co., Ltd. | System, function and interface for interconnecting multi-domain network slice control and management |
-
2022
- 2022-03-04 CN CN202210209165.4A patent/CN114615136B/en active Active
Patent Citations (17)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| 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 |
| CN108631873A (en) * | 2017-03-21 | 2018-10-09 | 中兴通讯股份有限公司 | Receiving/transmission method, device, sending device and the receiving device of network management information |
| 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静态检查;姜文;刘立康;;计算机技术与发展;26(第11期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114615136A (en) | 2022-06-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110049512B (en) | Forward-transmission network data processing device and method | |
| WO2018030529A1 (en) | Wireless base station, wireless device, wireless control device, wireless communication system, communication method, and wireless terminal | |
| WO2018127144A1 (en) | Method, device and system for managing network slice instance | |
| CN107612825B (en) | Method and network device for establishing flexible Ethernet path | |
| EP3032871B1 (en) | Data transmission method, device and system | |
| US6956824B2 (en) | Extension of link aggregation protocols over the network | |
| CN107889169B (en) | Method and device for establishing network slice | |
| EP1971083A1 (en) | A method and a system for optimizing the radio network layer to implement the network interconnection, and a method for interconnection between the radio network and the wired network | |
| EP3829215A2 (en) | Apparatus and method for qos aware gtp-u transport in mobile networks | |
| WO2018219229A1 (en) | Communication method and network device | |
| US10992385B2 (en) | Apparatus and method for joint profile-based slicing of mobile access and optical backhaul | |
| US11729104B1 (en) | Apparatus and method for providing hybrid access coordination | |
| CN109429267B (en) | Data transmission method, related device and system | |
| JP2022531749A (en) | A method for forwarding Ethernet frames over a time-dependent networking Ethernet bridge provided by mobile radio communication systems and mobile radio communication system configurations. | |
| CN114128228A (en) | MTNC-ID transmission through SRv6 headers to realize 5G transmission | |
| CN113228592B (en) | Method and apparatus for providing transport context and on-path metadata to support 5G-enabled networks | |
| CN104685959B (en) | Passive radio link control entity with unified interface | |
| CN109246756A (en) | data distribution method and device | |
| 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 | |
| CN115914887A (en) | Service data transmission method and related equipment | |
| US11483733B2 (en) | Transporting a multi-transport network context-identifier (MTNC- ID) across multiple domains | |
| CN114615136B (en) | FlexE interface management method for 5G smart grid slice | |
| CN114128227A (en) | Transmitting MTNC-ID over SRv 6-supported data plane to enable 5G transmission | |
| CN101296143A (en) | Method for multiplying band width of wireless communication 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 |