WO2009082897A1 - Method and device for multiplexing and demultiplexing ethernet messages - Google Patents

Abstract

The embodiment of the present solution provides a method and device for multiplexing and demultiplexing an Ethernet message, including: receiving the message waiting for encapsulation; when the length of message waiting for encapsulation is less than or equal to the predetermined and maximum allowed transmission length of the sub-message payload unit, determining whether the sum of the length of message waiting for encapsulation and the length of a multiplexed Ethernet message is greater than the predetermined and the Ethernet message maximum allowed transmission length; if yes, encapsulating the previously multiplexed Ethernet message to be sent, and multiplexing said message into a new Ethernet message; otherwise, multiplexing the message to be encapsulated into the sub-message payload unit of the multiplexed Ethernet message, and adding the length of message to be encapsulated to the payload length of the multiplexed Ethernet message so as to obtain the current Ethernet message payload length. The embodiment of the present solution improves inter alia the transmission efficiency of small packet service messages, and enhances the flexibility of the message multiplexing.

Description

 Ethernet message multiplexing, demultiplexing method and device

 The invention belongs to the field of network and communication technologies, and relates to an Ethernet message multiplexing and demultiplexing method and device. Background technique

 As the network is fully IP-based and flattened, the Asynchronous Transfer Mode (ATM) technology has been eliminated, and the synchronous digital series/quasi-synchronous numbers using Point-to-Point Protocol (PPP) technology have been eliminated. The series (Synchronous Digital Hierarchy / Pies iochronous Digital Hierarchy for short SDH/PDH) network is about to stop construction. Ethernet technology has made great progress in metropolitan area network and even wide area network. The use of Ethernet (Ethernet) to carry small packets of wireless voice is a network development. trend.

 A prior art uses a Frame Protocol (FP) multiplexing (Multiplexing, CDMA) technology on the User Datagram Protocol (UDP) layer to implement packet transmission. The FPMux technology is a multiplexing technology that uses the UDP layer between a base station controller (RNC) and a 3G base station (NodeB). As shown in Figure 1, the RNC or NodeB performs FPMux when sending a message and demultiplexing (FP DeMultiplexing, FPDMux for short) when receiving a message. For the NodeB, the NodeB is connected to the upstream RNC through the "Iub" interface. The FPMux operation needs to be implemented in the direction of the data flow sent by the NodeB to the RNC. The number of supported multiplex channels (Channel) = the differentiated service tag supported by the NodeB (Diff serv Code) Point, referred to as DSCP). When receiving downlink data from the RNC, it needs to be able to identify the FPMux packet and the normal non-Mux packet. For the Mux packet, it needs to be properly demultiplexed and processed. The package format of the specific FPMux is shown in Table 1:

Table 1 shows the package format of FPMux Ver HLen TOS 16-bit total length

 16-bit identifier F 13-bit offset

 TTL Protocol 16-bit first calibration - IP and IP

 32^iSIP

 32-bit DIP

 16-bit SPORT 16-bit DP0RT

 UDP

 16-bit UDP length 16-bit UDP checksum

 16-bit UID E length extension Mux head

FP message payload

16-bit UID E length extension

FP message payload

16-bit UID E length extension

The FP packet payload protocol stipulates that the triplet (Source IP, SIP), Destination IP (DIP), DSCP) uniquely identifies a multiplex channel, that is, has the same SIP and DIP. The data stream with the DSCP value is then multiplexed into an FP Mux frame. FP Mux is a technology for multiplexing small packets such as voice on UDP. The IP/UDP header of the message is completely reserved. Each FP payload (payload) is added with a Mux Header. (User Identification, UID for short) is generally the UDP destination port (DPORT).

 This technology has the following drawbacks: Because some IP headers and UDP headers exist at the same time, some network resources are wasted; in addition, since the FPMux technology is compatible with both Ethernet and PPP, the SDH/PDH network using PPP no longer has a development prospect, but for the Ethernet bearer. The network will not need to support PPP, so if it is compatible with PPP, it will waste some network resources.

Another prior art uses Intelligent Time-Division Multiplexing (IT) technology to implement packet transmission. IT Li Technology is based on time division (Time-Division Multiplexing (TDM) technology, can be connected to a variety of networks (including IP network, Public Switched Telephone Network (PSTN) I plain old telephone service (PLAIN OLD TELEPHONE SERVICE, POTS for short) network ) Technology. A schematic diagram of the package structure of the specific IT 丽 field, as shown in FIG. 2 . The description of Figure 2 is as follows: "Li AC" indicates the traditional destination medium access control sub-layer protocol (Media Access Control, MAC address), 6 bytes long; SMAC indicates the traditional source MAC address, 6 bytes long; Ether Type indicates the text The type is ITDM, 2 bytes long; DMAC, SMAC, Ether Type form MAC Header; PAD indicates reserved padding field, 6 bytes long; TAG indicates 2 bytes for ID ID (16-bit Packet ID specifying Jitter) Queue on Destination Node ) and 1 byte sequence 歹 'J number; PKT Type: Indicates whether it is an ordinary IT message or an ITOMMC control message; PAD\TAG, PKT Type constitutes IT 丽 shim; Payload indicates message payload, Payload Each Quad TOM Segment in the package contains 4 TDM Segments and 4 Segment IDs, which are fixed 8 bytes and 2 bytes respectively. When there are 24 TDM Segments in Payload, there can be n=6 Quad TDM Segments accordingly. Up to 148 TDM Segments can be packaged in the Pay load, with up to n=37 Quad TDM Segments.

 In the process of implementing the present invention, the inventor has found that the prior art has at least the following defects: It only supports fixed-length packet encapsulation, and is inflexible; even for voice packets, it needs to occupy multiple T-Segments (the typical length of the voice packet is 22 bytes); does not support message priority; 微Tima technology microcode implementation is more complex, software complexity is high, may require dedicated hardware implementation; network transmission requires E1/T1 similar precision clock guarantee, higher cost . Therefore, the transmission efficiency of packets such as the packet service of the prior art is relatively low. Summary of the invention

 A first aspect of the present invention provides an Ethernet packet multiplexing method and device to improve packet transmission efficiency of packet services.

A second aspect of the present invention provides an Ethernet packet demultiplexing method and device to improve demultiplexing efficiency of an Ethernet message. To implement the foregoing first aspect, an embodiment of the present invention provides an Ethernet packet multiplexing method, including: receiving a packet to be encapsulated; and when the length of the packet to be encapsulated is less than or equal to a sub-packet And determining, by the default maximum allowable length of the packet to be encapsulated, whether the sum of the length of the packet to be encapsulated and the length of the multiplexed Ethernet packet is greater than a preset maximum allowable transmission length of the Ethernet packet; if yes, The multiplexed Ethernet packet is encapsulated and sent by the Ethernet, and the packet to be encapsulated is multiplexed into a new Ethernet packet. If not, the packet to be encapsulated is multiplexed into the multiplexed Ethernet packet. a sub-message payload unit, and the length of the packet to be encapsulated is added to the payload length of the multiplexed Ethernet packet to obtain the payload length of the current Ethernet packet, where the sub-packet net The load unit includes a multiplex header and a sub-message payload, and the multiplex header includes length information of the packet to be encapsulated.

To implement the foregoing first aspect, an embodiment of the present invention further provides an Ethernet packet multiplexing device, including: a first receiving module, a determining module, a first encapsulating module, a multiplexing module, and an accumulating module; The module is configured to receive a packet to be encapsulated, and the determining module is configured to be connected to the first receiving module, and configured to: when determining that the length of the packet to be encapsulated is less than or equal to a preset of the payload unit of the sub-message When the maximum allowable length is used, it is determined whether the sum of the length of the packet to be encapsulated and the length of the multiplexed Ethernet packet is greater than a preset maximum allowable transmission length of the Ethernet packet; When the determining module determines that the sum of the length of the packet to be encapsulated and the length of the multiplexed Ethernet packet is greater than the preset maximum allowable transmission length of the Ethernet packet, the Ethernet packet is encapsulated in the Ethernet packet. And transmitting, the multiplexing module, is configured to: when the determining module determines that the sum of the length of the packet to be encapsulated and the length of the multiplexed Ethernet packet is greater than a preset maximum capacity of the Ethernet packet Transmitting the packet to be encapsulated into a new Ethernet packet, and when the determining module determines the length of the packet to be encapsulated and the length of the multiplexed Ethernet packet. And the packet to be encapsulated is multiplexed into a sub-message payload unit of the multiplexed Ethernet message, and the sub-message is traversed by the preset maximum allowable transmission length of the Ethernet packet. The charging unit includes a multiplexer header and a sub-message payload, the multiplexer header includes length information of the packet to be encapsulated, and an accumulation module, configured to determine, by the judging module, the length of the packet to be encapsulated The length of the packet to be encapsulated is accumulated when the sum of the lengths of the multiplexed Ethernet packets is not greater than the preset maximum allowable transmission length of the Ethernet packet. The payload length of the current Ethernet packet is obtained by the payload length of the multiplexed Ethernet packet. In the foregoing embodiment of the Ethernet packet multiplexing method and device, the multiplexer is added to the front end of each child packet payload to represent the type and length of the service content carried by the child packet payload, and the existing Compared with the UDP/IP header, the network resource is saved and the network resource utilization is improved. Meanwhile, the sub-message payload unit is set according to the actual length of the packet, and the existing method for multiplexing the fixed-length packet is used. In contrast, the use of additional resources is avoided, and the flexibility of message multiplexing is enhanced.

 To implement the foregoing second aspect, an embodiment of the present invention provides an Ethernet packet demultiplexing method, including: receiving an Ethernet packet; extracting a payload length unit and at least one sub-message in the Ethernet packet And the sub-message payload unit includes a sub-message payload and a multiplexing header, where the multiplexer header includes length information of the sub-message payload unit, where the payload length unit includes Determining the payload length of the Ether packet; demultiplexing the payload of the sub-message in the payload unit of the sub-message according to the length information of the payload of the sub-message; determining whether the length of the demultiplexed packet is equal to The length of the payload of the Ethernet packet, if yes, the demultiplexing operation is stopped; otherwise, the next sub-message payload unit is demultiplexed until the length of the demultiplexed packet is equal to the payload length of the Ethernet packet.

 To implement the foregoing second aspect, an embodiment of the present invention further provides an Ethernet packet demultiplexing device, including: a second receiving module, configured to receive an encapsulated Ethernet packet, where the Ethernet packet includes a payload length a unit and at least one sub-message payload unit, where the sub-message payload unit includes a sub-message payload and a multiplexing header, where the multiplex header includes length information of the sub-message payload unit, The load length unit includes a payload length of the Ethernet packet; a first determining module, configured to determine whether a length of the demultiplexed packet is equal to a payload length of the Ethernet packet; and a demultiplexing module, configured to The length information of the sub-packet payload in the multiplexer header in the sub-message payload unit, demultiplexing the sub-message payload in the sub-message payload unit, and when the first judging module When the length of the demultiplexed packet is equal to the payload length of the Ethernet packet, the demultiplexing operation is stopped, and the first determining module determines that the length of the demultiplexed packet is not equal to the payload length of the Ethernet packet. When, continue to solve With the next sub-packet payload unit, until the demultiplexed packet length is equal to the length of the payload of Ethernet packets.

In the foregoing embodiment of the Ethernet packet demultiplexing method and device, directly according to the payload of each sub-packet The type and length information of the service content carried in the multiplexer header of the front end is used to represent the type and length information of the service content carried in the payload of the sub-message to implement demultiplexing of the Ethernet packet, so as to improve the efficiency of multiplexing. DRAWINGS

 1 is a schematic diagram of a multiplexing and demultiplexing process of the prior art;

 2 is a schematic structural diagram of a multiplexing message based on the IT technology in the prior art; FIG. 3 is a schematic structural diagram of an Ethernet message involved in the embodiment of the present invention;

 4 is a schematic diagram of a message multiplexing and demultiplexing process between an RNC and a NodeB based on an Ethernet bearer network according to an embodiment of the present invention;

 FIG. 5 is a flowchart of Embodiment 1 of an Ethernet/Multitext multiplexing method according to the present invention; FIG.

 6 is a flowchart of Embodiment 2 of an Ethernet/Multitext multiplexing method according to the present invention;

 7 is a flowchart of Embodiment 1 of an Ethernet packet demultiplexing method according to the present invention;

 8 is a flowchart of Embodiment 2 of an Ethernet packet demultiplexing method according to the present invention;

 FIG. 9 is a schematic structural diagram of Embodiment 1 of an Ethernet packet multiplexing device according to the present invention;

 FIG. 10 is a schematic structural diagram of Embodiment 2 of an Ethernet packet multiplexing device according to the present invention; FIG. 11 is a schematic structural diagram of Embodiment 3 of an Ethernet packet multiplexing device according to the present invention; FIG. 13 is a schematic structural diagram of Embodiment 1 of an Ethernet packet demultiplexing device according to Embodiment 1 of the present invention; FIG. 14 is a schematic diagram of an Ethernet packet demultiplexing device according to the present invention; FIG. 15 is a schematic structural diagram of Embodiment 3 of an Ethernet de-duplication device according to the present invention. detailed description

 The technical solution of the present invention will be further described in detail below through the accompanying drawings and embodiments. FIG. 3 is a schematic structural diagram of an Ethernet message involved in an embodiment of the present invention. The description of the Ethernet message 3⁄4 below:

1, 丽 AC represents the traditional destination MAC address, 6 bytes long; 1. SMAC indicates a traditional source MAC address, which is 6 bytes long.

 3. VLAN (Virtual Local Area Network) Tag (Optional, optional) indicates the traditional 802. lp/q, 4 bytes long;

 4. The service tag indicates that the message is Ethernet Mux, and provides Quality of Service (QoS) and message order-preserving functions. The description of the internal fields is as follows:

TYPE indicates the payload type, 0x9910, demultiplexing (Lix) flag, 2 bytes long; Pri indicates priority information, similar to DSCP, in this embodiment its length is 3 bits long; Res indicates reserved The length, in the embodiment, is 1 bit long; the sequence indicates the message ordering information, such as the sequence number used for message order, in this embodiment, the length can be 12 bits long; the Total Length is the Ethernet message. a load length unit in which a payload length of an Ethernet message is stored, and the payload length is in units of bytes;

 5, FCS represents the school 3 full sum, for 32-bit Cyclic Redundancy Check (CRC) check, the length of this embodiment is 4 bytes long;

 6. Payload is the payload of the text, 0 - 1496 bytes to meet the Ethernet frame length limit of 64 - 1518 bytes. When the payload length is insufficient, the frame has a Padding field with a maximum of 42 bytes. Each sub-message is multiplexed in the Pay load, and a sub-header Mux Header (3-4 bytes) is added to each sub-book payload, which constitutes a sub-message payload unit, and the receiving device will be based on The Mux Header is demultiplexed. The description of the sub-field of the Mux Header is as follows: The UID indicates the user ID. In this embodiment, it can be 16 bits long. The user can customize according to the service type. E: lbit, indicating whether there is an extended field. Length: 7bit, indicating the net of the sub-message. The length of the load; Extend: 8bit, the user can make a custom extension in Extend; the 4 files that are reused in Pay load can be any type, such as ATM cell or PPP^艮;

 7. Padding (Optional, optional) field. When the payload length in Payload is insufficient, the frame has a Padding field.

In the present embodiment, the payload length is the length information of the packet payload, and in other optional embodiments, the payload length may also be the packet payload and the MN AC, The sum of the lengths of one or several of SMAC, Vlan TAG, Serv i ce Tag, Padding, FCS. The Ethernet packet multiplexing and demultiplexing method of the present invention will be described in detail below by taking the multiplexing and demultiplexing of Ethernet packets between the 3G NodeB device and the RNC device as an example.

 FIG. 4 is a schematic diagram of a packet multiplexing and demultiplexing process between a NodeB and an RNC based on an Ethernet bearer network according to the present invention. As shown in Figure 4, packet multiplexing and demultiplexing between the NodeB and the RNC includes the following aspects:

 1. The NodeB side implements a certain type of service. · Ethernet multiplexing of the text, correspondingly, the RNC side implements Ethernet demultiplexing;

 2. The RNC side implements a certain type of service. · Ethernet multiplexing of the text, correspondingly, the NodeB side implements Ethernet demultiplexing;

 3. Use Ethernet to carry the bearer of the multiplexed message.

 Taking the packet of the voice service, that is, the voice message multiplexing, as an example, the sub-payload in Figure 3 is the voice payload ( Vo i ce Payload ).

 In the NodeB -> RNC direction, multiple packets from the end user are multiplexed into the Pay load on the NodeB, encapsulated according to the packet type and length, and then encapsulated in the common Ethernet, and the Ethernet bearer network performs L2 forwarding. If the TYPE field in the Serv i ce Tag indicates that the message is Etherne t Mux, it will be demultiplexed according to the Mux Header.

 The processing flow in the RNC -> NodeB direction is similar, except that the RNC performs packet multiplexing and encapsulation, and the NodeB performs packet demultiplexing.

An embodiment of the present invention provides an Ethernet packet multiplexing method, including: receiving a packet to be encapsulated; when the length of the packet to be encapsulated is less than or equal to a preset maximum allowable length of the sub-mail payload unit And determining whether the sum of the length of the packet to be encapsulated and the length of the multiplexed Ethernet packet is greater than a preset maximum allowable transmission length of the Ethernet packet, and if yes, performing Ethernet session on the multiplexed Ethernet packet The packet is encapsulated and sent, and the packet to be encapsulated is multiplexed into a new Ethernet packet; if not, the packet to be encapsulated is multiplexed into a packet payload of the multiplexed Ethernet packet. In the message payload unit, the sub-message payload unit includes a multiplex header and a sub-packet payload, and the sub-packet payload carries The multiplexed header includes the length information of the packet to be encapsulated and the user identifier, and adds the length of the packet to be encapsulated to the payload length of the Ethernet packet.

 The length of the packet to be encapsulated is PKT_SIZE, the maximum allowable length of the single Sub Payload is MAX_PAYLOAD_SIZE, the length of the multiplexed Ethernet is OLD_MUX_SIZE, and the maximum allowable transmission length of the Ethernet packet is MTU.

 FIG. 5 is a flowchart of Embodiment 1 of an Ethernet packet multiplexing method according to the present invention. As shown in Figure 5, the Ethernet packet multiplexing method includes the following steps:

 Step 101: Receive a packet to be encapsulated. The packet to be encapsulated in this embodiment takes a voice packet as an example. Step 102: Determine whether Ethernet multiplex (Ethernet Mux) is enabled. If yes, go to step 104. Otherwise, go to step 103.

 Step 103: Perform traditional Ethernet encapsulation and send the voice packet to be encapsulated.

 Step 104: Determine whether the length PKT_S IZE of the voice message to be encapsulated is greater than a preset maximum allowable length of the single child message payload unit, MAX_PAYLOAD_SIZE, and if yes, execute step 105; otherwise, execute step 106;

 Step 105: Perform Ethernet encapsulation on the multiplexed Ethernet packet and send it, and perform traditional Ethernet encapsulation and transmission on the voice packet to be encapsulated. Specifically, the method includes the following steps: Step 1051: Perform Ethernet encapsulation on the multiplexed Ethernet packet and send the packet. Step 1042: Perform traditional Ethernet encapsulation and send the voice packet to be encapsulated.

 Step 106: Determine whether the sum of the length PKT_S IZE of the voice message to be encapsulated and the length of the multiplexed Ethernet message 0LD_MUX_SIZE is greater than the preset maximum allowable transmission length MTU of the Ethernet message; if yes, go to step 107; If no, step 108 is performed.

 In step 107, the multiplexed Ethernet packet is encapsulated and sent by the Ethernet, and the packet to be encapsulated is multiplexed into a new Ethernet packet. The method includes the step 1071: performing the multiplexed Ethernet > 3⁄4 text. The Ethernet encapsulates and sends the packet. Step 1072: The packet to be encapsulated is multiplexed into a new Ethernet packet.

Step 108: The message to be encapsulated is multiplexed into a sub-message payload unit of the multiplexed Ethernet message. The sub-message payload unit includes a multiplex header and a sub-packet payload, and the sub-packet payload carries the The multiplexed header includes the length information of the voice packet to be encapsulated, and may further include a user identifier of the voice packet to be encapsulated.

 Step 109: The length of the voice message to be encapsulated is added to the payload length of the multiplexed Ethernet message to obtain the current payload length of the Ethernet message. That is, the length of the voice packet to be encapsulated is added to the Tota l Length field in the service tag.

 The foregoing steps 101-109 are a complete process of multiplexing a voice message to be encapsulated into an Ethernet message. When receiving more than one packet, such as a voice packet but not limited to a voice packet, you can set a timer in the device that receives the packet. If no new packet arrives after the timeout, the Ethernet packet is sent. Encapsulate and send.

 FIG. 6 is a flowchart of Embodiment 2 of an Ethernet multiplexing method according to the present invention. As shown in FIG. 6, the embodiment is different from the previous embodiment in that after the step 109, the method further includes:

 Step 110: Start a timer.

 Step 111: Determine whether to time out according to the timer. If the timeout has not expired, continue to receive a new packet, and perform step 101; if timeout, execute step 112.

 Step 112: Encapsulate and send the currently multiplexed Ethernet packet.

 In the foregoing embodiment of the Ethernet packet multiplexing method, the payload length of the Ethernet packet may also be carried in the state identifier information Servi ce Tag of the Ethernet packet as shown in FIG. 3.

As shown in Figure 3, the structure of the Ethernet packet can also carry the following information or a combination of the following information in the service tag information Service Tag: The multiplexing type information TYPE of the Ethernet packet, the reused Ethernet packet The priority information Pr i of the text, or the order information Sequence of the multiplexed Ethernet message. Before the Service TAG includes the TYPE, the Pr, and the Sequence, the method further includes: setting the multiplexing type information of the Ethernet packet to the Ethernet packet in the Service Tag, that is, Ethernet multiplexing, that is, The TYPE in the specified Service Tag is 0x9910, and the value can be customized. The priority information pr i of the multiplexed Ethernet packet can be set in the Service Tag, and the pr i can be specified according to the QoS requirement. The specification can be specified according to the message ordering requirements. The setting steps of the above three parameters are not limited. FIG. 7 is a flowchart of Embodiment 1 of an Ethernet packet demultiplexing method according to the present invention. As shown in FIG. 7, the Ethernet packet demultiplexing method includes the following steps:

 Step 201: Receive an Ethernet message.

 Step 202: Determine whether the multiplexing type information TYPE in the Ethernet message is Ethernet multiplexing. If not, go to step 203; if yes, go to step 204. In this embodiment, it is determined whether the TYPE in the Serv i ce Tag is 0x9910.

 Step 203: Demultiplexing the etheric object by using an ordinary Ethernet demultiplexing method.

 Step 204: Extract a payload length unit and at least one sub-message payload unit in the Ethernet packet, where the sub-message payload unit includes a sub-packet payload and a multiplexing header, where the multiplexing header is The length information of the sub-message payload unit is included, and the payload length unit includes a payload length of the Ethernet packet.

 Step 205: Demultiplex the sub-message payload in the sub-message payload unit according to the length information of the sub-message payload. The service content carried in the sub-packet payload "Sub Pay load" in the payload unit of the sub-packet is demultiplexed according to the length of the payload of the sub-message in the Mux Header in the sub-message payload unit.

 Step 206: Send the service content to a corresponding upper application according to a user identifier UID in the multiplex header Mux Header for processing.

Step 207: Determine whether the length of the demultiplexed packet is equal to the payload length of the Ethernet packet. If yes, go to step 208. Otherwise, go to step 205 to continue demultiplexing the next sub-packet in the Ethernet packet. The length of the packet until the demultiplexed packet is equal to the payload length of the Ethernet packet. Demultiplexing includes: demultiplexing of the payload of the message and demultiplexing of information related to the multiplexed message. The demultiplexing of the message payload demultiplexes the payload of the sub-message in the payload of the message. The information related to the multiplexing message includes MAC, Vlan TAG, Serv ce Tag, Padding and FCS. In this embodiment, since the payload length in the Ethernet packet is the length information of the payload of the packet payload, it is only necessary to compare whether the total length of the demultiplexed sub-message payload unit is equal to the payload length. . In other optional implementation manners, the payload length may also be information related to the packet payload and the foregoing multiplexing packet. (DMAC, SMAC, Vlan TAG, Service Tag, Padding, FCS) The sum of the lengths of one or several of the packets, so in the comparison process, it is judged whether the length of the packet that has been taken is equal to the payload length of the Ethernet packet. To determine whether the total length of the demultiplexed sub-message payload unit plus the length of the multiplexed packet related information is equal to the payload length of the Ethernet packet.

 Step 208: Stop the demultiplexing operation of the current Ethernet message.

 When the priority information of the multiplexed Ethernet message is set in the service flag unit of the Ethernet packet, before the sub-message payload in the demultiplexing sub-mail payload unit, the method further includes: according to the priority Information is classified and prioritized.

 When the order information of the multiplexed Ethernet message is set in the service flag unit of the Ethernet packet, before the sub-message payload in the demultiplexing sub-mail payload unit, the method further includes: Information is processed in order.

 FIG. 8 is a flowchart of Embodiment 2 of an Ethernet demultiplexing method according to the present invention. The difference between this embodiment and the previous embodiment is that the flow classification and priority scheduling operations and the order-preserving processing operations are added. Specifically, between step 202 and step 204, the method further includes:

 Step 209: Perform flow classification and priority scheduling according to the priority information Pr i in the service tag information Service Tag. When the upper layer application specifies that the QoS is deployed according to the priority, the traffic classification and priority scheduling are performed according to the priority information Pr i in the service tag information Service Tag, such as QoS based on simple traffic classification or complex traffic classification.

Step 210: Perform a sequence-preserving process according to the order-preserving information Sequence in the service tag information Service Tag. When the upper layer application specifies the sequence number of the used message, the sink can correct the order of the received message according to the serial number. The message with the smaller serial number will be processed by the upper application first, and the TCP similarity can also be provided. Frame loss detection and retransmission mechanism. The packet described in the foregoing embodiment is not limited to the packet service carried by the Ethernet bearer network, such as the wireless voice service. The packet may also be included in the network such as the SDH/PDH network, the ATM network, and the PSTN/POTS, and is provided on the Ethernet. The bearer of PPP (PPP over Etherne t, PPPoE for short) and ATM over Ethernet (ATMoE for short) is multiplexed and encapsulated at the transmitting end and demultiplexed at the receiving end. Various networks The access device and the server device connected to the Ethernet bearer network are core devices. Take the above ATM network as an example. The main functions include:

 1. Multiple ATM units (ce l l ) are multiplexed into Ethernet packets when they are out of the ATM network;

 2. On the server side, implement demultiplexing of Ethernet packets to obtain ATM ce l h

 The multiplexed packet (or ce ll ) is encapsulated in the Ethernet packet on the device (or server) that the source network accesses the Ethernet bearer network, and the bearer network performs normal L2 forwarding according to the MAC address, and receives the network access device (or Demultiplexing on the server).

 ATM ce l l , ΡΡΡ ·^ and ordinary IP files can be multiplexed in this mode and transmitted on the Ethernet bearer network, and demultiplexed at the receiving end to provide a transmission mode similar to ATMoE and PPPoE.

 FIG. 9 is a schematic structural diagram of Embodiment 1 of an Ethernet/Multitext multiplexing device according to the present invention. As shown in FIG. 9, the method includes: a first receiving module 11, a determining module 12, a first encapsulating module 13, a multiplexing module 14, and an accumulating module 15; wherein, the first receiving module 11 is configured to receive a packet to be encapsulated; The judging module 12 is connected to the first receiving module 11. When it is determined that the length of the packet to be encapsulated is less than or equal to the preset maximum allowable length of the sub-mail payload unit, the judging module 12 continues to determine the packet to be encapsulated. Whether the sum of the length and the length of the multiplexed Ethernet message is greater than a preset maximum allowable transmission length of the Ethernet message;

 If yes, the first encapsulating module 13 is invoked, and the multiplexed Ethernet packet is encapsulated and sent by the Ethernet, and the multiplexing module 14 is invoked to multiplex the packet to be encapsulated into a new Ethernet packet.

 If not, the multiplexing module 14 is invoked, and the packet to be encapsulated is multiplexed into a sub-message payload unit of the multiplexed Ethernet message, where the sub-message payload unit includes a multiplexing header and a sub-port. a payload of the packet, the payload of the sub-packet carrying the packet to be multiplexed, the multiplexing header includes length information of the packet to be encapsulated, and a user identifier; and the accumulating module 15 is called to encapsulate the packet to be encapsulated. The length of the packet is added to the payload length of the multiplexed Ethernet packet to obtain the payload length of the current Ethernet packet. In this embodiment, the multiplexer header in the sub-message payload unit may further include a user identifier of the packet to be encapsulated.

That is, the judging module 12 is connected to the first receiving module 11 and is configured to continue to determine the to-be-suppressed when it is determined that the length of the packet to be encapsulated is less than or equal to the preset maximum allowable length of the sub-packet payload unit. Whether the sum of the length of the loaded message and the length of the multiplexed Ethernet message is greater than a preset maximum allowable transmission length of the Ethernet message;

 The first encapsulating module 13 is configured to: when the judging module 12 determines that the sum of the length of the packet to be encapsulated and the length of the multiplexed Ethernet packet is greater than the preset maximum allowable transmission length of the Ethernet packet, The Ethernet packet is encapsulated and sent by the Ethernet packet;

 The multiplexing module 14 is configured to: when the determining module 12 determines that the sum of the length of the packet to be encapsulated and the length of the multiplexed Ethernet packet is greater than the preset maximum allowable transmission length of the Ethernet packet, the packet to be encapsulated The text is multiplexed into a new Ethernet message, and is used by the determining module 12 to determine that the sum of the length of the packet to be encapsulated and the length of the multiplexed Ethernet message is not greater than the preset maximum tolerance of the Ethernet message. When the transmission length is used, the packet to be encapsulated is multiplexed into a sub-message payload unit of the multiplexed Ethernet packet, and the sub-message payload unit includes a multiplex header and a sub-packet payload, and the multiplex header The length information of the packet to be encapsulated is included;

 The accumulating module 15 is configured to: when the judging module 12 determines that the sum of the length of the packet to be encapsulated and the length of the multiplexed Ethernet packet is not greater than a preset maximum allowable transmission length of the Ethernet packet, the packet to be encapsulated The length of the text is added to the payload length of the multiplexed Ethernet packet to obtain the payload length of the current Ethernet packet.

 FIG. 10 is a schematic structural diagram of Embodiment 2 of an Ethernet packet multiplexing device according to the present invention. As shown in FIG. 10, the embodiment is different from the foregoing embodiment of the Ethernet device in the Ethernet packet. The first extension module 16 is further configured to set the Ethernet packet in the service identifier unit of the Ethernet packet. The multiplexing type information is Ethernet multiplexing; and may further include a second extension module, configured to set priority information of the multiplexed Ethernet message in a service flag unit of the Ethernet message; and may further include a third extension The module 18 is configured to set the order information of the multiplexed Ethernet message in the service flag unit of the Ethernet message.

When receiving more than one packet, a timer sub-module can be set in the device that receives the packet. When no new packet arrives after the timeout, the Ethernet packet is encapsulated and sent. FIG. 11 is a schematic structural diagram of Embodiment 3 of an Ethernet multiplex device according to the present invention. As shown in FIG. 11, this embodiment The difference between the foregoing embodiment of the Ethernet packet multiplexing device is that the determining module 12 further includes a timed submodule 1201, and the accumulating module 15 adds the length of the packet to be encapsulated to the multiplexed Ethernet message. After the payload length of the current Ethernet packet is obtained, the timing sub-module 1201 starts counting. When no packet arrives at the first receiving module 11 within a predetermined time, the first encapsulating module 13 , the Ethernet packet that is currently multiplexed is encapsulated and sent by Ethernet.

 FIG. 12 is a schematic structural diagram of Embodiment 4 of an Ethernet packet multiplexing device according to the present invention. As shown in FIG. 12, in this embodiment, the difference from the first embodiment of the Ethernet device is as follows: the second module module 19 is further included, and the determining module 12 determines the length of the packet to be encapsulated. When the maximum allowable length of the sub-message payload unit is greater than the preset maximum allowable length of the sub-packet payload unit, the first encapsulation module 13 is invoked, and the multiplexed Ethernet packet is encapsulated and sent by the Ethernet, and the second encapsulation module 19 is invoked. The message is encapsulated and sent in traditional Ethernet.

FIG. 13 is a schematic structural diagram of Embodiment 1 of an Ethernet packet demultiplexing device according to the present invention. As shown in FIG. 13 , the method includes: a second receiving module 21, configured to receive an encapsulated Ethernet packet, where the Ethernet packet may include a payload length unit and at least one sub-post payload unit, and the sub-message payload unit The sub-message payload and the multiplexing header are included, and the multiplexer header includes the length information of the sub-message payload unit, the payload length unit includes the payload length of the Ethernet packet, and the demultiplexing module 22 and the second receiving module 21 a connection, configured to demultiplex the sub-message payload in the sub-message payload unit according to the length information of the sub-message payload in the multiplexer header in the sub-message payload unit; the first determining module 24 And connecting to the demultiplexing module 22, determining whether the length of the demultiplexed packet is equal to the payload length of the Ethernet packet, and if so, stopping the demultiplexing operation; otherwise, calling the demultiplexing module 22 to continue demultiplexing The next child message payload unit, until the sum of the lengths of the demultiplexed messages is equal to the payload length of the Ethernet message. That is, the first determining module 24 is configured to determine whether the length of the demultiplexed packet is equal to the payload length of the Ethernet packet; the demultiplexing module 22 is configured to use the sub-header in the multiplex header in the sub-message payload unit. The packet payload length information is used to demultiplex the sub-packet payload in the sub-packet payload unit, and when the first judging module 24 determines that the length of the demultiplexed packet is equal to the payload length of the Ether packet Stop the demultiplexing operation. When the first determining module 24 determines that the length of the demultiplexed packet is not equal to the payload length of the Ethernet packet, continue to demultiplex the next one. The child message payload unit, until the length of the demultiplexed message is equal to the payload length of the Ethernet message. The Ethernet packet demultiplexing device in this embodiment further includes a sending module 23, which is connected to the demultiplexing module 22, and is configured to send the service content to the corresponding upper layer application for processing according to the user identifier in the multiplexing header.

 FIG. 14 is a schematic structural diagram of Embodiment 2 of an Ethernet demultiplexing device according to the present invention. As shown in FIG. 14, the difference between the embodiment and the foregoing embodiment of the Ethernet demultiplexing device is that the priority scheduling module 25 may be further included, and the used service flag unit of the Ethernet packet is configured to be multiplexed. When the priority information of the Ethernet packet is used, the traffic classification and priority scheduling are performed according to the priority information before the sub-message payload in the sub-message payload unit is demultiplexed. The preamble processing module 26 may be further configured to: when the order information of the multiplexed Ethernet message is set in the service flag unit of the Ethernet message, the sub-message used in the demultiplexing sub-mail payload unit Before the payload, the order-preserving process is performed according to the order-preserving information.

 FIG. 15 is a schematic structural diagram of Embodiment 3 of an Ethernet packet demultiplexing device according to the present invention. As shown in FIG. 15, the embodiment is different from the foregoing embodiment of the Ethernet packet demultiplexing device in that the second determining module 27 is further connected to the second receiving module 21, and is set in the service marking unit of the Ethernet message. When the multiplexing type information of the Ethernet packet is Ethernet multiplexing, the second determining module 27 is configured to use the multiplexing type information according to the multiplexing type information before demultiplexing the sub-message payload in the sub-message payload unit. Determining whether the multiplexing type of the Ethernet packet is Ethernet multiplexing, and if so, calling the demultiplexing module 22, according to the length information of the payload of the sub-packet in the multiplexing header in the payload unit of the sub-message, The sub-message payload in the sub-message payload unit is demultiplexed.

 In the above embodiment of the present invention, a method for directly multiplexing multiple packets into an Ethernet packet and performing Layer 2 transmission on the Ethernet bearer network is provided, and the UDP/IP header is no longer used, and one packet is added before each packet. The multiplex header Mux Header is used to characterize the type and length of the service content carried by the payload of the message, and the EtherType field of the traditional Ethernet is extended to TYPE to support Etherne t Mux frame identification, QoS, and language preservation, and supports traditional 802. lp/q is packaged with normal Ethernet.

In summary, the present invention has the following advantages: (1) Further improving transmission efficiency, enhancing flexibility, QoS characteristics, and achieving simpler implementation, further reducing development and operation costs;

 (2) The IP header/UDP header is removed, and a multiplex header Mux Header is added in front of each message to characterize the type and length of the service content carried by the packet payload, and the prior art is fixed. The problem of length payload transmission, thereby saving network resources and improving network resource utilization;

 (3) For a small packet service that can be multiplexed in a large amount, a manner of carrying various types of network type messages for multiplexing transmission is provided.

 A person skilled in the art can understand that all or part of the steps of implementing the above method embodiments may be completed by using hardware related to program instructions, and the foregoing program may be stored in a computer readable storage medium, and the program is executed when executed. The steps of the foregoing method embodiments are included; and the foregoing storage medium includes: a medium that can store program codes, such as a ROM, a RAM, a magnetic disk, or an optical disk.

 It should be noted that the above embodiments are only for explaining the technical solutions of the present invention, and are not intended to be limiting; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those skilled in the art that: The technical solutions described in the foregoing embodiments are modified, or some of the technical features are equivalently replaced. The modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

Claim 1. An Ethernet "3⁄4" multiplexing method, characterized in that it comprises:  Receiving a packet to be encapsulated;  When the length of the packet to be encapsulated is less than or equal to the preset maximum allowable length of the sub-message payload unit, the sum of the length of the packet to be encapsulated and the length of the multiplexed Ethernet packet is determined. Whether it is greater than the preset maximum allowable transmission length of the Ethernet message;  If yes, the multiplexed Ethernet packet is encapsulated and sent by the Ethernet, and the message to be encapsulated is multiplexed into a new Ethernet packet;  If not, the packet to be encapsulated is multiplexed into a sub-message payload unit of the multiplexed Ethernet packet, and the length of the packet to be encapsulated is added to the multiplexed Ethernet packet. The payload length is the payload length of the current Ethernet packet, where the sub-message payload unit includes a multiplex header and a sub-packet payload, and the multiplex header includes length information of the packet to be encapsulated.  2. The method according to claim 1, wherein the multiplexing header further comprises a user identifier of the file to be encapsulated.  The method according to claim 1, wherein after the length of the packet to be encapsulated is added to the payload length of the multiplexed Ethernet packet to obtain the payload length of the current Ethernet packet, the method further includes: When no next message arrives within a predetermined time, the currently multiplexed Ethernet text is encapsulated and sent by the Ethernet.  The method according to claim 1, wherein when the length of the packet to be encapsulated is greater than a preset maximum allowable length of the payload unit of the sub-message, the multiplexed Ethernet message is performed. The method according to claim 1, wherein the Ethernet message further includes a service marking unit, the service marking unit is provided with multiplexing type information, and the multiplexing type information is used to indicate the Whether the reuse type of the etheric text is Ethernet multiplexing. The method according to claim 1, wherein the Ethernet message further includes a service marking unit, the service marking unit is provided with priority information, and the priority information is used to refer to Performs traffic classification and priority scheduling on the multiplexed Ethernet packets.  The method according to claim 1, wherein the Ethernet message further includes a service marking unit, wherein the service marking unit is provided with a preservation information, and the preservation information is used to indicate that the pair is multiplexed The etheric message is processed in order.  8. An ethernet demultiplexing method, characterized in that:  Receiving an Ethernet message;  Extracting a payload length unit and at least one sub-message payload unit in the Ethernet packet, where the sub-message payload unit includes a sub-packet payload and a multiplexing header, where the multiplexing header includes the The length information of the sub-message payload unit, the load length unit includes a payload length of the Ethernet packet; and demultiplexing the sub-message payload unit neutron according to the length information of the sub-message payload Message payload  Determining whether the length of the demultiplexed message is equal to the payload length of the Ethernet message, and if yes, stopping the demultiplexing operation; otherwise, continuing to demultiplex the next sub-message payload unit until demultiplexed The length of the packet is equal to the payload length of the Ethernet packet.  The method according to claim 8, wherein the multiplexing header further includes a user identifier of the encapsulated packet, and the demultiplexing the payload of the sub-text in the sub-text payload unit Then, the method further includes: sending the service content to the corresponding upper application according to the user identifier in the multiplexing header for processing.  The method according to claim 8, wherein the Ethernet message further includes a service marking unit, the service marking unit is provided with multiplexing type information, and the extracting sub-mail payload unit is The method further includes: determining, according to the multiplexing type information, whether the multiplexing type of the Ethernet message is Ethernet multiplexing.  The method according to claim 8, wherein the Ethernet message further includes a service marking unit, wherein the service marking unit is provided with priority information, and is in the demultiplexing sub-mail payload unit. The sub-message payload further includes: performing traffic classification and priority scheduling on the multiplexed Ethernet packets according to the priority information. The method according to claim 8, wherein the Ethernet message further includes a service flag unit, where the service flag unit is provided with the preserving information, and before the sub-message payload in the demultiplexing sub-message payload unit, the method further includes: multiplexing the used Ethernet message according to the order-preserving information The text is processed in order.  An Ethernet packet multiplexing device, comprising: a first receiving module, a determining module, a first encapsulating module, a multiplexing module, and an accumulating module;  a first receiving module, configured to receive a packet to be encapsulated;  The determining module is connected to the first receiving module, and is configured to continue to determine the to-be-packaged when it is determined that the length of the packet to be encapsulated is less than or equal to a preset maximum allowable length of the sub-message payload unit. Whether the sum of the length of the packet and the length of the multiplexed Ethernet packet is greater than the preset maximum allowable transmission length of the Ethernet packet;  a first encapsulating module, configured to: when the determining module determines that the sum of the length of the packet to be encapsulated and the length of the multiplexed Ethernet packet is greater than a preset maximum allowable transmission length of the Ethernet packet, The Ethernet packet is encapsulated and sent by the Ethernet packet;  a multiplexing module, configured to: when the determining module determines that the sum of the length of the packet to be encapsulated and the length of the multiplexed Ethernet packet is greater than a preset maximum allowable transmission length of the Ethernet packet, The encapsulated packet is multiplexed into a new Ethernet packet, and is used by the determining module to determine that the sum of the length of the packet to be encapsulated and the length of the multiplexed Ethernet packet is not greater than that of the Ethernet packet. When the maximum allowable transmission length is set, the packet to be encapsulated is multiplexed into a sub-message payload unit of the multiplexed Ethernet packet, where the sub-message payload unit includes a multiplexing header and a sub-packet. a packet payload, where the multiplexing header includes length information of the packet to be encapsulated;  An accumulating module, configured to: when the determining module determines that the sum of the length of the packet to be encapsulated and the length of the multiplexed Ethernet packet is not greater than a preset maximum allowable transmission length of the Ethernet packet, The length of the encapsulated packet is added to the payload length of the multiplexed Ethernet packet to obtain the payload length of the current Ethernet packet. The device according to claim 13, wherein the determining module includes a timing sub-module, configured to: when the accumulating module accumulates the length of the packet to be encapsulated into the multiplexed Ethernet report After the payload length of the text obtains the payload length of the current Ethernet packet, the timing starts, and the first encapsulation module is notified when the predetermined time is reached;  The first encapsulating module performs Ethernet encapsulation and transmission on the currently multiplexed Ethernet packet when no next packet arrives at the receiving module within a predetermined time.  The device according to claim 13, further comprising a second encapsulating module, a preset maximum allowable length, and the first encapsulating module performs Ethernet encapsulation on the multiplexed Ethernet packet and The device according to claim 13, further comprising a first extension module, configured to set multiplexing type information in a service flag unit of the Ethernet message, where the multiplexing type information is used to indicate Whether the reuse type of the etheric text is Ethernet multiplexing.  The device according to claim 13, further comprising a second extension module, configured to set priority information in a service flag unit of the Ethernet message, where the priority information is used to indicate that the pair has been restored. The Ethernet packets are used for traffic classification and priority scheduling.  The device according to claim 13, further comprising a third extension module, configured to set a hold order information in the service identifier unit of the Ethernet message, where the save order information is used to indicate that the pair has been restored The etheric message is used for order preservation.  19. An Ethernet de-duplication device, characterized in that:  a second receiving module, configured to receive the encapsulated Ethernet packet, where the Ethernet packet includes a payload length unit and at least one sub-message payload unit, where the sub-message payload unit includes a sub-packet payload and a complex a header, the multiplexer header includes length information of the sub-message payload unit, where the payload length unit includes a payload length of the Ethernet packet;  a first determining module, configured to determine whether a length of the demultiplexed packet is equal to a payload length of the Ethernet packet; a demultiplexing module, configured to demultiplex a sub-message payload in the payload unit of the sub-message according to length information of a sub-message payload in a multiplexer header in a sub-message payload unit, And when the first judgment When the module determines that the length of the demultiplexed packet is equal to the payload length of the Ethernet packet, the demultiplexing operation is stopped, and the first determining module determines that the length of the demultiplexed packet is not equal to the payload of the Ethernet packet. If the length is longer, the next sub-message payload unit is demultiplexed until the length of the demultiplexed packet is equal to the payload length of the Ethernet packet.  The device according to claim 19, further comprising a sending module, connected to the demultiplexing module, configured to send the service content to the corresponding upper application according to the user identifier in the multiplexing header for processing.  The device according to claim 19, further comprising a second determining module, connected to the second receiving module, when the multiplexing type information set in the service marking unit of the Ethernet message is Ethernet multiplexing, Before demultiplexing the sub-message payload in the sub-message payload unit, the second judging module is configured to determine, according to the multiplexing type information, whether the multiplexing type of the Ethernet text is Ethernet multiplexing The demultiplexing module is configured to perform a demultiplexing operation when the second determining module determines that the multiplexing type of the Ethernet message is Ethernet multiplexing.  The device according to claim 19, further comprising a priority scheduling module, configured to: when the priority information is set in the service flag unit of the Ethernet message, used to demultiplex the sub-mail payload unit Before the sub-message payload, the traffic classification and priority scheduling are performed according to the priority information.  The device according to claim 19, further comprising a sequence processing module, configured to: when the order information is set in the service flag unit of the Ethernet message, used to demultiplex the child message payload unit Before the sub-message payload, the order-preserving processing is performed according to the order-preserving information.