Methods, apparatus, electronic devices and storage media for multicast information acquisition
By actively collecting the forwarding technical support capabilities and multicast information of multicast devices through the network controller, the problem of the network controller's inability to actively collect information is solved, and the automated activation and effective control of multicast services are realized.
Patent Information
- Application Number
- CN202210813081.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-07-11
- Publication Date
- 2026-11-17
- Estimated Expiration
- 2042-07-11
AI Technical Summary
In existing technologies, network controllers cannot actively collect information from multicast devices, resulting in a low degree of automation in the multicast service activation process.
The network controller obtains the multicast service activation request from the user equipment and determines whether the domain where the user equipment is located has a multicast service. If it does, the network controller is notified to collect multicast information. If it does not, the network controller collects information twice: forwarding technical support capabilities and multicast information.
It enables the network controller to actively collect information from multicast devices without requiring user devices to initiate reporting, adapts to the automated activation process of multicast services, and ensures effective control of multicast data.
Smart Images

Figure CN117424770B_ABST
Abstract
Description
Technical Field
[0001] This disclosure relates to the field of communication technology, and in particular to a method, apparatus, electronic device and storage medium for multicast information acquisition. Background Technology
[0002] Multicast is a network communication method in which a single sender corresponds to multiple receivers. Multicast technology effectively solves the problem of single-point sending and multi-point receiving in the data transmission process.
[0003] With the development of communication technology, the activation of user services is becoming increasingly automated and intent-based. The activation of intent-based automated multicast services relies on the network controller collecting information from network devices. Currently, related technologies involve the device side initiating the reporting of multicast information; a method for the controller to actively collect this information has not yet been defined.
[0004] It should be noted that the information disclosed in the background section above is only used to enhance the understanding of the background of this disclosure, and therefore may include information that does not constitute prior art known to those skilled in the art. Summary of the Invention
[0005] The purpose of this disclosure is to provide a method, apparatus, electronic device, and storage medium for multicast information collection. This method enables the network controller to actively collect multicast information from multicast devices without requiring the user equipment to actively initiate the reporting of multicast information.
[0006] Other features and advantages of this disclosure will become apparent from the following detailed description, or may be learned in part from practice of this disclosure.
[0007] This disclosure provides a method for collecting multicast information, comprising: obtaining a multicast service activation request from a user equipment; determining whether the multicast service exists in the domain where the user equipment is located; if the multicast service exists in the domain where the user equipment is located, notifying the network controller of the domain where the user equipment is located to collect the multicast information of the multicast equipment; if the multicast service does not exist in the domain where the user equipment is located, notifying the network controller of the domain where the user equipment is located to collect the forwarding technical support capability and the multicast information of the multicast equipment respectively.
[0008] This disclosure provides an apparatus for collecting multicast information, comprising: an acquisition module for acquiring a multicast service activation request from a user equipment; a judgment module for judging whether the multicast service exists in the domain where the user equipment is located; and a notification module for notifying the network controller of the domain where the user equipment is located to collect multicast information of the multicast equipment if the multicast service exists in the domain where the user equipment is located; the notification module is further configured to notify the network controller of the domain where the user equipment is located to collect the forwarding technical support capability and the multicast information of the multicast equipment respectively if the multicast service does not exist in the domain where the user equipment is located.
[0009] This disclosure provides an electronic device, including: at least one processor; and a storage terminal device for storing at least one program, which, when executed by the at least one processor, causes the at least one processor to implement any of the above-described methods for multicast information acquisition.
[0010] This disclosure provides a computer-readable storage medium storing a computer program thereon, characterized in that the computer program, when executed by a processor, implements any of the above-described methods for multicast information acquisition.
[0011] The method for multicast information collection provided in this disclosure, if a multicast service requested by a user exists in the domain where the user equipment is located, then the network controller of the domain where the user equipment is located is notified to actively collect the multicast information of the multicast device; if a multicast service requested by a user does not exist in the domain where the user equipment is located, then the network controller of the domain where the user equipment is located is notified to actively collect the forwarding technical support capability and the multicast information of the multicast device respectively. On the one hand, this method enables the network controller to actively collect the multicast information of the multicast device without requiring the user equipment to actively initiate the reporting of multicast information, which can be well adapted to the automated activation process of multicast services. On the other hand, when a multicast service requested by a user does not exist in the domain where the user equipment is located, the network controller can perform information collection twice, namely, actively collecting the forwarding technical support capability and actively collecting the multicast information of the multicast device, so as to realize the collection of multicast information based on the forwarding technical support capability of the multicast device, thereby realizing the control of multicast data.
[0012] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description
[0013] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure. It is obvious that the drawings described below are merely some embodiments of this disclosure, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort.
[0014] Figure 1 This is a schematic diagram illustrating a system framework for enabling multicast services oriented towards user intent, according to an exemplary embodiment.
[0015] Figure 2 This is a flowchart illustrating a method for multicast information acquisition according to an exemplary embodiment.
[0016] Figure 3 This is a flowchart illustrating another method for multicast information acquisition according to an exemplary embodiment.
[0017] Figure 4 This diagram illustrates the collection of multicast information when the user equipment's domain already has a multicast service requested by the user equipment.
[0018] Figure 5 This is a flowchart illustrating another method for multicast information acquisition according to an exemplary embodiment.
[0019] Figure 6 This diagram illustrates the collection of multicast information when the domain of the user equipment does not contain the multicast service requested by the user equipment.
[0020] Figure 7 A schematic diagram of an information acquisition TLV is shown.
[0021] Figure 8 A schematic diagram of an MPLS sub-TLV is shown.
[0022] Figure 9 A schematic diagram of an SR sub-TLV is shown.
[0023] Figure 10 A schematic diagram of a BIER sub-TLV is shown.
[0024] Figure 11 A schematic diagram of an information acquisition TLV is shown.
[0025] Figure 12 This is a block diagram illustrating an apparatus for multicast information acquisition according to an exemplary embodiment.
[0026] Figure 13 This is a schematic diagram of the structure of an electronic device according to an exemplary embodiment. Detailed Implementation
[0027] Exemplary embodiments will now be described more fully with reference to the accompanying drawings. However, these exemplary embodiments can be implemented in many forms and should not be construed as limited to the examples set forth herein; rather, they are provided so that this disclosure will be more comprehensive and complete, and will fully convey the concept of the exemplary embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.
[0028] Furthermore, the accompanying drawings are merely illustrative of this disclosure and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and therefore repeated descriptions of them will be omitted. Some block diagrams shown in the drawings are functional entities and do not necessarily correspond to physically or logically independent entities. These functional entities may be implemented in software, in one or more hardware modules or integrated circuits, or in different network and / or processor terminal devices and / or microcontroller terminal devices.
[0029] Furthermore, in the description of this disclosure, "a plurality of" means at least two, such as two, three, etc., unless otherwise expressly specified. The terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature.
[0030] Figure 1 This is a schematic diagram illustrating a system framework for enabling multicast services oriented towards user intent, according to an exemplary embodiment.
[0031] refer to Figure 1 The system framework may include a user portal, an intent processing module, an intent orchestrator, a multicast resource library, and a network controller; wherein, this disclosure adds a collection control module to the intent orchestrator for controlling the collection scope and collection information; and adds a multi-protocol collection module to the network controller for collecting multicast information in the network environment.
[0032] refer to Figure 1 The activation process for multicast services (also known as multicast business) may include the following steps.
[0033] Step S101: The user applies to activate the multicast service through the user portal;
[0034] Step S102: The intent processing module performs business orchestration on the user's multicast service activation request;
[0035] Step S103: The intent orchestrator queries the multicast source and / or multicast group, as well as the multicast information of the user's domain, from the multicast resource library;
[0036] Step S104: The acquisition control module in the intent orchestrator checks whether the multicast service already exists in the user's domain (i.e., the multicast service that the user applied to activate in step S101) based on the multicast source and / or multicast group information obtained from the query.
[0037] Step S1051: If the multicast service already exists in the user's domain, the protocol used for multicast has been determined. The acquisition control module can then notify the network controller of the user's domain to acquire the multicast information of the network device (also known as the multicast device).
[0038] Step S1052: If the multicast service does not exist in the user's domain, a new multicast service needs to be added. The data collection and control module notifies the network controller of the user's domain to collect information twice. The first time, it collects the forwarding technology support capability (also known as the forwarding protocol support capability) of the network device, that is, the forwarding technology supported by the network device. The second time, it collects the multicast information of the network device. Then, it sends a deployment policy template to the network controller to guide the network controller to select the protocol to be deployed.
[0039] Step S106: The network controller collects multicast information from network devices.
[0040] The steps of the method for multicast information collection in the exemplary embodiments of this disclosure will now be described in more detail with reference to the accompanying drawings and examples.
[0041] Figure 2 This is a flowchart illustrating a method for multicast information acquisition according to an exemplary embodiment. The method provided in this disclosure can be performed by any electronic device, such as the one described above. Figure 1 The intent processing module and intent orchestrator are included, but this disclosure does not limit them.
[0042] like Figure 2 As shown in the embodiments of this disclosure, the method for collecting multicast information may include the following steps.
[0043] In step S202, the multicast service activation request of the user equipment is obtained.
[0044] In this embodiment of the disclosure, multicast service (also known as multicast business) refers to a service that is directed to multiple terminals (also known as user equipment), such as video conferencing, television broadcasting, video on demand, online education, etc.
[0045] In this embodiment of the disclosure, the multicast service activation request may include a specific multicast, which can be represented as (multicast source, multicast group), where the multicast source refers to the device that sends messages in the multicast. For example, a multicast source S for a sports live broadcast can serve a multicast group G, and this multicast can be represented as (S, G). User equipment can apply to join this multicast (S, G).
[0046] In step S204, it is determined whether the multicast service exists in the domain where the user equipment is located.
[0047] In this embodiment of the disclosure, the intent orchestrator can query the multicast information of existing multicasts from the multicast resource library, and determine whether the multicast service already exists in the domain where the user equipment is located based on the multicast information queried.
[0048] The user equipment domain can be a geographical area within a certain range around the location of the user equipment, and its specific range can be set according to actual needs. This disclosure does not limit it. The user equipment domain (also referred to as the domain accessed by the user) can also be a geographical area within a certain range around the location of the edge node device accessed by the user equipment, and its specific range can be set according to actual needs. This disclosure does not limit it.
[0049] Specifically, determining whether the multicast service already exists in the domain where the user equipment is located can be done by determining whether there are multicast devices providing the multicast service within the domain where the user equipment is located.
[0050] In step S206, if the multicast service exists in the domain where the user equipment is located, the network controller of the domain where the user equipment is located is notified to collect the multicast information of the multicast device.
[0051] In this embodiment of the disclosure, one intent orchestrator can correspond to multiple network controllers; if the multicast service exists in the domain where the user equipment is located, the forwarding protocol used by the multicast has been determined, and the acquisition control module in the intent orchestrator can notify the network controller of the domain where the user equipment is located to acquire the multicast information of the multicast device.
[0052] In this embodiment of the disclosure, the network controller can collect multicast information from multicast devices according to the forwarding technology used by multicast. The specific collection process can be found in the following embodiments.
[0053] In step S208, if the multicast service does not exist in the domain where the user equipment is located, the network controller of the domain where the user equipment is located is notified to collect the forwarding technical support capability of the multicast device and the multicast information of the multicast device.
[0054] In this embodiment of the disclosure, if the multicast service does not exist in the domain where the user equipment is located, it is necessary to add a multicast service. The acquisition control module in the intent orchestrator can notify the network controller of the domain where the user equipment is located to perform two information acquisitions, namely, to acquire the forwarding technical support capability of the multicast device and the multicast information of the multicast device respectively.
[0055] Specifically, the acquisition control module can send two notifications to the network controller, one to notify the network controller of the forwarding technical support capability of the multicast device and the other to notify the multicast information of the multicast device. The acquisition control module can also send one notification to the network controller, which is used to notify the network controller of the forwarding technical support capability of the multicast device and the other to notify the multicast information of the multicast device.
[0056] Specifically, after receiving the above notification, the network controller can first collect the forwarding technical support capabilities of each multicast device in the multicast, and then collect multicast information based on the forwarding technical support capabilities of each multicast device.
[0057] Among them, forwarding technology support capability refers to the forwarding technologies that multicast devices can support. Forwarding technologies may include, but are not limited to, MPLS (Multi-Protocol Label Switching), SR (Segment Routing), P2MP (point-to-multipoint), BIER (Bit Indexed Explicit Replication), etc. Different networks have different support capabilities.
[0058] For example, after receiving the above notification, the network controller can first collect the forwarding technology support capabilities of each multicast device in the multicast. For example, if each multicast device in the multicast supports MPLS technology, then the network controller can collect the tree label of each multicast device and the termination label of the edge device in each multicast device.
[0059] In this embodiment of the disclosure, the network controller can collect multicast information from the multicast device based on the forwarding technology support capability of the multicast device. The specific collection process can be found in the following embodiments.
[0060] In an exemplary embodiment, if the domain where the user equipment is located does not have a multicast service, a deployment policy can be issued to the network controller so that the network controller can determine the target forwarding technology based on the deployment policy and the forwarding technology support capability of the multicast device. The target forwarding technology is used by the network controller to collect multicast information from the multicast device.
[0061] In this embodiment of the disclosure, the deployment strategy includes the priority of multiple forwarding technologies that are pre-set. The deployment strategy can be provided by the service provider, for example, it can be BIER>SR>MPLS, that is, the priority of BIER technology is greater than the priority of SR technology, and the priority of SR technology is greater than the priority of MPLS technology.
[0062] In an exemplary embodiment, the network controller determines at least one forwarding technology supported by multicast based on the forwarding technology support capability of the multicast device; the network controller determines a target forwarding technology from the at least one forwarding technology based on the priority of the multiple forwarding technologies.
[0063] For example, after the network controller collects the forwarding technology support capabilities of each multicast device, it finds that each multicast device supports BIER, SR, and MPLS technologies. Based on the deployment strategy, the highest priority technology is selected from the forwarding technologies supported by each multicast device as the target forwarding technology, i.e., BIER technology is selected as the target forwarding technology, and the corresponding multicast information is collected.
[0064] The method for multicast information collection provided in this disclosure, if a multicast service requested by a user exists in the domain where the user equipment is located, then the network controller of the domain where the user equipment is located is notified to actively collect the multicast information of the multicast device; if a multicast service requested by a user does not exist in the domain where the user equipment is located, then the network controller of the domain where the user equipment is located is notified to actively collect the forwarding technical support capability and the multicast information of the multicast device respectively. On the one hand, this method enables the network controller to actively collect the multicast information of the multicast device without requiring the user equipment to actively initiate the reporting of multicast information, which can be well adapted to the automated activation process of multicast services. On the other hand, when a multicast service requested by a user does not exist in the domain where the user equipment is located, the network controller can perform information collection twice, namely, actively collecting the forwarding technical support capability and actively collecting the multicast information of the multicast device, so as to realize the collection of multicast information based on the forwarding technical support capability of the multicast device, thereby realizing the control of multicast data.
[0065] In addition, in some embodiments, the network controller can combine deployment strategies (priority of forwarding technologies) and the forwarding technology support capabilities of multicast devices to automatically select forwarding technologies and perform collection and deployment.
[0066] Figure 3 This is a flowchart illustrating another method for multicast information acquisition according to an exemplary embodiment. The method provided in this disclosure can be performed by any electronic device, such as the one described above. Figure 1 The intent orchestrator and network controller in the process are executed jointly, but this disclosure does not limit this.
[0067] refer to Figure 3 ,exist Figure 2 After step S206 of the method for multicast information collection shown (i.e., when the multicast service exists in the domain where the user equipment is located), Figure 3 The method shown for collecting multicast information may also include the following steps.
[0068] In step S302, the network controller obtains the target forwarding technology used by the multicast device based on the control information in the local database.
[0069] In this embodiment of the disclosure, before step S302, the user has submitted a multicast service activation application through the user portal. After the intent processing module and intent orchestrator translate and orchestrate the application, the corresponding orchestration information is sent to the network controller, informing the network controller to analyze network conditions and manage control information for the user.
[0070] In this embodiment of the disclosure, when the multicast service exists in the domain where the user equipment is located, the network controller can know the forwarding technology currently used by the multicast (hereinafter referred to as the target forwarding technology) based on the control information (such as MPLS Label / SID / BitString) in the local database.
[0071] In step S304, the network controller collects multicast information from the multicast devices according to the target forwarding technology.
[0072] In this embodiment of the disclosure, the network controller can collect multicast information from each multicast device by carrying an extensible TLV (Type Length Value) through a network control protocol (e.g., BGP / PCEP / NETCONF).
[0073] Multicast devices can include intermediate node devices and edge node devices. Edge node devices are those that communicate with user equipment in the multicast, while intermediate node devices are those that connect to the ingress node devices and edge node devices. The ingress node devices can be those that communicate with the multicast source. Multicast information from multicast devices can include tree labels and termination labels; alternatively, multicast information can include tree SID (Segment Identifier) and termination SID; or, multicast information can include bit forwarding router identifier (BFR-ID) and termination identifier.
[0074] In an exemplary embodiment, when the target forwarding technology is MPLS, the network controller collects the tree labels of intermediate node devices and the tree labels and termination labels of edge node devices.
[0075] In an exemplary embodiment, when the target forwarding technology is SR technology, the network controller collects the tree SID of intermediate node devices and the network controller collects the tree SID and termination SID of edge node devices.
[0076] In an exemplary embodiment, when the target forwarding technology is BIER technology, the network controller collects the forwarding router identifier and termination identifier of the edge node device, without needing to collect the multicast information of the intermediate node device.
[0077] Specifically, the network controller can send multicast information collection requests to intermediate node devices and edge node devices respectively. In response to the multicast information collection request, the intermediate node devices and edge node devices can reply to the controller with the control information allocated for this multicast. For example, the intermediate node device only replies with the tree identifier, while the edge node needs to reply with the tree identifier / router identifier and termination information to inform the upstream to include this termination information when encapsulating data packets for forwarding to users.
[0078] Figure 4 This diagram illustrates the collection of multicast information when the user equipment's domain already has a multicast service requested by the user equipment.
[0079] The following is combined Figure 4 The process of collecting multicast information based on different forwarding technologies is explained.
[0080] refer to Figure 4 The multicast can include an entry node device P0, intermediate node devices P1, P2, P3, P4, and edge node devices PE1, PE2, and PE3. The entry node device P0 communicates with the multicast source, the edge node device PE1 communicates with n existing users, the edge node device PE2 communicates with m existing users, where n and m are positive integers, and the edge node device PE3 communicates with new users (i.e., users who apply to open the multicast service).
[0081] Specifically, for example, if the network controller learns that the forwarding technology currently used by the multicast is MPLS, the network controller can collect intermediate node control information (i.e., tree labels) from P1 and P4 through the information collection TLV of the network control protocol (e.g., PCEP), and collect edge node control information (i.e., tree labels and termination labels) from PE3 through the information collection TLV of the network control protocol (e.g., PCEP).
[0082] Based on the received message, P1 and P4 write the tree label to the corresponding TLV and reply to the network controller; PE3 writes the tree label and termination label to the corresponding TLV and reply to the network controller based on the received message.
[0083] Specifically, for example, if the network controller learns that the forwarding technology currently used for multicast is SR technology, the network controller can collect intermediate node control information (i.e., tree-SID) from P4 through the information collection TLV of the network control protocol (e.g., PCEP), and collect edge node control information (i.e., tree-SID and termination-SID) from PE3 through the information collection TLV of the network control protocol (e.g., PCEP).
[0084] It should be noted that when using SR technology, P1's Tree-SID already exists, so there is no need to collect P1's Tree-SID; P4 is a newly added node to this tree, so P4's Tree-SID needs to be collected.
[0085] Based on the received message, P4 writes the Tree-SID into the corresponding TLV and replies to the network controller; PE3 writes the Tree-SID and Termination-SID into the corresponding TLV and replies to the network controller.
[0086] Specifically, for example, if the network controller learns that the forwarding technology currently used for multicast is BIER technology, the network controller can collect edge node control information (i.e., BFR-ID + termination identifier) from PE3 through the information collection TLV of the network control protocol (e.g., PCEP).
[0087] Based on the received message, PE3 writes the BFR-ID + termination identifier (Label or SID) into the corresponding TLV and replies to the network controller with the control information assigned for this multicast.
[0088] In this embodiment of the disclosure, after a new user equipment accesses multicast, the network controller sends control signaling to the intermediate node device and the edge node device respectively. The control signaling sent to P1 is used to inform P1: "When forwarding multicast packets, send the multicast packets to P4 and encapsulate the label corresponding to P4 (e.g., tree label)". The control signaling sent to P4 is used to inform P4: "When forwarding multicast packets, send the multicast packets to PE3 and encapsulate the label corresponding to PE3 and the termination label". The control signaling sent to PE3 is used to inform PE3: "P4 will send multicast packets to it. After PE3 receives the tree label corresponding to PE3, it will forward multicast data for the new user according to the behavior defined by the termination label".
[0089] The method for multicast information collection provided in this disclosure allows the network controller to collect multicast information according to different forwarding technologies (e.g., through scalable sub-TLV), thus flexibly supporting information collection for different forwarding technologies.
[0090] Figure 5This is a flowchart illustrating another method for multicast information acquisition according to an exemplary embodiment. The method provided in this disclosure can be performed by any electronic device, such as the one described above. Figure 1 The intent orchestrator and network controller in the process are executed jointly, but this disclosure does not limit this.
[0091] refer to Figure 5 ,exist Figure 2 After step S208 of the method for multicast information collection shown (i.e., when the multicast service does not exist in the domain where the user equipment is located), Figure 5 The method shown for collecting multicast information may also include the following steps.
[0092] In step S502, the network controller collects the forwarding technology support capabilities of the multicast devices.
[0093] In this embodiment of the disclosure, before step S502, the user has submitted a multicast service activation application through the user portal. After the intent processing module and intent orchestrator translate and orchestrate the application, the corresponding orchestration information is sent to the network controller, informing the network controller to analyze network conditions and manage control information for the user.
[0094] If the multicast service does not exist in the domain where the user equipment is located, that is, if the multicast service has not been deployed in the user's domain before, the egress router of the domain where the multicast source requested by the user is located can be regarded as the multicast source of this domain; or a multicast tuple (S, G) can be added in this domain.
[0095] If the multicast service does not exist in the domain where the user equipment is located, and the network controller cannot find the existing multicast tree in the domain based on the multicast source requested by the user, then the corresponding multicast tree needs to be newly built, and the support capability of the corresponding nodes for forwarding technology needs to be collected.
[0096] In step S504, the network controller determines the target forwarding technology based on the forwarding technology support capabilities of the multicast device.
[0097] In this embodiment of the disclosure, the network controller can determine the target forwarding technology from among the forwarding technologies supported by all multicast devices.
[0098] In this embodiment of the disclosure, the network controller can refer to the custom deployment strategy provided by the service provider (corresponding to the priority of different forwarding technology deployments) and match it according to the capability support of the corresponding node. If the network supports it, the deployment method with higher priority in the strategy will be selected first.
[0099] If the multicast service does not exist in the domain of the user equipment, the network controller needs to collect information twice: first, it needs to collect the forwarding protocol support capabilities, and then it needs to collect the multicast information.
[0100] In step S506, the network controller collects multicast information from the multicast devices according to the target forwarding technology.
[0101] The process of collecting multicast information from multicast devices based on the target forwarding technology in steps S506 and S302 is similar and can be referred to the textual description in step S302. This disclosure will not repeat it here.
[0102] Figure 6 This diagram illustrates the collection of multicast information when the domain of the user equipment does not contain the multicast service requested by the user equipment.
[0103] The following is combined Figure 6 The process of collecting multicast information based on different forwarding technologies is explained.
[0104] refer to Figure 6 (A) and Figure 6 (B) The multicast may include ingress node device P0, intermediate node devices P1, P2, P3, P4, and edge node devices PE1, PE2, PE3.
[0105] If the network controller of the user equipment's domain, based on control information in its local database, finds that there is no multicast status requested by the user within its domain, it first informs the network controller of the domain where the multicast source requested by the user is located. The network controller of the domain where the multicast source requested by the user treats the user's domain as a receiver (i.e., a newly added user) and performs the appropriate processing (see [link to relevant documentation] for details). Figure 4 Example (Example).
[0106] refer to Figure 6 (A) If this multicast service was not previously deployed in the user's domain, the egress router PE' of the domain where the multicast source requested by the user is located can be considered as the multicast source for this domain; or, refer to... Figure 6 (B) allows adding a new multicast tuple (S, G) within this domain, which means adding a specified multicast source to communicate with P0.
[0107] Then, the network controller calculates the multicast tree for the user within the domain, collects information on the support for forwarding technologies by the relevant nodes, determines the target forwarding technology based on the support of the relevant nodes, and collects the multicast information of each multicast device based on the target forwarding technology (see [link to specific processing methods]). Figure 4 Example (Example).
[0108] After a new user terminal accesses the multicast network, the network controller sends corresponding control signals to each multicast device (see [link to relevant documentation] for details). Figure 4 Example (Example).
[0109] In this embodiment of the disclosure, a multi-protocol-oriented multicast information collection signaling is designed. For different forwarding technologies, the network control protocol (such as the PCEP protocol) is extended to carry different sub-TLVs for multicast information collection, thereby meeting the need to collect different multicast information for different forwarding technologies.
[0110] For example, when the target forwarding technology is MPLS, the network controller can collect the tree label of intermediate node devices through the first sub-TLV in the TLV carried by the network control protocol; and collect the tree label and termination label of edge node devices through the second sub-TLV in the TVL carried by the network control protocol.
[0111] Specifically, in combination Figure 4 When the target forwarding technology is MPLS, the network controller can collect intermediate node control information from P1 and P4 by carrying information collection TLV containing MPLS sub-TLV through the Initiating message of the network control protocol (e.g., PCEP), and collect edge node control information from PE3 by carrying information collection TLV containing MPLS sub-TLV and termination identifier sub-LV through the Initiating message of the network control protocol (e.g., PCEP).
[0112] P1 and P4 write the corresponding information into the corresponding MPLS sub-TLV based on the received message and reply to the network controller; PE3 writes the corresponding information into the corresponding MPLS sub-TLV and the termination identifier sub-TLV based on the received message and replies to the network controller with the control information allocated for this multicast.
[0113] For example, when the target forwarding technology is SR technology, the network controller can collect the tree SID of intermediate node devices through the third sub-TLV in the TLV carried by the network control protocol; and collect the tree SID and termination SID of edge node devices through the fourth sub-TLV in the TVL carried by the network control protocol.
[0114] For example, when the target forwarding technology is BIER technology, the network controller collects the forwarding router identifier and termination identifier of the edge node device through the fifth sub-TLV in the TLV carried by the network control protocol.
[0115] The following is combined Figures 7-11 The information collection signaling is explained. The network controller can collect multicast information from various multicast devices through information collection signaling.
[0116] Figure 7 A schematic diagram of an information acquisition TLV is shown. Figure 8 A schematic diagram of an MPLS sub-TLV is shown. Figure 9A schematic diagram of an SR sub-TLV is shown. Figure 10 A schematic diagram of a BIER sub-TLV is shown. Figure 11 A schematic diagram of an information acquisition TLV is shown.
[0117] In this embodiment of the disclosure, the information collection signaling may carry, for example, Figure 7 The TLV shown can contain a multicast source address, a multicast group address, and can also include a type, length, address length, and reserved fields. Depending on the use case, it can carry different sub-TLVs (optional sub-TLVs) to collect the corresponding control plane information.
[0118] Here, S can represent the use case; for example, S=0 represents MPLS, S=1 represents SR, and S=2 represents BIER.
[0119] If the data acquisition device is an intermediate node device, it can carry either MPLS sub-TLV or SR sub-TLV, with the corresponding information being 0. Among them, MPLS sub-TLV is as follows: Figure 8 As shown, tree labels are used to collect data from intermediate node devices; SR sub-TLVs are as follows. Figure 9 As shown, the tree SID is used to collect intermediate node devices.
[0120] If the data acquisition device is an edge node device, it can carry an MPLS sub-TLV, SR sub-TLV, or BIER sub-TLV + termination identifier sub-TLV, all with a content of 0. The MPLS sub-TLV is as follows: Figure 8 As shown, tree labels are used to collect data from edge node devices; SR sub-TLVs are as follows. Figure 9 As shown, the tree SID is used to collect data from edge node devices; BIER sub-TLV is as follows. Figure 10 As shown, the BFR-ID used to collect edge node devices, the BIER sub-TLV can also include a BSL (BitStringLength) field and a Subdomain-ID field; the termination identifier sub-TLV is as follows: Figure 11 As shown, this is used to collect the termination identifier (e.g., Forwading Identifier) of edge node devices.
[0121] The device being collected can fill in the corresponding sub-TLV information according to the usage scenario and respond to the network controller to complete the collection process.
[0122] It should also be understood that the above is only to help those skilled in the art better understand the embodiments of this disclosure, and is not intended to limit the scope of the embodiments of this disclosure. Those skilled in the art can obviously make various equivalent modifications or changes based on the examples given above. For example, some steps in the above methods may be unnecessary, or new steps may be added, etc. Alternatively, any combination of any two or more of the above embodiments may be used. Such modifications, changes, or combinations also fall within the scope of the embodiments of this disclosure.
[0123] It should also be understood that the above description of the embodiments of this disclosure focuses on highlighting the differences between the various embodiments. Similarities or differences not mentioned can be referred to each other, and for the sake of brevity, they will not be repeated here.
[0124] It should also be understood that the sequence number of each process does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this disclosure.
[0125] It should also be understood that, in the various embodiments of this disclosure, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions between different embodiments are consistent and can be referenced by each other, and the technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.
[0126] The foregoing section detailed examples of methods for determining network anomaly detection models provided in this disclosure. It is understood that, in order to implement the aforementioned functions, computer devices include corresponding hardware structures and / or software modules for executing each function. Those skilled in the art should readily recognize that, based on the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein, this disclosure can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this disclosure.
[0127] The following are embodiments of the apparatus disclosed herein, which can be used to execute embodiments of the method disclosed herein. For details not disclosed in the apparatus embodiments of this disclosure, please refer to the embodiments of the method disclosed herein.
[0128] Figure 12 This is a block diagram illustrating an apparatus for multicast information acquisition according to an exemplary embodiment.
[0129] like Figure 12 As shown, the device 1200 for multicast information acquisition may include: an acquisition module 1202, a judgment module 1204, and a notification module 1206.
[0130] The acquisition module 1202 is used to acquire the multicast service activation request of the user equipment; the judgment module 1204 is used to determine whether the multicast service exists in the domain where the user equipment is located; the notification module 1206 is used to notify the network controller of the domain where the user equipment is located to collect the multicast information of the multicast device if the multicast service exists; the notification module 1206 is also used to notify the network controller of the domain where the user equipment is located to collect the forwarding technical support capability and the multicast information of the multicast device respectively if the multicast service does not exist.
[0131] In some exemplary embodiments of this disclosure, the notification module 1206 is further configured to issue a deployment policy to the network controller if the multicast service does not exist in the domain where the user equipment is located, so that the network controller determines the target forwarding technology according to the deployment policy and the forwarding technology support capability of the multicast device, wherein the target forwarding technology is used by the network controller to collect multicast information of the multicast device.
[0132] In some exemplary embodiments of this disclosure, the apparatus 1200 for multicast information acquisition may further include: an acquisition module, used by the network controller to acquire the target forwarding technology used by the multicast device based on control information in a local database; and an acquisition module, used by the network controller to acquire multicast information of the multicast device based on the target forwarding technology.
[0133] In some exemplary embodiments of this disclosure, the apparatus 1200 for multicast information acquisition may further include: a determining module; wherein the acquisition module is further configured for the network controller to acquire the forwarding technology support capability of the multicast device; the determining module is configured for the network controller to determine the target forwarding technology based on the forwarding technology support capability of the multicast device; the acquisition module is further configured for the network controller to acquire the multicast information of the multicast device based on the target forwarding technology.
[0134] In some exemplary embodiments of this disclosure, the deployment strategy includes priorities corresponding to multiple forwarding technologies; wherein, the determining module is further configured to the network controller determine at least one forwarding technology supported by multicast based on the forwarding technology support capability of the multicast device; the determining module is further configured to the network controller determine the target forwarding technology from the at least one forwarding technology based on the priorities corresponding to the multiple forwarding technologies.
[0135] In some exemplary embodiments of this disclosure, the multicast device includes intermediate node devices and edge node devices, and the multicast information includes tree labels and termination labels; wherein, the acquisition module is further configured to, when the target forwarding technology is Multiprotocol Label Switching (MPLS) technology, have the network controller acquire the tree labels of the intermediate node devices, and have the network controller acquire the tree labels and termination labels of the edge node devices.
[0136] In some exemplary embodiments of this disclosure, the acquisition module is further configured to allow the network controller to acquire the tree label of the intermediate node device through a first sub-TLV in the Extended Type Length Value (TLV) carried by the network control protocol; and the network controller to acquire the tree label and termination label of the edge node device through a second sub-TLV in the TVL carried by the network control protocol.
[0137] In some exemplary embodiments of this disclosure, the multicast device includes intermediate node devices and edge node devices, and the multicast information includes tree SID and termination SID; wherein, the acquisition module is further configured to, when the target forwarding technology is segmented routing (SR) technology, have the network controller acquire the tree SID of the intermediate node devices, and have the network controller acquire the tree SID and termination SID of the edge node devices.
[0138] In some exemplary embodiments of this disclosure, the acquisition module is further configured to allow the network controller to acquire the tree SID of the intermediate node device through a third sub-TLV in the TLV carried by the network control protocol; and the network controller to acquire the tree SID and terminal SID of the edge node device through a fourth sub-TLV in the TVL carried by the network control protocol.
[0139] In some exemplary embodiments of this disclosure, the multicast device includes an edge node device, and the multicast information includes a forwarding router identifier and a termination identifier; wherein, the acquisition module is further configured to, when the target forwarding technology is Bit-Indexed Explicit Replication (BIER) technology, have the network controller acquire the forwarding router identifier and termination identifier of the edge node device.
[0140] In some exemplary embodiments of this disclosure, the acquisition module is further configured to acquire the forwarding router identifier and termination identifier of the edge node device through the fifth sub-TLV in the TLV carried by the network control protocol.
[0141] It should be noted that the block diagrams shown in the above figures are functional entities and do not necessarily correspond to physically or logically independent entities. These functional entities can be implemented in software, in one or more hardware modules or integrated circuits, or in different network and / or processor terminal devices and / or microcontroller terminal devices.
[0142] Figure 13 This is a schematic diagram illustrating the structure of an electronic device according to an exemplary embodiment. It should be noted that... Figure 13 The electronic device shown is merely an example and should not be construed as limiting the functionality and scope of the embodiments disclosed herein.
[0143] like Figure 13 As shown, the electronic device 1300 includes a central processing unit (CPU) 1301, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 1302 or a program loaded from a storage section 1308 into a random access memory (RAM) 1303. The RAM 1303 also stores various programs and data required for the operation of the electronic device 1300. The CPU 1301, ROM 1302, and RAM 1303 are interconnected via a bus 1304. An input / output (I / O) interface 1305 is also connected to the bus 1304.
[0144] The following components are connected to I / O interface 1305: an input section 1306 including a keyboard, mouse, etc.; an output section 1307 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 1308 including a hard disk, etc.; and a communication section 1309 including a network interface card such as a LAN card, modem, etc. The communication section 1309 performs communication processing via a network such as the Internet. A drive 1310 is also connected to I / O interface 1305 as needed. Removable media 1311, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., are installed on drive 1310 as needed so that computer programs read from them can be installed into storage section 1308 as needed.
[0145] In particular, according to embodiments of this disclosure, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this disclosure include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 1309, and / or installed from removable medium 1311. When the computer program is executed by central processing unit (CPU) 1301, it performs the functions defined above in the system of this disclosure.
[0146] It should be noted that the computer-readable medium disclosed herein may be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium may be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, terminal device, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, terminal device, or device. In this disclosure, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media can also be any computer-readable medium other than computer-readable storage media, which can send, propagate, or transmit programs for use by or in connection with an instruction execution system, terminal device, or apparatus. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wireless, wire, optical fiber, RF, etc., or any suitable combination thereof.
[0147] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.
[0148] The units described in the embodiments of this disclosure can be implemented in software or hardware. The described units can also be housed in a processor; for example, a processor can be described as including a sending unit, an acquisition unit, a determining unit, and a first processing unit. The names of these units do not necessarily limit the specific unit; for example, a sending unit can also be described as "a unit that sends an image acquisition request to a connected server."
[0149] In another aspect, this disclosure also provides a computer-readable storage medium, which may be included in the electronic device described in the above embodiments; or it may exist independently and not assembled into the electronic device. The computer-readable storage medium carries one or more programs that, when executed by the electronic device, cause the electronic device to perform the methods described in the following embodiments. For example, the electronic device may perform... Figure 2 The steps shown.
[0150] According to one aspect of this disclosure, a computer program product or computer program is provided, comprising computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the methods provided in various optional implementations of the above embodiments.
[0151] It should be understood that any number of elements in the accompanying drawings is for illustrative purposes only and not for limitation, and any naming is for distinction only and has no limiting meaning.
[0152] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this disclosure are indicated by the following claims.
[0153] It should be understood that this disclosure is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this disclosure is limited only by the appended claims.
Claims
1. A method for multicast information acquisition, characterized in that, include: Obtain the multicast service activation request from the user device; Determine whether the multicast service exists in the domain where the user equipment is located. The domain where the user equipment is located is a geographical area within a certain range around the location of the user equipment, or it is a geographical area within a certain range around the location of the edge node device to which the user equipment is connected. If the multicast service exists in the domain where the user equipment is located, then the network controller of the domain where the user equipment is located is notified to collect the multicast information of the multicast device; If the multicast service does not exist in the domain where the user equipment is located, the network controller of the domain where the user equipment is located is notified to collect the forwarding technical support capability of the multicast device and the multicast information of the multicast device respectively. A deployment policy is issued to the network controller so that the network controller can determine the target forwarding technology based on the deployment policy and the forwarding technology support capability of the multicast device, wherein the target forwarding technology is used by the network controller to collect multicast information from the multicast device.
2. The method according to claim 1, characterized in that, After notifying the network controller of the domain where the user equipment is located to collect multicast information from the multicast devices, the method further includes: The network controller obtains the target forwarding technology used by the multicast device based on control information in the local database. The network controller collects multicast information from the multicast devices according to the target forwarding technology.
3. The method according to claim 1, characterized in that, After notifying the network controller of the domain where the user equipment is located to collect the forwarding technical support capabilities of the multicast devices and the multicast information of the multicast devices, the method further includes: The network controller collects the forwarding technical support capabilities of the multicast devices; The network controller determines the target forwarding technology based on the forwarding technology support capability of the multicast device; The network controller collects multicast information from the multicast devices according to the target forwarding technology.
4. The method according to claim 3, characterized in that, The deployment strategy includes the priorities corresponding to multiple forwarding technologies; The network controller determines the target forwarding technology based on the forwarding technology support capabilities of the multicast device, including: The network controller determines at least one forwarding technology supported by multicast based on the forwarding technology support capability of the multicast device; The network controller determines the target forwarding technology from the at least one forwarding technology based on the priority of the plurality of forwarding technologies.
5. The method according to claim 2 or 3, characterized in that, The multicast device includes intermediate node devices and edge node devices, and the multicast information includes tree labels and terminal labels; The network controller collects multicast information from the multicast devices according to the target forwarding technology, including: When the target forwarding technology is Multiprotocol Label Switching (MPLS), the network controller collects the tree label of the intermediate node device, and the network controller collects the tree label and termination label of the edge node device.
6. The method according to claim 5, characterized in that, The network controller collects the tree labels of the intermediate node devices, and the network controller collects the tree labels and terminal labels of the edge node devices, including: The network controller collects the tree label of the intermediate node device through the first sub-TLV in the extended type length value TLV carried by the network control protocol; The network controller collects the tree label and termination label of the edge node device through the second sub-TLV in the TLV carried by the network control protocol.
7. The method according to claim 2 or 3, characterized in that, The multicast device includes intermediate node devices and edge node devices, and the multicast information includes tree SID and termination SID; The network controller collects multicast information from the multicast devices according to the target forwarding technology, including: When the target forwarding technology is segmented routing (SR) technology, the network controller collects the tree SID of the intermediate node device, and the network controller collects the tree SID and termination SID of the edge node device.
8. The method according to claim 7, characterized in that, The network controller collects the tree SID of the intermediate node device, and the network controller collects the tree SID and terminal SID of the edge node device, including: The network controller collects the tree SID of the intermediate node device through the third sub-TLV in the TLV carried by the network control protocol; The network controller collects the tree SID and terminal SID of the edge node device through the fourth sub-TLV in the TLV carried by the network control protocol.
9. The method according to claim 2 or 3, characterized in that, The multicast device includes edge node devices, and the multicast information includes a forwarding router identifier and a termination identifier; The network controller collects multicast information from the multicast devices according to the target forwarding technology, including: When the target forwarding technology is the bit-indexed explicit replication (BIER) technology, the network controller collects the forwarding router identifier and termination identifier of the edge node device.
10. The method according to claim 9, characterized in that, The network controller collects the forwarding router identifier and termination identifier of the edge node device, including: The network controller collects the forwarding router identifier and termination identifier of the edge node device through the fifth sub-TLV in the TLV carried by the network control protocol.
11. A device for multicast information acquisition, characterized in that, include: The acquisition module is used to acquire the multicast service activation request from user equipment; The judgment module is used to determine whether the multicast service exists in the domain where the user equipment is located. The domain where the user equipment is located is a geographical area within a certain range around the location of the user equipment, or it is a geographical area within a certain range around the location of the edge node device to which the user equipment is connected. The notification module is used to notify the network controller of the domain where the user equipment is located to collect the multicast information of the multicast device if the multicast service exists in the domain where the user equipment is located. The notification module is also used to notify the network controller of the domain where the user equipment is located to collect the forwarding technical support capability of the multicast device and the multicast information of the multicast device if the multicast service does not exist in the domain where the user equipment is located. A deployment policy is issued to the network controller so that the network controller can determine the target forwarding technology based on the deployment policy and the forwarding technology support capability of the multicast device, wherein the target forwarding technology is used by the network controller to collect multicast information from the multicast device.
12. An electronic device, characterized in that, include: At least one processor; A storage device for storing at least one program, which, when executed by the at least one processor, causes the at least one processor to implement the method as described in any one of claims 1 to 10.
13. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the method as described in any one of claims 1 to 10.
Citation Information
Patent Citations
Device, system and method for implementing multicast communication
CN101222414A
Multicast service processing method and device, storage medium and electronic equipment
CN114727235A
