Frame format analysis method and device of MAC layer multicast data frame based on HINOC system

[0042] The following description and the accompanying drawings fully illustrate the specific embodiments of the invention to enable those skilled in the art to practice them.

[0043] It should be clear that the described embodiments are merely the embodiments of the invention, not all of the embodiments. Based on the embodiments in the present invention, those of ordinary skill in the art will belong to the scope of the present invention in the scope of the present invention without any other embodiments obtained without creative labor.

[0044] Based on the existing parsing method, a problem with the frame format of the MAC layer multicast data frame is less resolved. In this application, the present application provides a frame format parsing method based on the Hinoc system based MAC layer multicast data frame. Apparatus to solve problems existing in the above-described related art issues. In the technical solution provided by the present application, the type information and MAC layer multicast data frames of each HM terminal device communicating with the HB are acquired; parsing the type information, obtaining each HM terminal device for communication with the HB local Type; parsing method for parsing the frame format of the MAC layer multicast data frame according to the type configuration of each HM terminal device, the resolution method includes the first resolution and HinoC2 matching the Hinoc3.0 HM terminal device. 0 HM terminal device matches the second resolution; according to the type of the current HM terminal device, the frame format of the MAC layer multicast data frame is parsed by the analysis method of the current HM terminal device to obtain the corresponding parsing result. Therefore, the parsing method provided in this application example is pre-paid according to the analysis of the frame format of the MAC layer multicast data frame according to the type configuration of the respective HM terminal devices, and the resolution method includes the Hinoc3.0 HM terminal device. Matching the first resolution and the second parsing method that matches the HinoC2.0 HM terminal device, since the parsing method is not only suitable for HinoC2.0 HM terminal devices that communicate with the HB local part, it is also suitable for adoption Hinoc3.0 HM terminal equipment for communication with the HB local end, can be achieved: for different types of HM terminal devices, for example, HinoC3.0 HM terminal equipment, HinoC2.0 HM terminal device for synchronization and parallel compatibility analysis The frame format of the MAC layer multicast data frame, so that the parsing efficiency of the frame format of the MAC layer multicast data frame is ultimately effectively improved, and the exemplary embodiment will be described in detail below.

[0045] The following will be combined Figure 1 to 5 The frame format parsing method based on the Hinoc system based MAC layer multicast data frame is described in detail.

[0046] Such as figure 1 As shown, it is a flowchart of a frame format parsing method based on a HinoC system based on the embodiment of the present application embodiment; figure 1 As shown, the parsing method of the present application embodiment can include the following steps:

[0047] S102, acquire the type information of each HM terminal device that communicates with the HB, and the MAC layer multicast data frame.

[0048] Such as figure 2 As shown, it is an illustration of the Hinoc multicast business scenario provided by the embodiment of the present application.

[0049] Such as figure 2 As shown, a multicast business scene is given. In this scenario, the HinoC3.0 HB local device has made multiple transmission channels, not only by multi-channel multicast services, such as, for example, only the channel number to # 2 single channel, which is multicasted. The HM5 terminal device is a HinoC2.0 HM terminal device; it is also possible to multicast traffic through a multi-channel, and the transmission channel number is # 1, # 2, # 3, and # 4, respectively. A total of 5 HMs were connected to the network, which were HM1, HM2, HM3, HM4 and HM5, each having 1 PC under each HM, each PC on a different IPv4 multicast service located in the upper RV4 in the HB.

[0050] As described above figure 2 As shown, the parsing method provided by the present application is not only suitable for HinoC2.0 HM terminal devices that communicate with the HB local end, but also to communicate with the HB local end device, Therefore, it is possible to: for different types of HM terminal devices, for example, HinoC3.0 HM terminal devices, HinoC2.0 HM terminal devices are synchronized and parallel compatible with the frame format of the MAC layer multicast data frame, which is ultimately effective The parsing efficiency of the frame format of the MAC layer multicast data frame is improved.

[0051] S104, parse the type information to obtain the type of each HM terminal device that communicates with the HB local;

[0052] In the present application embodiment, the type of each HM terminal device that communicates with the HB localization includes not only the HinoC3.0HM terminal device, but also a HinoC2.0 HM terminal device.

[0053] S106, the parsing method for parsing the frame format of the MAC layer multicast data frame according to the type configuration of each HM terminal device, the resolution method includes a first resolution and HinoC2 that matches the HinoC3.0 HM terminal device. 0 HM terminal device matches the second parsing method.

[0054] In the present application embodiment, the first parsing method that matches the HinoC3.0 HM terminal device includes parsing the sequence number field in the extended information subframe and the multicast member mask field in the extended information subframe. Words analysis. Thus, if the current HM terminal device is a HinoC3.0 HM terminal device, the process using the first resolution method to parse the frame format of the MAC layer multicast data frame not only includes the sequence number field of the extended information. The parsing process also includes parsing the multicast member mask field of the extended information subframe.

[0055] The frame format corresponding to the first resolution method that matches the HinoC3.0 HM terminal device has figure 2 The frame format shown in the display, and the frame format corresponding to the second resolution method that matches the HinoC2.0 HM terminal device is the HinoC2.0 MAC layer data frame format, which is a regular format, and will not be described here.

[0056] Such as image 3 As shown, it is a schematic diagram of a frame format of a HinoC MAC layer multicast data frame in an application scenario provided in the present application embodiment. Such as figure 2 The frame format shown is a frame format corresponding to the first parsing method.

[0057] Such as image 3 As shown, the HinoC MAC layer multicast data frame format corresponding to the first parsing method is provided in the present application embodiment includes the following features:

[0058] 1) The multicast service from the upper layer is filed according to the format of the HinoC2.0 MAC layer data frame.

[0059] Based on the multicast group frame of HinoC2.0 MAC layer data frames reflects the evolution of the protocol evolution, and is conducive to compatibility with the original HinoC2.0 HM, namely: HinoC2.0 HM device does not support multi-channel ties in HinoC3.0. Type, HinoC2.0 HM ignores the EISF extended information subframe when the MAC layer multicast data frame sent by HinoC3.0 HB is received, which can complete normal multicast data reception.

[0060] 2) Set the extended frame header (EH_FLAG) in the header of the data frame 1 and the extended information subframe flag (Eisf_Flag) in the extended frame header 1; thus, make each MAC layer multicast data frame will carry an extension Information subframe (EISF) can then carry more control information in EISF.

[0061] 3) Add a sequence number field in the EISF extended information subframe.

[0062] The serial number field uses the TLV coded field format (Type field - length domain - value domain), where the TLV coding field of the TLV coding field can be set according to the protocol; the length domain of the TLV coding field is 2 bytes or 4 bytes. The value domain of the TLV coding field is a count value of 2 bytes or 4 bytes, each of which generates a Hinoc multicast data frame that belongs to the multicast stream. 1.

[0063]By adding the serial number field, it can be obtained: numbered the multicast data frame belonging to the same multicast stream, the number size represents the order of multicast data frames in the multicast stream. This allows a portion of the multicast stream to be forwarded in a plurality of parallel physical layer transmission channels, which improves the transmission bandwidth of the multicast stream, and does not need to worry about the multicast flow charter reach the HM receiver because the HM receiver can Reissue the multicast data frames of the downtown domain based on the serial number field in the multicast data frame EISF.

[0064] 4) In the EISF extension information subframe, multicast member mask fields.

[0065] The multicast member mask field uses the TLV coded field format (Type Domain - Length Domain - Value Domain), where the TLV coding field of the TLV coding field can be set according to the protocol needs; the length domain of the TLV coding field is 8; TLV The value domain of the encoding field is a mask of length 64 bits, which represents 64 HMs whether it is necessary to receive the multicast data frame, and bit 1 represents receiving, and bit 0 means no reception.

[0066] The multicast member mask field is jointly determined by the multicast forwarding table generated by the IGMP or MLD protocol and the channel binding table of each HM, which should meet the following constraints: The HM indicated by the multicast member mask field indicated in the multi-playback publication The receiving member of the multicast stream; the HM indicated by the multicast member mask field is bound to the current multicast data frame; when the same multicast data frame is sent multiple times in multiple transport channels, the maximum of HM should be guaranteed. The multicast member mask field on a transport channel indicates valid.

[0067] By multicast member mask fields can be done: each multicast data frame indicates that HM allows receiving the frame, while designing multicast member masks in accordance with the above principles, HM can avoid HM to receive repetitive multicast data. frame.

[0068] In summary, the HinoC MAC layer multicast data frame format provided by the present application embodiment reflects the evolution of the Hinoc protocol, and is conducive to compatible with the original HinoC2.0 HM, while solving the group in the multi-channel binding system. The orderly unordered data is uniquely received.

[0069] In a specific application scenario, the present application provides an Hinoc system based MAC layer multicast data frame assembly frame format, which has the following features, as described below:

[0070] The connected multicast Ethernet frame is filed in the HinoC2.0 MAC layer data frame format; the extended frame head flag (EH_FLAG) in the header of the data frame is set and the extended information subframe flag in the extended frame head (EISF_FLAG Place 1; add the sequence field and multicast member mask fields in the extended information subframe (EISF).

[0071] Further, the serial number field uses the TLV coded field format (Type Domain-Length Domain), where the TLV coding field can be set according to the protocol needs; the length domain of the TLV coding field is 2 bytes or 4 bytes; the value domain of the TLV coding field is a count value of 2 bytes or 4 bytes, each of which generates a HinoC multicast data frame that belongs to the multicast stream. This serial number plus 1.

[0072] Further, the multicast member mask field uses the TLV coded field format (Type field - length domain - value field), where the TLV coding field can be set according to the protocol needs; the length domain of the TLV coding field is 8; the value domain of the TLV coding field is a mask of length 64 bits, which represents 64 HMs need to receive the multicast data frame, and bit 1 represents reception, and bit 0 represents no reception.

[0073] Further, multicast member mask fields are jointly decided by the multicast forwarding table generated by the IGMP or MLD protocol and the channel binding tables of each HM. The following constraints should be met: the HM indicated by the multicast member mask field indication is a multicast. Express the receiving member of this multicast stream; the HM indicated by the multicast member mask field is bound to the transfer channel of the current multicast data frame; the same multicast data frame should be guaranteed when multiple transmission channels are sent multiple times. HM is mostly indicated by the multicast member mask field on a transport channel as valid.

[0074] As will be known, the parsing method provided by the embodiment of the present application provides a frame format based on the HinoC MAC layer bank data frame, the frame format corresponding to the foregoing first parsing method. This format is based on the HinoC2.0 MAC layer data frame format, which can solve the multicast forwarding issues in the Hinoc3.0 channel binding system by extending the EISF in the HinoC2.0 MAC layer data frame.

[0075] Further, in the present application embodiment, in the multicast data frame corresponding to the first parsing method, since the serial number field is added to the extended information subframe of the multicast data frame, an ordered reception can be achieved. It is referring to the order of the Ethernet flow within the same multicast IP (destination MAC address), which is not allowed to change, so that it is possible to effectively solve the problem of chart in the multicast service forwarding in the multi-channel binding system, and The extended information subframe of the multicast data frame adds the multicast member mask field, which can effectively solve the problem of repeating frames in the multicast service forwarding in the multi-channel binding system, avoiding repeating multicast data frames. It means that the HM terminal does not allow multiple identical Etheri frames belonging to the same multicast IP stream.

[0076] Such as Figure 4 As shown, it is a schematic diagram of the signal transceiver flow of the HinoC3.0 channel binding system. Such as Figure 4 As shown, the HB local and HM terminal device consists of a MAC medium access control layer and a PHY physical layer module, wherein the PHY layer supports multi-channel binding, a single channel bandwidth is 128MHz, providing a plurality of parallel MAC frames for MAC layers. Channel, each PHY layer channel consists of a transmitting unit and a receiving unit, and the transmitting unit converts the MAC frame to a radio frequency signal, and the receiving unit converts the RF signal to the MAC frame.

[0077] Since HinoC3.0 uses channel binding technology, in order to ensure the multi-channel binding HM, the non-repetitive multicast data frame can be unruly, and the present application presents a Hinoc MAC layer multicast data frame format, such as image 3 Indicated. The Hinoc MAC layer multicast data frame is based on the HinoC2.0 MAC layer data frame, and the HinoC2.0 MAC layer data frame format includes head, subframe header, EISF, other subframes, fills, and CRCs. Among them, an EISF frame is a special subframe in the Hinoc2.0 protocol, which can be used to carry special control information, which use the TLV coded field in the form of a TLV coding field, such as the HinoC2.0 protocol defines the EISF transfer detailed queue report information.

[0078] S108, according to the type of the current HM terminal device, the frame format of the MAC layer multicast data frame is parsed by parsing the type matching of the current HM terminal device to obtain the corresponding parsing result.

[0079] In a possible implementation, based on the type of the current HM terminal device, parsing the MAC layer multicast data frame frame format is used to parse the MAC layer multicast data frame format using a parsing method of the current HM terminal device. The following steps are included.

[0080] If the type of HM terminal device is a HinoC3.0HM terminal device, the frame format of the MAC layer multicast data frame is parsed by the first resolution method to obtain the first resolution result.

[0081] In the present application embodiment, the first resolution includes a mode in which the sequence number field in the extended information subframe is analyzed and parsed by the multicast member mask field in the extended information subframe. If the current HM terminal device The type of Hinoc3.0 HM terminal device is used to parse the frame format of the MAC layer multicast data frame using the first resolution. The following steps:

[0082] If the type of the current HM terminal device is the HinoC3.0 HM terminal device, the sequence number field of the extended information subframe is parsed, and the multicast member mask field of the extended information subframe is parsed.

[0083] In the embodiment of the present application, the above figure 2 As shown, the parsing method provided herein also includes the following steps:

[0084] The connected multicast Ethernet frame is filed in accordance with the HinoC2.0 MAC layer data frame format, and the extended frame head flag 1 in the data frame header is set, and the extended information subframe flag in the extended frame header is set. Such a corresponding one of the extended information subframes to bring each MAC layer multicast data frame.

[0085] In the embodiment of the present application, the above figure 2 As shown, the serial number field is encoded by the first TLV coded field format. The first TLV coded field format includes a first type of domain, a first length domain, and a first value domain corresponding to the serial number field, and the first type of domain is based on the required protocol. Configure, the value of the first length field is 2 bytes or 4 bytes, the first value domain is a count value of 2 bytes, and each time the group frame generates a HinoC group belonging to the multicast stream. When the data frame is broadcast, the serial number plus 1.

[0086] In the embodiment of the present application, the above figure 2 As shown, the multicast member mask field is encoded by the second TLV coded field format, and the second TLV coding field format includes a second type of domain, the second length domain, and the second value domain corresponding to the multicast member mask field. The second type field is configured according to the required protocol, and the second length domain is 8, the second value domain is a mask of the preset length bit.

[0087] In the present application embodiment, the frame format parsing method of the HinoC system-based MAC layer multicast data frame also includes the following steps:

[0088] Gets the second value domain and the first preset condition, the first preset condition includes: if the bit number identifier of any one of the mask is 1, the HM terminal device corresponding to the position needs to receive the MAC layer multicast data frame. If the bit number of the bit number of any of the mask is 0, the HM terminal device corresponding to the location does not need to receive the MAC layer multicast data frame;

[0089] According to the first preset condition and the second value domain, it is determined that the first HM terminal device set of the MAC layer multicast data frame is determined in each HM terminal device, and the MAC layer group is not required. The second HM terminal device set of the data frame; this, it can be accurately identified in each HM terminal device of the HB local communication, which devices need to receive the MAC layer multicast data frame, and all need to receive MAC multicast data. The HM terminal device of the frame constitutes a set of first HM terminal devices; and which devices do not need to receive the MAC layer multicast data frame, and consisting of all the HM terminal devices that do not need to receive the MAC multicast data frame constitute a second HM terminal device collection.

[0090] When the effective area is divided into which the HM terminal device needs to receive the MAC layer multicast data frame, only the frame format of the data frame is parsed only when it is confirmed to receive the MAC layer multicast data frame, so that it can effectively avoid The invalid parsing process greatly enhances the frame format parsing efficiency of the MAC layer multicast data frame.

[0091] Combined with the aforementioned image 3 As shown, in the present application embodiment, the frame format parsing method of the HinoC system-based MAC layer multicast data frame also includes the following steps:

[0092]Gets the multi-broadcast forwarding form generated by the protocol in the preset format, the channel binding table and the second preset condition of each HM terminal device that communicates with the HB Local, the second preset conditions include: multicast member mask fields The indicated HM terminal device is a receiving member of the multicast flow in the multicast publication. The various HM terminal devices indicated by the multicast member mask field bound the current multicast data frame, the same multicast data frame. When multiple transmission channels are sent multiple times, the HM terminal device is configured to any one of the HM terminal devices is indicated by a multicast member mask field on one transport channel;

[0093] Generate a multicast member mask field according to the multicast member mask field according to the multicast member mask field; through the second preset condition, since the multicast member mask field is introduced, the multi-channel can be effectively solved. Duplicate frame issues in the multicast service forwarding in the binding system.

[0094] In the present application embodiment, protocols in preset format include IGMP protocols or MLD protocols, and IGMP protocols include IGMPv1, IGMPv2, or IGMPv3 protocol versions in IPv4 networks, and MLD protocols include MLDv1 and MLDv2 versions in IPv6 networks.

[0095] In a possible implementation, based on the type of the current HM terminal device, the parsing of the MAC layer multicast data frame frame format is parsed by parsing the type matching of the current HM terminal device also includes the following steps:

[0096] If the type of the current HM terminal device is the HinoC2.0 HM terminal device, the frame format of the MAC layer multicast data frame is parsed by the second parsing method to obtain the second parsing result.

[0097] In the present application embodiment, the second parsing method is used to parse the HinoC2.0 MAC layer data frame format, and based on the parsing method is a conventional method, and will not be described herein.

[0098] Such as Figure 5 As shown, it is another example of the Hinoc multicast business scenario provided by the embodiment of the present application. Such as Figure 5 A multicast business scene is given. In this scenario, the HinoC3.0 HB is bonded to the binding of the transport channel, and the transmission channel number is # 1, # 2, # 3, and # 4, respectively. A total of 4 HM terminal devices are connected to the network, which are HM1, HM2, HM3, and HM4, each with 1 PC under each HM terminal device, and each PC is induced by different IPv4 multicast services located in the upper server of HB. . Such as Figure 5 In the multicast business scenario shown, the step of multicast traffic based on the Hinoc system is specifically described below:

[0099] Step 1) HB uses IGMP or MLD protocol to control multicast receiving members of each multicast post; IGMP or MLD protocol includes IGMPv1, IGMPv2 or IGMPv3 protocol version in IPv4 network, and MLDv1 and MLDv2 in IPv6 networks. version. In this example, the multicast service is an IPv4 business, and the IGMP protocol is used. according to Figure 4 The PC on-demand shown in the middle, the HB is based on the multicast transfer form established by IGMP as follows 1:

[0100] Multicast IP Multicast receive member 224.0.1.100 HM1, HM2, HM3 224.0.1.101 HM1, HM4 224.0.1.102 HM2 224.0.1.103 HM3, HM4

[0101] Table 1

[0102] Step 2) Find the channel binding table according to the receiving member collection of each multicast IP stream in the multicast issuings, calculate the forwarding channel set of each multicast IP stream and multicast member mask on each forwarding channel; Different HM binding channel collections may be different, Figure 4 The four HM channel bindings in the middle shown in Table 2:

[0103] HM Binding channel collection HM1 #1、#2、#3、#4 HM2 #1、#2 HM3 #3、#4 HM4 #2、#4

[0104] Table 2

[0105] The receiving members of 224.0.1.100 are HM1, HM2 and HM3, taking into account the channel binding collection of HM1, HM2, and HM3 and to ensure that three HM can receive 224.0.1.100 service, then 224.0.1.100 business requires at least two times. Here we assume that 224.0.1.100 business is transmitted separately on channel # 1 and # 3, respectively.

[0106] The receiving member of 224.0.1.101 is HM1 and HM2, and the public channel {# 1, # 2} of HM1 and HM2 can be transmitted on the common channel {# 1, # 2} of HM1 and HM2, and the channel # 1 can be selected separately to transmit the group. Broadcasting IP stream, or simultaneously using channel {# 1, # 2}, so-called joint transmission means that the multicast IP flow is divided into two subflows, channel # 1, and # 2 transmit a tribunition. In this example, we use channel # 2 to transfer 224.0.1.100 business.

[0107] 224.0.1.102 The received member of the HM2 is similar to the case of 224.0.1.101, and one channel can be selected from channel # 1 and # 2 to separately transmit or two channels for split transmission. In this example, we use channel # 1 and # 2 to deliver.

[0108] The received members of 224.0.1.103 are HM3 and HM4, and only one common channel, i.e., channel # 4, then select the multicast IP stream on the public channel.

[0109] Through the above analysis, the forwarding channel set of each multicast IP stream can be obtained, and the update of the multicast post, as shown in Table 3 below:

[0110]

[0111]

[0112] table 3

[0113] After obtaining the forwarding channel collection of each multicast IP stream, it is necessary to further calculate multicast member masks on each forwarding channel to indicate which HM on each channel can demodulate the multicast data frame.

[0114] 224.0.1.100 The multicast stream is forwarded twice on channel # 1 and # 3, where HM2 can only receive multicast data frames on channel # 1, and HM3 receives multicast data frames on channel # 3, and HM1 can be in channel. # 1 or # 3 receive data, in order to avoid each HM receive multiple identical multicast data frames, HM1 can only select one of the channels to receive data. Here we choose HM1 to receive data from channel # 1.

[0115] 224.0.101 The multicast stream is required to receive in channel # 2 forwarding, HM1 and HM4 need to be received.

[0116] 224.0.102 The multicast stream is transmitted over the channel # 1 and # 2, and the HM2 needs to receive the subflow on the two channels simultaneously and reordered according to the serial number field in the multicast data frame.

[0117] 224.0.103 The multicast stream is required to receive in channel # 4 forwarding, HM3 and HM4 need to be received.

[0118] Through the above analysis, each multicast IP stream can be obtained in the multicast member mask on each forwarding channel, update the multicast post, as shown in Table 4 below:

[0119]

[0120] Table 4

[0121] Among them, the multicast member mask length of each channel is 64 bits, in this example, the leftmost side of the multicast member mask represents the indicator bit of the HM1, and the leftmost side represents the indicator bit of HM64, the bit "1" representative needs Receive, "0" representatives do not need to be received.

[0122] In the present application example, each of the multicast IP, the receiving member set, forwarding channel set, and the multicast member mask, which feature that the multicast IP is the index of the multicast. value. During the implementation, the multi-shooting post can be constructed of a table, or a plurality of sub-tables: constructed by a table is a set of multicast IP, receiving member set, forwarding channel set, and The multicast member mask is composed of multiple sub-tables, refers to the receiving member collection, forwarding channel set, and multicast member mask may exist in multiple subtables separately, each sub-table is indexed in multicast IP.

[0123] Step 3) When the multicast data frame is received, find the multicast transfer form. If the forwarding channel set of the multicast data frame is non-empty, the multicast data frame is set in accordance with the Hinoc multicast data frame format provided above. The frame forms a Hinoc multicast data frame, wherein the value field of the multicast member mask field fills the full zero value;

[0124] Step 4) Send the HinoC multicast data frame to each of the transfer channels in the forwarding channel collection, and modify the value domain of the multicast member mask field in the Hinoc Multicast Data Frame to the forwarding channel before transmitting. Multicast member mask.

[0125] In this example, 224.0.1.100 The multicast stream is forwarded to channel # 1 and # 3, and forward to the multicast member mask field in the multicast data frame formed by the multicast group frame, fill in the multicast data frame formed by the multicast group frame. For "11000000 ... 0", forward to channel # 3, the multicast member mask field is filled as "00100000 ... 0".

[0126] 224.0.1.101 The multicast stream needs to be forwarded to the channel # 2, and the multicast member mask in the multicast data frame is filled as "10010000 ... 0" in the forwarded multicast data frame.

[0127] 224.0.1.102 The multicast stream requires a shunt to forward to channel # 1 and channel # 2, and when forwarding, the multicast member mask of multicast data frames on each channel is "01000000 ... 0".

[0128] 224.0.1.103 The multicast stream needs to be forwarded to the channel # 4, and the multicast member mask in the multicast data frame is filled as "00110000 ... 0" in the forwarded multicast data frame.

[0129] In the present application embodiment, the type information and MAC layer multicast data frame of each HM terminal device that communicates with the HB is acquired; parse the type information to obtain the type of each HM terminal device for communication with the HB local. According to the type configuration of each HM terminal device, the parsing method for parsing the frame format of the MAC layer multicast data frame, the resolution method includes the first resolution and Hinoc2.0 matching with the Hinoc3.0 HM terminal device. The second parsing method of the HM terminal device is matched; according to the current HM terminal device, the frame format of the MAC layer multicast data frame is parsed by parsing the type matching of the current HM terminal device to obtain the corresponding parsing result, so The parsing method provided by the present application embodiment is pre-paid according to the analysis of the frame format of the MAC layer multicast data frame according to the type configuration of each HM terminal device, and the parsing method includes matching the HinoC3.0 HM terminal device. The first parsing method and the second parsing method matching the HinoC2.0 HM terminal device, since the parsing method is not only suitable for HinoC2.0 HM terminal devices that communicate with the HB local part, it is also applicable to pass multiple channels HinoC3.0 HM terminal equipment for communication with the HB local, can be achieved: for different types of HM terminal devices, for example, HinoC3.0 HM terminal equipment, HinoC2.0 HM terminal device synchronous and parallel compatible parsing Mac The frame format of the layer multicast data frame, so that it ultimately effectively improve the analysis efficiency of the frame format of the MAC layer multicast data frame.

[0130]The following is the frame format parsing device embodiment of the present invention based on the HinoC system based MAC layer, which can be used to perform the frame format parsing method of the present invention based on the HinoC system. For details of the frame format parsing device embodiment of the present invention based on a Hinoc system, a frame format parsing method embodiment of the HinoC system based MAC layer multicast data frame is parsed.

[0131] See Figure 6 It shows a schematic structural diagram of a frame format parsing apparatus of a Hinoc system-based MAC layer multicast data frame according to an exemplary embodiment of the present invention. The frame format parsing apparatus of the HINOC-based MAC layer multicast data frame can be implemented throughout or part of the terminal through software, hardware or binding. The frame format parsing apparatus of the HINOC-based MAC layer multicast data frame includes a acquisition module 10, a first parsing module 20, a configuration module 30, and a second parsing module 40.

[0132] Specifically, the acquisition module 10 is obtained for acquiring the type information of each HM terminal device that communicates with the HB, and the MAC layer multicast data frame;

[0133] The first parsing module 20 is configured to prepare the type information acquired by the acquisition module 10 to obtain a type of each HM terminal device that communicates with the HB local.

[0134] The configuration module 30 is configured to parse the frame format of the MAC layer multicast data frame acquired by the acquisition module 10 according to the type configuration of each HM terminal device parsed in the first resolution module 20, and the parsing method includes The first parsing method that matches the HinoC3.0 HM terminal device and the second parsing method that matches the HinoC2.0 HM terminal device;

[0135] The second parsing module 40 is configured to obtain a MAC layer acquired by the acquisition module 10 using the type matching of the current HM terminal device configured with the configuration module 30 according to the first resolution module 20. The frame format of the multicast data frame is parsed to obtain the corresponding parsing result.

[0136] Optionally, the second parsing module 40 is used in:

[0137] If the type of HM terminal device is the HinoC3.0HM terminal device, the frame format of the MAC layer multicast data frame is parsed by the first resolution method, and the first resolution result is obtained; or

[0138] If the type of the current HM terminal device is the HinoC2.0 HM terminal device, the frame format of the MAC layer multicast data frame is parsed by the second parsing method to obtain the second parsing result.

[0139] Optionally, the first resolution includes a mode in which the sequence number field in the extended information subframe is analyzed, and the second parsing module 40 is specifically used for the second analysis module 40 for parsing the multicast member mask fields in the extended information subframe. :

[0140] If the type of the current HM terminal device is the HinoC3.0 HM terminal device, the sequence number field of the extended information subframe is parsed, and the multicast member mask field of the extended information subframe is parsed.

[0141] Optionally, the apparatus also includes:

[0142] Frame module (in Figure 6 Not shown), the multicast Ethernet frame for docking is used in the Hinoc2.0MAC layer data frame format.

[0143] The configuration module 30 is also used to: set the extended frame head flag 1 in the header header and the extended information subframe flag in the extended frame header, so that each MAC layer multicast data frame carries a corresponding expansion Information subframe.

[0144] Optionally, the serial number field is encoded in the first TLV coded field format. The first TLV encoded field format includes a first type of domain, a first length domain, and a first value domain corresponding to the serial number field, and the first type of domain is based on the desired The protocol is configured, and the value of the first length is 2 bytes or 4 bytes, the first value domain is 2 bytes or 4 bytes of count value, and each of the group frame generates a Hinoc that belongs to the multicast stream. This serial number plus 1 when multicast data frames.

[0145] Optionally, the multicast member mask field uses the second TLV coded field format to encode, the second TLV encoded field format includes a second type of domain, the second length domain, and the second value domain corresponding to the multicast member mask field. The second type of domain is configured according to the required protocol, and the second length domain is 8, the second value domain is a mask of the preset length bit.

[0146] Optionally, the acquisition module 10 is also used to obtain the second value field and the first preset condition, and the first preset conditions acquired by the acquisition module 10 include: if the number of bits identified by the bit of any of the masks, Then, the HM terminal device corresponding to the location needs to receive the MAC layer multicast data frame, and if the number of bit numbers in any of the masks are identified, the HM terminal device corresponding to the position does not need to receive the MAC layer multicast data frame;

[0147] The apparatus also includes:

[0148] Judgment module (in Figure 6 Not shown), used to determine the first preset condition and the second value domain acquired according to the acquisition module 10, it is determined that the first HM terminal device that needs to receive the MAC layer multicast data frame in each HM terminal device that communicates with the HB local. The HM terminal device collection, and a second HM terminal device collection that does not need to receive the MAC layer multicast data frame.

[0149] Optionally, the acquisition module 10 is also used in:

[0150] Gets the multi-broadcast forwarding form generated by the protocol in the preset format, the channel binding table of each HM terminal device for communicating with the HB, the second preset condition acquired by the acquisition module 10 includes: group The HM terminal device indicated by the Member Mask field is a receiving member of the multicast flow in the multicast publication. The various HM terminal devices indicated by the multicast member mask field bound the current multicast data frame transmission channel, the same When a multicast data frame is transmitted multiple times in multiple transport channels, the HM terminal device is configured to any one of the HM terminal devices, and the multicast member mask field indicated by the multicast member mask field on one transport channel is active;

[0151] The apparatus also includes: generating a module (in Figure 6 Not shown), used to generate a multicast member mask field based on the multicast forwarding table, channel binding table, and second preset conditions acquired by the acquisition module 10.

[0152] Optional, preset format protocols include IGMP protocols or MLD protocols, IGMP protocols include IGMPv1, IGMPv2, or IGMPv3 protocol versions in IPv4 networks, MLD protocols include MLDv1 and MLDv2 versions in IPv6 networks.

[0153] It should be noted that the frame format parsing apparatus of the Hinoc system-based MAC layer multicast data frame provided by the above embodiment is parsed by the above function module when performing the frame format of the Hinoc system-based MAC layer multicast data frame. The division will be described, and in the actual application, the above function allocation can be done by different functional modules as needed, and the internal structure of the device is divided into different functional modules to complete all or part of the above described above. Further, the frame format parsing method of the Hinoc system-based MAC layer multicast data frame is provided with the frame format parsing method of the Hinoc system based on the frame format of the HinoC system belongs to the same concept. It reflects the implementation process. Frame format parsing method embodiments based on the MAC layer multicast data frame of the HinoC system, and details are not described here.

[0154] In the present application embodiment, the acquisition module is used to acquire the type information of each HM terminal device for communication with the HB, and the MAC layer multicast data frame is used; the first parsing module is used to parse the type information acquired by the acquisition module. The type of each HM terminal device that communicates with the HB is obtained; the configuration module is used to configure the MAC layer multicast data frame acquired to the acquisition module according to the type configuration of each HM terminal device parsed according to the first parsing module. The framing format is parsed, the resolution method includes the first resolution method that matches the HinoC3.0 HM terminal device and the second parsing method that matches the Hinoc2.0HM terminal device; and the second parsing module for the first resolution module The type of the current HM terminal device is analyzed by the analysis of the type matching of the current HM terminal device configured with the configuration module to parse the frame format of the MAC layer multicast data frame acquired by the acquisition module to obtain the corresponding parsing result. Therefore, the parsing apparatus provided by the present application, pre-parsing the analysis method for parsing the frame format of the MAC layer multicast data frame according to the type configuration of the respective HM terminal devices, including the HinoC3.0 HM terminal device Matching the first resolution and the second parsing method that matches the HinoC2.0 HM terminal device, since the parsing method is not only suitable for HinoC2.0 HM terminal devices that communicate with the HB local part, it is also suitable for adoption Hinoc3.0 HM terminal equipment for communication with the HB local end, can be achieved: for different types of HM terminal devices, for example, HinoC3.0 HM terminal equipment, HinoC2.0 HM terminal device for synchronization and parallel compatibility analysis The frame format of the MAC layer multicast data frame, so that the analysis efficiency of the frame format of the MAC layer multicast data frame is ultimately effectively improved.

[0155] One of ordinary skill in the art will appreciate that all or some of the flow in the above-described embodiment method is to be done by a computer program to instruct the hardware, which can be stored in a computer readable storage medium, which is When executed, the flow of the embodiments of each method may be included. The aforementioned storage medium can be a discharged disk, an optical disk, a read-only memory, a ROM, or a random storage memory (RAM), and the like, the RAM ACCESS MEMORY, RAM.

[0156] The various technical features of the above embodiments may be arbitrarily combined, in order to make the description, the possible combinations of various technical features in the above embodiments are not described, however, as long as the combination of these technical features does not have contradictions, It should be considered as the scope of this specification.

[0157] The above embodiments are merely expressed in several embodiments of the present invention, which are more specific and detailed, but are not to be construed as limiting the patent scope of the present invention. It should be noted that for ordinary skill in the art, several deformations and improvements can be made without departing from the concept of the present invention, which belongs to the scope of the present invention. Therefore, the scope of the scope of the invention should be taken as the appended claims.