CN116112452A - Message transmission method and communication device - Google Patents
Message transmission method and communication device Download PDFInfo
- Publication number
- CN116112452A CN116112452A CN202111332727.6A CN202111332727A CN116112452A CN 116112452 A CN116112452 A CN 116112452A CN 202111332727 A CN202111332727 A CN 202111332727A CN 116112452 A CN116112452 A CN 116112452A
- Authority
- CN
- China
- Prior art keywords
- message
- client
- data
- network device
- field
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 82
- 238000004891 communication Methods 0.000 title claims abstract description 60
- 230000005540 biological transmission Effects 0.000 title abstract description 37
- 238000002955 isolation Methods 0.000 claims abstract description 46
- 238000004590 computer program Methods 0.000 claims description 8
- 238000013461 design Methods 0.000 description 58
- 238000012545 processing Methods 0.000 description 24
- 238000010586 diagram Methods 0.000 description 18
- 238000005516 engineering process Methods 0.000 description 14
- 230000008569 process Effects 0.000 description 11
- 230000006870 function Effects 0.000 description 10
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000005538 encapsulation Methods 0.000 description 3
- 230000008859 change Effects 0.000 description 2
- 230000006835 compression Effects 0.000 description 2
- 238000007906 compression Methods 0.000 description 2
- 125000004122 cyclic group Chemical group 0.000 description 2
- 238000013507 mapping Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000002093 peripheral effect Effects 0.000 description 2
- 239000007787 solid Substances 0.000 description 2
- 238000013500 data storage Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000000802 evaporation-induced self-assembly Methods 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000004806 packaging method and process Methods 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L49/00—Packet switching elements
- H04L49/30—Peripheral units, e.g. input or output ports
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/42—Loop networks
- H04L12/427—Loop networks with decentralised control
- H04L12/43—Loop networks with decentralised control with synchronous transmission, e.g. time division multiplex [TDM], slotted rings
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L49/00—Packet switching elements
- H04L49/10—Packet switching elements characterised by the switching fabric construction
- H04L49/111—Switch interfaces, e.g. port details
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L49/00—Packet switching elements
- H04L49/60—Software-defined switches
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
The application provides a message transmission method and a communication device, relates to the technical field of communication, and can improve the utilization rate of port resources and flexibly send messages. The method comprises the following steps: the first network device determines a first message and a second message. The first message comprises data of common service, and the second message comprises data of hard isolation service. Then, the first network device sends the first message and the second message in the same period through the first port.
Description
Technical Field
The embodiment of the application relates to the field of communication, in particular to a message transmission method and a communication device.
Background
The store-and-forward is a forwarding technology used by standard ethernet since birth, and means that each receiving side device in the network completely receives and stores a message, performs table lookup processing on the message, finds out an output port, and forwards the message. The channel forwarding refers to forwarding according to a mapping relation of service access ports and a configuration table, and is a technology for forwarding based on code blocks. The store-and-forward and the channel-and-forward are carried out on different ports, and the two ports are mutually independent and mutually incompatible.
However, the number of messages to be transmitted in store-and-forward and channel-forward may be different, and there is a phenomenon that one port is idle, messages of another port cannot be sent in time, the port utilization rate is poor, and the messages cannot be flexibly transmitted.
Disclosure of Invention
The application provides a message transmission method and a communication device, which can improve the port resource utilization rate and flexibly send messages.
In order to achieve the above purpose, the embodiment of the application adopts the following technical scheme:
in a first aspect, an embodiment of the present application provides a method for transmitting a message, where an execution body of the method may be a first network device, or may be a chip applied to the first network device. The following describes an example in which the execution subject is the first network device. The method comprises the following steps: the first network device determines a first message and a second message. The first message comprises data of common service, and the second message comprises data of hard isolation service. Then, the first network device sends the first message and the second message in the same period through the first port.
Therefore, even if the number of the first messages and the number of the second messages dynamically change, the first network device can send more first messages when the number of the second messages is reduced or no second messages are sent because the two messages are sent through the same port, or conversely, can send more second messages when the number of the first messages is reduced or no first messages are sent, so that the port is prevented from being idle, the port utilization rate is improved, and the messages can be flexibly transmitted.
In one possible design, the first message includes a first field. The first field indicates a type of the first message, for example, indicates that the type of the first message is a normal message. The second message includes a second field. The second field indicates a type of the second message, for example, indicates that the type of the second message is a hard isolation message, so that the receiving end device, for example, the second network device, determines the type of the received message through the first field or the second field.
In one possible design, the first field is carried in a preamble portion of the first message, or the first field is carried in an overhead OH field of the first message.
In one possible design, the second field is carried in the preamble portion of the second message, or the second field is carried in the OH field of the second message.
In one possible design, the first message further includes a first identifier. The first identifier is used for identifying a first client, and the message of the first client comprises a first message.
That is, the first identifier indicates which client the first message is.
In one possible design, the first data unit includes a first code block. The first data unit is one or more data units in the second message, the first code block is a code block after the service data of the target client is coded, the target client is one second client in the at least one second client, and the data in the second message comprises the service data of all second clients in the at least one second client.
That is, the second message carries at least one data unit, and one or more of the at least one data unit carries traffic data of a second client.
In one possible design, the message transmission method of the embodiment of the present application further includes: the first network device determines a first code block in the first data unit based on the first information. The first information indicates a corresponding relation between the first data unit and the target client, so that the first network device encapsulates the second message.
In one possible design, the length of the encoded message is the same for the first message and the second message, e.g., the number of code blocks carried in the load of the first message and the second message is the same.
In one possible design, the encoding includes at least one of: 64B/66B, 66B/65B, or 64B/65B.
In one possible design, the first network device sends the first message and the second message in the same period through the first port thereof, including: the first network device sends a first message on a first time unit and a second message on a second time unit through the first port according to the second information. Wherein the second information indicates the positions of the first time unit and the second time unit in the period.
That is, the positions of the time units in the period are preconfigured, and the first network device only needs to transmit the first message and the second message according to the preconfigured positions of the time units.
In one possible design, the first network device sends the first message and the second message in the same period through the first port thereof, including: and the first network equipment sends a first message on the unoccupied first time unit and sends a second message on the unoccupied second time unit through the first port according to the second information and the third information. Wherein the second information indicates the number of configurations of the first time unit and the second time unit in the period, and the third information indicates the number of unoccupied first time unit and second time unit in the period.
That is, the number of time units in the period is preconfigured, but the position is not fixed, and the first network device transmits the first message and the second message according to the preconfigured number of time units. For example, at a certain moment, only the first message is packaged, and the number of time units of the first message corresponding to the clients is greater than zero, and then the first message is sent. For another example, at a certain moment, only the second message is packaged, and the number of time units of the second message corresponding to the clients is greater than zero, the second message is sent, so that the flexibility of message transmission is improved.
In one possible design, the second time unit in which the second message is located is earlier than the first time unit in which the first message is located. The second message has the same generation time as the first message, or the generation time of the second message is earlier than the generation time of the first message.
That is, if the second packet is encapsulated, even if the first packet is encapsulated, the first network device preferentially sends the second packet and then sends the first packet, so as to ensure the delay requirement of the hard isolation service.
In one possible design, the second time unit in which the second message is located is later than the first time unit in which the first message is located, and the second message is generated later than the first message. That is, if the second packet is not encapsulated, but the first packet is encapsulated, the first network device sends the first packet first and then sends the second packet, so as to avoid idle ports.
In one possible design, the second information is determined based on the traffic bandwidth of the first customer and the traffic bandwidth of the second customer. The message of the first client comprises a first message, and the data in the second message comprises service data of the second client. For example, the greater the traffic bandwidth of the first customer, the corresponding number of first time units. Similarly, the greater the traffic bandwidth of the second client, the corresponding greater the number of second time units.
In one possible design, the message transmission method of the embodiment of the present application further includes: the first network device determines a third message. The third message is a message of a third client, and the type of the third message is the same as that of the first message. The first network device sends a third message in a cycle through its first port. The third message is transmitted through a third time unit, the third time unit is configured to transmit a message of the first client, and the third time unit is in an idle state, and the message of the first client includes the first message.
That is, for a time unit(s) for transmitting the common message, even if a certain time unit(s), such as the third time unit, is (are) configured to transmit the message of the first client, if the message of the first client is not encapsulated, or the first client has no message transmission, the third time unit may transmit the message of the other client, such as the message of the third client, so as to realize the statistical multiplexing characteristic and improve the resource utilization.
In a second aspect, an embodiment of the present application provides a method for transmitting a message, where an execution body of the method may be a second network device, or may be a chip applied to the second network device. The following describes an example in which the execution subject is the second network device. The method comprises the following steps: the second network device receives the first message and the second message in the same period through the second port. The first message comprises data of common service, and the second message comprises data of hard isolation service. And then, the second network equipment forwards the service data in the first message according to the type of the first message, and forwards the service data in the second message according to the type of the second message.
In one possible design, the forwarding, by the second network device, service data in the first packet according to the type of the first packet includes: and the second network equipment determines a store-and-forward mode according to the type of the first message. The second network device forwards the service data in the first message in a store-and-forward mode.
That is, the second network device forwards the service data in the first packet in a store-and-forward manner.
In one possible design, the first message includes a first field. Wherein the first field indicates a type of the first message.
In one possible design, the first field is carried in a preamble portion of the first message, or the first field is carried in an overhead OH field of the first message.
In one possible design, the forwarding, by the second network device, service data in the second packet according to the type of the second packet includes: and the second network equipment determines a channel forwarding mode according to the type of the second message, and forwards the service data of each second client in at least one second client in the channel forwarding mode. The data in the second message includes service data of all second clients in at least one second client.
That is, the second network device forwards the service data in the second packet in a channel forwarding manner.
In one possible design, the second message includes a second field. Wherein the second field indicates a type of the second message.
In one possible design, the second field is carried in the preamble portion of the second message, or the second field is carried in the OH field of the second message.
In a third aspect, an embodiment of the present application provides a communication apparatus, where the communication apparatus may be the first network device in the first aspect or any one of the possible designs of the first aspect, or a chip implementing a function of the first network device; the communication device comprises corresponding modules, units or means (means) for realizing the method, and the modules, units or means can be realized by hardware, software or realized by executing corresponding software by hardware. The hardware or software includes one or more modules or units corresponding to the functions described above.
The communication device includes a processing unit and a transmitting unit. The processing unit is used for determining the first message and the second message. The first message comprises data of common service, and the second message comprises data of hard isolation service. And the sending unit is used for sending the first message and the second message in the same period through the first port.
In one possible design, the first message includes a first field. The first field indicates a type of the first message, for example, indicates that the type of the first message is a normal message. The second message includes a second field. Wherein the second field indicates a type of the second message.
In one possible design, the first field is carried in a preamble portion of the first message, or the first field is carried in an overhead OH field of the first message.
In one possible design, the second field is carried in the preamble portion of the second message, or the second field is carried in the OH field of the second message.
In one possible design, the first message further includes a first identifier. The first identifier is used for identifying a first client, and the message of the first client comprises a first message.
In one possible design, the first data unit includes a first code block. Wherein the first data unit is one or more data units in the second message. The first code block is a code block of the target client after the service data is encoded, and the target client is one of the at least one second client. The data in the second message includes service data of all second clients in the at least one second client.
In one possible design, the processing unit is further configured to determine a first code block in the first data unit according to the first information. Wherein the first information indicates a correspondence between the first data unit and the target client.
In one possible design, the first message and the second message have the same message length after encoding.
In one possible design, the encoding includes at least one of: 64B/66B, 66B/65B, or 64B/65B.
In one possible design, the sending unit is configured to send, through a first port thereof, a first packet and a second packet in the same period, and specifically includes: and according to the second information, sending the first message on the first time unit through the first port, and sending the second message on the second time unit. Wherein the second information indicates the positions of the first time unit and the second time unit in the period.
In one possible design, the sending unit is configured to send, through a first port thereof, a first packet and a second packet in the same period, and specifically includes: and according to the second information and the third information, sending a first message on an unoccupied first time unit through the first port, and sending a second message on an unoccupied second time unit. Wherein the second information indicates the number of configurations of the first time unit and the second time unit in the period, and the third information indicates the number of unoccupied first time unit and second time unit in the period.
In one possible design, the second time unit in which the second message is located is earlier than the first time unit in which the first message is located. The second message has the same generation time as the first message, or the generation time of the second message is earlier than the generation time of the first message.
In one possible design, the second time unit in which the second message is located is later than the first time unit in which the first message is located, and the second message is generated later than the first message.
In one possible design, the second information is determined based on the traffic bandwidth of the first customer and the traffic bandwidth of the second customer. The data in the first message comprises the business data of the first client, and the data in the second message comprises the business data of the second client.
In one possible design, the processing unit is further configured to determine the third message. The third message is a message of a third client, and the type of the third message is the same as that of the first message. And the sending unit is also used for sending a third message in the period through the first port. The third message is transmitted through a third time unit, the third time unit is configured to transmit the message of the first client, and the third time unit is in an idle state. The first client message includes a first message.
In a fourth aspect, an embodiment of the present application provides a communication apparatus, where the communication apparatus may be the second network device in the second aspect or any one of the possible designs of the second aspect, or a chip that implements a function of the second network device; the communication device comprises corresponding modules, units or means (means) for realizing the method, and the modules, units or means can be realized by hardware, software or realized by executing corresponding software by hardware. The hardware or software includes one or more modules or units corresponding to the functions described above.
The communication device includes a receiving unit, a processing unit, and a transmitting unit. The receiving unit is configured to receive, through the second port, the first message and the second message in the same period. The first message comprises data of common service, and the second message comprises data of hard isolation service. And the sending unit is used for forwarding the service data in the first message according to the type of the first message and forwarding the service data in the second message according to the type of the second message.
In one possible design, the sending unit is configured to forward, according to a type of the first packet, service data in the first packet, and specifically includes: and the processing unit is used for determining a store-and-forward mode according to the type of the first message. And the sending unit is used for forwarding the service data in the first message in a store-and-forward mode.
In one possible design, the first message includes a first field. Wherein the first field indicates a type of the first message.
In one possible design, the first field is carried in a preamble portion of the first message, or the first field is carried in an overhead OH field of the first message.
In one possible design, the sending unit is configured to forward, according to the type of the second packet, service data in the second packet, including: and the processing unit is used for determining a channel forwarding mode according to the type of the second message. And the sending unit is used for forwarding the service data of each second client in the at least one second client in a channel forwarding mode. The data in the second message includes service data of all second clients in at least one second client.
In one possible design, the second message includes a second field. Wherein the second field indicates a type of the second message.
In one possible design, the second field is carried in the preamble portion of the second message, or the second field is carried in the OH field of the second message.
In a fifth aspect, embodiments of the present application provide a communication apparatus, including: a processor and a memory; the memory is configured to store computer instructions that, when executed by the processor, cause the communication apparatus to perform the method performed by the first network device in any one of the above aspects or any one of the possible designs of any one of the above aspects. The communication means may be the first network device of the first aspect or any of the possible designs of the first aspect, or a chip implementing the functionality of the first network device.
In a sixth aspect, embodiments of the present application provide a communication apparatus, including: a processor; the processor is coupled to the memory for reading the instructions in the memory and executing the instructions to cause the communication device to perform the method performed by the first network device in any one of the above aspects or any one of the possible designs of any one of the above aspects. The communication means may be the first network device of the first aspect or any of the possible designs of the first aspect, or a chip implementing the functionality of the first network device.
In a seventh aspect, embodiments of the present application provide a chip including a processing circuit and an input-output interface. Wherein the input-output interface is for communication with a module outside the chip, which may be, for example, a chip implementing the functionality of the first network device in the first aspect or any of the possible designs of the first aspect. The processing circuitry is arranged to run a computer program or instructions to implement the method of the first aspect above or any of the possible designs of the first aspect.
In an eighth aspect, embodiments of the present application provide a communication apparatus, including: a processor and a memory; the memory is configured to store computer instructions that, when executed by the processor, cause the communication apparatus to perform the method performed by the second network device in any one of the above aspects or any one of the possible designs of any one of the above aspects. The communication means may be the second network device of the second aspect or any of the possible designs of the second aspect, or a chip implementing the functionality of the second network device.
In a ninth aspect, embodiments of the present application provide a communication apparatus, including: a processor; the processor is coupled to the memory for reading the instructions in the memory and executing to cause the communication apparatus to perform the method performed by the second network device in any one of the above aspects or any one of the possible designs. The communication means may be the second network device of the second aspect or any of the possible designs of the second aspect, or a chip implementing the functionality of the second network device.
In a tenth aspect, embodiments of the present application provide a chip including a processing circuit and an input-output interface. Wherein the input-output interface is for communication with a module external to the chip, which may be, for example, a chip implementing the functionality of the second network device in the second aspect or any of the possible designs of the second aspect. The processing circuitry is configured to run a computer program or instructions to implement the method of the second aspect above or any of the possible designs of the second aspect.
In an eleventh aspect, embodiments of the present application provide a computer-readable storage medium having instructions stored therein that, when run on a computer, cause the computer to perform the method of any one of the above aspects.
In a twelfth aspect, embodiments of the present application provide a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of any one of the above aspects.
In a thirteenth aspect, embodiments of the present application provide circuitry comprising processing circuitry configured to perform the method of any one of the above aspects.
In a fourteenth aspect, embodiments of the present application provide a communication system including the first network device and the second network device in any one of the above aspects.
The technical effects of any one of the designs of the third aspect to the fourteenth aspect may refer to the advantages of the corresponding methods provided above, and are not repeated herein.
Drawings
FIG. 1 is a diagram of a network architecture for use with embodiments of the present application;
FIG. 2a is a schematic diagram of an encoding format according to an embodiment of the present application;
FIG. 2b is a schematic diagram of another encoding format according to an embodiment of the present application;
fig. 3a is a schematic diagram of a communication scenario provided in an embodiment of the present application;
FIG. 3b is a schematic diagram of still another communication scenario provided in an embodiment of the present application;
FIG. 4 is a schematic diagram of a port configuration according to an embodiment of the present disclosure;
fig. 5 is a flow chart of a message transmission method according to an embodiment of the present application;
fig. 6a is a schematic diagram of a message structure according to an embodiment of the present application;
FIG. 6b is a schematic diagram of another message structure according to an embodiment of the present application;
FIG. 6c is a schematic diagram of another message structure according to an embodiment of the present application;
FIG. 6d is a schematic diagram of another message structure according to an embodiment of the present application;
FIG. 6e is a schematic diagram of another message structure according to an embodiment of the present application;
fig. 7a is a schematic process diagram of a packet encapsulation according to an embodiment of the present application;
FIG. 7b is a schematic diagram illustrating a process of another packet encapsulation according to an embodiment of the present application;
fig. 8 is a flow chart of another method for transmitting a message according to an embodiment of the present application;
fig. 9a is a schematic diagram of a scenario of message transmission according to an embodiment of the present application;
fig. 9b is a schematic diagram of a scenario of still another message transmission according to an embodiment of the present application;
fig. 10 is a flow chart of another method for transmitting a message according to an embodiment of the present application;
fig. 11 is a schematic structural diagram of a communication device according to an embodiment of the present application;
Fig. 12 is a schematic structural diagram of still another communication device according to an embodiment of the present application.
Detailed Description
The terms "first" and "second" and the like in the description and in the drawings are used for distinguishing between different objects or for distinguishing between different processes of the same object and not for describing a particular sequential order of objects. Furthermore, references to the terms "comprising" and "having" and any variations thereof in the description of the present application are intended to cover a non-exclusive inclusion. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those listed but may optionally include other steps or elements not listed or inherent to such process, method, article, or apparatus. It should be noted that, in the embodiments of the present application, words such as "exemplary" or "such as" are used to mean serving as an example, instance, or illustration. Any embodiment or design described herein as "exemplary" or "for example" should not be construed as preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "such as" is intended to present related concepts in a concrete fashion.
A network architecture to which embodiments of the present application may be applied is shown in fig. 1, where the network architecture includes a client device and a network device.
The number of client devices may be two or more, and four client devices, such as client device 101, client device 102, client device 103, and client device 104, are shown in fig. 1.
The network devices include Provider Edge (PE) devices and provider (P) devices. The number of the PE devices can be two or more. The P device may be one or more. Two PE devices (PE device 105 and PE device 106) and one P device are shown in fig. 1, the P devices being communicatively connected to PE device 105 and PE device 106, respectively. Client device 101 and client device 102 are each communicatively coupled to PE device 105, and client device 103 and client device 104 are each communicatively coupled to PE device 106.
The client device may be a router or a switch, or may be a host. The PE device may be a service provider edge router, an edge device of a service provider network, directly connected to the client device. The P device may be a backbone router in a service provider network, and is not directly connected to a client device, and implementation forms of the client device and the network device are not limited in the embodiments of the present application.
It should be understood that in different network architectures, the network devices and client devices may correspond to different names, and those skilled in the art will appreciate that the names do not limit the devices themselves.
In the network architecture, each device (e.g., the client device, PE device, P device) carries one or more services. By way of example, the service carried on a device may be one or more of mail service, web service, instant messaging service, and the like. For a client device, a service may be carried on a client device, or multiple services may be carried on a client device, where the services correspond to the same client, whether one service or multiple services. For a network device (e.g., PE device, P device) described above, one network device may carry one service, or may carry multiple services, whether one service or multiple services, which correspond to multiple clients.
In order to facilitate understanding of the embodiments of the present application, the following description will be given for the terms involved in the embodiments of the present application. It should be understood that these descriptions are merely for the purpose of facilitating understanding of the embodiments of the present application and should not be construed as limiting the application in any way.
1. M bit/N bit block (bit block):
an M-bit/N-bit block may also be referred to as an M-bit/N-bit encoded block, an M/N-bit encoded block, or an M/N-bit block. Where M represents the code input and N represents the code output. M and N are positive integers, and M < N.
64B/66B is a short for 64/66bit block, and refers to 64B/66B block defined by IEEE 802.3. Specifically, based on the 64bit input, a 2bit synchronization header (sync) is added depending on whether it is control information or traffic data information. Where 0b10 denotes a control code block, 0b01 denotes a data code block, and other types of sync headers denote invalid code blocks. In the control code Block, a Block Type Field (Block Type Field) is also included to indicate the Block Type. Illustratively, the values of the block type field include 0x1E, 0x78, 0x4B, 0x87, 0x99, 0xAA, 0xB4, 0xCC, 0xD2, 0xE1, or 0xFF, as shown in FIG. 2 a.
64B/65B, which is a short for 64/65bit block, refers to 64B/65B block defined by IEEE 802.3. Specifically, a 2-bit sync header is compressed into a 1-bit encoded block on a 64B/66B basis. Alternatively, the encoding is directly performed on the basis of 64bit input, and a 1bit synchronization header is added. 64B/65B are shown in FIG. 2B.
2. Hard isolated service, normal service
The hard isolation service refers to a service having a requirement for isolation. For example, referring to table a, if a service has a requirement for isolation, the service is a hard-isolated service. Optionally, the hard isolation service may also have requirements for indicators such as delay, jitter, etc. For example, the latency of the hard isolated traffic is less than or equal to 100us. For another example, the jitter of the hard isolated traffic is less than or equal to 10ns.
The normal service is a service which has no requirement on all the three indexes of isolation, time delay, jitter and the like, and is shown in the last row in the table a. Or the common service can be a service of the network given best effort service, namely, a service which has no guarantee on time delay, jitter and isolation.
Table a
In the embodiment of the present application, the service type refers to a normal service or a hard isolation service.
By way of example, still taking mail service, web service, instant messaging service as an example, the service types of mail service and web service are ordinary service, and the service type of instant messaging service (such as video conference service) is hard quarantine service.
3. Hard isolation message and common message
The hard isolation message is a message encapsulated by data of hard isolation service. The service data in the hard isolation message is data of the hard isolation service. The service data in one hard isolation packet may be from one client or from multiple clients, which is not limited in the embodiment of the present application.
The general report message refers to a message encapsulated by data of common service. The service data in the general report is data of a general service. The traffic data in a common message comes from a client.
In the embodiment of the present application, the message type refers to a normal message or a hard isolation message.
4. Hard isolation, statistical multiplexing
Hard isolation refers to the fact that when a link bandwidth is allocated to a service, the link bandwidth is not used by other services even if the service has no data to send. By way of example, the network device isolates different services from each other during transmission by time division technology, frequency division technology and the like, and achieves that delay, jitter, bandwidth and the like do not affect each other. That is, the network device needs to adopt a technology supporting the hard isolation characteristic, such as a time slot technology, to forward the message of the hard isolation service.
Statistical multiplexing refers to when a link bandwidth is allocated to a service, the link bandwidth can be used by other services when the service has no data to send. The technology adopted by the network equipment needs to support statistical multiplexing characteristics, such as a message technology, and can improve the resource utilization rate when forwarding the message of the common service.
Illustratively, the message technology supports statistical multiplexing characteristics and does not support hard isolation characteristics. The time slot technology supports hard isolation characteristics and does not support statistical multiplexing characteristics.
5. Store-and-forward, channel-forwarding
Store-and-forward is a forwarding technique that standard ethernet has used since birth. Store-and-forward refers to that after each receiving side device in the network receives and stores the message completely, it performs a table look-up process to find the output port of the message, and forwards the message through the output port, as shown in fig. 3 a. The receiving-side device may be a network device in fig. 3a, such as PE device 105, PE device 106, P device 107, or P device 108. In addition, store-and-forward may also be referred to as two-layer forwarding, packet forwarding, or destination forwarding (destination forwarding). Illustratively, the port on the receiving side device for store-and-forward, referred to as a message port, is in the form of the port shown in fig. 4. The message port may be a native ethernet port, such as an interface that implements message level forwarding using unmodified ethernet technology. The network device sends the ethernet frame through the message port.
The channel forwarding refers to that each receiving side device in the network forwards according to the mapping relationship between the outgoing port and the incoming port of the service, without recovering the complete message, as shown in fig. 3 b. The receiving-side device may be a network device in fig. 3b, such as PE device 105, PE device 106, P device 107, or P device 108. Channel forwarding belongs to the time-slotted technology. Channel forwarding, which may also be referred to as layer 1.5 forwarding, or channel forwarding. Illustratively, the port on the receiving side device for channel forwarding, referred to as a slotted port, has a port morphology as shown in fig. 4. The slotted port may be an interface that implements code block level forwarding using a modified ethernet technology, such as a flexible ethernet (FlexE) technology. The network device transmits the slotted frame through the slotted port. The time-slotted frame is a frame with a structure, and the time-slotted frame is a frame with a time-slotted frame structure.
It should be understood that in the embodiments of the present application, a frame or message refers to an ethernet frame. In the following, only the name of the message will be described.
As can be seen from fig. 4, the message port and the time slot port are independent of each other and are not compatible with each other. The same network device needs to have the two ports to forward the messages of the two services (namely the common service and the hard isolation service).
However, in the above two forwarding manners, the number of messages to be transmitted may be different. If the message to be forwarded in one forwarding mode does not exist, the corresponding port is idle, and the message to be forwarded in the other forwarding mode is Wen Jiaoduo, the message of the corresponding port cannot be sent in time, the port utilization rate is poor, and the network equipment cannot flexibly transmit the message.
In view of this, the embodiment of the present application provides a message transmission method, which is applied to the network architecture of fig. 1, fig. 3a or fig. 3 b. In the message transmission method of the embodiment of the application, the first network device determines the first message and the second message. The first message comprises data of common service, and the second message comprises data of hard isolation service. Then, the first network device sends a first message and a second message in the same period through the first port. Wherein the first port is a port on a first network device. In this way, even if the number of the first messages and the number of the second messages dynamically change, since the two messages are sent through the same port, the first network device can send more first messages when the number of the second messages is reduced or no second messages are sent, or conversely, the first network device can send more second messages when the number of the first messages is reduced or no first messages are sent, so that the port is prevented from being idle, the port utilization rate is improved, and the message transmission is more flexible.
Next, a detailed description of the message transmission method 500 according to the embodiment of the present application will be described with reference to fig. 5.
S501, the first network device determines a first message and a second message.
In fig. 1, for example, in the case where the packet is transmitted from left to right, the first network device may be a PE device 105 or a P device. In the case of a packet transmitted from right to left, the first network device may be a PE device 106 or a P device. In the embodiment of the present application, the first network device is implemented as the PE device 105 is described as an example.
The type of the first message is different from the type of the second message.
The description of the first message is as follows: the first message includes data of a normal service. Illustratively, the data of the normal service in the first message is from the first client. Still taking fig. 1 as an example, the first client may be a client corresponding to the client device 101. The client device 101 sends traffic data of the first client to the PE device 105. Accordingly, PE device 105 receives traffic data from a first client of client device 101. The PE device 105 then encapsulates the traffic data of the first customer into a first packet.
Illustratively, the first message indicates the message type via a field. For example, the first message includes a first field. The first field indicates the type of the first message, for example, the value of the first field is 0x55.
For example, taking fig. 6a as an example, the first message includes a preamble (preamble) field, a frame start delimiter (start frame delimiter, SFD) field, an Overhead (OH) field, a payload field, and a cyclic redundancy check (cyclic redundancy check, CRC) field. Illustratively, as shown in fig. 6a, the first field is carried in the preamble portion of the first message.
For another example, taking fig. 6b as an example, the first field is carried in the OH field of the first message, such as the first field is carried in the last field in the OH.
Optionally, the first message further includes a first identifier. The first identifier is used for identifying the first client so as to identify which client the first message is. The first identity is carried in the OH field. Taking FIG. 6a as an example, the first identifier may be denoted as a fine-grained client identifier (fine-granularity client identity, fgClientID), which occupies 2 fields, namely 16bits, with a value ranging from 0 to 2≡16-1. As shown in fig. 6a, the first identity occupies the first 2 fields of the OH fields. The third of the OH fields, field 2 in fig. 6a, is reserved.
The process of encapsulating the first message by the first network device is as follows:
as shown in fig. 7a, taking the medium access control (media access control, MAC) frame of the first client as an example, the first network device first performs 64B/66B encoding on the MAC frame to form a code block sequence 1. Wherein each code block in the code block sequence 1 is 66 bits. Then, the first network device performs synchronous header compression on the code block sequence 1 to form a code block sequence 2. Wherein each code block in the code block sequence 2 is 65 bits. Alternatively, the first network device performs 64B/65B encoding of the MAC frame to form code block sequence 3. Wherein each code block in the code block sequence 3 is 65 bits. Then, the first network device processes part of code blocks or all code blocks in the code block sequence 2 (or the code block sequence 3) to obtain a load part of the first message. Illustratively, the payload portion of the first message includes a start (S) code block, a plurality of data (D) code blocks, and an end (T) code block. The S code block and the T code block are used for determining a complete message. The D code block is used for bearing load data in the message.
The second message is introduced as follows: the second message includes data of the hard isolated service. Illustratively, the data of the hard-isolated service in the second message is from the second client. Still referring to fig. 1 as an example, the second client may be a client to which the client device 102 corresponds. The client device 102 sends the service data of the second client to the PE device 105. Accordingly, PE device 105 receives traffic data from a second client of client device 102. The PE device 105 then encapsulates the second customer's service data into a second message.
Illustratively, the second message indicates the message type via a field. For example, the second message includes a second field. The second field indicates the type of the second message, for example, the value of the second field is 0x66.
For example, taking fig. 6c as an example, the second message includes a preamble field, an SFD field, an OH field, a payload field, and a CRC field. Illustratively, as shown in fig. 6c, the second field is carried in the preamble portion of the second message.
For another example, taking fig. 6d as an example, the second field is carried in an OH field of the second message, for example, the second field is carried in the last field in OH, or the second field is carried in the second field in OH, that is, the position of field 1, which is not limited in this embodiment of the present application.
Optionally, the second message further comprises a multiframe indication (multiframe indicator, MFI). Wherein the MFI indicates that the second message is a multiframe. The description of the multiframe is as follows: a multiframe includes a plurality of data units, with different data units corresponding to different time slots. The different data units carry service data transmitted by the corresponding time slots. For example, taking 96 data units as an example, the 1 st data unit carries service data transmitted in the time slot 0, the 2 nd data unit carries service data transmitted in the time slot 1, and so on, until the 96 th data unit carries service data transmitted in the time slot 95, detailed description of the load of the second message will be omitted here. In addition, the data unit may also be described as a basic frame, fine-granularity slot (fgSlot) data, or slot data, etc. In the embodiment of the present application, a data unit is described as an example.
For example, in fig. 6c or 6d, the MFI may occupy 1 field, i.e. 8bits, with a value ranging from 0 to 19. The MFI is carried in the first of the OH fields. Of course, the MFI may also be carried in the second field, or the third field, of the OH fields, which is not limited in this embodiment of the present application.
It should be appreciated that the locations of the first field and the second field in the message may be the same. For example, the first field is carried on the preamble portion of the first message and the second field is also carried on the preamble portion of the second message. For another example, the first field is carried in an OH field of the first message, and the second field is also carried in an OH field of the second message. Alternatively, the first field and the second field may be located differently in the message. For example, the first field is carried in the preamble portion of the first message and the second field is carried in the OH field of the second message. For another example, the first field is carried in an OH field of the first packet, and the second field is carried in a preamble portion of the second packet, which is not limited in the embodiment of the present application.
Illustratively, the load in the second message is described as follows: the load portion comprises one or more data units, as shown in fig. 6e, and the load portion comprises 96 data units, denoted as fgSlot 0-fgSlot 95, respectively.
For different data units, there may be a one-to-one correspondence between data units and clients. That is, one data unit corresponds to one second client, and a different data unit corresponds to a different second client. For example, for different data units, one or more data units may correspond to the same second customer. Different data units carry traffic data transmitted in different time slots. Taking table 1 as an example, table 1 shows 96 client numbers and 96 slot indexes, and the client numbers and the slot indexes are in one-to-one correspondence. The different client number indicates a different second client. Different slot indexes identify different slots.
TABLE 1
In table 1, slot index 0 corresponds to the traffic data of slot transmission client number fgClient0, and slot index 1 corresponds to the traffic data of slot transmission client number fgClient 1. And the other can do so until the slot index 95 corresponds to the traffic data of the slot transmission client number fgClient 95.
In connection with table 1, the payload portion of the second message includes 96 data units, each transmitting traffic data transmitted in one slot. Specifically, the 1 st data unit, i.e. the data unit identified by fgSlot0, transmits service data transmitted by the corresponding slot of the slot index 0, i.e. the service data of the client number fgClient 0. The 2 nd data unit, i.e. the data unit identified by fgSlot1, transmits the service data transmitted by the corresponding time slot of the time slot index 1, i.e. the service data of the client number fgClient 1. And the other can be similar, until 96 th data unit, namely, the data unit identified by fgSlot95, the service data transmitted by the corresponding time slot of the time slot index 95, namely, the service data of the client number fgClient95 is transmitted.
Alternatively, for different data units, there may be many-to-one between the data unit and the client. That is, the plurality of data units corresponds to a second client. For example, in table 2, 48 client numbers and 96 slot indexes are shown, one client number corresponding to two slot indexes.
TABLE 2
Customer number | Time |
fgClient0 | |
0、1 | |
|
2、3 |
… | … |
fgClient46 | 92、93 |
|
94、95 |
In table 2, the time slot indexes 0 and 1 correspond to the time slot to transmit the service data of the client number fgClient0, and the time slot indexes 2 and 3 correspond to the time slot to transmit the service data of the client number fgClient 1. The other can do so until the slot index 94, 95 corresponds to the slot transmitting traffic data for the client number fgClient 47.
In connection with table 2, the payload portion of the second message includes 96 data units, each transmitting traffic data transmitted in one slot. Specifically, the 1 st data unit, i.e. the data unit identified by fgSlot0, transmits service data transmitted by the corresponding slot of the slot index 0, i.e. the service data of the client number fgClient 0. The 2 nd data unit, namely the data unit identified by fgSlot1, transmits the service data transmitted by the corresponding time slot of the time slot index 1, and is also the service data of the client number fgClient 0. And the other can be similar, until 96 th data unit, namely, the data unit identified by fgSlot95, the service data transmitted by the corresponding time slot of the time slot index 95, namely, the service data of the client number fgClient47 is transmitted.
It should be appreciated that table 2 is presented only with two data units corresponding to the same second customer. Of course, three or more data units may correspond to the same second client. Also, for different second clients, the number of data units corresponding to different second clients may be the same, as shown in table 1 or table 2. Alternatively, the number of data units corresponding to different second clients may also be different. For example, the second client identified by the client number fgClient0 corresponds to one data unit, the second client identified by the client number fgClient1 corresponds to two data units, and the second client identified by the client number fgClient2 corresponds to three data units, which is not limited in this embodiment of the present application.
For each data unit, each data unit includes a code block encoded by service data of a corresponding client. Each data unit includes at least one code block therein. For code blocks in the same data unit, the code blocks are encoded by service data of the same customer. The first network device may illustratively employ a coding format of 64B/65B, or 64B/66B and 66B/65B.
For example, taking a data unit, i.e. the first data unit, the process of encapsulating the second message by the first network device is described as follows:
the first network device determines a first code block in the first data unit based on the first information.
Wherein the first information indicates a correspondence between the first data unit and the target client. The first information may be table 1 or table 2. In the embodiment of the present application, the first information is described by taking table 1 as an example. It should be understood that the first information may also have other names, such as a timeslot configuration table of the hard isolation service, which is not limited in the embodiment of the present application.
Illustratively, the first data unit may be the data unit identified by fgSlot0 in Table 1. Accordingly, the target client is the second client identified by client number fgClient 0.
Illustratively, as shown in FIG. 7B, taking the MAC frame of client number fgClient0 as an example, the first network device first encodes the MAC frame by 64B/66B to form code block sequence 4. Wherein each code block in the code block sequence 4 is 66 bits. The first network device then performs a synchronization header compression on the sequence of code blocks 4 to form a sequence of code blocks 5. Wherein each code block in the code block sequence 5 is 65 bits. Alternatively, the first network device performs 64B/65B encoding of the MAC frame to form code block sequence 6. Wherein each code block in the sequence of code blocks 6 is 65 bits. In the code block sequence 5 or the code block sequence 6, each two adjacent code blocks are processed and then carried in the same data unit, namely, the data unit identified by fgSlot 0.
For other data units, the first network device still adopts the above-described processing procedure until 96 data unit determinations in the load portion are completed. Thus, the payload portion of the second message includes 2×96+2 code blocks, specifically, one S code block, a plurality of D code blocks, and one T code block. The S code block and the T code block are used for determining a complete message. The D code block is used for bearing load data in the message.
It should be noted that, the length of the encoded message is the same between the first message and the second message. For example, taking the second packet including 96 data units as an example, the number of code blocks in the first packet and the second packet is 194, and the number of bits in each code block is the same.
S502, the first network device sends a first message and a second message to the second network device in the same period through the first port. Correspondingly, the second network device receives the first message and the second message from the first network device in the same period through the second port.
In fig. 1, for example, in the case where the packet is transmitted from left to right, the second network device may be a PE device 106 or a P device. For example, in the case where the first network device is the PE device 105, the second network device is a P device. For another example, in the case where the first network device is a P device, the second network device is a P device or a PE device 106. In the case of a message transmitted from right to left, the second network device may be a PE device 105 or a P device. For example, in the case where the first network device is PE device 106, the second network device is a P device. For another example, in the case where the first network device is a P device, the second network device is a P device or a PE device 105. In the embodiment of the present application, the first network device is implemented as the PE device 105, and the second network device is implemented as the P device.
Wherein the first port is a port on the first network device, e.g., the first port is a transmit port on the first network device. The second port is a port on the second network device, e.g., the second port is a receiving port on the second network device. In the embodiment of the application, the first port and the second port are different from the message port, and the first port and the second port are different from the time-slotted port. The first port and the second port each have the following characteristics: hard isolation characteristics, and statistical multiplexing characteristics. Because the first port and the second port both have hard isolation characteristics, the first port can be used for sending hard isolation messages, and the second port can be used for receiving hard isolation messages. Since the first port and the second port both have the statistical multiplexing characteristic, the first port can be used for transmitting the plain message, and the second port can be used for receiving the plain message.
The implementation process of S502 includes the following two examples:
in example 1, as shown in the block of mode 1 in fig. 8, S502 includes S502a:
s502a, the first network equipment sends a first message to the second network equipment on a first time unit through the first port according to the second information, and sends a second message to the second network equipment on a second time unit. Correspondingly, the second network device receives the first message from the first network device on the first time unit through the second port according to the second information, and receives the second message from the first network device on the second time unit.
Wherein the first time unit and the second time unit are time units in the same period. Illustratively, a period includes 25 time units. The duration of each time unit is the same, e.g. each time unit comprises 1 time slot.
In the same period of mode 1, the time unit for transmitting the first message is described as a first time unit, and the time unit for transmitting the second message is described as a second time unit. For a message, one time unit means one transmission opportunity.
Wherein the second information indicates the positions of the first time unit and the second time unit in the period, as shown in table 3:
TABLE 3 Table 3
Customer number | Number of time units (units: personal) | Sequence number of time unit in |
0x0001 | ||
3 | 1~3 | |
|
1 | 4 |
|
1 | 5 |
|
5 | 6~10 |
|
2 | 11~12 |
|
3 | 13~15 |
|
1 | 16 |
|
1 | 17 |
|
5 | 18~22 |
|
2 | 23~24 |
|
1 | 25 |
Referring to table 3, table 3 shows port bandwidth configuration for one cycle. Taking a period including 25 time units as an example, a packet formed by encapsulating service data with a client number of 0x0001 occupies 3 time units, i.e. 1 st to 3 rd time units in the period. That is, the message of the client number 0x0001 occupies 3 transmission opportunities in the above period, and is the first 3 transmission opportunities in the above period. The packet formed by encapsulating the service data with the client number 0x0002 occupies 1 time unit, namely the 4 th time unit in the period. That is, the message of the client number 0x0002 occupies 1 transmission opportunity in the above period and is the 4 th transmission opportunity in the above period. In the third row, the second packet encapsulated by the service data with the client number 0x0000 occupies 1 time unit, i.e. the 5 th time unit in the period. Wherein, the client number 0x0000 refers to the second client, only provides the hard isolation service, and the specific client number can be seen in table 1 or table 2. That is, the message of the client number 0x0000 occupies 1 transmission opportunity in the above period and is the 5 th transmission opportunity in the above period. The customer numbers of other rows can be similarly deduced, and will not be described again.
In connection with table 3, taking the first message as the first client message, the second message includes the service data of the second client as an example, the client number of the first client may be one client number from 0x0001 to 0x0007 in table 3, for example, 0x0001. Correspondingly, the first time unit is the first 3 time units in the above-mentioned period. The second customer is identified by 0x0000 in table 3 to characterize a class of customers that provide hard quarantine services. Correspondingly, the second time unit is the time unit of the bold portion of the above-mentioned period.
The first network device sends a first packet encapsulated by the service data of the client number 0x0001 at the 1 st to 3 rd time units in the period and sends a second packet encapsulated by the service data of the second client at the 5 th, 11, 12, 17, 23, 24 th time units in the period according to table 3, as shown in fig. 9 a.
It should be appreciated that table 3 is presented only with the hard isolated traffic and the time cell position of each normal traffic in the cycle fixed as examples. Of course, as another possible implementation, in table 3, only the time cell positions of the hard-isolated service are fixed, and the time cell positions of each of the normal services are not fixed. For example, the hard isolated traffic occupies the 5 th, 11 th, 12 th, 17 th, 23 th, 24 th time units in the above period. The normal service occupies the 1 st to 4 th, 6 th to 10 th, 13 th to 16 th, 18 th to 22 th, and 25 th time units in the above period, but the specific time unit(s) each normal service occupies is not limited.
In this case, the first time unit is the first 3 time units in the above period, and the first message is, for example, a message with a client number of 0x0001, and if only the message with a client number of 0x0001 is encapsulated, the message with other client numbers is not encapsulated, the first network device sends the message with a client number of 0x0001 on the first time unit. Otherwise, if the packet encapsulation of the client number 0x0001 and the client number 0x0002 is completed, the first network device sends the packet on the first time unit according to the preset rule. For example, the preset rule may be a priority of the service, and the message of which client is sent is determined in order of priority from high to low. For example, if the service priority of 0x0001 is higher than the service priority of 0x0002, the first network device sends a message with a client number of 0x0001 on the first time unit according to a preset rule. For another example, the preset rule may be an order of the client numbers, and the order of the client numbers from front to back determines which client's message to send. For example, the client number 0x0001 is arranged before the client number 0x0002, and the first network device sends the message of the client number 0x0001 on the first time unit according to the preset rule. It should be understood that the foregoing description is only given by taking priority or client number ordering as an example, and the preset rule may also have other implementation forms, which is not limited in this embodiment of the present application.
Example 2, as shown in fig. 8 by the block of mode 2, S502 includes S502b:
s502b, the first network device sends a first message to the second network device on an unoccupied first time unit and sends a second message to the second network device on an unoccupied second time unit through the first port according to the second information and the third information. Correspondingly, the second network device receives the first message from the first network device on the unoccupied first time unit through the second port according to the second information and the third information, and receives the second message from the first network device on the unoccupied second time unit.
The first time unit and the second time unit may refer to the description of S502a, which is not repeated herein.
Wherein the second information indicates the number of configurations of the first time unit and the second time unit in the period, as shown in table 4-1:
TABLE 4-1
Customer number | Number of time units (units: units) |
0x0001 | 3 |
|
1 |
0x0000 | 6 |
|
5 |
|
3 |
|
1 |
|
5 |
|
1 |
Referring to table 4-1, table 4-1 shows port bandwidth configurations for one cycle. Taking a period comprising 25 time units as an example, a packet encapsulated by service data with a client number of 0x0001 occupies 3 time units, but the positions of the 3 time units in the period are not indicated. That is, the message of the client number 0x0001 has 3 transmission opportunities in the above period. The packet encapsulated by the service data of the client number 0x0002 occupies 1 time unit, but does not indicate the position of the time unit in the period. That is, the message of the client number 0x0002 has 1 transmission opportunity in the above period. In the third row, the second packet, encapsulated by the service data of the client number 0x0000, occupies 6 time units, but does not indicate the position of the time unit in the period. That is, the message of the client number 0x0000 has 6 transmission opportunities in the above period. Other client numbers can be similarly deduced and will not be described again.
Wherein the third information indicates the unoccupied number of the first time unit and the second time unit in the period, as shown in table 4-2:
TABLE 4-2
Customer number | Unoccupied number of time units (units: personal) |
|
2 |
|
0 |
|
5 |
0x0003 | 4 |
|
2 |
|
0 |
0x0006 | 4 |
|
0 |
Referring to table 4-2, taking an example that one period includes 25 time units, there are 2 unoccupied time units in the first packet formed by encapsulating service data with a client number of 0x0001. That is, there are 2 transmission opportunities in the above cycle for the message of the client number 0x0001. The number of unoccupied time units of the message formed by packaging the business data with the client number of 0x0002 is 0. That is, the message of the client number 0x0002 has no transmission opportunity in the above period. The second message formed by encapsulating the business data with the client number of 0x0000 has 5 unoccupied time units. That is, there are 5 transmission opportunities in the above cycle for the message of the client number 0x 0000. Other client numbers can be similarly deduced and will not be described again.
In connection with table 4-1, taking the first message as the first client message, the second message includes the service data of the second client as an example, the client number of the first client is still 0x0001. Accordingly, the number of configurations of the first time unit is 3. The second customer is identified by 0x0000 in table 4-1 to characterize a class of customers that provide hard quarantine services. Correspondingly, the number of configurations of the second time units is 6. In connection with table 4-2, the number of unoccupied first time cells is 2 and the number of unoccupied second time cells is 5.
The first network device sends the message of the hard isolation service preferentially in order to ensure the low time delay of the hard isolation service.
For example, in the case that the generation time of the second message is the same as that of the first message, the first network device sends the second message first, and then sends the first message. That is, the second time unit in which the second message is located is earlier than the first time unit in which the first message is located. Specifically, in the time unit 1, if the packets of the client number 0x0000 and the client number 0x0001 are already packaged, since the packet of the client number 0x0000 belongs to the hard isolation packet, the first network device sends the packet of the client number 0x0000 on the time unit 1 first, so as to ensure the delay requirement of the hard isolation service. Wherein the position of the time unit 1 in the cycle is shown by a certain dashed box in fig. 9 b. For a packet with a client number of 0x0001 that has been encapsulated, the first network device sends the packet one time unit after time unit 1, e.g., time unit 2. Correspondingly, the time unit 1 is the second time unit, and the time unit 2 is the first time unit. In addition, the first network device updates table 4-2, and the updated table 4-2 indicates that there are 4 time units that are not occupied by the message with the client number 0x0000, that is, there are 4 transmission opportunities for the message with the client number 0x 0000. The updated table 4-2 indicates that there are 1 more time units not occupied by the client number 0x0001 message, i.e., there are 1 more transmission opportunities for the client number 0x0001 message.
For another example, the first network device also sends the second message before sending the first message when the generation time of the second message is earlier than the generation time of the first message. That is, the second time unit in which the second message is located is earlier than the first time unit in which the first message is located. Specifically, in the time unit 1, if the packet with the client number 0x0000 is already encapsulated, but the packet with the client number 0x0001 is not already encapsulated, the first network device sends the packet with the client number 0x0000 on the time unit 1 to ensure the delay requirement of the hard isolation service. The first network device then transmits the message on a time unit, e.g. time unit 2, after time unit 1. Other descriptions may be found in the introduction of the previous paragraph, and are not repeated here.
For another example, when the generation time of the second message is later than the generation time of the first message, the first network device sends the first message first, and then sends the second message. That is, the second time unit in which the second message is located is later than the first time unit in which the first message is located. Specifically, taking time unit 1 as an example, if the packet with client number 0x0000 is not encapsulated, but the packet with client number 0x0001 is encapsulated, the first network device sends the packet with client number 0x0001 on time unit 1. After the packet with the client number 0x0000 is encapsulated, the first network device sends the packet with the client number 0x0000 in a time unit after the time unit 1, for example, in the time unit 2. Correspondingly, time unit 1 is a first time unit, and time unit 2 is a second time unit. In addition, the update of Table 4-2 can be referred to in the previous paragraph, and will not be described here again.
It should be noted that the second information in S502a and S502b is determined based on the service bandwidth of the client. The second information is used for bandwidth allocation of normal traffic and hard isolated traffic at the port level, for example, 25Gbps ports with a division granularity of 1Gbps. The first network device performs bandwidth configuration according to the bandwidth ratio of the hard isolation service to the common service, for example, the bandwidth allocated to the hard isolation service is 2Gbps, and the bandwidth allocated to the common service is 23Gbps. This allocation is indicated in the second information in an equivalent form of time units (or scheduling opportunities). Illustratively, a bandwidth of 23Gbps is equivalent to 23 allocated time units, i.e., 23 transmission opportunities. The bandwidth of 2Gbps is equivalent to 2 allocated time units, i.e., the transmission opportunity is 2 times.
It should be understood that the second information may also have other names, such as a port bandwidth configuration table, which is not limited in the embodiments of the present application.
As shown in fig. 10, in the foregoing modes 1 and 2, as one possible implementation manner, for a normal service, the embodiment of the present application further includes S503 and S504:
s503, the first network device determines a third message.
The third message includes data of the common service. The third message is a message of a third client, and service data of the third client belongs to data of common service. That is, the type of the third message is the same as the type of the first message, that is, the third message also belongs to the general report message. The third message has no requirement on isolation.
For example, still taking table 3 as an example, the client number of the first client is 0x0001, and the packet after the service data package of the client number 0x0001 is the first packet. The client number of the third client is 0x0002, and the message after the business data of the client number 0x0002 is packaged is the third message.
S504, the first network device sends a third message to the second network device in the period through the first port. Correspondingly, the second network device receives the third message from the first network device in the period through the second port.
The first port in S504 and the first port in S502 are the same port, the second port in S504 and the second port in S502 are the same port, and the period in S504 and the period in S502 are the same period, which can be described specifically in S502 and will not be repeated here.
Wherein the third message is transmitted through a third time unit. The third time unit is configured to transmit the message of the first client, and the third time unit is in an idle state.
Wherein the first client message comprises a first message.
For example, taking Table 3 as an example, the third time unit is the 2 nd time unit in the above period. Based on table 3, the 2 nd time unit is configured to send a packet with a client number of 0x0001, but the packet with the client number of 0x0001 is not encapsulated, and the packet with the client number of 0x0002 is encapsulated, so that in order to improve the resource utilization, the first network device sends a packet with a number of 0x0002 on the 2 nd time unit in the period.
For another example, taking Table 4-1 as an illustration, the third time unit is still the 2 nd time unit in the above period. The packet of the hard-isolated service is not encapsulated, in which case the first network device sends a generic packet on the third time unit. The first network device configures a third time unit according to a preset rule for sending a message of which client. For example, the preset rule may be a priority of the service, and is configured in order of priority from high to low. For example, if the traffic priority of 0x0001 is higher than the traffic priority of 0x0002, the third time unit is configured to send a message of 0x 0001. For another example, the preset rule may be an order of the client numbers, and be configured in order of the client numbers from front to back. For example, client number 0x0001 is ordered before client number 0x0002, then the third time unit is configured to send a message of 0x 0001. However, the packet with the client number 0x0001 is not encapsulated, and the packet with the client number 0x0002 is encapsulated, so that in order to improve the resource utilization, the first network device sends the packet with the client number 0x0002 on the 2 nd time unit in the period.
That is, in the process that the first network device sends the general report to the second network device, the characteristic of statistical multiplexing can be achieved, so as to improve the resource utilization rate.
For the second network device, after the second network device performs S502, S505 is also performed:
s505, the second network device forwards the service data in the first message according to the type of the first message, and forwards the service data in the second message according to the type of the second message.
The first message and the type of the first message may refer to the description of S501, and the second message and the type of the second message may refer to the description of S501, which is not repeated herein.
For example, for a certain packet, if the packet is the same as the first packet in the packet type, the second network device executes step 1 and step 2:
For example, if a message carries a first field, the message is a first message, that is, belongs to a general message, and needs to be forwarded by adopting a store-and-forward mode. Store-and-forward may refer to the description of the noun interpretation section and will not be repeated here.
And 2, forwarding the service data in the first message by the second network equipment in a store-and-forward mode.
Illustratively, the second network device queries the destination address based on the first identifier in the first message, and then forwards the service data in the first message according to the queried destination address.
It should be understood that the type of the third message is the same as the type of the first message, so after the second network device performs S504, the second network device may perform step 1 and step 2 described above to forward the third message.
For another example, for a certain packet, if the packet and the second packet are the same in packet type, the second network device executes step 3 and step 4:
and step 3, the second network equipment determines a channel forwarding mode according to the type of the second message.
For example, if a certain message carries a second field, the message is a second message, that is, belongs to a hard isolation message, and needs to be forwarded by adopting a channel forwarding mode. The channel forwarding may refer to the description of the noun interpretation section, and will not be repeated here.
And 4, forwarding the service data of each second client in at least one second client by the second network equipment in a channel forwarding mode.
Wherein the data in the second message includes service data of at least one second client.
The second network device determines, according to the first information, a code block of each second customer service data in the second packet. The code blocks of each second customer service data are then forwarded according to the egress slot table. Wherein the egress slot table indicates the egress port and slot position of each second client.
It should be understood that, in the embodiment of the present application, the number of the messages is not limited, and for example, the number of the first messages may be one or more. The number of the second messages may be one or more. The number of the third messages may be one or more.
It should be noted that, the types of services are different, so are the corresponding clients. The client corresponding to the first message is described as a first client, the client corresponding to the second message is described as a second client, and the first client and the second client are different clients. It should be understood that the first client and the second client may have other names, which are not limited in this embodiment of the present application.
The above description has been presented mainly from the point of interaction between the network elements. Correspondingly, the embodiment of the application also provides a communication device, which can be the network element in the embodiment of the method, or a device containing the network element, or a component applicable to the network element. It will be appreciated that the communication device, in order to achieve the above-described functions, comprises corresponding hardware structures and/or software modules performing the respective functions. Those of skill in the art will readily appreciate that the elements and algorithm steps of the examples described in connection with the embodiments disclosed herein may be implemented as hardware or combinations of hardware and computer software. Whether a function is implemented as hardware or computer software driven hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
By way of example, fig. 11 shows a schematic structural diagram of a communication device 1100. The communication apparatus 1100 includes a processing unit 1101, a transmitting unit 1102, and a receiving unit 1103.
In a possible example, taking the communication apparatus 1100 as the first network device, the processing unit 1101 is configured to support the first network device to perform S501 in fig. 5, and/or other processing operations that the first network device needs to perform in the embodiment of the present application. The receiving unit 1103 is configured to support other receiving operations that the first network device needs to perform. The sending unit 1102 is configured to support the first network device to perform S502 in fig. 5, and/or other sending operations that the first network device needs to perform in the embodiments of the present application.
In another possible example, taking the communication apparatus 1100 as the second network device as an example, the processing unit 1101 is configured to support the second network device to perform S505 in fig. 5, and/or other processing operations that the second network device needs to perform in the embodiment of the present application. The receiving unit 1103 is configured to support the second network device to perform S502 in fig. 5, and/or other receiving operations that the second network device needs to perform in the embodiments of the present application. The sending unit 1102 is configured to support the second network device to perform S505 in fig. 5, and/or other sending operations that the second network device needs to perform in the embodiments of the present application.
Optionally, the communication device 1100 may further include a storage unit 1104 for storing program codes and data of the communication device, and the data may include, but is not limited to, raw data or intermediate data.
The processing unit 1101 may be a processor or controller, such as a CPU, general purpose processor, application specific integrated circuit (application specific integrated circuit, ASIC), field programmable gate array (field programmable gate array, FPGA) or other programmable logic device, transistor logic device, hardware components, or any combination thereof. Which may implement or perform the various exemplary logic blocks, modules, and circuits described in connection with this disclosure. A processor may also be a combination that performs computing functions, e.g., including one or more microprocessors, a combination of a DSP and a microprocessor, and so forth.
The sending unit 1102 may be a communication interface, a sender, or a sending circuit, where the communication interface is generally called, and in a specific implementation, the communication interface may include multiple interfaces, for example may include: a first interface on a first network device, or an interface between a second network device and other devices, and/or other interfaces.
The receiving unit 1103 may be a communication interface, a receiver, or a receiving circuit, where the communication interface is generally called, and in a specific implementation, the communication interface may include multiple interfaces, for example may include: a second interface on a second network device, or an interface between the first network device and other devices and/or other interfaces.
The transmitting unit 1102 and the receiving unit 1103 may be physically or logically implemented as one and the same unit.
The storage unit 1104 may be a memory.
When the processing unit 1101 is a processor, the transmitting unit 1102 and the receiving unit 1103 are communication interfaces, and the storage unit 1104 is a memory, the communication apparatus according to the embodiment of the present application may be as shown in fig. 12.
Referring to fig. 12, the communication device includes: a processor 1201, a communication interface 1202, and a memory 1203. Optionally, the communication device may also include a bus 1204. Wherein the communication interface 1202, the processor 1201 and the memory 1203 may be interconnected via a bus 1204; bus 1204 may be a peripheral component interconnect standard (peripheral component interconnect, PCI) bus or an extended industry standard architecture (extended industry standard architecture, EISA) bus, or the like. The bus 1204 may be classified as an address bus, a data bus, a control bus, or the like. For ease of illustration, only one thick line is shown in fig. 12, but not only one bus or one type of bus.
Optionally, the embodiments of the present application further provide a computer program product carrying computer instructions that, when run on a computer, cause the computer to perform the method described in the above embodiments.
Optionally, the embodiment of the present application further provides a computer readable storage medium, where the computer readable storage medium stores computer instructions, which when executed on a computer, cause the computer to perform the method described in the above embodiment.
Optionally, an embodiment of the present application further provides a chip, including: processing circuitry and transceiver circuitry for implementing the methods described in the above embodiments. Wherein the processing circuit is used for executing the processing actions in the corresponding method, and the transceiver circuit is used for executing the receiving/transmitting actions in the corresponding method.
In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, produces a flow or function in accordance with embodiments of the present application, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by a wired (e.g., coaxial cable, fiber optic, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device including one or more servers, data centers, etc. that can be integrated with the available medium. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., digital video disc (digital video disc, DVD)), or a semiconductor medium (e.g., solid state disk (solid state drive, SSD)), etc.
In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods may be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative, and for example, the division of the modules is merely a logical function division, and there may be additional divisions when actually implemented, for example, multiple modules or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or modules, which may be in electrical or other forms.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of devices. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
From the above description of the embodiments, it will be clear to those skilled in the art that the present application may be implemented by means of software plus necessary general purpose hardware, or of course by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present application may be embodied essentially or in contributing parts in the form of a software product stored in a readable storage medium, such as a floppy disk, a hard disk, or an optical disk of a computer, etc., including several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to perform the methods described in the embodiments of the present application.
The foregoing is merely a specific embodiment of the present application, but the protection scope of the present application is not limited thereto, and the changes or substitutions within the technical scope of the present disclosure should be covered in the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
Claims (27)
1. A method for transmitting a message, comprising:
the method comprises the steps that first network equipment determines a first message and a second message, wherein the first message comprises data of common service, and the second message comprises data of hard isolation service;
the first network device sends the first message and the second message in the same period through a first port of the first network device.
2. The method of claim 1, wherein the first message comprises a first field, wherein the first field indicates a type of the first message;
the second message includes a second field, wherein the second field indicates a type of the second message.
3. The method of claim 2, wherein the first field is carried on a preamble portion of the first message or the first field is carried on an overhead OH field of the first message, and the second field is carried on a preamble portion of the second message or the second field is carried on an OH field of the second message.
4. A method according to any one of claims 1 to 3, wherein the first message further comprises a first identifier, the first identifier being used to identify a first client, the first client's message comprising the first message.
5. The method according to any of claims 1 to 4, wherein the first data unit comprises a first code block;
the first data unit is one or more data units in the second message, the first code block is a code block after service data of a target client is encoded, the target client is one second client in at least one second client, and the data in the second message includes service data of all second clients in the at least one second client.
6. The method of claim 5, wherein the method further comprises:
the first network device determines a first code block in the first data unit according to first information;
wherein the first information indicates a correspondence between the first data unit and the target client.
7. The method according to any one of claims 1 to 6, wherein the first message and the second message have the same message length after encoding.
8. The method of claim 7, wherein the encoding comprises at least one of: 64B/66B, 66B/65B, or 64B/65B.
9. The method according to any one of claims 1 to 8, wherein the first network device sending the first message and the second message in the same period through its first port comprises:
the first network device sends the first message on a first time unit through the first port according to second information, and sends the second message on a second time unit;
wherein the second information indicates the positions of the first time unit and the second time unit in the period.
10. The method according to any one of claims 1 to 8, wherein the first network device sending the first message and the second message in the same period through its first port comprises:
the first network device sends the first message on an unoccupied first time unit and sends the second message on an unoccupied second time unit through the first port according to the second information and the third information;
wherein the second information indicates the number of configurations of the first time unit and the second time unit in the period, and the third information indicates the number of unoccupied first time unit and second time unit in the period.
11. The method of claim 10, wherein a second time unit in which the second message is located is earlier than a first time unit in which the first message is located, and the second message is generated at the same time as the first message, or the second message is generated at a time earlier than the first message;
or the second time unit where the second message is located is later than the first time unit where the first message is located, and the generation time of the second message is later than the generation time of the first message.
12. The method according to any of claims 9 to 11, wherein the second information is determined based on the traffic bandwidth of the first client and the traffic bandwidth of the second client;
the message of the first client comprises the first message, and the data in the second message comprises the service data of the second client.
13. The method according to any one of claims 1 to 12, further comprising:
the first network device determines a third message, wherein the third message is a message of a third client, and the type of the third message is the same as the type of the first message;
The first network device sends the third message in the period through the first port, wherein the third message is transmitted through a third time unit, the third time unit is configured to transmit a message of a first client, the third time unit is in an idle state, and the message of the first client comprises the first message.
14. A method for transmitting a message, comprising:
the second network equipment receives a first message and a second message in the same period through a second port of the second network equipment, wherein the first message comprises data of common service, and the second message comprises data of hard isolation service;
and the second network equipment forwards the service data in the first message according to the type of the first message, and forwards the service data in the second message according to the type of the second message.
15. The method of claim 14, wherein the forwarding, by the second network device, the traffic data in the first message according to the type of the first message, comprises:
the second network equipment determines a store-and-forward mode according to the type of the first message;
And the second network equipment forwards the service data in the first message in the store-and-forward mode.
16. The method of claim 15, wherein the first message comprises a first field, wherein the first field indicates a type of the first message.
17. The method of claim 16, wherein the first field is carried in a preamble portion of the first message or the first field is carried in an overhead OH field of the first message.
18. The method according to any one of claims 14 to 17, wherein the forwarding, by the second network device, the service data in the second message according to the type of the second message includes:
the second network equipment determines a channel forwarding mode according to the type of the second message;
and the second network equipment forwards the service data of each second client in at least one second client in the channel forwarding mode, wherein the data in the second message comprises the service data of all second clients in the at least one second client.
19. The method of claim 18, wherein the second message comprises a second field, wherein the second field indicates a type of the second message.
20. The method of claim 19, wherein the second field is carried in a preamble portion of the second message or the second field is carried in an OH field of the second message.
21. A communication device, comprising: a unit for performing the steps of any one of claims 1 to 13.
22. A communication device, comprising: a processor and a memory coupled, the memory storing program instructions that when executed by the processor, implement the method of any one of claims 1 to 13.
23. A chip comprising logic circuitry for communicating with modules external to the chip and an input-output interface for running a computer program or instructions to implement a method as claimed in any one of claims 1 to 13.
24. A communication device, comprising: a unit for performing the steps of any of claims 14 to 20.
25. A communication device, comprising: a processor and a memory coupled, the memory storing program instructions that when executed by the processor implement the method of any one of claims 14 to 20.
26. A chip comprising logic circuitry for communicating with modules external to the chip and an input-output interface for running a computer program or instructions to implement a method as claimed in any one of claims 14 to 20.
27. A computer readable storage medium storing a program which, when invoked by a processor, performs the method of any one of claims 1 to 20.
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202111332727.6A CN116112452A (en) | 2021-11-11 | 2021-11-11 | Message transmission method and communication device |
PCT/CN2022/130613 WO2023083175A1 (en) | 2021-11-11 | 2022-11-08 | Packet transmission method and communication apparatus |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202111332727.6A CN116112452A (en) | 2021-11-11 | 2021-11-11 | Message transmission method and communication device |
Publications (1)
Publication Number | Publication Date |
---|---|
CN116112452A true CN116112452A (en) | 2023-05-12 |
Family
ID=86258491
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN202111332727.6A Pending CN116112452A (en) | 2021-11-11 | 2021-11-11 | Message transmission method and communication device |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN116112452A (en) |
WO (1) | WO2023083175A1 (en) |
Family Cites Families (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN105897820A (en) * | 2015-10-23 | 2016-08-24 | 乐卡汽车智能科技(北京)有限公司 | Data processing method and device, wireless router and Internet-of-Vehicles system |
CN105978582B (en) * | 2016-06-30 | 2019-03-19 | 深圳优克云联科技有限公司 | A kind of twin-channel communication means of list base band and communication equipment |
CN106453138B (en) * | 2016-11-25 | 2020-03-06 | 新华三技术有限公司 | Message processing method and device |
CN113542155B (en) * | 2017-04-11 | 2023-06-20 | 华为技术有限公司 | Method and device for processing service flow |
CN109995658B (en) * | 2017-12-29 | 2021-07-20 | 华为技术有限公司 | Method and device for sending, receiving and forwarding message |
CN111277454B (en) * | 2020-01-15 | 2021-06-25 | Ut斯达康通讯有限公司 | Network performance detection system and method |
CN113452623B (en) * | 2020-03-26 | 2023-11-14 | 华为技术有限公司 | Method and device for transmitting service flow based on FlexE |
-
2021
- 2021-11-11 CN CN202111332727.6A patent/CN116112452A/en active Pending
-
2022
- 2022-11-08 WO PCT/CN2022/130613 patent/WO2023083175A1/en active Application Filing
Also Published As
Publication number | Publication date |
---|---|
WO2023083175A1 (en) | 2023-05-19 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN111788794B (en) | Method and apparatus for configuring flexible Ethernet nodes | |
CN107438029B (en) | Method and device for forwarding data | |
EP3909209B1 (en) | Ethernet signal format using 256b/257b block encoding | |
CN113972997A (en) | Method and equipment for transmitting data | |
CN109698732B (en) | Method and device for transmitting data | |
WO2019029419A1 (en) | Method and device for pass-through of service frequency | |
US20200288468A1 (en) | Data transmission method and device | |
WO2022183875A1 (en) | Method for determining transmission time slot and related apparatus | |
US6330251B1 (en) | Method and apparatus for data extraction from a bit stream | |
CN110830152B (en) | Method for receiving code block stream, method for transmitting code block stream and communication device | |
US20230299880A1 (en) | Code block identification method and apparatus | |
CN116112452A (en) | Message transmission method and communication device | |
US11451325B2 (en) | Block generation method and apparatus, and block receiving method and apparatus | |
US11902403B2 (en) | Method for receiving code block stream, method for sending code block stream, and communications apparatus | |
CN113330696B (en) | CPRI data block transmission method and equipment | |
CN114629851A (en) | Service message sending method and equipment | |
US11290578B2 (en) | Encapsulating and exchanging bytes in a telecommunication system | |
WO2024032269A1 (en) | Communication method, related apparatus and computer-readable storage medium | |
KR100773904B1 (en) | LAN switch | |
CN114915371A (en) | Communication method, device and chip system | |
CN116015574A (en) | Communication method and device | |
CN117134854A (en) | Service mapping method, device and network equipment | |
JP2021517428A (en) | Data transmission method and transfer device |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PB01 | Publication | ||
PB01 | Publication | ||
SE01 | Entry into force of request for substantive examination | ||
SE01 | Entry into force of request for substantive examination |