CN115623253B - Scene-aware video stream management method, system, device, and medium - Google Patents
Scene-aware video stream management method, system, device, and medium Download PDFInfo
- Publication number
- CN115623253B CN115623253B CN202211532919.6A CN202211532919A CN115623253B CN 115623253 B CN115623253 B CN 115623253B CN 202211532919 A CN202211532919 A CN 202211532919A CN 115623253 B CN115623253 B CN 115623253B
- Authority
- CN
- China
- Prior art keywords
- low
- authority
- multicast
- multicast group
- video stream
- 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.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/25—Management operations performed by the server for facilitating the content distribution or administrating data related to end-users or client devices, e.g. end-user or client device authentication, learning user preferences for recommending movies
- H04N21/266—Channel or content management, e.g. generation and management of keys and entitlement messages in a conditional access system, merging a VOD unicast channel into a multicast channel
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/25—Management operations performed by the server for facilitating the content distribution or administrating data related to end-users or client devices, e.g. end-user or client device authentication, learning user preferences for recommending movies
- H04N21/258—Client or end-user data management, e.g. managing client capabilities, user preferences or demographics, processing of multiple end-users preferences to derive collaborative data
- H04N21/25866—Management of end-user data
- H04N21/25891—Management of end-user data being end-user preferences
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client
- H04N21/63—Control signaling related to video distribution between client, server and network components; Network processes for video distribution between server and clients or between remote clients, e.g. transmitting basic layer and enhancement layers over different transmission paths, setting up a peer-to-peer communication via Internet between remote STB's; Communication protocols; Addressing
- H04N21/631—Multimode Transmission, e.g. transmitting basic layers and enhancement layers of the content over different transmission paths or transmitting with different error corrections, different keys or with different transmission protocols
Abstract
The embodiment of the invention discloses a scene-aware video stream management method, a scene-aware video stream management system, a scene-aware video stream management device and a scene-aware video stream management medium. Wherein, the method comprises the following steps: receiving a joining message carrying a low-authority identifier sent by a low-authority multicast group member; determining a target output interface corresponding to a low-authority multicast group member in the candidate output interfaces of the multicast list item according to the adding message carrying the low-authority identification, and adding the low-authority identification to the target output interface; after receiving the multicast video stream carrying the authority limit identification, forwarding a preset authority limit image to a target output interface added with a low authority limit identification, and normally forwarding the multicast video stream to other output interfaces in the multicast list item; wherein, the other output interfaces refer to candidate output interfaces without low-authority identification added in the multicast list item. According to the technical scheme, different video stream processing measures can be adopted for the clients with different authorities, the network bandwidth is effectively saved, the network resource occupation is reduced, and meanwhile, the user experience is improved so as to better meet the actual requirements.
Description
Technical Field
The present invention relates to the field of video management technologies, and in particular, to a method, a system, a device, and a medium for scene-aware video stream management.
Background
In the field of video monitoring, the method can realize great reduction of video monitoring total flow and optimization of paths through a multicast mode. However, when sensitive content occurs in a monitoring scene, such as content of a specific limited scene, the monitoring camera scrambles the monitoring picture. Since different viewers have different rights, viewers with low rights cannot view the content, and viewers with non-low rights (normal rights and high rights) can view the content. Therefore, how to implement differential display of video content and traffic saving in a video multicast mode is one of the issues worth paying attention to in the current video management technology.
In the related art, a monitoring picture containing sensitive content is uniformly scrambled by a camera, and is descrambled by a client according to respective authority. However, the multicast video stream in this scheme does not distinguish client permissions, and the multicast video stream will be received by the client without permission, which wastes network bandwidth and causes network resource occupation. In addition, the video stream needs to be descrambled by the client side, so that the user experience is poor, and the actual requirements cannot be well met.
Disclosure of Invention
The invention provides a scene-aware video stream management method, a scene-aware video stream management system, a scene-aware video stream management device and a scene-aware video stream management medium, which can adopt different video stream processing measures for clients with different authorities, effectively save network bandwidth, reduce network resource occupation, and improve user experience so as to better meet actual requirements.
According to an aspect of the present invention, there is provided a scene-aware video stream management method performed by a gateway router connecting multicast group members, comprising:
receiving a joining message carrying a low-authority identification sent by a low-authority multicast group member;
determining a target output interface corresponding to the low-authority multicast group member in the candidate output interfaces of the multicast list items according to the join message carrying the low-authority identification, and adding the low-authority identification to the target output interface;
after receiving a multicast video stream carrying an authority limit identifier, forwarding a preset authority limit image to a target output interface added with the low authority limit identifier, and normally forwarding the multicast video stream to other output interfaces in the multicast list item; the other outgoing interfaces refer to candidate outgoing interfaces which are not added with low-authority identifiers in the multicast table entry.
According to another aspect of the invention, there is provided a scene aware video stream management system comprising:
the video acquisition device is used for acquiring multicast video streams, adding authority limit identifications to the multicast video streams according to content identification results in the multicast video streams, sending the multicast video streams carrying the authority limit identifications in a multicast mode, and sending authority limit notifications to a server;
the server side determines a low-authority multicast group member according to the authority limit notification sent by the video acquisition device and sends a low-authority identification adding notification to the low-authority multicast group member;
the low-authority multicast group member periodically sends a joining message carrying the low-authority identification to a correspondingly connected gateway router according to the low-authority identification adding notice sent by the server;
the gateway router determines a target output interface corresponding to the low-authority multicast group member in the candidate output interfaces of the multicast list item according to the received join message carrying the low-authority identification sent by the low-authority multicast group member, and adds the low-authority identification to the target output interface; and forwarding the multicast video stream carrying the permission limitation identifier to other outgoing interfaces which are not added with the low permission identifier in the candidate outgoing interfaces of the multicast table item, and forwarding a preset permission limitation image to the target outgoing interface added with the low permission identifier.
According to another aspect of the invention, there is provided a scene-aware video stream management electronic device, the electronic device comprising:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,
the memory stores a computer program executable by the at least one processor to enable the at least one processor to perform the method of scene aware video stream management according to any embodiment of the invention.
According to another aspect of the present invention, there is provided a computer-readable storage medium having stored thereon computer instructions for causing a processor to, when executed, implement a scene-aware video stream management method according to any one of the embodiments of the present invention.
According to the technical scheme of the embodiment of the invention, a gateway router connected with multicast group members receives a join message carrying a low-authority identifier sent by a low-authority multicast group member; determining a target output interface corresponding to a low-authority multicast group member in the candidate output interfaces of the multicast list item according to the adding message carrying the low-authority identification, and adding the low-authority identification to the target output interface; after receiving the multicast video stream carrying the authority limit identification, forwarding a preset authority limit image to a target output interface added with a low authority limit identification, and normally forwarding the multicast video stream to other output interfaces in the multicast list item; wherein, the other output interfaces refer to candidate output interfaces without low-authority identifiers added in the multicast table entry. According to the technical scheme, different video stream processing measures can be adopted for the clients with different authorities, the network bandwidth is effectively saved, the network resource occupation is reduced, and meanwhile, the user experience is improved so as to better meet the actual requirements.
It should be understood that the statements in this section are not intended to identify key or critical features of the embodiments of the present invention, nor are they intended to limit the scope of the invention. Other features of the present invention will become apparent from the following description.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a flowchart of a scene-aware video stream management method according to an embodiment of the present invention;
fig. 2 is a flowchart of a scene-aware video stream management method according to a second embodiment of the present invention;
fig. 3A is a schematic diagram illustrating an information list of an IP of a client IP-gateway router according to a second embodiment of the present invention;
fig. 3B is a schematic diagram of an information list of an account-permission-IP address of the client PC according to the second embodiment of the present invention;
fig. 4 is a schematic diagram illustrating a connection between a gateway router and a corresponding multicast group member according to a second embodiment of the present invention;
fig. 5 is a schematic structural diagram of a scene-aware video stream management system according to a third embodiment of the present invention;
fig. 6 is a schematic structural diagram of an electronic device implementing a scene-aware video stream management method according to an embodiment of the present invention.
Detailed Description
In order to make the technical solutions of the present invention better understood, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
It should be noted that the terms "first," "second," "target," and the like in the description and claims of the present invention and in the above-described drawings are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the invention described herein are capable of operation in sequences other than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
Example one
Fig. 1 is a flowchart of a scene-aware video stream management method according to an embodiment of the present invention, where the method is applicable to efficiently managing a multicast video stream, and the method may be executed by a gateway router connected to multicast group members, where the gateway router may be configured in a scene-aware video stream management system. As shown in fig. 1, the method includes:
and S110, receiving a joining message carrying a low-authority identification sent by a low-authority multicast group member.
The multicast may refer to an information transmission method for performing network communication between a sender and a plurality of receivers, and the method allows the multicast to forward a received multicast stream to the plurality of receivers through a destination address. The low-authority multicast group member may refer to a client having a low authority among clients participating in multicast, and the low-authority client refers to a client prohibited from watching a video containing a target scene content. The join message with the low-permission identifier may be an IGMP (Internet Group Management Protocol) join message with a low-permission identifier, and may be used for a low-permission multicast Group member to notify a gateway router that the low-permission multicast Group member has a low permission. Wherein, the low authority identifier can be used to represent that the multicast group member has low authority. The gateway router is used for connecting each multicast group member. The multicast group member may include at least one of a low-authority multicast group member, a normal-authority multicast group member, and a high-authority multicast group member.
In this embodiment, optionally, the low-permission multicast group member periodically sends the join message carrying the low-permission identifier according to the low-permission identifier addition notification sent by the server. The low-authority identifier adding notification can be used for the server side to notify the low-authority multicast group members to send the adding information carrying the low-authority identifier to the gateway router.
In this embodiment, when the video capture device (e.g., a camera) recognizes that the monitored picture contains the restricted scene content, an authority restriction notification may be sent to the server to notify that the server is about to send the multicast video stream containing the restricted scene content. After receiving the permission limitation notification sent by the video acquisition device, the server searches low-permission multicast group members in all multicast group members, and sends a low-permission identifier addition notification to the low-permission multicast group members so as to notify the low-permission multicast group members to send a join message carrying the low-permission identifier to the gateway router. After receiving the low-permission identifier addition notification sent by the server, the low-permission multicast group member may periodically send an addition message carrying the low-permission identifier to the gateway router to notify the gateway router that the low-permission multicast group member has low permission.
And S120, determining a target output interface corresponding to the low-authority multicast group member in the candidate output interfaces of the multicast list item according to the join message carrying the low-authority identifier, and adding the low-authority identifier to the target output interface.
The multicast table entry may refer to a multicast routing table entry (S, G) established by a PIM protocol, and may be applied to establish a shortest path tree in a PIM network. The PIM (Protocol Independent Multicast) may refer to a Protocol for Multicast forwarding of a router, where S denotes a Multicast source and G denotes a Multicast group. Specifically, the multicast table entry is composed of an ingress interface and an egress interface, and may be used to describe a connection relationship between the ingress interface and the egress interface. Wherein, one input interface can be correspondingly connected with a plurality of output interfaces. On the ingress interface, the router may prevent loops by running RPF (reverse path forwarding) checks. Specifically, the comparison is performed according to the last source address and the next hop of the route with the destination as the multicast source in the unicast routing table, if the next hop is the same as the last hop of the multicast data source, the RPF check is successful, otherwise, the RPF check is failed, and the corresponding ingress interface is deleted if the RPF check is failed. In the exit direction, the multicast video stream can be forwarded to the multicast group members by running between the gateway router and the multicast group members through an IGMP protocol, and determining whether the multicast group members exist on each exit interface. And after receiving the multicast video stream sent to the multicast group G, the gateway router forwards the multicast video stream only to the outgoing interfaces corresponding to the members with the multicast group G. The candidate interface may refer to any outgoing interface in the multicast table entry. The target outgoing interface may be an outgoing interface corresponding to a low-permission multicast group member in the candidate interfaces.
In this embodiment, after receiving the join message carrying the low-permission identifier sent by the low-permission multicast group member, the gateway router may determine, according to the join message carrying the low-permission identifier, a target outgoing interface corresponding to the low-permission multicast group member in the candidate outgoing interfaces of the multicast entry, and add the low-permission identifier to the target outgoing interface. It should be noted that the gateway router knows the connection relationship between the multicast group members and each output interface in advance, so that when receiving the join message with the low-permission identifier sent by the low-permission multicast group members, the gateway router can determine the target output interface corresponding to the low-permission multicast group members from the candidate output interfaces according to the join message with the low-permission identifier. In addition, for the output interface added with the low-authority identifier, the multicast group members corresponding to the output interface comprise low-authority multicast group members; for an outgoing interface without a low-authority identifier, the multicast group members corresponding to the outgoing interface do not include a low-authority multicast group member, that is, the multicast group members corresponding to the outgoing interface only include normal-authority multicast group members and/or high-authority multicast group members.
S130, after receiving the multicast video stream carrying the authority limit identifier, forwarding a preset authority limit image to the target output interface added with the low authority limit identifier, and normally forwarding the multicast video stream to other output interfaces in the multicast list item; wherein, the other output interfaces refer to candidate output interfaces without low-authority identification added in the multicast list item.
Wherein, the permission limitation identifier can be used to characterize that the multicast video stream has permission limitation. Specifically, the low-authority multicast group member does not have the viewing authority of the multicast video stream, and the normal-authority multicast group member and the high-authority multicast group member have the viewing authority of the multicast video stream. The preset authority limit image may refer to a preset display image corresponding to the image with the authority limit. Illustratively, the preset authority limit image may be a mosaic image. The other outgoing interfaces may refer to candidate outgoing interfaces to which the low-privilege identifier is not added in the multicast entry.
In this embodiment, after receiving the multicast video stream carrying the permission restriction identifier, the gateway router may forward a preset permission restriction image to the target output interface to which the low permission identifier is added, so as to prohibit the low permission multicast group members from normally viewing the multicast video stream, and normally forward the multicast video stream to other output interfaces to which the low permission identifier is not added in the multicast entry, thereby ensuring that normal permission multicast group members and high permission multicast group members other than the low permission multicast group members can normally view the multicast video stream.
According to the technical scheme of the embodiment of the invention, a gateway router connected with multicast group members receives a join message carrying a low-authority identifier sent by a low-authority multicast group member; determining a target output interface corresponding to a low-authority multicast group member in the candidate output interfaces of the multicast list item according to the adding message carrying the low-authority identification, and adding the low-authority identification to the target output interface; after receiving the multicast video stream carrying the authority limit identification, forwarding a preset authority limit image to a target output interface added with a low authority limit identification, and normally forwarding the multicast video stream to other output interfaces in the multicast list item; wherein, the other output interfaces refer to candidate output interfaces without low-authority identifiers added in the multicast table entry. According to the technical scheme, different video stream processing measures can be adopted for the clients with different authorities, the network bandwidth is effectively saved, the network resource occupation is reduced, and meanwhile, the user experience is improved so as to better meet the actual requirements.
In this embodiment, optionally, after adding the low-privilege identifier to the target outgoing interface, the method further includes: judging whether non-low-authority multicast group members exist in all multicast group members connected with a target output interface; if the multicast video stream exists, determining the unicast address of the multicast video stream according to the first address information of the non-low-authority multicast group member.
The non-low-authority multicast group member may refer to a multicast group member other than the low-authority multicast group member, and specifically may include a normal-authority multicast group member and/or a high-authority multicast group member. The first address information may refer to an IP (Internet Protocol) address of a non-low-authority multicast group member. It should be noted that, since one or more non-low-authority multicast group members may exist in all multicast group members connected to the target outgoing interface, the first address information may correspondingly include one or more IP addresses. The unicast address may refer to a corresponding IP address of the non-low-permission multicast group member when unicast is established for each non-low-permission multicast group member. The unicast may refer to an information transmission method for performing network communication between one sender and one receiver, that is, a point-to-point connection between a server and a multicast group member may be implemented.
In this embodiment, after the low-permission identifier is added to the target outgoing interface, it may be further determined whether non-low-permission multicast group members exist in all multicast group members connected to the target outgoing interface. If the multicast video stream exists, in order to not affect normal viewing of the multicast video stream by the non-low-authority multicast group member, a unicast needs to be established for the non-low-authority multicast group member, and a unicast address of the multicast video stream can be specifically determined according to the first address information of the non-low-authority multicast group member. It should be noted that one outgoing interface may be correspondingly connected to multiple multicast group members, and as long as one of the multicast group members belongs to a low-permission multicast group member, the outgoing interface may be determined as a target outgoing interface, and a low-permission identifier is added to the target outgoing interface. At this time, the gateway router forwards the preset authority limit image to all multicast group members connected to the target output interface, and establishes unicast for the non-low authority multicast group members connected to the target output interface. In this case, the low-permission multicast group member connected to the target output interface only receives the preset-permission-limited image, and the non-low-permission multicast group member connected to the target output interface simultaneously receives the preset-permission-limited image and the normal multicast video stream. At this time, the non-low-permission multicast group member connected to the target output interface may determine that the non-low-permission multicast group member connected to the target output interface finally displays a normal multicast video stream according to a preset priority (the priority of the multicast video stream is set to be higher than the preset permission limiting image), so as to ensure that the non-low-permission multicast group member can normally view the multicast video stream.
According to the scheme, the multicast video stream can be prohibited from being normally watched by the low-authority multicast group members, so that the network bandwidth is saved, and meanwhile, the multicast video stream can be normally watched by the non-low-authority multicast group members, so that the user experience is improved, and the actual demand can be better met.
In this embodiment, optionally, after adding the low-permission identifier to the target output interface, the method further includes: judging whether a target output interface of the multicast table item is connected with a non-low-authority multicast group member or not; and if the multicast list item does not exist, sending a second join message carrying the low-authority identifier to the upstream router through the input interface of the multicast list item, so that the upstream router cancels forwarding of the multicast video stream carrying the authority limit identifier to the gateway router according to the second join message carrying the low-authority identifier.
The second join message with the low-authority identifier may refer to a PIM join message with the low-authority identifier, and may be used to inform, by the gateway router, the upstream router that the low-authority multicast group member under the gateway router has low authority.
In this embodiment, after adding the low-permission identifier to the target outgoing interface, it is further required to determine whether the target outgoing interface of the multicast entry is connected to a non-low-permission multicast group member. If the multicast list item does not exist, the target output interface connection is all low-authority multicast group members, and at the moment, a second joining message carrying low-authority identification can be sent to the upstream router through the input interface of the multicast list item so as to inform the upstream router that the target output interface connection is all low-authority multicast group members. After the upstream router receives the second join message carrying the low-permission identifier sent by the gateway router, it needs to further determine whether the upstream router is connected to other gateway routers.
If the upstream router is not connected with other gateway routers, the upstream router can forward the multicast video stream carrying the permission limitation identifier to the gateway router according to the second join message carrying the low permission identifier, so that the network bandwidth is saved, and the network resource occupation is reduced. If the upstream router is connected with other gateway routers, and the outgoing interface connections corresponding to the other gateway routers are all low-authority multicast group members, the upstream router can cancel forwarding of multicast video streams carrying authority limit identifications to all gateway routers connected with the upstream router according to the second low-authority-carrying identification adding message; if the upstream router is connected with other gateway routers, but the outgoing interface connections corresponding to other gateway routers are not all low-authority multicast group members, that is, there are non-low-authority multicast group members in the multicast group members connected to the outgoing interfaces corresponding to other gateway routers, at this moment, the upstream router needs to forward the multicast video stream carrying the authority limit identifier to each connected gateway router, and subsequently, according to the actual authority of the multicast group members corresponding to the outgoing interface connections, the upstream router determines whether to forward the multicast video stream to the corresponding multicast group members and whether to establish unicast.
According to the scheme, when the target output interface of the multicast table entry is determined not to be connected with the non-low-authority multicast group member, the second join message carrying the low-authority identifier is sent to the upstream router, so that the upstream router cancels forwarding of the multicast video stream carrying the authority limit identifier to the gateway router according to the second join message carrying the low-authority identifier, the network bandwidth is further saved, and the network resource occupation is reduced.
In this embodiment, optionally, after adding the low-privilege identifier to the target outgoing interface, the method further includes: and after receiving the join message carrying the non-low-authority identification sent by all the multicast group members connected with the target output interface, canceling the low-authority identification added to the target output interface.
In this embodiment, after adding the low-permission identifier to the target output interface, after receiving the join message carrying the non-low-permission identifier sent by all multicast group members connected to the target output interface, the low-permission identifier added to the target output interface may be cancelled, so that the target output interface normally receives the multicast video stream forwarded by the gateway router, and thus all multicast group members connected to the target output interface can normally watch the multicast video stream. The multicast group member switches the non-low-authority identification carried in the joining message into a non-low-authority account number and then periodically sends the non-low-authority identification carried in the joining message. After the low-authority multicast group member is switched to the non-low-authority account, a join message carrying a non-low-authority identifier can be periodically sent to the gateway router to inform the gateway router that the low-authority multicast group member is converted into a non-low-authority multicast group member.
It should be noted that the gateway router may cancel the low-permission identifier added to the target outgoing interface only if all multicast group members connected to the target outgoing interface send a join message carrying the non-low-permission identifier to the gateway router, that is, all multicast group members connected to the target outgoing interface are non-low-permission multicast group members. The gateway router will not cancel the low-authority identifier added to the target output interface as long as there are low-authority multicast group members in all multicast group members connected to the target output interface.
According to the scheme, the gateway router can cancel the low-authority identification added to the target output interface after receiving the non-low-authority identification adding message sent by all multicast group members connected with the target output interface, so that the target output interface can normally receive the multicast video stream forwarded by the gateway router, and all multicast group members connected with the target output interface can normally watch the multicast video stream.
Example two
Fig. 2 is a flowchart of a scene-aware video stream management method according to a second embodiment of the present invention, which is optimized based on the second embodiment. The concrete optimization is as follows: before determining a target output interface corresponding to a low-permission multicast group member in the candidate output interfaces of the multicast table item according to the join message carrying the low-permission identifier, the method further comprises the following steps: acquiring second address information of a low-authority multicast group member sent by a server; the second address information is determined by the server side according to the member registration information; and determining a target output interface corresponding to the low-authority multicast group member in the candidate output interfaces of the multicast list item according to the second address information.
As shown in fig. 2, the method of this embodiment specifically includes the following steps:
s210, acquiring second address information of a low-authority multicast group member sent by a server; and the second address information is determined by the server side according to the member registration information.
The second address information may refer to an IP address of a low-permission multicast group member. Specifically, the second address information may be determined by the server according to the member registration information.
In this embodiment, in order to avoid setting an access control list by a multicast group member, after receiving a low-permission identifier addition notification sent by a server, a problem that the low-permission multicast group member continues to receive a multicast video stream containing restricted scene content by prohibiting the low-permission multicast group member from sending a low-permission identifier addition message to a gateway router is caused, and second address information of the low-permission multicast group member may be sent to the gateway router through the server, so that the gateway router adds a low-permission identifier to a target output interface corresponding to the low-permission multicast group member according to the received second address information of the low-permission multicast group member.
For example, each client PC (Personal Computer) needs to add its own gateway router IP address to registration information when registering with the server. After receiving the registration information, the server maintains two information lists locally at the server. One of them is an information list (as shown in fig. 3A) describing the correspondence between the client IP and the gateway router IP, and the other is an information list (as shown in fig. 3B) describing the correspondence between the account number, the authority, and the IP address of the client PC where the account number, the authority, and the gateway router IP are located. After receiving the permission limitation notification sent by the video acquisition device, the server can check all currently online low-permission accounts, and determine the IP addresses of the client PCs where all the low-permission accounts are located from an account-permission-information list of the IP addresses of the client PCs where the low-permission accounts are located, wherein the IP addresses are used as second address information of the members of the low-permission multicast group. And the server side can further determine a gateway router IP address corresponding to second address information (client IP) of the low-authority multicast group member through the information list of the client IP-gateway router IP, and sends the second address information to the corresponding gateway router.
S220, determining a target output interface corresponding to the low-authority multicast group member in the candidate output interfaces of the multicast list item according to the second address information, and adding a low-authority identifier to the target output interface.
In this embodiment, after the gateway router obtains the second address information of the low-permission multicast group member sent by the server, a target outgoing interface corresponding to the low-permission multicast group member in the candidate outgoing interfaces of the multicast table entry may be determined according to the second address information, and a low-permission identifier is added to the target outgoing interface. Fig. 4 is a schematic diagram illustrating a connection between a gateway router and a corresponding multicast group member according to a second embodiment of the present invention. As shown in fig. 4, an egress Interface-se:Sub>A of se:Sub>A Gateway router (Gateway-se:Sub>A) connects two multicast group members of PC-se:Sub>A and PC-B through se:Sub>A two-layer switch. For example, assume that the server determines, through the two information lists in fig. 3A and fig. 3B, that the client where the low-permission account User-se:Sub>A is located is PC-se:Sub>A, and determines that the Gateway router corresponding to PC-se:Sub>A is Gateway-se:Sub>A (whose corresponding outgoing Interface is Interface-se:Sub>A). And then, all multicast group members under the Interface-A corresponding to the IP address of the Gateway-A, such as PC-A and PC-B in FIG. 4, can be reversely determined from the information list of the IP of the client IP-Gateway router IP according to the IP address of the Gateway-A. Further, the running account numbers on the PC-A and the PC-B can be reversely determined from the information list of the account number, the authority number and the IP address of the client PC. Therefore, all multicast group members and accounts thereof under the same Gateway router Gateway-A as the PC-A can be obtained.
If no other PC is connected below the Gateway router Gateway-A connected with the PC-A or the other connected PCs are all PCs logged in by the low-authority account, the server side can inform the Gateway router Gateway-A to add se:Sub>A low-authority identifier to the target outgoing Interface-A corresponding to the PC-A in the multicast table entry. Under the condition, even if the PC-A does not send the joining message carrying the low authority limit identification to the Gateway router Gateway-A, the Gateway-A does not forward the multicast video stream carrying the authority limit identification to the PC-A through the destination outbound Interface-A.
If the PC-B logged in by the high authority account User-B is also connected below the Gateway router Gateway-A connected with the PC-A, the PC-B logged in by the high authority account and the PC-A logged in by the low authority account are connected with the Gateway router Gateway-A through the two-layer switch together. At the moment, in order to receive the multicast video stream containing the limited scene content by the PC-B which does not influence the login of the high-authority account number, the server side informs the Gateway router Gateway-A to add se:Sub>A low-authority identifier to the target output Interface-A corresponding to the PC-A in the multicast list item, establishes unicast for the PC-B, modifies the destination IP address of the multicast video stream into the unicast IP address of the PC-B, and directly sends the multicast video stream to the PC-B in se:Sub>A unicast mode. Therefore, only the PC-B logged in by the high-authority account can receive the multicast video stream containing the limited scene content, and the PC-A logged in by the low-authority account can only receive the preset authority limit image but cannot receive the multicast video stream containing the limited scene content, so that the low-authority multicast group members are prohibited from watching the multicast video stream while the non-low-authority multicast group members can watch the multicast video stream normally.
S230, after receiving the multicast video stream carrying the authority limit identifier, forwarding a preset authority limit image to the target output interface added with the low authority limit identifier, and normally forwarding the multicast video stream to other output interfaces in the multicast list item; wherein, the other output interfaces refer to candidate output interfaces without low-authority identification added in the multicast list item.
According to the technical scheme of the embodiment of the invention, second address information of a low-authority multicast group member sent by a server is obtained; the second address information is determined by the server side according to the member registration information; determining a target output interface corresponding to the low-authority multicast group member in the candidate output interfaces of the multicast list item according to the second address information, and adding a low-authority identifier to the target output interface; after receiving a multicast video stream carrying an authority limit identifier, forwarding a preset authority limit image to a target output interface added with the low authority limit identifier, and normally forwarding the multicast video stream to other output interfaces in the multicast list item; the other outgoing interfaces refer to candidate outgoing interfaces which are not added with low-authority identifiers in the multicast table entry. According to the technical scheme, different video stream processing measures can be adopted for clients with different authorities, network bandwidth is effectively saved, network resource occupation is reduced, user experience is improved, and meanwhile the problem that low-authority multicast group members continuously receive multicast video streams containing limited scene contents due to the fact that the low-authority multicast group members are prohibited to send messages carrying low-authority identifications to a gateway router can be effectively avoided.
EXAMPLE III
Fig. 5 is a schematic structural diagram of a scene-aware video stream management system according to a third embodiment of the present invention, which is capable of executing a scene-aware video stream management method according to any embodiment of the present invention, and has corresponding functional modules and beneficial effects of the execution method. As shown in fig. 5, the system includes:
the video acquisition device is used for acquiring the multicast video stream, adding an authority limit identifier for the multicast video stream according to the content identification result in the multicast video stream, sending the multicast video stream carrying the authority limit identifier in a multicast mode, and sending an authority limit notice to the server;
the server side determines the low-authority multicast group members according to the authority limit notification sent by the video acquisition device and sends a low-authority identification adding notification to the low-authority multicast group members;
the low-authority multicast group member periodically sends a joining message carrying the low-authority identification to a correspondingly connected gateway router according to the low-authority identification adding notice sent by the server;
the gateway router determines a target output interface corresponding to the low-authority multicast group member in the candidate output interfaces of the multicast list item according to the received low-authority identification adding message sent by the low-authority multicast group member, and adds the low-authority identification to the target output interface; and forwarding the multicast video stream carrying the permission limit identifier to other output interfaces which are not added with the low permission identifier in the candidate output interfaces of the multicast table item, and forwarding a preset permission limit image to the target output interface added with the low permission identifier.
In this embodiment, a video capture device (e.g., a camera) first captures a multicast video stream and performs content recognition on the multicast video stream. When the video acquisition device identifies that the monitoring picture contains the limited scene content, the video acquisition device can add an authority limit identifier to the multicast video stream to indicate that the multicast video stream has authority limit, and send the multicast video stream carrying the authority limit identifier in a multicast mode, and simultaneously send an authority limit notification to the server to inform the server that the multicast video stream containing the limited scene content is about to be sent. After receiving the permission limitation notification sent by the video acquisition device, the server can search low-permission multicast group members from all multicast group members, and send a low-permission identification addition notification to the low-permission multicast group members so as to notify the low-permission multicast group members to send a join message carrying the low-permission identification to the gateway router. After receiving the low-permission identifier addition notification sent by the server, the low-permission multicast group member can periodically send a join message carrying the low-permission identifier to the correspondingly connected gateway router so as to inform the gateway router that the low-permission multicast group member has low permission.
After receiving a join message carrying a low-authority identifier sent by a low-authority multicast group member, a gateway router firstly determines a target output interface corresponding to the low-authority multicast group member in candidate output interfaces of a multicast table item, and adds the low-authority identifier to the target output interface. Then judging whether non-low-authority multicast group members exist in all multicast group members connected with the target output interface, if so, in order to ensure that the non-low-authority multicast group members can normally receive the multicast video stream, determining a unicast address of the multicast video stream according to first address information of the non-low-authority multicast group members, and establishing unicast for the non-low-authority multicast group members according to the unicast address; if not, it indicates that all multicast group members connected with the target output interface are low-authority multicast group members, and at this time, a second join message carrying a low-authority identifier can be sent to the upstream router through the input interface of the multicast table entry, and whether the upstream router is connected with other gateway routers is judged.
If the upstream router is not connected with other gateway routers, the upstream router cancels the forwarding of the multicast video stream carrying the authority limit identifier to the gateway router according to the second joining message carrying the low authority limit identifier, thereby saving the network bandwidth and reducing the network resource occupation. If the upstream router is connected with other gateway routers, and the outgoing interface connections corresponding to the other gateway routers are all low-authority multicast group members, the upstream router can cancel forwarding of multicast video streams carrying authority limit identifications to all gateway routers connected with the upstream router according to the second low-authority-carrying identification adding message; if the upstream router is connected with other gateway routers, but there are non-low-permission multicast group members in the multicast group members connected to the egress interfaces corresponding to the other gateway routers, the upstream router needs to forward the multicast video stream carrying the permission restriction identifier to each connected gateway router.
If the gateway router receives the join message carrying the non-low-authority identification sent by all multicast group members connected with the target output interface, the low-authority identification added to the target output interface can be cancelled, and when all the low-authority multicast group members connected with the target output interface become non-low-authority multicast group members through switching the login account number, the gateway router can forward multicast video streams to all the non-low-authority multicast group members through the target output interface. In addition, in order to avoid setting an access control list by multicast group members, after receiving a low-permission identifier addition notification sent by a server, prohibiting the low-permission multicast group members from sending a low-permission identifier addition message to a gateway router, so that the problem that the low-permission multicast group members continuously receive multicast video streams containing restricted scene content is caused, and second address information of the low-permission multicast group members can be sent to the gateway router through the server. After the gateway router acquires the second address information of the low-permission multicast group member sent by the server, a target output interface corresponding to the low-permission multicast group member in the candidate output interfaces of the multicast table item can be determined according to the second address information, and a low-permission identifier is added to the target output interface.
After receiving the multicast video stream carrying the permission limit identifier, the gateway router can forward a preset permission limit image to the target output interface added with the low permission identifier, and normally forward the multicast video stream to other output interfaces not added with the low permission identifier in the multicast list item, thereby ensuring that the low permission multicast group members cannot watch the multicast video stream containing the limited scene content, and meanwhile, the normal permission multicast group members and the high permission multicast group members except the low permission multicast group members can normally watch the multicast video stream containing the limited scene content.
The scene-aware video stream management system provided by the embodiment of the invention can execute the scene-aware video stream management method provided by any embodiment of the invention, and has corresponding functional modules and beneficial effects of the execution method.
Example four
FIG. 6 illustrates a block diagram of an electronic device 10 that may be used to implement an embodiment of the invention. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device may also represent various forms of mobile devices, such as personal digital assistants, cellular phones, smart phones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the inventions described and/or claimed herein.
As shown in fig. 6, the electronic device 10 includes at least one processor 11, and a memory communicatively connected to the at least one processor 11, such as a Read Only Memory (ROM) 12, a Random Access Memory (RAM) 13, and the like, wherein the memory stores a computer program executable by the at least one processor, and the processor 11 can perform various suitable actions and processes according to the computer program stored in the Read Only Memory (ROM) 12 or the computer program loaded from a storage unit 18 into the Random Access Memory (RAM) 13. In the RAM 13, various programs and data necessary for the operation of the electronic apparatus 10 can also be stored. The processor 11, the ROM 12, and the RAM 13 are connected to each other via a bus 14. An input/output (I/O) interface 15 is also connected to bus 14.
A number of components in the electronic device 10 are connected to the I/O interface 15, including: an input unit 16 such as a keyboard, a mouse, or the like; an output unit 17 such as various types of displays, speakers, and the like; a storage unit 18 such as a magnetic disk, an optical disk, or the like; and a communication unit 19 such as a network card, modem, wireless communication transceiver, etc. The communication unit 19 allows the electronic device 10 to exchange information/data with other devices via a computer network such as the internet and/or various telecommunication networks.
The processor 11 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various specialized Artificial Intelligence (AI) computing chips, various processors running machine learning model algorithms, a Digital Signal Processor (DSP), and any suitable processor, controller, microcontroller, or the like. The processor 11 performs the various methods and processes described above, such as a scene-aware video stream management method.
In some embodiments, the scene-aware video stream management method may be implemented as a computer program tangibly embodied in a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program may be loaded and/or installed onto the electronic device 10 via the ROM 12 and/or the communication unit 19. When the computer program is loaded into the RAM 13 and executed by the processor 11, one or more steps of the scene-aware video stream management method described above may be performed. Alternatively, in other embodiments, the processor 11 may be configured to perform the scene-aware video stream management method by any other suitable means (e.g., by means of firmware).
Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuitry, field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), system on a chip (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, receiving data and instructions from, and transmitting data and instructions to, a storage system, at least one input device, and at least one output device.
Computer programs for implementing the methods of the present invention can be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the computer programs, when executed by the processor, cause the functions/acts specified in the flowchart and/or block diagram block or blocks to be performed. A computer program can execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.
In the context of the present invention, a computer-readable storage medium may be a tangible medium that can contain, or store a computer program for use by or in connection with an instruction execution system, apparatus, or device. A computer readable storage medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. Alternatively, the computer readable storage medium may be a machine readable signal medium. More specific examples of a machine-readable storage medium would include an electrical connection based on 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 compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
To provide for interaction with a user, the systems and techniques described here can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) by which a user may provide input to the electronic device. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic, speech, or tactile input.
The systems and techniques described here can be implemented in a computing system that includes a back-end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), wide Area Networks (WANs), blockchain networks, and the internet.
The computing system may include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server can be a cloud server, also called a cloud computing server or a cloud host, and is a host product in a cloud computing service system, so that the defects of high management difficulty and weak service expansibility in the traditional physical host and VPS service are overcome.
It should be understood that various forms of the flows shown above, reordering, adding or deleting steps, may be used. For example, the steps described in the present invention may be executed in parallel, sequentially, or in different orders, and are not limited herein as long as the desired results of the technical solution of the present invention can be achieved.
The above-described embodiments should not be construed as limiting the scope of the invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may be made, depending on design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (9)
1. A method for scene-aware video stream management, performed by a gateway router connected to members of a multicast group, comprising:
receiving a joining message carrying a low-authority identification sent by a low-authority multicast group member; when a video acquisition device identifies that a monitoring picture contains limited scene content, sending an authority limit notification to a server, and after receiving the authority limit notification, the server sending a low authority identifier adding notification to the low authority multicast group member so that the low authority multicast group member sends the low authority identifier-carried adding message to the gateway router;
determining a target output interface corresponding to the low-authority multicast group member in the candidate output interfaces of the multicast list items according to the join message carrying the low-authority identification, and adding the low-authority identification to the target output interface;
after receiving a multicast video stream carrying an authority limit identifier, forwarding a preset authority limit image to a target output interface added with the low authority limit identifier, and normally forwarding the multicast video stream to other output interfaces in the multicast list item; the other outgoing interfaces refer to candidate outgoing interfaces which are not added with low-authority identifiers in the multicast list item, and the candidate outgoing interfaces refer to any outgoing interfaces in the multicast list item;
after adding the low-authority identifier to the target output interface, the method further comprises the following steps:
judging whether non-low-authority multicast group members exist in all multicast group members connected with the target output interface;
if the multicast video stream exists, determining a unicast address of the multicast video stream according to the first address information of the non-low-authority multicast group member, and establishing unicast for the non-low-authority multicast group member.
2. The method of claim 1, wherein after adding a low privilege identification to the target outgoing interface, the method further comprises:
judging whether a target output interface of the multicast table item is connected with a non-low-authority multicast group member or not;
and if the multicast list item does not exist, sending a second join message carrying the low-authority identifier to an upstream router through an input interface of the multicast list item, so that the upstream router cancels the forwarding of the multicast video stream carrying the authority limit identifier to the gateway router according to the second join message carrying the low-authority identifier.
3. The method of claim 1, wherein after adding a low privilege identification to the target outgoing interface, the method further comprises:
and after receiving join messages carrying non-low-authority identifiers sent by all multicast group members connected with the target output interface, canceling the low-authority identifiers added to the target output interface.
4. The method according to claim 1, wherein before determining a target outgoing interface corresponding to the low-permission multicast group member in the candidate outgoing interfaces of the multicast table entry according to the join message carrying the low-permission identifier, the method further comprises:
acquiring second address information of a low-authority multicast group member sent by a server; the second address information is determined by the server side according to member registration information;
and determining a target output interface corresponding to the low-authority multicast group member in the candidate output interfaces of the multicast list item according to the second address information.
5. The method according to claim 1, wherein the join message with low-privilege identifier is periodically sent by the low-privilege multicast group members according to a low-privilege identifier addition notification sent by a server.
6. The method of claim 3, wherein the join message carrying the non-low-privilege identifier is periodically sent after being switched to a non-low-privilege account by a multicast group member.
7. A scene aware video stream management system, comprising:
the video acquisition device is used for acquiring multicast video streams, adding authority limit identifications to the multicast video streams according to content identification results in the multicast video streams, sending the multicast video streams carrying the authority limit identifications in a multicast mode, and sending authority limit notifications to a server;
the server side determines a low-authority multicast group member according to the authority limit notification sent by the video acquisition device and sends a low-authority identification adding notification to the low-authority multicast group member;
the low-authority multicast group member periodically sends a joining message carrying the low-authority identification to a correspondingly connected gateway router according to the low-authority identification adding notice sent by the server;
the gateway router determines a target output interface corresponding to the low-authority multicast group member in the candidate output interfaces of the multicast list item according to the received join message carrying the low-authority identification sent by the low-authority multicast group member, and adds the low-authority identification to the target output interface; after receiving the multicast video stream carrying the authority limit identifier, forwarding the multicast video stream carrying the authority limit identifier to other outgoing interfaces which are not added with the low authority limit identifier in the candidate outgoing interfaces of the multicast table item, and forwarding a preset authority limit image to a target outgoing interface added with the low authority limit identifier; the candidate interface is any output interface in the multicast list item;
wherein the gateway router is further configured to:
after adding a low-authority identifier to the target output interface, judging whether non-low-authority multicast group members exist in all multicast group members connected with the target output interface;
if the multicast video stream exists, determining a unicast address of the multicast video stream according to the first address information of the non-low-authority multicast group member, and establishing unicast for the non-low-authority multicast group member.
8. A scene aware video stream management electronic device, the electronic device comprising:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,
the memory stores a computer program executable by the at least one processor to enable the at least one processor to perform the scene-aware video stream management method of any one of claims 1-6.
9. A computer-readable storage medium storing computer instructions for causing a processor to perform the method of scene aware video stream management of any of claims 1-6 when executed.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211532919.6A CN115623253B (en) | 2022-12-02 | 2022-12-02 | Scene-aware video stream management method, system, device, and medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211532919.6A CN115623253B (en) | 2022-12-02 | 2022-12-02 | Scene-aware video stream management method, system, device, and medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115623253A CN115623253A (en) | 2023-01-17 |
| CN115623253B true CN115623253B (en) | 2023-04-07 |
Family
ID=84879730
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211532919.6A Active CN115623253B (en) | 2022-12-02 | 2022-12-02 | Scene-aware video stream management method, system, device, and medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115623253B (en) |
Family Cites Families (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100454888C (en) * | 2004-03-06 | 2009-01-21 | 鸿富锦精密工业（深圳）有限公司 | System and method for multicast traffic control management |
| EP2034731A4 (en) * | 2006-06-09 | 2010-03-03 | Huawei Tech Co Ltd | Multicast service processing method and access equipment |
| EP2177010B1 (en) * | 2006-12-13 | 2015-10-28 | Quickplay Media Inc. | Mobile media platform |
| CN101052166B (en) * | 2007-05-23 | 2013-02-27 | 中兴通讯股份有限公司 | Region control method for multimedia broadcast and multicast business |
| CN101150425B (en) * | 2007-11-15 | 2010-10-13 | 中国电信股份有限公司 | Right control method for multicast service and Ethernet passive optical network system |
| CN101605103B (en) * | 2009-07-16 | 2012-01-04 | 杭州华三通信技术有限公司 | Method and apparatus for static forwarding multicast data |
| US8995439B2 (en) * | 2010-05-13 | 2015-03-31 | Comcast Cable Communications, Llc | Control of multicast content distribution |
| CN102377636B (en) * | 2010-08-06 | 2014-12-17 | 北京乾唐视联网络科技有限公司 | Service communication method of access network device and system thereof |
| CN102368707B (en) * | 2011-10-31 | 2013-06-12 | 华为技术有限公司 | Method, equipment and system for multicast control |
| CN102655458B (en) * | 2012-04-23 | 2015-10-14 | 浙江宇视科技有限公司 | A kind of multicast safety management method and multicast boundary control appliance |
| CN102905199B (en) * | 2012-09-28 | 2015-11-25 | 杭州华三通信技术有限公司 | A kind of multicast service realizing method and equipment thereof |
| CN105592064B (en) * | 2015-10-30 | 2019-08-16 | 新华三技术有限公司 | A kind of multicast on demand method and apparatus |
| CN111447412B (en) * | 2020-03-27 | 2021-09-07 | 浙江信网真科技股份有限公司 | Multi-stream data distribution method and system based on content grading |
-
2022
- 2022-12-02 CN CN202211532919.6A patent/CN115623253B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN115623253A (en) | 2023-01-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102075417B (en) | Multicast cutting method, protocol independent multicast router | |
| CN200990617Y (en) | Intermediate network equipment | |
| US7729350B2 (en) | Virtual multicast routing for a cluster having state synchronization | |
| US20110055622A1 (en) | Network system and network relay apparatus | |
| KR20070012678A (en) | Multimedia communication and collaboration system and protocols | |
| US8868658B2 (en) | Client assisted multicasting for audio and video streams | |
| US8650309B2 (en) | Cascading architecture for audio and video streams | |
| CN109981308B (en) | Message transmission method and device | |
| CN105471610B (en) | Method and device for protecting HQoS (high-quality QoS) by using multiple board cards | |
| CN111698158A (en) | Method and device for electing master equipment and machine-readable storage medium | |
| US11057475B2 (en) | Methods, apparatus and systems for resuming transmission link | |
| US20090154349A1 (en) | Method and apparatus for managing traffic flow of forwarding entries through a virtual forwarding database of a network node | |
| CN103078794A (en) | Message processing control method and device | |
| US9088629B2 (en) | Managing an electronic conference session | |
| CN115623253B (en) | Scene-aware video stream management method, system, device, and medium | |
| CN105429881A (en) | Multicast message forwarding method and device | |
| CN114244768A (en) | Forwarding method, device, equipment and storage medium for two-layer unknown multicast | |
| CN113973020B (en) | Method, device and system for sending multicast message | |
| EP3269089A1 (en) | Subscription for communication attributes | |
| CN111385298B (en) | Data transmission method, medium, device and computing equipment | |
| CN106254267B (en) | Data forwarding path adjusting method and gateway equipment | |
| CN109787870B (en) | Access management method, device, system, initial and target access equipment | |
| CN102394813A (en) | Multicast routing table item management method and router | |
| CN112217718A (en) | Service processing method, device, equipment and storage medium | |
| US10205652B2 (en) | Path checking method, sink node device, and communications system |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |