CN117135003A - Method and device for managing multicast topology data - Google Patents
Method and device for managing multicast topology data Download PDFInfo
- Publication number
- CN117135003A CN117135003A CN202311152941.2A CN202311152941A CN117135003A CN 117135003 A CN117135003 A CN 117135003A CN 202311152941 A CN202311152941 A CN 202311152941A CN 117135003 A CN117135003 A CN 117135003A
- Authority
- CN
- China
- Prior art keywords
- multicast
- topology data
- data
- target
- database
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 51
- 238000004590 computer program Methods 0.000 claims description 15
- 238000012545 processing Methods 0.000 claims description 13
- 238000010586 diagram Methods 0.000 description 13
- 238000004891 communication Methods 0.000 description 7
- 230000006870 function Effects 0.000 description 6
- 230000003287 optical effect Effects 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 230000008447 perception Effects 0.000 description 3
- 230000008901 benefit Effects 0.000 description 2
- 239000000835 fiber Substances 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 239000004065 semiconductor Substances 0.000 description 2
- 238000010276 construction Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/16—Arrangements for providing special services to substations
- H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
- G06F16/275—Synchronous replication
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computing Systems (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses a method and a device for managing multicast topology data, and relates to the technical field of multicasting. One embodiment of the method comprises the following steps: receiving a multicast group joining request sent by a front end, wherein the multicast group joining request carries a target cloud host identifier and a target multicast group identifier; adding the target cloud host into the target multicast group to enable the target cloud host to become a multicast member of the target multicast group; updating the member information added to the target multicast group to multicast topology data in a database, and sending a data update message to the front end, so that the front end displays the multicast topology data on the front end after acquiring the multicast topology data from the database; the data update message carries the data identifier of the multicast topology data in the database. The implementation can solve the technical problem that if the multicast member fails to join the multicast group, the user does not feel the problem.
Description
Technical Field
The present invention relates to the field of multicast technologies, and in particular, to a method and an apparatus for managing multicast topology data.
Background
Currently, each cloud manufacturer realizes multicast on the cloud based on different technologies, and each manufacturer for multicast member management is different, but the two kinds of the multicast member management are basically divided, wherein the first kind of multicast member management is static configuration, and the second kind of multicast member management is performed by using an IGMP protocol.
Based on the existing product technology, each manufacturer product needs a user to confirm whether a certain node successfully joins a multicast group or not by himself, and the judging method is whether multicast data corresponding to a multicast address can be received or not. In this context, if a multicast member fails to join a multicast group, multicast data cannot be received, but the user is unaware.
Disclosure of Invention
In view of this, the embodiments of the present invention provide a method and apparatus for managing multicast topology data, so as to solve the technical problem that if a multicast member fails to join a multicast group, but the user does not feel the multicast topology data.
To achieve the above object, according to one aspect of the embodiments of the present invention, there is provided a method for managing multicast topology data, applied to a multicast gateway, including:
receiving a multicast group joining request sent by a front end, wherein the multicast group joining request carries a target cloud host identifier and a target multicast group identifier;
adding the target cloud host into the target multicast group to enable the target cloud host to become a multicast member of the target multicast group;
Updating the member information added to the target multicast group to multicast topology data in a database, and sending a data update message to the front end, so that the front end displays the multicast topology data on the front end after acquiring the multicast topology data from the database; the data update message carries the data identifier of the multicast topology data in the database.
Optionally, the method further comprises:
receiving a multicast group leaving request sent by the front end, wherein the multicast group leaving request carries the target cloud host identifier and the target multicast group identifier;
deleting the target cloud host from the target multicast group;
updating the leaving member information of the target multicast group to the multicast topology data in the database, and sending a data update message to the front end.
Optionally, updating the joining member information of the target multicast group to multicast topology data in a database, including:
updating the joining member information of the target multicast group to multicast topology data in any node in a redis cluster so that the node synchronizes the updated multicast topology data to other nodes in the redis cluster;
Wherein, key is the data identification of the multicast topology data in the redis cluster, and value is the multicast topology data.
Optionally, the multicast topology data includes detailed information of each multicast group, where the detailed information includes a multicast address, a number of multicast members that have been added, a cloud host identifier corresponding to each multicast member, a number of maximum available multicast members, and a number of remaining available multicast members.
In addition, according to another aspect of the embodiment of the present invention, there is provided a method for managing multicast topology data, applied to a front end, including:
sending a multicast group joining request to a multicast gateway, wherein the multicast group joining request carries a target cloud host identifier and a target multicast group identifier;
receiving a data update message sent by the multicast gateway, wherein the data update message carries a data identifier of multicast topology data in a database;
sending a topology data acquisition request to the database, wherein the topology data acquisition request carries the data identifier;
and receiving multicast topology data corresponding to the data identification returned by the database, and displaying the multicast topology data at the front end.
Optionally, receiving multicast topology data corresponding to the data identifier returned by the database, and displaying the multicast topology data at the front end, including:
receiving multicast topology data corresponding to the data identification returned by the database;
judging whether the locally stored multicast topology data is consistent with the multicast topology data returned by the database;
if yes, displaying the locally stored multicast topology data at the front end, and generating an alarm log, wherein the content of the alarm log is that the multicast topology data is not updated;
if not, the multicast topology data returned by the database is displayed at the front end, and the multicast topology data returned by the database is updated to the local.
In addition, according to another aspect of the embodiment of the present invention, there is provided an apparatus for managing multicast topology data, provided in a multicast gateway, including:
the first receiving module is used for receiving a multicast group joining request sent by the front end, wherein the multicast group joining request carries a target cloud host identifier and a target multicast group identifier;
the processing module is used for adding the target cloud host into the target multicast group to enable the target cloud host to become a multicast member of the target multicast group;
The updating module is used for updating the joining member information of the target multicast group to the multicast topology data in the database, and sending a data updating message to the front end so that the front end can display the multicast topology data on the front end after acquiring the multicast topology data from the database; the data update message carries the data identifier of the multicast topology data in the database.
Optionally, the first receiving module is further configured to receive a multicast group leaving request sent by the front end, where the multicast group leaving request carries the target cloud host identifier and the target multicast group identifier;
the processing module is further configured to delete the target cloud host from the target multicast group;
the updating module is further configured to update the leaving member information of the target multicast group to multicast topology data in the database, and send a data update message to the front end.
Optionally, the updating module is further configured to:
updating the joining member information of the target multicast group to multicast topology data in any node in a redis cluster so that the node synchronizes the updated multicast topology data to other nodes in the redis cluster;
Wherein, key is the data identification of the multicast topology data in the redis cluster, and value is the multicast topology data.
Optionally, the multicast topology data includes detailed information of each multicast group, where the detailed information includes a multicast address, a number of multicast members that have been added, a cloud host identifier corresponding to each multicast member, a number of maximum available multicast members, and a number of remaining available multicast members.
In addition, according to another aspect of the embodiment of the present invention, there is provided an apparatus for managing multicast topology data, provided at a front end, including:
the request module is used for sending a multicast group joining request to the multicast gateway, wherein the multicast group joining request carries a target cloud host identifier and a target multicast group identifier;
the message module is used for receiving a data update message sent by the multicast gateway, wherein the data update message carries a data identifier of multicast topology data in a database;
the acquisition module is used for sending a topology data acquisition request to the database, wherein the topology data acquisition request carries the data identifier;
and the second receiving module is used for receiving the multicast topology data corresponding to the data identifier returned by the database and displaying the multicast topology data at the front end.
Optionally, the second receiving module is further configured to:
receiving multicast topology data corresponding to the data identification returned by the database;
judging whether the locally stored multicast topology data is consistent with the multicast topology data returned by the database;
if yes, displaying the locally stored multicast topology data at the front end, and generating an alarm log, wherein the content of the alarm log is that the multicast topology data is not updated;
if not, the multicast topology data returned by the database is displayed at the front end, and the multicast topology data returned by the database is updated to the local.
According to another aspect of an embodiment of the present invention, there is also provided an electronic device including:
one or more processors;
storage means for storing one or more programs,
the one or more processors implement the method of any of the embodiments described above when the one or more programs are executed by the one or more processors.
According to another aspect of an embodiment of the present invention, there is also provided a computer readable medium having stored thereon a computer program which, when executed by a processor, implements the method according to any of the embodiments described above.
According to another aspect of embodiments of the present invention, there is also provided a computer program product comprising a computer program which, when executed by a processor, implements the method according to any of the embodiments described above.
One embodiment of the above invention has the following advantages or benefits: because the technical means of updating the joining member information of the target multicast group to the multicast topology data in the database and sending the data updating message to the front end is adopted, the front end obtains and displays the multicast topology data from the database, and the technical problem that if the joining member of the multicast group fails but a user does not feel in the prior art is solved. The embodiment of the invention directly manages the multicast members through the front-end page, and comprises the step of checking whether the multicast members successfully join the multicast group, whether the multicast members join the correct multicast group, the step of displaying the multicast members of each multicast group and the like, so that the user has perception.
Further effects of the above-described non-conventional alternatives are described below in connection with the embodiments.
Drawings
In order to more clearly illustrate the embodiments of the invention or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described, it being obvious that the drawings in the following description are only some embodiments of the invention, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art. Wherein:
Fig. 1 is a flow chart of a method of managing multicast topology data according to one embodiment of the present invention;
fig. 2 is a schematic diagram of a system architecture for managing multicast topology data according to an embodiment of the present invention;
fig. 3a and 3b are schematic diagrams of multicast topology data according to an embodiment of the present invention;
fig. 4 is a flowchart of a method of managing multicast topology data according to one referenceable embodiment of the present invention;
fig. 5 is a flowchart of a method of managing multicast topology data according to another embodiment of the present invention;
fig. 6 is a flowchart of a method of managing multicast topology data according to one referenceable embodiment of the present invention;
fig. 7 is a schematic diagram of an apparatus for managing multicast topology data according to one embodiment of the present invention;
fig. 8 is a schematic diagram of an apparatus for managing multicast topology data according to another embodiment of the present invention;
FIG. 9 is an exemplary system architecture diagram in which embodiments of the present invention may be applied;
fig. 10 is a schematic diagram of a computer system suitable for use in implementing an embodiment of the invention.
Detailed Description
Exemplary embodiments of the present invention will now be described with reference to the accompanying drawings, in which various details of the embodiments of the present invention are included to facilitate understanding, and are to be considered merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
It should be noted that, in the technical solution of the present disclosure, the related aspects of collecting, updating, analyzing, processing, using, transmitting, storing, etc. of the personal information of the user all conform to the rules of the related laws and regulations, and are used for legal purposes without violating the public order colloquial. Necessary measures are taken for the personal information of the user, illegal access to the personal information data of the user is prevented, and the personal information security, network security and national security of the user are maintained.
In the prior art, the following cases exist, which can cause the joining failure of multicast members, and multicast data cannot be received, but the user does not feel, and the reason of the joining failure cannot be analyzed either:
1) Exceeding multicast quota: in general, there is a quota limit on the multicast member side, for example, the number of multicast members is limited to 100 by a cloud vendor, and once a new multicast member is added after the quota is exceeded, the user side can only feel that multicast data cannot be received, but it is not clear whether the multicast data is a network problem, a software problem or other problems.
2) Misoperations join the wrong multicast group: in the case where there are a large number of multicast topologies in the network, a user is likely to join the wrong multicast group, and in this case, the user may receive multicast data, but the multicast data belongs to the multicast member, and may mislead the user.
3) Joining without multicast data, it cannot be determined whether to join the multicast group successfully: for the user, the condition for judging whether to join the multicast group successfully is that multicast data can be received, but in the case of no multicast data, the user cannot judge whether to join successfully, and once joining fails, the receiving of the multicast data is affected later.
In order to solve the technical problems in the prior art, the embodiment of the invention provides a method for managing multicast topology data. Fig. 1 is a flowchart of a method of managing multicast topology data according to an embodiment of the present invention. As an embodiment of the present invention, as shown in fig. 1, the method for managing multicast topology data is applied to a multicast gateway, and may include:
step 101, receiving a multicast group joining request sent by a front end, wherein the multicast group joining request carries a target cloud host identifier and a target multicast group identifier.
As shown in fig. 2, the multicast gateway receives a multicast group joining request sent by the front end, where the multicast group joining request carries an identifier of a target cloud host and an identifier of a target multicast group that the target cloud host desires to join. Optionally, the target cloud host identification may include an IP address of the target cloud host. Optionally, the target cloud host identification may include an IP address and a MAC address of the target cloud host. Optionally, the target cloud host identification may include a number of the target cloud host. Optionally, the target multicast group identifier may be an IP address of the cloud host corresponding to the multicast source of the target multicast group, or may be a number of the target multicast group, which is not limited in the embodiment of the present invention.
It should be noted that, the multicast gateway is deployed with IGMP proxy, which is a software program developed based on IGMP, and is mainly used for monitoring IGMP protocol data messages. The multicast group joining request is an IGMP protocol data message, and the multicast gateway can monitor the multicast group joining request.
Step 102, joining the target cloud host to the target multicast group, so that the target cloud host becomes a multicast member of the target multicast group.
After receiving the multicast group joining request sent by the front end, the multicast gateway analyzes the multicast group joining request, thereby obtaining the target cloud host identification and the target multicast group identification. Then, the multicast gateway adds the target cloud host into the target multicast group so that the target cloud host becomes a multicast member of the target multicast group.
Step 103, updating the joining member information of the target multicast group to the multicast topology data in the database, and sending a data update message to the front end, so that the front end can display the multicast topology data at the front end after acquiring the multicast topology data from the database; the data update message carries the data identifier of the multicast topology data in the database.
As shown in fig. 2, the multicast gateway updates joining member information of the target multicast group to multicast topology data in the database, where the joining member information may be a target cloud host identifier and an identifier of a target multicast group that the target cloud host desires to join. Optionally, the multicast topology data includes detailed information of each multicast group, where the detailed information includes a multicast address, a number of multicast members that have been added, a cloud host identifier corresponding to each multicast member, a number of maximum available multicast members, and a number of remaining available multicast members.
Optionally, the multicast gateway updates the joining member information of the target multicast group to the multicast topology data in the database, and sends a data update message to the front end after the multicast topology data in the database is updated successfully. Optionally, the multicast gateway updates the joining member information of the target multicast group to the multicast topology data in the database, and simultaneously sends the data update message to the front end, so that whether the multicast topology data in the database is updated successfully or not, the multicast gateway sends the data update message to the front end, so that the processing speed of the multicast gateway can be improved, and the front end can immediately receive the data update message.
It should be noted that, the front end subscribes to the related subject message, and once the multicast gateway updates the multicast topology data in the database, the multicast gateway will send a data update message to the front end, as shown in fig. 2.
Optionally, updating the topology data of the target multicast group to the multicast topology data in the database includes: updating the joining member information of the target multicast group to multicast topology data in any node in a redis cluster so that the node synchronizes the updated multicast topology data to other nodes in the redis cluster; wherein, key is the data identification of the multicast topology data in the redis cluster, and value is the multicast topology data. In order to improve the reading speed and the data security of multicast topology data, the embodiment of the invention uses a redis cluster as a database, a multicast gateway updates the joining member information of a target multicast group to the multicast topology data in any node in the redis cluster, and the node synchronizes the updated multicast topology data to other nodes in the redis cluster so as to ensure the data consistency of each node in the redis cluster.
As shown in fig. 2, after the front end receives the data update message sent by the multicast gateway, the front end acquires the multicast topology data from the database and displays the acquired multicast topology data.
The embodiment of the invention aims to solve the problem that a user cannot intuitively and efficiently manage multicast network topology after a new multicast member joins a multicast group. In the embodiment of the invention, after a new multicast member joins a multicast group, a multicast gateway updates multicast topology data in a database and issues a subscription message, and after a front end receives a corresponding subscription message, the database is queried to obtain the latest multicast topology data and is displayed on a front end page. The user can check the detailed information of each multicast group through the front-end page, wherein the detailed information comprises multicast addresses, the number of the added multicast members, cloud host identifications corresponding to the multicast members, the maximum number of the added multicast members and the number of the rest added multicast members.
As shown in fig. 3a, the front-end page displays a multicast group list including a multicast address, the number of added multicast members, the number of maximum available multicast members, and the number of remaining available multicast members, and after clicking on the multicast address of a certain multicast group, the multicast members of the multicast group can be viewed, as shown in fig. 3 b.
According to the various embodiments described above, it can be seen that the technical means of the embodiment of the present invention that the front end obtains and displays the multicast topology data from the database by updating the joining member information of the target multicast group to the multicast topology data in the database and sending the data update message to the front end, solves the technical problem in the prior art that if the joining member of the multicast group fails, but the user does not feel. In the prior art, after a multicast member joins a certain multicast group, the user has no other method to confirm whether the multicast member joins the multicast group successfully, except for checking whether the multicast data can be received. Once the problem of join failure occurs, firstly, multicast data is lost, and secondly, the method is time-consuming to check the reasons. The embodiment of the invention directly manages the multicast members through the front-end page, and comprises the step of checking whether the multicast members successfully join the multicast group, whether the multicast members join the correct multicast group, the step of displaying the multicast members of each multicast group and the like, so that the user has perception.
Fig. 4 is a flowchart of a method of managing multicast topology data according to one referenceable embodiment of the present invention. As still another embodiment of the present invention, as shown in fig. 4, the method for managing multicast topology data is applied to a multicast gateway, and may include:
step 401, receiving a multicast group joining request sent by a front end, where the multicast group joining request carries a target cloud host identifier and a target multicast group identifier.
Step 402, joining the target cloud host to the target multicast group, so that the target cloud host becomes a multicast member of the target multicast group.
Step 403, updating the joining member information of the target multicast group to multicast topology data in any node in the redis cluster, so that the node synchronizes the updated multicast topology data to other nodes in the redis cluster, and sends a data update message to the front end, so that the front end displays the multicast topology data at the front end after obtaining the multicast topology data from the redis cluster.
Wherein, key is the data identification of the multicast topology data in the redis cluster, value is the multicast topology data, and the data update message carries the data identification of the multicast topology data in the redis cluster.
Step 404, receiving a multicast group leaving request sent by the front end, where the multicast group leaving request carries the target cloud host identifier and the target multicast group identifier.
And step 405, deleting the target cloud host from the target multicast group.
Step 406, updating the leaving member information of the target multicast group to multicast topology data in any node in the redis cluster, so that the node synchronizes the updated multicast topology data to other nodes in the redis cluster, and sending a data update message to the front end, so that the front end displays the multicast topology data at the front end after obtaining the multicast topology data from the redis cluster.
The data update message carries a data identifier of the multicast topology data in the redis cluster.
In this embodiment, after the target cloud host joins the target multicast group and becomes a multicast member of the target multicast group, the target cloud host may also apply to leave the target multicast group. Specifically, the multicast gateway receives a multicast group leaving request sent by the front end, where the multicast group leaving request carries a target cloud host identifier and an identifier of a target multicast group that the target cloud host expects to leave. Optionally, the target cloud host identification may include an IP address of the target cloud host. Optionally, the target cloud host identification may include an IP address and a MAC address of the target cloud host. Optionally, the target cloud host identification may include a number of the target cloud host. Optionally, the target multicast group identifier may be an IP address of the cloud host corresponding to the multicast source of the target multicast group, or may be a number of the target multicast group, which is not limited in the embodiment of the present invention.
After receiving the multicast group leaving request sent by the front end, the multicast gateway analyzes the multicast group leaving request, thereby obtaining the target cloud host identifier and the target multicast group identifier. The multicast gateway then deletes the target cloud host from the target multicast group. The multicast gateway then updates leaving member information of the target multicast group to multicast topology data in the redis cluster, wherein the leaving member information may be a target cloud host identity and an identity of the target multicast group that the target cloud host desires to leave.
As the front-end subscribes to the related subject messages, once the multicast gateway updates the multicast topology data in the redis cluster, the multicast gateway will send a data update message to the front-end. After the front end receives the data updating message sent by the multicast gateway, the front end acquires the multicast topology data from the redis cluster and displays the acquired multicast topology data.
In addition, the implementation of the method for managing multicast topology data according to the present invention is described in detail in the above-mentioned method for managing multicast topology data, and thus the description thereof will not be repeated here.
Fig. 5 is a flowchart of a method of managing multicast topology data according to another embodiment of the present invention. As another embodiment of the present invention, as shown in fig. 5, the method for managing multicast topology data is applied to a front end, and may include:
Step 501, a multicast group joining request is sent to a multicast gateway, wherein the multicast group joining request carries a target cloud host identifier and a target multicast group identifier.
Step 502, receiving a data update message sent by the multicast gateway, where the data update message carries a data identifier of multicast topology data in a database.
Step 503, sending a topology data acquisition request to the database, where the topology data acquisition request carries the data identifier.
Step 504, receiving multicast topology data corresponding to the data identifier returned by the database, and displaying the multicast topology data at the front end.
When a user needs to join a target cloud host into a target multicast group, a multicast group joining request can be sent to a multicast gateway through a front end, wherein the multicast group joining request carries a target cloud host identifier and an identifier of a target multicast group which the target cloud host expects to join. Optionally, the target cloud host identification may include an IP address of the target cloud host. Optionally, the target cloud host identification may include an IP address and a MAC address of the target cloud host. Optionally, the target cloud host identification may include a number of the target cloud host. Optionally, the target multicast group identifier may be an IP address of the cloud host corresponding to the multicast source of the target multicast group, or may be a number of the target multicast group, which is not limited in the embodiment of the present invention.
After receiving a multicast group joining request sent by a front end, the multicast gateway joins a target cloud host into a target multicast group, so that the target cloud host becomes a multicast member of the target multicast group; then, the joining member information of the target multicast group is updated to the multicast topology data in the database, and a data update message is sent to the front end; the data update message carries the data identifier of the multicast topology data in the database. Alternatively, the database may be a redis cluster, so that the reading speed and the security of the multicast topology data can be improved.
As the front end subscribes to the relevant topic message, once the multicast gateway updates the multicast topology data in the database, the multicast gateway will send a data update message to the front end. After receiving the data update message sent by the multicast gateway, the front end sends a topology data acquisition request to the database, wherein the topology data acquisition request carries the data identifier, and the database inquires corresponding multicast topology data according to the data identifier and returns the inquiry result to the front end. And the front end receives the multicast topology data corresponding to the data identifier returned by the database and displays the multicast topology data at the front end.
As shown in fig. 3, the user may view detailed information of each multicast group through the front-end page, where the detailed information includes a multicast address, the number of added multicast members, a cloud host identifier corresponding to each multicast member, the number of maximum available multicast members, and the number of remaining available multicast members.
Fig. 6 is a flowchart of a method of managing multicast topology data according to another referenceable embodiment of the present invention. As another embodiment of the present invention, as shown in fig. 6, the method for managing multicast topology data is applied to a front end, and may include:
step 601, a multicast group joining request is sent to a multicast gateway, wherein the multicast group joining request carries a target cloud host identifier and a target multicast group identifier.
Step 602, receiving a data update message sent by the multicast gateway, where the data update message carries a data identifier of multicast topology data in a database.
Step 603, sending a topology data acquisition request to the database, where the topology data acquisition request carries the data identifier.
Step 604, receiving multicast topology data corresponding to the data identifier returned by the database.
Step 605, judging whether the locally stored multicast topology data is consistent with the multicast topology data returned by the database; if yes, go to step 606; if not, go to step 607.
And step 606, displaying the locally stored multicast topology data at the front end, and generating an alarm log, wherein the content of the alarm log is that the multicast topology data is not updated.
And step 607, displaying the multicast topology data returned by the database at the front end, and updating the multicast topology data returned by the database to the local.
When the multicast gateway updates the multicast topology data in the database, there may be a case of failure in updating, for this reason, after the front end receives the multicast topology data returned from the database, it needs to compare the locally stored multicast topology data with the multicast topology data returned from the database, and determine whether the locally stored multicast topology data and the multicast topology data are consistent, if so, it is indicated that the multicast gateway fails to update the multicast topology data, the front end generates an alarm log, and the content of the alarm log is that the multicast topology data is not updated, so as to facilitate subsequent tracing; if the multicast topology data is inconsistent, the multicast gateway is indicated to update the multicast topology data successfully, the front end displays the multicast topology data returned by the database, and updates the multicast topology data returned by the database to the local.
Fig. 7 is a schematic diagram of an apparatus for managing multicast topology data according to an embodiment of the present invention. As shown in fig. 7, the apparatus 700 for managing multicast topology data is disposed in a multicast gateway, and includes a first receiving module 701, a processing module 702, and an updating module 703; the first receiving module 701 is configured to receive a multicast group joining request sent by a front end, where the multicast group joining request carries a target cloud host identifier and a target multicast group identifier; the processing module 702 is configured to join the target cloud host into the target multicast group, so that the target cloud host becomes a multicast member of the target multicast group; the updating module 703 is configured to update the joining member information of the target multicast group to multicast topology data in a database, and send a data update message to the front end, so that the front end obtains the multicast topology data from the database and displays the multicast topology data at the front end; the data update message carries the data identifier of the multicast topology data in the database.
Optionally, the first receiving module 701 is further configured to receive a multicast group leave request sent by the front end, where the multicast group leave request carries the target cloud host identifier and the target multicast group identifier;
the processing module 702 is further configured to delete the target cloud host from the target multicast group;
the updating module 703 is further configured to update the leaving member information of the target multicast group to the multicast topology data in the database, and send a data update message to the front end.
Optionally, the updating module 703 is further configured to:
updating the joining member information of the target multicast group to multicast topology data in any node in a redis cluster so that the node synchronizes the updated multicast topology data to other nodes in the redis cluster;
wherein, key is the data identification of the multicast topology data in the redis cluster, and value is the multicast topology data.
Optionally, the multicast topology data includes detailed information of each multicast group, where the detailed information includes a multicast address, a number of multicast members that have been added, a cloud host identifier corresponding to each multicast member, a number of maximum available multicast members, and a number of remaining available multicast members.
The specific implementation of the apparatus for managing multicast topology data according to the present invention is described in detail in the method for managing multicast topology data described above, and thus the description thereof will not be repeated here.
Fig. 8 is a schematic diagram of an apparatus for managing multicast topology data according to another embodiment of the present invention. As shown in fig. 8, the device 800 for managing multicast topology data is disposed at a front end, and includes a request module 801, a message module 802, an obtaining module 803, and a second receiving module 804; the request module 801 is configured to send a multicast group joining request to a multicast gateway, where the multicast group joining request carries a target cloud host identifier and a target multicast group identifier; the message module 802 is configured to receive a data update message sent by the multicast gateway, where the data update message carries a data identifier of multicast topology data in a database; the obtaining module 803 is configured to send a topology data obtaining request to the database, where the topology data obtaining request carries the data identifier; the second receiving module 804 is configured to receive multicast topology data corresponding to the data identifier returned by the database, and display the multicast topology data at the front end.
Optionally, the second receiving module 804 is further configured to:
receiving multicast topology data corresponding to the data identification returned by the database;
judging whether the locally stored multicast topology data is consistent with the multicast topology data returned by the database;
if yes, displaying the locally stored multicast topology data at the front end, and generating an alarm log, wherein the content of the alarm log is that the multicast topology data is not updated;
if not, the multicast topology data returned by the database is displayed at the front end, and the multicast topology data returned by the database is updated to the local.
The specific implementation of the apparatus for managing multicast topology data according to the present invention is described in detail in the method for managing multicast topology data described above, and thus the description thereof will not be repeated here.
Fig. 9 illustrates an exemplary system architecture 900 of a method of managing multicast topology data or an apparatus of managing multicast topology data to which embodiments of the present invention may be applied.
As shown in fig. 9, system architecture 900 may include terminal devices 901, 902, 903, a network 904, and a server 905. The network 904 is the medium used to provide communications links between the terminal devices 901, 902, 903 and the server 905. The network 904 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.
A user may interact with the server 905 over the network 904 using the terminal devices 901, 902, 903 to receive or send messages, etc. Various communication client applications may be installed on the terminal devices 901, 902, 903, such as shopping class applications, web browser applications, search class applications, instant messaging tools, mailbox clients, social platform software, and the like (by way of example only).
Terminal devices 901, 902, 903 may be a variety of electronic devices having a display screen and supporting web browsing, including but not limited to smartphones, tablets, laptop and desktop computers, and the like.
The server 905 may be a server that provides various services, such as a background management server (by way of example only) that provides support for shopping-type websites browsed by users using terminal devices 901, 902, 903. The background management server can analyze and other data such as the received article information inquiry request and feed back the processing result to the terminal equipment.
It should be noted that, the method for managing multicast topology data provided in the embodiment of the present invention is generally executed by the server 905, and accordingly, the device for managing multicast topology data is generally disposed in the server 905. The method for managing multicast topology data provided by the embodiment of the present invention may also be performed by the terminal devices 901, 902, 903, and accordingly, the apparatus for managing multicast topology data may be provided in the terminal devices 901, 902, 903.
It should be understood that the number of terminal devices, networks and servers in fig. 9 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.
Referring now to FIG. 10, there is illustrated a schematic diagram of a computer system 1000 suitable for use in implementing an embodiment of the present invention. The terminal device shown in fig. 10 is only an example, and should not impose any limitation on the functions and the scope of use of the embodiment of the present invention.
As shown in fig. 10, the computer system 1000 includes a Central Processing Unit (CPU) 1001, which can execute various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 1002 or a program loaded from a storage section 1008 into a Random Access Memory (RAM) 1003. In the RAM1003, various programs and data required for the operation of the system 1000 are also stored. The CPU 1001, ROM 1002, and RAM1003 are connected to each other by a bus 1004. An input/output (I/O) interface 1005 is also connected to bus 1004.
The following components are connected to the I/O interface 1005: an input section 1006 including a keyboard, a mouse, and the like; an output portion 1007 including a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), etc., and a speaker, etc.; a storage portion 1008 including a hard disk or the like; and a communication section 1009 including a network interface card such as a LAN card, a modem, or the like. The communication section 1009 performs communication processing via a network such as the internet. The drive 1010 is also connected to the I/O interface 1005 as needed. A removable medium 1011, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like, is installed as needed in the drive 1010, so that a computer program read out therefrom is installed as needed in the storage section 1008.
In particular, according to embodiments of the present disclosure, the processes described above with reference to flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method shown in the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network via the communication portion 1009, and/or installed from the removable medium 1011. The above-described functions defined in the system of the present invention are performed when the computer program is executed by a Central Processing Unit (CPU) 1001.
The computer readable medium shown in the present invention may be a computer readable signal medium or a computer readable storage medium, or any combination of the two. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present invention, however, the computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, with the computer-readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer programs according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The modules involved in the embodiments of the present invention may be implemented in software or in hardware. The described modules may also be provided in a processor, for example, as: a processor comprises a first receiving module, a processing module and an updating module, wherein the names of these modules do not constitute a limitation of the module itself in some cases.
The modules involved in the embodiments of the present invention may be implemented in software or in hardware. The described modules may also be provided in a processor, for example, as: a processor comprises a request module, a message module, an acquisition module and a second receiving module, wherein the names of these modules do not constitute a limitation of the module itself in some cases.
As another aspect, the present invention also provides a computer-readable medium that may be contained in the apparatus described in the above embodiments; or may be present alone without being fitted into the device. The computer readable medium carries one or more programs which, when executed by a device, implement the method of: receiving a multicast group joining request sent by a front end, wherein the multicast group joining request carries a target cloud host identifier and a target multicast group identifier; adding the target cloud host into the target multicast group to enable the target cloud host to become a multicast member of the target multicast group; updating the member information added to the target multicast group to multicast topology data in a database, and sending a data update message to the front end, so that the front end displays the multicast topology data on the front end after acquiring the multicast topology data from the database; the data update message carries the data identifier of the multicast topology data in the database.
As another aspect, the present invention also provides a computer-readable medium that may be contained in the apparatus described in the above embodiments; or may be present alone without being fitted into the device. The computer readable medium carries one or more programs which, when executed by a device, implement the method of: sending a multicast group joining request to a multicast gateway, wherein the multicast group joining request carries a target cloud host identifier and a target multicast group identifier; receiving a data update message sent by the multicast gateway, wherein the data update message carries a data identifier of multicast topology data in a database; sending a topology data acquisition request to the database, wherein the topology data acquisition request carries the data identifier; and receiving multicast topology data corresponding to the data identification returned by the database, and displaying the multicast topology data at the front end.
As a further aspect, embodiments of the present invention also provide a computer program product comprising a computer program which, when executed by a processor, implements the method according to any of the above embodiments.
According to the technical scheme of the embodiment of the invention, the technical means that the multicast topology data is acquired and displayed by the front end from the database because the multicast topology data of the target multicast group is updated to the multicast topology data in the database and the data update message is sent to the front end is adopted, so that the technical problem that if the multicast member fails to join the multicast group but a user does not feel in the prior art is solved. The embodiment of the invention directly manages the multicast members through the front-end page, and comprises the step of checking whether the multicast members successfully join the multicast group, whether the multicast members join the correct multicast group, the step of displaying the multicast members of each multicast group and the like, so that the user has perception.
The above embodiments do not limit the scope of the present invention. It will be apparent to those skilled in the art that various modifications, combinations, sub-combinations and alternatives can occur depending upon design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included in the scope of the present invention.
Claims (11)
1. A method for managing multicast topology data, applied to a multicast gateway, comprising:
Receiving a multicast group joining request sent by a front end, wherein the multicast group joining request carries a target cloud host identifier and a target multicast group identifier;
adding the target cloud host into the target multicast group to enable the target cloud host to become a multicast member of the target multicast group;
updating the member information added to the target multicast group to multicast topology data in a database, and sending a data update message to the front end, so that the front end displays the multicast topology data on the front end after acquiring the multicast topology data from the database; the data update message carries the data identifier of the multicast topology data in the database.
2. The method as recited in claim 1, further comprising:
receiving a multicast group leaving request sent by the front end, wherein the multicast group leaving request carries the target cloud host identifier and the target multicast group identifier;
deleting the target cloud host from the target multicast group;
updating the leaving member information of the target multicast group to the multicast topology data in the database, and sending a data update message to the front end.
3. The method according to claim 1 or 2, wherein updating the joining member information of the target multicast group to multicast topology data in a database comprises:
updating the joining member information of the target multicast group to multicast topology data in any node in a redis cluster so that the node synchronizes the updated multicast topology data to other nodes in the redis cluster;
wherein, key is the data identification of the multicast topology data in the redis cluster, and value is the multicast topology data.
4. The method of claim 1, wherein the multicast topology data includes details of each multicast group including a multicast address, a number of multicast members that have been added, a cloud host identity corresponding to each multicast member, a maximum number of joinable multicast members, and a number of remaining joinable multicast members.
5. A method for managing multicast topology data, applied to a front end, comprising:
sending a multicast group joining request to a multicast gateway, wherein the multicast group joining request carries a target cloud host identifier and a target multicast group identifier;
Receiving a data update message sent by the multicast gateway, wherein the data update message carries a data identifier of multicast topology data in a database;
sending a topology data acquisition request to the database, wherein the topology data acquisition request carries the data identifier;
and receiving multicast topology data corresponding to the data identification returned by the database, and displaying the multicast topology data at the front end.
6. The method according to claim 5, wherein receiving the multicast topology data corresponding to the data identifier returned by the database, and displaying the multicast topology data at the front end, comprises:
receiving multicast topology data corresponding to the data identification returned by the database;
judging whether the locally stored multicast topology data is consistent with the multicast topology data returned by the database;
if yes, displaying the locally stored multicast topology data at the front end, and generating an alarm log, wherein the content of the alarm log is that the multicast topology data is not updated;
if not, the multicast topology data returned by the database is displayed at the front end, and the multicast topology data returned by the database is updated to the local.
7. An apparatus for managing multicast topology data, the apparatus being disposed in a multicast gateway, comprising:
the first receiving module is used for receiving a multicast group joining request sent by the front end, wherein the multicast group joining request carries a target cloud host identifier and a target multicast group identifier;
the processing module is used for adding the target cloud host into the target multicast group to enable the target cloud host to become a multicast member of the target multicast group;
the updating module is used for updating the joining member information of the target multicast group to the multicast topology data in the database, and sending a data updating message to the front end so that the front end can display the multicast topology data on the front end after acquiring the multicast topology data from the database; the data update message carries the data identifier of the multicast topology data in the database.
8. An apparatus for managing multicast topology data, disposed at a front end, comprising:
the request module is used for sending a multicast group joining request to the multicast gateway, wherein the multicast group joining request carries a target cloud host identifier and a target multicast group identifier;
the message module is used for receiving a data update message sent by the multicast gateway, wherein the data update message carries a data identifier of multicast topology data in a database;
The acquisition module is used for sending a topology data acquisition request to the database, wherein the topology data acquisition request carries the data identifier;
and the second receiving module is used for receiving the multicast topology data corresponding to the data identifier returned by the database and displaying the multicast topology data at the front end.
9. An electronic device, comprising:
one or more processors;
storage means for storing one or more programs,
the one or more processors implement the method of any of claims 1-7 when the one or more programs are executed by the one or more processors.
10. A computer readable medium, on which a computer program is stored, characterized in that the program, when being executed by a processor, implements the method according to any of claims 1-7.
11. A computer program product comprising a computer program which, when executed by a processor, implements the method according to any of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311152941.2A CN117135003A (en) | 2023-09-07 | 2023-09-07 | Method and device for managing multicast topology data |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311152941.2A CN117135003A (en) | 2023-09-07 | 2023-09-07 | Method and device for managing multicast topology data |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117135003A true CN117135003A (en) | 2023-11-28 |
Family
ID=88858138
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311152941.2A Pending CN117135003A (en) | 2023-09-07 | 2023-09-07 | Method and device for managing multicast topology data |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117135003A (en) |
-
2023
- 2023-09-07 CN CN202311152941.2A patent/CN117135003A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112860451A (en) | Multi-tenant data processing method and device based on SaaS | |
| US10958735B2 (en) | Client connection method and system | |
| US10972564B2 (en) | System and method for automating actions in distributed computing | |
| CN110851468A (en) | Method and device for making simulation response to test request of client | |
| CN106470150B (en) | Relation chain storage method and device | |
| CN111258627A (en) | Interface document generation method and device | |
| CN111917687A (en) | Method and device for circularly pushing reminding message | |
| JP7367120B2 (en) | Dynamic object update subscription based on user interaction with interfaces | |
| US20080034008A1 (en) | User side database | |
| CN110324384B (en) | Data pushing method and device | |
| CN107634942B (en) | Method and device for identifying malicious request | |
| CN112948138A (en) | Method and device for processing message | |
| CN113609516B (en) | Information generation method and device based on abnormal user, electronic equipment and medium | |
| CN117135003A (en) | Method and device for managing multicast topology data | |
| CN112257039B (en) | Identity attribute adding method and device and electronic equipment | |
| CN112306791B (en) | Performance monitoring method and device | |
| CN115086347A (en) | Data synchronization method and device, electronic equipment and storage medium | |
| CN113742617A (en) | Cache updating method and device | |
| CN114417318A (en) | Third-party page jumping method and device and electronic equipment | |
| CN109087097B (en) | Method and device for updating same identifier of chain code | |
| CN113553206A (en) | Data event execution method and device, electronic equipment and computer readable medium | |
| CN113760343A (en) | Method and device for processing service request | |
| CN113132447A (en) | Reverse proxy method and system | |
| CN115309612B (en) | Method and device for monitoring data | |
| CN112448931B (en) | Network hijacking monitoring method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |