Multicast communication method, device and system

Abstract

The present disclosure relates to a multicast communication method, device, and system, and relates to the field of communication technology. The multicast communication method includes: receiving authentication information of a multicast receiver sent by a receiver-side edge router, where different authentication information corresponds to different user needs; performing path calculation based on the multicast receiver's authentication information to determine a forwarding path corresponding to the authentication information; and sending relevant information about the forwarding path to the multicast source-side edge router and the receiver-side edge router to implement replication and forwarding of multicast messages. The technical solution of the present disclosure can provide different service guarantees based on different user needs, thereby improving communication performance.

Description

Technical Field

[0001] The present disclosure relates to the field of communication technology, and in particular to a multicast communication method, a multicast communication device, a multicast communication system, and a non-volatile computer-readable storage medium. Background Art

[0002] During the multicast information transmission process, related technologies provide the same service to all access points. Summary of the Invention

[0003] The inventors of the present disclosure have discovered that the above-mentioned related technologies have the following problems: they are unable to provide different service guarantees according to different user needs, resulting in a decrease in communication performance.

[0004] In view of this, the present disclosure proposes a multicast communication technology solution that can provide different service guarantees according to different user needs, thereby improving communication performance.

[0005] According to some embodiments of the present disclosure, a multicast communication method is provided, including: receiving authentication information of a multicast receiver sent by a receiver-side edge router, where different authentication information corresponds to different user needs; performing path calculation based on the authentication information of the multicast receiver to determine a forwarding path corresponding to the authentication information; and sending relevant information of the forwarding path to the multicast source-side edge router and the receiver-side edge router to realize replication and forwarding of multicast messages.

[0006] In some embodiments, performing path calculation based on the authentication information of the multicast receiver to determine the forwarding path corresponding to the authentication information includes: determining the path calculation parameters corresponding to the authentication information based on the stored correspondence between different authentication information and different path calculation parameters; and calculating the forwarding path using the corresponding path calculation parameters.

[0007] In some embodiments, the multicast communication method also includes: receiving multiple authentication information and corresponding multiple path calculation parameters returned by the application platform based on the registration information of the edge router on the multicast source side, and saving the correspondence between different authentication information and different path calculation parameters. Different authentication information and its corresponding path calculation parameters are generated by the application platform based on different user needs and / or different user levels.

[0008] In some embodiments, sending forwarding path related information to the multicast source side edge router and the receiver side edge router includes sending a control label corresponding to the forwarding path to the receiver side edge router, where different control labels correspond to different inbound interfaces.

[0009] In some embodiments, sending a control label corresponding to the forwarding path to the edge router on the receiver side includes: sending a first PCEP (Path Computation Element Communication Protocol) message to the edge router on the receiver side, the first PCEP message including a first object, the first object including a control label for distinguishing different user needs, and an inbound interface and / or VPN (Virtual Private Network) information corresponding to the control label.

[0010] In some embodiments, sending relevant information of the forwarding path to the multicast source side edge router and the receiver side edge router includes: sending a second PCEP message to the receiver side edge router, and the second PCEP message includes a second object for the forwarding path in the BIER (Bit Index Explicit Replication) network.

[0011] According to other embodiments of the present disclosure, a multicast communication device is provided, including: a receiving unit for receiving authentication information of a multicast receiver sent by a receiver-side edge router, where different authentication information corresponds to different user needs; a computing unit for performing path calculation based on the authentication information of the multicast receiver and determining a forwarding path corresponding to the authentication information; and a sending unit for sending relevant information of the forwarding path to the multicast source-side edge router and the receiver-side edge router to realize replication and forwarding of multicast messages.

[0012] In some embodiments, the calculation unit determines the path calculation parameters corresponding to the authentication information based on the stored correspondence between different authentication information and different path calculation parameters, and calculates the forwarding path using the corresponding path calculation parameters.

[0013] In some embodiments, the receiving unit receives multiple authentication information and corresponding multiple path calculation parameters returned by the application platform based on the registration information of the multicast source side edge router, and saves the correspondence between different authentication information and different path calculation parameters. Different authentication information and its corresponding path calculation parameters are generated by the application platform based on different user needs and / or different user levels.

[0014] In some embodiments, the sending unit sends a control label corresponding to the forwarding path to the edge router on the receiver side, and different control labels correspond to different inbound interfaces.

[0015] In some embodiments, the sending unit sends a first PCEP message to the receiver-side edge router, where the first PCEP message includes a first object, where the first object includes a control tag for distinguishing different user requirements, and an inbound interface and / or VPN information corresponding to the control tag.

[0016] In some embodiments, the sending unit sends a second PCEP message to the receiver edge router, where the second PCEP message includes a second object for identifying a bit index to explicitly copy the forwarding path in the BIER network.

[0017] According to further embodiments of the present disclosure, a multicast communication device is provided, comprising: a memory; and a processor coupled to the memory, wherein the processor is configured to execute the multicast communication method in any of the above embodiments based on instructions stored in the memory device.

[0018] According to some further embodiments of the present disclosure, a non-volatile computer-readable storage medium is provided, on which a computer program is stored. When the program is executed by a processor, the multicast communication method in any of the above embodiments is implemented.

[0019] According to some further embodiments of the present disclosure, a multicast communication system is provided, comprising: a controller for executing the multicast communication method in any one of the above embodiments; a receiver-side edge router for forwarding authentication information of the multicast receiver to the controller, and replicating and forwarding multicast messages according to relevant information of the forwarding path sent by the controller; and a multicast source-side edge router for replicating and forwarding multicast messages according to relevant information of the forwarding path sent by the controller.

[0020] In some embodiments, the multicast communication system further includes: an application platform for generating different authentication information and corresponding path calculation parameters based on the registration information of the multicast source side edge router forwarded by the controller, different user requirements and / or different user levels.

[0021] In the above embodiment, based on different authentication information, differentiated control of multicast joining is implemented according to different user needs. In this way, different service guarantees can be provided according to different user needs, thereby improving communication performance. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments of the present disclosure and, together with the description, serve to explain the principles of the present disclosure.

[0023] The present disclosure can be more clearly understood from the following detailed description with reference to the accompanying drawings:

[0024] Figure 1 A flowchart illustrating some embodiments of the multicast communication method disclosed herein;

[0025] Figure 2 A schematic diagram illustrating some embodiments of the multicast communication method disclosed herein;

[0026] Figure 3 Schematic diagrams showing other embodiments of the multicast communication method disclosed herein;

[0027] Figure 4 A block diagram illustrating some embodiments of the multicast communication apparatus of the present disclosure;

[0028] Figure 5 A block diagram showing some other embodiments of the multicast communication device disclosed herein;

[0029] Figure 6 A block diagram illustrating some further embodiments of the multicast communication device disclosed herein;

[0030] Figure 7 A block diagram illustrating some embodiments of the multicast communication system of the present disclosure is shown. DETAILED DESCRIPTION

[0031] Various exemplary embodiments of the present disclosure will now be described in detail with reference to the accompanying drawings. It should be noted that unless otherwise specifically stated, the relative arrangement of components and steps, numerical expressions and numerical values ​​set forth in these embodiments do not limit the scope of the present disclosure.

[0032] At the same time, it should be understood that for the convenience of description, the sizes of the various parts shown in the drawings are not drawn according to the actual proportional relationship.

[0033] The following description of at least one exemplary embodiment is merely illustrative in nature and is in no way intended to limit the present disclosure, its application, or uses.

[0034] Technologies, methods, and equipment known to ordinary technicians in the relevant art may not be discussed in detail, but where appropriate, the technologies, methods, and equipment should be considered part of the specification.

[0035] In all examples shown and discussed herein, any specific values ​​should be interpreted as merely exemplary and not limiting. Therefore, other examples of the exemplary embodiments may have different values.

[0036] It should be noted that like reference numerals and letters refer to like items in the following figures, and therefore, once an item is defined in one figure, it need not be further discussed in subsequent figures.

[0037] Because there was no authentication mechanism before, multicast services could only provide the same service to all access points and could not meet customized needs. Based on the addition of user authentication, different service guarantees can be provided to different categories of users according to their different user needs.

[0038] As previously mentioned, due to the lack of an authentication mechanism, multicast services can only provide the same service to all accessors during multicast information transmission, and cannot meet customized requirements. This disclosure addresses the above technical issues and, based on the addition of user authentication, can provide different service guarantees for different categories of users based on their different user needs.

[0039] This disclosure proposes a method for providing differentiated services based on controllable multicast. Leveraging the controller's routing capabilities, it can generate multicast data forwarding paths with different guarantees. Furthermore, leveraging the controllable multicast's authentication capabilities, it enables differentiated services for different receivers on the same router. For example, the technical solution of this disclosure can be implemented through the following embodiments.

[0040] Figure 1 A flow chart showing some embodiments of the multicast communication method of the present disclosure.

[0041] like Figure 1 As shown, in step 110, the authentication information of the multicast receiver sent by the edge router on the receiver side is received, and different authentication information corresponds to different user requirements.

[0042] In some embodiments, receivers of different levels carry different application multicast service access authentication information in IGMPv3 (Internet Group Management Protocol) or MLDv2 (Multicast Listener Discover) messages, applying to join the same multicast group and use a specific multicast source. The edge router on the receiver side converts the IGMPv3 or MLDv2 messages sent by these different receiver levels into multiple PCEP messages and sends them to the controller.

[0043] For example, receivers 1, 2, and 3 each carry different application multicast service access authentication information in an IGMPv3 or MLDv2 message to apply to join the multicast group and multicast source reported by PE5. Each authentication information corresponds to the service requirements of low latency, basic services, and high bandwidth, respectively.

[0044] PE2 converts the IGMPv3 or MLDv2 messages sent by receivers 1, 2, and 3 into multiple PCEP messages and sends them to the controller to request multicast joining.

[0045] In step 120, path calculation is performed based on the authentication information of the multicast receiver to determine a forwarding path corresponding to the authentication information.

[0046] In some embodiments, the path calculation parameters corresponding to the authentication information are determined based on the stored correspondence between different authentication information and different path calculation parameters; and the forwarding path is calculated using the corresponding path calculation parameters.

[0047] For example, the controller calculates paths based on the different service requirements set by the application at the edge router on the receiver side, obtains the corresponding forwarding paths for various user requirements, and sends them to the router on the source side.

[0048] For example, the controller matches the corresponding authentication information with the multicast join message sent by the edge router on the receiver side. If a match is successful, the controller calculates the path based on the service requirements corresponding to the authentication information using the corresponding calculation parameters. Ultimately, the controller obtains the corresponding forwarding paths for each requirement and sends them to the edge router on the multicast source side to guide the router in forwarding the multicast data.

[0049] In some embodiments, the controller may determine corresponding path calculation parameters according to a correspondence between a plurality of stored authentication information and a plurality of path calculation parameters.

[0050] For example, the receiving application platform receives multiple authentication information and corresponding multiple path calculation parameters returned based on the registration information of the edge router on the multicast source side, and saves the correspondence between different authentication information and different path calculation parameters. Different authentication information and its corresponding path calculation parameters are generated by the application platform based on different user needs and / or different user levels.

[0051] For example, a multicast source-side edge router registers multicast group and source information with the controller via PCEP messages. The controller stores the registration information (registered multicast group and source information) sent by the multicast source-side edge router and makes it available to applications through service-based interfaces. Based on the multicast group and source information, the application customizes service requirements for different user levels and generates different access authentication information for each service requirement. This authentication information is then sent to the controller (which can be an SDN (Software Defined Network) controller) for authentication of the multicast receiver's joining.

[0052] For example, the controller saves the registration information sent by the edge router on the multicast source side and informs the live broadcast platform (i.e., the application platform). The live broadcast platform converts user needs and user levels into requirements for the quality of the underlying network link and sends different authentication information and corresponding calculation parameters to the controller.

[0053] In step 130, the forwarding path related information is sent to the edge router on the multicast source side and the edge router on the receiver side to implement replication and forwarding of the multicast message.

[0054] In some embodiments, a control label corresponding to the forwarding path is sent to the edge router on the receiver side, and different control labels correspond to different inbound interfaces.

[0055] For example, the controller will send data forwarding control labels to the edge router on the receiver side based on different authentication information. Different control labels correspond to different inbound interfaces and different data forwarding paths.

[0056] For example, receiver 1 corresponds to low latency requirements, and the path with low latency requirements uses inbound interface A. After the edge router on the receiver side receives the data from interface A, it forwards it to receiver 1.

[0057] In some embodiments, a first PCEP message is sent to a receiver-side edge router, the first PCEP message including a first object, the first object including a control tag for distinguishing different user requirements, and an inbound interface and / or VPN information corresponding to the control tag.

[0058] For example, the controller adds an object to the PCEP message sent to the edge router on the receiver side, which contains a control tag used to distinguish different requirements and related information corresponding to the control tag. The related information can include inbound interface, VPN, etc.

[0059] In some embodiments, the multicast source sends an application multicast message; the edge router on the multicast source side follows the different paths issued by the controller; in the BIER network, replication and forwarding are performed through BIER-TE (Bit Index Explicit-Traffic Engineering); the receiver side router copies and forwards the application multicast message to the receiver according to the control label.

[0060] For example, the controller will send data forwarding control labels to the edge router on the receiver side based on different authentication information. Different control labels correspond to different inbound interfaces and different data forwarding paths.

[0061] For example, if control label 1 is used, the packet's inbound interface is interface A, VPN A is used, and a low-latency forwarding path is used to control receiver 1. If control label 2 is used for receiver 2, the packet's inbound interface is interface B, VPN B is used, and a basic forwarding path is used. If control label 3 is used for receiver 3, the packet's inbound interface is interface C, VPN C is used, and a high-bandwidth forwarding path is used.

[0062] In some embodiments, sending relevant information of the forwarding path to the multicast source side edge router and the receiver side edge router includes: sending a second PCEP message to the receiver side edge router, and the second PCEP message includes a second object for the forwarding path in the BIER network.

[0063] For example, a new object is added to the PCEP message sent by the controller to the source-side edge router to identify the detailed forwarding path in the BIER network and used for the implementation of BIER-TE.

[0064] In the above embodiment, user levels of third-party applications are categorized into different service requirements, and application-based identity authentication capabilities are used to isolate these requirements. Differentiated control of multicast joins is achieved based on the different authentication information of third-party applications, improving the flexibility of multicast joins. Leveraging the controller's routing capabilities, different forwarding paths are customized based on different demand parameters, achieving differentiated multicast service assurance. This also effectively reduces PCEP information exchange.

[0065] Figure 2 Schematic diagram showing some embodiments of the multicast communication method disclosed herein.

[0066] like Figure 2 As shown, there are edge routers such as source-side edge router PE5 and receiver-side edge router PE2 in AS (Autonomous System) Y. SLAs (Service-Level Agreements) 1 to 3 are set for different user levels.

[0067] In step 1, the multicast source-side edge router (PE5) registers the multicast group and multicast source information with the controller through a PCEP message.

[0068] In step 2, the controller saves the registration information sent by the edge router on the multicast source side and makes it available to the application through a service-based interface. Based on the multicast group and multicast source information, the application customizes different service requirements according to the user level and generates different access authentication information. It then sends it to the SDN controller for authentication of the multicast receiver to join.

[0069] In step three, receivers of different levels carry different application multicast service access authentication information in IGMPv3 or MLDv2 messages, apply to join the same multicast group, and use a specific multicast source.

[0070] In step 4, the edge router (PE2) on the receiver side converts the IGMPv3 or MLDv2 messages sent by these different levels of receivers into multiple PCEP messages and sends them to the controller.

[0071] In step 5, the controller calculates the path based on the different service requirements set by the application according to the edge router (PE2) on the receiver side, obtains the corresponding forwarding path for each requirement, and sends it to the router (PE5) on the source side.

[0072] In step six, the controller will send data forwarding control labels to the edge router (PE2) on the receiver side according to different authentication information. Different control labels correspond to different inbound interfaces and different data forwarding paths.

[0073] For example, receiver 1 has a low latency requirement, and the path with low latency requirement uses inbound interface A. After PE2 receives the data from interface A, it forwards it to receiver 1.

[0074] In step seven, the multicast source sends the application multicast message, and the edge router on the multicast source side copies and forwards it in the BIER network through BIER-TE according to the different paths issued by the controller (PE5); the router on the receiver side copies and forwards the application multicast message to the receiver according to the control label (see step six).

[0075] Figure 3 Schematic diagrams showing other embodiments of the multicast communication method disclosed herein.

[0076] like Figure 3 As shown, the application platform is a live broadcast platform.

[0077] In step 1, PE5 registers the information of the multicast group and multicast source with the controller through a PCEP message.

[0078] In step 2, the controller saves the registration information sent by PE5 and informs the live broadcast platform. The live broadcast platform converts the user's needs and user level into requirements for the quality of the underlying network link and sends different authentication information and calculation parameters to the controller.

[0079] In step 3, receivers 1, 2, and 3 carry different application multicast service access authentication information in IGMPv3 or MLDv2 messages, corresponding to low latency, basic services, and high bandwidth service requirements, respectively, and apply to join the multicast group and multicast source reported by PE5.

[0080] In step 4, PE2 converts the IGMPv3 or MLDv2 messages sent by receivers 1, 2, and 3 into multiple PCEP messages and sends them to the controller to request multicast joining.

[0081] In step 5, the controller matches the authentication information with the multicast join message sent by PE2. If a match is found, the controller calculates paths based on the service requirements corresponding to the authentication information and uses the corresponding calculation parameters. Ultimately, it determines the forwarding paths that meet the various requirements and sends them to PE5, instructing the router to forward the multicast data.

[0082] In step 6, the controller sends data forwarding control labels to PE2 based on the authentication information. Different control labels correspond to different inbound interfaces and data forwarding paths.

[0083] For example, if control label 1 is used, the packet's inbound interface is interface A, VPN A is used, and a low-latency forwarding path is used to control receiver 1. If control label 2 is used for receiver 2, the packet's inbound interface is interface B, VPN B is used, and a basic forwarding path is used. If control label 3 is used for receiver 3, the packet's inbound interface is interface C, VPN C is used, and a high-bandwidth forwarding path is used.

[0084] In step seven, the multicast source sends the application multicast message, and PE5 forwards it in the BIER network through BIER-TE according to the different paths issued by the controller. The receiver-side router copies and forwards the application multicast message to the receiver according to the control label (see step six).

[0085] Figure 4 A block diagram illustrating some embodiments of the multicast communication apparatus of the present disclosure.

[0086] like Figure 4 As shown, the multicast communication device 4 includes: a receiving unit 41, which is used to receive the authentication information of the multicast receiver sent by the edge router on the receiver side, and different authentication information corresponds to different user needs; a calculation unit 42, which is used to perform path calculation based on the authentication information of the multicast receiver and determine the forwarding path corresponding to the authentication information; a sending unit 43, which is used to send the relevant information of the forwarding path to the edge router on the multicast source side and the edge router on the receiver side to realize the replication and forwarding of the multicast message.

[0087] In some embodiments, the calculation unit 42 determines the path calculation parameters corresponding to the authentication information according to the stored correspondence between different authentication information and different path calculation parameters, and calculates the forwarding path using the corresponding path calculation parameters.

[0088] In some embodiments, the receiving unit 41 receives multiple authentication information and corresponding multiple path calculation parameters returned by the application platform based on the registration information of the multicast source side edge router, and saves the correspondence between different authentication information and different path calculation parameters. Different authentication information and its corresponding path calculation parameters are generated by the application platform based on different user needs and / or different user levels.

[0089] In some embodiments, the sending unit 43 sends a control label corresponding to the forwarding path to the edge router on the receiver side, and different control labels correspond to different inbound interfaces.

[0090] In some embodiments, the sending unit 43 sends a first PCEP message to the receiver-side edge router, where the first PCEP message includes a first object, which includes a control tag for distinguishing different user requirements, and an inbound interface and / or VPN information corresponding to the control tag.

[0091] In some embodiments, the sending unit 43 sends a second PCEP message to the receiver edge router, where the second PCEP message includes a second object for identifying a bit index that explicitly replicates a forwarding path in the BIER network.

[0092] Figure 5 A block diagram showing some other embodiments of the multicast communication device of the present disclosure.

[0093] like Figure 5 As shown, the multicast communication device 5 of this embodiment includes: a memory 51 and a processor 52 coupled to the memory 51 , and the processor 52 is configured to execute the multicast communication method in any one embodiment of the present disclosure based on instructions stored in the memory 51 .

[0094] The memory 51 may include, for example, a system memory, a fixed non-volatile storage medium, etc. The system memory may store, for example, an operating system, application programs, a boot loader, a database, and other programs.

[0095] Figure 6 A block diagram showing some further embodiments of the multicast communication device of the present disclosure.

[0096] like Figure 6 As shown, the multicast communication device 6 of this embodiment includes: a memory 610 and a processor 620 coupled to the memory 610 , and the processor 620 is configured to execute the multicast communication method in any of the aforementioned embodiments based on instructions stored in the memory 610 .

[0097] The memory 610 may include, for example, a system memory, a fixed non-volatile storage medium, etc. The system memory may store, for example, an operating system, application programs, a boot loader, and other programs.

[0098] The multicast communication device 6 may also include an input / output interface 630, a network interface 640, a storage interface 650, and the like. These interfaces 630, 640, and 650, as well as the memory 610 and the processor 620, may be connected, for example, via a bus 660. The input / output interface 630 provides a connection interface for input / output devices such as a display, mouse, keyboard, touch screen, microphone, and speakers. The network interface 640 provides a connection interface for various networked devices. The storage interface 650 provides a connection interface for external storage devices such as SD cards and USB flash drives.

[0099] Figure 7 A block diagram illustrating some embodiments of the multicast communication system of the present disclosure is shown.

[0100] like Figure 7 As shown, the multicast communication system 7 includes: a controller 71, which is used to execute the multicast communication method in any of the above embodiments; a receiver-side edge router 72, which is used to forward the authentication information of the multicast receiver to the controller, and to copy and forward the multicast message according to the relevant information of the forwarding path sent by the controller; and a multicast source-side edge router 73, which is used to copy and forward the multicast message according to the relevant information of the forwarding path sent by the controller.

[0101] In some embodiments, the multicast communication system 7 further includes an application platform 74 for generating different authentication information and corresponding path calculation parameters based on the registration information of the multicast source side edge router forwarded by the controller, different user requirements and / or different user levels.

[0102] Those skilled in the art will appreciate that embodiments of the present disclosure may be provided as methods, systems, or computer program products. Thus, the present disclosure may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware. Furthermore, the present disclosure may take the form of a computer program product implemented on one or more computer-usable non-transitory storage media, including but not limited to magnetic disk storage, CD-ROMs, optical storage, and the like, containing computer-usable program code.

[0103] The multicast communication method, multicast communication device, multicast communication system, and non-volatile computer-readable storage medium according to the present disclosure have been described in detail. To avoid obscuring the concepts of the present disclosure, some details known in the art have been omitted. Based on the above description, those skilled in the art will fully understand how to implement the technical solutions disclosed herein.

[0104] The methods and systems of the present disclosure may be implemented in many ways. For example, the methods and systems of the present disclosure may be implemented by software, hardware, firmware, or any combination of software, hardware, and firmware. The above order of steps for the method is for illustration only, and the steps of the method of the present disclosure are not limited to the order specifically described above unless otherwise specified. In addition, in some embodiments, the present disclosure may also be implemented as programs recorded in a recording medium, which include machine-readable instructions for implementing the methods according to the present disclosure. Therefore, the present disclosure also covers recording media that store programs for executing the methods according to the present disclosure.

[0105] Although some specific embodiments of the present disclosure have been described in detail by way of examples, those skilled in the art will appreciate that the above examples are for illustrative purposes only and are not intended to limit the scope of the present disclosure. Those skilled in the art will appreciate that modifications may be made to the above embodiments without departing from the scope and spirit of the present disclosure. The scope of the present disclosure is defined by the appended claims.

Claims

1. A multicast communication method, comprising: Receive the multicast receiver's authentication information sent by the receiver's edge router. Different authentication information corresponds to different user needs. Performing path calculation based on the authentication information of the multicast receiver to determine a forwarding path corresponding to the authentication information; The related information of the forwarding path is sent to the edge router on the multicast source side and the edge router on the receiver side to realize the copy and forwarding of the multicast message.

2. The multicast communication method according to claim 1, wherein: The performing path calculation according to the authentication information of the multicast receiver to determine the forwarding path corresponding to the authentication information includes: Determining the path calculation parameter corresponding to the authentication information according to the stored correspondence between different authentication information and different path calculation parameters; The forwarding path is calculated using the corresponding path calculation parameters.

3. The multicast communication method according to claim 2, further comprising: The receiving application platform receives multiple authentication information and corresponding multiple path calculation parameters returned according to the registration information of the edge router on the multicast source side, and saves the correspondence between the different authentication information and the different path calculation parameters. The different authentication information and the corresponding path calculation parameters are generated by the application platform according to different user needs and / or different user levels.

4. The multicast communication method according to claim 1, wherein: The sending of the forwarding path related information to the multicast source side edge router and the receiver side edge router includes: A control label corresponding to the forwarding path is issued to the edge router of the receiver, where different control labels correspond to different inbound interfaces.

5. The multicast communication method according to claim 4, wherein: The sending of the control label corresponding to the forwarding path to the edge router of the receiver includes: A first path computation unit communication protocol (PCEP) message is sent to the receiver-side edge router, where the first PCEP message includes a first object, where the first object includes the control label for distinguishing different user requirements, and an inbound interface and / or virtual private network (VPN) information corresponding to the control label.

6. The multicast communication method according to any one of claims 1 to 5, wherein: The sending of the forwarding path related information to the multicast source side edge router and the receiver side edge router includes: A second PCEP message is sent to the receiver edge router, where the second PCEP message includes a second object used to identify the bit index that explicitly replicates the forwarding path in the BIER network.

7. A multicast communication device, comprising: The receiving unit is used to receive the authentication information of the multicast receiver sent by the edge router of the receiver. Different authentication information corresponds to different user requirements. a calculation unit, configured to perform path calculation based on the authentication information of the multicast receiver and determine a forwarding path corresponding to the authentication information; The sending unit is used to send the relevant information of the forwarding path to the edge router on the multicast source side and the edge router on the receiver side to realize the copy and forwarding of the multicast message.

8. The multicast communication device according to claim 7, wherein: The calculation unit determines the path calculation parameters corresponding to the authentication information according to the stored correspondence between different authentication information and different path calculation parameters, and calculates the forwarding path using the corresponding path calculation parameters.

9. The multicast communication device according to claim 8, wherein: The receiving unit receives multiple authentication information and corresponding multiple path calculation parameters returned by the application platform based on the registration information of the multicast source side edge router, and saves the correspondence between the different authentication information and the different path calculation parameters. The different authentication information and the corresponding path calculation parameters are generated by the application platform according to different user needs and / or different user levels.

10. A multicast communication device, comprising: Memory; and A processor coupled to the memory, wherein the processor is configured to execute the multicast communication method according to any one of claims 1 to 6 based on instructions stored in the memory.

11. A non-volatile computer-readable storage medium having a computer program stored thereon, wherein when the program is executed by a processor, the multicast communication method according to any one of claims 1 to 6 is implemented.

12. A multicast communication system, comprising: A controller, configured to execute the multicast communication method according to any one of claims 1 to 6; The receiver-side edge router is used to forward the authentication information of the multicast receiver to the controller and copy and forward the multicast message according to the relevant information of the forwarding path issued by the controller; The edge router at the multicast source side is used to copy and forward the multicast message according to the relevant information of the forwarding path sent by the controller.

13. The multicast communication system according to claim 12, further comprising: The application platform is used to generate different authentication information and corresponding path calculation parameters according to the registration information of the multicast source side edge router forwarded by the controller, different user requirements and / or different user levels.

Images