Multicast message processing methods, OLT equipment, ONU equipment and software products

Abstract

This application discloses a multicast message processing method, an OLT device, an ONU device, and a program product, belonging to the field of optical communication technology. The method includes: upon receiving a multicast data message, an OLT slice encapsulates the multicast data message to obtain a multicast data XGEM frame; the OLT device broadcasts the multicast data XGEM frame to multiple optical network units (ONU) devices corresponding to the OLT device, so that a target ONU device among the multiple ONU devices forwards the multicast data message in the multicast data XGEM frame to a corresponding terminal device, wherein the local multicast frame domain information stored by the target ONU device matches the multicast frame domain information. This method can achieve isolation of multicast services from different OLT slices at the ONU side, avoiding the ONU device from invalidally parsing and forwarding multicast data messages from non-OLT slices, thus improving the isolation and service reliability of multicast services between slices.

Description

Technical Field

[0001] This application relates to the field of optical communication technology, and in particular to a multicast message processing method, an OLT device, an ONU device, and a software product. Background Technology

[0002] In optical access networks, network slicing technology is primarily applied to Optical Line Terminal (OLT) equipment, which can virtualize a single physical OLT into multiple OLT slices. Based on slicing granularity, it can be categorized as follows: Passive Optical Network (PON) board-level slicing, PON port-level slicing, Optical Network Unit (ONU)-level slicing, and hybrid granularity slicing. The operator holding the physical OLT equipment is called the infrastructure operator, while the operator sharing the OLT equipment to conduct business is called the Virtual Network Operator (MVNO). To maximize the sharing of access network infrastructure resources, infrastructure operators typically adopt ONU-level slicing granularity. This involves connecting to the operational support systems of each MVNO to enable independent activation and maintenance of each MVNO's services. Key resources such as OLT equipment, access rooms, fiber optic pipelines, and Optical Distribution Networks (ODNs) are shared among the MVNOs, providing end users with multiple MVNO broadband access service options.

[0003] However, when multicast services are running on OLT slices, each OLT slice copies multicast data packets to the corresponding physical PON interface. All ONUs under this physical PON interface will receive, parse, and forward all multicast packets to the user terminal, which leads to problems such as duplicate reception and incorrect interfaces that are not from the operator's multicast streams. This makes it impossible to guarantee the isolation and service reliability of multicast services between slices. Summary of the Invention

[0004] This application provides a multicast message processing method, an OLT device, an ONU device, and a program product to at least solve the problem in related solutions where the ONU device invalidally parses and forwards multicast data messages that do not belong to its OLT slice.

[0005] To solve the above-mentioned technical problems, this application is implemented as follows: In a first aspect, embodiments of this application provide a multicast message processing method applied to an OLT slice in an Optical Line Terminal (OLT) device in an XGSPON network. The method includes: in response to obtaining a multicast data message, encapsulating the multicast data message to obtain a multicast data XGEM frame; wherein, a reserved field in the XGEM frame header of the multicast data XGEM frame is configured as multicast frame domain information, and the multicast frame domain information corresponds one-to-one with the OLT slice; broadcasting the multicast data XGEM frame to multiple Optical Network Unit (ONU) devices corresponding to the OLT device through the OLT device, so that a target ONU device among the multiple ONU devices forwards the multicast data message in the multicast data XGEM frame to a corresponding terminal device, wherein the local multicast frame domain information stored by the target ONU device matches the multicast frame domain information.

[0006] Secondly, embodiments of this application provide a multicast packet processing method applied to ONU devices in an XGSPON network. The method includes: acquiring multicast data XGEM frames broadcast by an Optical Line Terminal (OLT) device in the XGSPON network; decapsulating the multicast data XGEM frames to obtain multicast frame domain information; wherein the multicast data XGEM frames are obtained by encapsulating multicast data packets by an OLT slice of the OLT device; the Options field in the XGEM frame header of the multicast data XGEM frames is configured as the multicast frame domain information, and the multicast frame domain information corresponds one-to-one with the OLT slice; in response to a match between the local multicast frame domain information and the multicast frame domain information, forwarding the multicast data packets obtained by decapsulating the multicast data XGEM frames to the terminal device.

[0007] Thirdly, embodiments of this application provide an OLT device, including a processor and a memory, wherein the memory stores a program or instructions that can run on the processor, and the program or instructions, when executed by the processor, implement the steps of the method described in the first aspect above.

[0008] Fourthly, embodiments of this application provide an ONU device, including a processor and a memory, wherein the memory stores programs or instructions that can run on the processor, and when the programs or instructions are executed by the processor, they implement the steps of the method described in the second aspect above.

[0009] Fifthly, embodiments of this application provide a network device, the network device including a processor and a memory, the memory storing programs or instructions executable on the processor, the programs or instructions, when executed by the processor, implementing the steps of the method described in the first or second aspect above.

[0010] In a sixth aspect, embodiments of this application provide a computer-readable storage medium on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the first or second aspect above.

[0011] In a seventh aspect, embodiments of this application provide a computer program product, the computer program product including a computer program stored on a non-transitory computer-readable storage medium, the computer program including program instructions, which, when executed by a computer, cause the computer to perform the steps of the method described in the first or second aspect above.

[0012] In this embodiment of the application, in the XGSPON network, the OLT slice of the Optical Line Terminal (OLT) device responds to the acquisition of multicast data packets by encapsulating the multicast data packets to obtain multicast data XGEM frames. The OLT device then broadcasts the multicast data XGEM frames to multiple Optical Network Units (ONUs) corresponding to the OLT device. This causes a target ONU device among the multiple ONU devices to forward the multicast data packets in the multicast data XGEM frames to its corresponding terminal device. The local multicast frame domain information stored by the target ONU device matches the multicast frame domain information. This method achieves isolation of multicast services from different OLT slices at the ONU side, preventing ONU devices from invalidally parsing and forwarding multicast data packets from OLT slices that do not belong to them, thus improving the isolation and service reliability of multicast services between slices.

[0013] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not limit this application. Attached Figure Description

[0014] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0015] Figure 1 A flowchart illustrating a multicast message processing method provided in some embodiments of this application is shown; Figure 2 This application provides example diagrams of OLT slicing networking scenarios for XGSPON networks according to some embodiments. Figure 3 A schematic diagram of the structure of an XGEM frame is shown; Figure 4 This diagram illustrates the structure of a GEM frame in a GPON system. Figure 5 A flowchart illustrating a multicast message processing method provided in some other embodiments of this application is shown; Figure 6A flowchart illustrating a multicast message processing method provided in some embodiments of this application is shown; Figure 7 The diagram illustrates a flowchart of a method for collaborative processing of OLT slicing and ONU-side multicast services in an XG(S)PON network provided in some embodiments of this application. Figure 8 The following is a timing diagram illustrating the collaborative processing method of OLT slicing and ONU-side multicast services in an XG(S)PON network provided in some embodiments of this application; Figure 9 The diagram shows a schematic representation of the hardware structure of a network device provided in some embodiments of this application. Detailed Implementation

[0016] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0017] In the telecommunications field, network slicing technology logically divides a physical network, enabling the creation of multiple isolated logical devices on a single physical device. This reduces redundant network construction and achieves efficient service aggregation, secure isolation, and differentiated service delivery. In optical access networks, network slicing technology is primarily applied to OLT devices, allowing a single physical OLT to be virtualized into multiple OLT slices. When ONUs under different OLT slice systems simultaneously stream a multicast program with identical multicast source Internet Protocol (IP) address, multicast group IP address, and Multicast Virtual Local Area Network (MVLAN), each OLT slice generates and distributes corresponding multicast data packets. All packets are broadcast to all ONUs under the physical PON port via the public broadcast channel with Port-ID=4095.

[0018] Because the relevant technologies rely solely on fields such as multicast IP, MVLAN, and GEMPort-ID to identify multicast streams, and multicast packets of the same program from different slices are completely identical in these fields, the ONU cannot distinguish between the OLT slice to which the packet belongs and the virtual operator, resulting in at least the following problems: (1) When the same ONU receives multiple identical multicast data streams in the Port-ID=4095 channel at the same time, multicast service stuttering and decoding abnormalities will occur. The ONU will overlay and cache multiple duplicate multicast streams and parse them repeatedly, resulting in frame duplication and timing disorder during terminal decoding, causing video stuttering, screen tearing, and audio desynchronization, which seriously affects the user experience.

[0019] (2) Service isolation between slices fails, multicast service flows from different virtual operators are mixed in the same physical channel, and ONUs in non-target slices can receive multicast data from other operators, which cannot guarantee the security isolation of services between slices and the privacy of data.

[0020] (3) Waste of system resources and performance degradation: All ONUs receive and parse multicast messages from all slices indiscriminately, even if the message does not belong to its own slice, resulting in the ineffective consumption of ONU CPU, cache and other resources, reducing the overall multicast data transmission efficiency and equipment operation performance of the OLT slice system.

[0021] To address the aforementioned problems in multicast packet forwarding, this application provides a multicast packet processing method. In response to receiving a multicast data packet, an OLT slice encapsulates the multicast data packet to obtain a multicast data XGEM frame. The OLT device then broadcasts the multicast data XGEM frame to multiple Optical Network Units (ONUs) corresponding to that OLT device. This causes a target ONU device to forward the multicast data packet from the XGEM frame to its corresponding terminal device. The target ONU device's stored local multicast frame domain information matches the multicast frame domain information. This method achieves isolation of multicast services from different OLT slices at the ONU side, preventing ONU devices from invalidally parsing and forwarding multicast data packets from non-OLT slices, thus improving the isolation and service reliability of multicast services between slices.

[0022] Please see Figure 1 , Figure 1 A flowchart illustrating a multicast message processing method provided in some embodiments of this application is shown. This method can be implemented using a 10 gigabit symmetric rate passive optical network (10... Gigabit In a capable Symmetric Passive Optical Network (XGSPON network), OLT slicing is performed on the Optical Line Terminal (OLT) device, as shown in the figure. This method 100 may include the following steps: Step 110: In response to obtaining a multicast data packet, the multicast data packet is encapsulated to obtain a multicast data XGEM frame; wherein, the reserved field in the XGEM frame header of the multicast data XGEM frame is configured as multicast frame domain information, and the multicast frame domain information corresponds one-to-one with the OLT slice.

[0023] In one exemplary embodiment, such as Figure 2 As shown, in an XGSPON network OLT slicing scenario, a single Optical Line Terminal (OLT) device is virtualized into multiple independent OLT slices, namely OLT slice 1, OLT slice 2, and OLT slice 3. Each OLT slice corresponds to a different virtual network operator, independently carrying services and managing its subordinate ONU devices. For example, OLT slice 1 manages its subordinate ONU1-1 and ONU1-2, OLT slice 2 manages its subordinate ONU2-1 and ONU2-2, and OLT slice 3 manages its subordinate ONU3-1 and ONU3-2.

[0024] After multicast functionality is enabled on each OLT slice, the OLT device assigns independent, globally unique multicast frame field information to each OLT slice. For example, the OLT device assigns a unique, dedicated multicast frame field number, Multicast_Slice_ID, to each OLT slice to distinguish multicast data packets from different slices. The encoding rule for this multicast frame field information can be as follows: the dedicated multicast frame field number for OLT slice 1 is 001, for OLT slice 2 it is 010, and for OLT slice 3 it is 011. However, the dedicated multicast frame field number for each OLT slice is not limited to the above binary encoding and can also use other forms of identification information.

[0025] When any of the aforementioned OLT slices acquires a multicast data packet, it encapsulates the multicast data packet to obtain a multicast data XGEM frame. For example, the multicast data packet can be encapsulated into an XGEM frame; according to a preset mapping rule, the dedicated multicast frame field number corresponding to the OLT slice is filled into a reserved field in the XGEM frame header of the XGEM frame to obtain the multicast data XGEM frame.

[0026] Step 120: Broadcast multicast data XGEM frames through the OLT device to multiple optical network unit (ONU) devices corresponding to the OLT device, so that the target ONU device among the multiple ONU devices forwards the multicast data packets in the multicast data XGEM frames to the corresponding terminal devices. The local multicast frame domain information stored by the target ONU device matches the multicast frame domain information.

[0027] Continuing with the above embodiment, the OLT device can broadcast multicast data XGEM frames to multiple ONU devices corresponding to the OLT device via the public broadcast channel with Port-ID=4095. This public broadcast channel is a dedicated multicast public channel specified in the XG(S)PON standard, used for multicast data transmission across all slices.

[0028] Each ONU device receives multicast data XGEM frames broadcast by the OLT device, decapsulates the multicast data XGEM frames to obtain multicast frame domain information, and performs a matching verification between this multicast frame domain information and pre-stored local multicast frame domain information. When the multicast frame domain information matches the local multicast frame domain information, the multicast data packet in the multicast data XGEM frame is forwarded to the corresponding terminal device.

[0029] Through the above steps, the OLT device broadcasts multicast data XGEM frames encapsulated by each OLT slice. The ONU device compares its local multicast frame field information with the multicast frame field information carried in the multicast data XGEM frame. Only when the two match will the ONU device forward the multicast data packet to the corresponding terminal device. This method can isolate multicast services of different OLT slices on the ONU side, avoiding the ONU device from invalidally parsing and forwarding multicast data packets that do not belong to its OLT slice, thus improving the isolation and service reliability of multicast services between slices.

[0030] In some embodiments, step 110 above, encapsulating the multicast data packet to obtain a multicast data XGEM frame, includes: mapping multicast frame domain information to a reserved field in the XGEM frame header of the multicast data XGEM frame; and generating a multicast data XGEM frame based on the XGEM frame header mapped with multicast frame domain information and the multicast data packet.

[0031] In one exemplary embodiment, multicast data XGEM frames can be constructed according to the XGEM frame structure of the XG(S)PON standard. For example... Figure 3 As shown, an XGEM frame includes an XGEM frame header and an XGEM payload. The fields in the XGEM frame header include a payload length indication (PLI) [14 bits], a key index [2 bits], an XGEM port-ID [16 bits], options [18 bits], a last fragment identifier (LF) [1 bit], and a hybrid error correction check (HEC) [13 bits].

[0032] According to the preset mapping rules, the multicast frame domain information of the OLT slice, such as Multicast_Slice_ID, is mapped to a reserved field in the XGEM frame header. This reserved field can be the Options field. According to the XG(S)PON standard, the Options field is fixed at 18 bits, and by default, it is set to 0x00000. The sender sets it to 0 by default, and the receiver ignores this field. The preset mapping rules include at least one of the following: (1) Directly map Multicast_Slice_ID to the Options field. The mapping process does not affect the normal function of other fields in the XGEM frame header, ensuring the normal encapsulation of multicast data.

[0033] For example, if the Multicast_Slice_ID is designed to be 18 bits long, it perfectly matches the standard length (18 bits) of the Options field. The 18-bit Multicast_Slice_ID can be directly mapped to the 18-bit Options field without segmenting the Options field or modifying its original structure. The specific mapping rule is: bits 1 through 18 of the Options field directly correspond to bits 1 through 18 of the Multicast_Slice_ID.

[0034] (2) The mapping method of "direct mapping + padding with zeros in the high bits" is adopted.

[0035] For example, if the actual number of valid bits in the Multicast_Slice_ID is less than 18 bits, it is padded with 0s in its high bits to ensure that the 18-bit Options field is filled. Figure 2 Taking the OLT slices in the network scenario shown as an example, the Multicast_Slice_ID corresponding to OLT slice 1 is 001 (binary, 3 bits). When mapped to the Options field, 15 zeros are padded to the high bits, and the final 18-bit value of the Options field is 000000000000000001 (binary), which corresponds to 0x00001 in hexadecimal. The Multicast_Slice_ID corresponding to OLT slice 2 is 010 (binary), and after mapping, the Options field is 0000000000000000010 (binary), which corresponds to 0x00002 in hexadecimal. The Multicast_Slice_ID of OLT slice 3 is 011 (binary), and after mapping, the Options field is 000000000000000011 (binary), which corresponds to 0x00003 in hexadecimal.

[0036] The mapping method described above is simple and efficient, does not affect the normal function of other fields such as PLI, Key index, and XGEM port-ID in the XGEM frame header, and is completely consistent with the parsing and verification logic on the ONU side, ensuring the normal encapsulation and recognition of multicast data packets.

[0037] Based on the XGEM frame header and multicast data packet with multicast frame domain information mapped above, a multicast data XGEM frame is generated.

[0038] It should be noted that the multicast message processing method described above applies only to XG(S)PON networks. For example... Figure 4 As shown, in a GPON network, the GEM frame header structure is a fixed 5 bytes (40 bits), containing only PLI (12 bits), GEMPort-ID (12 bits), PTI (3 bits), and HEC (13 bits), without a reserved Options extension field. Therefore, it is impossible to carry multicast frame domain information in a similar way. Furthermore, the multicast public broadcast channel GEMPort-ID defined by the GPON standard is fixed at 4095. Attempting to carry multicast frame domain information by extending GEMPort-ID would conflict with the GPON protocol standard. The GPON protocol explicitly stipulates that a unique Port-ID should be used to transmit multicast services in GEM mode. The aforementioned method of extending GEMPort-ID does not conform to the standard definition and cannot guarantee the compatibility and interoperability of standard equipment.

[0039] By following the steps above, ONU devices can quickly identify the OLT slice to which multicast data packets belong without extending the GEMPort-ID or increasing packet encapsulation overhead. This avoids ONU devices invalidally parsing and forwarding multicast data packets that do not belong to the OLT slice. Simultaneously, it ensures protocol compatibility and interoperability of OLT devices.

[0040] In some embodiments, before encapsulating the multicast data packet to obtain the multicast data XGEM frame in step 110 above, the method further includes: obtaining the multicast frame domain information allocated by the OLT device for the OLT slice, wherein the OLT device is used to allocate corresponding multicast frame domain information for each OLT slice and maintain the mapping relationship between each OLT slice and the corresponding multicast frame domain information.

[0041] In an exemplary embodiment, an XG(S)PON OLT device is deployed in an XGSPON network. Using virtualized resource partitioning technology, multiple independent OLT slices are configured on this OLT device to ensure complete isolation of services and resources between each slice system, preventing interference and providing a foundation for the independent operation of subsequent multicast services. The OLT device assigns corresponding multicast frame domain information to each OLT slice and maintains the mapping relationship between each OLT slice and its corresponding multicast frame domain information. For example, the physical OLT device establishes and maintains a mapping table between OLT slices and Multicast_Slice_ID locally, uniformly managing the multicast frame domain information of all OLT slices to ensure that the multicast frame domain information of different slices does not conflict, facilitating accurate identification of subsequent multicast data.

[0042] OLT slicing completes the encapsulation of multicast data packets and generates multicast data XGEM frames by obtaining the multicast frame domain information allocated by the OLT device for the OLT slice.

[0043] In some embodiments, the above method may further include the following steps: Step 130: In response to the OLT slice listening to the registration message sent by the target ONU device, a multicast dedicated channel is established between the target ONU device and the OLT slice based on the target port identifier, wherein the target port identifier is used to indicate a predetermined port in a predefined set of public multicast ports.

[0044] In some embodiments, after each OLT slice is started, it continuously monitors the registration messages of ONU devices within its jurisdiction, prepares for the ONU devices to go online, and ensures that it can respond to the registration requests of ONUs in a timely manner. Through the joint registration process of the Optical Network Unit Management and Control Interface (OMCI) and Physical Layer Operations, Administration and Maintenance (PLOAM) specified in the XG(S)PON standard, the ONU device reports a registration message to the OLT device. This registration message may include the ONU device's serial number, hardware capabilities, service requirements, etc., to complete the submission of the initial registration request.

[0045] After the OLT slice of the OLT device listens to the registration message sent by the target ONU device, it establishes a dedicated multicast channel between the target ONU device and the OLT slice based on the target port identifier. For example, there are 4096 public multicast channels corresponding to ports in the predefined set of public multicast ports. The public multicast channel corresponding to a predetermined port, such as the 4095th public multicast channel (Port-ID=4095), is assigned to the dedicated multicast channel. This dedicated multicast channel adopts the dedicated multicast channel specified in the XG(S)PON standard and is associated with the public broadcast channel of Port-ID=4095 for the distribution of multicast data.

[0046] Step 140: Send a multicast configuration message to the target ONU device through the multicast dedicated channel. The multicast configuration message includes multicast frame domain information and is used to instruct the target ONU device to store the multicast frame domain information as local multicast frame domain information.

[0047] Continuing with the above embodiments, the OLT device sends a multicast configuration message multicast_field_notice_message to the target ONU device under the jurisdiction of the OLT slice via the dedicated multicast channel in a unicast manner. The multicast configuration message includes multicast frame field information Multicast_Slice_ID. This multicast configuration message is used to instruct the target ONU device to store the multicast frame field information as local multicast frame field information.

[0048] By following the steps above, it can be ensured that the target ONU device can receive the multicast data packets corresponding to the OLT slice, thereby improving the reliability of multicast data packet forwarding.

[0049] In some embodiments, in step 130 above, establishing a dedicated multicast channel between the ONU device and the OLT slice based on a preset public multicast port identifier includes: performing identity authentication and permission verification on the target ONU device according to a preset slice partitioning strategy and ONU affiliation rules; and in response to successful identity authentication and permission verification, establishing a dedicated multicast channel between the target ONU device and the OLT slice based on the target port identifier.

[0050] In one exemplary embodiment, the OLT slice performs identity authentication and permission verification on the target ONU device according to a preset slice allocation strategy and ONU affiliation rules. For example, based on the preset slice allocation strategy and ONU affiliation rules, it determines whether the target ONU device belongs to the OLT slice and whether the target ONU device has the necessary permissions. When identity authentication and permission verification pass, a dedicated multicast channel is established between the target ONU device and the OLT slice based on the target port identifier.

[0051] Through the above steps, OLT slicing establishes a dedicated multicast channel only for target ONU devices that have passed identity authentication and permission verification. This achieves isolation of inter-device multicast services while ensuring device interoperability, thereby improving the service reliability of multicast services.

[0052] In some embodiments, after sending the multicast configuration message to the target ONU device in step 140 above, the method further includes: receiving a response message returned by the target ONU device through the OLT device, the response message being used to indicate that the target ONU device has stored the multicast frame domain information as local multicast frame domain information; and marking the multicast configuration status of the target ONU device as a target status, the target status being used to indicate that the multicast frame domain information of the ONU device has been configured.

[0053] In one exemplary embodiment, the ONU device receives a multicast configuration message sent by the OLT device, parses the multicast configuration message, extracts the multicast frame field information, and stores the multicast frame field information locally to obtain local multicast frame field information, preparing for the verification of subsequent multicast data packets. After the target ONU device has stored the multicast frame field information as local multicast frame field information, it constructs a response message multicast_field_register_ack and unicasts it back to the OLT device through the multicast dedicated channel to inform the OLT device that it has successfully received and stored the multicast frame field information, completing the interactive confirmation of configuration information.

[0054] The OLT device receives a response message from the target ONU device and marks the multicast configuration status of the target ONU device as the target status. This target status indicates that the multicast frame domain information of the ONU device has been configured successfully. For example, the OLT device marks the multicast configuration status of the target ONU device as "completed" in the local slice management table.

[0055] In some possible implementations, the OLT device can also verify the validity of the response message after receiving it from the target ONU device.

[0056] By following the steps above, the multicast service status of the ONU device can be determined based on the multicast configuration status, thereby accurately controlling the multicast services for the ONU device and ensuring that the ONU device can normally receive multicast data packets from the OLT slice.

[0057] In some embodiments, step 110 above, obtaining multicast data packets and encapsulating the multicast data packets to obtain multicast data XGEM frames, includes: listening to Internet Group Management Protocol (IGMP) join messages sent by the target ONU device, wherein the IGMP join message includes multicast source identification information; initiating a multicast subscription request to the multicast source indicated by the multicast source identification information, obtaining multicast data packets sent by the multicast source; and encapsulating the multicast data packets to generate multicast data XGEM frames.

[0058] In one exemplary embodiment, the OLT slice initiates the Internet Group Management Protocol (IGMP) to add message listening functionality, thereby capturing multicast subscription requests reported by the ONU devices under its jurisdiction in real time and preparing for the distribution of multicast data.

[0059] When an ONU device has a multicast program on-demand request, it generates an IGMP join message. This IGMP join message explicitly carries multicast source identification information, including key information such as the source IP address of the required multicast and the multicast Virtual Local Area Network (VLAN). The IGMP join message is then reported to the corresponding OLT slice through an established dedicated multicast channel, initiating a multicast subscription request.

[0060] After receiving the IGMP join message, the OLT slice parses the message, extracts the multicast source identifier information, and confirms the multicast subscription request of the target ONU device. The OLT slice then initiates a multicast subscription request to the multicast source indicated by the multicast source identifier information, obtains the multicast data packets sent by the multicast source, and encapsulates the multicast data packets to generate multicast data XGEM frames.

[0061] Through the above steps, the OLT slice only needs to obtain the corresponding multicast data packets from the multicast source subscribed to by the ONU device when the ONU device initiates an IGMP join message. This enables on-demand acquisition and encapsulation of multicast data packets, saving data transmission resources and achieving precise control of multicast services.

[0062] In some embodiments, after initiating a multicast subscription request to the multicast source indicated by the multicast source identification information, the method further includes: adding the target ONU device to the multicast member list of the corresponding OLT slice, and recording the multicast subscription information and multicast group context information of the target ONU device.

[0063] In one exemplary embodiment, the OLT slice adds the ONU to the dynamic member list of the corresponding multicast, and records the multicast subscription information such as the ONU's interface information, slice information, and subscription time to complete the multicast subscription registration. If this multicast group is the first subscription request received by the OLT slice system, multicast group context information for the multicast group is created within the slice, recording multicast stream parameters and member list information.

[0064] Through the above steps, the OLT slice can accurately identify the multicast subscription permissions of the target ONU, ensuring the accurate delivery of multicast data packets. Furthermore, by recording multicast subscription information and multicast group context information, traceable control of multicast status is achieved, enabling refined management of multicast services.

[0065] Please see Figure 5 , Figure 5 A flowchart illustrating a multicast message processing method provided in other embodiments of this application is shown. This method can be executed by an ONU device in an XGSPON network. As shown in the figure, method 500 may include the following steps: Step 510: Obtain the multicast data XGEM frame broadcast by the optical line terminal (OLT) device in the XGSPON network, decapsulate the multicast data XGEM frame, and obtain the multicast frame domain information; wherein, the multicast data XGEM frame is obtained by encapsulating the multicast data packet by the OLT slice of the OLT device; the reserved field in the XGEM frame header of the multicast data XGEM frame is configured as multicast frame domain information, and the multicast frame domain information corresponds one-to-one with the OLT slice.

[0066] In one exemplary embodiment, the ONU device can receive multicast data XGEM frames in broadcast form from the Port-ID=4095 channel via its own PON interface. These multicast data XGEM frames are broadcast by the optical line terminal (OLT) device in the XGSPON network.

[0067] The received multicast data XGEM frames are decapsulated to obtain multicast frame domain information. Specifically, the OLT device can extract reserved fields from the XGEM frame header of the multicast data XGEM frame, such as the Options field (18 bits). Following a preset mapping rule, the multicast frame domain information carried in this field is read, such as the Multicast_Slice_ID mentioned above.

[0068] Step 520: In response to the matching of local multicast frame domain information and multicast frame domain information, the multicast data packet obtained by decapsulating the multicast data XGEM frame is forwarded to the terminal device.

[0069] Continuing with the above embodiment, the OLT device reads the locally stored local multicast frame domain information and performs a matching verification between this local multicast frame domain information and the extracted multicast frame domain information. If the local multicast frame domain information matches the multicast frame domain information, the multicast data packet obtained by decapsulating the multicast data XGEM frame is forwarded to the terminal device, ensuring that the user can normally browse multicast content through the terminal device.

[0070] Through the above steps, when the local multicast frame domain information stored in the ONU device matches the multicast frame domain information, the multicast data packets obtained by decapsulating the multicast data XGEM frames are forwarded to the terminal device. This can prevent the ONU device from invalidally parsing and forwarding multicast data packets that do not belong to the OLT slice, thereby improving the isolation and service reliability of multicast services between slices.

[0071] In some embodiments, after obtaining the multicast frame domain information in step 510 above, the method further includes: In response to the mismatch between local multicast frame domain information and multicast frame domain information, multicast data XGEM frames are discarded.

[0072] In one exemplary embodiment, the OLT device reads locally stored local multicast frame domain information and performs a matching verification between the local multicast frame domain information and the extracted multicast frame domain information. If the local multicast frame domain information and the multicast frame domain information cannot match, the multicast data XGEM frame is discarded, and no subsequent parsing and forwarding operations on the multicast data packet are performed.

[0073] By following the steps above, invalid data can be prevented from consuming system resources, ensuring the normal operation of multicast services.

[0074] In some embodiments, the method further includes: sending a registration message to the OLT slice; obtaining a multicast configuration message sent by the OLT device through a multicast dedicated channel, wherein the multicast configuration message includes multicast frame domain information of the ONU device corresponding to the OLT slice, the multicast dedicated channel being a channel established between the ONU device and the OLT slice based on a target port identifier, the target port identifier being used to indicate a predetermined port in a predefined set of public multicast ports; and storing the multicast frame domain information as local multicast frame domain information.

[0075] By following the steps above, it can be ensured that the target ONU device can receive the multicast data packets corresponding to the OLT slice, thereby improving the reliability of multicast data packet forwarding.

[0076] In some embodiments, after storing the multicast frame domain information as local multicast frame domain information as described above, the method further includes: sending a response message to the OLT device, the response message being used to indicate that the ONU device has stored the multicast frame domain information as local multicast frame domain information.

[0077] By following the steps above, the OLT device can determine the multicast service status of the ONU device based on the response message, thereby accurately controlling the multicast service for that ONU device.

[0078] In some embodiments, before obtaining the multicast data XGEM frame broadcast by the Optical Line Terminal (OLT) device in the XGSPON network in step 510 above, the method further includes: sending an Internet Group Management Protocol (IGMP) join message to the OLT device, wherein the IGMP join message includes multicast source identification information.

[0079] By following the steps above, multicast data packets can be acquired and encapsulated on demand, saving data transmission resources and enabling precise control of multicast services.

[0080] In one exemplary embodiment, such as Figure 6 As shown, the multicast message processing method described above may include the following steps: Step 610: The ONU device sends a registration message to the OLT slice and obtains the multicast configuration message sent by the OLT device through the multicast dedicated channel. The multicast configuration message includes the multicast frame domain information of the ONU device corresponding to the OLT slice. The multicast frame domain information is stored as local multicast frame domain information.

[0081] Step 620: The ONU device sends an IGMP join message to the OLT device.

[0082] Step 630: The ONU device acquires the multicast data XGEM frame broadcast by the OLT device.

[0083] Step 640: Determine whether the local multicast frame domain information matches the multicast frame domain information. If the local multicast frame domain information matches the multicast frame domain information, proceed to step 650; otherwise, proceed to step 660.

[0084] Step 650: Forward the multicast data packets obtained by decapsulating the multicast data XGEM frames to the terminal device.

[0085] Step 660: Discard the multicast data packets obtained by decapsulating the multicast data XGEM frames.

[0086] In this embodiment, when the local multicast frame domain information stored by the ONU device matches the multicast frame domain information, the multicast data packet obtained by decapsulating the multicast data XGEM frame is forwarded to the terminal device; when the local multicast frame domain information and the multicast frame domain information cannot match, the multicast data packet obtained by decapsulating the multicast data XGEM frame is discarded. This avoids the ONU device from invalidally parsing and forwarding multicast data packets that do not belong to its OLT slice, improving the isolation and service reliability of multicast services between slices.

[0087] Please see Figure 7 , Figure 7 The figure shows a flowchart illustrating a method for collaborative processing of OLT slices and ONU-side multicast services in an XG(S)PON network according to some embodiments of this application. As shown in the figure, the method may include the following steps: Step 710: Configure multiple independent OLT slices on the OLT device in the XGSPON network, and assign a corresponding exclusive multicast frame field number (i.e., the multicast frame field information mentioned above) to each OLT slice.

[0088] Step 720: The OLT slice listens for the registration message sent by the ONU device and completes the ONU registration and online process. For example, taking the target OLT slice in the OLT device as an example... Figure 8 As shown, the collaborative processing method includes: 720-1, the OLT device receives a registration message sent by the ONU device under the jurisdiction of the target OLT slice. The registration message includes the ONU device's device serial number, hardware capabilities, etc. Optionally, 720-2, the OLT device can also authenticate the ONU device, and when the authentication is successful, send an authentication response to the ONU device.

[0089] Step 730: Establish a dedicated multicast channel between the ONU device and the OLT slice, and send a dedicated multicast frame field number to the ONU device through this channel. For example, such as... Figure 8 As shown, the above collaborative processing method further includes: 730-1, establishing a dedicated multicast channel; 730-2, sending a multicast_field_notice_message (i.e., the multicast configuration message mentioned above) through this channel, which includes a Multicast_Slice_ID (i.e., the multicast frame field information mentioned above); 730-3, the ONU device parses the multicast configuration message, extracts the Multicast_Slice_ID, and stores it in its local register; 730-4, the ONU device sends a multicast_field_register_ack (i.e., the response message mentioned above) to the OLT device, informing it that the multicast frame field information has been configured; 730-5, marking the multicast configuration status of the ONU device as "completed".

[0090] Step 740: Listen for information sent by the ONU device.

[0091] Step 750: Determine whether an IGMP join message has been detected. If an IGMP join message has been detected, proceed to step 760; otherwise, return to step 740 above.

[0092] Step 760: Add the ONU device to the multicast member list of the corresponding OLT slice. For example, such as... Figure 8As shown, the above collaborative processing method further includes: 760-1, the ONU device sends an IGMP join message to the OLT device, the IGMP join message including the multicast source IP address, multicast VLAN, etc.; 760-2, the OLT device parses the message and adds the ONU device to the multicast member list (if it is the first time it is received, a multicast context is created); optionally, it also includes: 760-3, the OLT device sends an IGMP response message to the ONU device to indicate that the subscription was successful.

[0093] Step 770: The OLT slice broadcasts multicast data XGEM frames via a dedicated multicast channel. For example, as shown... Figure 8 As shown, the above collaborative processing method also includes: 770-1, obtaining multicast data packets sent by the multicast source; 770-2, constructing a multicast data XGEM frame and filling the Multicast_Slice_ID into the Options field (i.e., the reserved field mentioned above); 770-3, broadcasting the multicast data XGEM frame through the Port-ID=4095 channel.

[0094] Step 780: The ONU device receives downlink broadcast multicast data XGEM frames. For example, as shown... Figure 8 As shown, the above collaborative processing method also includes: 780-1, the ONU device decapsulates the multicast data XGEM frame and extracts the Multicast_Slice_ID from the Options field.

[0095] Step 790: Determine whether the local multicast frame domain information matches the multicast frame domain information. If the local multicast frame domain information matches the multicast frame domain information, proceed to step 7100; otherwise, proceed to step 7110. For example, such as... Figure 8 As shown, the above collaborative processing method also includes: 790-1, matching and verifying Multicast_Slice_ID with local multicast frame domain information.

[0096] Step 7100: Forward the multicast data packets obtained by decapsulating the multicast data XGEM frames to the terminal device. For example, such as... Figure 8 As shown, the above collaborative processing method also includes: 7100-1, if the field numbers match, then parse the multicast data packet and forward the parsed multicast data packet to the terminal device.

[0097] Step 7110: Discard the multicast data packets obtained by decapsulating the multicast data XGEM frames. For example... Figure 8 As shown, the above collaborative processing method also includes: 7110-1, if the field number does not match, the multicast data packet is discarded.

[0098] Through the above steps, ONUs under different OLT slices under the same physical PON port can accurately identify the multicast data stream of their respective slices. Even if different slices use the same MVLAN and the same multicast group address, the problems of repeated reception, incorrect reception, or random reception of multicast packets from non-Original operators can be avoided. This enables ONUs to receive and filter multicast packets on demand, significantly improving the multicast data transmission efficiency, isolation, and overall system performance of the OLT slice system.

[0099] In another exemplary embodiment, with Figure 2 Taking the OLT slicing networking scenario of the XGSPON network shown as an example, the above multicast packet processing method will be explained. Figure 2 As shown, the network environment comprises three independent OLT slices: OLT slice 1, OLT slice 2, and OLT slice 3. All three OLT slice systems are deployed on the same physical XG(S)PON OLT device. Virtualization resource partitioning technology achieves complete isolation of services and resources, ensuring no interference between them. Specifically, OLT slice 1 has two ONU devices: ONU1-1 and ONU1-2; OLT slice 2 has two ONU devices: ONU2-1 and ONU2-2; and OLT slice 3 has two ONU devices: ONU3-1 and ONU3-2.

[0100] All the aforementioned OLT slices and their associated ONU devices support the multicast message processing mechanism described in this application embodiment, and are capable of receiving, storing, verifying, and filtering / forwarding multicast message fields for dedicated multicast frame field numbers. For example, the multicast message processing method includes the following steps: Step 910: After multicast functionality is enabled for each OLT slice system, the OLT device assigns an independent, globally unique multicast frame field number (Multicast_Slice_ID) to each OLT slice system based on the locally maintained mapping table between OLT slices and dedicated multicast frame field numbers. After allocation, the physical OLT device updates the slice-field number mapping table, recording the dedicated multicast frame field number corresponding to each slice system for quick lookup during subsequent multicast data encapsulation and verification.

[0101] Step 920: Each OLT slice system sends the configuration information of its own multicast frame field number (multicast_field_notice_message) to each ONU device under its jurisdiction via the PLOAM channel in a unicast manner. After receiving the configuration message, each ONU device parses the message, extracts the exclusive multicast frame field number carried in it, and stores the field number in the local preset multicast_field_key_register register to complete the local solidification storage of the field number, providing a basis for subsequent multicast message ownership verification.

[0102] Step 930: After each OLT slice completes the distribution of its dedicated multicast frame field number and ONU configuration, it immediately starts the IGMP join message listening function to continuously capture the IGMP join messages reported by the ONU devices under its jurisdiction and monitor the multicast subscription needs of each ONU in real time to ensure timely response to the multicast on-demand requests of the ONUs and prepare for the accurate distribution of multicast data.

[0103] Step 940: When the multicast monitoring module of OLT slice 1 receives the IGMP join message sent by its subordinate ONU1-2, it parses the IGMP join message and extracts the multicast-related parameters carried in the message. Assuming that the multicast VLAN (MVLAN) corresponding to ONU1-2 is 4000, the multicast group address is 225.0.0.1, and the multicast source IP is 192.168.1.100, after OLT slice 1 confirms the multicast subscription request of ONU1-2, it adds the corresponding PON interface of ONU1-2 to the multicast member list of the multicast group (multicast group address 225.0.0.1, MVLAN 4000) of OLT slice 1, and records the interface identifier, home slice ID (OLT slice 1), and subscription time of ONU1-2, the registration of multicast subscription is completed, ensuring that subsequent multicast data can be accurately delivered to ONU1-2.

[0104] Step 950: After receiving the original multicast data packet from the multicast source corresponding to the multicast group (225.0.0.1, MVLAN4000), OLT slice 1 constructs an XGEM multicast frame according to the encapsulation process described in this invention. After encapsulation, OLT slice 1 broadcasts the multicast data packet to all its subordinate ONU devices (ONU1-1, ONU1-2) through the public multicast Port-ID=4095 channel specified by the XG(S)PON standard. Since Port-ID=4095 is a global public broadcast channel, the multicast data packet will also be broadcast synchronously to the ONU devices (ONU2-1, ONU2-2, ONU3-1, ONU3-2) of other slices under the same physical PON port.

[0105] Step 960: After receiving the multicast data packet through its own PON interface, ONU1-2 decapsulates the packet, extracts the 18-bit Options field from the XGEM frame header, extracts the dedicated multicast frame field number carried in the field, and performs a matching and verification with the dedicated multicast frame field number (001) of OLT slice 1 stored in the local multicast_field_key_register register.

[0106] Step 970: When the multicast monitoring module of OLT slice 3 receives the IGMP join message sent by its subordinate ONU3-1, it parses the message and extracts the multicast parameters. Assuming that its corresponding multicast VLAN (MVLAN) is 4000 and the multicast group address is 225.0.0.1, which is completely consistent with the multicast program parameters subscribed by ONU1-2 in OLT slice 1, after OLT slice 3 confirms the multicast subscription request of ONU3-1, it adds the corresponding PON interface of ONU3-1 to the dynamic member list of the multicast group (225.0.0.1, MVLAN4000) of OLT slice 3, and records the interface identifier, home slice ID and subscription time of ONU3-1.

[0107] Step 980: After receiving the original multicast data packet from the multicast source corresponding to the multicast group (225.0.0.1, MVLAN4000), OLT slice 3 constructs a multicast data XGEM frame, maps its own exclusive multicast frame field number (011) to the 18-bit Options field of the XGEM frame header, and after encapsulation, OLT slice 3 broadcasts the multicast data packet to its subordinate ONU devices (ONU3-1, ONU3-2) through the public multicast Port-ID=4095 channel. The packet will also be broadcast to ONU devices (ONU1-1, ONU1-2, ONU2-1, ONU2-2) in other slices under the same physical PON port.

[0108] Step 990: After receiving the multicast message from OLT slice 3 via the public multicast channel Port-ID=4095 through the PON interface, ONU1-2 decapsulates the message, extracts the dedicated multicast frame field number (011) from the Options field of the XGEM frame header, and performs a matching verification with the dedicated multicast frame field number (001) of OLT slice 1 stored in the local multicast_field_key_register register. Since the two are inconsistent, ONU1-2 determines that the multicast message is not a multicast message. Invalid packets sent by its own slice are directly discarded without any subsequent parsing, caching, or forwarding operations. This avoids invalid data consuming its own CPU, cache, and other resources, while ensuring the isolation of multicast services between slices. After receiving the multicast packet, ONU3-1 also extracts the exclusive multicast frame field number (011) from the Options field and matches it with the field number (011) stored in the local register. Since they match, ONU3-1 receives the multicast packet normally, performs subsequent multicast IP, MVLAN, and payload parsing on the packet, and forwards the parsed multicast data to the terminal device, ensuring that the user can watch the multicast program normally.

[0109] The above steps can effectively solve the problem of packet confusion under the same multicast parameters for multiple slices, achieve strong isolation of multicast services between slices, and avoid problems such as service lag and resource waste caused by duplicate packets.

[0110] This application embodiment also provides an OLT device, including a processor and a memory, wherein the memory stores programs or instructions that can run on the processor, and the programs or instructions, when executed by the processor, implement... Figure 1 The steps of the method described in the illustrated embodiment.

[0111] This application embodiment also provides an ONU device, including a processor and a memory, wherein the memory stores programs or instructions that can run on the processor, and the programs or instructions, when executed by the processor, implement... Figure 5 The steps of the method described in the illustrated embodiment.

[0112] Figure 9The diagram illustrates the hardware structure of a network device implementing some embodiments of this application. Referring to the diagram, at the hardware level, the network device 900 includes a processor 910, and optionally includes an internal bus 920, a network interface 930, and a memory. The memory may include main memory 941, such as high-speed random-access memory (RAM), and may also include non-volatile memory 942, such as at least one disk storage device. Of course, the network device 900 may also include other hardware required for other services.

[0113] The processor 910, network interface 930, and memory can be interconnected via an internal bus 920. This internal bus 920 can be an Advanced Microcontroller Bus Architecture (AMIC) bus, a Wishbone bus, an Open Core Protocol (OCP) bus, an Avalon bus, etc. The bus can be categorized as an address bus, data bus, control bus, etc. For ease of illustration, only a single bidirectional arrow is used in this diagram, but this does not imply that there is only one bus or one type of bus.

[0114] The memory stores programs. Specifically, the program may include program code, which includes computer operation instructions. The memory may include main memory 941 and non-volatile memory 942, and provides instructions and data to the processor 910.

[0115] The processor 910 reads the corresponding computer program from the non-volatile memory 942 into memory and then runs it, forming a device for locating the target user at the logical level. The processor 910 executes the program stored in memory and specifically performs the following: Figure 1 or Figure 5 or Figure 6 or Figure 7 The methods disclosed in the embodiments shown achieve the functions and beneficial effects of the methods described in the preceding method embodiments, and will not be repeated here.

[0116] The above is as stated in this application. Figure 1 or Figure 5 or Figure 6 or Figure 7The methods disclosed in the illustrated embodiments can be applied to or implemented by processor 910. Processor 910 may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above methods can be completed by integrated logic circuits in the hardware or by instructions in software form within processor 910. Processor 910 can be a general-purpose processor, including a Central Processing Unit (CPU), a Network Processor (NP), etc.; it can also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field-Programmable Gate Array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software module can reside in a mature storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, or registers. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method.

[0117] The network device 900 can also execute the methods described in the preceding method embodiments and achieve the functions and beneficial effects of the methods described in the preceding method embodiments, which will not be repeated here.

[0118] Of course, in addition to software implementation, the network device 900 of this application does not exclude other implementation methods, such as logic devices or a combination of hardware and software, etc. In other words, the execution subject of the following processing flow is not limited to each logic unit, but can also be hardware or logic devices.

[0119] This application also proposes a computer-readable storage medium that stores one or more programs, which, when executed by a network device including multiple applications, cause the network device to perform... Figure 1 or Figure 5 or Figure 6 or Figure 7 The methods disclosed in the embodiments shown achieve the functions and beneficial effects of the methods described in the preceding method embodiments, and will not be repeated here.

[0120] The computer-readable storage medium mentioned above includes read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk, etc.

[0121] Furthermore, embodiments of this application also provide a computer program product, the computer program product including a computer program stored on a non-transitory computer-readable storage medium, the computer program including program instructions, which, when executed by a computer, implement the following process: Figure 1 or Figure 5 or Figure 6 or Figure 7 The methods disclosed in the embodiments shown achieve the functions and beneficial effects of the methods described in the preceding method embodiments, and will not be repeated here.

[0122] In summary, the above description is merely a preferred embodiment of this application and does not limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application.

[0123] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information by any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0124] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0125] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to interchangeably. Each embodiment focuses on describing the differences from other embodiments. In particular, the system embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions in the method embodiments.

Claims

1. A multicast message processing method, characterized in that, OLT slicing applied to Optical Line Terminal (OLT) equipment in an XGSPON network, the method comprising: In response to the acquisition of a multicast data packet, the multicast data packet is encapsulated to obtain a multicast data XGEM frame; wherein, the reserved field in the XGEM frame header of the multicast data XGEM frame is configured as multicast frame domain information, and the multicast frame domain information corresponds one-to-one with the OLT slice. The multicast data XGEM frame is broadcast by the OLT device to multiple optical network unit (ONU) devices corresponding to the OLT device, so that the target ONU device among the multiple ONU devices forwards the multicast data packets in the multicast data XGEM frame to the corresponding terminal device, and the local multicast frame domain information stored by the target ONU device matches the multicast frame domain information.

2. The method according to claim 1, characterized in that, The process of encapsulating the multicast data packets to obtain multicast data XGEM frames includes: The multicast frame domain information is mapped to the reserved field in the XGEM frame header of the multicast data XGEM frame; A multicast data XGEM frame is generated based on the XGEM frame header mapped with the multicast frame domain information and the multicast data packet.

3. The method according to claim 1, characterized in that, Before encapsulating the multicast data packet to obtain a multicast data XGEM frame, the method further includes: Obtain the multicast frame domain information allocated by the OLT device to the OLT slice, wherein the OLT device is used to allocate corresponding multicast frame domain information to each OLT slice and maintain the mapping relationship between each OLT slice and the corresponding multicast frame domain information.

4. The method according to claim 1, characterized in that, Also includes: In response to the OLT slice listening to the registration message sent by the target ONU device, a multicast dedicated channel is established between the target ONU device and the OLT slice based on the target port identifier, wherein the target port identifier is used to indicate a predetermined port in a predefined set of public multicast ports; Through the dedicated multicast channel, a multicast configuration message is sent to the target ONU device. The multicast configuration message includes the multicast frame domain information and is used to instruct the target ONU device to store the multicast frame domain information as local multicast frame domain information.

5. The method according to claim 4, characterized in that, The establishment of a dedicated multicast channel between the ONU device and the OLT slice based on the target port identifier includes: Based on the preset slicing strategy and ONU affiliation rules, the target ONU device is authenticated and its permissions are verified. In response to the successful authentication and authorization verification, a dedicated multicast channel is established between the target ONU device and the OLT slice based on the target port identifier.

6. The method according to claim 4, characterized in that, After sending the multicast configuration message to the target ONU device, the method further includes: The OLT device receives a response message returned by the target ONU device, the response message indicating that the target ONU device has stored the multicast frame field information as local multicast frame field information; The multicast configuration status of the target ONU device is marked as the target status, which indicates that the multicast frame domain information of the ONU device has been configured.

7. The method according to claim 1, characterized in that, The process of acquiring multicast data packets and encapsulating them to obtain multicast data XGEM frames includes: Monitor the Internet Group Management Protocol (IGMP) join message sent by the target ONU device, wherein the IGMP join message includes multicast source identification information; Initiate a multicast subscription request to the multicast source indicated by the multicast source identifier information, and obtain multicast data packets sent by the multicast source; The multicast data packets are encapsulated to generate multicast data XGEM frames.

8. The method according to claim 7, characterized in that, After initiating a multicast subscription request to the multicast source indicated by the multicast source identifier information, the method further includes: Add the target ONU device to the multicast member list of the corresponding OLT slice, and record the multicast subscription information and multicast group context information of the target ONU device.

9. A multicast message processing method, characterized in that, The method, applied to ONU devices in an XGSPON network, includes: The XGEM frames broadcast by the Optical Line Terminal (OLT) devices in the XGSPON network are obtained, and the XGEM frames are decapsulated to obtain multicast frame domain information. The XGEM frames are obtained by encapsulating multicast data packets into OLT slices of the OLT devices. Reserved fields in the XGEM frame header of the XGEM frames are configured as the multicast frame domain information, which corresponds one-to-one with the OLT slices. In response to the local multicast frame domain information matching the multicast frame domain information, the multicast data packet obtained by decapsulating the multicast data XGEM frame is forwarded to the terminal device.

10. The method according to claim 9, characterized in that, After obtaining the multicast frame domain information, the process also includes: In response to the fact that the local multicast frame domain information and the multicast frame domain information cannot be matched, the multicast data XGEM frame is discarded.

11. The method according to claim 9, characterized in that, Also includes: Send a registration message to the OLT slice; Obtain the multicast configuration message sent by the OLT device through the multicast dedicated channel. The multicast configuration message includes the multicast frame domain information of the OLT slice corresponding to the ONU device. The multicast dedicated channel is a channel established between the ONU device and the OLT slice based on the target port identifier. The target port identifier is used to indicate a predetermined port in a predefined set of public multicast ports. The multicast frame domain information is stored as local multicast frame domain information.

12. The method according to claim 11, characterized in that, After storing the multicast frame domain information as local multicast frame domain information, the method further includes: A response message is sent to the OLT device, the response message being used to indicate that the ONU device has stored the multicast frame field information as local multicast frame field information.

13. The method according to claim 9, characterized in that, Before acquiring the multicast data XGEM frames broadcast by the optical line terminal (OLT) device in the XGSPON network, the method further includes: Send an Internet Group Management Protocol (IGMP) join message to the OLT device, the IGMP join message including multicast source identification information.

14. An OLT device, characterized in that, It includes a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions being executed by the processor to implement the steps of the method as claimed in any one of claims 1 to 9.

15. An ONU device, characterized in that, It includes a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions being executed by the processor to implement the steps of the method as described in any one of claims 10 to 13.

16. A computer program product, characterized in that, The computer program product includes a computer program stored on a non-transitory computer-readable storage medium, the computer program including program instructions that, when executed by a computer, cause the computer to perform the steps of the method as described in any one of claims 1 to 13.

Images