Method, switching system and switching device for communication

By adding purpose identifiers to multicast service data, the problem of data loss during unicast and multicast switching is solved, and a fast lossless switching process is realized.

CN115348170BActive Publication Date: 2025-07-08HUAWEI TECH CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202110517524.8
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2021-05-12
Publication Date
2025-07-08
Estimated Expiration
2041-05-12

AI Technical Summary

Technical Problem

During the unicast and multicast switching process, the prior art cannot quickly and losslessly switch, resulting in lost service data.

Method used

By adding a purpose identifier that uniquely indicates the destination device to the multicast service data, the switching device can still identify and forward the data when the multicast table is not fully configured, and query the multicast table to determine other destination devices after the configuration is completed, simplifying the configuration process.

Benefits of technology

Reduces the probability of service data loss, simplifies the configuration process, and achieves fast unicast to multicast switching.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN115348170B_ABST
    Figure CN115348170B_ABST
Patent Text Reader

Abstract

The present disclosure relates to a method, a switching system, and a switching device for communication. The method includes: a controller modifies a destination device from a first configuration to a second configuration, in the first configuration, the destination device is used to receive unicast service data having a first service identifier, and in the second configuration, the destination device is used to receive unicast service data having a first service identifier and multicast service data having a second service identifier. The destination device sends a message indicating that the destination device has been modified to the second configuration to a source device via the switching device. After receiving the message, the source device sends multicast service data to the switching device, and the multicast service data includes a second service identifier and a first destination identifier that uniquely indicates the destination device. If it is determined that the multicast service data includes the first destination identifier, the switching device sends the multicast service data to the destination device. In this way, it is possible to quickly and losslessly switch from unicast service to multicast service.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] Embodiments of the present disclosure generally relate to the field of communications, and more particularly, to methods, switching systems, and switching devices for communications. Background Art

[0002] Currently, many switching devices support both unicast and multicast mechanisms. In some scenarios, communication is carried out through unicast services, while in some other scenarios, communication may be carried out through multicast services. During the switching process between different scenarios, a switch between unicast and multicast may occur. However, during the unicast-to-multicast switching process, there are still some problems that prevent a fast and lossless switch. Summary of the Invention

[0003] In view of the above problems, embodiments of the present disclosure provide a method, a switching device, and a switching system for communications.

[0004] In a first aspect of the present disclosure, a method for communications is provided. The method includes: a controller modifying a first destination device from a first configuration to a second configuration, where in the first configuration, the first destination device is configured to receive unicast service data with a first service identifier, and in the second configuration, the first destination device is configured to receive unicast service data with the first service identifier and multicast service data with a second service identifier; the first destination device sending, via a switching device, a message indicating that the first destination device has been modified to the second configuration to a source device; in response to receiving the message from the first destination device, the source device sending multicast service data to the switching device, the multicast service data including the second service identifier and a first destination identifier uniquely indicating the first destination device; the switching device determining whether the multicast service data includes the first destination identifier uniquely indicating the first destination device; and in response to determining that the multicast service data includes the first destination identifier uniquely indicating the first destination device, the switching device sending the multicast service data to the first destination device.

[0005] During the process of switching from unicast to multicast, by setting a destination identifier indicating a single destination device in the multicast service data, the multicast service data can be sent to the destination device when the multicast table in the switching device has not been successfully configured. Therefore, the probability of loss of service data can be reduced. Additionally, during this process, after the destination device completes the configuration, it notifies the source device of the information that the configuration has been completed, and there is no need to strictly perform handshakes in sequence to configure each device, thus simplifying the configuration process and enabling a fast unicast-to-multicast switch.

[0006] In some embodiments, the method further includes: The switching device queries the multicast table based on the second service identifier to determine whether the multicast table includes at least one second destination identifier indicating at least one second destination device. In response to determining that the multicast table includes at least one second destination identifier, the switching device sends multicast service data to the at least one second destination device. By querying the multicast table, the switching device can determine other destination devices in addition to the first destination device to send the multicast service data to these destination devices.

[0007] In some embodiments, the multicast table further includes a first destination identifier. The first destination identifier is one of the multiple leaf nodes in the multicast table, so that the first destination identifier can be more easily excluded when determining at least one second destination identifier, avoiding resending the multicast service data to the first destination device.

[0008] In some embodiments, the message includes a second service identifier and a first destination identifier indicating the first destination device. By including the second service identifier and the first destination identifier in the message, the source device can encapsulate the multicast service data without relying on the configuration of the controller, which can further improve the efficiency of system configuration.

[0009] In some embodiments, the method further includes: The controller modifies the configuration of the source device so that the source device sends unicast service data to the switching device, and the unicast service data includes a third destination identifier indicating a third destination device; The switching device forwards the unicast service data to the third destination device. When switching from multicast service to unicast service, only the configuration of the source device needs to be modified, and there is no need to configure the switching device and the destination device.

[0010] In some embodiments, the source device includes a source switching interface circuit, and the first destination device includes a first destination switching interface circuit.

[0011] In a second aspect of the present disclosure, a method for communication is provided. The method includes: The switching device receives multicast service data from the source device; The switching device determines whether the multicast service data includes a first destination identifier that uniquely indicates the first destination device; and If it is determined that the multicast service data includes a first destination identifier that uniquely indicates the first destination device, the switching device sends the multicast service data to the first destination device. During the process of switching from unicast to multicast, by setting the destination identifier indicating a single destination device in the multicast service data, the multicast service data can be sent to the destination device when the multicast table in the switching device has not been successfully configured. Therefore, the probability of service data loss can be reduced.

[0012] In some embodiments, the method further includes: the switching device determines the service identifier of the multicast service data, and queries the multicast table based on the service identifier of the multicast service data to determine whether the multicast table includes at least one second destination identifier indicating at least one second destination device; and in response to determining that the multicast table includes at least one second destination identifier, the switching device sends the multicast service data to at least one second destination device. By querying the multicast table, the switching device can determine other destination devices in addition to the first destination device, so as to send the multicast service data to these destination devices.

[0013] In some embodiments, the multicast table further includes a first destination identifier. The first destination identifier is one of the multiple leaf nodes in the multicast table, so that the first destination identifier can be more easily excluded when determining at least one second destination identifier, avoiding resending the multicast service data to the first destination device.

[0014] In some embodiments, the method further includes the switching device receiving unicast service data from the source device, the unicast service data including a third destination identifier indicating a third destination device; and the switching device sending the unicast service data to the third destination device.

[0015] In some embodiments, the source device includes a source switching interface circuit, and the first destination device includes a first destination switching interface circuit.

[0016] In a third aspect of the present disclosure, a switching system is provided. The switching system includes: a source device; a switching device communicatively connected to the source device; a first destination device communicatively connected to the switching device; and a controller. The source device, the switching device, the first destination device, and the controller can perform the operations described in the method according to the first aspect of the present disclosure.

[0017] In a fourth aspect of the present disclosure, a switching device is provided. The switching device includes a transceiver circuit and an analysis circuit, wherein the transceiver circuit can perform the transceiver operations in the method according to the second aspect of the present disclosure, and the analysis circuit can perform the data analysis operations in the method according to the second aspect of the present disclosure.

[0018] The Summary of the Invention is provided to introduce a selection of concepts in a simplified form, which will be further described in the Detailed Description below. The Summary of the Invention is not intended to identify the key features or main features of the present disclosure, nor is it intended to limit the scope of the present disclosure. Brief Description of the Drawings

[0019] By describing the exemplary embodiments of the present disclosure in more detail in conjunction with the drawings, the above and other objects, features, and advantages of the present disclosure will become more apparent. Among them, in the exemplary embodiments of the present disclosure, the same reference numerals generally represent the same components.

[0020] Figure 1 Shows a schematic block diagram of a switching system according to some embodiments of the present disclosure.

[0021] Figure 2 Shows a schematic diagram of a unicast service according to some embodiments of the present disclosure.

[0022] Figure 3 Shows a schematic diagram of a multicast service according to some embodiments of the present disclosure.

[0023] Figure 4 Shows an interaction diagram of the unicast-to-multicast handover process according to some embodiments of the present disclosure.

[0024] Figure 5 Shows an interaction diagram of the multicast-to-unicast handover process according to some embodiments of the present disclosure.

[0025] Figure 6 Shows a flowchart of a method for communication according to some embodiments of the present disclosure.

[0026] Figure 7 Shows a flowchart of a method for communication according to some embodiments of the present disclosure.

[0027] Figure 8 Shows a schematic diagram of a switching system according to some embodiments of the present disclosure.

[0028] Figure 9 Shows a schematic diagram of a switching system according to some embodiments of the present disclosure.

[0029] Figure 10 Shows a schematic diagram of a switching device according to some embodiments of the present disclosure. Detailed Embodiments

[0030] The embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although some embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. On the contrary, these embodiments are provided to more thoroughly and completely understand the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are only for illustrative purposes and are not used to limit the protection scope of the present disclosure.

[0031] In the description of the embodiments of the present disclosure, the term "including" and its like should be understood as an open inclusion, that is, "including but not limited to". The term "based on" should be understood as "at least partially based on". The term "one embodiment" or "the embodiment" should be understood as "at least one embodiment". The terms "first", "second", etc. may refer to different or the same objects. The term "and / or" means at least one of the two items associated therewith. For example, "A and / or B" means A, B, or A and B. There may also be other explicit and implicit definitions hereinafter.

[0032] It should be understood that for the technical solutions provided by the embodiments of the present application, in the following introduction of the specific embodiments, some repeated parts may not be elaborated again, but it should be regarded that there are mutual references between these specific embodiments and they can be combined with each other.

[0033] Figure 1 A schematic block diagram of a switching system 100 according to some embodiments of the present disclosure is shown. As Figure 1 shown, the switching system 100 may include a controller 102, devices 104-a to 104-d, and a switching device 106. The switching device 106 includes a plurality of ports and can forward the data received from one port to one or more other ports. The switching device 106 may include one or more switching devices. For example, the switching device 106 may be implemented by a switching network formed by interconnecting a plurality of switching devices with each other. As Figure 1 shown, the switching device 106 includes four ports, which are respectively communicatively connected to the devices 104-a to 104-d. For convenience, the devices 104-a to 104-d may be collectively referred to as the device 104. It should be understood that the number of ports of the switching device 106 and the number of the devices 104 are only provided as examples. The switching device 106 may include more or fewer ports, and the switching system 100 may include more or fewer devices 104. In some embodiments, the device 104-a may be implemented by a fabric interface circuit (FIC). The fabric interface circuit may be communicatively connected to other devices such as a network processor (not shown), and is used to send the service data from the network processor to the switching device 106, or send the service data from the switching device 106 to the network processor.

[0034] As Figure 1As shown, device 104 can send data to switching device 106 and can receive data from switching device 106. When sending data to switching device 106, device 104 can act as a data source that generates data or can forward data received from other data sources to switching device 106. When receiving data from switching device 106, device 104 can parse the received data and process the parsed data or forward the data to other devices for further processing.

[0035] Controller 102 can send configuration information to device 104 and switching device 106 to control the operations of device 104 and switching device 106. For example, controller 102 can communicate with the control planes of device 104 and switching device 106 to modify the configurations of device 104 and switching device 106. Device 104 and switching device 106 can be configured according to the configuration information received from controller 102. For example, controller 102 can send configuration information to device 104-a to configure device 104-a to send unicast service data with a unicast service identifier (e.g., flow identification (FLOWID)) or to configure device 104-a to send multicast service data with a multicast service identifier (e.g., multicast identification (MID)).

[0036] Figure 2 A schematic diagram of a unicast service according to some embodiments of the present disclosure is shown. In Figure 2 for clarity, the controller 102 shown in Figure 1 is omitted. As Figure 2 shown, in this unicast service, device 104-a is sending unicast service data to device 104-d, where the unicast service data includes a unicast service identifier, e.g., FLOWID. Device 104-a can also be referred to as the source device, and device 104-d can also be referred to as the destination device. The unicast service data, particularly the unicast service identifier, can include a destination identifier for specifying the destination device of the unicast service data, i.e., device 104-d. After receiving the unicast service data from device 104-a, switching device 106 determines the destination device (i.e., device 104-d) of the unicast service data according to the destination identifier included in the unicast service data, and switching device 106 forwards the unicast service data received from device 104-a to device 104-d.

[0037] Figure 3 A schematic diagram of a multicast service according to some embodiments of the present disclosure is shown. In Figure 3 for clarity, the controller 102 shown in Figure 1 is omitted. AsFigure 3 As shown, in this multicast service, device 104-a is sending a multicast service to devices 104-c and 104-d. Among them, the multicast service includes a multicast service identifier, for example, MID. The switching device 106 can query the multicast table configured in the switching device 106 according to the multicast service identifier to determine the destination device. In Figure 3 this example, the switching device 106 can determine two destination devices, namely, devices 104-c and 104-d, by querying the multicast table, and forward the multicast service data to devices 104-c and 104-d.

[0038] In some communication scenarios, data transmission and reception between different devices may switch between unicast services and multicast services. For example, from Figure 2 a unicast service to Figure 3 a multicast service, or from Figure 3 a multicast service to Figure 2 a unicast service. For example, during the process of converting from Figure 2 a unicast service to Figure 3 a multicast service, the controller 102 can send configuration information to device 104 and switching device 106 to configure device 104 and switching device 106 to be able to process multicast service data. However, due to the specific conditions of each device being different, even if the controller 102 sends configuration information to device 104 and switching device 106 simultaneously, the configuration processes of device 104 and switching device 106 may not be strictly synchronized. For example, the switching device 106 may be a cluster formed by multiple different switching devices, and the switching device 106 can only complete the configuration after all switching devices have completed the configuration. Therefore, the configuration process of the switching device 106 may take a relatively long time, so that after device 104 has completed the configuration, the switching device 106 may still not have completed the configuration. If the multicast table in the switching device 106 has not been completed when device 104-a starts to send multicast service data, then the switching device 106 cannot query the multicast table according to the multicast service identifier to determine the destination device, which may lead to the loss of multicast service data.

[0039] According to an embodiment of the present disclosure, by adding a destination identifier that uniquely indicates a destination device to the multicast service data, the switching device 106 can forward the multicast service data to the corresponding destination device based on the destination identifier. In this case, even if the multicast table in the switching device 106 is not fully configured, the switching device 106 can still identify the destination identifier in the multicast service data from the device 104-a, and determine the destination device 104-d based on the destination identifier indicating a single destination device, and forward the multicast service data to the destination device 104-d. Additionally, after the switching device 106 is fully configured, the switching device 106 can query the multicast table based on the multicast service identifier to determine other destination devices, such as the device 104-c. Then, the switching device 106 sends the multicast service data to the device 104-c.

[0040] In some embodiments, in the multicast service, the path from the device 104-a to the device 104-d can be the working path, and the path from the device 104-a to the device 104-c can be the protection path or the redundant path to provide a protection function. For example, Subnetwork Connection Protection (SNCP) implements the dual-transmission function through multicast, thereby providing protection features. During the process of switching from unprotected (unicast service) to protected (multicast service), the multicast table may not be fully configured, resulting in only the working path being able to work. At this time, although the redundant path cannot work to provide a protection function, since the working path can work, this still does not cause the loss of service data.

[0041] Figure 4 An interaction diagram showing a method for switching from unicast to multicast according to some embodiments of the present disclosure is shown. As Figure 4 shown, the device 104-a sends 402 unicast service data to the switching device 106. The unicast service data may include a unicast service identifier, for example, FLOWID. The unicast service data may also include a destination identifier indicating the device 104-d as the destination device. For example, the destination identifier indicating the destination device may be included in the unicast service identifier, for example, as a field within the unicast service identifier. After the switching device 106 receives the unicast service data, the switching device 106 can parse the unicast service data to determine the destination identifier indicating the destination device in the unicast service data. According to the destination identifier in the unicast service data, the switching device 106 can forward 404 the unicast service data to the device 104-d indicated by the destination identifier.

[0042] When determining to switch from unicast service to multicast service, the controller 102 may send configuration information 406 to the device 104 and the switching device 106 to modify the configurations of the device 104 and the switching device 106. For example, the controller 102 may send configuration information to the switching device 104-a to modify the configuration of the device 104-a from sending unicast service data with a unicast service identifier (e.g., FLOWID) to sending multicast service data with a multicast service identifier (e.g., MID). The controller 102 may send configuration information to the switching device 106 to configure the multicast table in the switching device 106. In an example where the switching device 106 includes a cluster formed by multiple switching devices, each switching device in the switching device 106 may maintain its own multicast table. The controller 102 may send configuration information to the device 104-d to configure the device 104-d to be able to receive unicast service data and multicast service data. Additionally, the controller 102 may send configuration information to the device 104-c to configure the device 104-c to receive multicast service data.

[0043] Due to various conditions, the devices 104 and the switching device 106 may not be able to synchronize their configurations. For example, as Figure 4 shown, the device 104-d first completes the configuration 408, the device 104-a completes the configuration 410 later, then the device 104-c completes the configuration 412, and finally the switching device 106 completes the configuration 422. It should be understood that the order of these device configurations is provided only as an example, and in different scenarios, the configuration order of these devices may change, thus being different from the Figure 4 order shown.

[0044] As Figure 4As shown, after completing configuration 408, device 104-d may send 414 a message indicating that device 104-d has completed configuration to switching device 106. In some embodiments, the message may include a multicast service identifier (e.g., MID) and a destination identifier indicating the destination device 104-d. For example, the destination identifier of destination device 104-d may be included within the multicast service identifier, e.g., as a field of the multicast service identifier. Switching device 106 may forward the message to device 104-a. After receiving the message, device 104-a may determine that device 104-d has completed configuration. Accordingly, device 104-a may send 418 multicast service data to switching device 106. The multicast service data may include a multicast service identifier and a destination identifier uniquely indicating the destination device. In some embodiments, the destination identifier uniquely indicating the destination device may be part of the multicast service identifier, e.g., as a field of the multicast service identifier. The configuration information received by device 104-a from controller 102 includes the multicast service identifier, and device 104-a knows the destination identifier of destination device 104-d when sending 402 unicast service data. Thus, device 104-a may encapsulate the multicast service data according to the multicast service identifier and the destination identifier of the destination device. Alternatively, in an example where the message sent by device 104-a to device 104-a includes the multicast service identifier and the destination identifier, device 104-a may also encapsulate the multicast service data according to the multicast service identifier and the destination identifier included in the message.

[0045] After receiving the multicast service data from device 104-a, switching device 106 may forward 420 the multicast service data to device 104-d according to the destination identifier uniquely indicating the destination device. Additionally, switching device 106 may also query 424 the multicast table according to the multicast service identifier to determine the destination identifiers of other destination devices. In some embodiments, the destination identifiers determined by querying the multicast table include the destination identifier indicating the destination device included in the multicast service data. In Figure 4 an example, the query 424 operation is performed after the forwarding 420 operation. In some examples, the query 424 may be performed before the forwarding 420 operation to determine whether the multicast table contains the destination identifier indicating the destination device. If the multicast table contains the destination identifier indicating the destination device, the multicast service data is forwarded to these destination devices. In some other embodiments, the forwarding 420 and query 424 operations may also be performed in parallel.

[0046] In Figure 4In the example, when querying the multicast table 424, the switching device 106 has completed the configuration 422. At this time, the switch can query the multicast table according to the multicast service identifier in the multicast service data to determine the destination identifier of the destination device. For example, the destination devices determined by querying the multicast table include devices 104-c and 104-d. Then, the switching device 106 can forward the multicast service data to other destination devices except device 104-d, that is, device 104-c. If the switching device 106 has not completed the configuration when querying the multicast table 424, the switching device 106 cannot query the destination identifier of the destination device and cannot forward the multicast service data to other destination devices. However, since the multicast service data includes the destination identifier indicating a single destination device, the switching device 106 can still send the multicast service to this destination device, that is, device 104-d. In this way, during the handover process from unicast to multicast, service data will not be lost, and the configuration process is simple, without the need for the controller 102 and each device to perform handshake configuration according to a predetermined order.

[0047] Figure 5 FIG. shows an interaction diagram of a method for switching from multicast to unicast according to some embodiments of the present disclosure. As Figure 5 shown, the controller 102 sends configuration information 502 to the device 104-a to modify the configuration of the device 104-a from multicast configuration to unicast configuration. After the device 104-a completes the configuration 504, the device 104-a can send unicast service data 508 to the switching device. The unicast service data includes a unicast service identifier, where the unicast service identifier may include a destination identifier indicating the destination device. The switching device 106 can determine the destination device according to the unicast service identifier in the unicast service data and forward 508 the unicast service data to the destination device, that is, device 104-d. It should be understood that depending on the specific configuration, the destination device may also be device 104-c or any other suitable device.

[0048] According to an embodiment of the present disclosure, during the process of switching from multicast to unicast, only the device 104-a that sends unicast service data needs to be configured to modify the service identifier from a multicast service identifier to a unicast service identifier, without the need to configure other devices.

[0049] Figure 6 FIG. shows a flowchart of a method 600 for communication according to some embodiments of the present disclosure. The method 600 may be implemented by a switching system 100 as Figure 1 shown below, and the method 600 will be described in conjunction with Figure 1 the switching system 100.

[0050] At block 602, the controller 102 modifies the first destination device 104-d from a first configuration to a second configuration. In the first configuration, the first destination device 104-d is used to receive unicast service data having a first service identifier (e.g., a flow identifier FLOWID), and in the second configuration, the first destination device 104-d is used to receive unicast service data having the first service identifier and multicast service data having a second service identifier (e.g., a multicast identifier MID).

[0051] At block 604, the first destination device 104-d sends a message via the switching device 106 to the source device 104-a indicating that the first destination device 104-d has been modified to the second configuration. In some embodiments, the message includes the second service identifier and a first destination identifier indicating the first destination device. For example, the source device 104-a may be a source switching interface circuit, and the first destination device 104-d may be a first destination switching interface circuit.

[0052] At block 606, in response to receiving the message from the first destination device 104-d, the source device 104-a sends multicast service data to the switching device 106, the multicast service data including the second service identifier and a first destination identifier uniquely indicating the first destination device 104-d.

[0053] At block 608, the switching device 106 determines whether the multicast service data includes a first destination identifier uniquely indicating the first destination device 104-d. If it is determined at block 608 that the multicast service data includes a first destination identifier uniquely indicating the first destination device 104-d, then method 600 proceeds to block 610. At block 610, the switching device 106 sends the multicast service data to the first destination device 104-d.

[0054] In some embodiments, the switching device 106 queries a multicast table based on the second service identifier to determine whether the multicast table includes at least one second destination identifier indicating at least one second destination device. In response to determining that the multicast table includes at least one second destination identifier, the switching device 106 sends the multicast service data to the at least one second destination device. For example, the second destination device may be the device 104-c as Figure 1 shown. In some embodiments, the switching device 106 determines a plurality of destination identifiers through querying the multicast table based on the second service identifier, and these destination identifiers include the first destination identifier and at least one second destination identifier.

[0055] In some embodiments, the controller 102 modifies the configuration of the source device 104-a so that the source device 104-a sends unicast service data to the switching device 106, and the unicast service data includes a third destination identifier indicating a third destination device. For example, the third destination device may be device 104-c or 104-d. The switching device 106 forwards the unicast service data to the third destination device. When switching from multicast service to unicast service, only the configuration of the source device 104-a needs to be modified, and there is no need to configure the switching device and the destination device.

[0056] Figure 7 FIG. 700 is a flowchart of a method for communication according to some embodiments of the present disclosure. The method 700 may be implemented at the switching device 106 as shown in Figure 1 and will be described below in conjunction with Figure 1 to describe the method 700.

[0057] At block 702, the switching device 106 receives multicast service data from the source device 104-a. For example, the source device 104-a may be a source switching interface circuit.

[0058] At block 704, the switching device 106 determines whether the multicast service data includes a first destination identifier that uniquely indicates a first destination device. For example, the first destination device may be a first destination switching interface circuit.

[0059] At block 706, if it is determined that the multicast service data includes a first destination identifier that uniquely indicates the first destination device 104-d, the switching device sends the multicast service data to the first destination device 104-d.

[0060] In some embodiments, the switching device 106 determines a service identifier of the multicast service data and queries a multicast table based on the service identifier of the multicast service data to determine whether the multicast table includes at least one second destination identifier indicating at least one second destination device. In response to determining that the multicast table includes at least one second destination identifier, the switching device 106 sends the multicast service data to the at least one second destination device. In some embodiments, the multicast table includes not only at least one second destination identifier but also a first destination identifier.

[0061] In some embodiments, the switching device 106 receives unicast service data from the source device 104-a, and the unicast service data includes a third destination identifier indicating a third destination device. For example, the third destination device may be device 104-c or 104-d. The switching device 106 sends the unicast service data to the third destination device.

[0062] Figure 8 FIG. 800 is a schematic diagram of a switching system according to some embodiments of the present disclosure. The switching system 800 may be as shown in Figure 1Exemplary implementation of the switching system 100 shown. As Figure 8 shown, the service board 802 includes FIC 810-a and FIC 810-b, which may be exemplary implementations of the devices 104-a and 104-b as Figure 1 shown. The service board 802 further includes an IO frame 806, communicatively connected to the FIC 810-a and FIC 810-b, for sending data from the FIC 810-a and 810-b out of the board, or sending data outside the board to the FIC 810-a and 810-b. Additionally, the service board 804 includes FIC 810-c and FIC 810-d, which may be exemplary implementations of the devices 104-c and 104-d as Figure 1 shown. The service board 802 further includes an IO frame 808, communicatively connected to the FIC 810-c and FIC 810-d, for sending data from the FIC 810-c and 810-d out of the board, or sending data outside the board to the FIC 810-c and 810-d. The IO frames 806 and 808 may be communicatively connected to each other, thus serving as the switching device 106 as Figure 1 shown.

[0063] Figure 9 A schematic diagram of a switching system 900 according to some embodiments of the present disclosure is shown. The switching system 900 may be an exemplary implementation of the switching system 100 as Figure 1 shown. Compared with the switching system 800 in Figure 8 , the switching system 900 further includes a cluster switching frame 902. The cluster switching frame 902 may be a cluster formed by interconnecting multiple switching nodes. The IO frames 806 and 808 are respectively communicatively connected to the cluster switching frame 902, thus serving as the switching device 106 as Figure 1 shown.

[0064] Figure 10 A schematic diagram of a switching device 1000 according to some embodiments of the present disclosure is shown. The switching device 1000 may be an exemplary implementation of the switching device 106 as Figure 1 shown. Additionally, the switching device 1000 may also be an exemplary implementation of the IO frames 807 and 808 as Figure 8 or Figure 9 shown, or an exemplary implementation of the cluster switching frame 902 or the switching nodes therein as Figure 9 shown. As Figure 10As shown, the switching device 1000 includes a transceiver circuit 1002 and an analysis circuit 1004 that communicates with the transceiver circuit 1002. The transceiver circuit 1002 is configured to receive multicast service data from a source device. The analysis circuit 1004 is configured to determine whether the multicast service data includes a first destination identifier that uniquely indicates a first destination device. If it is determined that the multicast service data includes a first destination identifier that uniquely indicates a first destination device, the transceiver circuit 1002 sends the multicast service data to the first destination device.

[0065] In some embodiments, the analysis circuit 1004 determines a service identifier of the multicast service data and queries a multicast table based on the service identifier of the multicast service data to determine whether the multicast table includes at least one second destination identifier that indicates at least one second destination device. In response to determining that the multicast table includes at least one second destination identifier, the transceiver circuit 1002 sends the multicast service data to the at least one second destination device. In some embodiments, the multicast table includes not only at least one second destination identifier but also a first destination identifier.

[0066] In some embodiments, the transceiver circuit 1002 receives unicast service data from a source device, and the unicast service data includes a third destination identifier that indicates a third destination device. The transceiver circuit 1002 sends the unicast service data to the third destination device.

[0067] The various embodiments of the present disclosure have been described above. The above description is exemplary and not exhaustive, and is also not limited to the disclosed embodiments. Many modifications and variations are obvious to those of ordinary skill in the art in the technical field without departing from the scope and spirit of the described embodiments. The selection of the terms used herein is intended to best explain the principles of the embodiments, practical applications, or improvements to the technology, or to enable other ordinary skill in the art in the technical field to understand the embodiments disclosed herein.

Claims

1. A method for communication, comprising: The controller modifies the first destination device from a first configuration to a second configuration. In the first configuration, the first destination device is used to receive unicast service data with a first service identifier, and in the second configuration, the first destination device is used to receive unicast service data with the first service identifier and multicast service data with a second service identifier; The first destination device sends a message indicating that the first destination device has been modified to the second configuration to the source device via a switching device; In response to receiving the message from the first destination device, the source device sends multicast service data to the switching device, where the multicast service data includes the second service identifier and a first destination identifier that uniquely indicates the first destination device; The switching device determines whether the multicast service data includes a first destination identifier that uniquely indicates the first destination device; And In response to determining that the multicast service data includes a first destination identifier that uniquely indicates the first destination device, the switching device sends the multicast service data to the first destination device.

2. The method according to claim 1, wherein Further comprising: The switching device queries a multicast table based on the second service identifier to determine whether the multicast table includes at least one second destination identifier indicating at least one second destination device; And In response to determining that the multicast table includes the at least one second destination identifier, the switching device sends the multicast service data to the at least one second destination device.

3. The method according to claim 2, wherein The multicast table further includes the first destination identifier.

4. The method according to any one of claims 1 to 3, characterized in that The message includes the second service identifier and the first destination identifier.

5. The method according to any one of claims 1-3, characterized in that, Further comprising: The controller modifies the configuration of the source device so that the source device sends unicast service data to the switching device, where the unicast service data includes a third destination identifier indicating a third destination device; And The switching device forwards the unicast service data to the third destination device.

6. The method according to any one of claims 1-3, characterized in that, The source device includes a source switching interface circuit, and the first destination device includes a first destination switching interface circuit.

7. A method for communication, comprising: The switching device receives multicast service data from a source device; The switching device determines whether the multicast service data includes a first destination identifier that uniquely indicates a first destination device; And If it is determined that the multicast service data includes a first destination identifier that uniquely indicates the first destination device, the switching device sends the multicast service data to the first destination device.

8. The method according to claim 7, wherein Further comprising: The switching device determines the service identifier of the multicast service data and queries a multicast table based on the service identifier of the multicast service data to determine whether the multicast table includes at least one second destination identifier indicating at least one second destination device; And In response to determining that the multicast table includes the at least one second destination identifier, the switching device sends the multicast service data to the at least one second destination device.

9. The method according to claim 8, wherein The multicast table further includes the first destination identifier.

10. The method according to any one of claims 7-9, characterized in that, Further comprising: The switching device receives unicast service data from the source device, where the unicast service data includes a third destination identifier indicating a third destination device; and The switching device sends the unicast service data to the third destination device.

11. The method according to any one of claims 7-9, characterized in that, The source device includes a source switching interface circuit, and the first destination device includes a first destination switching interface circuit.

12. A switching system, comprising: A source device; A switching device communicatively connected to the source device; A first destination device communicatively connected to the switching device; and A controller that modifies the first destination device from a first configuration to a second configuration, wherein in the first configuration, the first destination device receives unicast service data with a first service identifier, and in the second configuration, the first destination device receives unicast service data with the first service identifier and multicast service data with a second service identifier; wherein the first destination device sends a message indicating that the first destination device has been modified to the second configuration to the source device via the switching device; wherein the source device, in response to receiving the message from the first destination device, sends multicast service data to the switching device, the multicast service data including the second service identifier and a first destination identifier that uniquely indicates the first destination device; wherein the switching device determines whether the multicast service data includes a first destination identifier that uniquely indicates the first destination device, and in response to determining that the multicast service data includes the first destination identifier that uniquely indicates the first destination device, sends the multicast service data to the first destination device.

13. The switching system according to claim 12, wherein The switching device queries a multicast table based on the second service identifier to determine whether the multicast table includes at least one second destination identifier indicating at least one second destination device; and In response to determining that the multicast table includes the at least one second destination identifier, the switching device sends the multicast service data to the at least one second destination device.

14. The switching system according to claim 13, wherein The multicast table further includes the first destination identifier.

15. The switching system according to any one of claims 12-14, characterized in that, The message includes the second service identifier and the first destination identifier.

16. The switching system according to any one of claims 12-14, wherein The controller modifies the configuration of the source device so that the source device sends unicast service data to the switching device, the unicast service data including a third destination identifier indicating a third destination device; and The switching device forwards the unicast service data to the third destination device.

17. The switching system according to any one of claims 12-14, characterized in that, The source device includes a source switching interface circuit, and the first destination device includes a first destination switching interface circuit.

18. The switching system according to any one of claims 12 - 14, characterized in that, The switching device includes an input / output frame.

19. The switching system according to any one of claims 12 - 14, characterized in that, The switching device includes an input / output frame and a cluster switching frame.

20. A switching device, comprising: A transceiver circuit for receiving multicast service data from a source device; and An analysis circuit for determining whether the multicast service data includes a first destination identifier that uniquely indicates a first destination device, wherein if it is determined that the multicast service data includes a first destination identifier that uniquely indicates the first destination device, the transceiver circuit sends the multicast service data to the first destination device.

21. The switching device according to claim 20, wherein: the parsing circuit determines a service identifier of the multicast service data and queries a multicast table based on the service identifier of the multicast service data to determine whether the multicast table includes at least one second destination identifier indicating at least one second destination device; and in response to determining that the multicast table includes the at least one second destination identifier, the transceiver circuit sends the multicast service data to the at least one second destination device.

22. The switching device according to claim 21, characterized in that, The multicast table further includes the first destination identifier.

23. The switching device according to any one of claims 20-22, wherein: the transceiver circuit receives unicast service data from the source device, the unicast service data including a third destination identifier indicating a third destination device; and the transceiver circuit sends the unicast service data to the third destination device.

Citation Information

Patent Citations

  • Customer premise equipment and method for implementing wireless multicast-to-unicast service thereof

    CN101945342A

  • Traffic conversion method, distribution system, unicast / multicast conversion device, multicast / unicast conversion device, unicast / multicast conversion program, and multicast / unicast conversion program

    JP2019075741A