WO2021203680A1 - 一种业务流的传输方法、装置、设备及存储介质 - Google Patents

一种业务流的传输方法、装置、设备及存储介质 Download PDF

Info

Publication number
WO2021203680A1
WO2021203680A1 PCT/CN2020/124143 CN2020124143W WO2021203680A1 WO 2021203680 A1 WO2021203680 A1 WO 2021203680A1 CN 2020124143 W CN2020124143 W CN 2020124143W WO 2021203680 A1 WO2021203680 A1 WO 2021203680A1
Authority
WO
WIPO (PCT)
Prior art keywords
service flow
sub
priority
service
queue group
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.)
Ceased
Application number
PCT/CN2020/124143
Other languages
English (en)
French (fr)
Inventor
喻敬海
高陈强
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by ZTE Corp filed Critical ZTE Corp
Priority to US17/802,805 priority Critical patent/US12224943B2/en
Priority to EP20930547.3A priority patent/EP4135225A4/en
Publication of WO2021203680A1 publication Critical patent/WO2021203680A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/2408—Traffic characterised by specific attributes, e.g. priority or QoS for supporting different services, e.g. a differentiated services [DiffServ] type of service
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/50—Queue scheduling
    • H04L47/62—Queue scheduling characterised by scheduling criteria
    • H04L47/625—Queue scheduling characterised by scheduling criteria for service slots or service orders
    • H04L47/6275—Queue scheduling characterised by scheduling criteria for service slots or service orders based on priority
    • 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
    • H04J3/1605—Fixed allocated frame structures
    • H04J3/1652—Optical Transport Network [OTN]
    • H04J3/1658—Optical Transport Network [OTN] carrying packets or ATM cells
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/302—Route determination based on requested QoS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/2416—Real-time traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/50—Queue scheduling
    • H04L47/52—Queue scheduling by attributing bandwidth to queues
    • H04L47/528—Minimum bandwidth guarantee
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/50—Queue scheduling
    • H04L47/62—Queue scheduling characterised by scheduling criteria
    • H04L47/6295—Queue scheduling characterised by scheduling criteria using multiple queues, one for each individual QoS, connection, flow or priority
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J2203/00—Aspects of optical multiplex systems other than those covered by H04J14/05 and H04J14/07
    • H04J2203/0001—Provisions for broadband connections in integrated services digital network using frames of the Optical Transport Network [OTN] or using synchronous transfer mode [STM], e.g. SONET, SDH
    • H04J2203/0073—Services, e.g. multimedia, GOS, QOS
    • H04J2203/0082—Interaction of SDH with non-ATM protocols
    • H04J2203/0085—Support of Ethernet
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J2203/00—Aspects of optical multiplex systems other than those covered by H04J14/05 and H04J14/07
    • H04J2203/0001—Provisions for broadband connections in integrated services digital network using frames of the Optical Transport Network [OTN] or using synchronous transfer mode [STM], e.g. SONET, SDH
    • H04J2203/0098—Traffic aspects, e.g. arbitration, load balancing, smoothing, buffer management

Definitions

  • the embodiments of the present disclosure relate to the field of communication technologies, and in particular, to a method, device, device, and storage medium for transmitting a service stream.
  • Time Sensitive Network can be applied to professional audio and video, automobile control, and industrial fields.
  • the corresponding service streams usually include control signaling, motion control, audio stream, video stream, etc.
  • Priority service flow currently 5G communication technology is gradually being applied to TSN, and the bearer network in 5G technology is used to realize the transmission of service flows between multiple TSNs.
  • the bearer network mainly adopts Flexible Ethernet (Flexible Ethernet, FlexE) as the interface technology to support the transmission of service streams.
  • FlexE Flexible Ethernet
  • the current FlexE physical layer is usually used to transmit different types of high-priority service streams for the same interface, resulting in high
  • the interference between priority service flows causes jitter to increase, and service flows of different levels are scheduled and sent in a circular queue forwarding manner, which will also increase the transmission delay of high priority service flows. Therefore, the current FlexE service flow transmission The method does not meet the user's communication needs.
  • the present disclosure provides a service flow transmission method, device, equipment and storage medium, so as to avoid mutual interference between high-priority service flows.
  • the embodiment of the present disclosure provides a service flow transmission method, including: obtaining the service flow; and transmitting through different flexible Ethernet FlexE outgoing interfaces according to the priority of the service flow.
  • the embodiment of the present disclosure provides a service flow transmission device, which includes: a service flow acquisition module, which is set to obtain a service flow; transmission.
  • the embodiments of the present disclosure provide a device, including: one or more processors; a storage device, configured to store one or more programs. When one or more programs are executed by one or more processors, one or more Two processors implement the methods in the embodiments of the present disclosure.
  • the embodiment of the present disclosure provides a computer-readable storage medium on which a computer program is stored, and when the program is executed by a processor, the method in the embodiment of the present disclosure is implemented.
  • the service flow transmission method, device, equipment, and storage medium provided by the embodiments of the present disclosure determine the priority of the service flow, and perform transmission through different FlexE outbound interfaces according to the priority of the service flow, thereby avoiding the problem of the service flow. Mutual interference between.
  • Figure 1 is a schematic diagram of an application scenario provided by an embodiment of the present disclosure
  • FIG. 2 is a schematic diagram of the architecture of a flexible Ethernet FlexE according to an embodiment of the present disclosure
  • Fig. 3 is a flowchart of a service flow transmission method according to an embodiment of the present disclosure
  • FIG. 4 is a schematic diagram of static creation of an outbound interface according to an embodiment of the present disclosure
  • FIG. 5 is a schematic diagram of another static creation of an outbound interface according to an embodiment of the present disclosure.
  • Fig. 6 is a flowchart of a service flow transmission method according to an embodiment of the present disclosure.
  • FIG. 7 is a schematic diagram of the principle of priority scheduling transmission according to an embodiment of the present disclosure.
  • FIG. 8 is a schematic structural diagram of a service flow transmission device according to an embodiment of the present disclosure.
  • Fig. 9 is a schematic diagram of the structure of the device provided by the present disclosure.
  • FIG 1 is a schematic diagram of the application scenario of this embodiment, which mainly involves 5G supporting Time Sensitive Network (TSN) service networking, so as to realize the information transmission of two TSN network systems.
  • TSN Time Sensitive Network
  • the bearer network (BN-Bearer Network, BN) is applied to the flexible Ethernet (Flexible Ethernet, FlexE) architecture in Figure 2, and realizes the transmission of the service flow in the TSN through the arrangement and scheduling of the FlexE.
  • BN-Bearer Network, BN The bearer network
  • FlexE Flexible Ethernet
  • FIG. 3 it is a schematic flowchart of a service flow transmission method provided by the present disclosure. This method can be applied to the situation that the service flows of different levels are scheduled and transmitted through different outgoing interfaces.
  • the method can be executed by the service flow transmission device provided in the present disclosure, and the service flow transmission device is implemented by software and/or hardware, and is integrated on a device.
  • a flow chart of a method for transmitting a service flow may include:
  • Step 101 Obtain a service flow.
  • the service stream in the TSN network is obtained through the FlexE inbound interface in the bearer network.
  • the service stream types in this embodiment can include control signaling, motion control, audio stream, and video stream.
  • the specific type of service flow is also limited in this embodiment.
  • Step 102 Transmission is performed through different flexible Ethernet FlexE outgoing interfaces according to the priority of the service flow.
  • transmitting through different flexible Ethernet FlexE outbound interfaces according to the priority of the service flow may include: determining the first sub-service flow of the high-priority service in the priority of the service flow; The service flow is transmitted through different flexible Ethernet FlexE outgoing interfaces.
  • each sub-service flow can be divided into different levels due to different functions, and the priority threshold can be determined to be 3, and the service flow The sub-service flow above the priority threshold is classified as the first sub-service flow.
  • the level of the sub-service flow whose type is the control instruction is 4, and the level of the sub-service flow whose type is the audio stream is 5.
  • Both of the two sub-service flows are classified as the first sub-service flow. From this, it can be concluded that the number of the first sub-service flow in the embodiment of the present disclosure can be multiple, and the embodiment of the present disclosure does not limit the number of the first sub-service flow. The specific number.
  • the high-priority services in this embodiment can also be specified in advance.
  • the services that need to be executed first in the execution process are called high-priority services, and the types of high-priority services may include multiple types of services.
  • the priority of the service flow is compared with the known types of high-priority services, and the priority service flow belonging to the high-priority service is called the first sub-service flow.
  • transmitting through different flexible Ethernet FlexE outbound interfaces according to the priority of the service flow may also include: determining the second sub-service flow whose priority is not high-priority in the service flow; The stream is transmitted through the outgoing interface of the first sub-service stream in the same direction.
  • the bearer capacity of each outbound interface is greater than the sum of the bandwidth requirement of the first sub-service flow and the bandwidth requirement of the second sub-service flow to be transmitted.
  • the sub-service flow that is lower than the priority threshold in the service flow can be classified as the second sub-service flow. For example, if the level of the sub-service flow whose type is BE flow is 2, then The sub-service flow is classified as the second sub-service flow, and the second sub-service flow is transmitted through the outgoing interface of the first sub-service flow in the same direction.
  • the priority of the first sub-service flow in this embodiment is higher than the priority of the second sub-service flow. Therefore, the first sub-service flow may also be collectively referred to as a high-priority service flow, and the second sub-service flow may be referred to as a high priority service flow. The sub-service flows are collectively referred to as low-priority service flows.
  • the outbound interface needs to be created according to the first sub-service flow, that is, the number of outbound interfaces created needs to be the same as the number of the first sub-service.
  • the outlet creation methods in this embodiment include static creation and Dynamically created.
  • FIG. 4 is a schematic diagram of static creation of an outbound interface in an embodiment of the present disclosure, where it is determined that the number of first sub-service flows is four, corresponding to priority 7, and the bandwidth requirement is 4G.
  • Priority 6 bandwidth requirement is 3G
  • priority 5 bandwidth requirement is 2G
  • priority 4 bandwidth requirement is 2G
  • the controller sends configuration data to node 1 and node 2 of the bearer node, and is created at the FlexE physical layer
  • Each first sub-service flow uses one outgoing interface
  • the second sub-service flow transmitted in the same direction as each first sub-service flow, such as BE flow can use the same outgoing interface.
  • the first sub-service flow and the second sub-service flow can be simultaneously transmitted on the same outgoing interface, but the number of the first sub-service flow in each outgoing interface is one. And the carrying capacity of each outgoing interface is greater than the sum of the bandwidth demand of the first sub-service flow and the bandwidth demand of the second sub-service flow to be transmitted.
  • FIG. 5 is a schematic diagram of another static creation of an outbound interface in an embodiment of the present disclosure, in which it is determined that the number of the first sub-service flow is two, corresponding to priority 7, and the bandwidth requirement is 4G, priority 6, bandwidth demand is 8G, and the two first sub-service flows come from different nodes, the first sub-service flow corresponding to priority 7 passes from node 1 through node 3 to node 4, and priority 6 corresponds to The first sub-service flow from node 2 passes through node 3 to node 4.
  • the controller sends configuration data to node 1, node 3 and node 4 of the bearer node, and creates the first sub-service with priority 7 at the FlexE physical layer
  • the controller sends configuration data to node 2, node 3, and node 4 of the bearer node, and creates the second sub-service flow corresponding to the first sub-service flow with a priority of 6 at the FlexE physical layer.
  • Two outgoing interfaces, and the second sub-service flow transmitted in the same direction as each first sub-service flow, such as BE flow, can use the same outgoing interface, so the first sub-service flow and the second sub-service flow can be simultaneously transmitted on the same outgoing interface
  • the carrying capacity of each outgoing interface is greater than the sum of the bandwidth demand of the first sub-service flow and the bandwidth demand of the second sub-service flow to be transmitted.
  • the dynamic creation of the outbound interface in this embodiment refers to that the service flow is obtained in real time. According to the number of the first sub-service flow contained in the service flow, the first sub-service is dynamically created according to predetermined rules. Outgoing interface corresponding to the flow.
  • the service flow transmission method disclosed in the embodiment of the present disclosure determines the priority of the service flow, and performs transmission through different FlexE outgoing interfaces according to the priority of the service flow, thereby avoiding mutual interference between the service flows.
  • FIG. 6 shows a flowchart of a method for transmitting a service flow according to an embodiment of the present disclosure, and the method may include:
  • Step 201 Obtain a service flow.
  • Step 202 Determine the first sub-service flow in the service flow whose priority is higher than the priority threshold.
  • each first sub-service flow is transmitted through different FlexE outgoing interfaces in a preferential scheduling manner.
  • each outbound interface includes a high-priority queue group and a low-priority queue group; after creating an outbound interface according to the first sub-service flow, it also includes: saving each first sub-service flow in the corresponding outbound interface. In the high-priority queue group of the interface; the second sub-service flow transmitted in the same direction as each first sub-service flow is stored in the low-priority queue group of the corresponding outgoing interface.
  • transmitting each first sub-service flow through different FlexE outbound interfaces in a preferential scheduling manner may include: when it is determined that there are service flows in both the high-priority queue group and the low-priority queue group, The first sub-service flow in the high-priority queue group adopts the first-in-first-out (First Input First Output, FIFO) method for priority scheduling transmission; after determining that the scheduling of the high-priority queue group is completed, The second sub-service flow is scheduled for transmission.
  • FIFO First Input First Output
  • transmitting each first sub-service flow through different FlexE outgoing interfaces in a preferential scheduling manner may include: determining that there is no service flow in the high-priority queue group and there is service in the low-priority queue group During the flow, the second sub-service flow in the low-priority queue group is scheduled for transmission; when the second sub-service flow is scheduled for transmission, if a new first sub-service flow in the high-priority queue group joins, the second sub-service flow is interrupted. For the scheduled transmission of the sub-service flow, after the scheduled transmission of the new first sub-service flow is completed, the scheduled transmission of the second sub-service flow is restarted.
  • Each outgoing interface includes a high priority queue group (High Priority Queue Group, HPQG) and a low priority queue group (Low Priority Queue Group).
  • HPQG High Priority Queue Group
  • LPQG Priority Queue Group
  • HPQG is used to store each first sub-service flow
  • LPQG is used to store the second sub-service flow transmitted in the same direction with each first sub-service flow.
  • the scheduled transmission of the second sub-service flow After the scheduled transmission of the new first sub-service flow is completed, the scheduled transmission of the second second sub-service flow is continued, that is, the scheduling of the second sub-service flow by the new first sub-service flow
  • the transmission is preempted to achieve priority transmission of the service flow in the HPQG.
  • the service flow transmission method disclosed in the embodiment of the present disclosure determines the priority of the service flow, and performs transmission through different FlexE outgoing interfaces according to the priority of the service flow, thereby avoiding mutual interference between the service flows. And for the high-priority service flow, the priority scheduling method is adopted for transmission, so as to meet the transmission demand of low delay.
  • FIG. 8 shows a schematic structural diagram of a service flow transmission device according to an embodiment of the present disclosure.
  • the device includes: a service flow acquisition module 81, which is configured to acquire a service flow; and a service flow transmission module 82 which is configured according to The priority of the service flow is transmitted through different flexible Ethernet FlexE outgoing interfaces.
  • the service flow transmission device provided in this embodiment is set to implement the service flow transmission method.
  • the implementation principles and technical effects of the service flow transmission device provided in this embodiment are similar to the service flow transmission method of the present disclosure, and will not be repeated here. .
  • the service flow transmission module is specifically set to: determine the first sub-service flow of the high-priority service in the priority of the service flow; perform each first sub-service flow through different flexible Ethernet FlexE outgoing interfaces transmission.
  • the service flow transmission module is specifically set to: determine the second sub-service flow whose priority is not high-priority in the service flow; transmit the second sub-service flow through the output of the first sub-service flow in the same direction. Interface for transmission.
  • the carrying capacity of each outbound interface is greater than the sum of the bandwidth requirement of the first sub-service flow and the bandwidth requirement of the second sub-service flow to be transmitted.
  • the service flow transmission module executes the transmission of each first sub-service flow through different flexible Ethernet FlexE outgoing interfaces, it is specifically set to: pass each first sub-service flow in a preferential scheduling manner. Different FlexE outgoing interfaces for transmission.
  • each outbound interface includes a high-priority queue group and a low-priority queue group; the device further includes: a service flow storage module, configured to store each first sub-service flow in the high priority of the corresponding outbound interface. In the priority queue group; the second sub-service flow transmitted in the same direction as each first sub-service flow is stored in the low-priority queue group of the corresponding outgoing interface.
  • the service flow transmission module when the service flow transmission module performs priority scheduling for each first sub-service flow to be transmitted through different FlexE outgoing interfaces, it is specifically set as follows: When determining the high priority queue group and the low priority queue When there are service flows in the group at the same time, the first sub-service flow in the high-priority queue group is first-in-first-out FIFO for priority scheduling transmission; after determining that the scheduling of the high-priority queue group is completed, the low-priority queue group is The second sub-service flow is scheduled for transmission.
  • the service flow transmission module performs priority scheduling for each first sub-service flow to be transmitted through different FlexE outgoing interfaces, it is specifically set as follows: when it is determined that there is no service flow in the high-priority queue group When there is a service flow in the low-priority queue group, the second sub-service flow in the low-priority queue group is scheduled for transmission; when the second sub-service flow is scheduled for transmission, there is a new first sub-service in the high-priority queue group.
  • the service flow joins the scheduled transmission of the second sub-service flow is interrupted, and after the scheduled transmission of the new first sub-service flow is completed, the scheduled transmission of the second sub-service flow is restarted.
  • FIG. 9 a schematic structural diagram of a device provided by an embodiment of the present disclosure.
  • the device provided by the present disclosure includes: one or more processors 91 and a storage device 92; the processor 91 of the device may be one or more One, one processor 91 is taken as an example in FIG. 9; the storage device 92 is configured to store one or more programs; one or more programs are executed by one or more processors 91, so that one or more processors 91 implement The service flow transmission method in the embodiment of the present disclosure.
  • the processor 91 and the storage device 92 in the device may be connected through a bus or other methods.
  • the connection through a bus is taken as an example.
  • the storage device 92 can be configured to store software programs, computer-executable programs, and modules, such as program instructions/modules corresponding to the scheduling method of the super cell in the embodiment of the present disclosure.
  • the storage device 92 may include a program storage area and a data storage area.
  • the program storage area may store an operating system and an application program required for at least one function; the data storage area may store data created according to the use of the device, and the like.
  • the storage device 92 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, or other non-volatile solid-state storage devices.
  • the storage device 92 may further include a memory provided remotely with respect to the processor 91, and these remote memories may be connected to the device through a network.
  • networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.
  • the present disclosure provides a storage medium on which a computer program is stored, and when the program is executed by a processor, the method for transmitting any service flow in the embodiments of the present disclosure is realized.
  • the transmission method of the service flow includes: obtaining the service flow; transmitting through different flexible Ethernet FlexE outgoing interfaces according to the priority of the service flow.
  • the various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof.
  • some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software that may be executed by a controller, microprocessor, or other computing device, although the present disclosure is not limited thereto.
  • Computer program instructions can be assembly instructions, Instruction Set Architecture (ISA) instructions, machine instructions, machine-related instructions, microcode, firmware instructions, state setting data, or written in any combination of one or more programming languages Source code or object code.
  • ISA Instruction Set Architecture
  • the block diagram of any logic flow in the drawings of the present disclosure may represent program steps, or may represent interconnected logic circuits, modules, and functions, or may represent a combination of program steps and logic circuits, modules, and functions.
  • the computer program can be stored on the memory.
  • the memory can be of any type suitable for the local technical environment and can be implemented using any suitable data storage technology, such as but not limited to read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), optical Memory devices and systems (Digital Video Disc (DVD) or Compact Disk (CD)), etc.
  • Computer-readable media may include non-transitory storage media.
  • the data processor can be any type suitable for the local technical environment, such as but not limited to general-purpose computers, special-purpose computers, microprocessors, digital signal processors (Digital Signal Processing, DSP), application specific integrated circuits (ASICs) ), programmable logic devices (Field-Programmable Gate Array, FGPA), and processors based on multi-core processor architecture.
  • DSP Digital Signal Processing
  • ASICs application specific integrated circuits
  • FGPA programmable logic devices

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本公开公开了一种业务流的传输方法、装置、设备及存储介质，业务流的传输方法，包括：获取业务流；根据业务流的优先级通过不同的灵活以太网FlexE出接口进行传输。通过确定业务流的优先级，并根据业务流的优先级通过不同的FlexE出接口进行传输，从而避免了业务流之间的相互干扰。

Description

一种业务流的传输方法、装置、设备及存储介质 技术领域
本公开实施例涉及通讯技术领域，尤其涉及一种业务流的传输方法、装置、设备及存储介质。
背景技术
时间敏感性网络(Time Sensitive Network，TSN)可适用于专业音视频、汽车控制和工业领域，其所对应的业务流通常包括控制信令、运动控制、音频流、视频流等多种不同的高优先级业务流，目前5G通信技术也在逐渐应用到TSN中，并采用5G技术中的承载网来实现多个TSN之间业务流的传输。
目前承载网主要采用灵活以太网(Flexible Ethernet，FlexE)作为接口技术以支持业务流的传输，而目前的FlexE物理层针对同一接口通常会用于传输不同类型的高优先级业务流，从而造成高优先级业务流之间的干扰，导致抖动增加，并且不同等级的业务流按照循环队列转发的方式进行调度发送，还会增加高优先级业务流的传输时延，因此目前的FlexE的业务流传输方式并不能满足用户的通信需求。
发明内容
本公开提供了一种业务流的传输方法、装置、设备及存储介质，以实现避免高优先级业务流之间的相互干扰。
本公开实施例提供了一种业务流的传输方法，包括：获取业务流；根据业务流的优先级通过不同的灵活以太网FlexE出接口进行传输。
本公开实施例提供了一种业务流的传输装置，包括：业务流获取模块， 设置为获取业务流；业务流传输模块，设置为根据业务流的优先级通过不同的灵活以太网FlexE出接口进行传输。
本公开实施例提供了一种设备，包括：一个或多个处理器；存储装置，设置为存储一个或多个程序，当一个或多个程序被一个或多个处理器执行，使得一个或多个处理器实现本公开实施例中的方法。
本公开实施例提供了一种计算机可读存储介质，其上存储有计算机程序，该程序被处理器执行时实现本公开实施例中的方法。
本公开实施例所提供的业务流的传输方法、装置、设备及存储介质，通过确定业务流的优先级，并根据业务流的优先级通过不同的FlexE出接口进行传输，从而避免了业务流之间的相互干扰。
附图说明
图1是本公开实施例提供的应用场景示意图；
图2是本公开实施例的灵活以太网FlexE的架构示意图；
图3是本公开实施例的业务流的传输方法的流程图；
图4是本公开实施例的一种出接口静态创建示意图；
图5是本公开实施例的另一种出接口静态创建示意图；
图6是本公开实施例的业务流的传输方法的流程图；
图7是本公开实施例的优先调度传输的原理示意图；
图8是本公开实施例的业务流的传输装置的结构示意图；
图9是本公开提供的设备的结构示意图。
具体实施方式
为使本公开的目的、技术方案和优点更加清楚明白，下文中将结合附 图对本公开的实施例进行详细说明。需要说明的是，在不冲突的情况下，本公开中的实施例及实施例中的特征可以相互任意组合。
如图1所示是本实施例的应用场景示意图，主要涉及5G支持时间敏感型网络(Time Sensitive Network,TSN)业务组网，从而实现两个TSN网络系统的信息传输，其中，图1中的承载网(BN-Bearer Network，BN)应用到了图2中的灵活以太网(Flexible Ethernet，FlexE)的架构，并通过对FlexE的安排、调度实现对TSN中业务流的传输。
如图3所示，为本公开提供的一种业务流的传输方法的流程示意图。该方法可以适用于对不同等级的业务流通过不同的出接口进行调度传输的情况。该方法可以由本公开提供的业务流的传输装置执行，该业务流的传输装置由软件和/或硬件实现，并集成在一个设备上。
如图3所示，本公开实施方式提供的一种业务流的传输方法的流程图，该方法可以包括：
步骤101，获取业务流。
具体的说，在本实施方式中，会通过承载网中的FlexE入接口获取TSN网络中的业务流，本实施方式中的业务流的类型可以包括控制信令、运动控制、音频流、视频流和标准的因特网服务模式(Best Effort，BE)流，本实施方式中并限定业务流的具体类型。
步骤102，根据业务流的优先级通过不同的灵活以太网FlexE出接口进行传输。
在一个示例中，根据业务流的优先级通过不同的灵活以太网FlexE出接口进行传输，可以包括：确定业务流中优先级属于高优先级业务的第一子业务流；将每一个第一子业务流通过不同的灵活以太网FlexE出接口进行传输。
具体的说，在本实施方式中由于业务流中可以包括多种类型的子业务流，每一个子业务流由于不同的功能可以分为不同的等级，可以确定优先级阈值为3，将业务流中高于优先级阈值的子业务流归类为第一子业务流， 例如，类型为控制指令的子业务流的等级为4，类型为音频流的子业务流的等级为5，则可以将上述两个子业务流都归类为第一子业务流，由此可以得出本公开实施方式中第一子业务流的数量可以为多个，本公开实施方式中并不限定第一子业务流的具体数量。
需要说明的是，本实施方式中的高优先级业务还可以是提前指定的，例如，将在执行过程中需要优先执行的业务称为高优先级业务，并且高优先级业务的种类可以包括多个，将业务流的优先级与已知类型的高优先级业务进行对比，将属于高优先级业务的优先级业务流称为第一子业务流。
在一个示例中，根据业务流的优先级通过不同的灵活以太网FlexE出接口进行传输，还可以包括：确定业务流中优先级不属于高优先级的第二子业务流；将第二子业务流通过传输同向的第一子业务流的出接口进行传输。
在一个示例中，每一个出接口的承载容量大于传输的第一子业务流的带宽需求和第二子业务流的带宽需求之和。
具体的说，本实施方式中，将业务流中低于优先级阈值的子业务流可以归类为第二子业务流，例如，类型为BE流的子业务流的等级为2，则可以将该子业务流归类为第二子业务流，并且是将第二子业务流通过传输同向的第一子业务流的出接口进行传输。
需要说明的是，本实施方式中的第一子业务流的优先级都高于第二子业务流的优先级，因此还可以将第一子业务流统称为高优先级业务流，将第二子业务流统称为低优先级业务流。
需要说明的是，本实施方式中需要根据第一子业务流创建出接口，即所创建的出接口的数量需要与第一子业务的数量相同，本实施方式中的出口创建方式包括静态创建和动态创建。
在一个具体实现中，如图4所示为本公开实施例中的一种出接口静态创建示意图，其中，确定第一子业务流的数量有四个，对应优先级7，带宽需求为4G,优先级6,带宽需求为3G，优先级5，带宽需求为2G，以及 优先级4，带宽需求为2G，通过控制器向承载节点的节点1和节点2下发配置数据，在FlexE物理层创建4个对应的出接口，每一个第一子业务流分别使用一个出接口，并且与每一个第一子业务流同向传输的第二子业务流，例如BE流，可以使用同一个出接口，因此在同一个出接口中可以同时传输第一子业务流和第二子业务流，但其中每一个出接口中第一子业务流的数量为一个。并且每一个出接口的承载容量大于传输的第一子业务流的带宽需求和第二子业务流的带宽需求之和。
在另一个具体实现中，如图5所示为本公开实施例中的另一种出接口静态创建示意图，其中，确定第一子业务流的数量为两个，对应优先级7，带宽需求为4G，优先级6，带宽需求为8G，并且两个第一子业务流分别来自不同的节点，优先级7对应的第一子业务流从自节点1经过节点3到节点4，优先级6对应的第一子业务流从节点2经过节点3到节点4，通过控制器向承载节点的节点1、节点3和节点4下发配置数据，在FlexE物理层创建优先级为7的第一子业务流所对应的第一个出接口，通过控制器向承载节点的节点2、节点3和节点4下发配置数据，在FlexE物理层创建优先级为6的第一子业务流所对应的第二个出接口，并且与每一个第一子业务流同向传输的第二子业务流，例如BE流，可以使用同一个出接口，因此在同一个出接口中可以同时传输第一子业务流和第二子业务流，但其中每一个出接口中第一子业务流的数量为一。并且每一个出接口的承载容量大于传输的第一子业务流的带宽需求和第二子业务流的带宽需求之和。
需要说明的是，本实施方式中的动态创建出接口，指的是业务流是实时获取的，根据业务流中所包含的第一子业务流的数量，根据预定规则动态创建与第一子业务流对应的出接口。
本公开实施例公开的业务流的传输方法，通过确定业务流的优先级，并根据业务流的优先级通过不同的FlexE出接口进行传输，从而避免了业务流之间的相互干扰。
图6所示出本公开实施例的业务流的传输方法的流程图，该方法可以包括：
步骤201，获取业务流。
步骤202，确定业务流中优先级高于优先级阈值的第一子业务流。
步骤203，将每一个第一子业务流采用优先调度的方式通过不同的FlexE出接口进行传输。
在一个示例中，每一个出接口分别包括高优先级队列组和低优先级队列组；在根据第一子业务流创建出接口之后还包括：将每一个第一子业务流保存在所对应出接口的高优先级队列组中；将与每一个第一子业务流同向传输的第二子业务流，保存在所对应出接口的低优先级队列组中。
在一个示例中，将每一个第一子业务流采用优先调度的方式通过不同的FlexE出接口进行传输，可以包括：在确定高优先级队列组和低优先级队列组同时存在业务流时，对高优先级队列组中的第一子业务流采用先入先出(First Input First Output，FIFO)的方式进行优先调度传输；在确定高优先级队列组调度完成后，对低优先级队列组中的第二子业务流进行调度传输。
在一个示例中，将每一个第一子业务流采用优先调度的方式通过不同的FlexE出接口进行传输，可以包括：在确定高优先级队列组不存在业务流而低优先级队列组中存在业务流时，对低优先级队列组中的第二子业务流进行调度传输；在第二子业务流进行调度传输时，高优先级队列组中有新第一子业务流加入，则中断第二子业务流的调度传输，在完成新第一子业务流的调度传输后，重新启动第二子业务流的调度传输。
具体的说，如图7所示为本公开实施方式中优先调度传输的原理示意图，针对每一个出接口分别包括高优先级队列组(High Priority Queue Group，HPQG)和低优先级队列组(Low Priority Queue Group，LPQG),其中，HPQG用于保存每一个第一子业务流，LPQG用于保存与每一个第 一子业务流同向传输的第二子业务流。在HPQG中原有的第一子业务流已经调度传输完成的情况下，确定HPQG中不存在业务流而LPQG中存在业务流时，如图7中所示确定LPQG中包括三种第二子业务流，在按照顺序由上到下依次进行调度传输的过程中，当对第二个第二子业务流进行调度传输时，确定HPQG中有新第一子业务流加入，则中断当前第二个第二子业务流的调度传输，在完成新第一子业务流的调度传输后，再继续第二个第二子业务流的调度传输，即新第一子业务流对第二子业务流的调度传输进行抢占，以实现优先发送HPQG中的业务流。
本公开实施例公开的业务流的传输方法，通过确定业务流的优先级，并根据业务流的优先级通过不同的FlexE出接口进行传输，从而避免了业务流之间的相互干扰。并且对于高优先级业务流采用优先调度的方式进行传输，从而满足低延时的传输需求。
图8所示出本公开实施例的业务流的传输装置的结构示意图，如图8所示，该装置包括：业务流获取模块81，设置为获取业务流；业务流传输模块82，设置为根据业务流的优先级通过不同的灵活以太网FlexE出接口进行传输。
本实施例提供的业务流的传输装置设置为实现业务流的传输方法，本实施例提供的业务流的传输装置实现原理和技术效果与本公开的业务流的传输方法类似，此处不再赘述。
在一个示例中，业务流传输模块，具体设置为：确定业务流中优先级属于高优先级业务的第一子业务流；将每一个第一子业务流通过不同的灵活以太网FlexE出接口进行传输。
在一个示例中，业务流传输模块，具体设置为：确定业务流中优先级不属于高优先级的第二子业务流；将第二子业务流通过传输同向的第一子业务流的出接口进行传输。
在一个示例中，每一个出接口的承载容量大于传输的第一子业务流的 带宽需求和第二子业务流的带宽需求之和。
在一个示例中，业务流传输模块在执行将每一个第一子业务流通过不同的灵活以太网FlexE出接口进行传输时，具体设置为：将每一个第一子业务流采用优先调度的方式通过不同的FlexE出接口进行传输。
在一个示例中，每一个出接口分别包括高优先级队列组和低优先级队列组；装置还包括：业务流存储模块，设置为将每一个第一子业务流保存在所对应出接口的高优先级队列组中；将与每一个第一子业务流同向传输的第二子业务流，保存在所对应出接口的低优先级队列组中。
在一个示例中，业务流传输模块在执行将每一个第一子业务流采用优先调度的方式通过不同的FlexE出接口进行传输时，具体设置为：在确定高优先级队列组和低优先级队列组同时存在业务流时，对高优先级队列组中的第一子业务流采用先入先出FIFO的方式进行优先调度传输；在确定高优先级队列组调度完成后，对低优先级队列组中的第二子业务流进行调度传输。
在一个示例中，业务流传输模块在执行将每一个第一子业务流采用优先调度的方式通过不同的FlexE出接口进行传输时，具体设置为：在确定高优先级队列组不存在业务流而低优先级队列组中存在业务流时，对低优先级队列组中的第二子业务流进行调度传输；在第二子业务流进行调度传输时，高优先级队列组中有新第一子业务流加入，则中断第二子业务流的调度传输，在完成新第一子业务流的调度传输后，重新启动第二子业务流的调度传输。
如图9所示，本公开实施方式提供的一种设备的结构示意图，本公开提供的设备，包括：一个或多个处理器91和存储装置92；该设备的处理器91可以是一个或多个，图9中以一个处理器91为例；存储装置92设置为存储一个或多个程序；一个或多个程序被一个或多个处理器91执行，使得一个或多个处理器91实现如本公开实施例中的业务流的传输方法。
设备中的处理器91、存储装置92可以通过总线或其他方式连接，图9中以通过总线连接为例。
存储装置92作为一种计算机可读存储介质，可设置为存储软件程序、计算机可执行程序以及模块，如本公开实施例超级小区的调度方法对应的程序指令/模块。存储装置92可包括存储程序区和存储数据区，其中，存储程序区可存储操作系统、至少一个功能所需的应用程序；存储数据区可存储根据设备的使用所创建的数据等。此外，存储装置92可以包括高速随机存取存储器，还可以包括非易失性存储器，例如至少一个磁盘存储器件、闪存器件、或其他非易失性固态存储器件。在一些实例中，存储装置92可进一步包括相对于处理器91远程设置的存储器，这些远程存储器可以通过网络连接至设备。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
本公开提供了一种存储介质，其上存储有计算机程序，程序被处理器执行时实现本公开实施例中任一的业务流的传输方法。
其中，业务流的传输方法包括：获取业务流；根据业务流的优先级通过不同的灵活以太网FlexE出接口进行传输。
以上所述，仅为本公开的示例性实施例而已，并非用于限定本公开的保护范围。
一般来说，本公开的多种实施例可以在硬件或专用电路、软件、逻辑或其任何组合中实现。例如，一些方面可以被实现在硬件中，而其它方面可以被实现在可以被控制器、微处理器或其它计算装置执行的固件或软件中，尽管本公开不限于此。
本公开的实施例可以通过移动装置的数据处理器执行计算机程序指令来实现，例如在处理器实体中，或者通过硬件，或者通过软件和硬件的组合。计算机程序指令可以是汇编指令、指令集架构(Instruction Set Architecture，ISA)指令、机器指令、机器相关指令、微代码、固件指令、状态设置数据、或者以一种或多种编程语言的任意组合编写的源代码或目 标代码。
本公开附图中的任何逻辑流程的框图可以表示程序步骤，或者可以表示相互连接的逻辑电路、模块和功能，或者可以表示程序步骤与逻辑电路、模块和功能的组合。计算机程序可以存储在存储器上。存储器可以具有任何适合于本地技术环境的类型并且可以使用任何适合的数据存储技术实现，例如但不限于只读存储器(Read-Only Memory，ROM)、随机访问存储器(Random Access Memory，RAM)、光存储器装置和系统(数码多功能光碟(Digital Video Disc，DVD)或光盘(Compact Disk，CD))等。计算机可读介质可以包括非瞬时性存储介质。数据处理器可以是任何适合于本地技术环境的类型，例如但不限于通用计算机、专用计算机、微处理器、数字信号处理器(Digital Signal Processing，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、可编程逻辑器件(Field-Programmable Gate Array，FGPA)以及基于多核处理器架构的处理器。
通过示范性和非限制性的示例，上文已提供了对本公开的示范实施例的详细描述。但结合附图和权利要求来考虑，对以上实施例的多种修改和调整对本领域技术人员来说是显而易见的，但不偏离本公开的范围。因此，本公开的恰当范围将根据权利要求确定。

Claims (11)

  1. 一种业务流的传输方法，包括：
    获取业务流；
    根据业务流的优先级通过不同的灵活以太网FlexE出接口进行传输。
  2. 根据权利要求1所述的方法，其中，所述根据业务流的优先级通过不同的灵活以太网FlexE出接口进行传输，包括：
    确定所述业务流中优先级属于高优先级业务的第一子业务流；
    将每一个所述第一子业务流通过不同的灵活以太网FlexE出接口进行传输。
  3. 根据权利要求2所述的方法，其中，所述根据业务流的优先级通过不同的灵活以太网FlexE出接口进行传输，还包括：
    确定所述业务流中优先级不属于高优先级的第二子业务流；
    将所述第二子业务流通过传输同向的第一子业务流的出接口进行传输。
  4. 根据权利要求3所述的方法，其中，每一个所述出接口的承载容量大于传输的第一子业务流的带宽需求和第二子业务流的带宽需求之和。
  5. 根据权利要求4所述的方法，其中，所述将每一个所述第一子业务流通过不同的灵活以太网FlexE出接口进行传输，包括：
    将每一个所述第一子业务流采用优先调度的方式通过不同的FlexE出接口进行传输。
  6. 根据权利要求5所述的方法，其中，每一个所述出接口分别包括高优先级队列组和低优先级队列组；
    所述方法还包括：
    将每一个所述第一子业务流保存在所对应出接口的所述高优先级队列组中；
    将与每一个所述第一子业务流同向传输的所述第二子业务流，保存在所对应出接口的所述低优先级队列组中。
  7. 根据权利要求6所述的方法，其中，所述将每一个所述第一子业务流采用优先调度的方式通过不同的FlexE出接口进行传输，包括：
    在确定所述高优先级队列组和所述低优先级队列组同时存在业务流时，对所述高优先级队列组中的所述第一子业务流采用先入先出FIFO的方式进行优先调度传输；
    在确定所述高优先级队列组调度完成后，对所述低优先级队列组中的所述第二子业务流进行调度传输。
  8. 根据权利要求6所述的方法，其中，所述将每一个所述第一子业务流采用优先调度的方式通过不同的FlexE出接口进行传输，包括：
    在确定所述高优先级队列组不存在业务流而所述低优先级队列组中存在业务流时，对所述低优先级队列组中的所述第二子业务流进行调度传输；
    在所述第二子业务流进行调度传输时，所述高优先级队列组中有新第一子业务流加入，则中断所述第二子业务流的调度传输，在完成所述新第一子业务流的调度传输后，重新启动所述第二子业务流的调度传输。
  9. 一种业务流的传输装置，包括：
    业务流获取模块，设置为获取业务流；
    业务流传输模块，设置为根据业务流的优先级通过不同的灵活以太网FlexE出接口进行传输。
  10. 一种设备，所述设备包括：
    一个或多个处理器；
    存储装置，设置为存储一个或多个程序，
    当所述一个或多个程序被所述一个或多个处理器执行，使得所述一个或多个处理器实现如权利要求1至8中任一所述的方法。
  11. 一种计算机可读存储介质，其上存储有计算机程序，该程序被处理器执行时实现如权利要求1至8中任一所述的方法。
PCT/CN2020/124143 2020-04-08 2020-10-27 一种业务流的传输方法、装置、设备及存储介质 Ceased WO2021203680A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US17/802,805 US12224943B2 (en) 2020-04-08 2020-10-27 Service flow transmission method and apparatus, device, and storage medium
EP20930547.3A EP4135225A4 (en) 2020-04-08 2020-10-27 METHOD AND APPARATUS FOR TRANSMITTING SERVICE FLOWS AND DEVICE AND STORAGE MEDIUM

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010268167.1 2020-04-08
CN202010268167.1A CN112822125B (zh) 2020-04-08 2020-04-08 一种业务流的传输方法、装置、设备及存储介质

Publications (1)

Publication Number Publication Date
WO2021203680A1 true WO2021203680A1 (zh) 2021-10-14

Family

ID=75854355

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/124143 Ceased WO2021203680A1 (zh) 2020-04-08 2020-10-27 一种业务流的传输方法、装置、设备及存储介质

Country Status (4)

Country Link
US (1) US12224943B2 (zh)
EP (1) EP4135225A4 (zh)
CN (1) CN112822125B (zh)
WO (1) WO2021203680A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112822125B (zh) * 2020-04-08 2023-08-01 中兴通讯股份有限公司 一种业务流的传输方法、装置、设备及存储介质
CN115022901B (zh) * 2022-05-30 2025-05-06 重庆邮电大学 面向5g-tsn融合的5g侧业务流资源配置方法
WO2025112019A1 (zh) * 2023-11-30 2025-06-05 华为技术有限公司 一种调度方法和通信装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108243120A (zh) * 2016-12-26 2018-07-03 北京华为数字技术有限公司 基于灵活以太网的业务流传输方法、装置和通信系统
CN108924058A (zh) * 2018-08-30 2018-11-30 中国联合网络通信集团有限公司 业务流量传输方法及装置
CN108988977A (zh) * 2017-05-31 2018-12-11 中兴通讯股份有限公司 一种灵活以太网协议中传递业务流的方法、装置和系统
CN109981208A (zh) * 2017-12-27 2019-07-05 华为技术有限公司 基于灵活以太网FlexE传输业务流的方法和装置
US20190349282A1 (en) * 2015-06-30 2019-11-14 Ciena Corporation Flexible Ethernet Operations, Administration, and Maintenance systems and methods

Family Cites Families (32)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CA2266262A1 (en) * 1999-03-23 2000-09-23 Newbridge Networks Corporation Method and apparatus for prioritized release of connections in a communications network
WO2003096242A1 (en) * 2002-05-07 2003-11-20 British Telecommunications Public Limited Company Method and apparatus for selecting user policies
US20080075003A1 (en) * 2006-09-21 2008-03-27 Futurewei Technologies, Inc. Method and system for admission and congestion control of network communication traffic
WO2013097234A1 (zh) * 2011-12-31 2013-07-04 华为技术有限公司 处理业务的方法和系统
CN103260145B (zh) * 2013-04-18 2016-07-20 中国科学院计算技术研究所 基于PMIPv6域内业务流切换的移动管理方法及系统
WO2016010526A1 (en) * 2014-07-15 2016-01-21 Hitachi, Ltd. Avoiding congestion in a cellular network via preemptive traffic management
US9800361B2 (en) * 2015-06-30 2017-10-24 Ciena Corporation Flexible ethernet switching systems and methods
US11277217B2 (en) * 2015-06-30 2022-03-15 Ciena Corporation Flexible Ethernet switching systems and methods
US10193688B2 (en) * 2015-12-11 2019-01-29 Ciena Corporation Flexible Ethernet encryption systems and methods
US10979506B2 (en) * 2016-09-19 2021-04-13 Westinghouse Air Brake Technologies Corporation Vehicle control system
US10505655B2 (en) * 2016-07-07 2019-12-10 Infinera Corp. FlexE GMPLS signaling extensions
US11843414B2 (en) * 2016-10-11 2023-12-12 Ciena Corporation FlexO/ZR subrating and partial survivability
CN108462646B (zh) * 2017-02-17 2020-08-25 华为技术有限公司 一种报文处理方法及装置
CN108965157B (zh) * 2017-05-19 2020-08-07 华为技术有限公司 数据传输方法、装置、设备及系统
CN113259309A (zh) * 2017-07-24 2021-08-13 华为技术有限公司 一种通信方法、设备及存储介质
CN109428840B (zh) * 2017-08-31 2022-05-06 华为技术有限公司 一种通信方法、设备及存储介质
CN109586864B (zh) * 2017-09-28 2021-01-15 华为技术有限公司 数据传输方法、装置及系统
CN114944910B (zh) 2017-10-30 2025-02-28 华为技术有限公司 时钟同步的方法和装置
CN109729025B (zh) * 2017-10-31 2021-04-20 华为技术有限公司 一种处理灵活以太网的数据的方法及相关设备
CN111788794B (zh) * 2017-12-22 2022-07-08 瑞典爱立信有限公司 用于配置灵活以太网节点的方法和设备
CN108988770A (zh) 2018-05-29 2018-12-11 苏州翠南电子科技有限公司 一种太能板防雨装置
US10880206B2 (en) * 2018-06-13 2020-12-29 Futurewei Technologies, Inc. Multipath selection system and method for datacenter-centric metro networks
CN110635931B (zh) * 2018-06-22 2021-05-14 华为技术有限公司 链路组配置方法和装置
CN110875796B (zh) * 2018-08-30 2021-02-23 华为技术有限公司 物理层端口通道化的方法和装置
CN111224746B (zh) * 2018-11-26 2022-06-24 华为技术有限公司 一种业务比特流处理方法及装置
CN111585779B (zh) * 2019-02-19 2021-10-15 华为技术有限公司 一种灵活以太网通信方法及网络设备
WO2020181462A1 (zh) * 2019-03-11 2020-09-17 华为技术有限公司 交互时钟同步报文的方法及装置
US12418353B2 (en) * 2019-08-12 2025-09-16 Telefonaktiebolaget Lm Ericsson (Publ) Transmitting and receiving synchronization data
JP7305882B2 (ja) * 2019-09-12 2023-07-10 華為技術有限公司 スロットネゴシエーション方法およびデバイス
CN116192726A (zh) * 2020-03-20 2023-05-30 华为技术有限公司 转发路径建立方法、装置以及计算机可读存储介质
CN113497728A (zh) * 2020-04-03 2021-10-12 华为技术有限公司 一种业务流调整方法和通信装置
CN112822125B (zh) * 2020-04-08 2023-08-01 中兴通讯股份有限公司 一种业务流的传输方法、装置、设备及存储介质

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190349282A1 (en) * 2015-06-30 2019-11-14 Ciena Corporation Flexible Ethernet Operations, Administration, and Maintenance systems and methods
CN108243120A (zh) * 2016-12-26 2018-07-03 北京华为数字技术有限公司 基于灵活以太网的业务流传输方法、装置和通信系统
CN108988977A (zh) * 2017-05-31 2018-12-11 中兴通讯股份有限公司 一种灵活以太网协议中传递业务流的方法、装置和系统
CN109981208A (zh) * 2017-12-27 2019-07-05 华为技术有限公司 基于灵活以太网FlexE传输业务流的方法和装置
CN108924058A (zh) * 2018-08-30 2018-11-30 中国联合网络通信集团有限公司 业务流量传输方法及装置

Non-Patent Citations (1)

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

Also Published As

Publication number Publication date
US20230088040A1 (en) 2023-03-23
EP4135225A4 (en) 2023-10-11
CN112822125B (zh) 2023-08-01
CN112822125A (zh) 2021-05-18
US12224943B2 (en) 2025-02-11
EP4135225A1 (en) 2023-02-15

Similar Documents

Publication Publication Date Title
US10705878B2 (en) Task allocating method and system capable of improving computational efficiency of a reconfigurable processing system
US11831554B2 (en) Packet forwarding method and apparatus, system, device, and storage medium
CN110691370A (zh) 一种数据传输方法、装置及系统
CN105979007A (zh) 加速资源处理方法、装置及网络功能虚拟化系统
CN112822125B (zh) 一种业务流的传输方法、装置、设备及存储介质
CN113934529B (zh) 多级别核心的任务调度方法、装置、系统和存储介质
WO2018013443A1 (en) Multiple core software forwarding
WO2020083301A1 (zh) 一种网络切片的方法、计算机设备及存储介质
WO2022032694A1 (en) Dynamic deterministic adjustment of bandwidth across multiple hubs with adaptive per-tunnel quality of service (qos)
CN115734281A (zh) 一种数据传输方法、装置及设备
WO2020062311A1 (zh) 一种内存访问方法及装置
KR102958074B1 (ko) 다운링크 송신 방법 및 통신 장치
WO2019152942A2 (en) Dynamic software architecture reconfiguration for converged cable access platform (ccap)
US9282041B2 (en) Congestion profiling of computer network devices
CN112804162B (zh) 一种调度方法、装置、终端设备和存储介质
CN106372013B (zh) 远程内存访问方法、装置和系统
US20210136007A1 (en) Method and apparatus for orchestrating resources in multi-access edge computing (mec) network
CN111756650A (zh) 一种数据处理方法、装置、运算芯片及存储介质
JP2011091711A (ja) ノード及び送信フレーム振り分け方法並びにプログラム
US12223068B2 (en) Secure computing control method, data packet processing method and device and system thereof
CN118233310A (zh) 一种调整小颗粒业务带宽的方法
CN110661731B (zh) 一种报文处理方法及其装置
WO2020108350A1 (zh) 一种会话管理设备及系统
CN114500581B (zh) 一种等延迟的分布式缓存以太网mac架构的实现方法
CN112788771A (zh) 数据传输方法、装置、相关设备及存储介质

Legal Events

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

Ref document number: 20930547

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2020930547

Country of ref document: EP

Effective date: 20221108