Multicast message copying method and device

Abstract

The invention provides a multicast message copying method and device, and is applied to the technical field of communication, and the method comprises the steps: obtaining a current ring head address from a multicast access table entry for a to-be-copied multicast message at this time; using the current ring head address to query a ring multicast chain table to obtain a target table item corresponding to the current ring head address, the table items included in the ring multicast chain table being linked in a ring structure; performing copying operation on the multicast message based on the target table item; if it is identified that the multicast copy task is not completed in the annular multicast linked list, acquiring a next hop address; and updating the value of the current ring head address in the multicast access table entry to the next hop address.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of communication technology, in particular to a multicast message replication method and device. BACKGROUND

[0002] With the development of network technology, multicast replication technology is applied more and more widely. In special industry application scenarios such as securities, in addition to the requirement of increasing the number of replicated nodes in a multicast group, there is also a specific requirement for the execution order of each replicated node. For example, each replicated node corresponds to a table entry, and when multicast message replication is performed, it is hoped that each multicast replication operation of each replicated node corresponding to each table entry has a priority execution opportunity, and the priority execution opportunities are equal.

[0003] The existing multicast replication execution mechanism is roughly as follows: the table entries corresponding to each replicated node of a multicast group are stored in the form of a straight chain list. In this way, when actual multicast message replication is performed, the straight chain list can be used to perform multicast message replication and forwarding operations. However, if multicast replication is performed starting from the head table entry (the first table entry of the straight chain list) according to the above straight chain structure, each time the to-be-replicated message arrives, the replicated node corresponding to the table entry close to the head will necessarily execute the replication operation in priority to the replicated node corresponding to the table entry close to the tail (the last table entry of the straight chain list). From the perspective of the chip or device outlet, the multicast replication message of the replicated node corresponding to the head table entry will always be output first at the outlet position, and for each downstream interface / device that needs to highly observe the refresh order and time limit of each multicast replication message, it will cause the problem of unfairness in the order of obtaining messages from each other.

[0004] Therefore, how to solve the problem of fixed priority order of multicast messages obtained by downstream devices caused by fixed execution order when multicast message replication is performed in the form of a straight chain list is one of the technical problems worth considering. SUMMARY

[0005] Embodiments of the present application provide a multicast message replication method and device to solve the problem of fixed priority order of multicast messages obtained by downstream devices caused by fixed execution order when multicast message replication is performed in the form of a straight chain list.

[0006] In one aspect, the present application provides a multicast message replication method, which comprises: For the multicast message to be replicated this time, obtaining a current ring head address from a multicast access table entry; Querying a ring-type multicast link list using the current ring head address to obtain a target table entry corresponding to the current ring head address, wherein the table entries included in the ring-type multicast link list are linked in a ring type structure; Performing a replication operation on the multicast message based on the target table entry; obtaining a next hop address; updating a value of the current ring head address in the multicast access table item as the next hop address.

[0007] In another aspect, an embodiment of the present application provides a multicast message replication device, the device comprising: a first obtaining module configured to obtain a current ring head address from a multicast access table item for a multicast message to be replicated this time; a querying module configured to query a ring-type multicast link list by using the current ring head address to obtain a target table item corresponding to the current ring head address, wherein the table items included in the ring-type multicast link list are linked in a ring-type structure; a replicating module configured to perform a replication operation on the multicast message based on the target table item; a second obtaining module configured to obtain a next hop address; an updating module configured to update a value of the current ring head address in the multicast access table item as the next hop address.

[0008] The technical solutions provided by the embodiments of the present application can include the following beneficial effects: In the process of replicating a multicast message, a ring-type multicast link list is introduced, wherein the table items included in the ring-type multicast link list are linked in a ring-type structure. Thus, in the process of replicating a multicast message to be replicated, a current ring head address is obtained from a multicast access table item. Then, the ring-type multicast link list is queried by using the current ring head address to obtain a target table item corresponding to the current ring head address. Then, a replication operation is performed on the multicast message based on the target table item. After the replication operation on the multicast message is completed, a next hop address is obtained. Then, a value of the current ring head address in the multicast access table item is updated as the next hop address. In this way, the ring head address in the multicast access table item can be dynamically updated. Thus, when a multicast message arrives next time, a corresponding table item can be found based on the updated ring head address. That is, the table item found each time based on the dynamic ring head address is not fixed. Thus, the order of the replicated multicast message in the process of forwarding is not fixed. Thus, the problem that the order of the multicast message obtained by a downstream device is fixed due to the fixed order of the table items in the straight chain link list when the multicast message is replicated in the form of a straight chain link list is solved.

[0009] It should be understood that the foregoing general description and the following detailed description are only exemplary and explanatory, and cannot limit the present specification. BRIEF DESCRIPTION OF DRAWINGS

[0010] Figure 1 is a flowchart of a multicast message replication method according to an embodiment of the present application; Figure 2ais a structural diagram of a ring-type multicast linked list obtained by linking a plurality of table entries in a ring-type structure according to an embodiment of the present application; Figure 2b is a structural diagram of a ring-type multicast linked list obtained by linking a plurality of table entries in a ring-type structure according to an embodiment of the present application; Figure 2c is a structural diagram of a ring-type multicast linked list obtained by linking a plurality of table entries in a ring-type structure according to an embodiment of the present application; Figure 2d is a structural diagram of a ring-type multicast linked list obtained by linking a plurality of table entries in a ring-type structure according to an embodiment of the present application; Figure 3 is a structural diagram of a multicast message replication device according to an embodiment of the present application; Figure 4 is a hardware structure diagram of a computer device according to an embodiment of the present application. DETAILED DESCRIPTION

[0011] The following will be described in detail with reference to the accompanying drawings. In the following description, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all the embodiments consistent with the present description, but are exemplary embodiments of devices and methods consistent with some aspects of the present description.

[0012] The terms used in the present description are merely for the purpose of describing particular embodiments and are not intended to limit the present description. As used in the present description, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.

[0013] It should be understood that the terms "first", "second", "third", etc. can be used in the present description to describe various information or structural modules, and the purpose is to make the scheme more clearly described, and it cannot be understood as indicating or implying the relative importance or implicitly indicating the number, order or position of the indicated technical features. Therefore, the features defined as "first", "second", "third", etc. can be explicitly or implicitly included one or more features. In the description of the present description, unless otherwise specified, the meaning of "a plurality of" is two or more; "if" can be interpreted as "when" or "when" or "in response to determining".

[0014] In the present description, "and / or" describes the association relationship of the associated objects, which means that there can be three relationships, for example, A and / or B, which means that A exists alone, A and B exist together, and B exists alone, where A and B can be singular or plural. The character " / " generally represents that the associated objects before and after are in a "or" relationship.

[0015] Next, the embodiments of the present specification are described in detail.

[0016] As shown in Figure 1 , Figure 1 is a flow chart of a multicast message replication method according to an exemplary embodiment of the present specification. The multicast message replication method can be applied to a network device. When implementing the method, the network device can include the following steps: In step 102, the current ring head address is obtained from the multicast access table item for the multicast message to be replicated this time.

[0017] In this step, when the network device obtains the multicast message, and identifies that the message replication operation needs to be performed based on the multicast message, the multicast message can be recorded as the multicast message to be replicated this time. In order to realize the replication of the multicast message, the present application pre-maintains a multicast access table item, which only maintains a ring head address, which is used to point to the table item in the ring multicast linked list for multicast replication. It should be noted that the first ring head address can be any one in the ring multicast linked list.

[0018] On this basis, the network device obtains the current ring head address from the multicast access table item before performing multicast message replication on the multicast message. The current ring head address can be understood as the ring head address currently recorded in the multicast access table item.

[0019] In step 104, the ring multicast linked list is queried using the current ring head address to obtain the target table item corresponding to the current ring head address.

[0020] The table items included in the above-mentioned ring multicast linked list are linked in a ring type structure.

[0021] Optionally, the above-mentioned ring multicast linked list can include at least one table item. When the ring multicast linked list includes one table item, the single table item is also linked in a ring type structure, and the tail of the table item points to the table item, Figure 2a A single table item ring type link is given to obtain a ring multicast linked list. When the above-mentioned ring multicast linked list includes multiple table items, the multiple table items are linked in a ring type structure, and the link between adjacent table items is directional; in addition, the setting of adjacent table items in the multiple table items can be determined according to actual conditions. Specifically, multiple table items for multicast replication are pre-configured in the network device. In order to achieve the purpose that the messages obtained after multicast replication based on the table items are randomly distributed and have no fixed order, the multiple table items are linked in a ring type structure. The ring multicast linked list obtained by the multiple table items ring type link can refer to Figure 2b as shown, Figure 2b Each link point in the above-mentioned ring multicast linked list represents a table item.

[0022] For better understanding, taking the current configuration of 5 table entries as an example, the 5 table entries are respectively denoted as table entry 1, table entry 2, table entry 3, table entry 4 and table entry 5. It should be noted that the settings of adjacent table entries in the ring type link can be configured according to actual conditions, and can be dynamically adjusted according to actual conditions. In one embodiment, the ring type multicast linked list obtained by the ring type link of the 5 table entries can be as follows: table entry 1 links table entry 2, table entry 2 links table entry 3, table entry 3 links table entry 4, table entry 4 links table entry 5, table entry 5 links table entry 1, and table entry 1 points to table entry 2, table entry 2 points to table entry 3, table entry 3 points to table entry 4, table entry 4 points to table entry 5, and table entry 5 points to table entry 1, which can be referred to in the description of FIG. 1. Figure 2c In another embodiment, the ring type multicast linked list obtained by the ring type link of the 5 table entries can also be as follows: table entry 1 links table entry 3, table entry 3 links table entry 2, table entry 2 links table entry 4, table entry 4 links table entry 5, table entry 5 links table entry 1, and table entry 1 points to table entry 3, table entry 3 points to table entry 2, table entry 2 points to table entry 4, table entry 4 points to table entry 5, and table entry 5 points to table entry 1, which can be referred to in the description of FIG. 1. Figure 2d Of course, there can be other embodiments, which will not be enumerated one by one in detail herein.

[0023] Specifically, each table entry includes an address, replication requirement information, etc. On this basis, the current ring head address obtained can be used to query the ring type multicast linked list to confirm the table entry containing the current ring head address, that is, the above-mentioned target table entry.

[0024] In step 106, a replication operation is performed on the multicast message based on the target table entry.

[0025] In this step, after the target table entry is found, the replication requirement information included in the target table entry can be used to perform a replication operation on the multicast message, thereby obtaining a multicast replication message.

[0026] In addition, the target table entry also includes an out interface, and after obtaining the multicast replication message, the multicast replication message can be forwarded to the outside through the out interface of the target table entry.

[0027] In step 108, a next hop address is obtained.

[0028] In this step, in order to realize that the order of multicast message replication is no longer fixed, it is ensured that the multicast replication message obtained based on each table entry has an equal opportunity to be executed preferentially, after performing the message replication action on the multicast message to be replicated this time, the next hop address can be obtained, and the next hop address can be obtained from the target table entry. In order to better understand this step, taking the above-mentioned Figure 2cThe ring type multicast link list is taken as an example for illustration. If the current ring head address is the address of the table entry 2, and the address obtained from the table entry 2 is the address of the table entry 4, then the next hop address is the address of the table entry 4.

[0029] In step 110, the value of the current ring head address in the multicast access table entry is updated to the next hop address.

[0030] In this step, after the next hop address is obtained, the value of the current ring head address in the multicast access table entry is updated to the obtained next hop address. In this way, when the multicast packet is obtained next time, the table entry corresponding to the next hop address can be found based on the current ring head address at that time, and then the multicast packet is copied based on the found table entry. In this way, multicast packet copying based on different table entries is realized, and the multicast replication packet copied based on each table entry has the opportunity to be executed preferentially, thereby solving the problem that the order of obtaining the multicast packet by the downstream device is fixed when the straight chain link list is used for multicast packet copying.

[0031] In the above multicast packet copying method, the current ring head address is obtained from the multicast access table entry for the multicast packet to be copied this time; the target table entry corresponding to the current ring head address is obtained by querying the ring type multicast link list using the current ring head address, and the table entries included in the ring type multicast link list are linked in a ring type structure; the multicast packet is copied based on the target table entry; if it is identified that the multicast replication task of the ring type multicast link list is not completed, the next hop address is obtained; and the value of the current ring head address in the multicast access table entry is updated to the next hop address. In this way, the ring head address in the multicast access table entry can be dynamically updated, and then when the multicast packet arrives next time, the corresponding table entry can be found based on the updated ring head address, that is, the table entry found each time based on the dynamic ring head address is not fixed, and then the order of the replicated multicast packet for forwarding is also not fixed, thereby solving the problem that the order of obtaining the multicast packet by the downstream device is fixed when the straight chain link list is used for multicast packet copying.

[0032] Optionally, based on the above embodiment, before the step of obtaining the next hop address, the multicast message replication method provided by the embodiment further comprises the following step of identifying whether the ring-type multicast link list completes the multicast replication task: obtaining the number of entries of the current ring-type link list from the multicast access table entry, the number of entries of the current ring-type link list being used to represent the life cycle of the ring-type multicast link list for multicast replication; if the number of entries of the current ring-type link list is not the first set value, it is identified that the ring-type multicast link list does not complete the multicast replication task; if the number of entries of the current ring-type link list is the first set value, it is identified that the ring-type multicast link list completes the multicast replication task.

[0033] After it is identified that the ring-type multicast link list does not complete the multicast replication task, the step of obtaining the next hop address is executed.

[0034] Specifically, in order to better perform multicast replication, since the ring-type multicast link list is a ring-type link list structure, in order to avoid the ring-type multicast link list always performing multicast replication cycle, the embodiment proposes to monitor the multicast replication task of the ring-type multicast link list for multicast replication, and obtain the next hop address when it is identified that the ring-type multicast link list does not complete the multicast replication task, so as to perform multicast replication operation based on the next hop address after the next multicast message arrives. Since the ring head address in the multicast access table entry is dynamically changed, the order of each multicast replication is effectively refreshed, thereby better solving the problem that the order of multicast messages obtained by downstream devices is fixed when multicast message replication is performed in a straight chain link list form due to the fixed order of each entry of the straight chain link list.

[0035] Further, in order to better identify the completion of the multicast replication task of the ring-type multicast link list, the embodiment proposes to maintain the number of entries of the ring-type link list in the above multicast access table entry, and use the number of entries of the ring-type link list to represent the life cycle of the ring-type multicast link list for multicast replication. The larger the value of the number of entries of the ring-type link list, the longer the multicast replication life cycle. The smaller the value of the number of entries of the ring-type link list, the shorter the multicast replication life cycle. When the value of the number of entries of the ring-type link list is 0, it is indicated that the life cycle of the ring-type multicast link list for multicast replication is terminated.

[0036] On this basis, the above first set value can be set to 0. In this way, after the multicast message replication operation of the target entry is performed, the number of entries of the current ring-type link list can be obtained from the multicast access table entry. If it is identified that the value of the number of entries of the current ring-type link list is 0, it is indicated that the life cycle of the ring-type multicast link list for multicast replication is terminated, i.e., the ring-type multicast link list currently completes the multicast replication task. If it is identified that the value of the number of entries of the current ring-type link list is not 0, it is indicated that the ring-type multicast link list currently does not complete the multicast replication task.

[0037] Further, if the ring-type multicast chain list does not complete the multicast replication task, the embodiment proposes to perform a decrement operation on the number of entries of the current ring-type chain list according to a second set value.

[0038] Specifically, the second set value can be 1. Based on this, since it is currently identified that the ring-type multicast chain list has not completed the multicast replication task, but has performed a multicast packet replication operation once based on the found target entry, the number of entries of the current ring-type chain list in the multicast access entry can be decremented by 1, so as to obtain the number of entries of the ring-type chain list after the decrement operation, in order to facilitate the next multicast replication task.

[0039] In another embodiment, the ring-type multicast chain list can also be identified whether it completes the multicast replication task according to the following method: when the multicast access entry only maintains the ring head address, it is identified whether the corresponding counter of the ring-type multicast chain list reaches a set count value, the set count value being the number of entries of the ring-type multicast chain list; when the set count value is reached, it indicates that the ring-type multicast chain list has completed the multicast replication task; if the set count value is not reached, it indicates that the ring-type multicast chain list currently does not complete the multicast replication task.

[0040] Optionally, based on any of the above embodiments, the multicast access entry acquisition method in the embodiment is: acquiring the multicast access entry address from the packet side information or the packet header of the multicast packet; and acquiring the multicast access entry by using the multicast access entry address.

[0041] Specifically, after acquiring the multicast packet, the multicast packet is identified, and when it is identified that the multicast packet needs to be replicated, the multicast access entry address is added in the packet side information or the packet header of the multicast packet, and correspondingly, the multicast packet is the multicast packet to be replicated this time. In this way, after the network device acquires the multicast packet to be replicated this time, the multicast access entry address can be acquired from the packet side information or the packet header, and then the multicast access entry can be acquired by using the multicast access entry address.

[0042] It should be noted that when the network device includes a processing core and a forwarding chip, the processing core can identify the multicast packet after receiving the multicast packet, and when it is identified that the multicast packet needs to be replicated, the multicast access entry address of the multicast access entry is written into the packet side information or the packet header to obtain the multicast packet to be replicated this time; then, the processing core can send it to the forwarding chip to perform packet forwarding processing. After the forwarding chip receives the multicast packet, the multicast access entry address can be acquired from the packet side information or the packet header, and then the multicast access entry can be acquired. After the forwarding chip acquires the multicast access entry, the multicast packet replication process proposed in any of the embodiments of the application is performed.

[0043] It is worth noting that the processing core can identify whether the multicast message copy identifier is included in the message header of the multicast message, and when included, it is determined that the multicast message needs to be copied.

[0044] By providing the above multicast message copy method, the multicast message copy is performed using the ring type multicast link structure, and the table item address for the next multicast message copy can be updated each time the multicast message copy process is executed, effectively solving the problem of fixed priority of multicast copy messages obtained by downstream devices when the multicast message copy is performed using the straight chain link structure.

[0045] Corresponding to the above-mentioned embodiments of the method, the present specification also provides embodiments of a multicast message copy device and a computer device applied thereto. The above-mentioned multicast message copy device can refer to Figure 3 as shown, which can include: The first acquisition module 301 is configured to acquire the current ring head address from the multicast access table item for the multicast message to be copied this time; The query module 302 is configured to query the ring type multicast link list using the current ring head address to obtain the target table item corresponding to the current ring head address, wherein the table items included in the ring type multicast link list are linked in a ring type structure; The copy module 303 is configured to perform a copy operation on the multicast message based on the target table item; The second acquisition module 304 is configured to acquire the next hop address; The update module 305 is configured to update the value of the current ring head address in the multicast access table item to the next hop address.

[0046] In the above-mentioned multicast message copy device, the current ring head address is acquired from the multicast access table item for the multicast message to be copied this time; the ring type multicast link list is queried using the current ring head address to obtain the target table item corresponding to the current ring head address, wherein the table items included in the ring type multicast link list are linked in a ring type structure; a copy operation is performed on the multicast message based on the target table item; if it is identified that the ring type multicast link list has not completed the multicast copy task, the next hop address is acquired; and the value of the current ring head address in the multicast access table item is updated to the next hop address. In this way, the ring head address in the multicast access table item can be dynamically updated, and the corresponding table item can be found based on the updated ring head address when the next multicast message arrives, that is, the table item found each time based on the dynamic ring head address is not fixed, and the order of the copied multicast message when forwarded is also not fixed, thereby solving the problem of fixed priority of multicast messages obtained by downstream devices caused by the fixed order of each table item of the straight chain link table when the multicast message copy is performed using the straight chain link table form.

[0047] Optionally, based on the above-mentioned embodiments, the multicast message replication device provided by the present embodiment can further comprise: The identification module (not shown in the figure) is configured to identify whether the ring-type multicast chain table has completed the multicast replication task according to the following method: obtaining the number of table entries of the current ring-type chain table from the multicast access table entry, wherein the number of table entries of the current ring-type chain table is used to represent the life cycle of the ring-type multicast chain table for multicast replication; if the number of table entries of the current ring-type chain table is not a first set value, it is identified that the ring-type multicast chain table has not completed the multicast replication task; if the number of table entries of the current ring-type chain table is the first set value, it is identified that the ring-type multicast chain table has completed the multicast replication task. The second obtaining module is specifically configured to perform the step of obtaining the next hop address after the identification module identifies that the ring-type multicast chain table has not completed the multicast replication task.

[0048] Optionally, the update module 305 is further configured to perform a decrement operation on the number of table entries of the current ring-type chain table according to a second set value if the identification module identifies that the ring-type multicast chain table has not completed the multicast replication task.

[0049] Based on any of the above-mentioned embodiments, the multicast message replication device provided by the present embodiment can further comprise: The third obtaining module (not shown in the figure) is configured to obtain the multicast access table entry address from the message side information or the message header of the multicast message, and obtain the multicast access table entry by using the multicast access table entry address.

[0050] The embodiments of the multicast message replication device of the present specification can be applied to computer devices, such as network devices and the like. The device embodiments can be implemented by software, or by hardware or a combination of software and hardware. Taking software implementation as an example, as a logical device, it is formed by reading the corresponding computer program instructions in the non-volatile memory into the memory for running by the forwarding chip where the multicast message replication device is located. From the hardware level, as shown in the figure, it is a hardware structure diagram of the computer device where the multicast message replication device of the present specification is located. In addition to the processor 410, the memory 430, the network interface 420, the non-volatile memory 440, and the forwarding chip shown in the figure, the network device or electronic device where the multicast message replication device 431 is located in the embodiment can also include other hardware according to the actual function of the computer device, and details are not repeated. Figure 4 Figure 4

[0051] Correspondingly, the present specification also provides a multicast message replication device, which comprises a processor, a memory for storing processor-executable instructions, wherein the processor is configured to: ​​For the multicast message to be copied this time, the current ring head address is obtained from the multicast access table item; the current ring head address is used to query the ring multicast link list to obtain the target table item corresponding to the current ring head address, the table items included in the ring multicast link list are linked in a ring structure; based on the target table item, the multicast message is executed; if it is identified that the ring multicast link list has not completed the multicast replication task, the next hop address is obtained; the value of the current ring head address in the multicast access table item is updated to the next hop address.

[0052] The multicast message replication is performed by using the ring multicast link structure, and the table item address for the next multicast message replication can be updated each time the multicast message replication process is executed, thereby effectively solving the problem that the multicast replication message priority of the downstream device is fixed due to the fixed execution sequence when the multicast message replication is performed by using the straight chain link structure.

[0053] The implementation process of the functions and roles of each module in the above device is specifically described in the implementation process of the corresponding steps in the above method, which will not be repeated here.

[0054] For the device embodiment, since it basically corresponds to the method embodiment, the related parts can be referred to the part of the method embodiment. The device embodiments described above are only illustrative, and the modules described as separate components can or can not be physically separated, and the components shown as modules can or can not be physical modules, i.e., they can be located in one place or distributed on multiple network modules. Part or all of the modules can be selected to achieve the purpose of the scheme of the present application according to actual needs. Those skilled in the art can understand and implement without creative labor.

[0055] The above describes the exemplary embodiments of the present application, and it should be understood that in some cases, the modules described in the present application can be divided in a manner different from the embodiments, and the described actions or steps can also be executed in an order different from the embodiments, and the desired results can still be achieved. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multi-task processing and parallel processing are also possible or can be advantageous.

[0056] Those skilled in the art will readily understand other embodiments of the present application upon considering the specification and practicing the application claimed herein. The present application is intended to cover any variations, uses, or adaptations of the present application following the general principles thereof and including the general knowledge or custom of the present art not specifically exemplified herein.

[0057] The above description is only the preferred embodiment of the present specification, and is not used to limit the present specification. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present specification shall be included in the protection scope of the present specification.

Claims

1. A multicast message replication method, characterized in that, The method comprises: obtaining a current ring head address from a multicast access table for a multicast message to be copied this time; querying a ring multicast link list by using the current ring head address to obtain a target table corresponding to the current ring head address, wherein the tables included in the ring multicast link list are linked in a ring structure; performing a copy operation on the multicast message based on the target table; obtaining a next hop address; updating a value of the current ring head address in the multicast access table to the next hop address.

2. The method of claim 1, wherein, Before obtaining the next hop address, the method further comprises the following steps of identifying whether the ring multicast link list completes a multicast copy task: obtaining a table number of a current ring link list from the multicast access table, wherein the table number of the current ring link list is used to represent a life cycle of the ring multicast link list for multicast copy; if the table number of the current ring link list is not a first set value, identifying that the ring multicast link list does not complete the multicast copy task; if the table number of the current ring link list is the first set value, identifying that the ring multicast link list completes the multicast copy task; after identifying that the ring multicast link list does not complete the multicast copy task, performing the step of obtaining the next hop address.

3. The method of claim 2, wherein, If it is identified that the ring multicast link list does not complete the multicast copy task, the method further comprises: performing a decrement operation on the table number of the current ring link list according to a second set value.

4. The method of claim 1, wherein, The method for obtaining the multicast access table comprises: obtaining a multicast access table address from message side information or a message header of the multicast message; and obtaining the multicast access table by using the multicast access table address.

5. A multicast message replication apparatus characterized by comprising: The device comprises: a first obtaining module configured to obtain a current ring head address from a multicast access table for a multicast message to be copied this time; a querying module configured to query a ring multicast link list by using the current ring head address to obtain a target table corresponding to the current ring head address, wherein the tables included in the ring multicast link list are linked in a ring structure; a copying module configured to perform a copy operation on the multicast message based on the target table; a second obtaining module configured to obtain a next hop address; an updating module configured to update a value of the current ring head address in the multicast access table to the next hop address.

6. The apparatus of claim 5, wherein, The device further comprises: an identifying module configured to identify whether the ring multicast link list completes a multicast copy task according to the following method: obtaining a table number of a current ring link list from the multicast access table, wherein the table number of the current ring link list is used to represent a life cycle of the ring multicast link list for multicast copy; if the table number of the current ring link list is not a first set value, identifying that the ring multicast link list does not complete the multicast copy task; and if the table number of the current ring link list is the first set value, identifying that the ring multicast link list completes the multicast copy task; the second obtaining module is specifically configured to perform the step of obtaining the next hop address after the identifying module identifies that the ring multicast link list does not complete the multicast copy task.

7. The device of claim 6, wherein The update module is further configured to, if the identification module identifies that the circular multicast linked list has not completed the multicast replication task, decrement the number of entries in the current circular linked list according to a second preset value.

8. The apparatus of claim 5, wherein, The device further includes: The third acquisition module is used to obtain the multicast access entry address from the message accompanying information or message header of the multicast message; and to obtain the multicast access entry using the multicast access entry address.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, performs the method as described in any one of claims 1 to 4.

10. A computer device, comprising: The device includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the program, performs the following method: For the multicast message to be copied, obtain the current ring head address from the multicast access table entry; The current ring start address is used to query the ring multicast linked list to obtain the target entry corresponding to the current ring start address. The entries in the ring multicast linked list are linked in a ring structure. Perform a copy operation on the multicast message based on the target entry; Get the next hop address; Update the value of the current ring head address in the multicast access entry to the next hop address.

Images