WO2019033910A1

WO2019033910A1 - Multi-port multicast method and device, and computer readable storage medium

Info

Publication number: WO2019033910A1
Application number: PCT/CN2018/097125
Authority: WO
Inventors: 梁建适; 张晓渠
Original assignee: 中兴通讯股份有限公司
Priority date: 2017-08-14
Filing date: 2018-07-25
Publication date: 2019-02-21
Also published as: CN109391551B; CN109391551A

Abstract

The present disclosure relates to a multi-port multicast method and device, and a computer readable storage medium. The method comprises: after joining a multi-cast group, configuring a multi-port list locally; and matching, according to the multi-port list, destination ports in a received multi-cast packet, and processing the multi-cast packet when the matching is successful. The present disclosure does not require the establishment of multiple UDP sockets by configuring a multi-port list, thereby reducing the creation of sockets and reducing the management complexity of application layer sockets.

Description

Multi-port multicast method, device and computer readable storage medium

Technical field

The present disclosure relates to the field of communications technologies, and in particular, to a multi-port multicast method, device, and computer readable storage medium.

Background technique

In the field of Internet transmission, with the development of multimedia video technology, the application of multicast transmission technology is more and more extensive, such as IPTV channel transmission, emerging VR (Virtual Reality) live broadcast technology, all using multicast transmission media. data. Moreover, these multicast transmissions need to support one-way multicast transmission of multiple streams. For example, OTT (Over The Top) multicast transmission needs to transmit code streams of different code rates, and VR multicast transmission needs to support transmission of multi-view streams. .

The current windows and linux systems manage multicast groups by attaching to UDP sockets. The UDP socket must specify the multicast IP address and port to join and leave the multicast group. In this case, the UDP socket can only receive multicast packets whose destination port is the binding port (or the default port of the system).

In the case of the implementation of the traditional protocol stack, if the same multicast group is to receive multicast packets of different ports, multiple UDP multicast sockets need to be created. Each socket receives multicast packets containing one type of port and adds the application layer. Management complexity of UDP multicast sockets. Moreover, because the number of multicast routing entries of the CDN (Content Delivery Network) server interface network card, the protocol stack, and the number of multicast groups on the bearer network router (that is, the number of multicast routing entries) are limited, the multicast resources are limited. It is very scarce. Therefore, a new multicast group communication method is needed to implement multi-port multicast communication in the same multicast group.

Summary of the invention

The present disclosure provides a multi-port multicast method, device, and computer readable storage medium for solving the problem that a multicast group cannot implement multi-port multicast communication in the related art.

In order to achieve the above object, the present disclosure adopts the following technical solutions:

According to an aspect of the present disclosure, a multi-port multicast method is provided, including: configuring a multi-port list locally after joining a multicast group; and, according to the multi-port list, a destination port in the received multicast packet Matching is performed, and when the matching is successful, the multicast packet is processed.

Optionally, the locally configuring the multi-port list includes: pre-adding a port configuration interface in the multicast protocol stack; and adding, by using the port configuration interface, multiple ports to the multicast in a hash list In the protocol stack.

Optionally, the matching, by the multi-port list, the destination port in the received multicast packet, including: verifying the multicast address in the multicast packet; and, when the verification succeeds, determining the group Whether any destination port in the broadcast message is located in the multi-port list; if it is located, the match is successful, and the multicast message is added to the receive queue.

Optionally, the method further includes: when the multicast address verification fails or when any destination port in the multicast packet is not in the multi-port list, the multicast packet is discarded.

Optionally, the method further includes: when a multi-port multicast packet needs to be sent, configuring a different port into the destination port field in the multicast packet.

According to an aspect of the present disclosure, a multi-port multicast device including a memory and a processor; wherein the memory stores a multi-port multicast program, when the multi-port multicast program is executed by the processor The following steps are performed: after the multicast group is added, the multi-port list is configured locally; and the destination port in the received multicast packet is matched according to the multi-port list, and when the matching is successful, the group is processed. Broadcast message.

Optionally, when the multi-port multicast program is executed by the processor, the following steps are implemented: pre-adding a port configuration interface in the multicast protocol stack; and, by using the port configuration interface, multiple ports are A hash list form is added to the multicast protocol stack.

Optionally, when the multi-port multicast program is executed by the processor, the following steps are performed: verifying a multicast address in the multicast packet; and, when the verification is successful, determining the multicast packet Whether any of the destination ports in the text is located in the multi-port list; when located, the matching is successful, and the multicast packet is added to the receiving queue.

Optionally, when the multi-port multicast program is executed by the processor, the following steps are implemented: when a multi-port multicast packet needs to be sent, the port is configured to be in the multicast packet. In the port field.

According to an aspect of the present disclosure, a computer readable storage medium storing a multi-port multicast program when the multi-port multicast program is executed by the processor to implement the above The steps in the multi-port multicast method.

The multi-port multicast method, device, and computer readable storage medium provided by the embodiments of the present disclosure configure a multi-port list set to multi-port communication after establishing multicast group communication; and receive different port numbers when receiving When a multicast packet is received, the multicast packet can be processed according to the multi-port list to receive packets of different ports in the same multicast group. It can be seen that the configuration of the multi-port list does not need to establish multiple UDP sockets according to the disclosure, which reduces the creation of the socket and reduces the management complexity of the application layer socket.

The above description is only an overview of the technical solutions of the present disclosure, and the above-described and other objects, features and advantages of the present disclosure can be more clearly understood. Exemplary embodiments of the present disclosure are provided below.

DRAWINGS

In order to more clearly illustrate the embodiments of the present disclosure or related aspects, the drawings used in the embodiments or the related description will be briefly described below. It is obvious that the drawings in the following description are only the disclosure of the present disclosure. In some embodiments, other drawings may be obtained from those of ordinary skill in the art without departing from the scope of the invention.

1 is a flowchart of a multi-port multicast method according to an embodiment of the present disclosure;

2 is a flowchart of a multi-port multicast method according to an embodiment of the present disclosure;

FIG. 3 is a schematic block diagram of a multi-port multicast device according to an embodiment of the present disclosure.

Detailed ways

The present disclosure is described in detail below in conjunction with the drawings and exemplary embodiments. It is to be understood that the exemplary embodiments described herein are merely illustrative of the disclosure and are not intended to be limiting.

In the protocol stack of the general operating systems such as windows and linux, the IGMP (Internet Group Management Protocol) protocol is used to control and manage multicast groups. Only the IGMP protocol directly contacts the multicast host. The router that runs IGMP is responsible for managing the joining, leaving, and maintaining group membership of the group members. For the IGMP packet format, see the following table, including the version field, including the IGMP version identifier. Currently, there are three versions of V1, V2, and V3. Type fields, including membership query (0x11), membership report (0x12), checksum. Field, set to the checksum of IGMP protocol packets; group address; when a membership report is being sent, the group address field contains the multicast address. When set to a membership query, this field is 0 and is ignored by the host.

Table 1

The format of the UDP packet used by the multicast group when performing UDP socket communication is as follows:

In UDP packets, only the source and destination ports represent fields of data packet length, UDP data packet checksum, and UDP data.

Table 2

As shown in the IGMP protocol specification and the packet format, the IGMP protocol has no relationship with the IP address of the multicast group and is not related to the port of the UDP protocol carried on the IP. Multicast packets are carried on the IP and UDP protocols. Therefore, it is feasible to transmit multi-port data flows on a multicast group, and it does not affect the normal operation of the IGMP protocol family. Based on the above ideas, the multi-port multicast method of the present disclosure is proposed.

The multi-port multicast method provided by the embodiment of the present disclosure, as shown in FIG. 1, includes the following steps.

In step 101, after joining the multicast group, the multi-port list is configured locally.

In this step, when a multicast host wants to join a multicast group, you need to create a UDP socket and set the IP_ADD_MEMBERSHIP attribute in the multicast protocol stack. Then, an IGMP protocol join message is sent to the switch to complete the action of joining the multicast group. If the host wants to leave the multicast group, you need to set the IP_DROP_MEMBERSHIP attribute of the IP layer of the UDP socket to send the IGMP Leave message to the switch to complete the action of leaving the multicast group.

After the multicast host joins the multicast group, UDP socket communication is established. In this embodiment, the multicast group protocol stack is improved, and a multi-port configuration interface is added to the protocol stack. After the multicast group communication is established, the port number can be configured through the multi-port configuration interface, and the port number is saved in the hash protocol form to the corresponding data structure of the UDP socket communication in the multicast protocol stack.

In step 102, the port in the received multicast packet is matched according to the multi-port list, and when the matching is successful, the multicast packet is processed.

After the multicast group is added to the multicast group, the multicast packets sent by the switch are matched according to the multi-port list in the UDP socket communication.

When the communication is performed in the multicast group (between the multicast host and the switch), the IP protocol is used to carry the UDP protocol. Therefore, after receiving the multicast packet, the multicast address in the multicast packet is also the multicast IP address. Address) for verification. After the verification is passed, the next step of verifying the port number is performed. If the authentication fails, the current multicast packet is not in the group. The multicast packet is discarded.

The port number set in the multi-port list is matched with the destination port number in the multicast packet when the port in the received multicast packet is matched. When the destination port number is any port number in the multi-port list, the multicast packet is a processable packet, and the packet is added to the receiving queue for subsequent processing in an embodiment. If the destination port number does not exist in the multi-port list, the multicast packet is directly discarded.

Based on the above, it is known that when performing multicast group communication, the packet is not limited to the processing of the packet of the specific destination port, but the multi-port list is configured in the local protocol stack, and the multi-port list can be used for different purposes. The processing of packets on the port enables the reception of data streams of different ports in the same multicast group. In this embodiment, multiple methods are not required, and the foregoing method can be implemented through a single socket, which effectively reduces communication complexity and saves multicast resources.

Optionally, the method may further include sending a multicast message.

When you need to send multi-port multicast packets, you can configure different ports in the destination port field of the multicast packets. When you need to send a multi-port multicast packet, you can configure the port number to be sent as required. The data packet carrying the multi-port number is encapsulated by the protocol used by the multicast address and then sent to the multicast. Just in the group.

The technical content of the present disclosure will be described in detail below with reference to the accompanying drawings and embodiments.

In this embodiment, as an example, the multicast host may adopt a Linux protocol stack. Of course, the disclosure is not limited to the Linux protocol stack, and may also be a Windows protocol stack. In this embodiment, the IGMP protocol packet is used to manage the joining and leaving the multicast group, and the multicast information is reported. The multicast host uses the IP and UDP protocols to communicate, and carries the data content carried by the UDP protocol through the IP protocol. Specify the destination address as the multicast address (multicast IP address) in the IP packet header, and specify different destination ports in the UDP protocol header to indicate different data flows. As shown in FIG. 2, the multi-port multicast method of this embodiment may include the following steps.

In step 201, the multicast host creates a UDP socket and sets the IP_ADD_MEMBERSHIP interface of the UDP socket IP layer.

In step 202, the multicast host uses the Linux protocol stack to notify the local operating system of the occurrence of IGMP messages through the IP_ADD_MEMBERSHIP interface, and sends the packets to the switch to generate a multicast entry on the switch.

Optionally, a multicast MAC address and a multicast IP address are created on the network port of the local system when the IGMP protocol packet is generated, and the IGMP protocol packet is sent to the switch.

In step 203, after the multicast host joins the multicast group, multiple ports are configured to be added to the UDP socket through the IP_ADD_MEMBERPORT interface.

An IP_ADD_MEMBERPORT interface needs to be added to the Linux protocol stack to notify the local operating system to add the specified port to the multicast UDP socket.

In the Linux protocol stack, the __be16inet_sport field in the struct inet_sock data structure indicates the socket source port; the struct ip_mc_socklist mc_list field indicates the list of joined multicast groups; in the struct ip_mc_socklist structure, the struct ip_mreqn multi field indicates the information of the multicast group.

In order to enable the multicast UDP socket to receive multicast packets of multiple ports, in the embodiment of the present disclosure, a multicast multi-port hash table is added to the struct ip_mc_socklist data structure of the Linux protocol stack, that is, struct inet_mc_hashbucket port_bucket , store the port information of the multicast UDP socket. The implementation code can be, for example:

In step 205, the multicast host receives the multicast packet and matches the multi-port hash table of the multicast IP address to which the UDP socket belongs in the multicast packet. When the match is passed, the multicast packet is added to the receive queue.

After the multicast group communication is established, the switch sends the multicast packets belonging to the multicast group to all multicast hosts that join the multicast group. Here, the switch uses UDP sockets to communicate, and only the packets are forwarded according to the multicast IP address. The processing of the packets is performed by the multicast host.

The Linux protocol stack can receive multicast packets containing multiple ports through the kernel receiving function. When receiving a multicast packet, check whether the UDP socket belongs to the multicast group by checking the multicast IP address to which the UDP socket belongs. If it belongs to the multicast group, it scans the multi-port hash table of the struct inet_sock member of the UDP socket and matches the destination port in the multicast packet.

If the destination port of the multicast packet matches a port in the multi-port hash table of the UDP socket, the corresponding data packet is added to the receiving queue of the UDP socket, and the application layer program waits for the multicast packet of the UDP socket to be received. .

If the destination port of the multicast packet is multiple, the device detects that any destination port is in the multi-port hash table, and then matches the packet to add the corresponding data packet to the receive queue.

When a multicast host sends multicast packets through a UDP socket, it can be sent in the UDP protocol format. If the UDP socket needs to send UDP multicast packets containing multiple ports, you only need to fill in different port values in the destination port field, and encapsulate the multicast IP address through the IP protocol. This can implement UDP socket multi-port group. The transmission of the broadcast message.

Based on the above, in the embodiment, the related resident operating system multicast group management application is extended. In this embodiment, the multicast group joins and leaves the IP_ADD_MEMBERSHIP command compatible with the Linux protocol stack UDP socket. At the same time, by adding the IP_ADD_MEMBERPORT interface, you can add multiple ports to the multicast UDP socket and modify the process of receiving UDP sockets for multicast packets, so that the Linux protocol stack can receive multiple multicast packets containing different ports.

According to an embodiment of the present disclosure, there is provided a multi-port multicast device configured to implement the multi-port multicast method described above. As shown in Figure 3. The device includes a processor 32 and a memory 31 that stores instructions executable by the processor 32.

The processor 32 may be a general-purpose processor, such as a central processing unit (CPU), or may be a digital signal processor (DSP), an application specific integrated circuit (ASIC), or Is one or more integrated circuits configured to implement embodiments of the present disclosure.

The memory 31 can be used to store program code and transfer the program code to the CPU. The memory 31 may include a volatile memory such as a random access memory (RAM). The memory 31 may also include a non-volatile memory such as a read-only memory (ROM), a flash memory, a hard disk drive (HDD), or a solid state hard disk. (solid-state drive, SSD). The memory 31 may also include a combination of memories of the above kind.

The multi-port multicast device provided by the present disclosure may include a memory 31 and a processor 32. A multi-port multicast program is stored in the memory 31. When the multi-port multicast program is executed by the processor 32, the following steps are performed: after joining the multicast group, the multi-port list is locally configured; and, according to the multi-port list The destination port is matched in the received multicast packet. When the match is successful, the multicast packet is processed.

Optionally, when the multi-port multicast program is executed by the processor 32, the following steps are implemented: pre-adding a port configuration interface in the multicast protocol stack; and configuring multiple ports through the port configuration interface It is added to the multicast protocol stack in the form of a hash list.

Optionally, when the multi-port multicast program is executed by the processor 32, the following steps are performed: verifying a multicast address in the multicast packet; and, when the verification is successful, determining the group Whether any destination port in the broadcast message is located in the multi-port list; if it is located, the match is successful, and the multicast message is added to the receive queue.

When the multicast address verification fails or when any destination port in the multicast packet is not in the multi-port list, the multicast packet is discarded.

Optionally, when the multi-port multicast program is executed by the processor 32, the following steps are performed: when a multi-port multicast message needs to be sent, different ports are configured in the multicast packet. In the destination port field.

It should be noted that, in the device embodiment, only the respective steps are briefly described. For the implementation method, the foregoing has been described in detail with reference to FIG. 1 and FIG. 2, and is not repeated in this embodiment.

The embodiment of the present disclosure also provides a computer readable storage medium. The computer readable storage medium herein stores one or more programs. The computer readable storage medium may include a volatile memory such as a random access memory; the memory may also include a non-volatile memory such as a read only memory, a flash memory, a hard disk or a solid state hard disk; the memory may also include the above categories a combination of memory. One or more programs in a computer readable storage medium may be executed by one or more processors to implement all of the steps and steps in the multi-port multicast method provided by the method embodiments. For the implementation of the steps, reference may be made to the detailed description in the above embodiments, and details are not described in this embodiment.

The disclosure supplements the Linux protocol and effectively solves the problem that one multicast group can receive multiple multicast streams. The IP_ADD_MEMBERPORT interface is added to the Linux protocol stack to enhance the receiving function of the UDP socket multicast packets in the Linux protocol stack. The multicast packets containing different ports are received in the same multicast UDP socket. The function of sending and receiving multicast packets on the port is effective. This reduces the complexity of socket management and reduces the complexity of application layer socket management. It reduces IGMP protocol packet exchange between the streaming server node and the switch, saving multicast on related devices. The number of occupations of the group entry.

A person skilled in the art can understand that all or part of the process of implementing the above embodiment method can be completed by a computer program to instruct related hardware, and the program can be stored in a computer readable storage medium. The flow of an embodiment of the methods as described above may be included.

While the present invention has been described by the embodiments of the invention, it will be understood that Thus, it is intended that the present invention cover the modifications and the modifications

Claims

A multi-port multicast method includes:

After joining a multicast group, configure a multi-port list locally.

The destination port in the received multicast packet is matched according to the multi-port list. When the matching succeeds, the multicast packet is processed.
The multi-port multicast method of claim 1, wherein the locally configuring the multi-port list comprises:

Add a port configuration interface in advance in the multicast protocol stack;

A plurality of ports are added to the multicast protocol stack in a hash list through the port configuration interface.
The multi-port multicast method according to claim 1 or 2, wherein the matching the destination port in the received multicast packet according to the multi-port list comprises:

Verifying the multicast address in the multicast packet;

When the verification succeeds, it is determined whether any of the destination ports in the multicast packet are located in the multi-port list; when located, the matching succeeds, and the multicast packet is added to the receiving queue.
The multi-port multicast method of claim 3, wherein the method further comprises:

When the multicast address verification fails or when any destination port in the multicast packet is not in the multi-port list, the multicast packet is discarded.
The multi-port multicast method of claim 1, wherein the method further comprises:

When a multi-port multicast packet needs to be sent, configure a different port to the destination port field in the multicast packet.
A multi-port multicast device includes a memory and a processor; wherein the memory stores a multi-port multicast program, and when the multi-port multicast program is executed by the processor, the following steps are implemented:

After joining a multicast group, configure a multi-port list locally.

The destination port in the received multicast packet is matched according to the multi-port list. When the matching succeeds, the multicast packet is processed.
The multi-port multicast device of claim 6, wherein when said multi-port multicast program is executed by said processor, the following steps are implemented:

Add a port configuration interface in advance in the multicast protocol stack;

A plurality of ports are added to the multicast protocol stack in a hash list through the port configuration interface.
The multi-port multicast device according to claim 6 or 7, wherein when said multi-port multicast program is executed by said processor, the following steps are implemented:

Verifying the multicast address in the multicast packet;

When the verification succeeds, it is determined whether any of the destination ports in the multicast packet are located in the multi-port list; when located, the matching succeeds, and the multicast packet is added to the receiving queue.
The multi-port multicast device of claim 6, wherein when said multi-port multicast program is executed by said processor, the following steps are implemented:

When a multi-port multicast packet needs to be sent, configure a different port to the destination port field in the multicast packet.
A computer readable storage medium, wherein the computer readable storage medium stores a multi-port multicast program, when the multi-port multicast program is executed by the processor, to implement any of claims 1 to 5 The steps in the multi-port multicast method described in the item.