WO2019184485A1 - 传输组播报文的方法、设备和系统 - Google Patents

传输组播报文的方法、设备和系统 Download PDF

Info

Publication number
WO2019184485A1
WO2019184485A1 PCT/CN2018/124157 CN2018124157W WO2019184485A1 WO 2019184485 A1 WO2019184485 A1 WO 2019184485A1 CN 2018124157 W CN2018124157 W CN 2018124157W WO 2019184485 A1 WO2019184485 A1 WO 2019184485A1
Authority
WO
WIPO (PCT)
Prior art keywords
subnet
destination
multicast
multicast packet
core network
Prior art date
Application number
PCT/CN2018/124157
Other languages
English (en)
French (fr)
Inventor
夏怒
陈建
朱夏
周军
黄一宏
李吉
韦乃文
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to KR1020207030626A priority Critical patent/KR102430395B1/ko
Priority to EP18912178.3A priority patent/EP3767901A4/en
Priority to JP2020552777A priority patent/JP7050177B2/ja
Publication of WO2019184485A1 publication Critical patent/WO2019184485A1/zh
Priority to US17/033,100 priority patent/US11736411B2/en

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/16Multipoint routing
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/02Details
    • H04L12/16Arrangements for providing special services to substations
    • H04L12/18Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/1886Arrangements for providing special services to substations for broadcast or conference, e.g. multicast with traffic restrictions for efficiency improvement, e.g. involving subnets or subdomains
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/28Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46Interconnection of networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/28Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46Interconnection of networks
    • H04L12/4633Interconnection of networks using encapsulation techniques, e.g. tunneling
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/74Address processing for routing
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/74Address processing for routing
    • H04L45/745Address table lookup; Address filtering
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic control in data switching networks
    • H04L47/70Admission control; Resource allocation
    • H04L47/80Actions related to the user profile or the type of traffic
    • H04L47/806Broadcast or multicast traffic

Definitions

  • the present application relates to the field of electronic technologies, and in particular, to a method, device, and system for transmitting a multicast message.
  • the functions of the network are becoming more and more powerful, and users can watch various live video broadcasts on the network. Since the live broadcast of the video is generally viewed by multiple users at the same time, the live broadcast data sent from the media server is received by multiple users, and the live broadcast data can be transmitted to multiple terminals in the form of multicast packets.
  • the data transmission network may include a core network and a subnet, and multiple subnets communicate with each other through the core network.
  • the routing device connected to the source device (usually the media server) that generates the multicast packet is called the source CE (Customer Edge) and the destination device (usually the terminal) that receives the multicast packet.
  • the routing device is called the destination CE.
  • the device that connects to the source CE can be called a BFIR (Bit Forwarding Ingress Router).
  • the device that connects to the destination CE can be called a BFER (Bit Forwarding Egress Router).
  • the subnet to which the BFIR belongs is called the source subnet
  • the subnet to which the BFER belongs is called the destination subnet.
  • the BFIR when the BFIR receives the multicast packet, it determines the number N of multicast packets to be sent to different destination subnets. Multicast packets are copied in the BFIR to obtain N multicast packets, which are sent to N different destination subnets. After the destination BPDU is forwarded to the corresponding BFER, the BFER forwards the packet to the destination CE based on the multicast address in the multicast packet.
  • the number of multicast packets that need to be transmitted is increased.
  • a method for transmitting a multicast packet is provided, where the method is applied to a device connected to a core network in a source subnet corresponding to a target multicast group, where the method includes:
  • the destination address in the outer encapsulation is the device connected to the core network in each destination subnet. address.
  • a device connected to the core network in the source subnet When a device connected to the core network in the source subnet receives the multicast packet, it copies the multicast packet according to the number of the destination subnet to which the multicast packet is sent. This prevents the multicast packet from being started. When entering the data transmission network, it is copied by BFIR. Thereby, the number of multicast messages in the data transmission network can be greatly reduced, and the occupation of network resources is reduced.
  • determining the address of the device connected to the core network among the plurality of destination subnets corresponding to the target multicast group including:
  • the mapping between the identifier information of the destination subnet and the address of the device connected to the core network in the destination subnet, and the header of the multicast packet Identification information of multiple destination subnets carried in the network, and determining an address of a device connected to the core network among the corresponding multiple destination subnets.
  • the BFIR receives the identification information (SI information) of the destination subnet from the controller, and adds the SI information to the header of the multicast packet.
  • SI information the identification information
  • the device connected to the core network in the source subnet receives the multicast packet, it can read the SI information in the header of the multicast packet.
  • determining the address of the device connected to the core network among the plurality of destination subnets corresponding to the target multicast group including:
  • the payload of the multicast packet carries a multicast address (192.168.1.1, 224.0.1.254), which can be determined based on the mapping between the preset multicast address and the address of the device connected to the core network in the destination subnet.
  • the method before the outer layer is separately added to each multicast packet, the method further includes:
  • the TE bit string of each destination subnet is added to the header of the corresponding multicast packet to obtain the multicast packet corresponding to each destination subnet.
  • the TE bit string of each destination subnet can also be added to the header of the multicast packet in the BFIR.
  • the TE bit string of each destination subnet is added to the header of the corresponding multicast packet, and the multicast packet corresponding to each destination subnet is obtained, including:
  • the TE bit string of the source subnet in the header of the corresponding multicast packet is replaced by the TE bit string of the destination subnet, and the multicast packet corresponding to each destination subnet is obtained.
  • the TE packet of the active subnet can carry the TE bit string of the active subnet to indicate how the multicast packet is forwarded in the source subnet.
  • the source subnet originally carried in the header of the multicast packet
  • the TE bit string has no effect. Therefore, in the device connected to the core network in the source subnet, the TE bit string of each destination subnet received from the controller can be replaced with the TE of the source subnet in the header of the corresponding multicast packet.
  • the bit string obtains the multicast packet corresponding to each destination subnet.
  • a method for transmitting a multicast message is provided, where the method is applied to a controller, and the method includes:
  • the TE bit string of each destination subnet is sent to the device connected to the core network in the corresponding destination subnet or the device connected to the core network in the source subnet corresponding to the target multicast group.
  • the method further includes:
  • the identifier information and the BFIR corresponding to the target multicast group are Determining, by the source subnet, the identifier information of the device connected to the core network, and determining the TE bit string of the source subnet, including:
  • the method further includes:
  • the identification information of each destination subnet is sent to the BFIR.
  • a method for transmitting a multicast message is provided, where the method is applied to BFIR, and the method includes:
  • the identifier information of each destination subnet is added to the header of the multicast packet, and each destination subnet is added through the multicast mode.
  • the multicast information of the identification information is forwarded.
  • the method further includes:
  • the identifier information of each destination subnet is added to the header of the multicast packet, and each destination is added by using a multicast mode.
  • the multicast packets of the subnet ID are forwarded, including:
  • the TE bit string and the identification information of each destination subnet are added to the header of the multicast packet, and the TE bit is added.
  • the multicast packets of the string and the identification information of each destination subnet are forwarded.
  • a method for transmitting a multicast packet is provided, where the method is applied to a device connected to a core network in a destination subnet corresponding to a target multicast group, where the method includes:
  • the outer layer encapsulation is removed to obtain the multicast packet.
  • the multicast packet to which the bit string of the destination subnet is added is forwarded.
  • bit string is a TE bit string
  • the method before adding the bit string of the destination subnet to the header of the multicast packet, the method further includes:
  • the adding a bit string of the destination subnet to the header of the multicast packet includes:
  • a device connected to a core network in a source subnet corresponding to a target multicast group where the device includes at least one module, and the at least one module is configured to implement the foregoing first aspect.
  • the method of transmitting multicast messages is provided, where the device includes at least one module, and the at least one module is configured to implement the foregoing first aspect.
  • a controller is provided, where the controller includes at least one module, and the at least one module is configured to implement the method for transmitting a multicast message provided by the foregoing second aspect.
  • a BFIR is provided, where the BFIR includes at least one module, and the at least one module is configured to implement the method for transmitting a multicast message provided by the foregoing third aspect.
  • a device connected to a core network in a destination subnet corresponding to a target multicast group where the device includes at least one module, and the at least one module is configured to implement the foregoing fourth aspect.
  • the method of transmitting multicast messages is provided, where the device includes at least one module, and the at least one module is configured to implement the foregoing fourth aspect.
  • a system for transmitting a multicast packet includes a device and a BFIR connected to a core network in a source subnet corresponding to a target multicast group;
  • the BFIR is configured to forward the multicast packet by using a multicast mode when receiving the multicast packet of the target multicast group;
  • the device connected to the core network in the source subnet is configured to: when receiving the multicast packet, determine an address of a device connected to the core network among multiple destination subnets corresponding to the target multicast group, Copying the multicast packet to obtain multiple multicast packets equal to the number of the plurality of destination subnets; adding outer layer encapsulation to each multicast packet, and adding the outer layer encapsulated multicast
  • the packet is forwarded, where the destination address in the outer package is the address of the device connected to the core network in each destination subnet.
  • the system further includes a controller
  • the controller is configured to send identification information of each destination subnet corresponding to the target multicast group to the BFIR;
  • the BFIR is further configured to add the identifier information of each destination subnet to a header of the multicast packet.
  • the device connected to the core network in the source subnet is configured to: when receiving the multicast packet, based on the identifier information of the preset destination subnet and the address of the device connected to the core network in the destination subnet. Corresponding relationship, and identifier information of multiple destination subnets carried in the header of the multicast packet, determining an address of a device connected to the core network in the corresponding multiple destination subnets.
  • system further includes: a device connected to the core network in the destination subnet corresponding to the target multicast group;
  • the controller is further configured to respectively determine a destination subnet to which the multiple BFERs corresponding to the target multicast group belong, according to identification information of devices connected to the core network in each destination subnet, and each destination subnet.
  • the identification information of the BFER in the medium determines the bit string of each destination subnet; respectively, sends the bit string of each destination subnet to the device connected to the core network in the corresponding destination subnet;
  • the device connected to the core network in the destination subnet is configured to: when receiving the multicast packet that is added to the outer layer, remove the outer layer encapsulation to obtain the multicast packet; The bit string is added to the header of the multicast packet, and the multicast packet to which the bit string of the destination subnet is added is forwarded.
  • the controller is further configured to: according to the identifier information of the BFIR corresponding to the target multicast group, and the identifier information of at least one device connected to the core network in the source subnet, Determining a bit string of the source subnet; transmitting a bit string of the source subnet to the BFIR;
  • the BFIR is further configured to receive a bit string of the source subnet sent by the controller; when receiving the multicast packet, the bit string of the source subnet and each destination subnet The identifier information is added to the header of the multicast packet, and the multicast packet to which the bit string of the source subnet and the identification information of each destination subnet are added is forwarded.
  • a device connected to a core network in a source subnet corresponding to a target multicast group includes a processor, a memory, a receiver, and a transmitter, where:
  • the processor is configured to determine, when the receiver receives the multicast packet of the target multicast group, the address of the device connected to the core network among the plurality of destination subnets corresponding to the target multicast group, The multicast packet is copied to obtain a plurality of multicast packets equal to the number of the plurality of destination subnets; and an outer layer is added to each multicast packet;
  • the transmitter is configured to forward the multicast packet that is added to the outer layer, where the destination address in the outer package is respectively the device connected to the core network in each destination subnet stored in the memory. address.
  • the processor is configured to:
  • Corresponding relationship between the identifier information of the destination subnet and the address of the device connected to the core network in the destination subnet, and the multicast, when the receiver receives the multicast packet of the target multicast group The identification information of multiple destination subnets carried in the header of the packet determines the address of the device connected to the core network among the corresponding multiple destination subnets.
  • the processor is configured to:
  • the receiver is further configured to receive a TE bit string of each destination subnet sent by the controller;
  • the processor is further configured to add the TE bit string of each destination subnet to the header of the corresponding multicast packet to obtain a multicast packet corresponding to each destination subnet.
  • the processor is configured to:
  • the TE bit string of the source subnet in the header of the corresponding multicast packet is replaced by the TE bit string of the destination subnet, and the multicast packet corresponding to each destination subnet is obtained.
  • a controller including a processor and a transmitter, wherein:
  • the processor is configured to respectively determine a destination subnet to which the multiple BFERs corresponding to the target multicast group belong, according to the identification information of the device connected to the core network in each destination subnet, and the BFER in each destination subnet. Identification information, respectively determining the TE bit string of each destination subnet;
  • the transmitter is configured to send a TE bit string of each destination subnet to a device connected to the core network in the corresponding destination subnet or a source subnet corresponding to the target multicast group, and connect to the core network. device of.
  • the processor is further configured to: according to the identifier information of the BFIR corresponding to the target multicast group, and the identifier information of at least one device connected to the core network in the source subnet, Determining a TE bit string of the source subnet;
  • the transmitter is further configured to send a TE bit string of the source subnet to the BFIR.
  • the processor when at least one BFER in the BFER corresponding to the target multicast group belongs to the source subnet, the processor is configured to:
  • the transmitter is further configured to:
  • the identification information of each destination subnet is sent to the BFIR.
  • a BFIR comprising a processor, a memory, a receiver, and a transmitter, wherein:
  • the receiver is configured to receive identification information of each destination subnet corresponding to the target multicast group sent by the controller;
  • the processor is configured to store identifier information of each destination subnet received by the receiver into the memory, and when the receiver receives the multicast packet of the target multicast group, Adding identification information of each destination subnet stored in the memory to a header of the multicast packet;
  • the transmitter is configured to forward the multicast packet with the identifier information of each destination subnet by using a multicast mode.
  • the receiver is further configured to receive a TE bit string of a source subnet corresponding to the target multicast group sent by the controller;
  • the processor is configured to add the TE bit string and the identification information of each destination subnet to the header of the multicast packet when receiving the multicast packet of the target multicast group;
  • the transmitter is configured to forward the multicast message to which the TE bit string and the identification information of each destination subnet are added.
  • a device connected to a core network in a destination subnet corresponding to a target multicast group includes a processor, a memory, a receiver, and a transmitter, where:
  • the processor is configured to: when the receiver receives the multicast packet of the target multicast group that is added to the outer layer, remove the outer layer encapsulation to obtain the multicast packet; The stored bit string of the destination subnet is added to the header of the multicast packet;
  • the transmitter is configured to forward a multicast packet to which a bit string of the destination subnet is added.
  • bit string is a TE bit string
  • receiver is further configured to:
  • the processor is configured to:
  • a fourteenth aspect of the embodiments of the present disclosure there is provided a computer readable storage medium comprising instructions for when the computer readable storage medium is run on a device connected to a core network in a source subnet corresponding to a target multicast group Having the apparatus perform the method described in the first aspect above.
  • a computer program product comprising instructions, when the computer program product is run on a device connected to a core network in a source subnet corresponding to a target multicast group, The apparatus performs the method of the first aspect described above.
  • a computer readable storage medium comprising instructions, when the computer readable storage medium is run on a controller, causing the controller to perform the second aspect described above method.
  • a computer program product comprising instructions, when the computer program product is run on a controller, causing the controller to perform the method of the second aspect described above.
  • a computer readable storage medium comprising instructions for causing the BFIR to perform the method of the third aspect described above when the computer readable storage medium is run on a BFIR.
  • a computer program product comprising instructions for causing the BFIR to perform the method of the third aspect described above when the computer program product is run on a BFIR.
  • a computer readable storage medium comprising instructions for when the computer readable storage medium is run on a device connected to a core network in a destination subnet corresponding to a target multicast group Having the apparatus perform the method described in the fourth aspect above.
  • a computer program product comprising instructions, when the computer program product runs on a device connected to a core network in a destination subnet corresponding to a target multicast group, The apparatus is caused to perform the method described in the fourth aspect above.
  • the device connected to the core network in the source subnet receives the multicast packet of the target multicast group
  • the device connected to the core network in the plurality of destination subnets corresponding to the target multicast group is determined.
  • the address is used to replicate the multicast packets to obtain multiple multicast packets with the same number of destination subnets.
  • the outer packet is added to each multicast packet. Forwarding, where the destination address in the outer package is the address of the device connected to the core network in each destination subnet.
  • the device connected to the core network in the source subnet receives the multicast packet, it copies the multicast packet according to the number of the destination subnet to which the multicast packet is sent, and avoids the multicast packet.
  • it first entered the data transmission network it was copied by BFIR. Thereby, the number of multicast messages in the data transmission network can be greatly reduced, and the occupation of network resources is reduced.
  • FIG. 1 is a schematic structural diagram of a device connected to a core network in a source subnet according to an exemplary embodiment
  • FIG. 1-b is a schematic structural diagram of a controller according to an exemplary embodiment
  • FIG. 1-c is a schematic structural diagram of a BFIR according to an exemplary embodiment
  • FIG. 1 is a schematic structural diagram of a device connected to a core network in a destination subnet according to an exemplary embodiment
  • FIG. 2 is a schematic flowchart of a method for transmitting a multicast packet according to an exemplary embodiment
  • FIG. 2 is a schematic flowchart of a method for transmitting a multicast packet according to an exemplary embodiment
  • FIG. 3 is a schematic diagram showing attribute information of video data recorded by a BFIR to all BFER broadcasts according to an exemplary embodiment
  • FIG. 4 is a schematic flowchart of a method for transmitting a multicast packet according to an exemplary embodiment
  • FIG. 4 is a schematic flowchart of a method for transmitting a multicast packet according to an exemplary embodiment
  • FIG. 5 is a schematic diagram of a port of a device in a source subnet according to an exemplary embodiment
  • FIG. 6 is a schematic structural diagram of an apparatus connected to a core network in a source subnet according to an exemplary embodiment
  • FIG. 7 is a schematic structural diagram of a controller according to an exemplary embodiment
  • FIG. 8 is a schematic structural diagram of a BFIR according to an exemplary embodiment
  • FIG. 9 is a schematic structural diagram of an apparatus connected to a core network in a destination subnet according to an exemplary embodiment.
  • the embodiment of the present invention provides a method for transmitting a multicast packet, where the method may be corresponding to a device, a controller, a BFIR, and the target multicast group connected to the core network in a source subnet corresponding to the target multicast group.
  • the devices connected to the core network in the destination subnet are implemented together.
  • the device connected to the core network in the source subnet corresponding to the target multicast group may include the processor 110, the transmitter 120, and the receiver 130.
  • the receiver 130 and the transmitter 120 may be respectively connected to the processor 110, as shown in FIG. 1-a. Shown.
  • the receiver 130 can be used to receive messages or data
  • the transmitter 120 and the receiver 130 can be network cards
  • the transmitter 120 can be used to send messages or data, that is, the outer-packaged multicast packets can be forwarded.
  • the device connected to the core network in the source subnet may further include an acceleration component (which may be referred to as an accelerator), and when the acceleration component is a network acceleration component, the acceleration component may be a network card.
  • an acceleration component which may be referred to as an accelerator
  • the processor 110 may be a control center of a device connected to the core network in the source subnet, and connects various parts of the entire source server, such as the receiver 130 and the transmitter 120, using various interfaces and lines.
  • the processor 110 may be a CPU (Central Processing Unit), and may be used to determine an address of a device connected to the core network among multiple destination subnets corresponding to the target multicast group, optionally,
  • the processor 110 may include one or more processing units; the processor 110 may integrate an application processor and a modem processor, wherein the application processor primarily processes an operating system, and the modem processor primarily processes wireless communications.
  • Processor 110 can also be a digital signal processor, an application specific integrated circuit, a field programmable gate array, or other programmable logic device or the like.
  • the device connected to the core network in the source subnet may further include a memory 140, the memory 140 may be used to store a software program and a module, and the processor 110 executes the source subnet and the core network by reading the software code and the module stored in the memory.
  • Various functional applications and data processing of connected devices may further include a memory 140, the memory 140 may be used to store a software program and a module, and the processor 110 executes the source subnet and the core network by reading the software code and the module stored in the memory.
  • the controller can include a processor 210, a transmitter 220, a receiver 230, and a receiver 230 and a transmitter 220 can be coupled to the processor 210, respectively, as shown in Figure 1-b.
  • the receiver 230 can be used to receive messages or data
  • the transmitter 220 and the receiver 230 can be network cards
  • the transmitter 220 can be used to send messages or data, that is, TE (Traffic Engineering) can be used for each destination subnet.
  • the bit string is sent to the device connected to the core network in the corresponding destination subnet or the device connected to the core network in the source subnet corresponding to the target multicast group.
  • the controller may also include an acceleration component (which may be referred to as an accelerator), and when the acceleration component is a network acceleration component, the acceleration component may be a network card.
  • the processor 210 can be the control center of the controller, connecting various parts of the entire source server, such as the receiver 230 and the transmitter 220, using various interfaces and lines.
  • the processor 210 may be a CPU, and may be configured to respectively determine a destination subnet to which the plurality of bit forwarding egress routers BFER corresponding to the target multicast group belong, according to devices connected to the core network in each destination subnet.
  • the identifier information and the identification information of the BFER in each destination subnet respectively determine a TE bit string of each destination subnet.
  • the processor 210 may include one or more processing units; the processor 210 may integrate the application.
  • a processor and a modem processor wherein the application processor primarily processes an operating system, and the modem processor primarily processes wireless communications.
  • Processor 210 can also be a digital signal processor, an application specific integrated circuit, a field programmable gate array, or other programmable logic device or the like.
  • the controller may also include a memory 240 that may be used to store software programs and modules, and the processor 210 performs various functional applications and data processing of the controller by reading software code and modules stored in the memory.
  • the BFIR can include a processor 310, a transmitter 320, a receiver 330, and a receiver 330 and a transmitter 320 can be coupled to the processor 310, respectively, as shown in Figure 1-c.
  • the receiver 330 can be used to receive messages or data
  • the transmitter 320 and the receiver 330 can be network cards
  • the transmitter 320 can be used to send messages or data, that is, multicast packets can be added to the identification information of each destination subnet.
  • the text is forwarded.
  • the BFIR may also include an acceleration component (which may be referred to as an accelerator), and when the acceleration component is a network acceleration component, the acceleration component may be a network card.
  • the processor 310 can be a control center of the BFIR that connects various parts of the entire source server, such as the receiver 330 and the transmitter 320, using various interfaces and lines.
  • the processor 310 may be a CPU, and may be configured to add the identification information of each destination subnet to the header of the multicast packet when receiving the multicast packet of the target multicast group.
  • the processor 310 can include one or more processing units; the processor 310 can integrate an application processor and a modem processor, wherein the application processor primarily processes an operating system, and the modem processor primarily processes wireless communications.
  • Processor 310 can also be a digital signal processor, an application specific integrated circuit, a field programmable gate array, or other programmable logic device or the like.
  • the BFIR may also include a memory 340 that may be used to store software programs and modules, and the processor 310 performs various functional applications and data processing of the BFIR by reading software code and modules stored in the memory.
  • the device connected to the core network in the destination subnet corresponding to the target multicast group may include a processor 410, a transmitter 420, a receiver 430, and the receiver 430 and the transmitter 420 may be respectively connected to the processor 410, as shown in FIG. 1-d. Shown.
  • the receiver 430 can be used to receive messages or data
  • the transmitter 420 and the receiver 430 can be network cards
  • the transmitter 420 can be used to send messages or data, that is, the multicast message to which the bit string of the destination subnet is added can be performed.
  • the device connected to the core network in the destination subnet may further include an acceleration component (which may be referred to as an accelerator), and when the acceleration component is a network acceleration component, the acceleration component may be a network card.
  • an acceleration component which may be referred to as an accelerator
  • the processor 410 may be a control center of a device connected to the core network in the destination subnet, and connects various parts of the entire source server, such as the receiver 430 and the transmitter 420, using various interfaces and lines.
  • the processor 410 may be a CPU, and may be configured to remove the outer layer encapsulation to obtain a multicast packet when receiving the multicast packet of the target multicast group that is added to the outer layer encapsulation, optionally, the processor 410 may include one or more processing units; processor 410 may integrate an application processor and a modem processor, wherein the application processor primarily processes an operating system, and the modem processor primarily processes wireless communications.
  • Processor 410 can also be a digital signal processor, an application specific integrated circuit, a field programmable gate array, or other programmable logic device or the like.
  • the device connected to the core network in the destination subnet may further include a memory 440, the memory 440 may be used to store software programs and modules, and the processor 410 executes the destination subnet and the core network by reading software code and modules stored in the memory.
  • Various functional applications and data processing of connected devices may be a digital signal processor, an application specific integrated circuit, a field programmable gate array, or other programmable logic device or the like.
  • the device connected to the core network in the destination subnet may further include a memory 440, the memory 440 may be used to store software programs and modules, and the processor 410 executes the destination subnet and the core network by reading software code and modules stored in the memory.
  • Various functional applications and data processing of connected devices may be a digital signal processor, an application specific integrated circuit, a field programmable gate array, or other programmable logic device or
  • An exemplary embodiment of the present disclosure provides a method for transmitting a multicast packet. As shown in FIG. 2-a, the method can be applied to a device connected to a core network in a source subnet corresponding to a target multicast group, and the control is performed.
  • the device connected to the core network in the destination subnet corresponding to the BFIR and the target multicast group, the method may include:
  • Step S210 The controller respectively determines the destination subnet to which the multiple BFERs corresponding to the target multicast group belong, and the identifier information of the device connected to the core network in each destination subnet and the identifier of the BFER in each destination subnet. Information, respectively, determines the bit string for each destination subnet.
  • the bit string can be a TE bit string.
  • the identification information of the device connected to the core network in each destination subnet, the identification information of the port, and the identification information of the BFER in each destination subnet may be sequence number information. You can configure a unique serial number (just unique in a subnet) for the edge devices in the source subnet and the forwarding ports of the devices belonging to the source subnet. This sequence number plays an important role in the representation of the TE bit string.
  • the controller may determine the destination subnet to which the multiple BFERs corresponding to the target multicast group belong, and may identify the identification information of the device connected to the core network in each destination subnet, the identifier information of the port, and each The identification information of the BFER in the destination subnet determines the TE bit string of each destination subnet.
  • the media server Before the controller performs the above operations, first, if the media server is a server of a television station, when the television station records the program and broadcasts on the network, the media server can acquire the recorded video data. Then, the media server can send the attribute information of the recorded video data to the BFIR connected thereto. As shown in FIG. 3, the BFIR broadcasts attribute information of recorded video data to all BFERs. The user holding the terminal can choose whether to watch the recorded program, and if interested in the recorded program, can choose to watch the recorded program. The BFER connected to the terminal can feed back information of interest to the BFIR asking for it. It should be noted that, in the foregoing process, the BGP (Border Gateway Protocol) information can be exchanged between the BFIR and the BFER.
  • BGP Border Gateway Protocol
  • the BFIR can determine the relationship between the recorded video data (corresponding to a target multicast group) and the recipient, that is, the BFER.
  • a target multicast group can be interested in multiple receivers at the same time. Multiple receivers can be from different destination subnets, from the same destination subnet, or from the source subnet where BFIR resides.
  • the BFIR may send the identification information of the target multicast group and the identification information of the BFER in each destination subnet to the controller.
  • the BFIR may send a request for determining a TE bit string of each destination subnet to the controller, where the request carries the identification information of the target multicast group (the address of the multicast group) and the identifier of the BFER in each destination subnet. Information (serial number).
  • the controller can perform the operation of step S210.
  • the BFER may not feed back the information of interest to the BFIR, but directly feed back the information of interest to the controller.
  • the controller can also perform the operation of step S210.
  • the controller knows which BFER is interested in the target multicast group, and the controller may also pre-store the topology map of the entire network, including the source subnet, the core network, and the destination subnet. In this way, the controller can determine the destination subnet to which the multiple BFERs corresponding to the target multicast group belong.
  • Each destination subnet has at least one device connected to the core network, and the controller may pre-store the identification information of the device connected to the core network and the port in the destination subnet and the destination subnet. In this way, the controller can determine the identification information of the device connected to the core network in each destination subnet.
  • the TE bit string of each destination subnet is determined according to the identification information of the device connected to the core network, the identification information of the port, and the BFER identification information corresponding to the target multicast group in each destination subnet. That is, the controller knows the topology map of the entire network and the starting position and the target location of the target multicast group to be forwarded, and can determine the TE bit string of each destination subnet according to the TE or the differentiated service policy and the like.
  • the TE bit string can be used to indicate the specific path of multicast packet forwarding in the target multicast group. If there is no TE string, the multicast packets in the destination multicast group can only be forwarded according to the routing table maintained by the router.
  • the TE bit string may be the TE bit string in the draft of T. Eckert, and the draft number is "Draft-Eckert-Bier-TE-Arch-05".
  • the controller can also determine the bit string for each destination subnet, and the bit string can be the bit string proposed in the draft "Draft-IETF-Bier-Architecture-07".
  • the step S210 may include: the controller according to the identification information of the BFIR corresponding to the target multicast group, at least one of the source subnets and the core The identification information of the device connected to the network and the identification information of at least one BFER determine the TE bit string of the source subnet.
  • a target multicast group can be interested in multiple receivers at the same time. Multiple receivers can be from different destination subnets, from the same destination subnet, or belong to the source subnet where BFIR is located. If at least one BFER in the BFER corresponding to the target multicast group belongs to the source subnet, not only the TE bit string of each destination subnet but also the TE bit string of the source subnet is determined.
  • the controller can determine the TE bit string of each destination subnet required for forwarding the multicast packet of the target multicast group to the destination subnet, and at least one of the BFERs corresponding to the target multicast group exists.
  • the BFER belongs to the source subnet, it can also determine the TE bit string of the source subnet required for forwarding the multicast packets of the target multicast group in the source subnet.
  • the method provided by the embodiment of the present disclosure further includes: determining, by the controller, the source subnet according to the identifier information of the BFIR corresponding to the target multicast group and the identifier information of the device connected to the core network in at least one of the source subnets.
  • TE bit string sends the TE bit string of the source subnet to the BFIR.
  • the multicast packet in addition to forwarding the multicast packets through the TE bit string in the destination subnet, the multicast packet can also be forwarded through the TE bit string in the source subnet. It should be noted that there are many devices in the source subnet and the destination subnet, and the path is complex. You can calculate the forwarding path of multicast packets by using the TE policy that handles complex situations. In addition, the TE policy can also automatically identify the number of destination subnets to which multicast packets are sent. When the destination subnet is a subnet, it can be forwarded in unicast mode. If the number of the destination subnets is greater than or equal to 2, the multicast packets can be forwarded.
  • the multicast packets are copied only when the forked node is encountered.
  • the copied multicast packets are sent out through different egresses. In this way, the number of messages in the data transmission network can be greatly reduced.
  • the controller can also determine the TE bit string of the source subnet as in the manner of determining the TE bit string of each destination subnet, and details are not described herein again.
  • Step S220 The controller sends the bit string of each destination subnet to the device connected to the core network in the corresponding destination subnet.
  • the controller may send the TE bit string of each destination subnet to the device connected to the core network in the corresponding destination subnet or the device connected to the core network in the source subnet corresponding to the target multicast group. .
  • the device connected to the core network in the destination subnet or the device connected to the core network in the source subnet corresponding to the target multicast group can use the obtained TE bit string of the destination subnet.
  • the controller sends the TE bit string of each destination subnet to the devices P and Q connected to the core network in the corresponding destination subnet.
  • the controller sends the TE bit string of each destination subnet to the device O connected to the core network in the source subnet corresponding to the target multicast group.
  • the method provided by the embodiment of the present disclosure may further include: the controller sending the identification information of each destination subnet to the BFIR.
  • the identifier information of the destination subnet may be SI (Set Identification) information.
  • the controller can generate SI information, and the SI information can be a bit string corresponding to the sequence number of the destination subnet. Then, the SI information can be sent to the BFIR, so that the BFIR can add the SI information to the packet header of the multicast packet, so that the device connected to the core network in the source subnet that receives the multicast packet can be based on the SI information. Determine to copy several multicast packets to different destination subnets.
  • devices connected to the core network in the source subnet can determine how many multicast packets to be replicated in other ways, as described in detail later.
  • the method provided by the embodiment of the present disclosure further includes: the BFIR receiving the identification information of each destination subnet corresponding to the target multicast group sent by the controller.
  • the identification information of the destination subnet may be SI information.
  • the BFIR can add the SI information to the packet header of the multicast packet, and the device connected to the core network in the source subnet that receives the multicast packet can determine that multiple multicast packets are to be sent to the device according to the SI information. Different destination subnets.
  • the method provided by the embodiment of the present disclosure further includes: when the BFIR receives the multicast packet of the target multicast group, adding the identifier information of each destination subnet to the header of the multicast packet, and adopting the group The multicast mode forwards the multicast packets with the identification information of each destination subnet.
  • the BFIR may first store the identification information of each destination subnet.
  • the identification information of each destination subnet is added to the header of the multicast packet.
  • the header of the multicast packet is extended, and the identifier information of each destination subnet is added to the extended position in the header of the multicast packet. In this way, the identification information of the destination subnet has its own location in the header, and can carry more information.
  • Each data bit (bit) in the SI information can be set to represent the sequence number of a destination subnet. If the SI information is 8 bits, it can represent 8 destination subnets. When the SI information is "00001010", the destination subnet can be represented as the destination subnet 2 and the destination subnet 4. Because the destination data bit 2 and destination subnet 4 corresponding data bits are set.
  • the BFIR can forward the multicast packet with the identification information of each destination subnet in the multicast mode. Specifically, the BFIR can find the address of the next hop corresponding to the target multicast group in the routing table, and forward the multicast packet with the identification information of each destination subnet according to the found address.
  • the method provided by the embodiment of the present disclosure may further include: the BFIR receiving the TE bit string of the source subnet corresponding to the target multicast group sent by the controller.
  • the BFIR receives the multicast packet of the destination multicast group
  • the BFIR adds the identification information of each destination subnet to the header of the multicast packet, and adds the identification information of each destination subnet through the multicast mode.
  • the step of forwarding the multicast packet may include: adding the TE bit string and the identifier information of each destination subnet to the header of the multicast packet when the BFIR receives the multicast packet of the target multicast group, The multicast packet with the TE bit string and the identification information of each destination subnet is forwarded.
  • the multicast packet in addition to forwarding the multicast packet through the routing table, can also be forwarded according to the TE bit string.
  • the BFIR can receive the TE bit string of the source subnet corresponding to the target multicast group sent by the controller. Then, when the BFIR receives the multicast packet of the target multicast group, the BFIR can add the TE bit string and the identification information of each destination subnet to the header of the multicast packet, and add the TE bit string and each. The multicast packet of the destination subnet is forwarded.
  • the TE bit string and the identification information of each destination subnet may occupy 64, 128, 256, 512, 1024, 2048, and 4096 data bits in the header. It can be configured according to actual needs.
  • the TE bit string is 64.
  • the SI information needs to be expressed by 1024 (65535 divided by 64) data bits.
  • the TE bit strings are 128, 256, 512, 1024, 2048 data bits, respectively, the number of data bits occupied by the SI information is 512, 256, 128, 64, 32 bits.
  • the network shown in the figure is a source subnet.
  • a device in the source subnet that is connected to the core network has a port ING1, which is used to forward multicast packets from the source subnet to the core network.
  • Another device in the source subnet that is connected to the core network has a port EG1 that is used to forward multicast packets from the core network to the source subnet.
  • the numbers represent the port numbers of the different devices.
  • the port number of the device connected to the core network is forwarded through the ING1 port of the source network. 4 and 12 (only need to mark the port), the corresponding TE bit string is "100000001100". As can be seen from the form of the TE bit string, bits 3, 4, and 12 are set to indicate that multicast packets are to be forwarded to these ports for forwarding.
  • BFIR For BFIR, it has 2 port numbers 1 and 2, and port numbers 1 and 2 are 3 and 4.
  • the BFIR discovers that the multicast packet needs to be copied from the two ports connected to the next device to the next device. The first one exits from port 1 and enters port 3. The second branch exits from port 2 and enters port 4.
  • the fork node can always copy the multicast packet by n when it determines that the received multicast packet is to be sent to n different devices.
  • Step S230 When the device connected to the core network in the source subnet corresponding to the target multicast group receives the multicast packet of the target multicast group, determine that multiple destination subnets corresponding to the target multicast group are connected to the core network. The address of the device is copied to the multicast packet to obtain multiple multicast packets equal to the number of multiple destination subnets.
  • the multicast packet it is determined that the multicast packet needs to be sent to several different destination subnets. If it needs to be sent to m different destination subnets, the multicast packets are copied to m.
  • the specific information can be determined by using the SI information in the header of the multicast packet.
  • the step S230 may include: when the device connected to the core network in the source subnet receives the multicast packet of the target multicast group, the identifier information based on the preset destination subnet and the core in the destination subnet.
  • the address of the device connected to the network and the identification information of multiple destination subnets carried in the header of the multicast packet determine the address of the device connected to the core network in the corresponding multiple destination subnets.
  • the BFIR receives the identification information (SI information) of the destination subnet from the controller, and adds the SI information in the header of the multicast packet.
  • SI information the identification information
  • the device connected to the core network in the source subnet receives the multicast packet, it can read the SI information in the header of the multicast packet.
  • the device that is connected to the core network in the source subnet can pre-establish the correspondence between the identification information including the destination subnet and the address of the device connected to the core network in the destination subnet as shown in Table 1.
  • the step S230 may include: the device connected to the core network in the source subnet determines the group carried in the multicast packet based on the correspondence between the preset multicast address and the address of the device connected to the core network in the destination subnet. The address of the device connected to the core network among the plurality of destination subnets corresponding to the broadcast address.
  • the payload of the multicast packet carries a multicast address (for example, 192.168.1.1, 224.0.1.254), and may be based on the preset multicast address and the address of the device connected to the core network in the destination subnet. Corresponding relationship, determining the address of the device connected to the core network among the plurality of destination subnets corresponding to the multicast address carried in the multicast packet. Alternatively, the identifier information of the plurality of destination subnets corresponding to the multicast address carried in the multicast packet may be determined based on the correspondence between the preset multicast address and the identifier information of the destination subnet.
  • a multicast address for example, 192.168.1.1, 224.0.1.254
  • Determining according to a preset correspondence between the identifier information of the destination subnet and the address of the device connected to the core network in the destination subnet, respectively, connecting the plurality of destination subnets corresponding to the identification information of the plurality of destination subnets to the core network The address of the device.
  • Step S240 The device connected to the core network in the source subnet adds an outer encapsulation to each multicast packet, and forwards the multicast packet that is added to the outer layer.
  • the destination address in the outer package is the address of the device connected to the core network in each destination subnet.
  • the multicast packets can be forwarded through the TE policy in the destination subnet or the source subnet.
  • multicast packets can be forwarded in unicast mode. The specific reason is that the number of devices in the core network is small, the forwarding path is relatively simple, and the unicast can meet the forwarding requirements.
  • the multicast packet is sent to the device connected to the core network in the destination subnet in unicast mode.
  • the multicast packet can be unicast, such as GRE (Generic Routing Encapsulation, Encapsulation in the form of MPLS (Multi-Protocol Label Switching).
  • GRE Generic Routing Encapsulation, Encapsulation in the form of MPLS (Multi-Protocol Label Switching).
  • a device connected to the core network in the source subnet forwards the multicast packets that are added to the outer layer.
  • Step S250 When the device connected to the core network in the destination subnet corresponding to the target multicast group receives the multicast packet of the target multicast group that is added to the outer layer, the outer layer encapsulates the multicast packet.
  • the multicast message is unicast from the device O connected to the core network in the source subnet to the device connected to the core network in the destination subnet.
  • a device connected to the core network in the destination subnet can remove the outer layer encapsulation of multicast packets, that is, remove the GRE encapsulation or MPLS encapsulation.
  • Step S260 The device connected to the core network in the destination subnet adds the bit string of the destination subnet to the header of the multicast packet.
  • the device connected to the core network in the destination subnet can add a bit string of the destination subnet received from the controller to the header of the multicast packet.
  • the method provided by the embodiment of the present disclosure further includes: the device connected to the core network in the destination subnet receives the destination sent by the controller.
  • the TE bit string of the net is added to the header of the multicast packet.
  • Step S260 may include: the device connected to the core network in the destination subnet replaces the bit string of the source subnet corresponding to the target multicast group in the header of the multicast packet by using the bit string of the destination subnet.
  • the device connected to the core network in the destination subnet obtains the multicast address from the payload of the multicast packet.
  • the multicast group is determined to be the target multicast group, and then the correspondence between the pre-received multicast group and the destination sub-network bit string can be queried. As shown in Table 2, the bit string of the destination subnet corresponding to the target multicast group is determined. .
  • Step S270 The device connected to the core network in the destination subnet forwards the multicast packet with the bit string of the destination subnet.
  • the multicast packets are forwarded through the TE sub-string of the source subnet.
  • the multicast packets can be forwarded through the TE sub-string of the destination subnet.
  • multicast packets are forwarded to BFER 1 and BFER 2.
  • BFER 1 and BFER 2 the multicast message is forwarded to BFER 3 and BFER 4.
  • BFER 1, BFER 2, BFER 3, and BFER 4 respectively forward the multicast packet to the CE device until the CE device forwards the multicast packet to the terminal.
  • the device connected to the core network in the source subnet receives the multicast packet of the target multicast group
  • the device connected to the core network in the plurality of destination subnets corresponding to the target multicast group is determined.
  • the address is used to replicate the multicast packets to obtain multiple multicast packets with the same number of destination subnets.
  • the outer packet is added to each multicast packet. Forwarding, where the destination address in the outer package is the address of the device connected to the core network in each destination subnet.
  • the device connected to the core network in the source subnet receives the multicast packet, it copies the multicast packet according to the number of the destination subnet to which the multicast packet is sent, and avoids the multicast packet.
  • it first entered the data transmission network it was copied by BFIR. Thereby, the number of multicast messages in the data transmission network can be greatly reduced, and the occupation of network resources is reduced.
  • An exemplary embodiment of the present disclosure provides a method for transmitting a multicast packet. As shown in FIG. 2-b, the method can be applied to a device connected to a core network in a source subnet corresponding to a target multicast group, and the control is performed.
  • the device connected to the core network in the destination subnet corresponding to the BFIR and the target multicast group, the method may include:
  • Step S310 the controller respectively determines the destination subnet to which the multiple BFERs corresponding to the target multicast group belong, and the identifier information of the device connected to the core network in each destination subnet and the identifier of the BFER in each destination subnet. Information, respectively, determines the bit string for each destination subnet.
  • the bit string can be a TE bit string.
  • the identification information of the device connected to the core network in each destination subnet and the identification information of the BFER in each destination subnet may be sequence number information. You can configure a unique serial number (just unique in a subnet) for the edge devices in the source subnet and the forwarding ports of the devices belonging to the source subnet. This sequence number plays an important role in the representation of the TE bit string.
  • the step S210 may include: the controller according to the identification information of the BFIR corresponding to the target multicast group, at least one of the source subnets and the core The identification information of the device connected to the network and the identification information of at least one BFER determine the TE bit string of the source subnet.
  • the method provided by the embodiment of the present disclosure further includes: determining, by the controller, the source subnet according to the identifier information of the BFIR corresponding to the target multicast group and the identifier information of the device connected to the core network in at least one of the source subnets.
  • TE bit string sends the TE bit string of the source subnet to the BFIR.
  • Step S320 The controller sends the bit string of each destination subnet to the device connected to the core network in the source subnet corresponding to the target multicast group.
  • the method provided by the embodiment of the present disclosure may further include: the controller sending the identification information of each destination subnet to the BFIR.
  • the method provided by the embodiment of the present disclosure further includes: the BFIR receiving the identification information of each destination subnet corresponding to the target multicast group sent by the controller.
  • the method provided by the embodiment of the present disclosure further includes: when the BFIR receives the multicast packet of the target multicast group, adding the identifier information of each destination subnet to the header of the multicast packet, and adopting the group The multicast mode forwards the multicast packets with the identification information of each destination subnet.
  • the method provided by the embodiment of the present disclosure may further include: the BFIR receiving the TE bit string of the source subnet corresponding to the target multicast group sent by the controller.
  • the BFIR receives the multicast packet of the destination multicast group
  • the BFIR adds the identification information of each destination subnet to the header of the multicast packet, and adds the identification information of each destination subnet through the multicast mode.
  • the step of forwarding the multicast packet may include: adding the TE bit string and the identifier information of each destination subnet to the header of the multicast packet when the BFIR receives the multicast packet of the target multicast group, The multicast packet with the TE bit string and the identification information of each destination subnet is forwarded.
  • step S330 when the device connected to the core network in the source subnet corresponding to the target multicast group receives the multicast packet of the target multicast group, the device determines that the target multicast group is connected to the core network. The address of the device is copied to the multicast packet to obtain multiple multicast packets equal to the number of multiple destination subnets.
  • the step S330 may include: when the device connected to the core network in the source subnet receives the multicast packet of the target multicast group, the identifier information based on the preset destination subnet and the core in the destination subnet.
  • the address of the device connected to the network and the identification information of multiple destination subnets carried in the header of the multicast packet determine the address of the device connected to the core network in the corresponding multiple destination subnets.
  • the step S330 may include: determining, by the device in the source subnet, the device that is connected to the core network, the group that is carried in the multicast packet, based on the correspondence between the preset multicast address and the address of the device connected to the core network in the destination subnet. The address of the device connected to the core network among the plurality of destination subnets corresponding to the broadcast address.
  • Step S340 the device connected to the core network in the source subnet receives the bit string of each destination subnet sent by the controller.
  • Step S350 The device connected to the core network in the source subnet adds the bit string of each destination subnet to the header of each corresponding multicast packet, and obtains the multicast packet corresponding to each destination subnet.
  • the TE bit string of each destination subnet can also be added to the header of the multicast packet in the BFIR.
  • the step S350 may include: replacing the TE bit string of the source subnet in the header of each corresponding multicast packet with the TE bit string of the destination subnet, respectively, to obtain the multicast corresponding to each destination subnet. Message.
  • the header of the multicast packet carries the TE bit string of the active subnet, which is used to indicate how the multicast packet is forwarded in the source subnet.
  • the source subnet originally carried in the header of the multicast packet
  • the TE bit string has no effect. Therefore, as shown in FIG. 4-b, in the device connected to the core network in the source subnet, the TE bit string of each destination subnet received from the controller may be replaced by the corresponding multicast packet.
  • the TE bit string of the source subnet in the header obtains the multicast packet corresponding to each destination subnet.
  • the replacement operation is not performed in the device connected to the core network in the source subnet but in other devices. If the device connected to the core network in the source subnet only copies the multicast packets, and does not add the TE bit string of each destination subnet to the header of the multicast packet, you can configure the destination subnet with The device connected to the core network adds the TE bit string of each destination subnet to the header of the multicast packet.
  • Step S360 The device connected to the core network in the source subnet adds an outer encapsulation packet to the multicast packet corresponding to each destination subnet, and forwards the multicast packet that is added to the outer layer.
  • the destination address in the outer package is the address of the device connected to the core network in each destination subnet.
  • Step S370 When the device connected to the core network in the destination subnet corresponding to the target multicast group receives the multicast packet of the target multicast group in the outer layer encapsulation, the outer layer encapsulation obtains the multicast packet.
  • Step S380 The device connected to the core network in the destination subnet forwards the multicast packet with the bit string of the destination subnet.
  • the device connected to the core network in the source subnet receives the multicast packet of the target multicast group
  • the device connected to the core network in the plurality of destination subnets corresponding to the target multicast group is determined.
  • the address is used to replicate the multicast packets to obtain multiple multicast packets with the same number of destination subnets.
  • the outer packet is added to each multicast packet. Forwarding, where the destination address in the outer package is the address of the device connected to the core network in each destination subnet.
  • the device connected to the core network in the source subnet receives the multicast packet, it copies the multicast packet according to the number of the destination subnet to which the multicast packet is sent, and avoids the multicast packet.
  • it first entered the data transmission network it was copied by BFIR. Thereby, the number of multicast messages in the data transmission network can be greatly reduced, and the occupation of network resources is reduced.
  • An exemplary embodiment of the present disclosure provides a device connected to a core network in a source subnet corresponding to a target multicast group. As shown in FIG. 6, the device includes:
  • the determining module 610 is configured to: when receiving the multicast packet of the target multicast group, determine an address of a device connected to the core network among the plurality of destination subnets corresponding to the target multicast group, and the multicast packet The file is copied to obtain a plurality of multicast packets equal to the number of the plurality of destination subnets. Specifically, the determining function in the foregoing step S230 or step S330, and other implicit steps may be implemented.
  • the adding module 620 is configured to add an outer encapsulation to each multicast packet, where the destination address in the outer encapsulation is the address of the device connected to the core network in each destination subnet. Specifically, the added function in the above step S240 or step S360, and other implicit steps can be implemented.
  • the forwarding module 630 is configured to forward the multicast packet that is added to the outer layer. Specifically, the forwarding function in step S240 or step S360 described above, and other implicit steps may be implemented.
  • the determining module 610 is configured to:
  • the mapping between the identifier information of the destination subnet and the address of the device connected to the core network in the destination subnet, and the header of the multicast packet Identification information of multiple destination subnets carried in the network, and determining an address of a device connected to the core network among the corresponding multiple destination subnets.
  • the determining module 610 is configured to:
  • the device further includes:
  • a receiving module configured to receive a TE bit string of each destination subnet sent by the controller
  • the adding module is further configured to add the TE bit string of each destination subnet to the header of the corresponding multicast packet to obtain a multicast packet corresponding to each destination subnet.
  • the adding module 620 is configured to:
  • the TE bit string of the source subnet in the header of the corresponding multicast packet is replaced by the TE bit string of the destination subnet, and the multicast packet corresponding to each destination subnet is obtained.
  • the foregoing determining module 610, the adding module 620, and the forwarding module 630 may be implemented by a processor, or the processor may be implemented by using a memory, or the processor may execute the program instructions in the memory.
  • An exemplary embodiment of the present disclosure provides a controller. As shown in FIG. 7, the controller includes:
  • the determining module 710 is configured to respectively determine a destination subnet to which the multiple BFERs corresponding to the target multicast group belong, according to the identification information of the device connected to the core network in each destination subnet, and the BFER in each destination subnet.
  • the identification information is respectively determined by the TE bit string of each destination subnet; specifically, the determining function in the above step S210 or step S310, and other implicit steps may be implemented.
  • the sending module 720 is configured to send the TE bit string of each destination subnet to the device connected to the core network in the corresponding destination subnet or the source subnet corresponding to the target multicast group to be connected to the core network. device. Specifically, the sending function in the above step S220 or step S320, and other implicit steps can be implemented.
  • the determining module 710 is further configured to determine the source according to the identifier information of the BFIR corresponding to the target multicast group and the identifier information of at least one device connected to the core network in the source subnet.
  • the sending module 720 is further configured to send a TE bit string of the source subnet to the BFIR.
  • the determining module 710 is configured to:
  • the sending module 720 is further configured to:
  • the identification information of each destination subnet is sent to the BFIR.
  • determining module 710 and the sending module 720 may be implemented by a processor, or the processor may be implemented by using a memory, or the processor may execute the program instructions in the memory.
  • the BFIR includes:
  • the receiving module 810 is configured to receive the identifier information of each destination subnet corresponding to the target multicast group sent by the controller. Specifically, the receiving function in the foregoing method embodiment, and other implicit steps may be implemented.
  • the forwarding module 820 is configured to: when receiving the multicast packet of the target multicast group, add the identifier information of each destination subnet to the header of the multicast packet, and add the multicast mode.
  • the multicast packet of the identification information of each destination subnet is forwarded.
  • the forwarding function in the foregoing method embodiments, and other implicit steps may be implemented.
  • the receiving module 810 is further configured to receive a TE bit string of a source subnet corresponding to the target multicast group sent by the controller;
  • the forwarding module 820 is configured to add the TE bit string and the identifier information of each destination subnet to the header of the multicast packet when receiving the multicast packet of the target multicast group.
  • the multicast packet with the TE bit string and the identification information of each destination subnet is forwarded.
  • receiving module 810 and the forwarding module 820 may be implemented by a processor, or the processor may be implemented by using a memory, or the processor may execute the program instructions in the memory.
  • An exemplary embodiment of the present disclosure provides a device connected to a core network in a destination subnet corresponding to a target multicast group. As shown in FIG. 9, the device includes:
  • the receiving module 911 is configured to receive the multicast packet of the target multicast group that is added to the outer layer; specifically, the receiving function in the foregoing step S250 or step S370, and other implicit steps may be implemented.
  • the removing module 910 is configured to: when receiving the multicast packet of the target multicast group that is added to the outer layer, remove the outer layer to obtain the multicast packet; specifically, the foregoing step S250 or step S370 is implemented.
  • the removal function as well as other implied steps.
  • the adding module 920 is configured to add a bit string of the destination subnet to the header of the multicast packet. Specifically, the adding function in the foregoing step S260 and other implicit steps may be implemented.
  • the forwarding module 930 is configured to forward the multicast packet to which the bit string of the destination subnet is added. Specifically, the forwarding function in the above step S270 or step S380, and other implicit steps can be implemented.
  • bit string is a TE bit string
  • receiving module 911 is further configured to:
  • the adding module 920 is configured to:
  • receiving module 911, the removing module 910, the adding module 920, and the forwarding module 930 may be implemented by a processor, or the processor may be implemented by using a memory, or the processor may execute a program instruction in the memory.
  • the device connected to the core network in the source subnet receives the multicast packet
  • the device replicates the multicast packet according to the number of the destination subnet to which the multicast packet is to be sent.
  • Multicast packets are copied by BFIR when they first enter the data transmission network. Thereby, the number of multicast messages in the data transmission network can be greatly reduced, and the occupation of network resources is reduced.
  • the device provided by the foregoing embodiment transmits the multicast packet
  • only the division of each functional module is used as an example.
  • the function distribution may be completed by different functional modules according to requirements.
  • the internal structure of each device is divided into different functional modules to complete all or part of the functions described above.
  • the device provided by the foregoing embodiment is the same as the method for transmitting the multicast packet. The specific implementation process is described in the method embodiment, and details are not described herein again.
  • An exemplary embodiment of the present disclosure provides a system for transmitting a multicast packet, where the system includes a device and a BFIR connected to a core network in a source subnet corresponding to a target multicast group;
  • the BFIR is configured to forward the multicast packet by using a multicast mode when receiving the multicast packet of the target multicast group;
  • the device connected to the core network in the source subnet is configured to: when receiving the multicast packet, determine an address of a device connected to the core network among multiple destination subnets corresponding to the target multicast group, Copying the multicast packet to obtain multiple multicast packets equal to the number of the plurality of destination subnets; adding outer layer encapsulation to each multicast packet, and adding the outer layer encapsulated multicast
  • the packet is forwarded, where the destination address in the outer package is the address of the device connected to the core network in each destination subnet.
  • the system further includes a controller
  • the controller is configured to send identification information of each destination subnet corresponding to the target multicast group to the BFIR;
  • the BFIR is further configured to add the identifier information of each destination subnet to a header of the multicast packet.
  • the device connected to the core network in the source subnet is configured to: when receiving the multicast packet, based on the identifier information of the preset destination subnet and the address of the device connected to the core network in the destination subnet. Corresponding relationship, and identifier information of multiple destination subnets carried in the header of the multicast packet, determining an address of a device connected to the core network in the corresponding multiple destination subnets.
  • system further includes: a device connected to the core network in the destination subnet corresponding to the target multicast group;
  • the controller is further configured to respectively determine a destination subnet to which the multiple BFERs corresponding to the target multicast group belong, according to identification information of devices connected to the core network in each destination subnet, and each destination subnet.
  • the identification information of the BFER in the medium determines the bit string of each destination subnet; respectively, sends the bit string of each destination subnet to the device connected to the core network in the corresponding destination subnet;
  • the device connected to the core network in the destination subnet is configured to: when receiving the multicast packet that is added to the outer layer, remove the outer layer encapsulation to obtain the multicast packet; The bit string is added to the header of the multicast packet, and the multicast packet to which the bit string of the destination subnet is added is forwarded.
  • the controller is further configured to determine the source according to the identifier information of the BFIR corresponding to the target multicast group and the identifier information of at least one device connected to the core network in the source subnet. a bit string of the network; transmitting a bit string of the source subnet to the BFIR;
  • the BFIR is further configured to receive a bit string of the source subnet sent by the controller; when receiving the multicast packet, the bit string of the source subnet and each destination subnet The identifier information is added to the header of the multicast packet, and the multicast packet to which the bit string of the source subnet and the identification information of each destination subnet are added is forwarded.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本公开是关于一种传输组播报文的方法、设备和系统,属于电子技术领域。该方法包括:当源子网中与核心网连接的设备接收到目标组播组的组播报文时,确定目标组播组对应的多个目的子网中与核心网连接的设备的地址,对组播报文进行复制,得到与多个目的子网数量相等的多个组播报文;分别对每个组播报文添加外层封装,对添加外层封装的组播报文进行转发,其中,外层封装中的目的地址为每个目的子网中与核心网连接的设备的地址。采用本公开,可以大大减少数据传输网络中的组播报文的数量,并且减少网络资源的占用。

Description

传输组播报文的方法、设备和系统
本申请要求于2018年3月30日提交中国专利局、申请号为201810277203.3、申请名称为“传输组播报文的方法、设备和系统”的中国专利申请的优先权,其全部内容通过引用结合在本申请中。
技术领域
本申请涉及电子技术领域,尤其涉及一种传输组播报文的方法、设备和系统。
背景技术
随着网络技术的发展,网络的功能也越来越强大,用户可以在网络上观看各种视频直播。由于这种视频直播一般是由多个用户同时收看的,即从媒体服务器发送出来的直播数据要被多个用户接收,直播数据可以以组播报文的形式传输给多个终端。
数据传输网络可以包括核心网和子网,多个子网通过核心网相互通信。一般,和生成组播报文的源设备(一般为媒体服务器)连接的路由设备称作源CE(Customer Edge,用户网络边缘设备),和接收组播报文的目的设备(一般为终端)连接的路由设备称作目的CE。在数据传输网络中,连接源CE的设备可以称作BFIR(Bit Forwarding Ingress Router,位转发入口路由器),连接目的CE的设备可以称作BFER(Bit Forwarding Egress Router,位转发出口路由器)。BFIR所属的子网称作源子网,BFER所属的子网称作目的子网。
在上述传输过程中,当BFIR接收到组播报文时,确定组播报文要发送至不同的目的子网的数量N。在BFIR中将组播报文进行复制,得到N份组播报文,分别用于发送至N个不同的目的子网。在每个目的子网内部,将组播报文转发至相应的BFER,再由BFER根据组播报文中的组播地址,将其转发至目的CE。
在实现本公开的过程中,发明人发现至少存在以下问题:
由于通过网络传输信息的应用越来越广泛,需要传输的组播报文的数量也越来越多,如果每个组播报文都被复制N份进行传输,占用的网络资源巨大。
发明内容
为了克服相关技术中存在的问题,本公开提供了以下技术方案:
根据本公开实施例的第一方面,提供一种传输组播报文的方法,所述方法应用于目标组播组对应的源子网中与核心网连接的设备,所述方法包括:
当接收到目标组播组的组播报文时,确定所述目标组播组对应的多个目的子网中与核心网连接的设备的地址,对所述组播报文进行复制,得到与所述多个目的子网数量相等的多个组播报文;
分别对每个组播报文添加外层封装,对添加外层封装的组播报文进行转发,其中,外层封装中的目的地址分别为每个目的子网中与核心网连接的设备的地址。
在源子网中与核心网连接的设备接收到组播报文时,根据组播报文要发往的目的子网的数量对组播报文进行复制,避免了在组播报文一开始进入数据传输网络时就被BFIR复制多份。从而,可以大大减少数据传输网络中的组播报文的数量,并且减少网络资源的占用。
在一种可能的实现方式中,所述当接收到目标组播组的组播报文时,确定所述目标组播组对应的多个目的子网中与核心网连接的设备的地址,包括:
当接收到目标组播组的组播报文时,基于预设的目的子网的标识信息和目的子网中与核心网连接的设备的地址的对应关系,以及所述组播报文的报头中携带的多个目的子网的标识信息,确定对应的多个目的子网中与核心网连接的设备的地址。
BFIR从控制器接收来目的子网的标识信息(SI信息),将SI信息添加在组播报文的报头中。当源子网中与核心网连接的设备接收到组播报文时,可以读取组播报文的报头中的SI信息。
在一种可能的实现方式中,所述当接收到目标组播组的组播报文时,确定所述目标组播组对应的多个目的子网中与核心网连接的设备的地址,包括:
基于预设的组播地址和目的子网中与核心网连接的设备的地址的对应关系,确定所述组播报文中携带的组播地址对应的多个目的子网中与核心网连接的设备的地址。
组播报文的净荷中携带有组播地址例如(192.168.1.1,224.0.1.254),可以基于预设的组播地址和目的子网中与核心网连接的设备的地址的对应关系,确定组播报文中携带的组播地址对应的多个目的子网中与核心网连接的设备的地址。
在一种可能的实现方式中,在分别对每个组播报文添加外层封装之前,所述方法还包括:
接收控制器发送的每个目的子网的流量工程TE位串;
分别将每个目的子网的TE位串,添加到对应的组播报文的报头中,得到每个目的子网对应的组播报文。
也可以在BFIR中就将每个目的子网的TE位串添加到组播报文的报头中。
在一种可能的实现方式中,所述分别将每个目的子网的TE位串,添加到对应的组播报文的报头中,得到每个目的子网对应的组播报文,包括:
分别用所述目的子网的TE位串,替换对应的组播报文的报头中的所述源子网的TE位串,得到每个目的子网对应的组播报文。
组播报文的报头中可以携带有源子网的TE位串,用于指示组播报文在源子网中如何进行转发。然而,当组播报文到达源子网中与核心网连接的设备,并且将要从源子网中与核心网连接的设备进入核心网时,组播报文的报头中原来携带的源子网的TE位串就没有作用了。因此,在源子网中与核心网连接的设备中,可以分别用从控制器接收来的每个目的子网的TE位串,替换对应的组播报文的报头中的源子网的TE位串,得到每个目的子网对应的组播报文。
根据本公开实施例的第二方面,提供一种传输组播报文的方法,所述方法应用于控制器,所述方法包括:
分别确定目标组播组对应的多个位转发出口路由器BFER所属的目的子网,根据每 个目的子网中与核心网连接的设备的标识信息、以及每个目的子网中的BFER的标识信息,分别确定每个目的子网的TE位串;
将每个目的子网的TE位串分别发送至对应的目的子网中与核心网连接的设备、或所述目标组播组对应的源子网中与核心网连接的设备。
在一种可能的实现方式中,所述方法还包括:
根据所述目标组播组对应的位转发入口路由器BFIR的标识信息、以及所述源子网中至少一个与核心网连接的设备的标识信息,确定所述源子网的TE位串;
将所述源子网的TE位串发送至所述BFIR。
在一种可能的实现方式中,如果所述目标组播组对应的BFER中存在至少一个BFER属于所述源子网,则所述根据所述目标组播组对应的BFIR的标识信息、以及所述源子网中至少一个与核心网连接的设备的标识信息,确定所述源子网的TE位串,包括:
根据所述目标组播组对应的BFIR的标识信息、所述源子网中至少一个与核心网连接的设备的标识信息、以及所述至少一个BFER的标识信息,确定所述源子网的TE位串。
在一种可能的实现方式中,所述方法还包括:
将每个目的子网的标识信息发送至所述BFIR。
根据本公开实施例的第三方面,提供一种传输组播报文的方法,所述方法应用于BFIR,所述方法包括:
接收控制器发送的目标组播组对应的每个目的子网的标识信息;
当接收到所述目标组播组的组播报文时,将每个目的子网的标识信息添加到所述组播报文的报头中,通过组播方式,对添加了每个目的子网的标识信息的组播报文进行转发。
在一种可能的实现方式中,所述方法还包括:
接收所述控制器发送的所述目标组播组对应的源子网的TE位串;
所述当接收到所述目标组播组的组播报文时,将每个目的子网的标识信息添加到所述组播报文的报头中,通过组播方式,对添加了每个目的子网的标识信息的组播报文进行转发,包括:
当接收到所述目标组播组的组播报文时,将所述TE位串和每个目的子网的标识信息添加到所述组播报文的报头中,将添加了所述TE位串和每个目的子网的标识信息的组播报文进行转发。
根据本公开实施例的第四方面,提供一种传输组播报文的方法,所述方法应用于目标组播组对应的目的子网中与核心网连接的设备,所述方法包括:
当接收到添加外层封装的所述目标组播组的组播报文时,去除所述外层封装得到所述组播报文;
将所述目的子网的位串添加到所述组播报文的报头中;
对添加了所述目的子网的位串的组播报文进行转发。
在一种可能的实现方式中,所述位串为TE位串,在将所述目的子网的位串添加到 所述组播报文的报头中之前,所述方法还包括:
接收控制器发送的所述目的子网的TE位串。
在一种可能的实现方式中,所述将所述目的子网的位串添加到所述组播报文的报头中,包括:
用所述目的子网的位串,替换所述组播报文的报头中的所述目标组播组对应的源子网的位串。
根据本公开实施例的第五方面,提供一种目标组播组对应的源子网中与核心网连接的设备,该设备包括至少一个模块,该至少一个模块用于实现上述第一方面所提供的传输组播报文的方法。
根据本公开实施例的第六方面,提供一种控制器,该控制器包括至少一个模块,该至少一个模块用于实现上述第二方面所提供的传输组播报文的方法。
根据本公开实施例的第七方面,提供一种BFIR,该BFIR包括至少一个模块,该至少一个模块用于实现上述第三方面所提供的传输组播报文的方法。
根据本公开实施例的第八方面,提供一种目标组播组对应的目的子网中与核心网连接的设备,该设备包括至少一个模块,该至少一个模块用于实现上述第四方面所提供的传输组播报文的方法。
根据本公开实施例的第九方面,提供一种传输组播报文的系统,所述系统包括目标组播组对应的源子网中与核心网连接的设备和BFIR;
所述BFIR,用于当接收到所述目标组播组的组播报文时,通过组播方式,对所述组播报文进行转发;
所述源子网中与核心网连接的设备,用于当接收到所述组播报文时,确定所述目标组播组对应的多个目的子网中与核心网连接的设备的地址,对所述组播报文进行复制,得到与所述多个目的子网数量相等的多个组播报文;分别对每个组播报文添加外层封装,对添加外层封装的组播报文进行转发,其中,外层封装中的目的地址分别为每个目的子网中与核心网连接的设备的地址。
在一种可能的实现方式中,所述系统还包括控制器;
所述控制器,用于将所述目标组播组对应的每个目的子网的标识信息发送至所述BFIR;
所述BFIR,还用于将所述每个目的子网的标识信息添加到所述组播报文的报头中;
所述源子网中与核心网连接的设备,用于当接收到所述组播报文时,基于预设的目的子网的标识信息和目的子网中与核心网连接的设备的地址的对应关系,以及所述组播报文的报头中携带的多个目的子网的标识信息,确定对应的多个目的子网中与核心网连接的设备的地址。
在一种可能的实现方式中,所述系统还包括目标组播组对应的目的子网中与核心 网连接的设备;
所述控制器,还用于分别确定所述目标组播组对应的多个BFER所属的目的子网,根据每个目的子网中与核心网连接的设备的标识信息、以及每个目的子网中的BFER的标识信息,分别确定每个目的子网的位串;将每个目的子网的位串分别发送至对应的目的子网中与核心网连接的设备;
所述目的子网中与核心网连接的设备,用于当接收到添加外层封装的组播报文时,去除所述外层封装得到所述组播报文;将所述目的子网的位串添加到所述组播报文的报头中;对添加了所述目的子网的位串的组播报文进行转发。
在一种可能的实现方式中,所述控制器,还用于根据所述目标组播组对应的BFIR的标识信息、以及所述源子网中至少一个与核心网连接的设备的标识信息,确定所述源子网的位串;将所述源子网的位串发送至所述BFIR;
所述BFIR,还用于接收所述控制器发送的所述源子网的位串;当接收到所述组播报文时,将所述源子网的位串和每个目的子网的标识信息添加到所述组播报文的报头中,将添加了所述源子网的位串和每个目的子网的标识信息的组播报文进行转发。
根据本公开实施例的第十方面,提供了一种目标组播组对应的源子网中与核心网连接的设备,所述设备包括处理器、存储器、接收器和发射器,其中:
所述处理器,用于当所述接收器接收到目标组播组的组播报文时,确定所述目标组播组对应的多个目的子网中与核心网连接的设备的地址,对所述组播报文进行复制,得到与所述多个目的子网数量相等的多个组播报文;分别对每个组播报文添加外层封装;
所述发射器,用于对添加外层封装的组播报文进行转发,其中,外层封装中的目的地址分别为所述存储器中存储的每个目的子网中与核心网连接的设备的地址。
在一种可能的实现方式中,所述处理器用于:
当所述接收器接收到目标组播组的组播报文时,基于预设的目的子网的标识信息和目的子网中与核心网连接的设备的地址的对应关系,以及所述组播报文的报头中携带的多个目的子网的标识信息,确定对应的多个目的子网中与核心网连接的设备的地址。
在一种可能的实现方式中,所述处理器用于:
基于所述存储器中存储的预设的组播地址和目的子网中与核心网连接的设备的地址的对应关系,确定所述组播报文中携带的组播地址对应的多个目的子网中与核心网连接的设备的地址。
在一种可能的实现方式中,所述接收器,还用于接收控制器发送的每个目的子网的TE位串;
所述处理器,还用于分别将每个目的子网的TE位串,添加到对应的组播报文的报头中,得到每个目的子网对应的组播报文。
在一种可能的实现方式中,所述处理器用于:
分别用所述目的子网的TE位串,替换对应的组播报文的报头中的所述源子网的TE位串,得到每个目的子网对应的组播报文。
根据本公开实施例的第十一方面,提供一种控制器,所述控制器包括处理器和发射器,其中:
所述处理器,用于分别确定目标组播组对应的多个BFER所属的目的子网,根据每个目的子网中与核心网连接的设备的标识信息、以及每个目的子网中的BFER的标识信息,分别确定每个目的子网的TE位串;
所述发射器,用于将每个目的子网的TE位串分别发送至对应的目的子网中与核心网连接的设备、或所述目标组播组对应的源子网中与核心网连接的设备。
在一种可能的实现方式中,所述处理器,还用于根据所述目标组播组对应的BFIR的标识信息、以及所述源子网中至少一个与核心网连接的设备的标识信息,确定所述源子网的TE位串;
所述发射器,还用于将所述源子网的TE位串发送至所述BFIR。
在一种可能的实现方式中,当所述目标组播组对应的BFER中存在至少一个BFER属于所述源子网时,所述处理器用于:
根据所述目标组播组对应的BFIR的标识信息、所述源子网中至少一个与核心网连接的设备的标识信息、以及所述至少一个BFER的标识信息,确定所述源子网的TE位串。
在一种可能的实现方式中,所述发射器还用于:
将每个目的子网的标识信息发送至所述BFIR。
根据本公开实施例的第十二方面,提供一种BFIR,所述BFIR包括处理器、存储器、接收器和发射器,其中:
所述接收器,用于接收控制器发送的目标组播组对应的每个目的子网的标识信息;
所述处理器,用于将所述接收器接收的每个目的子网的标识信息存储到所述存储器中,并当所述接收器接收到所述目标组播组的组播报文时,将所述存储器存储的每个目的子网的标识信息添加到所述组播报文的报头中;
所述发射器,用于通过组播方式,对添加了每个目的子网的标识信息的组播报文进行转发。
在一种可能的实现方式中,所述接收器,还用于接收所述控制器发送的所述目标组播组对应的源子网的TE位串;
所述处理器,用于当接收到所述目标组播组的组播报文时,将所述TE位串和每个目的子网的标识信息添加到所述组播报文的报头中;
所述发射器,用于将添加了所述TE位串和每个目的子网的标识信息的组播报文进行转发。
根据本公开实施例的第十三方面,提供一种目标组播组对应的目的子网中与核心网连接的设备,所述设备包括处理器、存储器、接收器和发射器,其中:
所述处理器,用于当所述接收器接收到添加外层封装的所述目标组播组的组播报文时,去除所述外层封装得到所述组播报文;将所述存储器存储的所述目的子网的位 串添加到所述组播报文的报头中;
所述发射器,用于对添加了所述目的子网的位串的组播报文进行转发。
在一种可能的实现方式中,所述位串为TE位串,所述接收器还用于:
接收控制器发送的所述目的子网的TE位串。
在一种可能的实现方式中,所述处理器用于:
用所述目的子网的位串,替换所述组播报文的报头中的所述目标组播组对应的源子网的位串。
根据本公开实施例的第十四方面,提供了计算机可读存储介质,包括指令,当所述计算机可读存储介质在目标组播组对应的源子网中与核心网连接的设备上运行时,使得所述设备执行上述第一方面所述的方法。
根据本公开实施例的第十五方面,提供了一种包含指令的计算机程序产品,当所述计算机程序产品在目标组播组对应的源子网中与核心网连接的设备上运行时,使得所述设备执行上述第一方面所述的方法。
根据本公开实施例的第十六方面,提供了计算机可读存储介质,包括指令,当所述计算机可读存储介质在控制器上运行时,使得所述控制器执行上述第二方面所述的方法。
根据本公开实施例的第十七方面,提供了一种包含指令的计算机程序产品,当所述计算机程序产品在控制器上运行时,使得所述控制器执行上述第二方面所述的方法。
根据本公开实施例的第十八方面,提供了计算机可读存储介质,包括指令,当所述计算机可读存储介质在BFIR上运行时,使得所述BFIR执行上述第三方面所述的方法。
根据本公开实施例的第十九方面,提供了一种包含指令的计算机程序产品,当所述计算机程序产品在BFIR上运行时,使得所述BFIR执行上述第三方面所述的方法。
根据本公开实施例的第二十方面,提供了计算机可读存储介质,包括指令,当所述计算机可读存储介质在目标组播组对应的目的子网中与核心网连接的设备上运行时,使得所述设备执行上述第四方面所述的方法。
根据本公开实施例的第二十一方面,提供了一种包含指令的计算机程序产品,当所述计算机程序产品在目标组播组对应的目的子网中与核心网连接的设备上运行时,使得所述设备执行上述第四方面所述的方法。
本公开的实施例提供的技术方案可以包括以下有益效果:
本公开实施例中,当源子网中与核心网连接的设备接收到目标组播组的组播报文 时,确定目标组播组对应的多个目的子网中与核心网连接的设备的地址,对组播报文进行复制,得到与多个目的子网数量相等的多个组播报文;分别对每个组播报文添加外层封装,对添加外层封装的组播报文进行转发,其中,外层封装中的目的地址为每个目的子网中与核心网连接的设备的地址。这样,在源子网中与核心网连接的设备接收到组播报文时,根据组播报文要发往的目的子网的数量对组播报文进行复制,避免了在组播报文一开始进入数据传输网络时就被BFIR复制多份。从而,可以大大减少数据传输网络中的组播报文的数量,并且减少网络资源的占用。
应当理解的是,以上的一般描述和后文的细节描述仅是示例性和解释性的,并不能限制本公开。
附图说明
此处的附图被并入说明书中并构成本说明书的一部分,示出了符合本公开的实施例,并与说明书一起用于解释本公开的原理。在附图中:
图1-a是根据一示例性实施例示出的一种源子网中与核心网连接的设备的结构示意图;
图1-b是根据一示例性实施例示出的一种控制器的结构示意图;
图1-c是根据一示例性实施例示出的一种BFIR的结构示意图;
图1-d是根据一示例性实施例示出的一种目的子网中与核心网连接的设备的结构示意图;
图2-a是根据一示例性实施例示出的一种传输组播报文的方法的流程示意图;
图2-b是根据一示例性实施例示出的一种传输组播报文的方法的流程示意图;
图3是根据一示例性实施例示出的一种BFIR向所有的BFER广播录制的视频数据的属性信息的示意图;
图4-a是根据一示例性实施例示出的一种传输组播报文的方法的流程示意图;
图4-b是根据一示例性实施例示出的一种传输组播报文的方法的流程示意图;
图5是根据一示例性实施例示出的一种源子网中的设备的端口示意图;
图6是根据一示例性实施例示出的一种源子网中与核心网连接的设备的结构示意图;
图7是根据一示例性实施例示出的一种控制器的结构示意图;
图8是根据一示例性实施例示出的一种BFIR的结构示意图;
图9是根据一示例性实施例示出的一种目的子网中与核心网连接的设备的结构示意图。
通过上述附图,已示出本公开明确的实施例,后文中将有更详细的描述。这些附图和文字描述并不是为了通过任何方式限制本公开构思的范围,而是通过参考特定实施例为本领域技术人员说明本公开的概念。
具体实施方式
这里将详细地对示例性实施例进行说明,其示例表示在附图中。下面的描述涉及附图时,除非另有表示,不同附图中的相同数字表示相同或相似的要素。以下示例性 实施例中所描述的实施方式并不代表与本公开相一致的所有实施方式。相反,它们仅是与如所附权利要求书中所详述的、本公开的一些方面相一致的装置和方法的例子。
本发明实施例提供了一种传输组播报文的方法,该方法可以由目标组播组对应的源子网中与核心网连接的设备、控制器、BFIR以及所述目标组播组对应的目的子网中与核心网连接的设备共同实现。
目标组播组对应的源子网中与核心网连接的设备可以包括处理器110、发射器120、接收器130,接收器130和发射器120可以分别与处理器110连接,如图1-a所示。接收器130可以用于接收消息或数据,发射器120和接收器130可以是网卡,发射器120可以用于发送消息或数据,即可以对添加外层封装的组播报文进行转发。源子网中与核心网连接的设备还可以包括加速部件(可称为加速器),当加速部件为网络加速部件时,加速部件可以为网卡。处理器110可以是源子网中与核心网连接的设备的控制中心,利用各种接口和线路连接整个源服务器的各个部分,如接收器130和发射器120等。在本发明中,处理器110可以是CPU(Central Processing Unit,中央处理器),可以用于确定目标组播组对应的多个目的子网中与核心网连接的设备的地址,可选的,处理器110可以包括一个或多个处理单元;处理器110可集成应用处理器和调制解调处理器,其中,应用处理器主要处理操作系统,调制解调处理器主要处理无线通信。处理器110还可以是数字信号处理器、专用集成电路、现场可编程门阵列或者其他可编程逻辑器件等。源子网中与核心网连接的设备还可以包括存储器140,存储器140可用于存储软件程序以及模块,处理器110通过读取存储在存储器的软件代码以及模块,从而执行源子网中与核心网连接的设备的各种功能应用以及数据处理。
控制器可以包括处理器210、发射器220、接收器230,接收器230和发射器220可以分别与处理器210连接,如图1-b所示。接收器230可以用于接收消息或数据,发射器220和接收器230可以是网卡,发射器220可以用于发送消息或数据,即可以将每个目的子网的TE(Traffic Engineering,流量工程)位串分别发送至对应的目的子网中与核心网连接的设备、或目标组播组对应的源子网中与核心网连接的设备。控制器还可以包括加速部件(可称为加速器),当加速部件为网络加速部件时,加速部件可以为网卡。处理器210可以是控制器的控制中心,利用各种接口和线路连接整个源服务器的各个部分,如接收器230和发射器220等。在本发明中,处理器210可以是CPU,可以用于分别确定目标组播组对应的多个位转发出口路由器BFER所属的目的子网,根据每个目的子网中与核心网连接的设备的标识信息、以及每个目的子网中的BFER的标识信息,分别确定每个目的子网的TE位串,可选的,处理器210可以包括一个或多个处理单元;处理器210可集成应用处理器和调制解调处理器,其中,应用处理器主要处理操作系统,调制解调处理器主要处理无线通信。处理器210还可以是数字信号处理器、专用集成电路、现场可编程门阵列或者其他可编程逻辑器件等。控制器还可以包括存储器240,存储器240可用于存储软件程序以及模块,处理器210通过读取存储在存储器的软件代码以及模块,从而执行控制器的各种功能应用以及数据处理。
BFIR可以包括处理器310、发射器320、接收器330,接收器330和发射器320 可以分别与处理器310连接,如图1-c所示。接收器330可以用于接收消息或数据,发射器320和接收器330可以是网卡,发射器320可以用于发送消息或数据,即可以对添加了每个目的子网的标识信息的组播报文进行转发。BFIR还可以包括加速部件(可称为加速器),当加速部件为网络加速部件时,加速部件可以为网卡。处理器310可以是BFIR的控制中心,利用各种接口和线路连接整个源服务器的各个部分,如接收器330和发射器320等。在本发明中,处理器310可以是CPU,可以用于当接收到目标组播组的组播报文时,将每个目的子网的标识信息添加到组播报文的报头中,可选的,处理器310可以包括一个或多个处理单元;处理器310可集成应用处理器和调制解调处理器,其中,应用处理器主要处理操作系统,调制解调处理器主要处理无线通信。处理器310还可以是数字信号处理器、专用集成电路、现场可编程门阵列或者其他可编程逻辑器件等。BFIR还可以包括存储器340,存储器340可用于存储软件程序以及模块,处理器310通过读取存储在存储器的软件代码以及模块,从而执行BFIR的各种功能应用以及数据处理。
目标组播组对应的目的子网中与核心网连接的设备可以包括处理器410、发射器420、接收器430,接收器430和发射器420可以分别与处理器410连接,如图1-d所示。接收器430可以用于接收消息或数据,发射器420和接收器430可以是网卡,发射器420可以用于发送消息或数据,即可以对添加了目的子网的位串的组播报文进行转发。目的子网中与核心网连接的设备还可以包括加速部件(可称为加速器),当加速部件为网络加速部件时,加速部件可以为网卡。处理器410可以是目的子网中与核心网连接的设备的控制中心,利用各种接口和线路连接整个源服务器的各个部分,如接收器430和发射器420等。在本发明中,处理器410可以是CPU,可以用于当接收到添加外层封装的目标组播组的组播报文时,去除外层封装得到组播报文,可选的,处理器410可以包括一个或多个处理单元;处理器410可集成应用处理器和调制解调处理器,其中,应用处理器主要处理操作系统,调制解调处理器主要处理无线通信。处理器410还可以是数字信号处理器、专用集成电路、现场可编程门阵列或者其他可编程逻辑器件等。目的子网中与核心网连接的设备还可以包括存储器440,存储器440可用于存储软件程序以及模块,处理器410通过读取存储在存储器的软件代码以及模块,从而执行目的子网中与核心网连接的设备的各种功能应用以及数据处理。
本公开一示例性实施例提供了一种传输组播报文的方法,如图2-a所示,该方法可以应用于目标组播组对应的源子网中与核心网连接的设备、控制器、BFIR和目标组播组对应的目的子网中与核心网连接的设备,该方法可以包括:
步骤S210,控制器分别确定目标组播组对应的多个BFER所属的目的子网,根据每个目的子网中与核心网连接的设备的标识信息、以及每个目的子网中的BFER的标识信息,分别确定每个目的子网的位串。
其中,位串可以是TE位串。每个目的子网中与核心网连接的设备的标识信息、端口的标识信息、每个目的子网中的BFER的标识信息可以是序号信息。可以给源子网中的边缘设备以及属于源子网的设备的转发端口配置一个唯一的序号(只是在一个子网中唯一)。该序号在TE位串的表示方式中起到很重要的作用。
在实施中,控制器可以分别确定目标组播组对应的多个BFER所属的目的子网,并且可以根据每个目的子网中与核心网连接的设备的标识信息、端口的标识信息、以及每个目的子网中的BFER的标识信息,分别确定每个目的子网的TE位串。
在控制器执行上述操作之前,首先,假如媒体服务器是某电视台的服务器,当电视台录制了节目并在网络进行直播时,媒体服务器可以获取录制的视频数据。接着,媒体服务器可以将该录制的视频数据的属性信息发送给与之相连的BFIR。如图3所示,BFIR向所有的BFER广播录制的视频数据的属性信息。持有终端的用户可以选择是否收看录制的节目,如果对录制的节目感兴趣,可以选择收看录制的节目。与终端连接的BFER可以向询问它的BFIR反馈感兴趣的信息。需要说明的是,在上述过程中,BFIR和BFER之间可以通过BGP(Border Gateway Protocol,边界网关协议)信息进行交互。进而,BFIR可以确定录制的视频数据(对应一个目标组播组)和接收者即BFER之间的关系。一个目标组播组可以同时被多个接收者感兴趣,多个接收者可以来自不同的目的子网,也可以来自同一目的子网,还可以属于BFIR所在的源子网。每当达到预设的周期时,BFIR可以将目标组播组的标识信息和每个目的子网中的BFER的标识信息发送给控制器。或者,BFIR可以向控制器发送确定每个目的子网的TE位串的请求,请求中携带有目标组播组的标识信息(组播组的地址)和每个目的子网中的BFER的标识信息(序号)。这样,控制器就可以执行步骤S210的操作了。
除了上述方式之外,BFER可以不将感兴趣的信息反馈给BFIR,而是直接将感兴趣的信息反馈给控制器。这样,控制器也可以执行步骤S210的操作了。
控制器知道哪个BFER对目标组播组感兴趣,控制器中还可以预先存储有整个网络的拓扑图,包括源子网、核心网和目的子网。这样,控制器可以确定目标组播组对应的多个BFER所属的目的子网。每个目的子网中有至少一个与核心网连接的设备,控制器可以预先存储目的子网和目的子网中与核心网连接的设备以及端口的标识信息。这样,控制器可以确定每个目的子网中与核心网连接的设备的标识信息。根据每个目的子网中与核心网连接的设备的标识信息、端口的标识信息、以及目标组播组对应的BFER的标识信息,分别确定每个目的子网的TE位串。即控制器知道整个网络的拓扑图、以及目标组播组被转发的起始位置和目标位置,就可以根据TE或差异化服务策略等策略分别确定每个目的子网的TE位串。
TE位串可以用于指示目标组播组中的组播报文转发的具体路径。如果没有TE位串,目标组播组中的组播报文只能按照路由器底层维护的路由表按部就班地被转发了。TE位串可以是T.Eckert(瑅.埃克特)的草案中的TE位串,草案的编号为“Draft-Eckert-Bier-TE-Arch-05”。除了TE位串之外,控制器还可以分别确定每个目的子网的位串,位串可以是编号为“Draft-IETF-Bier-Architecture-07”草案中提出的位串。
可选地,如果目标组播组对应的BFER中存在至少一个BFER属于源子网,则步骤S210可以包括:控制器根据目标组播组对应的BFIR的标识信息、源子网中至少一个与核心网连接的设备的标识信息、以及至少一个BFER的标识信息,确定源子网的TE位串。
在实施中,一个目标组播组可以同时被多个接收者感兴趣,多个接收者可以来自 不同的目的子网,也可以来自同一目的子网,还可以属于BFIR所在的源子网。如果目标组播组对应的BFER中存在至少一个BFER属于源子网,则不仅要确定每个目的子网的TE位串,还要确定源子网的TE位串。
通过上述方式,控制器可以确定目标组播组的组播报文到达目的子网时,进行转发所需的每个目的子网的TE位串,当目标组播组对应的BFER中存在至少一个BFER属于源子网时,还可以确定目标组播组的组播报文在源子网中,进行转发所需的源子网的TE位串。
可选地,本公开实施例提供的方法还包括:控制器根据目标组播组对应的BFIR的标识信息、以及源子网中至少一个与核心网连接的设备的标识信息,确定源子网的TE位串;将源子网的TE位串发送至BFIR。
在实施中,除了在目的子网中通过TE位串进行组播报文的转发之外,还可以在源子网中也通过TE位串进行组播报文的转发。需要说明的是,源子网和目的子网中的设备较多,路径较为复杂,此时可以通过擅长处理复杂情况的TE策略来计算组播报文的转发路径。除此以外,通过TE策略,还可以自动识别组播报文发往的目的子网的数量。当目的子网是一个子网时,可以采用单播的方式进行转发。当目的子网的数量大于等于2个时,可以采用组播的方式进行转发,即只在传输组播报文的过程中,遇到分叉节点时,才对组播报文进行复制,将复制得到的组播报文分别通过不同的出口发送出去。这样,可以大大减少数据传输网络中的报文的数量。
如同确定每个目的子网的TE位串的方式,控制器还可以确定源子网的TE位串,在此不再赘述。
步骤S220,控制器将每个目的子网的位串分别发送至对应的目的子网中与核心网连接的设备。
在实施中,控制器可以将每个目的子网的TE位串分别发送至对应的目的子网中与核心网连接的设备、或目标组播组对应的源子网中与核心网连接的设备。这样,目的子网中与核心网连接的设备、或目标组播组对应的源子网中与核心网连接的设备就可以使用获得的目的子网的TE位串了。如图4-a所示,控制器将每个目的子网的TE位串分别发送至对应的目的子网中与核心网连接的设备P和Q。如图4-b所示,控制器将每个目的子网的TE位串分别发送至目标组播组对应的源子网中与核心网连接的设备O。
可选地,本公开实施例提供的方法还可以包括:控制器将每个目的子网的标识信息发送至BFIR。
在实施中,目的子网的标识信息可以是SI(Set Identification,子集身份标识)信息。控制器可以生成SI信息,SI信息可以是位串,对应于目的子网的序号。接着,可以将SI信息发送给BFIR,这样,BFIR可以将SI信息添加在组播报文的包头中,让后面接收到组播报文的源子网中与核心网连接的设备可以根据SI信息,确定要复制几份组播报文发往不同的目的子网。除了这种方式之外,源子网中与核心网连接的设备还可以通过其他方式确定要复制几份组播报文,在后面会详细介绍。
可选地,本公开实施例提供的方法还包括:BFIR接收控制器发送的目标组播组对应的每个目的子网的标识信息。
在实施中,目的子网的标识信息可以是SI信息。BFIR可以将SI信息添加在组播报文的包头中,让后面接收到组播报文的源子网中与核心网连接的设备可以根据SI信息,确定要复制几份组播报文发往不同的目的子网。
可选地,本公开实施例提供的方法还包括:当BFIR接收到目标组播组的组播报文时,将每个目的子网的标识信息添加到组播报文的报头中,通过组播方式,对添加了每个目的子网的标识信息的组播报文进行转发。
在实施中,BFIR可以先将每个目的子网的标识信息存储好,待目标组播组的组播报文到达时,将每个目的子网的标识信息添加到组播报文的报头中。可选地,可以将组播报文的报头进行扩展,将每个目的子网的标识信息添加到组播报文的报头中的扩展位置上。这样,目的子网的标识信息在报头中有了自己的位置,可以携带更多的信息。
可以设置SI信息中的每一个数据位(bit)代表一个目的子网的序号。假如SI信息是8位,则可以代表8个目的子网。当SI信息为“00001010”时,可以表示目的子网为目的子网2和目的子网4。因为目的子网2和目的子网4对应数据位被置1了。
接着,BFIR可以通过组播方式,对添加了每个目的子网的标识信息的组播报文进行转发。具体地,BFIR可以在路由表中查找目标组播组对应的下一跳的地址,根据查找到的地址对添加了每个目的子网的标识信息的组播报文进行转发。
可选地,本公开实施例提供的方法还可以包括:BFIR接收控制器发送的目标组播组对应的源子网的TE位串。当BFIR接收到目标组播组的组播报文时,将每个目的子网的标识信息添加到组播报文的报头中,通过组播方式,对添加了每个目的子网的标识信息的组播报文进行转发的步骤可以包括:当BFIR接收到目标组播组的组播报文时,将TE位串和每个目的子网的标识信息添加到组播报文的报头中,将添加了TE位串和每个目的子网的标识信息的组播报文进行转发。
在实施中,除了通过路由表转发组播报文的方式之外,还可以根据TE位串转发组播报文。首先,BFIR可以接收控制器发送的目标组播组对应的源子网的TE位串。接着,当BFIR接收到目标组播组的组播报文时,可以将TE位串和每个目的子网的标识信息添加到组播报文的报头中,将添加了TE位串和每个目的子网的标识信息的组播报文进行转发。
可选地,TE位串和每个目的子网的标识信息共可以占报头中64、128、256、512、1024、2048、4096个数据位(bit)。可以根据实际需求进行配置。
在实施中,由于一个管理域(包含源子网和所有目的子网)可支持的端口序号的上限为65535(协议规定),因此如果每个子网分配了64个端口序号即TE位串为64个数据位,则SI信息需要由1024(65535除以64)个数据位来表达。以此类推,如果TE位串分别为128、256、512、1024、2048个数据位,相应地,SI信息所占的数据位的数量为512、256、128、64、32位。
如图5所示,该图显示的网络是源子网,在该网络中,有1个BFIR,1个BFER,1个中间转发设备,2个源子网中与核心网连接的设备。其中,1个源子网中与核心网连接的设备中存在一个端口ING1,用于将源子网的组播报文转发到核心网中。另外1个源子网中与核心网连接的设备中存在一个端口EG1,用于从核心网中的组播报文转 发到源子网中。在图5中,数字代表不同设备的端口号。如果要将组播报文从BFIR转发到BFER和源子网中与核心网连接的设备,从源子网中与核心网连接的设备的ING1端口转发出去,所需经过的端口号为3、4和12(只需要标记入端口即可),对应的TE位串为“100000001100”。从TE位串的形式上可以看出,第3、4和第12位被置1了,代表组播报文要进入这些端口进行转发。
对于BFIR,它有2个端口号分别为1和2,1和2连接的端口号为3和4。当组播报文传输到BFIR时,BFIR发现该组播报文需要从和自己连接的2个端口进入下一个设备,则将组播报文复制2份。第1份从1端口出,进入端口3。第2份从2端口出,进入端口4。以此类推,分叉节点总能在确定要将接收到的组播报文发送n个不同的设备时,对组播报文进行复制n份。
步骤S230,当目标组播组对应的源子网中与核心网连接的设备接收到目标组播组的组播报文时,确定目标组播组对应的多个目的子网中与核心网连接的设备的地址,对组播报文进行复制,得到与多个目的子网数量相等的多个组播报文。
在实施中,可以确定组播报文需要发往几个不同的目的子网,假如需要发往m个不同的目的子网,则将组播报文复制m份。具体可以通过组播报文的报头中的SI信息确定。
可选地,步骤S230可以包括:当源子网中与核心网连接的设备接收到目标组播组的组播报文时,基于预设的目的子网的标识信息和目的子网中与核心网连接的设备的地址的对应关系,以及组播报文的报头中携带的多个目的子网的标识信息,确定对应的多个目的子网中与核心网连接的设备的地址。
在实施中,BFIR从控制器接收来目的子网的标识信息(SI信息),将SI信息添加在组播报文的报头中。当源子网中与核心网连接的设备接收到组播报文时,可以读取组播报文的报头中的SI信息。在源子网中与核心网连接的设备可以预先建立包含目的子网的标识信息和目的子网中与核心网连接的设备的地址的对应关系如表1所示。
表1
Figure PCTCN2018124157-appb-000001
可选地,步骤S230可以包括:源子网中与核心网连接的设备基于预设的组播地址和目的子网中与核心网连接的设备的地址的对应关系,确定组播报文中携带的组播地址对应的多个目的子网中与核心网连接的设备的地址。
在实施中,组播报文的净荷中携带有组播地址例如(192.168.1.1,224.0.1.254),可以基于预设的组播地址和目的子网中与核心网连接的设备的地址的对应关系,确定组播报文中携带的组播地址对应的多个目的子网中与核心网连接的设备的地址。或者,也可以基于预设的组播地址和目的子网的标识信息的对应关系,确定组播报文中携带的组播地址对应的多个目的子网的标识信息。基于预设的目的子网的标识信息和目的 子网中与核心网连接的设备的地址的对应关系,分别确定多个目的子网的标识信息对应的多个目的子网中与核心网连接的设备的地址。
步骤S240,源子网中与核心网连接的设备分别对每个组播报文添加外层封装,对添加外层封装的组播报文进行转发。
其中,外层封装中的目的地址分别为每个目的子网中与核心网连接的设备的地址
在实施中,在目的子网中或者源子网中,可以通过TE策略对组播报文进行转发。在核心网中,可以通过单播的方式对组播报文进行转发。具体原因是,核心网的设备数量较少,转发路径较为简单,单播就可以满足转发需求。
这样,组播报文此时在源子网中与核心网连接的设备中,将要通过单播的方式发往目的子网中与核心网连接的设备。在确定了目的子网中与核心网连接的设备的地址例如IP(Internet Protocol,网络之间互连的协议)地址之后,可以将组播报文以单播的形式如GRE(Generic Routing Encapsulation,通用路由封装)或者MPLS(Multi-Protocol Label Switching,多协议标签交换)的形式进行封装。源子网中与核心网连接的设备对添加外层封装的组播报文进行转发。
步骤S250,当目标组播组对应的目的子网中与核心网连接的设备接收到添加外层封装的目标组播组的组播报文时,去除外层封装得到组播报文。
在实施中,通过单播的方式将组播报文从源子网中与核心网连接的设备O单播到目的子网中与核心网连接的设备。目的子网中与核心网连接的设备可以将组播报文的外层封装去除,即去除掉GRE封装或者MPLS封装。
步骤S260,目的子网中与核心网连接的设备将目的子网的位串添加到组播报文的报头中。
在实施中,如图4-a所示,目的子网中与核心网连接的设备可以将从控制器接收来的目的子网的位串添加到组播报文的报头中。
可选地,在将目的子网的位串添加到组播报文的报头中之前,本公开实施例提供的方法还包括:目的子网中与核心网连接的设备接收控制器发送的目的子网的TE位串。
步骤S260可以包括:目的子网中与核心网连接的设备用目的子网的位串,替换组播报文的报头中的目标组播组对应的源子网的位串。
在实施中,当组播报文到达时,目的子网中与核心网连接的设备从组播报文的净荷中获取组播地址。通过组播地址确定是目标组播组,然后可以查询预先接收的组播组与目的子网的位串的对应关系如表2所示,确定与目标组播组对应的目的子网的位串。
表2
Figure PCTCN2018124157-appb-000002
步骤S270,目的子网中与核心网连接的设备对添加了目的子网的位串的组播报文进行转发。
在实施中,如同在源子网中通过源子网的TE位串进行组播报文的转发一样,依然可以在目的子网中,通过目的子网的TE位串进行组播报文的转发。如图4-a所示,在目的子网A中,将组播报文转发至BFER 1和BFER 2。在目的子网B中,将组播报文转发至BFER 3和BFER 4。然后,BFER 1、BFER 2、BFER 3和BFER 4分别将组播报文转发至CE设备,直至CE设备将组播报文转发至终端。
本公开实施例中,当源子网中与核心网连接的设备接收到目标组播组的组播报文时,确定目标组播组对应的多个目的子网中与核心网连接的设备的地址,对组播报文进行复制,得到与多个目的子网数量相等的多个组播报文;分别对每个组播报文添加外层封装,对添加外层封装的组播报文进行转发,其中,外层封装中的目的地址为每个目的子网中与核心网连接的设备的地址。这样,在源子网中与核心网连接的设备接收到组播报文时,根据组播报文要发往的目的子网的数量对组播报文进行复制,避免了在组播报文一开始进入数据传输网络时就被BFIR复制多份。从而,可以大大减少数据传输网络中的组播报文的数量,并且减少网络资源的占用。
本公开一示例性实施例提供了一种传输组播报文的方法,如图2-b所示,该方法可以应用于目标组播组对应的源子网中与核心网连接的设备、控制器、BFIR和目标组播组对应的目的子网中与核心网连接的设备,该方法可以包括:
步骤S310,控制器分别确定目标组播组对应的多个BFER所属的目的子网,根据每个目的子网中与核心网连接的设备的标识信息、以及每个目的子网中的BFER的标识信息,分别确定每个目的子网的位串。
其中,位串可以是TE位串。每个目的子网中与核心网连接的设备的标识信息、每个目的子网中的BFER的标识信息可以是序号信息。可以给源子网中的边缘设备以及属于源子网的设备的转发端口配置一个唯一的序号(只是在一个子网中唯一)。该序号在TE位串的表示方式中起到很重要的作用。
可选地,如果目标组播组对应的BFER中存在至少一个BFER属于源子网,则步骤S210可以包括:控制器根据目标组播组对应的BFIR的标识信息、源子网中至少一个与核心网连接的设备的标识信息、以及至少一个BFER的标识信息,确定源子网的TE位串。
可选地,本公开实施例提供的方法还包括:控制器根据目标组播组对应的BFIR的标识信息、以及源子网中至少一个与核心网连接的设备的标识信息,确定源子网的TE位串;将源子网的TE位串发送至BFIR。
步骤S320,控制器将每个目的子网的位串分别发送至目标组播组对应的源子网中与核心网连接的设备。
可选地,本公开实施例提供的方法还可以包括:控制器将每个目的子网的标识信息发送至BFIR。
可选地,本公开实施例提供的方法还包括:BFIR接收控制器发送的目标组播组对应的每个目的子网的标识信息。
可选地,本公开实施例提供的方法还包括:当BFIR接收到目标组播组的组播报文时,将每个目的子网的标识信息添加到组播报文的报头中,通过组播方式,对添加了 每个目的子网的标识信息的组播报文进行转发。
可选地,本公开实施例提供的方法还可以包括:BFIR接收控制器发送的目标组播组对应的源子网的TE位串。当BFIR接收到目标组播组的组播报文时,将每个目的子网的标识信息添加到组播报文的报头中,通过组播方式,对添加了每个目的子网的标识信息的组播报文进行转发的步骤可以包括:当BFIR接收到目标组播组的组播报文时,将TE位串和每个目的子网的标识信息添加到组播报文的报头中,将添加了TE位串和每个目的子网的标识信息的组播报文进行转发。
步骤S330,当目标组播组对应的源子网中与核心网连接的设备接收到目标组播组的组播报文时,确定目标组播组对应的多个目的子网中与核心网连接的设备的地址,对组播报文进行复制,得到与多个目的子网数量相等的多个组播报文。
可选地,步骤S330可以包括:当源子网中与核心网连接的设备接收到目标组播组的组播报文时,基于预设的目的子网的标识信息和目的子网中与核心网连接的设备的地址的对应关系,以及组播报文的报头中携带的多个目的子网的标识信息,确定对应的多个目的子网中与核心网连接的设备的地址。
可选地,步骤S330可以包括:源子网中与核心网连接的设备基于预设的组播地址和目的子网中与核心网连接的设备的地址的对应关系,确定组播报文中携带的组播地址对应的多个目的子网中与核心网连接的设备的地址。
步骤S340,源子网中与核心网连接的设备接收控制器发送的每个目的子网的位串。
步骤S350,源子网中与核心网连接的设备分别将每个目的子网的位串,添加到每个对应的组播报文的报头中,得到每个目的子网对应的组播报文。
在实施中,也可以在BFIR中就将每个目的子网的TE位串添加到组播报文的报头中。
可选地,步骤S350可以包括:分别用目的子网的TE位串,替换每个对应的组播报文的报头中的源子网的TE位串,得到每个目的子网对应的组播报文。
在实施中,组播报文的报头中可以携带有源子网的TE位串,用于指示组播报文在源子网中如何进行转发。然而,当组播报文到达源子网中与核心网连接的设备,并且将要从源子网中与核心网连接的设备进入核心网时,组播报文的报头中原来携带的源子网的TE位串就没有作用了。因此,如图4-b所示,在源子网中与核心网连接的设备中,可以分别用从控制器接收来的每个目的子网的TE位串,替换对应的组播报文的报头中的源子网的TE位串,得到每个目的子网对应的组播报文。
当然,替换操作不在源子网中与核心网连接的设备中进行而是在其他设备中进行也可以。假如在源子网中与核心网连接的设备中只是将组播报文进行复制,没有将每个目的子网的TE位串添加到组播报文的报头中,可以让目的子网中与核心网连接的设备将每个目的子网的TE位串添加到组播报文的报头中。
步骤S360,源子网中与核心网连接的设备分别对每个目的子网对应的组播报文添加外层封装,对添加外层封装的组播报文进行转发。
其中,外层封装中的目的地址分别为每个目的子网中与核心网连接的设备的地址。
步骤S370,当目标组播组对应的目的子网中与核心网连接的设备接收到添加外层封装的目标组播组的组播报文时,去除外层封装得到组播报文。
步骤S380,目的子网中与核心网连接的设备对添加了目的子网的位串的组播报文进行转发。
本公开实施例中,当源子网中与核心网连接的设备接收到目标组播组的组播报文时,确定目标组播组对应的多个目的子网中与核心网连接的设备的地址,对组播报文进行复制,得到与多个目的子网数量相等的多个组播报文;分别对每个组播报文添加外层封装,对添加外层封装的组播报文进行转发,其中,外层封装中的目的地址为每个目的子网中与核心网连接的设备的地址。这样,在源子网中与核心网连接的设备接收到组播报文时,根据组播报文要发往的目的子网的数量对组播报文进行复制,避免了在组播报文一开始进入数据传输网络时就被BFIR复制多份。从而,可以大大减少数据传输网络中的组播报文的数量,并且减少网络资源的占用。
本公开一示例性实施例提供了一种目标组播组对应的源子网中与核心网连接的设备,如图6所示,所述设备包括:
确定模块610,用于当接收到目标组播组的组播报文时,确定所述目标组播组对应的多个目的子网中与核心网连接的设备的地址,对所述组播报文进行复制,得到与所述多个目的子网数量相等的多个组播报文;具体可以实现上述步骤S230或者步骤S330中的确定功能,以及其他隐含步骤。
添加模块620,用于分别对每个组播报文添加外层封装,其中,外层封装中的目的地址分别为每个目的子网中与核心网连接的设备的地址。具体可以实现上述步骤S240或者步骤S360中的添加功能,以及其他隐含步骤。
转发模块630,用于对添加外层封装的组播报文进行转发。具体可以实现上述步骤S240或者步骤S360中的转发功能,以及其他隐含步骤。
可选地,所述确定模块610用于:
当接收到目标组播组的组播报文时,基于预设的目的子网的标识信息和目的子网中与核心网连接的设备的地址的对应关系,以及所述组播报文的报头中携带的多个目的子网的标识信息,确定对应的多个目的子网中与核心网连接的设备的地址。
可选地,所述确定模块610用于:
基于预设的组播地址和目的子网中与核心网连接的设备的地址的对应关系,确定所述组播报文中携带的组播地址对应的多个目的子网中与核心网连接的设备的地址。
可选地,所述设备还包括:
接收模块,用于接收控制器发送的每个目的子网的TE位串;
所述添加模块,还用于分别将每个目的子网的TE位串,添加到对应的组播报文的报头中,得到每个目的子网对应的组播报文。
可选地,所述添加模块620用于:
分别用所述目的子网的TE位串,替换对应的组播报文的报头中的所述源子网的TE位串,得到每个目的子网对应的组播报文。
需要说明的是,上述确定模块610、添加模块620和转发模块630可以由处理器实现,或者处理器配合存储器来实现,或者,处理器执行存储器中的程序指令来实现。
本公开一示例性实施例提供了一种控制器,如图7所示,所述控制器包括:
确定模块710,用于分别确定目标组播组对应的多个BFER所属的目的子网,根据每个目的子网中与核心网连接的设备的标识信息、以及每个目的子网中的BFER的标识信息,分别确定每个目的子网的TE位串;具体可以实现上述步骤S210或者步骤S310中的确定功能,以及其他隐含步骤。
发送模块720,用于将每个目的子网的TE位串分别发送至对应的目的子网中与核心网连接的设备、或所述目标组播组对应的源子网中与核心网连接的设备。具体可以实现上述步骤S220或者步骤S320中的发送功能,以及其他隐含步骤。
可选地,所述确定模块710,还用于根据所述目标组播组对应的BFIR的标识信息、以及所述源子网中至少一个与核心网连接的设备的标识信息,确定所述源子网的TE位串;
所述发送模块720,还用于将所述源子网的TE位串发送至所述BFIR。
可选地,当所述目标组播组对应的BFER中存在至少一个BFER属于所述源子网时,所述确定模块710用于:
根据所述目标组播组对应的BFIR的标识信息、所述源子网中至少一个与核心网连接的设备的标识信息、以及所述至少一个BFER的标识信息,确定所述源子网的TE位串。
可选地,所述发送模块720还用于:
将每个目的子网的标识信息发送至所述BFIR。
需要说明的是,上述确定模块710和发送模块720可以由处理器实现,或者处理器配合存储器来实现,或者,处理器执行存储器中的程序指令来实现。
本公开一示例性实施例提供了一种BFIR,如图8所示,所述BFIR包括:
接收模块810,用于接收控制器发送的目标组播组对应的每个目的子网的标识信息;具体可以实现上述方法实施例中的接收功能,以及其他隐含步骤。
转发模块820,用于当接收到所述目标组播组的组播报文时,将每个目的子网的标识信息添加到所述组播报文的报头中,通过组播方式,对添加了每个目的子网的标识信息的组播报文进行转发。具体可以实现上述方法实施例中的转发功能,以及其他隐含步骤。
可选地,所述接收模块810,还用于接收所述控制器发送的所述目标组播组对应的源子网的TE位串;
所述转发模块820,用于当接收到所述目标组播组的组播报文时,将所述TE位串和每个目的子网的标识信息添加到所述组播报文的报头中,将添加了所述TE位串和每个目的子网的标识信息的组播报文进行转发。
需要说明的是,上述接收模块810和转发模块820可以由处理器实现,或者处理器配合存储器来实现,或者,处理器执行存储器中的程序指令来实现。
本公开一示例性实施例提供了一种目标组播组对应的目的子网中与核心网连接的设备,如图9所示,所述设备包括:
接收模块911,用于接收添加外层封装的所述目标组播组的组播报文;具体可以实现上述步骤S250或者步骤S370中的接收功能,以及其他隐含步骤。
去除模块910,用于当接收到添加外层封装的所述目标组播组的组播报文时,去除所述外层封装得到所述组播报文;具体可以实现上述步骤S250或者步骤S370中的去除功能,以及其他隐含步骤。
添加模块920,用于将所述目的子网的位串添加到所述组播报文的报头中;具体可以实现上述步骤S260中的添加功能,以及其他隐含步骤。
转发模块930,用于对添加了所述目的子网的位串的组播报文进行转发。具体可以实现上述步骤S270或者步骤S380中的转发功能,以及其他隐含步骤。
可选地,所述位串为TE位串,所述接收模块911还用于:
接收控制器发送的所述目的子网的TE位串。
可选地,所述添加模块920用于:
用所述目的子网的位串,替换所述组播报文的报头中的所述目标组播组对应的源子网的位串。
需要说明的是,上述接收模块911、去除模块910、添加模块920和转发模块930可以由处理器实现,或者处理器配合存储器来实现,或者,处理器执行存储器中的程序指令来实现。
本公开实施例中,在源子网中与核心网连接的设备接收到组播报文时,根据组播报文要发往的目的子网的数量对组播报文进行复制,避免了在组播报文一开始进入数据传输网络时就被BFIR复制多份。从而,可以大大减少数据传输网络中的组播报文的数量,并且减少网络资源的占用。
需要说明的是:上述实施例提供的设备在传输组播报文时,仅以上述各功能模块的划分进行举例说明,实际应用中,可以根据需要而将上述功能分配由不同的功能模块完成,即将各设备的内部结构划分成不同的功能模块,以完成以上描述的全部或者部分功能。另外,上述实施例提供的设备与传输组播报文的方法实施例属于同一构思,其具体实现过程详见方法实施例,这里不再赘述。
本公开一示例性实施例提供了一种传输组播报文的系统,所述系统包括目标组播组对应的源子网中与核心网连接的设备和BFIR;
所述BFIR,用于当接收到所述目标组播组的组播报文时,通过组播方式,对所述组播报文进行转发;
所述源子网中与核心网连接的设备,用于当接收到所述组播报文时,确定所述目标组播组对应的多个目的子网中与核心网连接的设备的地址,对所述组播报文进行复制,得到与所述多个目的子网数量相等的多个组播报文;分别对每个组播报文添加外层封装,对添加外层封装的组播报文进行转发,其中,外层封装中的目的地址分别为每个目的子网中与核心网连接的设备的地址。
可选地,所述系统还包括控制器;
所述控制器,用于将所述目标组播组对应的每个目的子网的标识信息发送至所述BFIR;
所述BFIR,还用于将所述每个目的子网的标识信息添加到所述组播报文的报头中;
所述源子网中与核心网连接的设备,用于当接收到所述组播报文时,基于预设的目的子网的标识信息和目的子网中与核心网连接的设备的地址的对应关系,以及所述组播报文的报头中携带的多个目的子网的标识信息,确定对应的多个目的子网中与核心网连接的设备的地址。
可选地,所述系统还包括目标组播组对应的目的子网中与核心网连接的设备;
所述控制器,还用于分别确定所述目标组播组对应的多个BFER所属的目的子网,根据每个目的子网中与核心网连接的设备的标识信息、以及每个目的子网中的BFER的标识信息,分别确定每个目的子网的位串;将每个目的子网的位串分别发送至对应的目的子网中与核心网连接的设备;
所述目的子网中与核心网连接的设备,用于当接收到添加外层封装的组播报文时,去除所述外层封装得到所述组播报文;将所述目的子网的位串添加到所述组播报文的报头中;对添加了所述目的子网的位串的组播报文进行转发。
可选地,所述控制器,还用于根据所述目标组播组对应的BFIR的标识信息、以及所述源子网中至少一个与核心网连接的设备的标识信息,确定所述源子网的位串;将所述源子网的位串发送至所述BFIR;
所述BFIR,还用于接收所述控制器发送的所述源子网的位串;当接收到所述组播报文时,将所述源子网的位串和每个目的子网的标识信息添加到所述组播报文的报头中,将添加了所述源子网的位串和每个目的子网的标识信息的组播报文进行转发。
关于上述实施例中的系统,其中各设备执行操作的具体方式已经在有关该方法的实施例中进行了详细描述,此处将不做详细阐述说明。
本领域技术人员在考虑说明书及实践这里公开的公开后,将容易想到本公开的其它实施方案。本申请旨在涵盖本公开的任何变型、用途或者适应性变化,这些变型、用途或者适应性变化遵循本公开的一般性原理并包括本公开未公开的本技术领域中的公知常识或惯用技术手段。说明书和实施例仅被视为示例性的,本公开的真正范围和精神由下面的权利要求指出。
应当理解的是,本公开并不局限于上面已经描述并在附图中示出的精确结构,并且可以在不脱离其范围进行各种修改和改变。本公开的范围仅由所附的权利要求来限制。

Claims (40)

  1. 一种传输组播报文的方法,其特征在于,所述方法应用于目标组播组对应的源子网中与核心网连接的设备,所述方法包括:
    当接收到目标组播组的组播报文时,确定所述目标组播组对应的多个目的子网中与核心网连接的设备的地址,对所述组播报文进行复制,得到与所述多个目的子网数量相等的多个组播报文;
    分别对每个组播报文添加外层封装,对添加外层封装的组播报文进行转发,其中,外层封装中的目的地址分别为每个目的子网中与核心网连接的设备的地址。
  2. 根据权利要求1所述的方法,其特征在于,所述当接收到目标组播组的组播报文时,确定所述目标组播组对应的多个目的子网中与核心网连接的设备的地址,包括:
    当接收到目标组播组的组播报文时,基于预设的目的子网的标识信息和目的子网中与核心网连接的设备的地址的对应关系,以及所述组播报文的报头中携带的多个目的子网的标识信息,确定对应的多个目的子网中与核心网连接的设备的地址。
  3. 根据权利要求1所述的方法,其特征在于,所述当接收到目标组播组的组播报文时,确定所述目标组播组对应的多个目的子网中与核心网连接的设备的地址,包括:
    基于预设的组播地址和目的子网中与核心网连接的设备的地址的对应关系,确定所述组播报文中携带的组播地址对应的多个目的子网中与核心网连接的设备的地址。
  4. 根据权利要求1所述的方法,其特征在于,在分别对每个组播报文添加外层封装之前,所述方法还包括:
    接收控制器发送的每个目的子网的流量工程TE位串;
    分别将每个目的子网的TE位串,添加到对应的组播报文的报头中,得到每个目的子网对应的组播报文。
  5. 根据权利要求4所述的方法,其特征在于,所述分别将每个目的子网的TE位串,添加到对应的组播报文的报头中,得到每个目的子网对应的组播报文,包括:
    分别用所述目的子网的TE位串,替换对应的组播报文的报头中的所述源子网的TE位串,得到每个目的子网对应的组播报文。
  6. 一种传输组播报文的方法,其特征在于,所述方法应用于控制器,所述方法包括:
    分别确定目标组播组对应的多个位转发出口路由器BFER所属的目的子网,根据每个目的子网中与核心网连接的设备的标识信息、以及每个目的子网中的BFER的标识信息,分别确定每个目的子网的TE位串;
    将每个目的子网的TE位串分别发送至对应的目的子网中与核心网连接的设备、或所述目标组播组对应的源子网中与核心网连接的设备。
  7. 根据权利要求6所述的方法,其特征在于,所述方法还包括:
    根据所述目标组播组对应的位转发入口路由器BFIR的标识信息、以及所述源子网中至少一个与核心网连接的设备的标识信息,确定所述源子网的TE位串;
    将所述源子网的TE位串发送至所述BFIR。
  8. 根据权利要求7所述的方法,其特征在于,如果所述目标组播组对应的BFER 中存在至少一个BFER属于所述源子网,则所述根据所述目标组播组对应的BFIR的标识信息、以及所述源子网中至少一个与核心网连接的设备的标识信息,确定所述源子网的TE位串,包括:
    根据所述目标组播组对应的BFIR的标识信息、所述源子网中至少一个与核心网连接的设备的标识信息、以及所述至少一个BFER的标识信息,确定所述源子网的TE位串。
  9. 根据权利要求7所述的方法,其特征在于,所述方法还包括:
    将每个目的子网的标识信息发送至所述BFIR。
  10. 一种传输组播报文的方法,其特征在于,所述方法应用于BFIR,所述方法包括:
    接收控制器发送的目标组播组对应的每个目的子网的标识信息;
    当接收到所述目标组播组的组播报文时,将每个目的子网的标识信息添加到所述组播报文的报头中,通过组播方式,对添加了每个目的子网的标识信息的组播报文进行转发。
  11. 根据权利要求10所述的方法,其特征在于,所述方法还包括:
    接收所述控制器发送的所述目标组播组对应的源子网的TE位串;
    所述当接收到所述目标组播组的组播报文时,将每个目的子网的标识信息添加到所述组播报文的报头中,通过组播方式,对添加了每个目的子网的标识信息的组播报文进行转发,包括:
    当接收到所述目标组播组的组播报文时,将所述TE位串和每个目的子网的标识信息添加到所述组播报文的报头中,将添加了所述TE位串和每个目的子网的标识信息的组播报文进行转发。
  12. 一种传输组播报文的方法,其特征在于,所述方法应用于目标组播组对应的目的子网中与核心网连接的设备,所述方法包括:
    当接收到添加外层封装的所述目标组播组的组播报文时,去除所述外层封装得到所述组播报文;
    将所述目的子网的位串添加到所述组播报文的报头中;
    对添加了所述目的子网的位串的组播报文进行转发。
  13. 根据权利要求12所述的方法,其特征在于,所述位串为TE位串,在将所述目的子网的位串添加到所述组播报文的报头中之前,所述方法还包括:
    接收控制器发送的所述目的子网的TE位串。
  14. 根据权利要求12所述的方法,其特征在于,所述将所述目的子网的位串添加到所述组播报文的报头中,包括:
    用所述目的子网的位串,替换所述组播报文的报头中的所述目标组播组对应的源子网的位串。
  15. 一种目标组播组对应的源子网中与核心网连接的设备,其特征在于,所述设 备包括:
    确定模块,用于当接收到目标组播组的组播报文时,确定所述目标组播组对应的多个目的子网中与核心网连接的设备的地址,对所述组播报文进行复制,得到与所述多个目的子网数量相等的多个组播报文;
    添加模块,用于分别对每个组播报文添加外层封装,其中,外层封装中的目的地址分别为每个目的子网中与核心网连接的设备的地址;
    转发模块,用于对添加外层封装的组播报文进行转发。
  16. 根据权利要求15所述的设备,其特征在于,所述确定模块用于:
    当接收到目标组播组的组播报文时,基于预设的目的子网的标识信息和目的子网中与核心网连接的设备的地址的对应关系,以及所述组播报文的报头中携带的多个目的子网的标识信息,确定对应的多个目的子网中与核心网连接的设备的地址。
  17. 根据权利要求15所述的设备,其特征在于,所述确定模块用于:
    基于预设的组播地址和目的子网中与核心网连接的设备的地址的对应关系,确定所述组播报文中携带的组播地址对应的多个目的子网中与核心网连接的设备的地址。
  18. 根据权利要求15所述的设备,其特征在于,所述设备还包括:
    接收模块,用于接收控制器发送的每个目的子网的TE位串;
    所述添加模块,还用于分别将每个目的子网的TE位串,添加到对应的组播报文的报头中,得到每个目的子网对应的组播报文。
  19. 根据权利要求18所述的设备,其特征在于,所述添加模块用于:
    分别用所述目的子网的TE位串,替换对应的组播报文的报头中的所述源子网的TE位串,得到每个目的子网对应的组播报文。
  20. 一种控制器,其特征在于,所述控制器包括:
    确定模块,用于分别确定目标组播组对应的多个BFER所属的目的子网,根据每个目的子网中与核心网连接的设备的标识信息、以及每个目的子网中的BFER的标识信息,分别确定每个目的子网的TE位串;
    发送模块,用于将每个目的子网的TE位串分别发送至对应的目的子网中与核心网连接的设备、或所述目标组播组对应的源子网中与核心网连接的设备。
  21. 根据权利要求20所述的控制器,其特征在于,所述确定模块,还用于根据所述目标组播组对应的BFIR的标识信息、以及所述源子网中至少一个与核心网连接的设备的标识信息,确定所述源子网的TE位串;
    所述发送模块,还用于将所述源子网的TE位串发送至所述BFIR。
  22. 根据权利要求21所述的控制器,其特征在于,当所述目标组播组对应的BFER中存在至少一个BFER属于所述源子网时,所述确定模块用于:
    根据所述目标组播组对应的BFIR的标识信息、所述源子网中至少一个与核心网连接的设备的标识信息、以及所述至少一个BFER的标识信息,确定所述源子网的TE位串。
  23. 根据权利要求21所述的控制器,其特征在于,所述发送模块还用于:
    将每个目的子网的标识信息发送至所述BFIR。
  24. 一种BFIR,其特征在于,所述BFIR包括:
    接收模块,用于接收控制器发送的目标组播组对应的每个目的子网的标识信息;
    转发模块,用于当接收到所述目标组播组的组播报文时,将每个目的子网的标识信息添加到所述组播报文的报头中,通过组播方式,对添加了每个目的子网的标识信息的组播报文进行转发。
  25. 根据权利要求24所述的BFIR,其特征在于,所述接收模块,还用于接收所述控制器发送的所述目标组播组对应的源子网的TE位串;
    所述转发模块,用于当接收到所述目标组播组的组播报文时,将所述TE位串和每个目的子网的标识信息添加到所述组播报文的报头中,将添加了所述TE位串和每个目的子网的标识信息的组播报文进行转发。
  26. 一种目标组播组对应的目的子网中与核心网连接的设备,其特征在于,所述设备包括:
    接收模块,用于接收添加外层封装的所述目标组播组的组播报文;
    去除模块,用于去除所述外层封装得到所述组播报文;
    添加模块,用于将所述目的子网的位串添加到所述组播报文的报头中;
    转发模块,用于对添加了所述目的子网的位串的组播报文进行转发。
  27. 根据权利要求26所述的设备,其特征在于,所述位串为TE位串,所述接收模块还用于:
    接收控制器发送的所述目的子网的TE位串。
  28. 根据权利要求26所述的设备,其特征在于,所述添加模块用于:
    用所述目的子网的位串,替换所述组播报文的报头中的所述目标组播组对应的源子网的位串。
  29. 一种传输组播报文的系统,其特征在于,所述系统包括目标组播组对应的源子网中与核心网连接的设备和BFIR;
    所述BFIR,用于当接收到所述目标组播组的组播报文时,通过组播方式,对所述组播报文进行转发;
    所述源子网中与核心网连接的设备,用于当接收到所述组播报文时,确定所述目标组播组对应的多个目的子网中与核心网连接的设备的地址,对所述组播报文进行复制,得到与所述多个目的子网数量相等的多个组播报文;分别对每个组播报文添加外层封装,对添加外层封装的组播报文进行转发,其中,外层封装中的目的地址分别为每个目的子网中与核心网连接的设备的地址。
  30. 根据权利要求29所述的系统,其特征在于,所述系统还包括控制器;
    所述控制器,用于将所述目标组播组对应的每个目的子网的标识信息发送至所述BFIR;
    所述BFIR,还用于将所述每个目的子网的标识信息添加到所述组播报文的报头中;
    所述源子网中与核心网连接的设备,用于当接收到所述组播报文时,基于预设的 目的子网的标识信息和目的子网中与核心网连接的设备的地址的对应关系,以及所述组播报文的报头中携带的多个目的子网的标识信息,确定对应的多个目的子网中与核心网连接的设备的地址。
  31. 根据权利要求29或30所述的系统,其特征在于,所述系统还包括目标组播组对应的目的子网中与核心网连接的设备;
    所述控制器,还用于分别确定所述目标组播组对应的多个BFER所属的目的子网,根据每个目的子网中与核心网连接的设备的标识信息、以及每个目的子网中的BFER的标识信息,分别确定每个目的子网的位串;将每个目的子网的位串分别发送至对应的目的子网中与核心网连接的设备;
    所述目的子网中与核心网连接的设备,用于当接收到添加外层封装的组播报文时,去除所述外层封装得到所述组播报文;将所述目的子网的位串添加到所述组播报文的报头中;对添加了所述目的子网的位串的组播报文进行转发。
  32. 根据权利要求29-31中任一项所述的系统,其特征在于,所述控制器,还用于根据所述目标组播组对应的BFIR的标识信息、以及所述源子网中至少一个与核心网连接的设备的标识信息,确定所述源子网的位串;将所述源子网的位串发送至所述BFIR;
    所述BFIR,还用于接收所述控制器发送的所述源子网的位串;当接收到所述组播报文时,将所述源子网的位串和每个目的子网的标识信息添加到所述组播报文的报头中,将添加了所述源子网的位串和每个目的子网的标识信息的组播报文进行转发。
  33. 一种计算机可读存储介质,其特征在于,包括指令,当所述计算机可读存储介质在目标组播组对应的源子网中与核心网连接的设备上运行时,使得所述设备执行所述权利要求1-5中任一权利要求所述的方法。
  34. 一种包含指令的计算机程序产品,其特征在于,当所述计算机程序产品在目标组播组对应的源子网中与核心网连接的设备上运行时,使得所述设备执行所述权利要求1-5中任一权利要求所述的方法。
  35. 一种计算机可读存储介质,其特征在于,包括指令,当所述计算机可读存储介质在控制器上运行时,使得所述控制器执行所述权利要求6-9中任一权利要求所述的方法。
  36. 一种包含指令的计算机程序产品,其特征在于,当所述计算机程序产品在控制器上运行时,使得所述控制器执行所述权利要求6-9中任一权利要求所述的方法。
  37. 一种计算机可读存储介质,其特征在于,包括指令,当所述计算机可读存储介质在BFIR上运行时,使得所述BFIR执行所述权利要求10-11中任一权利要求所述的方法。
  38. 一种包含指令的计算机程序产品,其特征在于,当所述计算机程序产品在BFIR上运行时,使得所述BFIR执行所述权利要求10-11中任一权利要求所述的方法。
  39. 一种计算机可读存储介质,其特征在于,包括指令,当所述计算机可读存储介质在目标组播组对应的目的子网中与核心网连接的设备上运行时,使得所述设备执行所述权利要求12-14中任一权利要求所述的方法。
  40. 一种包含指令的计算机程序产品,其特征在于,当所述计算机程序产品在目标组播组对应的目的子网中与核心网连接的设备上运行时,使得所述设备执行所述权利要求12-14中任一权利要求所述的方法。
PCT/CN2018/124157 2018-03-30 2018-12-27 传输组播报文的方法、设备和系统 WO2019184485A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
KR1020207030626A KR102430395B1 (ko) 2018-03-30 2018-12-27 멀티캐스트 패킷을 전송하기 위한 방법, 장치, 및 시스템
EP18912178.3A EP3767901A4 (en) 2018-03-30 2018-12-27 METHOD OF TRANSMISSION OF MULTICAST MESSAGES, DEVICE AND SYSTEM
JP2020552777A JP7050177B2 (ja) 2018-03-30 2018-12-27 マルチキャストパケットを伝送する方法、デバイス、及びシステム
US17/033,100 US11736411B2 (en) 2018-03-30 2020-09-25 Method, device, and system for transmitting multicast packet

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810277203.3A CN110324263B (zh) 2018-03-30 2018-03-30 传输组播报文的方法、设备和系统
CN201810277203.3 2018-03-30

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/033,100 Continuation US11736411B2 (en) 2018-03-30 2020-09-25 Method, device, and system for transmitting multicast packet

Publications (1)

Publication Number Publication Date
WO2019184485A1 true WO2019184485A1 (zh) 2019-10-03

Family

ID=68059481

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/124157 WO2019184485A1 (zh) 2018-03-30 2018-12-27 传输组播报文的方法、设备和系统

Country Status (6)

Country Link
US (1) US11736411B2 (zh)
EP (1) EP3767901A4 (zh)
JP (1) JP7050177B2 (zh)
KR (1) KR102430395B1 (zh)
CN (1) CN110324263B (zh)
WO (1) WO2019184485A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112995091A (zh) * 2019-12-02 2021-06-18 中兴通讯股份有限公司 数据压缩方法、装置、网络设备及存储介质
CN114301839A (zh) * 2020-09-22 2022-04-08 华为技术有限公司 一种组播报文传输方法及装置

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111614556B (zh) * 2019-02-26 2023-05-12 中兴通讯股份有限公司 一种基于bier的双向转发检测会话创建方法及相关设备
CN112671630B (zh) * 2020-12-11 2023-01-17 北京东土军悦科技有限公司 一种组播方法、装置、网络设备及存储介质
CN113595912B (zh) * 2021-07-05 2022-11-11 北京邮电大学 5GLAN中基于IPv6扩展报头的一对多通信方法及装置
CN116112696A (zh) * 2021-11-11 2023-05-12 中兴通讯股份有限公司 直播方法、系统、bier控制器、路由器、设备及可读介质
US20230261969A1 (en) * 2022-02-11 2023-08-17 Nokia Solutions And Networks Oy Stateless and secure packet forwarding

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104811387A (zh) * 2014-01-24 2015-07-29 思科技术公司 具有位索引显式复制的等价多路径
US20160012714A1 (en) * 2007-08-03 2016-01-14 Belkin International, Inc. Emergency notification device and system
CN106656524A (zh) * 2015-10-30 2017-05-10 中兴通讯股份有限公司 一种bier控制信息的传输方法、装置和系统
CN107171977A (zh) * 2016-03-08 2017-09-15 中兴通讯股份有限公司 报文转发方法及装置
CN107592262A (zh) * 2016-07-07 2018-01-16 中兴通讯股份有限公司 报文发送方法和装置、报文跨域转发的网络架构

Family Cites Families (52)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
ES2129038T3 (es) * 1992-11-27 1999-06-01 Ibm Encaminamiento a destinos multiples entre dominios.
US7016351B1 (en) * 2000-02-29 2006-03-21 Cisco Technology, Inc. Small group multicast in a computer network
US7707300B1 (en) * 2001-04-13 2010-04-27 Cisco Technology, Inc. Methods and apparatus for transmitting information in a network
US7339903B2 (en) * 2001-06-14 2008-03-04 Qualcomm Incorporated Enabling foreign network multicasting for a roaming mobile node, in a foreign network, using a persistent address
US8935333B2 (en) * 2001-08-09 2015-01-13 International Business Machines Corporation Implementing multicast on a system area network channel adapter
US7039052B2 (en) * 2001-09-19 2006-05-02 International Business Machines Corporation Selective routing of multi-recipient communications
US7221676B2 (en) * 2002-07-30 2007-05-22 Brocade Communications Systems, Inc. Supporting local IB packet communication between separate subnets
JP2005051548A (ja) * 2003-07-29 2005-02-24 Furukawa Electric Co Ltd:The データ中継方法、データ中継装置およびその装置を用いたデータ中継システム
CN101620687B (zh) 2004-04-26 2011-07-13 瑞萨电子株式会社 存储卡
US8036221B2 (en) * 2004-06-14 2011-10-11 Cisco Technology, Inc. Method and system for dynamic secured group communication
CN100446241C (zh) 2005-06-30 2008-12-24 矽品精密工业股份有限公司 可容置大尺寸芯片的半导体装置及其制法
US20070032122A1 (en) 2005-08-03 2007-02-08 3 View Technology Co., Ltd Electronic device with USB storage card
WO2009011014A1 (ja) * 2007-07-13 2009-01-22 Fujitsu Limited マルチキャスト配信システム及び方法
CN102087879A (zh) 2009-12-07 2011-06-08 三星电子株式会社 存储卡和电子装置
US9019865B2 (en) * 2011-03-04 2015-04-28 Juniper Networks, Inc. Advertising traffic engineering information with the border gateway protocol
JP5776337B2 (ja) * 2011-06-02 2015-09-09 富士通株式会社 パケット変換プログラム、パケット変換装置、及びパケット変換方法
US9330154B2 (en) * 2011-08-22 2016-05-03 Sybase, Inc. Multicast database replication
US8937949B2 (en) * 2012-12-20 2015-01-20 Oracle International Corporation Method and system for Infiniband host channel adapter multicast packet replication mechanism
US9521007B2 (en) * 2013-04-25 2016-12-13 Mediatek Inc. Multi-level replication counter storage device for multicast packet processing and related method for managing multicast packet processing
US9438432B2 (en) * 2013-09-17 2016-09-06 Cisco Technology, Inc. Bit indexed explicit replication packet encapsulation
US10461946B2 (en) * 2013-09-17 2019-10-29 Cisco Technology, Inc. Overlay signaling for bit indexed explicit replication
US9794079B2 (en) * 2014-03-31 2017-10-17 Nicira, Inc. Replicating broadcast, unknown-unicast, and multicast traffic in overlay logical networks bridged with physical networks
KR102168170B1 (ko) 2014-06-30 2020-10-20 삼성전자주식회사 메모리 카드
US20160012739A1 (en) 2014-07-14 2016-01-14 Ali Jafari Networking systems and methods for facilitating communication and collaboration using a social-networking and interactive approach
US9742575B2 (en) * 2014-11-04 2017-08-22 Telefonaktiebolaget L M Ericsson (Publ) Explicit list encoding of sparse multicast group membership information with Bit Index Explicit Replication (BIER)
US9432205B2 (en) * 2014-11-04 2016-08-30 Telefonaktiebolaget L M Ericsson (Publ) Explicit block encoding of multicast group membership information with bit index explicit replication (BIER)
US10158566B2 (en) * 2015-03-20 2018-12-18 Telefonaktiebolaget Lm Ericsson (Publ) Shortest path bridge with MPLS labels
US9544240B1 (en) * 2015-07-13 2017-01-10 Telefonaktiebolaget L M Ericsson (Publ) MTU discovery over multicast path using bit indexed explicit replication
CN106572017B (zh) * 2015-10-09 2021-06-15 中兴通讯股份有限公司 Bier信息的发送方法、接收方法及装置
CN106656794B (zh) * 2015-10-30 2021-02-09 中兴通讯股份有限公司 一种报文传输方法及装置
CN106982157B (zh) * 2016-01-18 2020-11-20 中兴通讯股份有限公司 流量工程隧道建立方法和装置
US10142227B2 (en) * 2016-01-28 2018-11-27 Cisco Technology, Inc. Bit indexed explicit replication for deterministic network data plane
CN107147508B (zh) 2016-03-01 2022-11-01 中兴通讯股份有限公司 故障检测方法及装置
CN107204920A (zh) 2016-03-18 2017-09-26 中兴通讯股份有限公司 一种快速重路由处理方法、装置和系统
CN107204867B (zh) 2016-03-18 2020-03-24 中兴通讯股份有限公司 一种信息传输方法、装置和系统
EP3252677A1 (en) 2016-06-01 2017-12-06 SmarDTV S.A. A pcmcia contacting unit
WO2018138545A1 (en) * 2017-01-24 2018-08-02 Telefonaktiebolaget Lm Ericsson (Publ) Lossless handover for mobility with location identifier separation protocol in 3rd generation partnership project networks
US10447496B2 (en) * 2017-03-30 2019-10-15 Cisco Technology, Inc. Multicast traffic steering using tree identity in bit indexed explicit replication (BIER)
US10164794B2 (en) 2017-04-28 2018-12-25 Cisco Technology, Inc. Bridging of non-capable subnetworks in bit indexed explicit replication
US10681000B2 (en) * 2017-06-30 2020-06-09 Nicira, Inc. Assignment of unique physical network addresses for logical network addresses
CN109246018B (zh) 2017-07-11 2021-11-30 中兴通讯股份有限公司 基于bier-te的报文转发方法、节点装置及存储介质
CN109391478B (zh) 2017-08-10 2021-09-10 中兴通讯股份有限公司 一种组播业务控制方法和装置、计算机可读存储介质
US10574589B2 (en) * 2017-09-28 2020-02-25 Nokia Technologies Oy Multicast based on bit indexed explicit replication
CN109660460B (zh) 2017-10-10 2021-10-19 中兴通讯股份有限公司 Bier-te信息的处理方法、服务器及存储介质
US10530656B2 (en) * 2017-10-19 2020-01-07 Nicira, Inc. Traffic replication in software-defined networking (SDN) environments
CN109802914B (zh) 2017-11-16 2022-02-18 中兴通讯股份有限公司 一种bsl的确定方法、bier-te控制器和计算机存储介质
US10397010B2 (en) * 2017-11-30 2019-08-27 International Business Machines Corporation Customized multicasting
CN109921987B (zh) 2017-12-13 2022-01-21 中兴通讯股份有限公司 一种bier-te网络检测方法、装置及系统
US11595474B2 (en) * 2017-12-28 2023-02-28 Cisco Technology, Inc. Accelerating data replication using multicast and non-volatile memory enabled nodes
US10567187B2 (en) * 2018-01-11 2020-02-18 Nicira, Inc. Methods to optimize multicast routing in overlay networks
CN207965941U (zh) 2018-02-01 2018-10-12 华为技术有限公司 存储卡和终端
US11483237B2 (en) * 2019-04-25 2022-10-25 Nokia Solutions And Networks Oy BIER traffic engineering (BIER-TE) using unicast MPLS-TE tunnels

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160012714A1 (en) * 2007-08-03 2016-01-14 Belkin International, Inc. Emergency notification device and system
CN104811387A (zh) * 2014-01-24 2015-07-29 思科技术公司 具有位索引显式复制的等价多路径
CN106656524A (zh) * 2015-10-30 2017-05-10 中兴通讯股份有限公司 一种bier控制信息的传输方法、装置和系统
CN107171977A (zh) * 2016-03-08 2017-09-15 中兴通讯股份有限公司 报文转发方法及装置
CN107592262A (zh) * 2016-07-07 2018-01-16 中兴通讯股份有限公司 报文发送方法和装置、报文跨域转发的网络架构

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112995091A (zh) * 2019-12-02 2021-06-18 中兴通讯股份有限公司 数据压缩方法、装置、网络设备及存储介质
CN112995091B (zh) * 2019-12-02 2023-06-23 中兴通讯股份有限公司 数据压缩方法、装置、网络设备及存储介质
CN114301839A (zh) * 2020-09-22 2022-04-08 华为技术有限公司 一种组播报文传输方法及装置
CN114301839B (zh) * 2020-09-22 2023-05-12 华为技术有限公司 一种组播报文传输方法及装置

Also Published As

Publication number Publication date
JP7050177B2 (ja) 2022-04-07
KR102430395B1 (ko) 2022-08-05
CN110324263A (zh) 2019-10-11
KR20200130459A (ko) 2020-11-18
EP3767901A4 (en) 2021-04-28
CN110324263B (zh) 2021-06-29
US20210014174A1 (en) 2021-01-14
JP2021517425A (ja) 2021-07-15
EP3767901A1 (en) 2021-01-20
US11736411B2 (en) 2023-08-22

Similar Documents

Publication Publication Date Title
WO2019184485A1 (zh) 传输组播报文的方法、设备和系统
WO2021063232A1 (zh) 建立bier转发表项的方法、装置和系统
US11240053B2 (en) Overlay signaling for bit indexed explicit replication
US10616063B1 (en) Stateless multicast in IP networks
US10498547B2 (en) Bit indexed explicit replication
US9948574B2 (en) Bit indexed explicit replication packet encapsulation
EP3863237A1 (en) Packet forwarding method, packet transmission device, and packet reception device
US8908527B2 (en) Using context labels to scale MAC tables on computer network edge devices
US11652735B2 (en) Multicast data packet processing method, and apparatus
US9832290B2 (en) Protocol independent multicast register optimization
CN107124366B (zh) 一种实现服务质量控制的方法、装置及系统
WO2022062506A1 (zh) 一种数据处理方法、装置、存储介质及电子装置
CN101656663B (zh) 一种mpls多播报文的转发方法、装置及系统
WO2017198131A1 (zh) 用于重定向数据流的方法和系统、网络设备和控制设备
CN112491706B (zh) 数据报文的处理方法及装置、存储介质、电子装置
CN112134776B (zh) 生成组播转发表项的方法和接入网关
WO2021143279A1 (zh) 段路由业务处理方法和装置、路由设备及存储介质
KR20180025944A (ko) Sdn 기반의 arp 구현 방법 및 장치
JP2020188478A (ja) Sfcネットワークにおけるトポロジー情報を同期させるための方法、およびルーティングネットワーク要素
WO2022117018A1 (zh) 报文传输的方法和装置
WO2020168982A1 (zh) 一种发送和获取断言报文的方法和网络节点
US20230081052A1 (en) Method and apparatus for sending multicast packet
WO2022116615A1 (zh) 报文传输的方法、获取对应关系的方法、装置及系统
WO2022222582A1 (zh) 一种报文处理方法、装置、存储介质及电子装置
CN118301060A (zh) 组播数据报文的处理方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18912178

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2020552777

Country of ref document: JP

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2018912178

Country of ref document: EP

Effective date: 20201012

ENP Entry into the national phase

Ref document number: 20207030626

Country of ref document: KR

Kind code of ref document: A