Controllable multicast implementation method based on FTTR P2MP scheme, operating system, terminal and storage medium

By extending the OMCI protocol, the controllable multicast function of the FTTR network is realized, which solves the problem that traditional multicast cannot meet high security needs, improves the security and control of multicast services, and is suitable for intelligent manufacturing and commercial application scenarios.

CN118984297APending Publication Date: 2024-11-19SICHUAN CHANGHONG NETWORK TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411041951.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-07-31
Publication Date
2024-11-19

AI Technical Summary

Technical Problem

Traditional FTTR multicast service cannot meet the security needs of some application scenarios, especially in intelligent manufacturing and commercial applications. For example, in multicast batch upgrade scenarios, devices cannot send IGMP Report messages to request to join the multicast group when booting. This leads to the inability of traditional multicast to meet security requirements.

Method used

By extending the OMCI protocol, the managed entities with controllable multicast are added based on the ITU 984.4 standard, and the controlled multicast functions of the FTTR network are realized, including creating and maintaining controllable multicast instances, closing the multicast agent and snoop functions, and deleting multicast Forwarding and VLAN forwarding rules and forwarding only matching multicast messages.

Benefits of technology

It improves the security and control of multicast services, allowing the FTTR network to meet application scenarios with high security needs, such as intelligent manufacturing and commercial video advertising.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118984297A_ABST
    Figure CN118984297A_ABST
Patent Text Reader

Abstract

The invention relates to the technical field of communication, in particular to an implementation method of controllable multicast based on an FTTR P2MP scheme, an operating system, a terminal and a storage medium, the implementation method comprises the following steps: S1, expanding an OMCI protocol based on an ITU 984.4 standard, and adding managed entities of controllable multicast, the managed entities comprising a first managed entity and a second managed entity; s2, creating a first managed entity instance after the slave optical modem is started, and reporting the first managed entity instance to the master optical modem; s3, enabling the controllable multicast function of the slave optical modem by the master optical modem; s4, enabling a controllable multicast function by the slave optical modem; s5, maintaining the instance by the main optical modem; s6, the slave optical modem completes the configuration of controllable multicast according to the second managed entity instance, wherein the configuration is to complete the operation control of a multicast forwarding table and a vlan forwarding table; and the slave optical modem only forwards the multicast message which can be matched with the multicast forwarding table and the vlan forwarding table. According to the invention, by expanding the OMCI protocol, the controllable multicast function of the FTTR network is realized, and the multicast security is improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of communication technology, and in particular to a method for implementing controllable multicast based on an FTTR P2MP solution, an operating system, a terminal and a storage medium. Background Art

[0002] With the development of FTTR, the cost has dropped rapidly. Due to the long transmission distance of FTTR network and the strong anti-interference ability of optical network, the application of FTTR is not limited to the all-optical network within the home. There are also many demands in some scenarios such as smart manufacturing and commercial applications, such as batch upgrade of smart manufacturing multicast and video advertising in shopping malls. These application scenarios have high requirements for data security.

[0003] In traditional multicast services, users request to join a group through IGMP Report messages. After the optical modem forms a multicast forwarding table, it directly forwards the multicast data, which is uncontrollable, so the security of ordinary multicast is low. In some application scenarios, ordinary multicast cannot meet the needs. Taking multicast batch upgrade as an example, the devices to be upgraded generally listen to a fixed multicast group in boot, and boot will not send IGMP Report messages to request to join the group, so traditional multicast services cannot meet this demand. Summary of the invention

[0004] One of the purposes of the present invention is to provide a method for realizing controllable multicast based on FTTR P2MP scheme, realize the controllable multicast function of FTTR network by extending OMCI protocol, and improve the multicast security.

[0005] In order to achieve the above object, a method for implementing controllable multicast based on FTTR P2MP solution is provided, comprising the following steps:

[0006] S1. Based on the ITU 984.4 standard, the OMCI protocol is extended to increase the managed entity of the controllable multicast; the managed entity comprises a first managed entity and a second managed entity, the first managed entity is an extended FTTR control multicast configuration data, the second managed entity is an extended FTTR ipv4 control multicast port configuration data;

[0007] S2. Create the first managed entity instance after starting the optical modem and report it to the main optical modem;

[0008] S3 master optical modem enables controllable multicast function from the optical modem; specifically: the master optical modem receives the first managed entity instance reported from the optical modem, according to the user configuration to enable the controllable multicast function from the optical modem;

[0009] S4. Enable controllable multicast function from the optical modem; specifically: after the optical modem is enabled by the main optical modem, the multicast proxy and snoop functions are automatically turned off, and the existing multicast forwarding table and vlan forwarding table rules are deleted;

[0010] S5 main optical modem to maintain the second managed entity instance; specifically: the main optical modem according to the user configuration, through the second managed entity instance, complete the controllable multicast function control from the optical modem, including controllable multicast entries add, delete, modify, check operations;

[0011] S6. The optical modem completes the configuration of controllable multicast according to the second managed entity instance, wherein the configuration is: completing the operation control of the multicast forwarding table and the vlan forwarding table; and forwarding only the multicast packets that can match the multicast forwarding table and the vlan forwarding table from the optical modem.

[0012] Further, the extended FTTR control multicast configuration data includes first relationship data, first attribute data and first action data;

[0013] First relationship data: If the slave optical modem supports controllable multicast, the entity is automatically created when the slave optical modem is turned on, and is actively reported during the online process; if the master optical modem finds that there is a corresponding instance report, it means that the slave optical modem supports controllable multicast, otherwise it is considered not to be supported;

[0014] The first attribute data includes a managed entity ID and a controllable multicast enable, wherein the managed entity ID provides a unique number for each managed entity instance; the controllable multicast enable: 0 indicates that the controllable multicast is turned off, 1 indicates that the controllable multicast is turned on, and the default is off;

[0015] The first action data includes an obtain action and a set action, wherein the obtain action is used to obtain one or more attributes of the managed entity; and the set action is used to set one or more attributes of the managed entity.

[0016] Further, the extended FTTR ipv4 control multicast port configuration data includes second relationship data, second attribute data and second action data;

[0017] Second relational data: If the slave optical modem supports controllable multicast, the master optical modem creates, deletes, and modifies the instance according to specific business needs; each multicast group corresponds to an instance;

[0018] The second attribute data includes a managed entity ID, a multicast VLAN, a source multicast address, a destination multicast address, and a bridge port instance ID pointer list. The managed entity ID provides a unique number for each managed entity instance; the multicast VLAN is a VLAN used to carry multicast services; the source multicast address is the source IP address of the multicast stream; the destination multicast address is the destination IP address of the multicast stream; a bridge port instance ID pointer list: the pointer points to the 9.3.4 MAC bridge port configuration data instance, indicating the specific port to which the message corresponding to the multicast group of this instance needs to be forwarded;

[0019] The second action data includes a create action, a delete action, an obtain action and a set action, wherein the create action is used to create an instance of the managed entity; the delete action is used to delete the instance of the managed entity; the obtain action is used to obtain one or more attributes of the managed entity; and the set action is used to set one or more attributes of the managed entity.

[0020] Further, in the step S2, when the slave optical modem automatically creates the first managed entity instance, the controllable multicast function is turned off by default; in the step S3, the master optical modem enables the controllable multicast function of the slave optical modem, including turning the controllable multicast function on or off.

[0021] Furthermore, in step S2, if the master optical modem finds that there is a corresponding first managed entity instance reporting, it marks the slave optical modem as not supporting controllable multicast.

[0022] The second object of the present invention is to provide an operating system for controllable multicast based on the FTTR P2MP solution, which uses the above-mentioned method for implementing controllable multicast based on the FTTR P2MP solution and includes the following modules:

[0023] Managed entity extension module: used to extend the OMCI protocol based on the ITU 984.4 standard and add a managed entity with controllable multicast; the managed entity includes a first managed entity and a second managed entity, the first managed entity is the extended FTTR control multicast configuration data, and the second managed entity is the extended FTTR ipv4 control multicast port configuration data;

[0024] Reporting module: used to enable the slave optical modem to report the first managed entity instance to the master optical modem after the slave optical modem is started and the first managed entity instance is created;

[0025] The master optical modem enables the control module: used to enable the master optical modem to enable the controllable multicast function of the slave optical modem; specifically: after the master optical modem receives the first managed entity instance reported by the slave optical modem, it enables the controllable multicast function of the slave optical modem according to the user configuration;

[0026] Slave optical modem enabling control module: used to enable the controllable multicast function of the slave optical modem; specifically: after the slave optical modem is enabled by the master optical modem, the multicast proxy and snoop functions are automatically turned off, and the existing multicast forwarding table and vlan forwarding table rules are deleted;

[0027] Instance maintenance module: used to enable the master optical modem to maintain the second managed entity instance; specifically: the master optical modem completes the control of the controllable multicast function of the slave optical modem through the second managed entity instance according to the user configuration, including the addition, deletion, modification and query operations of the controllable multicast entries;

[0028] Configuration module: used to enable the slave optical modem to complete the configuration of controllable multicast according to the second managed entity instance, the configuration is: complete the operation control of the multicast forwarding table and the vlan forwarding table; the slave optical modem only forwards multicast messages that can match the multicast forwarding table and the vlan forwarding table.

[0029] A third object of the present invention is to provide a terminal, comprising a memory and a processor;

[0030] The memory is used to store programs;

[0031] The processor is used to execute the program to implement the various steps of the above-mentioned method for implementing controllable multicast based on the FTTR P2MP solution.

[0032] A fourth object of the present invention is to provide a readable storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, the steps of the method for implementing controllable multicast based on the FTTR P2MP solution as described above are implemented.

[0033] Principles and advantages:

[0034] This solution combines the characteristics of the FTTR P2MP solution where the master and slave optical modems are managed through OMCI, expands the OMCI protocol based on the ITU 984.4 standard, and adds a private controllable multicast instance. After the controllable multicast upgrade is enabled, the slave optical modem does not process traditional IGMP-related messages, but directly maintains the multicast forwarding table and VLAN forwarding table based on the controllable multicast instance, and finally completes the forwarding of multicast data. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] Figure 1 A logic block diagram of a method for implementing controllable multicast based on the FTTR P2MP solution according to an embodiment of the present invention;

[0036] Figure 2 Configure the operation flow chart for controllable multicast. DETAILED DESCRIPTION

[0037] The following is further described in detail through specific implementation methods:

[0038] Example

[0039] A controllable multicast implementation method based on FTTR P2MP solution is basically as follows Figure 1 , Figure 2 As shown, the following steps are included:

[0040] S1. Based on the ITU 984.4 standard, the OMCI protocol is extended to increase the managed entity of the controllable multicast; the managed entity includes a first managed entity and a second managed entity, the first managed entity is the extended FTTR control multicast configuration data (Extended FTTR control multicast configuration data), and the second managed entity is the extended FTTR ipv4 control multicast port configuration data (Extended FTTR ipv4 control multicast port configuration data); as shown in the following table:

[0041] Managed Entity Class Value Managed Entity 65280 Extended FTTR control multicast configuration data 65281 Extended FTTR ipv4 control multicast port configuration data

[0042] (1)Extended FTTR control multicast configuration data

[0043] The extended FTTR control multicast configuration data includes first relationship data, first attribute data and first action data;

[0044] First relationship data: If the slave optical modem supports controllable multicast, the entity is automatically created when the slave optical modem is turned on, and is actively reported during the online process; if the master optical modem finds that there is a corresponding instance report, it means that the slave optical modem supports controllable multicast, otherwise it is considered not to be supported;

[0045] The first attribute data includes a managed entity ID and controllable multicast enable;

[0046] The managed entity ID provides a unique number for each managed entity instance (read-only, mandatory, 2 bytes);

[0047] Controllable multicast enable: 0 means turn off controllable multicast, 1 means turn on controllable multicast, and it is turned off by default (readable and writable, forced, 1 byte);

[0048] The first action data includes a get action (Get) and a set action (Set);

[0049] The Get action (Get) is used to obtain one or more attributes of the managed entity;

[0050] The setting action (Set) is used to set one or more attributes of the managed entity.

[0051] (2)Extended FTTR ipv4 control multicast port configuration data

[0052] The extended FTTR ipv4 control multicast port configuration data includes second relationship data, second attribute data and second action data;

[0053] Second relational data: If the slave optical modem supports controllable multicast, the master optical modem creates, deletes, and modifies the instance according to specific business needs; each multicast group corresponds to an instance;

[0054] The second attribute data includes a managed entity ID, a multicast vlan, a source multicast address, a destination multicast address, and a bridge port instance ID pointer linked list;

[0055] The managed entity ID provides a unique number for each managed entity instance (read-only, mandatory, 2 bytes);

[0056] The multicast vlan is used to carry the vlan of the multicast service (read-write, mandatory, 2 bytes);

[0057] The source multicast address is the source IP address of the multicast stream; the destination multicast address is the destination IP address of the multicast stream. If the value is 0.0.0.0, it means that the source multicast address is not checked (read-write, mandatory, 4 bytes).

[0058] Bridge port instance ID pointer list: This pointer points to the 9.3.4MAC bridge port configuration data instance, indicating the specific port to which the message corresponding to the multicast group of this instance needs to be forwarded. It can point to multiple ports. Read-write, mandatory (2N bytes, the length of the N pointer list).

[0059] The second action data includes a create action (Creat), a delete action (Delete), an obtain action (Get) and a set action (Set);

[0060] The create action (Creat) is used to create an instance of the managed entity;

[0061] The delete action (Delete) is used to delete the instance of the managed entity;

[0062] The Get action (Get) is used to obtain one or more attributes of the managed entity;

[0063] The setting action (Set) is used to set one or more attributes of the managed entity.

[0064] S2. After the slave optical modem is started, the first managed entity instance 65280 is created and reported to the master optical modem; in the step S2, when the slave optical modem automatically creates the first managed entity instance 65280, the controllable multicast function is turned off by default; in the step S2, if the master optical modem finds that there is a corresponding first managed entity instance 65280 reported, it is marked that the slave optical modem does not support controllable multicast.

[0065] S3. The master optical modem enables the controllable multicast function of the slave optical modem; specifically: after the master optical modem receives the first managed entity instance 65280 reported by the slave optical modem, it enables the controllable multicast function of the slave optical modem according to the user configuration; in step S3, the master optical modem's enabling of the controllable multicast function of the slave optical modem includes turning the controllable multicast function on or off.

[0066] S4. Enable controllable multicast function from the optical modem; specifically: after the optical modem is enabled by the main optical modem, the multicast proxy and snoop functions are automatically turned off, and the existing multicast forwarding table and vlan forwarding table rules are deleted;

[0067] S5. The main optical modem maintains the second managed entity instance 65281; specifically: the main optical modem completes the controllable multicast function control from the optical modem according to the user configuration through the second managed entity instance 65281, including the controllable multicast entry add, delete, modify, check operation;

[0068] S6. The slave optical modem completes the configuration of controllable multicast according to the second managed entity instance 65281, wherein the configuration is: completing the operation control of the multicast forwarding table and the vlan forwarding table; and forwarding only the multicast packets that can match the multicast forwarding table and the vlan forwarding table from the optical modem.

[0069] An operating system for controllable multicast based on FTTR P2MP solution, characterized in that it uses the above-mentioned method for implementing controllable multicast based on FTTR P2MP solution, and includes the following modules:

[0070] Managed entity extension module: used to extend the OMCI protocol based on the ITU 984.4 standard and add a managed entity with controllable multicast; the managed entity includes a first managed entity and a second managed entity, the first managed entity is the extended FTTR control multicast configuration data, and the second managed entity is the extended FTTR ipv4 control multicast port configuration data;

[0071] Reporting module: used to enable the slave optical modem to report the first managed entity instance to the master optical modem after the slave optical modem is started and the first managed entity instance is created;

[0072] The master optical modem enables the control module: used to enable the master optical modem to enable the controllable multicast function of the slave optical modem; specifically: after the master optical modem receives the first managed entity instance reported by the slave optical modem, it enables the controllable multicast function of the slave optical modem according to the user configuration;

[0073] Slave optical modem enabling control module: used to enable the controllable multicast function of the slave optical modem; specifically: after the slave optical modem is enabled by the master optical modem, the multicast proxy and snoop functions are automatically turned off, and the existing multicast forwarding table and vlan forwarding table rules are deleted;

[0074] Instance maintenance module: used to enable the master optical modem to maintain the second managed entity instance; specifically: the master optical modem completes the control of the controllable multicast function of the slave optical modem through the second managed entity instance according to the user configuration, including the addition, deletion, modification and query operations of the controllable multicast entries;

[0075] Configuration module: used to enable the slave optical modem to complete the configuration of controllable multicast according to the second managed entity instance, the configuration is: complete the operation control of the multicast forwarding table and the vlan forwarding table; the slave optical modem only forwards multicast messages that can match the multicast forwarding table and the vlan forwarding table.

[0076] A terminal comprises a memory and a processor;

[0077] The memory is used to store programs;

[0078] The processor is used to execute the program to implement the various steps of the above-mentioned method for implementing controllable multicast based on the FTTR P2MP solution.

[0079] A readable storage medium stores a computer program thereon. When the computer program is executed by a processor, the computer program implements the steps of the above-mentioned method for implementing controllable multicast based on the FTTR P2MP solution.

[0080] A readable storage medium stores a computer program thereon, and when the computer program is executed by a processor, the steps of the method for implementing a controllable multicast based on the FTTR P2MP scheme described above are implemented. The steps of the method or algorithm described in conjunction with the embodiments disclosed herein can be implemented directly using hardware, a software module executed by a processor, or a combination of the two. The software module can be placed in a random access memory (RAMD, memory, read-only memory ROM, programmable ROM, electrically erasable programmable ROM, register, hard disk, removable disk, CD-ROM) or any other form of storage medium known in the technical field.

[0081] The above is only an embodiment of the present invention. The common sense such as the known specific structure and characteristics in the scheme is not described in detail here. The ordinary technicians in the relevant field know all the common technical knowledge in the technical field of the invention before the application date or priority date, can obtain all the existing technologies in the field, and have the ability to apply the conventional experimental means before that date. The ordinary technicians in the relevant field can improve and implement this scheme in combination with their own abilities under the enlightenment given by this application. Some typical known structures or known methods should not become obstacles for ordinary technicians in the relevant field to implement this application. It should be pointed out that for those skilled in the art, without departing from the structure of the present invention, several deformations and improvements can be made, which should also be regarded as the protection scope of the present invention, which will not affect the effect of the implementation of the present invention and the practicality of the patent. The protection scope required by this application shall be based on the content of its claims, and the specific implementation methods and other records in the specification can be used to interpret the content of the claims.

Claims

1. A method for implementing controllable multicast based on FTTR P2MP solution, It is characterized in that The following steps are involved: S1. Based on the ITU 984.4 standard, the OMCI protocol is extended to increase the managed entity of the controllable multicast; the managed entity comprises a first managed entity and a second managed entity, the first managed entity is an extended FTTR control multicast configuration data, the second managed entity is an extended FTTR ipv4 control multicast port configuration data; S2. Create the first managed entity instance after starting the optical modem and report it to the main optical modem; S3 master optical modem enables controllable multicast function from the optical modem; specifically: the master optical modem receives the first managed entity instance reported from the optical modem, according to the user configuration to enable the controllable multicast function from the optical modem; S4. Enable controllable multicast function from the optical modem; specifically: after the optical modem is enabled by the main optical modem, the multicast proxy and snoop functions are automatically turned off, and the existing multicast forwarding table and vlan forwarding table rules are deleted; S5 main optical modem to maintain the second managed entity instance; specifically: the main optical modem according to the user configuration, through the second managed entity instance, complete the controllable multicast function control from the optical modem, including controllable multicast entries add, delete, modify, check operations; S6. Complete the controllable multicast configuration from the optical modem according to the second managed entity instance, the configuration is: complete the multicast forwarding table and vlan forwarding table operation control; Only multicast packets that match the multicast forwarding table and VLAN forwarding table are forwarded from the optical modem.

2. According to claim 1, a method for implementing controllable multicast based on FTTR P2MP solution, Features: The extended FTTR control multicast configuration data includes first relationship data, first attribute data and first action data; First relationship data: If the slave optical modem supports controllable multicast, the entity is automatically created when the slave optical modem is turned on, and is actively reported during the online process; if the master optical modem finds that there is a corresponding instance report, it means that the slave optical modem supports controllable multicast, otherwise it is considered not to be supported; The first attribute data includes a managed entity ID and a controllable multicast enable, wherein the managed entity ID provides a unique number for each managed entity instance; the controllable multicast enable: 0 indicates that the controllable multicast is turned off, 1 indicates that the controllable multicast is turned on, and the default is off; The first action data includes an obtain action and a set action, wherein the obtain action is used to obtain one or more attributes of the managed entity; and the set action is used to set one or more attributes of the managed entity.

3. According to the method for implementing controllable multicast based on FTTR P2MP solution according to claim 2, Features: The extended FTTR ipv4 control multicast port configuration data includes second relationship data, second attribute data and second action data; Second relation data: If the slave optical modem supports controllable multicast, the master optical modem creates, deletes, and modifies the instance according to specific business needs; Each multicast group corresponds to an instance; The second attribute data includes a managed entity ID, a multicast VLAN, a source multicast address, a destination multicast address, and a bridge port instance ID pointer list, wherein the managed entity ID provides a unique number for each managed entity instance; the multicast VLAN is a VLAN used to carry multicast services; the source multicast address is a multicast stream source IP address; The destination multicast address is the destination IP address of the multicast stream; Bridge port instance ID pointer list: the pointer points to the 9.3.4 MAC bridge port configuration data instance, indicating the specific port to which the message corresponding to the multicast group of this instance needs to be forwarded; The second action data includes a create action, a delete action, an obtain action and a set action, wherein the create action is used to create an instance of the managed entity; the delete action is used to delete the instance of the managed entity; the obtain action is used to obtain one or more attributes of the managed entity; and the set action is used to set one or more attributes of the managed entity.

4. According to claim 3, a method for implementing controllable multicast based on FTTR P2MP solution, Features: In the step S2, when the slave optical modem automatically creates the first managed entity instance, the controllable multicast function is turned off by default; in the step S3, the master optical modem enables the controllable multicast function of the slave optical modem, including turning the controllable multicast function on or off.

5. According to claim 3, a method for implementing controllable multicast based on FTTR P2MP solution, Features: In step S2, if the master optical modem finds that there is a corresponding first managed entity instance reporting, it marks the slave optical modem as not supporting controllable multicast.

6. A controllable multicast operating system based on FTTR P2MP solution, It is characterized in that A method for implementing controllable multicast based on the FTTR P2MP solution according to any one of claims 1 to 5 above is used, comprising the following modules: Managed entity extension module: used to extend the OMCI protocol based on the ITU 984.4 standard and add a managed entity with controllable multicast; the managed entity includes a first managed entity and a second managed entity, the first managed entity is the extended FTTR control multicast configuration data, and the second managed entity is the extended FTTR ipv4 control multicast port configuration data; Reporting module: used to enable the slave optical modem to report the first managed entity instance to the master optical modem after the slave optical modem is started and the first managed entity instance is created; The master optical modem enables the control module: used to enable the master optical modem to enable the controllable multicast function of the slave optical modem; specifically: after the master optical modem receives the first managed entity instance reported by the slave optical modem, it enables the controllable multicast function of the slave optical modem according to the user configuration; Slave optical modem enabling control module: used to enable the controllable multicast function of the slave optical modem; specifically: after the slave optical modem is enabled by the master optical modem, the multicast proxy and snoop functions are automatically turned off, and the existing multicast forwarding table and vlan forwarding table rules are deleted; Instance maintenance module: used to enable the master optical modem to maintain the second managed entity instance; specifically: the master optical modem completes the control of the controllable multicast function of the slave optical modem through the second managed entity instance according to the user configuration, including the addition, deletion, modification and query operations of the controllable multicast entries; Configuration module: used to enable the slave optical modem to complete the configuration of controllable multicast according to the second managed entity instance, wherein the configuration is to complete the operation control of the multicast forwarding table and the vlan forwarding table; Only multicast packets that match the multicast forwarding table and VLAN forwarding table are forwarded from the optical modem.

7. A terminal, Features: including memory and processor; The memory is used to store programs; The processor is used to execute the program to implement each step of the method for implementing controllable multicast based on the FTTRP2MP solution as described in any one of claims 1-5.

8. A readable storage medium, Features: A computer program is stored thereon, and when the computer program is executed by a processor, each step of a method for realizing controllable multicast based on an FTTR P2MP solution as claimed in any one of claims 1 to 5 is implemented.