CN117424770A

CN117424770A - Method, device, electronic equipment and storage medium for multicast information acquisition

Info

Publication number: CN117424770A
Application number: CN202210813081.1A
Authority: CN
Inventors: 李华楠; 王巍; 邓桓; 张鑫; 崔正光
Original assignee: China Telecom Corp Ltd
Current assignee: China Telecom Corp Ltd
Priority date: 2022-07-11
Filing date: 2022-07-11
Publication date: 2024-01-19

Abstract

The disclosure provides a method, a device, electronic equipment and a storage medium for multicast information acquisition. The method comprises the following steps: acquiring an opening request of multicast service of user equipment; judging whether the multicast service exists in the domain of the user equipment; if the multicast service exists in the domain of the user equipment, notifying a network controller of the domain of the user equipment to acquire multicast information of the multicast equipment; if the domain where the user equipment is located does not have the multicast service, notifying a network controller of the domain where the user equipment is located to respectively collect forwarding technical support capability of the multicast equipment and multicast information of the multicast equipment.

Description

Method, device, electronic equipment and storage medium for multicast information acquisition

Technical Field

The disclosure relates to the field of communication technologies, and in particular, to a method, a device, an electronic device and a storage medium for multicast information acquisition.

Background

Multicast refers to a network communication mode of a single sender corresponding to a plurality of receivers, and the multicast technology effectively solves the problems of single-point sending and multi-point receiving in the data transmission process.

With the development of communication technology, the opening of user services is more and more automated and intended, and the opening of an automatic multicast service based on intention needs to rely on a network controller to collect information of network equipment. In the related art, the reporting of the multicast information is initiated through the equipment side, and the mode of active collection of the controller is not defined at present.

It should be noted that the information disclosed in the above background section is only for enhancing understanding of the background of the present disclosure and thus may include information that does not constitute prior art known to those of ordinary skill in the art.

Disclosure of Invention

The invention aims to provide a method, a device, electronic equipment and a storage medium for multicast information acquisition, wherein the method can enable a network controller to actively acquire multicast information of multicast equipment without actively initiating reporting of the multicast information at a user equipment side.

Other features and advantages of the present disclosure will be apparent from the following detailed description, or may be learned in part by the practice of the disclosure.

The embodiment of the disclosure provides a method for multicast information acquisition, which comprises the following steps: acquiring an opening request of multicast service of user equipment; judging whether the multicast service exists in the domain of the user equipment; if the multicast service exists in the domain of the user equipment, notifying a network controller of the domain of the user equipment to acquire multicast information of the multicast equipment; if the domain where the user equipment is located does not have the multicast service, notifying a network controller of the domain where the user equipment is located to respectively collect forwarding technical support capability of the multicast equipment and multicast information of the multicast equipment.

The embodiment of the disclosure provides a device for multicast information acquisition, comprising: the acquisition module is used for acquiring an opening request of the multicast service of the user equipment; a judging module, configured to judge whether the multicast service exists in a domain where the user equipment is located; a notification module, configured to notify a network controller of a domain where the user equipment is located to collect multicast information of a multicast device if the domain where the user equipment is located has the multicast service; and the notification module is further used for notifying a network controller of the domain where the user equipment is located to acquire forwarding technical support capability of the multicast equipment and multicast information of the multicast equipment respectively if the multicast service does not exist in the domain where the user equipment is located.

An embodiment of the present disclosure provides an electronic device, including: at least one processor; and the storage terminal equipment is used for storing at least one program, and when the at least one program is executed by the at least one processor, the at least one processor is enabled to realize any method for multicast information acquisition.

The disclosed embodiments provide a computer readable storage medium having a computer program stored thereon, wherein the computer program when executed by a processor implements any of the methods for multicast information acquisition described above.

In the method for collecting multicast information provided by the embodiment of the present disclosure, if a domain where a user device is located has a multicast service applied by a user, a network controller of the domain where the user device is located is notified to actively collect multicast information of the multicast device; if the domain of the user equipment does not have the multicast service applied by the user, informing a network controller of the domain of the user equipment to actively collect the forwarding technical support capability of the multicast equipment and the multicast information of the multicast equipment respectively; on one hand, the method can enable the network controller to actively collect the multicast information of the multicast equipment, does not need to actively initiate the report of the multicast information at the user equipment side, and can be well adapted to the automatic opening flow of the multicast service; on the other hand, under the condition that the domain where the user equipment is located does not have the multicast service applied by the user, the network controller can acquire the information twice, namely, actively acquiring the forwarding technical support capability of the multicast equipment and actively acquiring the multicast information of the multicast equipment, so as to acquire the multicast information according to the forwarding technical support capability of the multicast equipment, thereby realizing the control of the multicast data.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the disclosure and together with the description, serve to explain the principles of the disclosure. It will be apparent to those of ordinary skill in the art that the drawings in the following description are merely examples of the disclosure and that other drawings may be derived from them without undue effort.

Fig. 1 is a schematic diagram illustrating a system framework for user intent oriented multicast service provisioning, according to an example embodiment.

Fig. 2 is a flow chart illustrating a method for multicast information acquisition according to an exemplary embodiment.

Fig. 3 is a flow chart illustrating another method for multicast information acquisition according to an exemplary embodiment.

Fig. 4 shows a schematic diagram of multicast information acquisition in the case where a multicast service applied by a user equipment already exists in a domain where the user equipment is located.

Fig. 5 is a flow chart illustrating another method for multicast information acquisition according to an exemplary embodiment.

Fig. 6 shows a schematic diagram of multicast information acquisition in the case where the domain in which the user equipment is located does not have a multicast service applied by the user equipment.

Fig. 7 shows a schematic diagram of an information acquisition TLV.

Fig. 8 shows a schematic diagram of an MPLS sub-TLV.

Fig. 9 shows a schematic diagram of an SR sub-TLV.

Fig. 10 shows a schematic diagram of a BIER sub-TLV.

Fig. 11 shows a schematic diagram of an information acquisition TLV.

Fig. 12 is a block diagram illustrating an apparatus for multicast information acquisition, according to an example embodiment.

Fig. 13 is a schematic diagram of an electronic device according to an exemplary embodiment.

Detailed Description

Example embodiments will now be described more fully with reference to the accompanying drawings. However, the exemplary embodiments may be embodied in many forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of the example 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.

Furthermore, the drawings are merely schematic illustrations of the present disclosure and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and thus a repetitive description thereof will be omitted. Some of the block diagrams shown in the figures are functional entities and do not necessarily correspond to physically or logically separate entities. These functional entities may be implemented in software or in one or more hardware modules or integrated circuits or in different networks and/or processor terminals and/or microcontroller terminals.

Furthermore, in the description of the present disclosure, the meaning of "a plurality" is at least two, such as two, three, etc., unless specifically defined otherwise. The terms "first," "second," and the like, are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defining "a first" or "a second" may explicitly or implicitly include one or more such feature.

Referring to fig. 1, the system framework may include a user portal, an intent processing module, an intent orchestrator, a multicast repository, a network controller; the system comprises an intention composer, an acquisition control module, a data processing module and a data processing module, wherein the acquisition control module is added in the intention composer and is used for controlling an acquisition range and acquisition information; and a multi-protocol acquisition module is added in the network controller and used for acquiring multicast information in a network environment.

Referring to fig. 1, an activation procedure of a multicast service (which may also be referred to as a multicast service) may include the following steps.

Step S101, a user applies for opening multicast service through a user gate;

Step S102, an intention processing module performs service arrangement on an opening request of a multicast service of a user;

step S103, the intention composer queries multicast sources and/or multicast groups and multicast information of the domain where the user is located from a multicast resource library;

step S104, the acquisition control module in the intention composer checks whether the multicast service exists in the domain where the user is located according to the multicast source and/or the multicast group information obtained by query (namely, the multicast service which the user applies for to be opened in step S101);

step S1051, if the multicast service already exists in the domain where the user is located, the protocol used by multicast is determined, and the acquisition control module informs the network controller in the domain where the user is located to acquire the multicast information of the network device (also referred to as multicast device);

step S1052, if the domain where the user is located does not have the multicast service, a new multicast service needs to be added, and the acquisition control module informs the network controller of the domain where the user is located to perform 2 times of information acquisition, and the 1 st time acquires the forwarding technology supporting capability (also referred to as forwarding protocol supporting capability) of the network device, that is, the forwarding technology supported by the network device; collecting multicast information of network equipment for the 2 nd time; and issuing a deployment strategy template to the network controller to guide the network controller to select a protocol for deployment.

Step S106, the network controller collects the multicast information of the network device.

The steps of the method for multicast information acquisition in the exemplary embodiments of the present disclosure will be described in more detail with reference to the accompanying drawings and embodiments.

Fig. 2 is a flow chart illustrating a method for multicast information acquisition according to an exemplary embodiment. The method provided by the embodiments of the present disclosure may be performed by any electronic device, such as the intent processing module and the intent orchestrator in fig. 1 described above, but the present disclosure is not limited in this regard.

As shown in fig. 2, a method for multicast information acquisition provided by an embodiment of the present disclosure may include the following steps.

In step S202, an activation request for a multicast service of a user equipment is acquired.

In the embodiment of the present disclosure, a multicast service (may also be referred to as a multicast service) refers to a service for a plurality of terminals (may also be referred to as user equipment), for example, video conference, television broadcast, video on demand, online education, and the like.

In the embodiment of the disclosure, the request for opening the multicast service may include a specific multicast, and the specific multicast may be expressed by (multicast source, multicast group), where the multicast source refers to a device sending a message in the multicast. For example, a multicast source S of a sports live, which may serve a multicast group G, this multicast may be denoted (S, G) and the user equipment may apply to join the multicast (S, G).

In step S204, it is determined whether the multicast service exists in the domain where the user equipment is located.

In the embodiment of the disclosure, the intention composer may query multicast information of existing multicast from a multicast resource library, and determine whether the multicast service exists in the domain where the user equipment is located according to the queried multicast information of the multicast.

The domain where the user equipment is located may be a geographical area within a certain range around the location where the user equipment is located, and a specific range of the geographical area may be set according to actual needs, which is not limited in the disclosure; the domain in which the user equipment is located (may also be referred to as a domain in which the user is accessed) may also be a geographical area within a certain range around the location in which the edge node device to which the user equipment is accessed is located, and the specific range may be set according to actual needs, which is not limited in the present disclosure.

Specifically, determining whether the domain in which the user equipment is located already exists the multicast service may be determining whether the domain in which the user equipment is located exists a multicast device that provides the multicast service.

In step S206, if the domain where the ue is located has the multicast service, the network controller of the domain where the ue is located is notified to collect multicast information of the multicast device.

In embodiments of the present disclosure, one intention orchestrator may correspond to multiple network controllers; if the multicast service exists in the domain where the user equipment is located, the forwarding protocol used by multicast is determined, and the acquisition control module in the intention composer can inform the network controller in the domain where the user equipment is located to acquire the multicast information of the multicast equipment.

In the embodiment of the disclosure, the network controller may collect multicast information of the multicast device according to a forwarding technology used in multicast, and a specific collection process may be referred to the following embodiment.

In step S208, if the domain where the ue is located does not have the multicast service, the network controller of the domain where the ue is located is notified to collect the forwarding technical support capability of the multicast device and the multicast information of the multicast device, respectively.

In the embodiment of the disclosure, if the multicast service does not exist in the domain where the user equipment is located, a new multicast service needs to be added, and the acquisition control module in the intention composer can inform the network controller in the domain where the user equipment is located of 2 times of information acquisition, that is, acquire the forwarding technology supporting capability of the multicast equipment and the multicast information of the multicast equipment respectively.

Specifically, the acquisition control module may send 2 notifications to the network controller, which are respectively used to notify the network controller to acquire forwarding technical support capability of the multicast device and multicast information of the multicast device; the acquisition control module may also send a notification to the network controller, where the notification is used to notify the network controller to acquire the forwarding technical support capability of the multicast device and the multicast information of the multicast device, respectively.

Specifically, after receiving the notification, the network controller may collect the forwarding technical support capability of each multicast device in the multicast first, and then collect the multicast information according to the forwarding technical support capability of each multicast device.

The forwarding technology supporting capability refers to a forwarding technology that can be supported by the multicast device, and the forwarding technology may include, but is not limited to, MPLS (Multi-Protocol Label Switching ) technology, SR (Segment Routing) technology, P2MP (point-to-multipoint) technology, BIER (Bit Indexed Explicit Replication, explicit replication based on bit indexes) technology, and the like, where different networks have different supporting capabilities.

For example, after receiving the notification, the network controller may collect forwarding technology supporting capability of each multicast device in the multicast, for example, each multicast device in the multicast supports MPLS technology, and then the network controller collects tree labels of each multicast device and terminal labels of edge devices in each multicast device.

In the embodiment of the disclosure, the network controller may collect multicast information of the multicast device according to forwarding technical support capability of the multicast device, and a specific collection process may be referred to the following embodiment.

In an exemplary embodiment, if the domain where the user equipment is located does not have a multicast service, a deployment policy may also be issued to the network controller, so that the network controller determines a target forwarding technology according to the deployment policy and a forwarding technology supporting capability of the multicast equipment, where the target forwarding technology is used for the network controller to collect multicast information of the multicast equipment.

In the embodiment of the present disclosure, the deployment policy includes priorities corresponding to a plurality of preset forwarding technologies, and the deployment policy may be provided by a service provider, for example, BIER > SR > MPLS may be provided, 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.

In an exemplary embodiment, the network controller determines at least one forwarding technology supported by the multicast according to forwarding technology support capabilities of the multicast device; and the network controller determines a target forwarding technology from at least one forwarding technology according to the priorities corresponding to the plurality of forwarding technologies.

For example, after the network controller collects the forwarding technology supporting capability of each multicast device, it finds that each multicast device supports BIER technology, SR technology, and MPLS technology; according to the deployment strategy, selecting the technology with the highest priority from the forwarding technologies supported by each multicast device as the target forwarding technology, namely selecting the BIER technology as the target forwarding technology, and collecting corresponding multicast information.

Furthermore, in some embodiments, the network controller may combine the deployment policy (priority of forwarding technology) and the forwarding technology support capability of the multicast device, automatically select the forwarding technology and perform the acquisition deployment.

Fig. 3 is a flow chart illustrating another method for multicast information acquisition according to an exemplary embodiment. The method provided by the embodiments of the present disclosure may be performed by any electronic device, such as the intent composer and the network controller described above in fig. 1, but the present disclosure is not limited thereto.

Referring to fig. 3, after step S206 of the method for multicast information collection shown in fig. 2 (i.e., in the case where the domain in which the user equipment is located has the multicast service), the method for multicast information collection shown in fig. 3 may further include the following steps.

In step S302, the network controller obtains a target forwarding technique used by the multicast device according to control information of the local database.

In the disclosed embodiment, before step S302, the user submits an application for opening the multicast service through the user portal, translates and composes the application through the intent processing module and the intent composer, and sends corresponding composition information to the network controller, informing the network controller to analyze the network condition and manage the control information for the user.

In the embodiment of the present disclosure, when the multicast service exists in the domain where the user equipment is located, the network controller may learn the forwarding technology (hereinafter referred to as the target forwarding technology) used by the current multicast according to the control information (e.g., MPLS Label/SID/BitString) of the local database.

In step S304, the network controller collects multicast information of the multicast device according to the target forwarding technique.

In the embodiment of the disclosure, the network controller may collect multicast information of each multicast device by carrying an expandable TLV (Type Length Value, an expanded type length value) through a network control protocol (e.g., BGP/PCEP/netcon).

Wherein, the multicast equipment can comprise intermediate node equipment and edge node equipment; the edge node device is a device in multicast that communicates with the user device, the intermediate node device is a device between the ingress node device and the edge node device, and the ingress node device may be a device in communication with a multicast source. The multicast information of the multicast device may include a tree tag and a termination tag, or the multicast information of the multicast device may include a tree SID (Segment Identifier, segment identification) and a termination SID, or the multicast information of the multicast device may include a forwarding router identification (BFR-ID, bit Forwarding Router-ID) and a termination identification.

In an exemplary embodiment, when the target forwarding technology is MPLS technology, the network controller collects tree labels of intermediate node devices, and the network controller collects tree labels and termination labels of edge node devices.

In an exemplary embodiment, when the target forwarding technique is an SR technique, the network controller collects a tree SID of the intermediate node device, and the network controller collects a tree SID and a termination SID of the edge node device.

In an exemplary embodiment, when the target forwarding technology is BIER technology, the network controller collects the forwarding router identifier and the termination identifier of the edge node device, and does not need to collect multicast information of the intermediate node device.

Specifically, the network controller may send a multicast information acquisition request to the intermediate node device and the edge node device, respectively, and the intermediate node device and the edge node device may respond to the multicast information acquisition request and reply control information allocated by the intermediate node device and the edge node device to the controller. For example, the intermediate node device only replies to the tree identifier, and the edge node needs to reply to the tree identifier/router identifier, and the termination information to inform the upstream that the upstream carries the termination information when encapsulating the data packet for forwarding to the user.

The procedure for multicast information acquisition according to different forwarding techniques is described below in connection with fig. 4.

Referring to fig. 4, the multicast may include an ingress node device P0, intermediate node devices P1, P2, P3, P4, and edge node devices PE1, PE2, PE3, where the ingress node device P0 communicates with a multicast source, the edge node device PE1 communicates with n existing users, and the edge node device PE2 communicates with m existing users, where n and m are both positive integers; the edge node device PE3 communicates with the newly added user, i.e. the user who has applied for opening the multicast service.

Specifically, for example, the network controller knows that the forwarding technology currently used by multicast is MPLS technology, and the network controller may collect intermediate node control information (i.e., tree labels) to P1 and P4 through an information collection TLV of a network control protocol (e.g., PCEP), and collect edge node control information (i.e., tree labels and termination labels) to PE3 through an information collection TLV of a network control protocol (e.g., PCEP).

P1 and P4 write the Tree Label (Tree-Label) into the corresponding TLV according to the received message and reply to the network controller; PE3 writes the tree Label and the terminal Label (terminal Label) into corresponding TLVs according to the received message and replies to the network controller.

Specifically, for example, the network controller knows that the forwarding technology currently used by multicast is SR technology, and the network controller can collect intermediate node control information (i.e. tree-SID) to P4 through an information collection TLV of a network control protocol (e.g. PCEP), and collect edge node control information (i.e. tree-SID and termination-SID) to PE3 through an information collection TLV of a network control protocol (e.g. PCEP).

It should be noted that, when the SR technique is used, the Tree-SID of P1 already exists, and the acquisition of the Tree-SID of P1 is not required; p4 is a node newly added to the Tree, and the Tree-SID of P4 needs to be acquired.

P4 writes the Tree-SID (Tree-SID) into the corresponding TLV according to the received message and replies to the network controller; and the PE3 writes the tree-SID and the terminal-SID into corresponding TLVs according to the received message and replies to the network controller.

Specifically, for example, the network controller knows that the forwarding technology currently used by multicast is BIER technology, and the network controller can acquire edge node control information (i.e. BFR-id+termination identifier) to PE3 through an information acquisition TLV of a network control protocol (e.g. PCEP).

PE3 writes BFR-ID+ termination identification (Label or SID) into corresponding TLV according to received message and replies control information allocated for multicast to network controller.

In the embodiment of the present disclosure, after a newly added ue accesses multicast, a network controller issues control signaling to an intermediate node device and an edge node device, where the control signaling issued to P1 is used to inform P1: "send multicast message to P4 when forwarding multicast message, and encapsulate the label (e.g. tree label) corresponding to P4)"; the control signaling issued to P4 is used to inform P4: "when forwarding the multicast message, sending the multicast message to the PE3, and encapsulating the label and the termination label corresponding to the PE 3"; the control signaling issued to PE3 is used to inform PE3: and the P4 sends a multicast message to the PE3, and after the PE3 receives the tree label corresponding to the PE3, the multicast data is forwarded for the new user according to the behavior defined by the terminal label.

According to the method for collecting the multicast information, which is provided by the embodiment of the disclosure, the network controller can collect the multicast information according to different forwarding technologies (for example, through an extensible sub-TLV (sub-TLV) which can be extensible), and can flexibly support information collection of different forwarding technologies.

Fig. 5 is a flow chart illustrating another method for multicast information acquisition according to an exemplary embodiment. The method provided by the embodiments of the present disclosure may be performed by any electronic device, such as the intent composer and the network controller described above in fig. 1, but the present disclosure is not limited thereto.

Referring to fig. 5, after step S208 of the method for multicast information collection shown in fig. 2 (i.e., in the case where the domain in which the user equipment is located does not have the multicast service), the method for multicast information collection shown in fig. 5 may further include the following steps.

In step S502, the network controller collects forwarding technical support capabilities of the multicast device.

In the disclosed embodiment, before step S502, a user submits an application for opening a multicast service through a user portal, translates and composes the application through an intention processing module and an intention composer, and sends corresponding composition information to a network controller, informing the network controller to analyze network conditions for the user and manage the control information.

Under the condition that the multicast service does not exist in the domain where the user equipment is located, that is, the multicast service is not deployed before the domain where the user is located, an exit router of the domain where the multicast source applied by the user is located can be regarded as the multicast source of the local domain; or multicast tuples (S, G) may be added newly in the home domain.

Under the condition that the multicast service does not exist in the domain where the user equipment is located, the network controller cannot inquire the existing multicast tree in the domain according to the multicast source applied by the user, and then a corresponding multicast tree needs to be newly built, and the supporting capability of the corresponding node on the forwarding technology needs to be acquired.

In step S504, the network controller determines a target forwarding technology according to the forwarding technology supporting capability of the multicast device.

In the embodiment of the disclosure, the network controller may determine the target forwarding technology from forwarding technologies supported by the multicast devices.

In the embodiment of the disclosure, the network controller may refer to a custom deployment policy (corresponding to priorities of deployment of different forwarding technologies) provided by a service provider, match according to the capability supporting situation of the corresponding node, and in the case of network support, preferably select a deployment mode with a higher priority in the policy.

Under the condition that the multicast service does not exist in the domain where the user equipment is located, the network controller needs to acquire information twice, firstly acquires the forwarding protocol supporting capability, and then acquires multicast information.

In step S506, the network controller collects multicast information of the multicast device according to the target forwarding technique.

The multicast information of the multicast device collected according to the target forwarding technique in step S506 and step S302 is similar, and reference may be made to the text description in step S302, which is not repeated herein.

The procedure for multicast information acquisition according to different forwarding techniques is described below in connection with fig. 6.

Referring to fig. 6 (a) and 6 (B), the ingress node device P0, the intermediate node devices P1, P2, P3, P4, and the edge node devices PE1, PE2, PE3 may be included in the multicast.

According to the control information of the local database, the network controller of the domain where the user equipment is located discovers that the domain where the user equipment is located does not have the multicast state applied by the user, and then the network controller of the domain where the multicast source applied by the user is located is informed of the user, wherein the user exists, the network controller of the domain where the multicast source applied by the user is located takes the domain where the user is located as a receiver (i.e. newly added user), and corresponding processing is performed (the specific processing mode can be seen in the embodiment of fig. 4).

Referring to fig. 6 (a), the multicast service is not deployed before the domain where the user is located, and the egress router PE' of the domain where the multicast source applied by the user is located may be regarded as the multicast source of the local domain; alternatively, referring to fig. 6 (B), a new multicast tuple (S, G), i.e., a new designated multicast source, may be added in the home domain to communicate with P0.

Then, the network controller calculates a multicast tree for the user in the local domain, collects the supporting condition of the corresponding node to the forwarding technology, determines the target forwarding technology according to the supporting condition of the corresponding node to the forwarding technology, and collects the multicast information of each multicast device according to the target forwarding technology (the specific processing mode can be seen in the embodiment of fig. 4).

After the newly added user terminal accesses the multicast, the network controller issues corresponding control signaling to each multicast device (see the embodiment of fig. 4 for a specific processing manner).

In the embodiment of the disclosure, multi-protocol-oriented multicast information acquisition signaling is designed, and aiming at different forwarding technologies, the multi-protocol-oriented multicast information acquisition signaling is expanded in a network control protocol (e.g., PCEP protocol) and carries different sub-TLVs (sub-TLVs) for acquiring multicast information, so that the requirements of acquiring different multicast information aiming at different forwarding technologies are met.

For example, when the target forwarding technology is MPLS technology, the network controller may collect the tree label of the intermediate node device through a first sub-TLV in TLVs carried by the network control protocol; the tree label and the terminal label of the edge node device are collected through a second sub-TLV in the TVL carried by the network control protocol.

Specifically, in connection with fig. 4, when the target forwarding technology is an MPLS technology, the network controller may collect intermediate node control information to P1 and P4 through an Initiating message of a network control protocol (e.g., PCEP) carrying an information collecting TLV including an MPLS sub-TLV, and collect edge node control information to PE3 through an Initiating message of a network control protocol (e.g., PCEP) carrying an information collecting TLV including an MPLS sub-TLV and a termination identifier sub-LV.

P1 and P4 write corresponding information into corresponding MPLS sub-TLVs according to the received information and reply to the network controller; and the PE3 writes corresponding information into the corresponding MPLS sub-TLV and the termination identifier sub-TLV according to the received message and replies control information allocated for multicast to the network controller.

For example, when the target forwarding technology is SR technology, the network controller may collect the tree SID of the intermediate node device through a third sub-TLV in TLVs carried by the network control protocol; the tree SID and the termination SID of the edge node device are collected through a fourth sub-TLV in the TVL carried by the network control protocol.

For example, when the target forwarding technology is BIER technology, the network controller collects the forwarding router identification and the termination identification of the edge node device through a fifth sub-TLV in TLVs carried by the network control protocol.

The information acquisition signaling will be described with reference to fig. 7 to 11. The network controller can collect multicast information from each multicast device through the information collection signaling.

Fig. 7 shows a schematic diagram of an information acquisition TLV, fig. 8 shows a schematic diagram of an MPLS sub-TLV, fig. 9 shows a schematic diagram of an SR sub-TLV, fig. 10 shows a schematic diagram of a BIER sub-TLV, and fig. 11 shows a schematic diagram of an information acquisition TLV.

In the embodiment of the disclosure, the information collection signaling may carry TLVs as shown in fig. 7, which may include a multicast source Address (Multicast Source Address), a multicast group Address (Multicast Group Address), and may further include a Type (Type), a Length (Length), an Address Length (Address Length), a Reserved field (Reserved), and carry different Sub-TLVs (i.e., optional Sub-TLVs) according to a usage Scenario (Scenario), so as to collect corresponding control plane information.

Wherein S may represent a usage scenario; for example, s=0 represents MPLS, s=1 represents SR, and s=2 represents BIER.

If the acquired equipment is intermediate node equipment, MPLS sub-TLV or SR sub-TLV can be carried, and the corresponding information is 0. The MPLS sub-TLVs are shown in FIG. 8 and are used for collecting tree labels of intermediate node equipment; the SR sub-TLV is shown in fig. 9, and is used to collect the tree SID of the intermediate node device.

If the acquired equipment is edge node equipment, carrying MPLS sub-TLV or SR sub-TLV or BIER sub-TLV+termination identification sub-TLV, wherein the content is 0. The MPLS sub-TLVs are shown in FIG. 8 and are used for collecting tree labels of edge node equipment; the SR sub-TLV is shown in fig. 9 and is used for collecting the tree SIDs of the edge node equipment; the BIER sub-TLV is shown in fig. 10, and is used for collecting the BFR-ID of the edge node device, and may further include a BSL (bit string length) field and a Subdomain-ID field; the termination identity sub-TLV is shown in fig. 11 and is used to collect the termination identity (e.g. Forwading Identifier (forwarding identifier)) of the edge node device.

The acquired equipment can fill corresponding sub-TLV information according to the use scene and respond to the network controller to finish the acquisition process.

It should also be understood that the above is only intended to assist those skilled in the art in better understanding the embodiments of the present disclosure, and is not intended to limit the scope of the embodiments of the present disclosure. It will be apparent to those skilled in the art from the foregoing examples that various equivalent modifications or variations can be made, for example, some steps of the methods described above may not be necessary, or some steps may be newly added, etc. Or a combination of any two or more of the above. Such modifications, variations, or combinations thereof are also within the scope of the embodiments of the present disclosure.

It should also be understood that the foregoing description of the embodiments of the present disclosure focuses on highlighting differences between the various embodiments and that the same or similar elements not mentioned may be referred to each other and are not repeated here for brevity.

It should also be understood that the sequence numbers of the above processes do not mean the order of execution, and the order of execution of the processes should be determined by the functions and internal logic thereof, and should not constitute any limitation on the implementation process of the embodiments of the present disclosure.

It is also to be understood that in the various embodiments of the disclosure, terms and/or descriptions of the various embodiments are consistent and may be referenced to one another in the absence of a particular explanation or logic conflict, and that the features of the various embodiments may be combined to form new embodiments in accordance with their inherent logic relationships.

Examples of the method for determining the network anomaly detection model provided by the present disclosure are described in detail above. It will be appreciated that the computer device, in order to carry out the functions described above, comprises corresponding hardware structures and/or software modules that perform the respective functions. Those of skill in the art will readily appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as hardware or combinations of hardware and computer software. Whether a function is implemented as hardware or computer software driven hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

The following are device embodiments of the present disclosure that may be used to perform method embodiments of the present disclosure. For details not disclosed in the embodiments of the apparatus of the present disclosure, please refer to the embodiments of the method of the present disclosure.

As shown in fig. 12, an apparatus 1200 for multicast information acquisition may include: an acquisition module 1202, a determination module 1204, and a notification module 1206.

The acquiring module 1202 is configured to acquire an opening request of a multicast service of a user equipment; the judging module 1204 is configured to judge whether the domain where the ue is located has the multicast service; the notification module 1206 is configured to notify a network controller of a domain where the ue is located to collect multicast information of a multicast device if the multicast service exists in the domain where the ue is located; the notification module 1206 is further configured to notify a network controller of a domain where the ue is located to collect forwarding technical support capability of the multicast device and multicast information of the multicast device, respectively, if the domain where the ue is located does not have the multicast service.

In some exemplary embodiments of the present disclosure, the notification module 1206 is further configured to issue a deployment policy to the network controller if the domain in which the user equipment is located does not have the multicast service, so that the network controller determines a target forwarding technology according to the deployment policy and a forwarding technology supporting capability of the multicast equipment, where the target forwarding technology is used for the network controller to collect multicast information of the multicast equipment.

In some exemplary embodiments of the present disclosure, the apparatus 1200 for multicast information acquisition may further include: the obtaining module is used for the network controller to obtain a target forwarding technology used by the multicast equipment according to the control information of the local database; and the acquisition module is used for acquiring the multicast information of the multicast equipment according to the target forwarding technology by the network controller.

In some exemplary embodiments of the present disclosure, the apparatus 1200 for multicast information acquisition may further include: a determining module; the acquisition module is also used for acquiring the forwarding technical support capacity of the multicast equipment by the network controller; a determining module, configured to determine, by using the network controller, the target forwarding technology according to forwarding technology supporting capability of the multicast device; the acquisition module is also used for the network controller to acquire the multicast information of the multicast equipment according to the target forwarding technology.

In some exemplary embodiments of the present disclosure, the deployment policy includes priorities corresponding to a plurality of forwarding technologies; the determining module is further configured to determine at least one forwarding technology supported by the multicast according to forwarding technology supporting capability of the multicast device by using the network controller; the determining module is further configured to determine, by the network controller according to priorities corresponding to the plurality of forwarding technologies, the target forwarding technology from the at least one forwarding technology.

In some exemplary embodiments of the present disclosure, the multicast device includes an intermediate node device and an edge node device, and the multicast information includes a tree tag and a termination tag; the acquisition module is further configured to, when the target forwarding technology is a multiprotocol label switching MPLS technology, acquire a tree label of the intermediate node device, and acquire a tree label and a termination label of the edge node device by using the network controller.

In some exemplary embodiments of the present disclosure, the collecting module is further configured to collect, by the network controller, a tree label of the intermediate node device through a first sub TLV in an extended type length value TLV carried by a network control protocol; and the network controller acquires the tree label and the terminal label of the edge node equipment through a second sub-TLV in the TVL carried by the network control protocol.

In some exemplary embodiments of the present disclosure, the multicast device includes an intermediate node device and an edge node device, and the multicast information includes a tree SID and a termination SID; the acquisition module is further configured to, when the target forwarding technology is a segment routing SR technology, acquire a tree SID of the intermediate node device, and acquire a tree SID and a termination SID of the edge node device by using the network controller.

In some exemplary embodiments of the present disclosure, the collecting module is further configured to collect, by the network controller, the tree SID of the intermediate node device through a third sub-TLV in TLVs carried by a network control protocol; the network controller collects tree SIDs and terminal SIDs of the edge node devices through a fourth sub-TLV in the TVL carried by the network control protocol.

In some exemplary embodiments of the present disclosure, the multicast device includes an edge node device, and the multicast information includes a forwarding router identification and a termination identification; the acquisition module is further configured to acquire a forwarding router identifier and a termination identifier of the edge node device when the target forwarding technology is a bit-indexed explicit replication BIER technology.

In some exemplary embodiments of the present disclosure, the collecting module is further configured to collect, by the network controller, the forwarding router identification and the termination identification of the edge node device through a fifth sub-TLV in TLVs carried by a network control protocol.

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 separate entities. These functional entities may be implemented in software or in one or more hardware modules or integrated circuits or in different networks and/or processor terminals and/or microcontroller terminals.

Fig. 13 is a schematic diagram of an electronic device according to an exemplary embodiment. It should be noted that the electronic device shown in fig. 13 is only an example, and should not impose any limitation on the functions and the scope of use of the embodiments of the present disclosure.

As shown in fig. 13, the electronic apparatus 1300 includes a Central Processing Unit (CPU) 1301, which can execute 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. In the RAM 1303, various programs and data necessary for the operation of the electronic apparatus 1300 are also stored. The CPU 1301, ROM 1302, and RAM 1303 are connected to each other through a bus 1304. An input/output (I/O) interface 1305 is also connected to bus 1304.

The following components are connected to the I/O interface 1305: an input section 1306 including a keyboard, a mouse, and the like; an output portion 1307 including a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker, and the like; a storage portion 1308 including a hard disk or the like; and a communication section 1309 including a network interface card such as a LAN card, a modem, or the like. The communication section 1309 performs a communication process via a network such as the internet. The drive 1310 is also connected to the I/O interface 1305 as needed. Removable media 1311, such as magnetic disks, optical disks, magneto-optical disks, semiconductor memory, and the like, is installed as needed on drive 1310 so that a computer program read therefrom is installed as needed into storage portion 1308.

In particular, according to embodiments of the present disclosure, the processes described above with reference to flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method shown in the flowcharts. In such embodiments, the computer program may be downloaded and installed from a network via the communication portion 1309 and/or installed from the removable medium 1311. The above-described functions defined in the system of the present disclosure are performed when the computer program is executed by a Central Processing Unit (CPU) 1301.

It should be noted that the computer readable medium shown in the present disclosure may be a computer readable signal medium or a computer readable storage medium, or any combination of the two. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, terminal device, or apparatus, or a combination of any of the foregoing. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, terminal device, or apparatus. In the present disclosure, however, the computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, with the computer-readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, terminal device, or apparatus. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.

The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The units involved in the embodiments of the present disclosure may be implemented by means of software, or may be implemented by means of hardware. The described units may also be provided in a processor, for example, described as: a processor includes a transmitting unit, an acquiring unit, a determining unit, and a first processing unit. The names of these units do not constitute a limitation on the unit itself in some cases, and for example, the transmitting unit may also be described as "a unit that transmits a picture acquisition request to a connected server".

As another aspect, the present disclosure also provides a computer-readable storage medium that may be included in the electronic device described in the above embodiments; or may exist alone without being incorporated into the electronic device. The computer-readable storage medium carries one or more programs which, when executed by the electronic device, cause the electronic device to implement the methods described in the embodiments below. For example, the electronic device may implement the steps shown in fig. 2.

According to one aspect of the present disclosure, there is provided a computer program product or computer program comprising computer instructions stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device performs the methods provided in the various alternative implementations of the above-described embodiments.

It should be understood that any number of elements in the drawings of the present disclosure are for illustration and not limitation, and that any naming is used for distinction only and not for limitation.

Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This disclosure is intended to cover any adaptations, uses, or adaptations of the disclosure following the general principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.

It is to be understood that the present disclosure is not limited to the precise arrangements and instrumentalities shown in the drawings, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims

1. A method for multicast information acquisition, comprising:

acquiring an opening request of multicast service of user equipment;

judging whether the multicast service exists in the domain of the user equipment;

if the multicast service exists in the domain of the user equipment, notifying a network controller of the domain of the user equipment to acquire multicast information of the multicast equipment;

If the domain where the user equipment is located does not have the multicast service, notifying a network controller of the domain where the user equipment is located to respectively collect forwarding technical support capability of the multicast equipment and multicast information of the multicast equipment.

2. The method as recited in claim 1, further comprising:

and if the multicast service does not exist in the domain where the user equipment is located, issuing a deployment strategy to the network controller so that the network controller determines a target forwarding technology according to the deployment strategy and forwarding technology supporting capability of the multicast equipment, wherein the target forwarding technology is used for the network controller to acquire multicast information of the multicast equipment.

3. The method according to claim 1, wherein after informing the network controller of the domain in which the user equipment is located to collect multicast information of a multicast device, the method further comprises:

the network controller obtains a target forwarding technology used by the multicast equipment according to control information of a local database;

and the network controller acquires the multicast information of the multicast equipment according to the target forwarding technology.

4. The method according to claim 2, wherein after informing the network controller of the domain in which the user equipment is located to collect forwarding technical support capability of the multicast equipment and multicast information of the multicast equipment, respectively, the method further comprises:

The network controller collects the forwarding technical support capability of the multicast equipment;

the network controller determines the target forwarding technology according to the forwarding technology supporting capability of the multicast equipment;

5. The method of claim 4, wherein the deployment policy includes priorities corresponding to a plurality of forwarding techniques;

the network controller determines the target forwarding technology according to the forwarding technology supporting capability of the multicast equipment, and the method comprises the following steps:

the network controller determines at least one forwarding technology supported by the multicast according to forwarding technology supporting capability of the multicast equipment;

and the network controller determines the target forwarding technology from the at least one forwarding technology according to the priorities corresponding to the plurality of forwarding technologies.

6. The method according to claim 3 or 4, wherein the multicast device comprises an intermediate node device and an edge node device, and the multicast information comprises a tree label and a termination label;

the network controller collects multicast information of the multicast device according to the target forwarding technology, and the method comprises the following steps:

And when the target forwarding technology is a multiprotocol label switching (MPLS) technology, the network controller collects the tree label of the intermediate node equipment, and the network controller collects the tree label and the terminal label of the edge node equipment.

7. The method of claim 6, wherein the network controller collecting the tree label of the intermediate node device and the network controller collecting the tree label and the termination label of the edge node device comprises:

the network controller collects tree labels of the intermediate node equipment through a first sub-TLV in an extended type length value TLV carried by a network control protocol;

and the network controller acquires the tree label and the terminal label of the edge node equipment through a second sub-TLV in the TVL carried by the network control protocol.

8. The method according to claim 3 or 4, wherein the multicast device comprises an intermediate node device and an edge node device, the multicast information comprising a tree SID and a termination SID;

and when the target forwarding technology is a Segment Routing (SR) technology, the network controller collects the tree SID of the intermediate node equipment, and the network controller collects the tree SID and the termination SID of the edge node equipment.

9. The method of claim 8, wherein the network controller collecting the tree SID of the intermediate node device and the network controller collecting the tree SID and the termination SID of the edge node device comprises:

the network controller collects tree SIDs of the intermediate node equipment through a third sub-TLV in TLVs carried by a network control protocol;

the network controller collects tree SIDs and terminal SIDs of the edge node devices through a fourth sub-TLV in the TVL carried by the network control protocol.

10. The method according to claim 3 or 4, wherein the multicast device comprises an edge node device, the multicast information comprising a forwarding router identification and a termination identification;

and when the target forwarding technology is the bit index explicit copy BIER technology, the network controller collects the forwarding router identification and the termination identification of the edge node equipment.

11. The method of claim 10, wherein the network controller collecting forwarding router identification and termination identification of the edge node device comprises:

The network controller collects the forwarding router identification and the termination identification of the edge node equipment through a fifth sub-TLV in TLVs carried by a network control protocol.

12. An apparatus for multicast information acquisition, comprising:

the acquisition module is used for acquiring an opening request of the multicast service of the user equipment;

a judging module, configured to judge whether the multicast service exists in a domain where the user equipment is located;

a notification module, configured to notify a network controller of a domain where the user equipment is located to collect multicast information of a multicast device if the domain where the user equipment is located has the multicast service;

and the notification module is further used for notifying a network controller of the domain where the user equipment is located to acquire forwarding technical support capability of the multicast equipment and multicast information of the multicast equipment respectively if the multicast service does not exist in the domain where the user equipment is located.

13. An electronic device, comprising:

at least one processor;

storage means 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 of any one of claims 1 to 11.

14. A computer readable storage medium, on which a computer program is stored, which computer program, when being executed by a processor, implements the method according to any one of claims 1 to 11.