WO2023138390A1 - 一种时隙分配的方法、网络设备和系统 - Google Patents

一种时隙分配的方法、网络设备和系统 Download PDF

Info

Publication number
WO2023138390A1
WO2023138390A1 PCT/CN2023/070705 CN2023070705W WO2023138390A1 WO 2023138390 A1 WO2023138390 A1 WO 2023138390A1 CN 2023070705 W CN2023070705 W CN 2023070705W WO 2023138390 A1 WO2023138390 A1 WO 2023138390A1
Authority
WO
WIPO (PCT)
Prior art keywords
flexe client
network device
priority
time slot
flexe
Prior art date
Application number
PCT/CN2023/070705
Other languages
English (en)
French (fr)
Inventor
郑娟
韩涛
董杰
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from CN202210285749.XA external-priority patent/CN116527193A/zh
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2023138390A1 publication Critical patent/WO2023138390A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J3/00—Time-division multiplex systems
    • H04J3/16—Time-division multiplex systems in which the time allocation to individual channels within a transmission cycle is variable, e.g. to accommodate varying complexity of signals, to vary number of channels transmitted

Definitions

  • the present application relates to the technical field of communications, and in particular to a time slot allocation method, network device and system.
  • Flexible Ethernet (FlexE) technology is an interface technology for bearer network to realize service isolation and network fragmentation.
  • F flexible Ethernet spacer
  • MAC media access control
  • PHY physical layer
  • lexE Shim lexE Shim
  • the FlexE standard defines the client/group architecture, which can support the mapping and transmission of any number of different FlexE Clients on any set of PHYs in the FlexE group, thereby realizing on-demand bandwidth allocation and hard pipe isolation solutions, which are used in scenarios such as ultra-large bandwidth interfaces, 5G network slicing, and optical transmission equipment interconnection.
  • the present application provides a time slot allocation method, network equipment and system, which are used to improve the SLA of high-priority services in a FlexE network.
  • a method for allocating time slots comprising: a first network device determines that a first available time slot among time slots allocated to a first Flexible Ethernet FlexE client does not meet a first required bandwidth of the first FlexE client; the first network device reallocates at least part of the time slots allocated to a second FlexE client to the first FlexE client, wherein the first priority of the first FlexE client is higher than the second priority of the second FlexE client.
  • the first network device determines that the first available time slot in the time slot allocated to the first FlexE client does not meet the required bandwidth of the first FlexE client, if the first FlexE client can only use the first available time slot to send the data of the first FlexE client, the SLA of the first FlexE client will be damaged, and the first network device will be allocated to at least part of the time slots allocated to the second FlexE client with a lower priority than the first FlexE client to the first FlexE client.
  • the first FlexE client can not only use the first available time slot to send data, but also use at least part of the time slots originally belonging to the second FlexE client to send data, which improves the SLA of the high-priority service of the first FlexE client.
  • the method when the first network device determines that the first available time slot among the time slots allocated to the first FlexE client does not meet the first required bandwidth of the first FlexE client, the method includes: the first network device determines that a first physical layer PHY fails, and the first PHY is associated with the first FlexE client.
  • the time slots associated with the first PHY are no longer available, and the remaining time slots are the first available time slots, which do not meet the bandwidth requirements of the first FlexE client.
  • To send data in time slots at least part of the time slots originally belonging to the second FlexE client can be used to send data.
  • the SLA of the high-priority service of the first FlexE client is improved.
  • the method when the first network device determines that the first available time slot in the time slots allocated to the first FlexE client does not meet the first required bandwidth of the first FlexE client, the method includes: the first network device determines that the bandwidth requirement of the first FlexE client is changed from the second required bandwidth to the first required bandwidth, and the second required bandwidth is smaller than the first required bandwidth.
  • the first network device allocates the first available time slot that meets the demand according to the demand bandwidth of the first FlexE client is the second demand bandwidth, and then, the demand bandwidth of the first FlexE client is changed from the second demand bandwidth to a larger first demand bandwidth. At least part of the time slots in the time slots of the lexE client are reassigned to the first FlexE client, so that the first FlexE client can not only use the first available time slot to send data, but also use at least part of the time slots originally belonging to the second FlexE client to send data. In the expansion phase, the SLA of the high-priority business of the first FlexE client is improved.
  • the method when the first network device reallocates at least part of the time slots allocated to the second FlexE client to the first FlexE client, the method includes: the first network device updating the second time slot entry to the first time slot entry, where the second time slot entry indicates at least part of the time slots of the second FlexE client.
  • the first network device updating the second time slot entry to the first time slot entry includes: the first network device updating the second identifier in the second time slot entry to the first identifier in the first time slot entry, where the second identifier indicates the second FlexE client, and the first identifier indicates the first FlexE client.
  • the method further includes: the first network device configures the first priority; the first network device receives a third priority sent by a second network device, the second network device and the first network device include the same FlexE group, and the third priority is the priority assigned by the second network device to the first FlexE client; The first priority is equal to the third priority.
  • the first network device configures priorities for the FlexE clients, so that when the available time slots allocated to the high-priority FlexE clients do not meet their bandwidth requirements, at least part of the time slots allocated to the low-priority FlexE clients are reassigned to the high-priority FlexE clients, thereby improving the SLA of the high-priority services of the high-priority FlexE clients.
  • the first priority and/or the third priority are carried in a FlexE overhead frame.
  • the method further includes: the first network device determines that the first priority is higher than the second priority according to the first identifier being smaller than the second identifier, where the first identifier indicates the first FlexE client, and the second identifier indicates the second FlexE client.
  • the first network device uses the client identification in the existing FlexE protocol to determine the priority of different clients, so that when the available time slots allocated to the high-priority FlexE clients do not meet their bandwidth requirements, at least some of the time slots allocated to the low-priority FlexE clients are reassigned to the high-priority FlexE clients, thereby improving the SLA of the high-priority services of the high-priority FlexE clients.
  • the method further includes: the first network device determines that a second available time slot among the time slots allocated to the first FlexE client does not meet the first required bandwidth of the first FlexE client, wherein the second available time slot includes at least part of the first available time slot and the time slot allocated to the second FlexE client; Reallocating at least some of the time slots allocated to the third FlexE client to the first FlexE client, wherein the first priority is higher than a third priority of the third FlexE client, and the third priority is higher than the second priority.
  • the first network device determines that the second available time slot among the time slots allocated to the first FlexE client still does not meet the requirements of the first FlexE client. Bandwidth is required. Then the first network device reallocates at least part of the time slots allocated to the third FlexE client to the first FlexE client. Therefore, the first FlexE client can not only use the second available time slot to send data, but also use at least part of the time slots originally belonging to the third FlexE client to send data, which improves the SLA of the high-priority service of the first FlexE client.
  • the first network device before the first network device reallocates at least part of the time slots allocated to the second FlexE client to the first FlexE client, the first network device starts the first FlexE client.
  • the first network device before the first network device reallocates at least part of the time slots allocated to the second FlexE client to the first FlexE client, the first network device turns on the first FlexE client, and then preempts the time slot of the second FlexE client, so that when the time slot allocated by the first network device to the first FlexE client does not meet the bandwidth of the first FlexE client, the first FlexE client can also be kept in the open state and continue to transmit high-priority data, thereby improving the efficiency of the first FlexE client. SLA of the high-priority service of the first FlexE client.
  • a first network device in a second aspect, has a function of implementing the behavior of the first network device in the above method.
  • the functions may be implemented based on hardware, or corresponding software may be implemented based on hardware.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • the structure of the first network device includes a processor and an interface, and the processor is configured to support the first network device to perform corresponding functions in the foregoing method.
  • the interface is used to support communication between the first network device and another network device, and receive information or instructions involved in the above method from the other network device.
  • the interface is also used to support communication between the first network device and the user equipment.
  • the first network device may further include a memory, which is used to be coupled with the processor, and stores necessary program instructions and data of the first network device.
  • the first network device includes: a processor, a transmitter, a receiver, a random access memory, a read only memory, and a bus.
  • the processor is respectively coupled to the transmitter, the receiver, the random access memory and the read-only memory through the bus.
  • the basic input/output system solidified in the read-only memory or the bootloader boot system in the embedded system is started to guide the first network device into a normal operation state. After the first network device enters the normal running state, run the application program and the action system in the random access memory, so that the processor executes the method in the first aspect or any possible implementation manner of the first aspect.
  • a first network device in a third aspect, includes: a main control board and an interface board, and may further include a switching fabric board.
  • the first network device is configured to execute the method in the first aspect or any possible implementation manner of the first aspect.
  • the first network device includes a module for executing the method in the first aspect or any possible implementation manner of the first aspect.
  • a first network device in a fourth aspect, includes a controller and a forwarding sub-device.
  • the forwarding sub-device includes: an interface board, and may further include a switching fabric board.
  • the forwarding sub-device is used to perform the function of the interface board in the third aspect, and further, may also perform the function of the switching fabric board in the third aspect.
  • the controller includes a receiver, a processor, a transmitter, a random access memory, a read only memory and a bus. Wherein, the processor is respectively coupled to the receiver, the transmitter, the random access memory and the read-only memory through the bus.
  • the basic input/output system solidified in the read-only memory or the bootloader boot system in the embedded system is started to guide the controller into a normal operation state.
  • the application program and the action system are run in the random access memory, so that the processor executes the functions of the main control board in the third aspect.
  • a computer storage medium for storing programs, codes, or instructions used by the above-mentioned first network device.
  • a processor or hardware device executes these programs, codes, or instructions, the functions or steps of the first network device in the above-mentioned first aspect can be completed.
  • a communication system in a sixth aspect, includes a first network device, where the first network device is the first network device in the foregoing first aspect.
  • a chip including: an interface circuit and a processor.
  • the interface circuit is connected to the processor, and the processor is configured to make the chip perform the method described in any of the foregoing aspects and part or all of the operations included in any possible implementation of any of the foregoing aspects.
  • the first network device determines that the first available time slot among the time slots allocated to the first FlexE client does not meet the required bandwidth of the first FlexE client. If the first FlexE client can only use the first available time slot to send the data of the first FlexE client, the SLA of the first FlexE client will be damaged, and the first network device re-allocates at least part of the time slots allocated to the second FlexE client with a lower priority than the first FlexE client to the first FlexE client. The FlexE client can not only use the first available time slot to send data, but also use at least part of the time slots originally belonging to the second FlexE client to send data, which improves the SLA of the high-priority service of the first FlexE client.
  • FIG. 1 is a schematic diagram of an application scenario of an embodiment of the present application
  • FIG. 2 is a schematic diagram of using FlexE technology to transmit data in the embodiment of the present application
  • FIG. 3 is a flowchart of a method for allocating time slots according to an embodiment of the present application
  • FIG. 4 is a flow chart of another method for allocating time slots according to an embodiment of the present application.
  • FIG. 5 is a schematic structural diagram of a first network device according to an embodiment of the present application.
  • FIG. 6 is a schematic diagram of a hardware structure of a first network device according to an embodiment of the present application.
  • FIG. 7 is a schematic diagram of a hardware structure of another first network device according to an embodiment of the present application.
  • FIG. 1 shows an application scenario of the embodiment of the present application.
  • the scenario shown in FIG. 1 will be described in detail below.
  • FIG. 1 includes two network devices, namely network device 1 and network device 2, and two user devices, respectively user device 1 and user device 2.
  • Network device 1 can be an edge node in the bearer network, such as a provider edge (provider edge, PE) node. At this time, network device 1 is directly connected to user equipment 1.
  • Network device 1 can also be an intermediate node in the bearer network, such as a provider (provider, P) node. At this time, network device is connected to user equipment 1 through other network devices.
  • the network device 2 may also be an edge node or an intermediate node, and reference may be made to the relevant description of the network device 1 , which will not be repeated here.
  • the connection between network device 1 and network device 2 is a FlexE group, a FlexE is composed of multiple physical structures, and can carry data of multiple FlexE clients.
  • FIG. 1 it should be understood that only 2 network devices and 2 user equipments are shown in FIG. 1 exemplarily, and the network may include any other number of network devices and user equipments, which is not limited in this embodiment of the present application.
  • the FlexE communication system shown in FIG. 1 is only for illustration, and the application scenarios of the FlexE communication system provided in the present application are not limited to the scenarios shown in FIG. 1 .
  • the technical solutions provided in this application are applicable to all network scenarios where FlexE technology is used for data transmission.
  • FlexE client It supports Ethernet data streams at various rates, such as 10 gigabits per second (Gbps), 40Gbps, n*25Gbps data streams, and even non-standard rate data streams.
  • FlexE client is a container for data streams, which can also be regarded as a logical interface. This logical interface is the transmission interface of data streams, and the data streams are transmitted to FlexE through 64B/66B encoding shim layer.
  • FlexE group Essentially, it is the various Ethernet PHY layers defined by the IEEE 802.3 standard. By default, the bandwidth of the PHY is pooled into 5GE granular resources.
  • FlexE shim As an additional logical layer inserted between the MAC and PHY (PCS sublayer) of the traditional Ethernet architecture, FlexE shim divides each PHY in the FlexE group into multiple time slots. Generally speaking, it supports a data bearing channel divided into 20 time slots by default, and the bandwidth corresponding to each time slot is 5Gbps. FlexE shim encodes the Ethernet frames in the original data stream of the FlexE client in Block atomic data blocks (64/66B The data block) is divided into units, and these atomic data blocks are mapped and transmitted in the FlexE group through the Calendar mechanism of the FlexE Shim to achieve strict isolation.
  • Block atomic data blocks 64/66B The data block
  • the present application does not limit that there is only one FlexE group between two network devices, that is, there may be multiple FlexE groups between two network devices.
  • One PHY can be used to carry at least one client, and one client can be transmitted on at least one PHY.
  • the bandwidth of each PHY is 10 Gbps
  • PHY1, PHY2, PHY3, and PHY4 are bound into a FlexE group, and data is transmitted between network device 1 and network device 2 through the FlexE group.
  • the FlexE group corresponds to 3 clients, namely client1, client2 and client3, wherein the business data in client1 is the most important data, and the required bandwidth is 20Gbps; the business data in client2 is the least important data, and the required bandwidth is 10Gbps; Y1 and PHY2, network device 1 allocates 2 time slots for client2, corresponding to PHY3, network device 1 allocates 1 time slot for client3, corresponding to PHY4, network device 1 establishes a time slot table, and instructs network device 1 to send data corresponding to the client according to the time slot indication of the time slot table, as shown in Table 1.
  • network device 1 can create a time slot table for a FlexE group, such as Table 1, and can also create a table for a PHY, then Table 1 will be split into 4 tables, and the embodiment of the present application does not limit the form of the time slot table.
  • the network device 2 will establish the same time slot table as Table 1 according to the shim layer control protocol, which is used to instruct the network device 2 to receive the data of the corresponding client in the corresponding time slot.
  • FlexE shim slices the data according to the same clock, and encapsulates the sliced data into pre-divided time slots, and then, according to the time slot table 1, maps each divided time slot to the PHY in the FlexE group for transmission.
  • the present application proposes a time slot allocation method 100 for improving the SLA of priority services.
  • the method 100 can be used in the scenario shown in FIG. 1 or FIG. 2.
  • the method 100 will be described below in conjunction with the scenario shown in FIG. 1 or FIG. 2, wherein the first network device is equivalent to the network device in FIG. 1 or FIG. 2, such as network device 1, and the second network device is equivalent to the network device in FIG. 1 or FIG.
  • the first network device determines that the first available time slot in the time slots allocated to the first Flexible Ethernet FlexE client does not meet the first required bandwidth of the first FlexE client.
  • the first network device determines that the first available time slot in the time slot allocated to the first flexible Ethernet FlexE client does not meet the first required bandwidth of the first FlexE client:
  • Scenario 1 Fault scenario: the first network device determines that a fault occurs in a first physical layer PHY, and the first PHY is associated with the first FlexE client.
  • the first network device allocates time slots for the first FlexE client according to the first bandwidth requirement of the first FlexE client, so that the first network device determines that the time slots allocated for the first FlexE client are all available time slots, satisfying the first required bandwidth of the first FlexE client.
  • the first required bandwidth of client1 is the bandwidth that satisfies the data stream transmission requirement of the client.
  • the specific implementation method is that on network device 1, a virtual interface will be created for each client, and the configuration corresponding to the client will be configured under the virtual interface. Under virtual interface 1, the required bandwidth of client1 will be configured, such as 20Gbps, and then the first network device will allocate time slots for client1 according to 20Gbps to meet the transmission requirements of client1's data stream. PHY2.
  • the first PHY breaks down. At this time, among the time slots allocated by the first network device for the first FlexE client, some time slots not corresponding to the first PHY are still available, which are the first available time slots, and some time slots corresponding to the first PHY are unavailable. Obviously, the first available time slots are part of the time slots allocated by the first network device for the first FlexE client, thereby not satisfying the first required bandwidth of the first FlexE client.
  • the faults in the embodiments of the present application include physical link faults, faults of devices connected to the PHY on the sending side, faults of devices connected to the PHY on the receiving side, etc.
  • the present application does not limit the types of PHY faults. Take the first PHY corresponding to PHY1 in FIG. 2 as an example. At this time, the two time slots corresponding to PHY1 cannot transmit the data of client1, and the remaining two time slots corresponding to PHY2 do not meet the required bandwidth of client1 of 20 Gbps.
  • Scenario 2 Capacity expansion scenario: the first network device determines that the bandwidth requirement of the first FlexE client is changed from the second required bandwidth to the first required bandwidth, and the second required bandwidth is smaller than the first required bandwidth.
  • the bandwidth requirement of the first FlexE client is the second bandwidth requirement
  • the first network device allocates time slots for the first FlexE client according to the second required bandwidth, and the time slots allocated at this time meet the second required bandwidth of the first FlexE client.
  • the second required bandwidth is 20Gbps
  • the first network device will allocate time slots for client1 according to 20Gbps to meet the transmission requirements of client1's data stream, as shown in Table 1.
  • the first network device allocates 4 time slots for client1, of which 2 time slots correspond to PHY1 and 2 time slots correspond to PHY2.
  • the bandwidth demand of the first FlexE client is changed from the second demand bandwidth to the first demand bandwidth, and the first demand bandwidth is greater than the second demand bandwidth.
  • all the time slots in the time slots allocated by the first network device for the first FlexE client are still available, which is the first available time slot, but due to the increase in bandwidth demand, the first demand bandwidth of the first FlexE client is not satisfied.
  • the required bandwidth of client1 is changed from 20Gbps to 40Gbps.
  • the original 4 time slots are not enough to transmit 40Gbps data.
  • Scenario 3 A new client scenario: the first network device adds a new client, and determines that the time slot allocated for the new client cannot meet the bandwidth requirement of the new client.
  • Network device 1 allocates one time slot for client4, corresponding to PHY4, which does not meet the bandwidth requirements of client4.
  • the first network device starts the first FlexE client, that is, performs shrink processing on the FlexE client, instead of directly shutting down the FlexE client, and provides services for the FlexE client in a shrinking manner.
  • the first network device reallocates at least part of the time slots allocated to the second FlexE client to the first FlexE client, where the first priority of the first FlexE client is higher than the second priority of the second FlexE client.
  • each FlexE client is associated with a priority, which represents the priority of the traffic of the FlexE client.
  • the priorities of different FlexE clients can be the same or different.
  • the first network device will create a virtual interface for each client, configure the configuration related to the client under the virtual interface, and increase the configuration of the priority at this time.
  • 1 represents the highest priority
  • 2 represents the middle priority
  • 3 represents the lowest priority. It should be understood that only three priority levels are listed in the embodiment of the present application. Of course, more priority levels can also be included, which are also within the protection scope of the present application.
  • the priority of clien1 is 1
  • the priority of clien2 is 3
  • the priority of client3 is 2.
  • the first network device and the second network device need to perform client priority negotiation to ensure that the same client priority configurations are the same.
  • the priority negotiation process is: the first network device receives the third priority sent by the second network device, the second network device and the first network device include the same FlexE group, the third priority is the priority assigned by the second network device to the first FlexE client; the first network device determines that the first priority is equal to the third priority.
  • the first priority and/or the third priority are carried in a FlexE overhead frame.
  • the embodiment of this application provides the following two client priority negotiation methods.
  • the priority negotiation process between network device 1 and client1 on network device 2 is as follows: network device 1 and network device 2 allocate and configure the priority of client1 to be 1, then network device 1 sends priority 1 to network device 2, network device 2 determines that it is the same as the priority 1 of client1 configured locally, and network device 2 sends a confirmation message 1 to network device 1, indicating that network device 2 and network device 1 have the same priority. Network device 2 sends priority 1 to network device 1, network device 1 determines that it is the same as the priority 1 of client1 configured locally, and network device 1 sends a confirmation message 2 to network device 2, indicating that network device 1 and network device 2 have the same priority.
  • the priority negotiation between network device 1 and network device 2 succeeds.
  • Network device 1 sends priority 1 to network device 2, and network device 2 determines that it is the same as priority 1 of client1 configured locally.
  • Network device 2 sends priority 1 to network device 1, and network device 1 determines that it is the same as priority 1 of client1 configured locally.
  • the priority negotiation between network device 1 and network device 2 succeeds.
  • the priority negotiation fails.
  • the network management needs to check and correct the priority configuration of the network device to ensure that the priorities configured by the network devices at both ends are the same.
  • a rule can also be set in the FlexE communication system.
  • the priority of the client is positively or negatively correlated with the client ID. Then, on the device that supports FlexE, the relationship between the priorities of different FlexE clients can be determined without performing the above-mentioned priority configuration and negotiation process.
  • the above describes how the first network device determines the priority levels of different FlexE clients.
  • the following specifically introduces the processing after the first network device determines that the first available time slot in the time slots allocated for the first FlexE client does not meet the first required bandwidth of the first FlexE client.
  • the first network device determines that the first available time slot among the time slots allocated to the first flexible Ethernet FlexE client does not meet the first required bandwidth of the first FlexE client, at least part of the time slots allocated to the second FlexE client with a priority lower than that of the first FlexE client will be reallocated to the first FlexE client. All time slots in .
  • the first network device selects a client with a lower priority than the first FlexE client as the second FlexE client, or the first network device selects a client with the lowest priority among the clients with a lower priority than the first FlexE client as the second FlexE client.
  • PHY1 in Figure 2 fails. At this time, the two time slots corresponding to PHY1 cannot transmit the data of client1, and the remaining two time slots corresponding to PHY2 do not meet the bandwidth requirement of client1 of 20Gbps. Network device 1 will re-allocate the 2 time slots allocated by client2 to client1. At this time, client1 has 4 time slots to transmit data, which meets the bandwidth requirement of client1 of 20Gbps. Alternatively, network device 1 will reallocate one of the two time slots allocated by client2 to client1. At this time, client1 has three time slots for data transmission, and the transmission bandwidth obtained by client1 increases. The remaining bandwidth of client2 does not meet the bandwidth requirement, and client2 remains open.
  • Scenario 3 New client scenario: Add a new client client4 in the scenario shown in Figure 2.
  • the priority of client4 is 1, and the required bandwidth of client4 is 10Gbps.
  • the remaining PHY bandwidth is 0Gbps.
  • the network device will re-allocate one of the two time slots allocated by client2 to client4.
  • client4 has one time slot to transmit data, c
  • the bandwidth obtained by client4 increases, and client4 remains on, or the network device will re-allocate the 2 time slots allocated by client2 to client4.
  • client4 has 2 time slots to transmit data to meet the bandwidth requirements of client4.
  • the remaining bandwidth of client2 does not meet the bandwidth requirement, and client2 remains open.
  • the meaning of enabling the client is the same as that of keeping the client in the enabled state, both of which are to configure the client in the enabled state.
  • the first network device When the first network device reallocates at least part of the time slots allocated to the second FlexE client to the first FlexE client, the first network device updates the second time slot entry to the first time slot entry, where the second time slot entry indicates at least part of the time slots of the second FlexE client.
  • the first network device updating the second time slot entry to the first time slot entry includes: the first network device updating the second identifier in the second time slot entry to the first identifier in the first time slot entry, where the second identifier indicates the second FlexE client, and the first identifier indicates the first FlexE client.
  • network device 1 will re-allocate the 2 time slots allocated to client2 to client1.
  • the second time slot entry is Table 1, and the network device 1 updates Table 1 to Table 2, specifically, client2 in the FlexE client identifier in Table 1 is updated to client1.
  • the first network device determines that the first available time slot in the time slot allocated to the first FlexE client does not meet the required bandwidth of the first FlexE client. If the first FlexE client can only use the first available time slot to send the data of the first FlexE client, the SLA of the first FlexE client will be damaged, and the first network device will re-allocate at least part of the time slots allocated to the second FlexE client with a lower priority than the first FlexE client to the first FlexE client. Therefore, the first FlexE client can not only use the first available time slot to send data, but also use at least part of the time slots originally belonging to the second FlexE client to send data, which improves the SLA of the high priority service of the first FlexE client.
  • the first network device after the first network device reallocates at least part of the time slots allocated to the second FlexE client to the first FlexE client, the first network device further needs to perform S103-S104.
  • the first network device determines that a second available time slot in the time slots allocated to the first FlexE client does not meet the first required bandwidth of the first FlexE client.
  • the second available time slot includes at least part of the first available time slot in the method 100 and the time slot allocated to the second FlexE client, for example, corresponding to the failure scenario in S101, after PHY1 fails, the first available time slot in the time slot allocated by network device 1 to client1 is 2 time slots, network device 1 will allocate one of the time slots allocated to client2 to client1, and the second time slot in the time slot allocated to client1 by network device 1 Available slots are 3 slots.
  • the first network device reallocates at least part of the time slots allocated to the third FlexE client to the first FlexE client, where the first priority is higher than a third priority of the third FlexE client, and the third priority is higher than the second priority.
  • the first network device determines that the first available time slot among the time slots allocated to the first FlexE client does not meet the first required bandwidth of the first FlexE client, and then reallocates at least part of the time slots of the second client with the lowest priority to the first FlexE client, and if after the redistribution, the time slots of the first FlexE client are still not enough, redistributes at least part of the time slots allocated to the third FlexE client to the first FlexE client, wherein the first priority is higher than the third priority of the third FlexE client level, the third priority is higher than the second priority.
  • the first available time slot allocated by network device 1 to client1 is 2 time slots
  • network device 1 allocates 1 time slot to client1 in the time slot allocated to client2
  • the second available time slot in the time slot allocated by network device 1 to client1 is 3 time slots, which still does not meet the bandwidth requirements of client1
  • network device 1 allocates 1 time slot to client3. Allocated to client1, at this time client1 obtains 4 time slots for transmitting client1's data to meet its bandwidth requirements.
  • the first network device determines that the second available time slot among the time slots allocated to the first FlexE client still does not meet the requirements of the first FlexE client. The first demand bandwidth. Then the first network device reallocates at least part of the time slots allocated to the third FlexE client to the first FlexE client. Therefore, the first FlexE client can not only use the second available time slot to send data, but also use at least part of the time slots originally belonging to the third FlexE client to send data, which improves the SLA of the high-priority service of the first FlexE client.
  • FIG. 5 is a schematic structural diagram of a first network device 1000 according to an embodiment of the present application.
  • the first network device 1000 shown in FIG. 5 may execute corresponding steps performed by the first network device in the method of the foregoing embodiments.
  • the first network device 1000 is deployed in a communication network, and the communication network further includes a second network device.
  • the first network device 1000 includes a processing unit 1001 and a transceiver unit 1002 .
  • the processing unit 1001 is configured to determine that the first available time slot among the time slots allocated to the first flexible Ethernet FlexE client does not meet the first required bandwidth of the first FlexE client;
  • the processing unit 1001 is further configured to reallocate at least part of the time slots allocated to the second FlexE client to the first FlexE client, where the first priority of the first FlexE client is higher than the second priority of the second FlexE client.
  • the processing unit 1001 is configured to determine that the first available time slot among the time slots allocated to the first FlexE client does not meet the first required bandwidth of the first FlexE client, the processing unit 1001 is specifically configured to: determine that a failure occurs in a first physical layer PHY, and the first PHY is associated with the first FlexE client.
  • the processing unit 1001 is configured to determine that the first available time slot among the time slots allocated to the first FlexE client does not meet the first required bandwidth of the first FlexE client, the processing unit 1001 is specifically configured to: determine that the bandwidth requirement of the first FlexE client is changed from the second required bandwidth to the first required bandwidth, and the second required bandwidth is smaller than the first required bandwidth.
  • the processing unit 1001 is configured to reallocate at least part of the time slots allocated to the second FlexE client to the first FlexE client, and the processing unit 1001 is specifically configured to:
  • the processing unit 1001 is specifically configured to: update the second identifier in the second slot entry to the first identifier in the first slot entry, where the second identifier indicates the second FlexE client, and the first identifier indicates the first FlexE client.
  • the processing unit 1001 is configured to determine that the first available time slot among the time slots allocated to the first FlexE client does not meet the first required bandwidth of the first FlexE client, the processing unit 1001 is further configured to configure the first priority;
  • the transceiver unit 1002 is configured to receive a third priority sent by a second network device, the second network device and the first network device include the same FlexE group, and the third priority is the priority assigned by the second network device to the first FlexE client;
  • the processing unit 1001 is further configured to determine that the first priority is equal to the third priority.
  • the first priority and/or the third priority are carried in a FlexE overhead frame.
  • the processing unit 1001 before the processing unit 1001 is configured to determine that the first available time slot among the time slots allocated to the first FlexE client does not meet the first required bandwidth of the first FlexE client, the processing unit 1001 is further configured to: determine that the first priority is higher than the second priority according to the first identifier being smaller than the second identifier, where the first identifier indicates the first FlexE client, and the second identifier indicates the second FlexE client.
  • the processing unit 1001 is used to reintermine at least part of the time slot in the time slot assigned to the second Flexe client to the first Flexe client.
  • the second availability time slot includes at least part of the time clearance in the time clearance of the first availability of the first availability and the time clearance assigned to the second Flexe client;
  • the processing unit 1001 is configured to, before reallocating at least part of the time slots allocated to the second FlexE client to the first FlexE client, the processing unit 1001 is further configured to start the first FlexE client.
  • FIG. 6 is a schematic diagram of a hardware structure of a first network device 1100 according to an embodiment of the present application.
  • the first network device 1100 shown in FIG. 6 may execute corresponding steps performed by the first network device in the method of the foregoing embodiments.
  • the first network device 1100 includes a processor 1101 , a memory 1102 , an interface 1103 and a bus 1104 .
  • the interface 1103 can be implemented in a wireless or wired manner.
  • the aforementioned processor 1101 , memory 1102 and interface 1103 are connected through a bus 1104 .
  • the interface 1103 may specifically include a transmitter and a receiver for sending and receiving information between the first network device and the second network device in the above embodiment.
  • the interface 1103 is configured to support sending a control message to the second network device.
  • the interface 1103 is used to support the priority negotiation process in the process S102 in FIG. 3 .
  • the processor 1101 is configured to execute the processing performed by the first network device in the foregoing embodiments.
  • the processor 1101 is configured to execute an action of generating the control message; and/or other processes for the technology described herein.
  • the processor 1101 is used to support the process S101 in FIG. 3 .
  • the memory 1102 is used for storing programs, codes or instructions, for example, storing the action system 11021 and the application program 11022. When the processor or hardware device executes these programs, codes or instructions, the processing process involving the first network device in the method embodiment can be completed.
  • the memory 1102 may include a read-only memory (Read-only Memory, ROM) and a random access memory (Random Access Memory, RAM).
  • the ROM includes a basic input/output system (Basic Input/Output System, BIOS) or an embedded system
  • the RAM includes an application program and an action system.
  • the first network device 1100 When it is necessary to run the first network device 1100, boot the system through the BIOS solidified in the ROM or the bootloader in the embedded system, and guide the first network device 1100 into a normal operation state. After the first network device 1100 enters the normal running state, the application program and the action system in the RAM are run, thereby completing the processing procedures related to the first network device in the method embodiment.
  • FIG. 6 only shows a simplified design of the first network device 1100 .
  • the first network device may include any number of interfaces, processors or memories.
  • FIG. 7 is a schematic diagram of a hardware structure of another first network device 1200 according to an embodiment of the present application.
  • the first network device 1200 shown in FIG. 7 may execute corresponding steps performed by the first network device in the method of the foregoing embodiments.
  • the first network device 1200 includes: a main control board 1210 , an interface board 1230 , a switching fabric board 1220 and an interface board 1240 .
  • the main control board 1210, the interface boards 1230 and 1240, and the switching fabric board 1220 are connected to the system backplane through the system bus to realize intercommunication.
  • the main control board 1210 is used to complete functions such as system management, equipment maintenance, and protocol processing.
  • the SFU 1220 is used to implement data exchange between interface boards (interface boards are also called line cards or service boards).
  • the interface boards 1230 and 1240 are used to provide various service interfaces (for example, POS interface, GE interface, ATM interface, etc.), and realize data packet forwarding.
  • the interface board 1230 may include a central processing unit 1231 , a forwarding entry storage 1234 , a physical interface card 1233 and a network processor 1232 .
  • the central processing unit 1231 is used for controlling and managing the interface board and communicating with the central processing unit on the main control board.
  • the forwarding entry storage 1234 is used for storing forwarding entries.
  • the physical interface card 1233 is used to receive and send traffic.
  • the network storage 1232 is configured to control the physical interface card 1233 to send and receive traffic according to the forwarding entry.
  • the physical interface card 1233 is configured to send the first priority to the second network device.
  • the central processing unit 1231 is configured to control the network processor 1232 to send the first priority to the second network device via the physical interface card 1233 .
  • the actions on the interface board 1240 in the embodiment of the present invention are consistent with the actions of the interface board 1230 , and for the sake of brevity, details are not repeated here.
  • the first network device 1200 in this embodiment may correspond to the functions and/or various steps implemented in the foregoing method embodiments, and details are not repeated here.
  • main control boards there may be one or more main control boards, and when there are multiple main control boards, the main main control board and the standby main control board may be included.
  • the first network device may have at least one SFU, through which data exchange between multiple interface boards is realized, and large-capacity data exchange and processing capabilities are provided. Therefore, the data access and processing capabilities of the first network device in the distributed architecture are greater than those in the centralized architecture. Which architecture to use depends on the specific networking deployment scenario, and there is no limitation here.
  • An embodiment of the present application provides a computer storage medium for storing computer software instructions used by the above-mentioned first network device, which includes a program designed to execute the above-mentioned method embodiment.
  • the embodiment of the present application also provides a chip, including: an interface circuit and a processor.
  • the interface circuit is connected to the processor, and the processor is configured to make the chip execute part or all of the operations in the method (for example, method 100 ) described in any one of the foregoing embodiments.
  • An embodiment of the present application further provides a chip system, including: a processor, the processor is coupled to a memory, and the memory is used to store a program or an instruction, and when the program or instruction is executed by the processor, the chip system implements part or all of the operations in the method (for example, method 100) described in any one of the above embodiments.
  • processors in the chip system there may be one or more processors in the chip system.
  • the processor can be realized by hardware or by software.
  • the processor may be a logic circuit, an integrated circuit, or the like.
  • the processor may be a general-purpose processor implemented by reading software codes stored in a memory.
  • the memory may be integrated with the processor, or may be configured separately from the processor, which is not limited in this embodiment of the present application.
  • the memory can be a non-transitory processor, such as a read-only memory ROM, which can be integrated with the processor on the same chip, or can be respectively arranged on different chips.
  • the embodiment of the present application does not specifically limit the type of the memory and the arrangement of the memory and the processor.
  • the chip system may be FPGA, ASIC, system on chip (system on chip, SoC), CPU, NP, digital signal processing circuit (digital signal processor, DSP), microcontroller (micro controller unit, MCU), programmable controller (programmable logic device, PLD) or other integrated chips.
  • SoC system on chip
  • DSP digital signal processor
  • MCU microcontroller
  • PLD programmable logic device
  • the embodiment of the present application also includes a network system, where the network system includes a first network device and a second network device, the first network device is the first network device in FIG. 5 or FIG. 6 or FIG. 7 , and the second network device is the second network device in FIG. 5 or FIG. 6 or FIG. 7 .
  • the steps of the methods or algorithms described in connection with the disclosure of this application can be implemented in the form of hardware, or can be implemented in the form of a processor executing software instructions.
  • the software instructions can be composed of corresponding software modules, and the software modules can be stored in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, mobile hard disk, CD-ROM or any other form of storage medium known in the art.
  • An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium.
  • the storage medium may also be a component of the processor.
  • the processor and storage medium can be located in the ASIC. Additionally, the ASIC may be located in the user equipment.
  • the processor and the storage medium may also exist in the user equipment as discrete components.
  • Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • a storage media may be any available media that can be accessed by a general purpose or special purpose computer.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Small-Scale Networks (AREA)

Abstract

本申请提供了一种时隙分配的方法、网络设备和系统，第一网络设备确定为第一FlexE客户端分配的时隙中的第一可用时隙不满足第一FlexE客户端的需求带宽，如果第一FlexE客户端只能使用所述第一可用时隙发送第一FlexE客户端的数据，第一FlexE客户端的SLA会受损，第一网络设备将分配给比第一FlexE客户端优先级低的第二FlexE客户端的时隙中的至少部分时隙重新分配给所述第一FlexE客户端，从而，第一FlexE客户端不仅可以使用所述第一可用时隙发送数据，还可以使用原来属于第二FlexE客户端的时隙中的至少部分时隙发送数据，提高了第一FlexE客户端的高优先级业务的SLA。

Description

一种时隙分配的方法、网络设备和系统
本申请要求申请日为2022年01月24日，申请号为202210098892.8，名称为“一种分配发送资源的方法、设备及系统”的中国专利申请的优先权，以及要求申请日为2022年03年22日，申请号为202210285749.X，名称为“一种时隙分配的方法、网络设备和系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种时隙分配的方法、网络设备和系统。
背景技术
灵活以太(flexible ethernet，FlexE)技术是承载网实现业务隔离和网络分片的一种接口技术，在电气电子工程师学会(institute of electrical and electronics engineers，IEEE)802.3定义的标准以太网技术基础上，通过在媒体接入控制(media access control，MAC)与物理层(physical layer，PHY)之间增加一个灵活以太网垫片(FlexE Shim)层，实现了MAC与PHY层解耦，从而使FlexE客户端(client)可以向上层应用提供各种灵活的带宽。
FlexE标准定义了客户端/组(client/group)架构，可以支持任意多个不同FlexE Client在FlexE组(group)的任意一组PHY上的映射和传输，从而实现带宽按需分配和硬管道隔离等方案，用于超大带宽接口、5G网络分片和光传输设备对接等场景。
按照当前FlexE标准，当FlexE组中的PHY处于故障状态时，则使用这一PHY传输数据的所有FlexE客户端均会受损，其中，某些FlexE客户端承载高优先级的业务数据，这些数据也无法通过故障的PHY发送，导致高优先级业务的服务水平协议(service level agreement，SLA)受损。
发明内容
有鉴于此，本申请提供了一种时隙分配的方法、网络设备和系统，用于提高FlexE网络中高优先级业务的SLA。
第一方面，提供了一种时隙分配的方法，所述方法包括：第一网络设备确定为第一灵活以太FlexE客户端分配的时隙中的第一可用时隙不满足所述第一FlexE客户端的第一需求带宽；所述第一网络设备将分配给第二FlexE客户端的时隙中的至少部分时隙重新分配给所述第一FlexE客户端，其中，所述第一FlexE客户端的第一优先级高于所述第二FlexE客户端的第二优先级。
基于本申请提供的方案，第一网络设备确定为第一FlexE客户端分配的时隙中的第一可用时隙不满足第一FlexE客户端的需求带宽，如果第一FlexE客户端只能使用所述第一可用时隙发送第一FlexE客户端的数据，第一FlexE客户端的SLA会受损，第一网络设备将分配给比第一FlexE客户端优先级低的第二FlexE客户端的时隙中的 至少部分时隙重新分配给所述第一FlexE客户端，从而，第一FlexE客户端不仅可以使用所述第一可用时隙发送数据，还可以使用原来属于第二FlexE客户端的时隙中的至少部分时隙发送数据，提高了第一FlexE客户端的高优先级业务的SLA。
在一种可能的实现方式中，在所述第一网络设备确定为第一FlexE客户端分配的时隙中的第一可用时隙不满足所述第一FlexE客户端的第一需求带宽中，包括：所述第一网络设备确定第一物理层PHY发生故障，所述第一PHY与所述第一FlexE客户端关联。
基于本申请提供的方案，当第一PHY发生故障时，所以第一网络设备为第一FlexE客户端分配的时隙中，与第一PHY关联的时隙不再可用，剩余的时隙为第一可用时隙，不满足第一FlexE客户端的带宽需求，第一网络设备将分配给比第一FlexE客户端优先级低的第二FlexE客户端的时隙中的至少部分时隙重新分配给所述第一FlexE客户端，从而，第一FlexE客户端不仅可以使用所述第一可用时隙发送数据，还可以使用原来属于第二FlexE客户端的时隙中的至少部分时隙发送数据，在PHY发生故障后，提高了第一FlexE客户端的高优先级业务的SLA。
在一种可能的实现方式中，在所述第一网络设备确定为第一FlexE客户端分配的时隙中的第一可用时隙不满足所述第一FlexE客户端的第一需求带宽中，包括：所述第一网络设备确定所述第一FlexE客户端的带宽需求由第二需求带宽变更为所述第一需求带宽，所述第二需求带宽小于所述第一需求带宽。
基于本申请提供的方案，第一网络设备根据第一FlexE客户端的需求带宽是第二需求带宽，为第一FlexE客户端分配了满足需求的第一可用时隙，然后，第一FlexE客户端的需求带宽由第二需求带宽变更为更大的第一需求带宽，此时，所述第一网络设备确定为第一FlexE客户端分配的时隙中的第一可用时隙不再满足所述第一FlexE客户端的第一需求带宽，第一网络设备将分配给比第一FlexE客户端优先级低的第二FlexE客户端的时隙中的至少部分时隙重新分配给所述第一FlexE客户端，从而，第一FlexE客户端不仅可以使用所述第一可用时隙发送数据，还可以使用原来属于第二FlexE客户端的时隙中的至少部分时隙发送数据，在扩容阶段，提高了第一FlexE客户端的高优先级业务的SLA。
在一种可能的实现方式中，在所述第一网络设备将分配给第二FlexE客户端的时隙中的至少部分时隙重新分配给所述第一FlexE客户端中，包括：所述第一网络设备将第二时隙表项更新为第一时隙表项，其中，所述第二时隙表项指示所述第二FlexE客户端的时隙中的至少部分时隙。
在一种可能的实现方式中，所述第一网络设备将第二时隙表项更新为第一时隙表项，包括：所述第一网络设备将所述第二时隙表项中的第二标识更新为所述第一时隙表项中的第一标识，其中，所述第二标识指示所述第二FlexE客户端，所述第一标识指示所述第一FlexE客户端。
在一种可能的实现方式中，在所述第一网络设备确定为第一FlexE客户端分配的时隙中的第一可用时隙不满足所述第一FlexE客户端的第一需求带宽之前，所述方法还包括：所述第一网络设备配置所述第一优先级；所述第一网络设备接收第二网络设备发送的第三优先级，所述第二网络设备与所述第一网络设备包括相同的FlexE组， 所述第三优先级是所述第二网络设备为所述第一FlexE客户端分配的优先级；所述第一网络设备确定所述第一优先级与所述第三优先级相等。
基于本申请提供的方案，第一网络设备为FlexE客户端配置优先级，从而在为高优先级FlexE客户端分配的可用时隙不满足其带宽需求时，将分配给低优先级的FlexE客户端的时隙中的至少部分时隙重新分配给所述高优先级FlexE客户端，从而，提高了高优先级FlexE客户端的高优先级业务的SLA。
在一种可能的实现方式中，所述第一优先级和/或所述第三优先级承载在FlexE开销帧中。
在一种可能的实现方式中，在所述第一网络设备确定为第一FlexE客户端分配的时隙中的第一可用时隙不满足所述第一FlexE客户端的第一需求带宽之前，所述方法还包括：所述第一网络设备根据第一标识小于第二标识，确定所述第一优先级高于所述第二优先级，其中，所述第一标识指示所述第一FlexE客户端，所述第二标识指示所述第二FlexE客户端。
基于本申请提供的方案，第一网络设备利用现有FlexE协议中客户端标识，确定不同客户端的优先级高低，从而在为高优先级FlexE客户端分配的可用时隙不满足其带宽需求时，将分配给低优先级的FlexE客户端的时隙中的至少部分时隙重新分配给所述高优先级FlexE客户端，从而，提高了高优先级FlexE客户端的高优先级业务的SLA。
在一种可能的实现方式中，在所述第一网络设备将分配给第二FlexE客户端的时隙中的至少部分时隙重新分配给所述第一FlexE客户端之后，所述方法还包括：第一网络设备确定为第一FlexE客户端分配的时隙中的第二可用时隙不满足所述第一FlexE客户端的第一需求带宽，其中，所述第二可用时隙包括所述第一可用时隙和所述分配给第二FlexE客户端的时隙中的至少部分时隙；所述第一网络设备将分配给第三FlexE客户端的时隙中的至少部分时隙重新分配给所述第一FlexE客户端，其中，所述第一优先级高于所述第三FlexE客户端的第三优先级，所述第三优先级高于所述第二优先级。
基于本申请提供的方案，在FlexE客户端有多个优先级时，高优先级的第一FlexE客户端分配的时隙中的第一可用时隙不满足第一FlexE客户端的需求带宽时，第一网络设备将分配给最低优先级的第二FlexE客户端的时隙中的至少部分时隙重新分配给所述第一FlexE客户端之后，第一网络设备确定为第一FlexE客户端分配的时隙中的第二可用时隙仍然不满足所述第一FlexE客户端的第一需求带宽。然后第一网络设备将分配给第三FlexE客户端的时隙中的至少部分时隙重新分配给所述第一FlexE客户端。从而，第一FlexE客户端不仅可以使用所述第二可用时隙发送数据，还可以使用原来属于第三FlexE客户端的时隙中的至少部分时隙发送数据，提高了第一FlexE客户端的高优先级业务的SLA。
在一种可能的实现方式中，在所述第一网络设备将分配给第二FlexE客户端的时隙中的至少部分时隙重新分配给所述第一FlexE客户端之前，所述第一网络设备开启所述第一FlexE客户端。
基于本申请提供的方案，在所述第一网络设备将分配给第二FlexE客户端的时隙 中的至少部分时隙重新分配给所述第一FlexE客户端之前，所述第一网络设备开启所述第一FlexE客户端，然后再抢占第二FlexE客户端的时隙，从而，在第一网络设备为第一FlexE客户端分配的时隙不满足第一FlexE客户端的带宽时，也能使第一FlexE客户端保持开启状态继续传输高优先级的数据，从而提高了第一FlexE客户端的高优先级业务的SLA。
第二方面，提供了一种第一网络设备，第一网络设备具有实现上述方法中第一网络设备行为的功能。所述功能可以基于硬件实现，也可以基于硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一个可能的设计中，第一网络设备的结构中包括处理器和接口，所述处理器被配置为支持第一网络设备执行上述方法中相应的功能。所述接口用于支持第一网络设备与另一网络设备之间的通信，从所述另一网络设备接收上述方法中所涉及的信息或者指令。所述接口还用于支持第一网络设备与用户设备之间的通信。所述第一网络设备还可以包括存储器，所述存储器用于与处理器耦合，其保存第一网络设备必要的程序指令和数据。
在另一个可能的设计中，所述第一网络设备包括：处理器、发送器、接收器、随机存取存储器、只读存储器以及总线。其中，处理器通过总线分别耦接发送器、接收器、随机存取存储器以及只读存储器。其中，当需要运行第一网络设备时，通过固化在只读存储器中的基本输入/输出系统或者嵌入式系统中的bootloader引导系统进行启动，引导第一网络设备进入正常运行状态。在第一网络设备进入正常运行状态后，在随机存取存储器中运行应用程序和动作系统，使得该处理器执行第一方面或第一方面的任意可能的实现方式中的方法。
第三方面，提供一种第一网络设备，所述第一网络设备包括：主控板和接口板，进一步，还可以包括交换网板。所述第一网络设备用于执行第一方面或第一方面的任意可能的实现方式中的方法。具体地，所述第一网络设备包括用于执行第一方面或第一方面的任意可能的实现方式中的方法的模块。
第四方面，提供一种第一网络设备，所述第一网络设备包括控制器和转发子设备。所述转发子设备包括：接口板，进一步，还可以包括交换网板。所述转发子设备用于执行第三方面中的接口板的功能，进一步，还可以执行第三方面中交换网板的功能。所述控制器包括接收器、处理器、发送器、随机存取存储器、只读存储器以及总线。其中，处理器通过总线分别耦接接收器、发送器、随机存取存储器以及只读存储器。其中，当需要运行控制器时，通过固化在只读存储器中的基本输入/输出系统或者嵌入式系统中的bootloader引导系统进行启动，引导控制器进入正常运行状态。在控制器进入正常运行状态后，在随机存取存储器中运行应用程序和动作系统，使得该处理器执行第三方面中主控板的功能。
第五方面，提供了一种计算机存储介质，用于储存为上述第一网络设备所用的程序、代码或指令，当处理器或硬件设备执行这些程序、代码或指令时可以完成上述第一方面中第一网络设备的功能或步骤。
第六方面，提供一种通信系统，所述通信系统包括第一网络设备，所述第一网络设备为前述第一方面中的第一网络设备。
第七方面，提供了一种芯片，包括：接口电路和处理器。所述接口电路和所述处理器相连接，所述处理器用于使得所述芯片执行前述任一方面所述的方法以及前述任一方面的任一可能的实现方式中所包括的部分或全部操作。
基于本申请提供的方案，第一网络设备确定为第一FlexE客户端分配的时隙中的第一可用时隙不满足第一FlexE客户端的需求带宽，如果第一FlexE客户端只能使用所述第一可用时隙发送第一FlexE客户端的数据，第一FlexE客户端的SLA会受损，第一网络设备将分配给比第一FlexE客户端优先级低的第二FlexE客户端的时隙中的至少部分时隙重新分配给所述第一FlexE客户端，从而，第一FlexE客户端不仅可以使用所述第一可用时隙发送数据，还可以使用原来属于第二FlexE客户端的时隙中的至少部分时隙发送数据，提高了第一FlexE客户端的高优先级业务的SLA。
附图说明
图1是本申请实施例的应用场景示意图；
图2是本申请实施例中使用FlexE技术传输数据的示意图；
图3是本申请实施例的一种分配时隙的方法流程图；
图4是本申请实施例的另一种分配时隙的方法流程图；
图5为本申请实施例的第一网络设备的结构示意图；
图6为本申请实施例的第一网络设备的硬件结构示意图；
图7为本申请实施例的另一种第一网络设备的硬件结构示意图。
具体实施方式
图1示出了本申请实施例的一种应用场景，下面具体介绍图1示出的场景，在图1中包括2个网络设备，分别为网络设备1、网络设备2，2个用户设备，分别为用户设备1、用户设备2。网络设备1可以是承载网中的边缘节点，例如供应商边缘(provider edge，PE)节点，此时网络设备1直接与用户设备1连接，网络设备1也可以是承载网中的中间节点，例如供应商(provider，P)节点，此时网络设备通过其他网络设备与用户设备1连接。网络设备2也可以是边缘节点或中间节点，可以参考网络设备1的相关描述，此处不再赘述。网络设备1与网络设备2上的连线为一个FlexE组，一个FlexE由多个物理结构组合而成，并且可以承载多个FlexE客户端的数据。
应理解，图1中仅示例性的示出了2个网络设备和2个用户设备，该网络可以包括任意其它数量的网络设备和用户设备，本申请实施例对此不做限定。图1中所示的FlexE通信系统仅是举例说明，本申请提供的FlexE通信系统的应用场景不限于图1所示的场景。本申请提供的技术方案适用于所有应用采用FlexE技术进行数据传输的网络场景。
在介绍具体实施例之前，首先对FlexE相关的技术术语进行介绍。
FlexE客户端：是支持各种速率的以太网数据流，如10千兆位/秒(gigabits per second，Gbps)、40Gbps、n*25Gbps数据流，甚至非标准速率数据流，具体来说，FlexE client是数据流的一个容器，也可以看做一个逻辑接口，这个逻辑接口是数据流 的传输接口，通过64B/66B的编码的方式将数据流传递至FlexE shim层。
FlexE组：本质上就是IEEE 802.3标准定义的各种以太网PHY层，默认把PHY的带宽池化为5GE粒度的资源。
FlexE shim：作为插入传统以太架构的MAC与PHY(PCS子层)中间的一个额外逻辑层，FlexE shim将FlexE组中的每个PHY划分为多个时隙，一般来说，默认支持划分为20个时隙的数据承载通道，其中每个时隙所对应的带宽为5Gbps，FlexE shim把FlexE客户端的原始数据流中的以太网帧以Block原子数据块(64/66B编码的数据块)为单位进行切分，这些原子数据块通过FlexE Shim的Calendar机制实现在FlexE组中的时隙映射和传输，实现严格的隔离。
本申请并不限定两个网络设备之间仅存在一个FlexE组，即两个网络设备之间也可以具有多个FlexE组。一个PHY可用于承载至少一个客户端，一个客户端可在至少一个PHY上传输。
下面，结合图2介绍图1所示的网络设备1和网络设备2采用FlexE技术传输数据的过程。在图2中，每个PHY的带宽为10Gbps，PHY1、PHY2、PHY3、PHY4绑定成为一个FlexE组，网络设备1和网络设备2之间通过所述FlexE组传输数据。所述FlexE组对应3个客户端，分别为client1、client2和client3，其中client1中的业务数据是最重要的数据，需求带宽为20Gbps，client2中的业务数据是最不重要的数据，需求带宽为10Gbps，client3中的业务数据是重要等级为中间重要的数据，需求带宽为10Gbps，那么，网络设备1为client1分配4个时隙，对应于PHY1和PHY2，网络设备1为client2分配2个时隙，对应于PHY3，网络设备1为client3分配1个时隙，对应于PHY4，网络设备1建立时隙表，指示网络设备1按照时隙表的时隙指示发送对应客户端的数据，如表1。应理解，网络设备1可以对一个FlexE组建立1张时隙表，如表1，也可以对一个PHY建立一张表，那么表1会被拆分成4张表，本申请实施例并不对时隙表的形式加以限制。
时隙号 FlexE客户端号 PHY标识 FlexE组
1 1 1 1
2 1 1 1
1 1 2 1
2 1 2 1
1 2 3 1
2 2 3 1
1 3 4 1
2 3 4 1
表1
应理解，网络设备2会按照shim层控制协议建立与表1相同的时隙表，用于指示网络设备2在对应的时隙接收对应的客户端的数据。
FlexE shim根据相同的时钟对数据进行切片，并将切片后的数据封装至预先划分的时隙中，然后，根据时隙表1，将划分好的各时隙映射至FlexE组中的PHY上进行传输。
按照当前FlexE标准，当FlexE组中的PHY处于故障状态时，则使用这一PHY传输数据的所有FlexE客户端均会受损，其中，某些FlexE客户端承载高优先级的业务数据，例如client1，这些数据也无法通过故障的PHY发送，导致高优先级业务的SLA受损。
有鉴于此，参见图3，本申请提出了一种时隙分配的方法100，用于提高优先级业务的SLA。所述方法100可以用于图1或图2所示的场景中，下面结合图1或图2所示的场景介绍方法100，其中，第一网络设备相当于图1或图2中的网络设备，例如网络设备1，第二网络设备相当于图1或图2中的网络设备，例如网络设备2，所述方法包括S101-S102。
S101、第一网络设备确定为第一灵活以太FlexE客户端分配的时隙中的第一可用时隙不满足所述第一FlexE客户端的第一需求带宽。
一般情况下，在如下3个场景中，第一网络设备确定为第一灵活以太FlexE客户端分配的时隙中的第一可用时隙不满足所述第一FlexE客户端的第一需求带宽：
场景1、故障场景：所述第一网络设备确定第一物理层PHY发生故障，所述第一PHY与所述第一FlexE客户端关联。
在第一PHY没有发生故障时，第一网络设备按照第一FlexE客户端的第一带宽需求为第一FlexE客户端分配时隙，从而，第一网络设备确定为第一FlexE客户端分配的时隙都是可用时隙，满足所述第一FlexE客户端的第一需求带宽。以第一FlexE客户端对应于图2中的client1为例进行说明，client1的第一需求带宽是满足client数据流传输需求的带宽。具体实现方式为，在网络设备1上，会为每个client创建一个虚拟接口，在虚拟接口下配置与client对应的配置，在虚拟接口1下，会配置client1的需求带宽，例如20Gbps，然后第一网络设备会按照20Gbps为client1分配时隙以满足client1数据流的传输需求，如表1，第一网络设备为client1分配4个时隙，其中，2个时隙对应PHY1，2个时隙对应PHY2。
第一PHY发生故障，此时，第一网络设备为第一FlexE客户端分配的时隙中，没有对应第一PHY的部分时隙仍然可用，为第一可用时隙，对应第一PHY的部分时隙不可用，显然，第一可用时隙为第一网络设备为第一FlexE客户端分配的部分时隙，从而，不满足第一FlexE客户端的第一需求带宽。本申请实施例中的故障包括物理链路故障，发送侧连接PHY的装置故障，接收侧连接PHY的装置故障等，本申请并不对PHY故障的类型进行限制。以第一PHY对应于图2中的PHY1为例，此时对应PHY1的2个时隙无法传输client1的数据，剩余的对应PHY2的2个时隙不满足client1的需求带宽20Gbps。
场景2、扩容场景：所述第一网络设备确定所述第一FlexE客户端的带宽需求由第二需求带宽变更为所述第一需求带宽，所述第二需求带宽小于所述第一需求带宽。
在第一FlexE客户端的带宽需求没有变更之前，第一FlexE客户端的带宽需求为第二带宽需求，所述第一网络设备按照第二需求带宽为第一FlexE客户端分配时隙，此时分配的时隙满足第一FlexE客户端的第二需求带宽。仍然以第一FlexE客户端对应于图2中的client1为例进行说明，第二需求带宽为20Gbps，第一网络设备会按照20Gbps为client1分配时隙以满足client1数据流的传输需求，如表1，第一网络设备为client1分配4个时隙，其中，2个时隙对应PHY1，2个时隙对应PHY2。
所述第一FlexE客户端的带宽需求由第二需求带宽变更为所述第一需求带宽，所述第一需求带宽大于所述第二需求带宽，此时，第一网络设备为第一FlexE客户端分配的时隙中的全部时隙仍然可用，为第一可用时隙，但是由于带宽需求增加，不满足所述第一FlexE客户端的第一需求带宽。例如，client1的需求带宽由20Gbps变更为40Gbps，此时，原有的4个时隙不够传输40Gbps的数据。
场景3、新增客户端场景：所述第一网络设备新增客户端，确定为新增客户端分配的时隙无法满足新增客户端的带宽需求。
在图2场景中，新增一个客户端client4，client4的需求带宽为10Gbps，目前剩余的PHY的带宽为5Gbps，那么没有足够的PHY资源供client4使用，网络设备1为client4分配的时隙是1个，对应于PHY4，不满足client4的带宽需求。
在本申请实施例中，当为第一FlexE客户端分配的时隙中的第一可用时隙不满足所述第一FlexE客户端的第一需求带宽时，所述第一网络设备开启所述第一FlexE客户端，即对FlexE客户端进行缩容处理，而不是直接将FlexE客户端关闭，以缩容的方式，为FlexE客户端提供服务。
S102、第一网络设备将分配给第二FlexE客户端的时隙中的至少部分时隙重新分配给所述第一FlexE客户端，其中，所述第一FlexE客户端的第一优先级高于所述第二FlexE客户端的第二优先级。
在本申请实施例中，每个FlexE客户端与一个优先级关联，表示FlexE客户端的流量的优先级，不同FlexE客户端的优先级可以相同，也可以不同，具体实现时，第一网络设备会为每个客户端创建一个虚拟接口，在虚拟接口下配置与客户端相关的配置，此时增加优先级的配置。在本申请实施例中，以使用数字表示优先级为例，1表示最高优先级，2表示中间优先级，3表示最低优先级，应理解，本申请实施例中只例举出3种优先级，当然，也可以包括更多的优先级等级，也在本申请的保护范围中。在图2中，clien1的优先级为1，clien2的优先级为3，client3的优先级为2。
第一网络设备和第二网络设备需要进行客户端的优先级协商，以保证相同的客户端的优先级配置相同，优先级协商的过程为：所述第一网络设备接收第二网络设备发送的第三优先级，所述第二网络设备与所述第一网络设备包括相同的FlexE组，所述第三优先级是所述第二网络设备为所述第一FlexE客户端分配的优先级；所述第一网络设备确定所述第一优先级与所述第三优先级相等。其中，所述第一优先级和/或所述第三优先级承载在FlexE开销帧中。
本申请实施例提供了以下2种客户端的优先级协商方式。
方式1、以图2所示的场景为例，网络设备1和网络设备2上的client1的优先级协商过程为：网络设备1和网络设备2分配配置client1的优先级为1，然后网络设备1向网络设备2发送优先级1，网络设备2确定与本地配置的client1的优先级1相同，网络设备2向网络设备1发送确认消息1，指示网络设备2和网络设备1的优先级相同。网络设备2向网络设备1发送优先级1，网络设备1确定与本地配置的client1的优先级1相同，网络设备1向网络设备2发送确认消息2，指示网络设备1和网络设备2的优先级相同。由此，网络设备1和网络设备2的优先级协商成功。
方式2、网络设备1向网络设备2发送优先级1，网络设备2确定与本地配置的client1 的优先级1相同。网络设备2向网络设备1发送优先级1，网络设备1确定与本地配置的client1的优先级1相同。由此，网络设备1和网络设备2的优先级协商成功。
在上述优先级协商的过程中，如果任何一个网络设备发现接收的优先级与本地配置的优先级不同，那么优先级协商失败，此时需要网管检查并修正网络设备的优先级配置，确保两端网络设备配置的优先级相同。
在本申请实施例中，FlexE通信系统中还可以设置一个规则，例如，客户端的优先级与客户端标识呈正相关或负相关，那么，在支持FlexE的设备上，不需要进行上述优先级配置和协商的过程，就能够确定不同FlexE客户端的优先级的关系。
以上介绍了第一网络设备确定不同FlexE客户端的优先级高低的方式，下面具体介绍第一网络设备确定为第一FlexE客户端分配的时隙中的第一可用时隙不满足所述第一FlexE客户端的第一需求带宽之后的处理。
第一网络设备确定为第一灵活以太FlexE客户端分配的时隙中的第一可用时隙不满足所述第一FlexE客户端的第一需求带宽之后，会将为优先级低于第一FlexE客户端的第二FlexE客户端分配的时隙中的至少部分时隙重新分配给所述第一FlexE客户端，所述至少部分时隙可以是第一网络设备为第二FlexE客户端分配的时隙中的部分时隙，也可以是第一网络设备为第二FlexE客户端分配的时隙中的全部时隙。第一网络设备在比第一FlexE客户端的优先级低的客户端中任选一个客户端作为第二FlexE客户端，或者，第一网络设备在比第一FlexE客户端的优先级低的客户端中选择优先级最低的客户端作为所述第二FlexE客户端。
下面，对应于S101中的3种场景，举例说明第一网络设备确定为第一FlexE客户端分配的时隙中的第一可用时隙不满足所述第一FlexE客户端的第一需求带宽之后的处理。
场景1、故障场景：图2中的PHY1故障，此时对应PHY1的2个时隙无法传输client1的数据，剩余的对应PHY2的2个时隙不满足client1的需求带宽20Gbps。网络设备1将为client2分配的2个时隙重新分配给client1，此时，client1有4个时隙传输数据，满足client1的需求带宽20Gbps。或者，网络设备1将为client2分配的2个时隙中的1个时隙重新分配给client1，此时，client1有3个时隙传输数据，client1获得的传输带宽增加。client2剩余的带宽不满足带宽需求，client2仍然保持开启状态。
场景2、扩容场景：图2中的client1的需求带宽由20Gbps变更为40Gbps，此时，原有的4个时隙不够传输40Gbps的数据。网络设备1将为client2分配的2个时隙重新分配给client1，此时，client1有6个时隙传输数据，client1获得的传输带宽增加。或者，网络设备1将为client2分配的2个时隙中的1个时隙重新分配给client1，此时，client1有3个时隙传输数据，client1获得的传输带宽增加。client2剩余的带宽不满足带宽需求，client2仍然保持开启状态。
场景3、新增客户端场景：图2场景新增一个客户端client4，client4的优先级为1，client4的需求带宽为10Gbps，目前剩余的PHY的带宽为0Gbps，那么没有足够的PHY资源供client4使用，不满足client4的带宽需求，网络设备将为client2分配的2个时隙中的1个时隙重新分配给client4，此时，client4有1个时隙传输数据，client4获得的带宽增加，client4保持开启状态，或者，网络设备将为client2分配的2个时隙重新分配给client4，此时，client4有2个时隙传输数据，满足client4的带宽需求。client2剩余的带宽不满足带宽 需求，client2仍然保持开启状态。
应理解，本申请实施例中，开启客户端与客户端保持开启状态的含义相同，都是将客户端配置为开启状态。
在所述第一网络设备将分配给第二FlexE客户端的时隙中的至少部分时隙重新分配给所述第一FlexE客户端中，所述第一网络设备将第二时隙表项更新为第一时隙表项，其中，所述第二时隙表项指示所述第二FlexE客户端的时隙中的至少部分时隙。
所述第一网络设备将第二时隙表项更新为第一时隙表项，包括：所述第一网络设备将所述第二时隙表项中的第二标识更新为所述第一时隙表项中的第一标识，其中，所述第二标识指示所述第二FlexE客户端，所述第一标识指示所述第一FlexE客户端。
例如，对应于上述故障的场景，网络设备1将为client2分配的2个时隙重新分配给client1。第二时隙表项为表1，网络设备1将表1更新为表2，具体为，将表1中FlexE客户端标识中client2更新为client1。
时隙号 FlexE客户端标识 PHY标识 FlexE组
1 1 1 1
2 1 1 1
1 1 2 1
2 1 2 1
1 1 3 1
2 1 3 1
1 3 4 1
2 3 4 1
表2
由此，基于本申请实施例提供的方案，第一网络设备确定为第一FlexE客户端分配的时隙中的第一可用时隙不满足第一FlexE客户端的需求带宽，如果第一FlexE客户端只能使用所述第一可用时隙发送第一FlexE客户端的数据，第一FlexE客户端的SLA会受损，第一网络设备将分配给比第一FlexE客户端优先级低的第二FlexE客户端的时隙中的至少部分时隙重新分配给所述第一FlexE客户端，从而，第一FlexE客户端不仅可以使用所述第一可用时隙发送数据，还可以使用原来属于第二FlexE客户端的时隙中的至少部分时隙发送数据，提高了第一FlexE客户端的高优先级业务的SLA。
可选地，如图4所示，在所述第一网络设备将分配给第二FlexE客户端的时隙中的至少部分时隙重新分配给所述第一FlexE客户端之后，所述第一网络设备还需要执行S103-S104。
S103、第一网络设备确定为第一FlexE客户端分配的时隙中的第二可用时隙不满足所述第一FlexE客户端的第一需求带宽。
其中，所述第二可用时隙包括方法100中的所述第一可用时隙和所述分配给第二FlexE客户端的时隙中的至少部分时隙，例如，对应于S101中故障的场景，PHY1故障后，网络设备1为client1分配的时隙中的第一可用时隙为2个时隙，网络设备1将为client2分配的时隙中的1个时隙分配给client1，网络设备1为client1分配的时隙中的第二可用时隙为3个时隙。
S104、所述第一网络设备将分配给第三FlexE客户端的时隙中的至少部分时隙重新分配给所述第一FlexE客户端，其中，所述第一优先级高于所述第三FlexE客户端的第三优先级，所述第三优先级高于所述第二优先级。
第一网络设备确定为第一FlexE客户端分配的时隙中的第一可用时隙不满足所述第一FlexE客户端的第一需求带宽，然后将优先级最低的第二客户端的至少部分时隙重新分配给第一FlexE客户端，如果重新分配之后，第一FlexE客户端的时隙还是不够，再将分配给第三FlexE客户端的时隙中的至少部分时隙重新分配给所述第一FlexE客户端，其中，所述第一优先级高于所述第三FlexE客户端的第三优先级，所述第三优先级高于所述第二优先级。
例如，对应于S101中故障的场景，PHY1故障后，网络设备1为client1分配的时隙中的第一可用时隙为2个时隙，网络设备1将为client2分配的时隙中的1个时隙分配给client1，网络设备1为client1分配的时隙中的第二可用时隙为3个时隙，仍然不满足client1的带宽需求，那么网络设备1将为client3分配的时隙中的1个时隙分配给client1，此时client1获得4个时隙用于传输client1的数据，满足其带宽需求。
基于本申请实施例提供的方案，在FlexE客户端有多个优先级时，高优先级的第一FlexE客户端分配的时隙中的第一可用时隙不满足第一FlexE客户端的需求带宽时，第一网络设备将分配给最低优先级的第二FlexE客户端的时隙中的至少部分时隙重新分配给所述第一FlexE客户端之后，第一网络设备确定为第一FlexE客户端分配的时隙中的第二可用时隙仍然不满足所述第一FlexE客户端的第一需求带宽。然后第一网络设备将分配给第三FlexE客户端的时隙中的至少部分时隙重新分配给所述第一FlexE客户端。从而，第一FlexE客户端不仅可以使用所述第二可用时隙发送数据，还可以使用原来属于第三FlexE客户端的时隙中的至少部分时隙发送数据，提高了第一FlexE客户端的高优先级业务的SLA。
图5为本申请实施例的第一网络设备1000的结构示意图。图5所示的第一网络设备1000可以执行上述实施例的方法中第一网络设备执行的相应步骤。所述第一网络设备1000被部署在通信网络中，所述通信网络还包括第二网络设备。如图5所示，所述第一网络设备1000包括处理单元1001和收发单元1002。
处理单元1001，用于确定为第一灵活以太FlexE客户端分配的时隙中的第一可用时隙不满足所述第一FlexE客户端的第一需求带宽；
所述处理单元1001，还用于将分配给第二FlexE客户端的时隙中的至少部分时隙重新分配给所述第一FlexE客户端，其中，所述第一FlexE客户端的第一优先级高于所述第二FlexE客户端的第二优先级。
在一种可能的实现方式中，所述处理单元1001，用于确定为第一FlexE客户端分配的时隙中的第一可用时隙不满足所述第一FlexE客户端的第一需求带宽中，所述处理单元1001具体用于：确定第一物理层PHY发生故障，所述第一PHY与所述第一FlexE客户端关联。
在一种可能的实现方式中，所述处理单元1001，用于确定为第一FlexE客户端分配的时隙中的第一可用时隙不满足所述第一FlexE客户端的第一需求带宽中，所述处理单元1001具体用于：确定所述第一FlexE客户端的带宽需求由第二需求带宽变更为所述第一需 求带宽，所述第二需求带宽小于所述第一需求带宽。
在一种可能的实现方式中，所述处理单元1001，用于将分配给第二FlexE客户端的时隙中的至少部分时隙重新分配给所述第一FlexE客户端中，所述处理单元1001具体用于：
将第二时隙表项更新为第一时隙表项，其中，所述第二时隙表项指示所述第二FlexE客户端的时隙中的至少部分时隙。
在一种可能的实现方式中，所述处理单元1001具体用于：将所述第二时隙表项中的第二标识更新为所述第一时隙表项中的第一标识，其中，所述第二标识指示所述第二FlexE客户端，所述第一标识指示所述第一FlexE客户端。
在一种可能的实现方式中，所述处理单元1001，用于确定为第一FlexE客户端分配的时隙中的第一可用时隙不满足所述第一FlexE客户端的第一需求带宽之前，所述处理单元1001，还用于配置所述第一优先级；
所述收发单元1002，用于接收第二网络设备发送的第三优先级，所述第二网络设备与所述第一网络设备包括相同的FlexE组，所述第三优先级是所述第二网络设备为所述第一FlexE客户端分配的优先级；
所述处理单元1001，还用于确定所述第一优先级与所述第三优先级相等。
在一种可能的实现方式中，所述第一优先级和/或所述第三优先级承载在FlexE开销帧中。
在一种可能的实现方式中，在所述处理单元1001，用于确定为第一FlexE客户端分配的时隙中的第一可用时隙不满足所述第一FlexE客户端的第一需求带宽之前，所述处理单元1001还用于：根据第一标识小于第二标识，确定所述第一优先级高于所述第二优先级，其中，所述第一标识指示所述第一FlexE客户端，所述第二标识指示所述第二FlexE客户端。
在一种可能的实现方式中，所述处理单元1001，用于将分配给第二FlexE客户端的时隙中的至少部分时隙重新分配给所述第一FlexE客户端之后，所述处理单元1001还用于：确定为第一FlexE客户端分配的时隙中的第二可用时隙不满足所述第一FlexE客户端的第一需求带宽，其中，所述第二可用时隙包括所述第一可用时隙和所述分配给第二FlexE客户端的时隙中的至少部分时隙；
将分配给第三FlexE客户端的时隙中的至少部分时隙重新分配给所述第一FlexE客户端，其中，所述第一优先级高于所述第三FlexE客户端的第三优先级，所述第三优先级高于所述第二优先级。
在一种可能的实现方式中，所述处理单元1001，用于将分配给第二FlexE客户端的时隙中的至少部分时隙重新分配给所述第一FlexE客户端之前，所述处理单元1001，还用于开启所述第一FlexE客户端。
图6为本申请实施例的第一网络设备1100的硬件结构示意图。图6所示的第一网络设备1100可以执行上述实施例的方法中第一网络设备执行的相应步骤。
如图6所示，所述第一网络设备1100包括处理器1101、存储器1102、接口1103和总线1104。其中接口1103可以通过无线或有线的方式实现。上述处理器1101、存储器1102和接口1103通过总线1104连接。
所述接口1103具体可以包括发送器和接收器，用于第一网络设备与上述实施例 中的第二网络设备之间收发信息。例如，所述接口1103用于支持向所述第二网络设备发送控制消息。作为举例，所述接口1103用于支持图3中的过程S102中优先级协商过程。所述处理器1101用于执行上述实施例中由第一网络设备进行的处理。例如，所述处理器1101用于执行生成所述控制消息的动作；和/或用于本文所描述的技术的其他过程。作为举例，所述处理器1101用于支持图3中的过程S101。存储器1102，用于存储程序、代码或指令，例如，存储动作系统11021和应用程序11022，当处理器或硬件设备执行这些程序、代码或指令时可以完成方法实施例中涉及第一网络设备的处理过程。可选地，所述存储器1102可以包括只读存储器(Read-only Memory，ROM)和随机存取存储器(Random Access Memory，RAM)。其中，所述ROM包括基本输入/输出系统(Basic Input/Output System，BIOS)或嵌入式系统；所述RAM包括应用程序和动作系统。当需要运行第一网络设备1100时，通过固化在ROM中的BIOS或者嵌入式系统中的bootloader引导系统进行启动，引导第一网络设备1100进入正常运行状态。在第一网络设备1100进入正常运行状态后，运行在RAM中的应用程序和动作系统，从而，完成方法实施例中涉及第一网络设备的处理过程。
可以理解的是，图6仅仅示出了第一网络设备1100的简化设计。在实际应用中，第一网络设备可以包含任意数量的接口，处理器或者存储器。
图7为本申请实施例的另一种第一网络设备1200的硬件结构示意图。图7所示的第一网络设备1200可以执行上述实施例的方法中第一网络设备执行的相应步骤。
如图7所述，第一网络设备1200包括：主控板1210、接口板1230、交换网板1220和接口板1240。主控板1210、接口板1230和1240，以及交换网板1220之间通过系统总线与系统背板相连实现互通。其中，主控板1210用于完成系统管理、设备维护、协议处理等功能。交换网板1220用于完成各接口板(接口板也称为线卡或业务板)之间的数据交换。接口板1230和1240用于提供各种业务接口(例如，POS接口、GE接口、ATM接口等)，并实现数据包的转发。
接口板1230可以包括中央处理器1231、转发表项存储器1234、物理接口卡1233和网络处理器1232。其中，中央处理器1231用于对接口板进行控制管理并与主控板上的中央处理器进行通信。转发表项存储器1234用于保存转发表项。物理接口卡1233用于完成流量的接收和发送。网络存储器1232用于根据所述转发表项控制物理接口卡1233收发流量。
具体地，物理接口卡1233用于用于向所述第二网络设备发送所述第一优先级。具体的，中央处理器1231用于控制网络处理器1232经由物理接口卡1233向所述第二网络设备发送所述第一优先级。
应理解，本发明实施例中接口板1240上的动作与所述接口板1230的动作一致，为了简洁，不再赘述。应理解，本实施例的第一网络设备1200可对应于上述方法实施例所具有的功能和/或所实施的各种步骤，在此不再赘述。
此外，需要说明的是，主控板可能有一块或多块，有多块的时候可以包括主用主控板和备用主控板。接口板可能有一块或多块，第一网络设备的数据处理能力越强，提供的接口板越多。接口板上的物理接口卡也可以有一块或多块。交换网板可能没有，也可能有一块或多块，有多块的时候可以共同实现负荷分担冗余备份。在集中式转发 架构下，第一网络设备可以不需要交换网板，接口板承担整个系统的业务数据的处理功能。在分布式转发架构下，第一网络设备可以有至少一块交换网板，通过交换网板实现多块接口板之间的数据交换，提供大容量的数据交换和处理能力。所以，分布式架构的第一网络设备的数据接入和处理能力要大于集中式架构的设备。具体采用哪种架构，取决于具体地组网部署场景，此处不做任何限定。
本申请实施例提供了一种计算机存储介质，用于储存为上述第一网络设备所用的计算机软件指令，其包含用于执行上述方法实施例所设计的程序。
本申请实施例还提供了一种芯片，包括：接口电路和处理器。所述接口电路和所述处理器相连接，所述处理器用于使得所述芯片执行前述实施例中任一实施例所述的方法(例如，方法100)中的部分或全部操作。
本申请实施例还提供一种芯片系统，包括：处理器，所述处理器与存储器耦合，所述存储器用于存储程序或指令，当所述程序或指令被所述处理器执行时，使得该芯片系统实现前述实施例中任一实施例所述的方法(例如，方法100)中的部分或全部操作。
可选地，该芯片系统中的处理器可以为一个或多个。该处理器可以通过硬件实现也可以通过软件实现。当通过硬件实现时，该处理器可以是逻辑电路、集成电路等。当通过软件实现时，该处理器可以是一个通用处理器，通过读取存储器中存储的软件代码来实现。
可选地，该芯片系统中的存储器也可以为一个或多个。该存储器可以与处理器集成在一起，也可以和处理器分离设置，本申请实施例并不限定。示例性的，存储器可以是非瞬时性处理器，例如只读存储器ROM，其可以与处理器集成在同一块芯片上，也可以分别设置在不同的芯片上，本申请实施例对存储器的类型，以及存储器与处理器的设置方式不作具体限定。
示例性的，该芯片系统可以是FPGA，可以是ASIC，还可以是系统芯片(system on chip，SoC)，还可以是CPU，还可以是NP，还可以是数字信号处理电路(digital signal processor，DSP)，还可以是微控制器(micro controller unit，MCU)，还可以是可编程控制器(programmable logic device，PLD)或其他集成芯片。
本申请实施例还包括一种网络系统，所述网络系统包括第一网络设备和第二网络设备，所述第一网络设备为前述图5或图6或图7中的第一网络设备，所述第二网络设备为前述图5或图6或图7中的第二网络设备。
结合本申请公开内容所描述的方法或者算法的步骤可以硬件的方式来实现，也可以是由处理器执行软件指令的方式来实现。软件指令可以由相应的软件模块组成，软件模块可以被存放于RAM存储器、闪存、ROM存储器、EPROM存储器、EEPROM存储器、寄存器、硬盘、移动硬盘、CD-ROM或者本领域熟知的任何其它形式的存储介质中。一种示例性的存储介质耦合至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息。当然，存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外，该ASIC可以位于用户设备中。当然，处理器和存储介质也可以作为分立组件存在于用户设备中。
本领域技术人员应该可以意识到，在上述一个或多个示例中，本申请所描述的功 能可以用硬件或者用硬件和软件的组合来实现。当使用硬件和软件的组合实现时，可以将这些软件存储在计算机可读介质中或者作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质，其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是通用或专用计算机能够存取的任何可用介质。
以上所述的具体实施方式，对本申请的目的、技术方案和有益效果进行了进一步详细说明。所应理解的是，以上所述仅为本申请的具体实施方式而已。

Claims (22)

  1. 一种时隙分配的方法，其特征在于，包括：
    第一网络设备确定为第一灵活以太FlexE客户端分配的时隙中的第一可用时隙不满足所述第一FlexE客户端的第一需求带宽；
    所述第一网络设备将分配给第二FlexE客户端的时隙中的至少部分时隙重新分配给所述第一FlexE客户端，其中，所述第一FlexE客户端的第一优先级高于所述第二FlexE客户端的第二优先级。
  2. 如权利要求1所述的方法，其特征在于，在所述第一网络设备确定为第一FlexE客户端分配的时隙中的第一可用时隙不满足所述第一FlexE客户端的第一需求带宽中，包括：
    所述第一网络设备确定第一物理层PHY发生故障，所述第一PHY与所述第一FlexE客户端关联。
  3. 如权利要求1所述的方法，其特征在于，在所述第一网络设备确定为第一FlexE客户端分配的时隙中的第一可用时隙不满足所述第一FlexE客户端的第一需求带宽中，包括：
    所述第一网络设备确定所述第一FlexE客户端的带宽需求由第二需求带宽变更为所述第一需求带宽，所述第二需求带宽小于所述第一需求带宽。
  4. 如权利要求1-3任一项所述的方法，其特征在于，在所述第一网络设备将分配给第二FlexE客户端的时隙中的至少部分时隙重新分配给所述第一FlexE客户端中，包括：
    所述第一网络设备将第二时隙表项更新为第一时隙表项，其中，所述第二时隙表项指示所述第二FlexE客户端的时隙中的至少部分时隙。
  5. 如权利要求4所述的方法，其特征在于，所述第一网络设备将第二时隙表项更新为第一时隙表项，包括：
    所述第一网络设备将所述第二时隙表项中的第二标识更新为所述第一时隙表项中的第一标识，其中，所述第二标识指示所述第二FlexE客户端，所述第一标识指示所述第一FlexE客户端。
  6. 权利要求1-5任一项所述的方法，其特征在于，在所述第一网络设备确定为第一FlexE客户端分配的时隙中的第一可用时隙不满足所述第一FlexE客户端的第一需求带宽之前，所述方法还包括：
    所述第一网络设备配置所述第一优先级；
    所述第一网络设备接收第二网络设备发送的第三优先级，所述第二网络设备与所述第一网络设备包括相同的FlexE组，所述第三优先级是所述第二网络设备为所述第一FlexE客户端分配的优先级；
    所述第一网络设备确定所述第一优先级与所述第三优先级相等。
  7. 如权利要求6所述的方法，其特征在于，所述第一优先级和/或所述第三优先级承载在FlexE开销帧中。
  8. 如权利要求1-4任一项所述的方法，其特征在于，在所述第一网络设备确定为第一FlexE客户端分配的时隙中的第一可用时隙不满足所述第一FlexE客户端的第一需求带宽之前，所述方法还包括：
    所述第一网络设备根据第一标识小于第二标识，确定所述第一优先级高于所述第二优先级，其中，所述第一标识指示所述第一FlexE客户端，所述第二标识指示所述第二FlexE 客户端。
  9. 如权利要求1-8任一项所述的方法，其特征在于，在所述第一网络设备将分配给第二FlexE客户端的时隙中的至少部分时隙重新分配给所述第一FlexE客户端之后，所述方法还包括：
    第一网络设备确定为第一FlexE客户端分配的时隙中的第二可用时隙不满足所述第一FlexE客户端的第一需求带宽，其中，所述第二可用时隙包括所述第一可用时隙和所述分配给第二FlexE客户端的时隙中的至少部分时隙；
    所述第一网络设备将分配给第三FlexE客户端的时隙中的至少部分时隙重新分配给所述第一FlexE客户端，其中，所述第一优先级高于所述第三FlexE客户端的第三优先级，所述第三优先级高于所述第二优先级。
  10. 如权利要求1-9任一项所述的方法，其特征在于，在所述第一网络设备将分配给第二FlexE客户端的时隙中的至少部分时隙重新分配给所述第一FlexE客户端之前，所述第一网络设备开启所述第一FlexE客户端。
  11. 一种第一网络设备，其特征在于，所述第一网络设备包括：
    处理单元，用于确定为第一灵活以太FlexE客户端分配的时隙中的第一可用时隙不满足所述第一FlexE客户端的第一需求带宽；
    所述处理单元，还用于将分配给第二FlexE客户端的时隙中的至少部分时隙重新分配给所述第一FlexE客户端，其中，所述第一FlexE客户端的第一优先级高于所述第二FlexE客户端的第二优先级。
  12. 如权利要求11所述的第一网络设备，其特征在于，在所述处理单元，用于确定为第一FlexE客户端分配的时隙中的第一可用时隙不满足所述第一FlexE客户端的第一需求带宽中，所述处理单元具体用于：
    确定第一物理层PHY发生故障，所述第一PHY与所述第一FlexE客户端关联。
  13. 如权利要求11所述的第一网络设备，其特征在于，在所述处理单元，用于确定为第一FlexE客户端分配的时隙中的第一可用时隙不满足所述第一FlexE客户端的第一需求带宽中，所述处理单元具体用于：
    确定所述第一FlexE客户端的带宽需求由第二需求带宽变更为所述第一需求带宽，所述第二需求带宽小于所述第一需求带宽。
  14. 如权利要求11-13任一项所述的第一网络设备，其特征在于，在所述处理单元，用于将分配给第二FlexE客户端的时隙中的至少部分时隙重新分配给所述第一FlexE客户端中，所述处理单元具体用于：
    将第二时隙表项更新为第一时隙表项，其中，所述第二时隙表项指示所述第二FlexE客户端的时隙中的至少部分时隙。
  15. 如权利要求14所述的第一网络设备，其特征在于，所述处理单元具体用于：
    将所述第二时隙表项中的第二标识更新为所述第一时隙表项中的第一标识，其中，所述第二标识指示所述第二FlexE客户端，所述第一标识指示所述第一FlexE客户端。
  16. 权利要求11-15任一项所述的第一网络设备，其特征在于，在所述处理单元，用于确定为第一FlexE客户端分配的时隙中的第一可用时隙不满足所述第一FlexE客户端的第一需求带宽之前，所述处理单元，还用于配置所述第一优先级；
    所述第一网络设备还包括收发单元，用于接收第二网络设备发送的第三优先级，所述第二网络设备与所述第一网络设备包括相同的FlexE组，所述第三优先级是所述第二网络设备为所述第一FlexE客户端分配的优先级；
    所述处理单元，还用于确定所述第一优先级与所述第三优先级相等。
  17. 如权利要求16所述的第一网络设备，其特征在于，所述第一优先级和/或所述第三优先级承载在FlexE开销帧中。
  18. 如权利要求11-14任一项所述的第一网络设备，其特征在于，在所述处理单元，用于确定为第一FlexE客户端分配的时隙中的第一可用时隙不满足所述第一FlexE客户端的第一需求带宽之前，所述处理单元还用于：
    根据第一标识小于第二标识，确定所述第一优先级高于所述第二优先级，其中，所述第一标识指示所述第一FlexE客户端，所述第二标识指示所述第二FlexE客户端。
  19. 如权利要求11-18任一项所述的第一网络设备，其特征在于，在所述处理单元，用于将分配给第二FlexE客户端的时隙中的至少部分时隙重新分配给所述第一FlexE客户端之后，所述处理单元还用于：
    确定为第一FlexE客户端分配的时隙中的第二可用时隙不满足所述第一FlexE客户端的第一需求带宽，其中，所述第二可用时隙包括所述第一可用时隙和所述分配给第二FlexE客户端的时隙中的至少部分时隙；
    将分配给第三FlexE客户端的时隙中的至少部分时隙重新分配给所述第一FlexE客户端，其中，所述第一优先级高于所述第三FlexE客户端的第三优先级，所述第三优先级高于所述第二优先级。
  20. 如权利要求11-19任一项所述的第一网络设备，其特征在于，在所述处理单元，用于将分配给第二FlexE客户端的时隙中的至少部分时隙重新分配给所述第一FlexE客户端之前，所述处理单元，还用于开启所述第一FlexE客户端。
  21. 一种通信系统，其特征在于，包括第一网络设备，所述第一网络设备用于执行权利要求1-10任一项所述的方法。
  22. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质中存储有指令，当所述指令在处理器上运行时，实现权利要求1-10任一项所述的方法。
PCT/CN2023/070705 2022-01-24 2023-01-05 一种时隙分配的方法、网络设备和系统 WO2023138390A1 (zh)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN202210098892.8 2022-01-24
CN202210098892 2022-01-24
CN202210285749.X 2022-03-22
CN202210285749.XA CN116527193A (zh) 2022-01-24 2022-03-22 一种时隙分配的方法、网络设备和系统

Publications (1)

Publication Number Publication Date
WO2023138390A1 true WO2023138390A1 (zh) 2023-07-27

Family

ID=87347767

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/070705 WO2023138390A1 (zh) 2022-01-24 2023-01-05 一种时隙分配的方法、网络设备和系统

Country Status (1)

Country Link
WO (1) WO2023138390A1 (zh)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109428840A (zh) * 2017-08-31 2019-03-05 华为技术有限公司 一种通信方法、设备及存储介质
CN112787844A (zh) * 2020-06-28 2021-05-11 中兴通讯股份有限公司 客户端状态处理方法、装置、网络设备和可读存储介质
CN113452623A (zh) * 2020-03-26 2021-09-28 华为技术有限公司 基于FlexE传输业务流的方法及设备

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109428840A (zh) * 2017-08-31 2019-03-05 华为技术有限公司 一种通信方法、设备及存储介质
CN113452623A (zh) * 2020-03-26 2021-09-28 华为技术有限公司 基于FlexE传输业务流的方法及设备
CN112787844A (zh) * 2020-06-28 2021-05-11 中兴通讯股份有限公司 客户端状态处理方法、装置、网络设备和可读存储介质

Similar Documents

Publication Publication Date Title
US11095571B2 (en) Flexible and scalable enhanced transmission selection method for network fabrics
WO2022022263A1 (zh) 一种传输数据的方法和设备
CN102857494B (zh) 通用网络接口控制器
CN110650002B (zh) 一种FlexE组中PHY的调整方法、相关设备及存储介质
CN113452623B (zh) 基于FlexE传输业务流的方法及设备
US8014401B2 (en) Electronic device and method of communication resource allocation
EP1869845A1 (en) Network-on-chip environment and method for reduction of latency
WO2022042743A1 (zh) 数据传输方法和装置、电子设备、计算机可读介质
US11979335B2 (en) Network controller
WO2022021929A1 (zh) 一种FlexE的资源管理方法及装置
WO2023138390A1 (zh) 一种时隙分配的方法、网络设备和系统
WO2023116449A1 (zh) 一种控制网络切片状态的方法及相关设备
CN116489777A (zh) 应用于tdma数据链时隙资源复用的方法、介质及装置
CN116527193A (zh) 一种时隙分配的方法、网络设备和系统
CN109150747B (zh) 一种变更业务带宽的方法、装置及计算机可读存储介质
CN106453145B (zh) 一种传输链路控制方法及装置
WO2024087691A1 (zh) 一种报文处理方法及相关设备
WO2023169285A1 (zh) 通信方法、装置、网络设备及系统
WO2023021634A1 (ja) 通信制御システム、通信制御方法及び通信制御プログラム
CN116389381A (zh) 一种共享切片资源的方法及相关设备
CN101588587B (zh) 一种通信端口故障后的处理方法及装置
CN118842726A (zh) 一种报文传输的方法、装置及系统
Kaminsky et al. Dynamic channel allocation

Legal Events

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

Ref document number: 23742706

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE