WO2020057534A1 - 业务处理方法和设备 - Google Patents
业务处理方法和设备 Download PDFInfo
- Publication number
- WO2020057534A1 WO2020057534A1 PCT/CN2019/106370 CN2019106370W WO2020057534A1 WO 2020057534 A1 WO2020057534 A1 WO 2020057534A1 CN 2019106370 W CN2019106370 W CN 2019106370W WO 2020057534 A1 WO2020057534 A1 WO 2020057534A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- code block
- service
- code
- traffic
- idle
- Prior art date
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/70—Admission control; Resource allocation
- H04L47/76—Admission control; Resource allocation using dynamic resource allocation, e.g. in-call renegotiation requested by the user or requested by the network in response to changing network conditions
-
- 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
-
- 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/525—Queue scheduling by attributing bandwidth to queues by redistribution of residual bandwidth
Definitions
- the present disclosure relates to the wireless field, and in particular, to a service processing method and device.
- FlexE Flexible Ethernet
- PHYs physical layers
- FlexE runs in a set 64B / 66B block calendar slot.
- the granularity of the calendar slot is 5G, and 20 slots can be divided in the 100G Ethernet physical layer (PHY).
- FlexE only defines the rates of 10 Gigabit Ethernet (GE), 40GE, n ⁇ 25GE, and has to adapt to the corresponding peak rate when allocating bandwidth to various services, that is, assigning fixed bandwidth resources to FlexE users . Then, when the services of these FlexE users have only lightweight data traffic or no data transmission at all, a large amount of bandwidth resources will be wasted due to fixed bandwidth allocation, resulting in low bandwidth utilization.
- GE Gigabit Ethernet
- 40GE Gigabit Ethernet
- n 25GE
- Service 1 and Service 2 are called “existing services” and represent a class of delay-sensitive services, such as Augmented Reality (AR) and virtual reality. (Virtual Reality, VR) and so on.
- Service 3 is called “new service”, which represents a burst bandwidth service with limited bandwidth transmitted by traditional store-and-forward methods, such as e-mail, web page, and so on.
- FlexE only defines 10GE, 40GE, and n ⁇ 25GE rates. When allocating bandwidth to various services, it has to adapt to the corresponding peak rate, that is, it allocates fixed bandwidth resources to FlexE users. Then, when the services of these FlexE users have only lightweight data traffic or no data transmission at all, a large amount of bandwidth resources will be wasted due to fixed bandwidth allocation, resulting in low bandwidth utilization.
- Some embodiments of the present disclosure provide a service processing method and device to solve the problem of low bandwidth utilization of the FlexE system.
- a service processing method applied to a transmitting end including: identifying an idle code block from a first code block traffic corresponding to a first service; Replacing the idle code block with a first code block used by a second service; mixing the second code block used by the first service and the first code block used by the second service in the first code block traffic Processing to obtain the second code block traffic; and sending the second code block traffic obtained by the hybrid processing to the receiving end.
- the idle code blocks include code blocks that have been allocated to the first service but are not used by the first service, and / or code blocks reserved for the second service.
- the second code block traffic includes a third code block, where the third code block is used to indicate positions of all idle code blocks in a row where the third code block is located.
- the encoding method of the third code block is a 64B / 66B encoding method
- the third code block includes mapping information of an idle code block, where the mapping information is used to indicate where the third code block is located. The position of all free code blocks of the row.
- another service processing method applied to a receiving end including: receiving a second code block traffic from a transmitting end; and dividing the second code block traffic into Sending the second service using the first code block to the corresponding first user; and sending the first service using the second code block in the second code block traffic to the corresponding second user; wherein the second service The code block traffic is obtained by mixing processing of the second code block used by the first service and the first code block used by the second service in the first code block traffic, and the first code block used by the second service And multiplexing positions of unused idle code blocks in the first code block traffic.
- the idle code blocks include: code blocks that have been allocated to the first service but are not used, and / or code blocks reserved for the second service.
- the second code block traffic includes a third code block, where the third code block is used to indicate positions of all idle code blocks in a row where the third code block is located.
- the encoding method of the third code block is a 64B / 66B encoding method
- the third code block includes mapping information of an idle code block, where the mapping information is used to indicate where the third code block is located. The position of all free code blocks of the row.
- a transmitting end including: a first transceiver and a first processor, wherein the first processor is configured to receive a first service corresponding to a first service. An idle code block is identified in the code block traffic; the first processor is further configured to replace the idle code block with a first code block used by a second service; and the first processor is further configured to replace the idle code block with the first code block. Performing a mixing process on the second code block used by the first service and the first code block used by the second service in the first code block traffic to obtain a second code block traffic; and the first transceiver, using Sending the second code block traffic obtained by the hybrid processing to the receiving end.
- the idle code blocks include code blocks that have been allocated to the first service but are not used by the first service, and / or code blocks reserved for the second service.
- the second code block traffic includes a third code block, where the third code block is used to indicate positions of all idle code blocks in a row where the third code block is located.
- the encoding method of the third code block is a 64B / 66B encoding method
- the third code block includes mapping information of an idle code block, where the mapping information is used to indicate where the third code block is located. The position of all free code blocks of the row.
- a receiving end including: a second transceiver and a second processor, wherein the second transceiver is configured to receive a second code block from a transmitting end Traffic; the second transceiver is further configured to send a second service using the first code block to the corresponding first user in the second code block traffic; and the second transceiver is further configured to send The first service using the second code block in the second code block traffic is sent to the corresponding second user; wherein the second code block traffic is the first service used by the first service in the first code block traffic. It is obtained by mixing the two code blocks and the first code block used by the second service, and the first code block used by the second service is multiplexed with the position of the unused idle code block in the first code block traffic.
- the idle code blocks include: code blocks that have been allocated to the first service but are not used, and / or code blocks reserved for the second service.
- the second code block traffic includes a third code block, where the third code block is used to indicate positions of all idle code blocks in a row where the third code block is located.
- the encoding method of the third code block is a 64B / 66B encoding method
- the third code block includes mapping information of an idle code block, where the mapping information is used to indicate where the third code block is located. The position of all free code blocks of the row.
- a communication device including a processor, a memory, and a computer program stored on the memory and executable on the processor. The steps of implementing the service processing method according to the first aspect when the processor is executed, or the steps of the service processing method according to the second aspect when executed by the processor.
- a computer-readable storage medium stores a computer program, and the computer program is implemented by a processor as implemented in the first aspect. The steps of the business processing method, or the steps of the business processing method according to the second aspect.
- the transmitting end replaces the idle code block in the first code block traffic corresponding to the first service with the first code block used by the second service, and replaces the second code block used by the first service with the first code block.
- the first code blocks used by the two services are mixed to obtain the second code block traffic, and the second code block traffic is sent to the receiving end.
- FIG. 1 is a block diagram of a related hard pipe-based FlexE multiplexing system
- FIG. 2 is a first flowchart of a service processing method according to some embodiments of the present disclosure
- FIG. 3 is a traffic schematic diagram of 20 code blocks / times according to some embodiments of the present disclosure
- FIG. 4 is a schematic diagram of a 64B / 66B code block type according to some embodiments of the present disclosure
- FIG. 6 is a second flowchart of a service processing method according to some embodiments of the present disclosure.
- FIG. 7 is a block diagram of a system for implementing hybrid multiplexing on FlexE according to some embodiments of the present disclosure
- FIG. 8 is a schematic structural diagram of a transmitting end according to some embodiments of the present disclosure.
- FIG. 9 is a schematic structural diagram of a receiving end according to some embodiments of the present disclosure.
- FIG. 10 is a schematic structural diagram of a communication device according to some embodiments of the present disclosure.
- LTE Long Time Evolution
- LTE-A LTE-Advanced
- CDMA Code Division Multiple Access
- TDMA Time Division Multiple Access
- FDMA Frequency Division Multiple Access
- OFDMA Orthogonal Frequency Division Multiple Access
- SC-FDMA Single Carrier Frequency Single-carrier
- 5G 5th-generation
- the terms “system” and “network” are often used interchangeably.
- the CDMA system can implement radio technologies such as CDMA2000, Universal Terrestrial Radio Access (UTRA) and the like.
- UTRA includes Wideband CDMA (Wideband Code Division Multiple Access) and other CDMA variants.
- the TDMA system can implement a radio technology such as Global System for Mobile (Communication, Global System for Mobile).
- OFDMA system can implement such as Ultra Mobile Broadband (UMB), Evolution-UTRA (Evolution-UTRA, E-UTRA), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, etc. Radio technology.
- UMB Ultra Mobile Broadband
- Evolution-UTRA Evolution-UTRA
- IEEE 802.11 Wi-Fi
- IEEE 802.16 WiMAX
- IEEE 802.20 Flash-OFDM
- Flash-OFDM Flash-OFDM
- LTE and more advanced LTE are new UMTS versions using E-UTRA.
- UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization named "3rd Generation Partnership Project” (3rd Generation Generation Partnership Project (3GPP)).
- CDMA2000 and UMB are described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2).
- the techniques described herein can be used for both the systems and radio technologies mentioned above as well as other systems and radio technologies.
- some embodiments of the present disclosure provide a service processing method, which is applied to a sending end.
- the specific steps are as follows:
- Step 201 identify an idle code block from the first code block traffic corresponding to the first service
- the first service is a type of delay-sensitive service, for example, service 1 and service 2 in FIG. 1, that is, “existing services”.
- the idle code blocks include: code blocks that have been allocated to the first service but are not used by the first service, and / or code blocks reserved for the second service.
- Step 202 Replace the idle code block with the first code block used by the second service.
- the second service is a burst bandwidth service with limited bandwidth transmitted by the traditional store and forward method, for example, service 3 in FIG. 1, that is, “new service”.
- Step 203 Mix the second code block used by the first service and the first code block used by the second service in the first code block traffic to obtain the second code block traffic;
- the second code block traffic further includes a third code block, where the third code block is used to indicate positions of all free code blocks in a row where the third code block is located.
- a flow of 20 code blocks / second is taken as an example, and each line has 20 code blocks.
- the code block marked “D / C” is the second code block;
- the code blocks marked with "+” are idle code blocks in the first code block traffic, wherein the code blocks marked with "*” indicate reserved code blocks for the second service, and the code blocks marked with "+” indicate allocated to Code blocks of the first service but not used by the first service; code blocks marked with "#” are third code blocks.
- the code blocks marked with "*" and "+” are filled with the first code blocks used by the second service.
- a 64B / 66B encoding method is shown, which can be used for encoding a third code block.
- Bits marked with diagonal lines in the D1, D2, and D3 areas in the figure can store mapping information of the free code blocks, and the mapping information of the free code blocks is used to indicate the positions of all the free code blocks in the row where the third code block is located.
- mapping information of an idle code block there is shown mapping information of an idle code block.
- the mapping information of each line can be placed in a code block marked with “#” in FIG. 3 to indicate the position of the free code block.
- each number corresponds to each code block in FIG. 3, "1" represents the second code block used by the first service, "0” represents the first code block used by the second service, and "x" represents allocated to Code blocks of the first service but not used by the first service.
- Step 204 Send the second code block traffic obtained by the hybrid processing to the receiving end.
- the sender replaces the idle code block in the first code block traffic corresponding to the first service with the first code block used by the second service, and replaces the second code block used by the first service with The first code block used by the second service is mixed and processed to obtain the second code block traffic, and the second code block traffic is sent to the receiving end.
- some embodiments of the present disclosure provide another service processing method, which is applied to a receiving end.
- the specific steps are as follows:
- Step 601 Receive second code block traffic from the transmitting end
- the second code block traffic is obtained by mixing processing of the second code block used by the first service and the first code block used by the second service in the first code block traffic, and the second service uses The position of the unused idle code block in the first code block traffic of the first code block is multiplexed.
- Step 602 Send the second service using the first code block in the second code block traffic to the corresponding first user;
- Step 603 Send the first service using the second code block in the second code block traffic to the corresponding second user.
- the sending end mixes the second code block used by the first service and the first code block used by the second service to obtain a second code block traffic, and sends the second code block traffic.
- the receiving end sends the second service using the first code block and the first service using the second code block to the corresponding first user and second user respectively in the second code block traffic.
- some embodiments of the present disclosure provide a system flow for implementing hybrid multiplexing on FlexE.
- FlexE MUX multiplexes delay-sensitive "existing services” (such as service 1 and service 2 in the figure), and then combines them with "new services” (such as service 3 in the figure) by a hybrid multiplexer ( Hybrid multiplexer (Hybrid Multiplex).
- Hybrid MUX can identify free code blocks in the code block traffic from FlexE MUX, and then replace the "new services" with free code blocks. It is then sent by the sender to the receiver via FlexEGroup.
- the receiving end has a symmetrical structure.
- Hybrid Multiplexer (Hybrid Multiplexer, Hybrid DMUX) first demultiplexes the "new service” and transmits it to the FlexE peer user. Then the remaining "existing services” are transmitted to the corresponding FlexE counterpart users via FlexE DMUX.
- some embodiments of the present disclosure provide a transmitting end 800, including a first transceiver 801 and a first processor 802;
- the first processor 802 is configured to identify an idle code block from a first code block traffic corresponding to a first service
- the first processor 802 is further configured to replace the idle code block with a first code block used by a second service
- the first processor 802 is further configured to perform a hybrid processing on the second code block used by the first service and the first code block used by the second service in the first code block traffic to obtain a second code block.
- Code block traffic
- the first transceiver 801 is configured to send the second code block traffic obtained by the hybrid processing to a receiving end.
- the idle code blocks include code blocks that have been allocated to the first service but are not used by the first service, and / or code blocks reserved for the second service.
- the second code block traffic includes a third code block, where the third code block is used to indicate positions of all idle code blocks in a row where the third code block is located.
- the encoding method of the third code block is a 64B / 66B encoding method
- the third code block includes mapping information of an idle code block, where the mapping information is used to indicate where the third code block is located. The position of all free code blocks of the row.
- the sender replaces the idle code block in the first code block traffic corresponding to the first service with the first code block used by the second service, and replaces the second code block used by the first service with The first code block used by the second service is mixed and processed to obtain the second code block traffic, and the second code block traffic is sent to the receiving end.
- some embodiments of the present disclosure provide a receiving end 900, including: a second transceiver 901 and a second processor 902;
- the second transceiver 901 is configured to receive a second code block traffic from a transmitting end
- the second transceiver 901 is further configured to send a second service using the first code block in the second code block traffic to a corresponding first user;
- the second transceiver 901 is further configured to send a first service using the second code block in the second code block traffic to a corresponding second user;
- the second code block traffic is obtained by mixing processing of the second code block used by the first service and the first code block used by the second service in the first code block traffic, and the second service
- the used first code block multiplexes positions of unused idle code blocks in the first code block traffic.
- the idle code blocks include: code blocks that have been allocated to the first service but are not used, and / or code blocks reserved for the second service.
- the second code block traffic includes a third code block, where the third code block is used to indicate positions of all idle code blocks in a row where the third code block is located.
- the encoding method of the third code block is a 64B / 66B encoding method
- the third code block includes mapping information of an idle code block, where the mapping information is used to indicate where the third code block is located. The position of all free code blocks of the row.
- the sending end mixes the second code block used by the first service and the first code block used by the second service to obtain a second code block traffic, and sends the second code block traffic.
- the receiving end sends the second service using the first code block and the first service using the second code block to the corresponding first user and second user respectively in the second code block traffic.
- some embodiments of the present disclosure provide another communication device 1000, including a processor 1001, a transceiver 1002, a memory 1003, and a bus interface.
- the processor 1001 may be responsible for managing the bus architecture and general processing.
- the memory 1003 may store data used by the processor 1001 when performing operations.
- the communication device 1000 may further include: a computer program stored on the memory 1003 and executable on the processor 1001. When the computer program is executed by the processor 1001, some embodiments of the present disclosure are provided. Steps of the method.
- the bus architecture may include any number of interconnected buses and bridges, and one or more processors specifically represented by the processor 1001 and various circuits of the memory represented by the memory 1003 are linked together.
- the bus architecture can also link various other circuits such as peripherals, voltage regulators, and power management circuits, etc., which are all well known in the art, so some embodiments of the present disclosure will not perform them anymore. Further description.
- the bus interface provides the interface.
- the transceiver 1002 may be multiple elements, including a transmitter and a receiver, providing a unit for communicating with various other devices over a transmission medium.
- Some embodiments of the present disclosure also provide a computer-readable storage medium.
- a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, each process of the foregoing method embodiment of network access is implemented, and To achieve the same technical effect, to avoid repetition, it will not be repeated here.
- the computer-readable storage medium is, for example, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.
- an embodiment or “an embodiment” mentioned throughout the specification means that a particular feature, structure, or characteristic related to the embodiment is included in at least one embodiment of the present disclosure.
- the appearances of "in one embodiment” or “in an embodiment” appearing throughout the specification are not necessarily referring to the same embodiment.
- the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.
- B corresponding to A means that B is associated with A, and B can be determined according to A.
- determining B based on A does not mean determining B based on A alone, but also determining B based on A and / or other information.
- the disclosed methods and devices may be implemented in other ways.
- the device embodiments described above are only schematic.
- the division of the unit is only a logical function division.
- multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not implemented.
- the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, which may be electrical, mechanical or other forms.
- each functional unit in each embodiment of the present disclosure may be integrated into one processing unit, or each unit may be separately physically included, or two or more units may be integrated into one unit.
- the above integrated unit may be implemented in the form of hardware, or in the form of hardware plus software functional units.
- the above integrated unit implemented in the form of a software functional unit may be stored in a computer-readable storage medium.
- the above software functional unit is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network-side device, etc.) to perform some steps of the transmitting and receiving method described in the embodiments of the present disclosure.
- the foregoing storage media include: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc. The medium.
- the embodiments described in the embodiments of the present disclosure may be implemented by hardware, software, firmware, middleware, microcode, or a combination thereof.
- the processing unit can be implemented in one or more application-specific integrated circuits (ASICs), digital signal processors (DSP), digital signal processing devices (DSPD), programmable Programmable Logic Device (PLD), Field-Programmable Gate Array (FPGA), general-purpose processor, controller, microcontroller, microprocessor, other for performing functions described in this disclosure Electronic unit or combination thereof.
- ASICs application-specific integrated circuits
- DSP digital signal processors
- DSPD digital signal processing devices
- PLD programmable Programmable Logic Device
- FPGA Field-Programmable Gate Array
- controller microcontroller
- microprocessor other for performing functions described in this disclosure Electronic unit or combination thereof.
- the technology described in the embodiments of the present disclosure may be implemented by modules (such as procedures, functions, and the like) that perform the functions described in the embodiments of the present disclosure.
- Software codes may be stored in a memory and executed by a processor.
- the memory can be implemented in the processor or external to the processor.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
本公开的一些实施例提供了一种业务处理方法及设备,该方法包括:从第一业务对应的第一码块流量中识别出空闲码块;将空闲码块替换为第二业务使用的第一码块;将第一码块流量中第一业务使用的第二码块和第二业务使用的第一码块进行混合处理,得到第二码块流量;以及向接收端发送混合处理得到的第二码块流量。
Description
相关申请的交叉引用
本申请主张在2018年9月20日在中国提交的中国专利申请号No.201811099522.6的优先权,其全部内容通过引用包含于此。
本公开涉及无线领域,特别涉及一种业务处理方法和设备。
光联网论坛(Optical Internet Forum,OIF)灵活以太网(Flex Ethernet,FlexE)-01.0中定义了FlexE技术,FlexE技术特点是,可以将带宽划分多个分槽信道,可以将一组物理层(PHYs)实现绑定,可以支持子速率划分。FlexE运行在设定好的64B/66B块日历槽位。日历槽的颗粒度是5G,在100G的以太网物理层(PHY)可以划分出20个槽位。
FlexE只定义了10千兆以太网(Gigabit Ethernet,GE)、40GE、n×25GE的速率,在对各种不同业务分配带宽时不得不适应对应的峰值速率,即向FlexE用户分配固定的带宽资源。那么当这些FlexE用户的业务中,只有轻量级的数据流量或者根本没有数据传输时,由于固定带宽分配,会造成大量的带宽资源浪费,导致带宽利用率低下。
如图1所示,假定FlexE用户有两种业务,业务1和业务2称为“现有业务”,代表对时延敏感的一类业务,例如:增强现实(Augmented Reality,AR),虚拟现实(Virtual Reality,VR)等。业务3称为“新增业务”,代表靠传统的存储转发方式传输的带宽有限的突发流量业务,例如:电子邮件(E-mail),网页(Web)网页等。这两种业务在发送端由灵活以太网数据选择器(Flex Ethernet multiplexer,FlexE MUX)复用到日历槽中,再经由灵活以太网组(FlexE Group)发送至接收端,接收端通过灵活以太网数据分配器 (Flex Ethernet demultiplexer,FlexE DMUX)解复用至对端用户。
FlexE只定义了10GE、40GE、n×25GE的速率,在对各种不同业务分配带宽时不得不适应对应的峰值速率,即向FlexE用户分配固定的带宽资源。那么当这些FlexE用户的业务中,只有轻量级的数据流量或者根本没有数据传输时,由于固定带宽分配,会造成大量的带宽资源浪费,导致带宽利用率低下。
发明内容
本公开的一些实施例提供了一种业务处理方法和设备,解决FlexE系统的带宽利用率低的问题。
依据本公开的一些实施例的第一方面,提供了一种业务处理方法,应用于发送端,所述方法包括:从第一业务对应的第一码块流量中识别出空闲码块;将所述空闲码块替换为第二业务使用的第一码块;将所述第一码块流量中所述第一业务使用的第二码块和所述第二业务使用的第一码块进行混合处理,得到第二码块流量;以及向接收端发送混合处理得到的所述第二码块流量。
可选地,所述空闲码块包括:已分配给所述第一业务但所述第一业务未使用的码块,和/或给所述第二业务预留的码块。
可选地,所述第二码块流量中包括:第三码块,所述第三码块用于指示所述第三码块所在行的所有空闲码块的位置。
可选地,所述第三码块的编码方式为64B/66B编码方式,所述第三码块中包括:空闲码块的映射信息,所述映射信息用于指示所述第三码块所在行的所有空闲码块的位置。
依据本公开的一些实施例的第二方面,提供了另一种业务处理方法,应用于接收端,所述方法包括:从发送端接收第二码块流量;将所述第二码块流量中使用第一码块的第二业务发送至对应的第一用户;以及将所述第二码块流量中使用第二码块的第一业务发送至对应的第二用户;其中,所述第二码块流量是由第一码块流量中所述第一业务使用的第二码块和所述第二业务使用的第一码块混合处理得到 的,所述第二业务使用的第一码块复用所述第一码块流量中未使用的空闲码块的位置。
可选地,所述空闲码块包括:已分配给所述第一业务但未使用的码块,和/或给所述第二业务预留的码块。
可选地,所述第二码块流量中包括:第三码块,所述第三码块用于指示所述第三码块所在行的所有空闲码块的位置。
可选地,所述第三码块的编码方式为64B/66B编码方式,所述第三码块中包括:空闲码块的映射信息,所述映射信息用于指示所述第三码块所在行的所有空闲码块的位置。
依据本公开的一些实施例的第三方面,提供了一种发送端,包括:第一收发机和第一处理器,其中,所述第一处理器,用于从第一业务对应的第一码块流量中识别出空闲码块;所述第一处理器,还用于将所述空闲码块替换为第二业务使用的第一码块;所述第一处理器,还用于将所述第一码块流量中所述第一业务使用的第二码块和所述第二业务使用的第一码块进行混合处理,得到第二码块流量;以及所述第一收发机,用于向接收端发送混合处理得到的所述第二码块流量。
可选地,所述空闲码块包括:已分配给所述第一业务但所述第一业务未使用的码块,和/或给所述第二业务预留的码块。
可选地,所述第二码块流量中包括:第三码块,所述第三码块用于指示所述第三码块所在行的所有空闲码块的位置。
可选地,所述第三码块的编码方式为64B/66B编码方式,所述第三码块中包括:空闲码块的映射信息,所述映射信息用于指示所述第三码块所在行的所有空闲码块的位置。
依据本公开的一些实施例的第四方面,提供了一种接收端,包括:第二收发机和第二处理器,其中,所述第二收发机,用于从发送端接收第二码块流量;所述第二收发机,还用于将所述第二码块流量中使用第一码块的第二业务发送至对应的第一用户;以及所述第二收发机,还用于将所述第二码块流量中使用第二码块的第一业务发送至对应的第二用户;其中,所述第二码块流量是由第一码块流量中所述第一 业务使用的第二码块和所述第二业务使用的第一码块混合处理得到的,所述第二业务使用的第一码块复用所述第一码块流量中未使用的空闲码块的位置。
可选地,所述空闲码块包括:已分配给所述第一业务但未使用的码块,和/或给所述第二业务预留的码块。
可选地,所述第二码块流量中包括:第三码块,所述第三码块用于指示所述第三码块所在行的所有空闲码块的位置。
可选地,所述第三码块的编码方式为64B/66B编码方式,所述第三码块中包括:空闲码块的映射信息,所述映射信息用于指示所述第三码块所在行的所有空闲码块的位置。
依据本公开的一些实施例的第五方面,提供了一种通信设备,包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的计算机程序,所述计算机程序被所述处理器执行时实现如第一方面所述的业务处理方法的步骤,或者,如第二方面所述的业务处理方法的步骤。
依据本公开的一些实施例的第六方面,提供了一种计算机可读存储介质,所述计算机可读存储介质上存储计算机程序,所述计算机程序被处理器执行时实现如第一方面所述的业务处理方法的步骤,或者,如第二方面所述的业务处理方法的步骤。
本公开的一些实施例中,发送端将第一业务对应的第一码块流量中的空闲码块替换为第二业务使用的第一码块,将第一业务使用的第二码块和第二业务使用的第一码块混合处理,得到第二码块流量,并将该第二码块流量发送给接收端。通过释放和重用这些已分配但未使用的带宽资源,同时保证不对时分系统中现有的流量造成影响,提高FlexE系统的带宽利用率。
为了更清楚地说明本公开实施例的技术方案,下面将对本公开实施例描述中所需要使用的附图作简单地介绍,显而易见地,下面描述 中的附图仅仅是本公开的一些实施例,对于本领域普通技术人员来讲,在不付出创造性劳动的前提下,还可以根据这些附图获得其他的附图。
图1为相关的基于硬管道的FlexE多路复用的系统框图;
图2为本公开的一些实施例的业务处理方法的流程图之一;
图3为本公开的一些实施例的20码块/次的流量示意图;
图4为本公开的一些实施例的64B/66B码块类型示意图;
图5为本公开的一些实施例的空闲码块信息的映射图;
图6为本公开的一些实施例的业务处理方法的流程图之二;
图7为本公开的一些实施例的FlexE上实现混合多路复用的系统框图;
图8为本公开的一些实施例的发送端的结构示意图;
图9为本公开的一些实施例的接收端的结构示意图;以及
图10为本公开的一些实施例的通信设备的结构示意图。
为使本公开要解决的技术问题、技术方案和优点更加清楚,下面将结合附图及具体实施例进行详细描述。
本文所描述的技术不限于长期演进型(Long Time Evolution,LTE)/LTE的演进(LTE-Advanced,LTE-A)系统,并且也可用于各种无线通信系统,诸如码分多址(Code Division Multiple Access,CDMA)、时分多址(Time Division Multiple Access,TDMA)、频分多址(Frequency Division Multiple Access,FDMA)、正交频分多址(Orthogonal Frequency Division Multiple Access,OFDMA)、单载波频分多址(Single-carrier Frequency-Division Multiple Access,SC-FDMA)和其他系统,例如:第五代移动通信(5th-generation,5G)系统以及后续演进通信系统。
术语“系统”和“网络”常被可互换地使用。CDMA系统可实现诸如CDMA2000、通用地面无线电接入(Universal Terrestrial Radio Access,UTRA)等无线电技术。UTRA包括宽带CDMA(Wideband Code Division Multiple Access,WCDMA)和其他CDMA变体。TDMA系统可实现诸如全球移动通信系统(Global System for Mobile Communication,GSM)之类的无线电技术。OFDMA系统可实现诸如超移动宽带(Ultra Mobile Broadband,UMB)、演进型UTRA(Evolution-UTRA,E-UTRA)、IEEE 802.11(Wi-Fi)、IEEE 802.16(WiMAX)、IEEE 802.20、Flash-OFDM等无线电技术。UTRA和E-UTRA是通用移动电信系统(Universal Mobile Telecommunications System,UMTS)的部分。LTE和更高级的LTE(如LTE-A)是使用E-UTRA的新UMTS版本。UTRA、E-UTRA、UMTS、LTE、LTE-A以及GSM在来自名为“第三代伙伴项目”(3rd Generation Partnership Project,3GPP)的组织的文献中描述。CDMA2000和UMB在来自名为“第三代伙伴项目2”(3GPP2)的组织的文献中描述。本文所描述的技术既可用于以上提及的系统和无线电技术,也可用于其他系统和无线电技术。
本公开的说明书和权利要求书中的术语“第一”、“第二”等是用于区别类似的对象,而不必用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换,以便这里描述的本公开的实施例例如能够以除了在这里图示或描述的那些以外的顺序实施。
参见图2,本公开的一些实施例提供了一种业务处理方法,应用于发送端,具体步骤如下:
步骤201:从第一业务对应的第一码块流量中识别出空闲码块;
在本公开的一些实施例中,第一业务为对时延敏感的一类业务,例如:图1中的业务1和业务2,即“现有业务”。
上述空闲码块包括:已分配给第一业务但第一业务未使用的码块,和/或给第二业务预留的码块。
步骤202:将空闲码块替换为第二业务使用的第一码块;
在本公开的一些实施例中,第二业务为靠传统的存储转发方式传输的带宽有限的突发流量业务,例如:图1中的业务3,即“新增业务”。
步骤203:将第一码块流量中第一业务使用的第二码块和第二业务使用的第一码块进行混合处理,得到第二码块流量;
在本公开的一些实施例中,第二码块流量中还包括第三码块,该第三码块用于指示该第三码块所在行的所有空闲码块的位置。
具体地,参见图3,图中以20码块/秒的流量为例,每行有20个码块,其中,标注“D/C”的码块为第二码块;标注“*”和标注“+”的码块为第一码块流量中的空闲码块,其中,标注“*”的码块表示给第二业务预留的码块,标注“+”的码块表示已分配给第一业务但第一业务未使用的码块;标注“#”的码块为第三码块。在混合处理的过程中,标注“*”和标注“+”的码块均会由第二业务使用的第一码块填充。
进一步地,参见图4,图中示出了一种64B/66B编码方式,该编码方式可以用于第三码块的编码。图中D1、D2和D3区域中标注有斜线的比特可以存放空闲码块的映射信息,该空闲码块的映射信息用于指示第三码块所在行的所有空闲码块的位置。
进一步地,参见图5,图中示出了一种空闲码块的映射信息。每一行的映射信息可以放到如图3中标注“#”的码块中,用于指示空闲码块的位置。其中,每个数字对应图3中的每个码块,“1”表示第一业务使用的第二码块,“0”表示第二业务使用的第一码块,“x”表示已分配给第一业务但第一业务未使用的码块。
步骤204:向接收端发送混合处理得到的第二码块流量。
在本公开的一些实施例中,发送端将第一业务对应的第一码块流量中的空闲码块替换为第二业务使用的第一码块,将第一业务使用的第二码块和第二业务使用的第一码块混合处理,得到第二码块流量,并将该第二码块流量发送给接收端。通过释放和重用这些已分配但未使用的带宽资源,同时保证不对时分系统中现有的流量造成影响,提高FlexE系统的带宽利用率。
参见图6,本公开的一些实施例提供了另一种业务处理方法,应用于接收端,具体步骤如下:
步骤601:从发送端接收第二码块流量;
在本公开的一些实施例中,第二码块流量是由第一码块流量中第一业务使用的第二码块和第二业务使用的第一码块混合处理得到的,第二业务使用的第一码块复用第一码块流量中未使用的空闲码块的位置。
发送端生成第二码块流量的方式可以参照如图2中步骤201至步骤203的描述,再此不再赘述。
步骤602:将第二码块流量中使用第一码块的第二业务发送至对应的第一用户;
步骤603:将第二码块流量中使用第二码块的第一业务发送至对应的第二用户。
在本公开的一些实施例中,发送端将第一业务使用的第二码块和第二业务使用的第一码块混合处理,得到第二码块流量,并将该第二码块流量发送给接收端,接收端将第二码块流量中使用第一码块的第二业务与使用第二码块的第一业务分别发送给对应的第一用户和第二用户。通过释放和重用这些已分配但未使用的带宽资源,同时保证不对时分系统中现有的流量造成影响,提高FlexE系统的带宽利用率。
参见图7,本公开的一些实施例提供一种FlexE上实现混合多路复用的系统流程。FlexE MUX将时延敏感的“现有业务”(例如图中业务1和业务2)进行复用,然后和“新增业务”(例如图中业务3)一起,由混合多路复用器(Hybrid multiplexer,Hybrid MUX)进行复用。Hybrid MUX能够识别出来自FlexE MUX的码块流量中的空闲码块,然后将“新增业务”替换掉空闲码块。之后由发送端经FlexE Group发送至接收端。接收端有着对称的结构,混合多路数据分配器(Hybrid demultiplexer,Hybrid DMUX)首先将“新增业务”解复用,传送至FlexE对端用户。再将剩下的“现有业务”经由FlexE DMUX将业务传送至对应的FlexE对端用户。
参见图8,本公开的一些实施例提供了一种发送端800,包括第一收发机801和第一处理器802;
其中,所述第一处理器802,用于从第一业务对应的第一码块流量中识别出空闲码块;
所述第一处理器802,还用于将所述空闲码块替换为第二业务使用的第一码块;
所述第一处理器802,还用于将所述第一码块流量中所述第一业务使用的第二码块和所述第二业务使用的第一码块进行混合处理,得到第二码块流量;
所述第一收发机801,用于向接收端发送混合处理得到的所述第二码块流量。
可选地,所述空闲码块包括:已分配给所述第一业务但所述第一业务未使用的码块,和/或给所述第二业务预留的码块。
可选地,所述第二码块流量中包括:第三码块,所述第三码块用于指示所述第三码块所在行的所有空闲码块的位置。
可选地,所述第三码块的编码方式为64B/66B编码方式,所述第三码块中包括:空闲码块的映射信息,所述映射信息用于指示所述第三码块所在行的所有空闲码块的位置。
在本公开的一些实施例中,发送端将第一业务对应的第一码块流量中的空闲码块替换为第二业务使用的第一码块,将第一业务使用的第二码块和第二业务使用的第一码块混合处理,得到第二码块流量,并将该第二码块流量发送给接收端。通过释放和重用这些已分配但未使用的带宽资源,同时保证不对时分系统中现有的流量造成影响,提高FlexE系统的带宽利用率。
参见图9,本公开的一些实施例提供一种接收端900,包括:第二收发机901和第二处理器902;
其中,所述第二收发机901,用于从发送端接收第二码块流量;
所述第二收发机901,还用于将所述第二码块流量中使用第一码块的第二业务发送至对应的第一用户;
所述第二收发机901,还用于将所述第二码块流量中使用第二码块的第一业务发送至对应的第二用户;
其中,所述第二码块流量是由第一码块流量中所述第一业务使用的第二码块和所述第二业务使用的第一码块混合处理得到的,所述第二业务使用的第一码块复用所述第一码块流量中未使用的空闲码块的位置。
可选地,所述空闲码块包括:已分配给所述第一业务但未使用的码块,和/或给所述第二业务预留的码块。
可选地,所述第二码块流量中包括:第三码块,所述第三码块用于指示所述第三码块所在行的所有空闲码块的位置。
可选地,所述第三码块的编码方式为64B/66B编码方式,所述第三码块中包括:空闲码块的映射信息,所述映射信息用于指示所述第三码块所在行的所有空闲码块的位置。
在本公开的一些实施例中,发送端将第一业务使用的第二码块和第二业务使用的第一码块混合处理,得到第二码块流量,并将该第二码块流量发送给接收端,接收端将第二码块流量中使用第一码块的第二业务与使用第二码块的第一业务分别发送给对应的第一用户和第二用户。通过释放和重用这些已分配但未使用的带宽资源,同时保证不对时分系统中现有的流量造成影响,提高FlexE系统的带宽利用率。
参见图10,本公开的一些实施例提供另一种通信设备1000,包括:处理器1001、收发机1002、存储器1003和总线接口。
其中,处理器1001可以负责管理总线架构和通常的处理。存储器1003可以存储处理器1001在执行操作时所使用的数据。
在本公开的一些实施例中,通信设备1000还可以包括:存储在存储器1003上并可在处理器1001上运行的计算机程序,该计算机程序被处理器1001执行时实现本公开的一些实施例提供的方法的步骤。
在图10中,总线架构可以包括任意数量的互联的总线和桥,具体由处理器1001代表的一个或多个处理器和存储器1003代表的存储器的各种电路链接在一起。总线架构还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起,这些都是本领域所公知的,因此,本公开的一些实施例不再对其进行进一步描述。总 线接口提供接口。收发机1002可以是多个元件,即包括发送机和接收机,提供用于在传输介质上与各种其他装置通信的单元。
本公开的一些实施例还提供一种计算机可读存储介质,计算机可读存储介质上存储有计算机程序,该计算机程序被处理器执行时实现上述网络接入的方法实施例的各个过程,且能达到相同的技术效果,为避免重复,这里不再赘述。其中,所述的计算机可读存储介质,如只读存储器(Read-Only Memory,简称ROM)、随机存取存储器(Random Access Memory,简称RAM)、磁碟或者光盘等。
需要说明的是,在本文中,术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含,从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素,而且还包括没有明确列出的其他要素,或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下,由语句“包括一个……”限定的要素,并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。
应理解,说明书通篇中提到的“一个实施例”或“一实施例”意味着与实施例有关的特定特征、结构或特性包括在本公开的至少一个实施例中。因此,在整个说明书各处出现的“在一个实施例中”或“在一实施例中”未必一定指相同的实施例。此外,这些特定的特征、结构或特性可以任意适合的方式结合在一个或多个实施例中。
在本公开的各种实施例中,应理解,上述各过程的序号的大小并不意味着执行顺序的先后,各过程的执行顺序应以其功能和内在逻辑确定,而不应对本公开实施例的实施过程构成任何限定。
在本申请所提供的实施例中,应理解,“与A相应的B”表示B与A相关联,根据A可以确定B。但还应理解,根据A确定B并不意味着仅仅根据A确定B,还可以根据A和/或其它信息确定B。
在本申请所提供的几个实施例中,应该理解到,所揭露方法和装置,可以通过其它的方式实现。例如,以上所描述的装置实施例仅仅是示意性的,例如,所述单元的划分,仅仅为一种逻辑功能划分, 实际实现时可以有另外的划分方式,例如多个单元或组件可以结合或者可以集成到另一个系统,或一些特征可以忽略,或不执行。另一点,所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口,装置或单元的间接耦合或通信连接,可以是电性,机械或其它的形式。
另外,在本公开各个实施例中的各功能单元可以集成在一个处理单元中,也可以是各个单元单独物理包括,也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现,也可以采用硬件加软件功能单元的形式实现。
上述以软件功能单元的形式实现的集成的单元,可以存储在一个计算机可读取存储介质中。上述软件功能单元存储在一个存储介质中,包括若干指令用以使得一台计算机设备(可以是个人计算机,服务器,或者网络侧设备等)执行本公开各个实施例所述收发方法的部分步骤。而前述的存储介质包括:U盘、移动硬盘、只读存储器(Read-Only Memory,简称ROM)、随机存取存储器(Random Access Memory,简称RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
可以理解的是,本公开实施例描述的这些实施例可以用硬件、软件、固件、中间件、微码或其组合来实现。对于硬件实现,处理单元可以实现在一个或多个专用集成电路(Application Specific Integrated Circuits,ASIC)、数字信号处理器(Digital Signal Processing,DSP)、数字信号处理设备(DSP Device,DSPD)、可编程逻辑设备(Programmable Logic Device,PLD)、现场可编程门阵列(Field-Programmable Gate Array,FPGA)、通用处理器、控制器、微控制器、微处理器、用于执行本公开所述功能的其它电子单元或其组合中。
对于软件实现,可通过执行本公开实施例所述功能的模块(例如过程、函数等)来实现本公开实施例所述的技术。软件代码可存储在存储器中并通过处理器执行。存储器可以在处理器中或在处理器外部 实现。以上所述是本公开的可选实施方式,应当指出,对于本技术领域的普通技术人员来说,在不脱离本公开所述原理的前提下,还可以作出若干改进和润饰,这些改进和润饰也应视为本公开的保护范围。
Claims (18)
- 一种业务处理方法,应用于发送端,所述方法包括:从第一业务对应的第一码块流量中识别出空闲码块;将所述空闲码块替换为第二业务使用的第一码块;将所述第一码块流量中所述第一业务使用的第二码块和所述第二业务使用的第一码块进行混合处理,得到第二码块流量;以及向接收端发送混合处理得到的所述第二码块流量。
- 根据权利要求1所述的方法,其中,所述空闲码块包括:已分配给所述第一业务但所述第一业务未使用的码块,和/或给所述第二业务预留的码块。
- 根据权利要求1所述的方法,其中,所述第二码块流量中包括:第三码块,所述第三码块用于指示所述第三码块所在行的所有空闲码块的位置。
- 根据权利要求3所述的方法,其中,所述第三码块的编码方式为64B/66B编码方式,所述第三码块中包括:空闲码块的映射信息,所述映射信息用于指示所述第三码块所在行的所有空闲码块的位置。
- 一种业务处理方法,应用于接收端,所述方法包括:从发送端接收第二码块流量;将所述第二码块流量中使用第一码块的第二业务发送至对应的第一用户;以及将所述第二码块流量中使用第二码块的第一业务发送至对应的第二用户;其中,所述第二码块流量是由第一码块流量中所述第一业务使用的第二码块和所述第二业务使用的第一码块混合处理得到的,所述第二业务使用的第一码块复用所述第一码块流量中未使用的空闲码块的位置。
- 根据权利要求5所述的方法,其中,所述空闲码块包括:已 分配给所述第一业务但未使用的码块,和/或给所述第二业务预留的码块。
- 根据权利要求5所述的方法,其中,所述第二码块流量中包括:第三码块,所述第三码块用于指示所述第三码块所在行的所有空闲码块的位置。
- 根据权利要求7所述的方法,其中,所述第三码块的编码方式为64B/66B编码方式,所述第三码块中包括:空闲码块的映射信息,所述映射信息用于指示所述第三码块所在行的所有空闲码块的位置。
- 一种发送端,包括:第一收发机和第一处理器,其中,所述第一处理器,用于从第一业务对应的第一码块流量中识别出空闲码块;所述第一处理器,还用于将所述空闲码块替换为第二业务使用的第一码块;所述第一处理器,还用于将所述第一码块流量中所述第一业务使用的第二码块和所述第二业务使用的第一码块进行混合处理,得到第二码块流量;以及所述第一收发机,用于向接收端发送混合处理得到的所述第二码块流量。
- 根据权利要求9所述的发送端,其中,所述空闲码块包括:已分配给所述第一业务但所述第一业务未使用的码块,和/或给所述第二业务预留的码块。
- 根据权利要求9所述的发送端,其中,所述第二码块流量中包括:第三码块,所述第三码块用于指示所述第三码块所在行的所有空闲码块的位置。
- 根据权利要求11所述的发送端,其中,所述第三码块的编码方式为64B/66B编码方式,所述第三码块中包括:空闲码块的映射信息,所述映射信息用于指示所述第三码块所在行的所有空闲码块的位置。
- 一种接收端,包括:第二收发机和第二处理器,其中,所述第二收发机,用于从发送端接收第二码块流量;所述第二收发机,还用于将所述第二码块流量中使用第一码块的第二业务发送至对应的第一用户;以及所述第二收发机,还用于将所述第二码块流量中使用第二码块的第一业务发送至对应的第二用户;其中,所述第二码块流量是由第一码块流量中所述第一业务使用的第二码块和所述第二业务使用的第一码块混合处理得到的,所述第二业务使用的第一码块复用所述第一码块流量中未使用的空闲码块的位置。
- 根据权利要求13所述的接收端,其中,所述空闲码块包括:已分配给所述第一业务但未使用的码块,和/或给所述第二业务预留的码块。
- 根据权利要求13所述的接收端,其中,所述第二码块流量中包括:第三码块,所述第三码块用于指示所述第三码块所在行的所有空闲码块的位置。
- 根据权利要求15所述的接收端,其中,所述第三码块的编码方式为64B/66B编码方式,所述第三码块中包括:空闲码块的映射信息,所述映射信息用于指示所述第三码块所在行的所有空闲码块的位置。
- 一种通信设备,包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的计算机程序,所述计算机程序被所述处理器执行时实现如权利要求1至4中任一项所述的业务处理方法的步骤,或者,如权利要求5至8中任一项所述的业务处理方法的步骤。
- 一种计算机可读存储介质,所述计算机可读存储介质上存储计算机程序,所述计算机程序被处理器执行时实现如权利要求1至4中任一项所述的业务处理方法的步骤,或者,如权利要求5至8中任一项所述的业务处理方法的步骤。
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201811099522.6A CN110932999A (zh) | 2018-09-20 | 2018-09-20 | 业务处理方法和设备 |
CN201811099522.6 | 2018-09-20 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2020057534A1 true WO2020057534A1 (zh) | 2020-03-26 |
Family
ID=69856166
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2019/106370 WO2020057534A1 (zh) | 2018-09-20 | 2019-09-18 | 业务处理方法和设备 |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN110932999A (zh) |
WO (1) | WO2020057534A1 (zh) |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN114257333A (zh) * | 2020-09-24 | 2022-03-29 | 华为技术有限公司 | 一种码块流的处理方法及装置 |
CN113438185B (zh) * | 2021-06-24 | 2022-07-01 | 新华三技术有限公司 | 一种带宽分配方法、装置及设备 |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090103487A1 (en) * | 2007-10-18 | 2009-04-23 | Samsung Electronics Co. Ltd. | Method and apparatus for allocating resources in a wireless communication system |
CN107566075A (zh) * | 2016-07-01 | 2018-01-09 | 华为技术有限公司 | 一种发送和接收业务的方法、装置和网络系统 |
US20180076932A1 (en) * | 2016-09-13 | 2018-03-15 | Fujitsu Limited | Transmission device and transmission method |
CN108242969A (zh) * | 2016-12-23 | 2018-07-03 | 华为技术有限公司 | 一种传输速率的调整方法及网络设备 |
Family Cites Families (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN106788855B (zh) * | 2015-11-23 | 2018-12-07 | 华为技术有限公司 | 一种灵活以太网业务的光传送网承载方法及装置 |
CN108092739B (zh) * | 2016-11-23 | 2020-10-16 | 华为技术有限公司 | 业务的传输方法和装置 |
CN108347317B (zh) * | 2017-01-22 | 2020-11-10 | 华为技术有限公司 | 一种业务的传输方法、网络设备及网络系统 |
-
2018
- 2018-09-20 CN CN201811099522.6A patent/CN110932999A/zh active Pending
-
2019
- 2019-09-18 WO PCT/CN2019/106370 patent/WO2020057534A1/zh active Application Filing
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090103487A1 (en) * | 2007-10-18 | 2009-04-23 | Samsung Electronics Co. Ltd. | Method and apparatus for allocating resources in a wireless communication system |
CN107566075A (zh) * | 2016-07-01 | 2018-01-09 | 华为技术有限公司 | 一种发送和接收业务的方法、装置和网络系统 |
US20180076932A1 (en) * | 2016-09-13 | 2018-03-15 | Fujitsu Limited | Transmission device and transmission method |
CN108242969A (zh) * | 2016-12-23 | 2018-07-03 | 华为技术有限公司 | 一种传输速率的调整方法及网络设备 |
Also Published As
Publication number | Publication date |
---|---|
CN110932999A (zh) | 2020-03-27 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2019085816A1 (zh) | 业务数据传输方法及装置 | |
US20210281344A1 (en) | Methods and Apparatus for Configuring a Flex Ethernet Node | |
WO2018177223A1 (zh) | 资源配置、确定部分带宽及指示部分带宽的方法及设备 | |
WO2017088517A1 (zh) | 一种灵活以太网业务的光传送网承载方法及装置 | |
CN110535611A (zh) | 信号发送、接收、信息反馈方法、装置、通信节点及介质 | |
WO2019062227A1 (zh) | 数据传输方法、传输设备和传输系统 | |
KR20190103332A (ko) | 데이터 처리 방법, 장치 및 시스템 | |
CN113972997A (zh) | 一种传输数据的方法和设备 | |
WO2018112890A1 (zh) | 传输数据的方法、网络设备和终端设备 | |
WO2020057534A1 (zh) | 业务处理方法和设备 | |
CN109479006B (zh) | 生成转发表的方法和转发设备 | |
JP2020506595A (ja) | データ処理方法、通信デバイス、およびネットワークデバイス | |
EP2430804A1 (en) | Universal service transport transitional encoding | |
WO2018126787A1 (zh) | 一种上行免授权用户激活检测方法、装置及基站 | |
AU2015409983A1 (en) | Data transmission method and apparatus | |
BR112020002809A2 (pt) | método de transmissão de dados, dispositivo, dispositivo terminal, dispositivo de rede, mídia de armazenamento legível por computador, chip e sistema de comunicações de dados | |
KR102450095B1 (ko) | 데이터 송신 방법, 전송 장치, 및 수신 장치 | |
WO2019153853A1 (zh) | 资源指示方法、用户设备及网络侧设备 | |
US20220149973A1 (en) | Service data transmission method and communication apparatus | |
WO2022021929A1 (zh) | 一种FlexE的资源管理方法及装置 | |
WO2020207429A1 (zh) | 报文处理方法、装置及计算机可读存储介质 | |
WO2017173881A1 (zh) | 参考信号的传输方法、设备和系统 | |
CN107005959A (zh) | 一种同步方法、装置及系统 | |
WO2023109424A1 (zh) | 一种数据传输的方法以及相关装置 | |
WO2015021609A1 (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: 19863614 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
32PN | Ep: public notification in the ep bulletin as address of the adressee cannot be established |
Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 08.07.2021) |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 19863614 Country of ref document: EP Kind code of ref document: A1 |