CN117459335A - Data statistics method and device, related electronic equipment and product - Google Patents

Abstract

The disclosure provides a data statistics method and device, electronic equipment and a computer readable storage medium, and relates to the technical field of communication. The data statistics method comprises the following steps: the method comprises the steps that a first controller obtains a first multicast request quantity from a second controller in a target network, wherein the first multicast request quantity is the quantity of multicast receivers of a multicast proxy agent, which is obtained from a multicast proxy device by the second controller; the first controller determines the multicast request number of the target network according to the first multicast request number. The embodiment of the disclosure can accurately count the multicast users under the condition that the multicast proxy exists in the target network.

Description

Data statistics method and device, related electronic equipment and product

Technical Field

The present disclosure relates to the field of communications technologies, and in particular, to a data statistics method and apparatus, an electronic device, a computer readable storage medium, and a computer product.

Background

For operators and content providers, the user statistical information of multicast service has important significance in aspects of service analysis, market planning and the like. At present, a multicast statistical method based on an operator network exists, but a primary management architecture is oriented, namely, the number of users of a multicast bearer network directly accessing an operator can be counted. In the case of a two-level architecture, such as a multicast proxy, the proxy device will hide the number of users. There is no corresponding measure so that the network provider can perceive the number of users of a specific access multicast.

Therefore, the technical problem to be solved by the present disclosure is how to accurately determine the number of all multicast users (i.e. multicast recipients) in a multicast bearer network.

It should be noted that the information disclosed in the foregoing background section is only for enhancing understanding of the background of the present disclosure.

Disclosure of Invention

The disclosure aims to provide a data statistics method, a data statistics device, an electronic device, a computer readable storage medium and a computer product, which can accurately determine the number of multicast receivers in a target network.

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 data statistics method, which comprises the following steps: the method comprises the steps that a first controller obtains a first multicast request quantity from a second controller in a target network, wherein the first multicast request quantity is the quantity of multicast receivers of a multicast proxy agent, which is obtained from a multicast proxy device by the second controller; the first controller determines the multicast request number of the target network according to the first multicast request number.

In some embodiments, the method further comprises: the first controller obtains a second multicast request quantity from the edge equipment of the target network, wherein the second multicast request quantity is the multicast request quantity received by the edge equipment; wherein the first controller determines the multicast request number of the target network according to the first multicast request number, including: the first controller determines the multicast request number of the target network according to the first multicast request number and the second multicast request number.

In some embodiments, the target network includes at least one second controller, where each second controller corresponds to a first multicast request number; the target network comprises at least one edge device, wherein each edge device corresponds to a second multicast request quantity; wherein the first controller determines the multicast request number of the target network according to the first multicast request number and the second multicast request number, including: summing the respective first multicast request numbers to determine a proxy multicast receiver number; adding the respective second multicast request numbers to determine the number of independent multicast receivers; determining the number of the multicast proxy apparatuses; and determining the multicast request number according to the proxy multicast receiver number, the independent multicast receiver number and the multicast proxy equipment number.

In some embodiments, determining the number of multicast requests from the number of proxy multicast recipients, the number of independent multicast recipients, and the number of multicast proxy devices includes: and subtracting the number of multicast proxy devices from the sum of the number of proxy multicast receivers and the number of independent multicast receivers to determine the number of multicast requests.

In some embodiments, the second controller includes a first controller and a second controller, and the first multicast request number includes a first multicast request number and a second multicast request number; the first controller obtains a first multicast request quantity from a second controller in a target network, and the first controller comprises: the first controller obtains the multicast request quantity I from the controller I; the first controller obtains the multicast request quantity II from the controller II so as to determine the first multicast request quantity according to the multicast request quantity I and the multicast request quantity II.

In some embodiments, the first controller obtaining the multicast request quantity one from the controller one includes: the first controller obtains the multicast request quantity I from the controller I through a first signaling, wherein the first signaling comprises an identity of the controller I, identification information of a multicast proxy device of a nano tube, a multicast group, a multicast source and the quantity of multicast receivers of the nano tube of the controller I.

In some embodiments, the controller-nanotube at least one multicast proxy device, the at least one multicast proxy component comprising a target multicast proxy component; wherein before the first controller obtains the first multicast request number from the first controller, the method further comprises: the controller firstly acquires the number of multicast receivers proxied by the target multicast proxy equipment from the target multicast proxy component through a second signaling, wherein the second signaling comprises the identity of the multicast proxy equipment, multicast proxy mark information, a multicast group, a multicast source and the number of multicast receivers proxied by the target multicast proxy equipment.

In some embodiments, the first multicast request number includes a target group request number one, and the second multicast request number includes a target group request number two; wherein the first controller obtains a first multicast request number from a second controller in the target network, including: the first controller obtains the first target group request quantity corresponding to the target multicast group from the second controller in the target network, wherein the first target group request quantity is the quantity of multicast receivers of which the multicast proxy obtained by the second controller from the multicast proxy is the target multicast group proxy; the first controller obtains a second multicast request number from an edge device of the target network, where the second multicast request number is a multicast request number received by the edge device, and the method includes: the first controller obtains the second target group request quantity from the edge equipment of the target network, wherein the second target group request quantity is the multicast request quantity in the multicast group received by the edge equipment; wherein the first controller determines the multicast request number of the target network according to the first multicast request number and the second multicast request number, including: the first controller determines the target multicast group request number in the target multicast group according to the target group request number I and the target group request number II.

The embodiment of the disclosure provides a data statistics device, which comprises: the system comprises a first multicast request quantity acquisition module and a multicast request quantity determination module.

The first multicast request quantity acquisition module is used for a first controller to acquire a first multicast request quantity from a second controller in a target network, wherein the first multicast request quantity is the quantity of multicast receivers of the multicast proxy agent acquired by the second controller from the multicast proxy device; the multicast request number determining module may be configured to determine, by the first controller, a multicast request number of the target network according to the first multicast request number.

The embodiment of the disclosure provides an electronic device, which comprises: one or more processors; and a storage device for storing one or more programs that, when executed by the one or more processors, cause the one or more processors to implement the data statistics method of any of the above.

The disclosed embodiments provide a computer readable storage medium having stored thereon a computer program which when executed by a processor implements a data statistics method as described in any of the above.

Embodiments of the present disclosure propose a computer program product or a 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 executes the computer instructions to cause the computer device to perform the data statistics method described above.

The data statistics method, the data statistics device, the electronic equipment, the computer readable storage medium and the computer product provided by the embodiment of the disclosure, wherein the first controller can acquire the number of multicast receivers proxied by the multicast proxy equipment through the second controller, so that the number of multicast requests in the target network can be accurately determined.

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 multicast subscriber number counting method according to the related art.

FIG. 2 is a flow chart illustrating a method of data statistics according to an exemplary embodiment.

Fig. 3 is a schematic diagram illustrating a multicast subscriber number statistics method according to an exemplary embodiment.

Fig. 4 is a flow chart illustrating a method of data statistics according to an exemplary embodiment.

Fig. 5 is a schematic diagram illustrating a multicast subscriber number statistics method according to an exemplary embodiment.

Fig. 6 is a flow chart illustrating a method of data statistics according to an exemplary embodiment.

Fig. 7 is a flow chart illustrating a method of data statistics according to an exemplary embodiment.

Fig. 8 is a schematic diagram illustrating one type of first signaling or second signaling according to an example embodiment.

Fig. 9 is a flow chart illustrating a method of data statistics according to an exemplary embodiment.

Fig. 10 is a block diagram illustrating a data statistics apparatus according to an exemplary embodiment.

Fig. 11 shows a schematic structural diagram of an electronic device suitable for use in implementing embodiments of the present disclosure.

Detailed Description

Example embodiments will now be described more fully with reference to the accompanying drawings. However, the exemplary embodiments can be embodied in many forms and should not be construed as limited to the embodiments 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 same reference numerals in the drawings denote the same or similar parts, and thus a repetitive description thereof will be omitted.

The described features, structures, or characteristics of the disclosure may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of embodiments of the present disclosure. However, those skilled in the art will recognize that the aspects of the present disclosure may be practiced with one or more of the specific details, or with other methods, components, devices, steps, etc. In other instances, well-known methods, devices, implementations, or operations are not shown or described in detail to avoid obscuring aspects of the disclosure.

The drawings are merely schematic illustrations of the present disclosure, in which like reference numerals denote like or similar parts, and thus a repetitive description thereof will be omitted. Some of the block diagrams shown in the figures 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 devices and/or microcontroller devices.

The flow diagrams depicted in the figures are exemplary only, and not necessarily all of the elements or steps are included or performed in the order described. For example, some steps may be decomposed, and some steps may be combined or partially combined, so that the order of actual execution may be changed according to actual situations.

In the description of the present application, "/" means "or" unless otherwise indicated, for example, a/B may mean a or B. "and/or" herein is merely an association relationship describing an association object, and means that three relationships may exist, for example, a and/or B may mean: a exists alone, A and B exist together, and B exists alone. Furthermore, "at least one" means one or more, and "a plurality" means two or more. The terms "first," "second," and the like do not limit the amount and order of execution, and the terms "first," "second," and the like do not necessarily differ; the terms "comprising," "including," and "having" are intended to be inclusive and mean that there may be additional elements/components/etc., in addition to the listed elements/components/etc.;

in order that the above-recited objects, features and advantages of the present invention can be more clearly understood, a more particular description of the invention will be rendered by reference to specific embodiments thereof which are illustrated in the appended drawings, it being understood that the embodiments and features of the embodiments may be combined with each other without conflict.

In explaining the embodiments of the present disclosure, the multicast, that is, the related content in the multicast may be explained.

Multicasting is a one-to-many communication mode between hosts.

The multicast mode: a one-to-multipoint connection mode is adopted between the data sender and the receivers, a plurality of receivers join the same multicast group and share the same IP address (the IP address is logical, each receiver still needs to configure a separate IP address for receiving actual data), meanwhile, members in the multicast group are dynamic, and the joining and exiting of a certain member do not affect the original multicast group.

When some users in the network need specific data, a multicast data sender (namely a multicast source) only sends the data once, a multicast distribution tree is established for a multicast data packet by means of a multicast routing protocol, and the transmitted data starts to be copied and distributed after reaching a node which is as close as possible to a user side.

In multicast technology, the following terms may be referred to.

1. Multicast sender: a sender transmitting data for a multicast group does not join the multicast group.

2. Multicast transmitter: routers or three-layer switches supporting three-layer multicast functions, which do not join the multicast group.

3. Multicast receivers: members of the multicast group.

4. Multicast address: IP address shared by members of all multicast groups

5. Multicast protocol: the multicast protocol is classified into a group membership protocol between host-routers and a multicast routing protocol between routers.

Fig. 1 is a schematic diagram illustrating a multicast subscriber number counting method according to the related art.

As shown in fig. 1, the statistical implementation of multicast subscribers (i.e., multicast receivers, such as handsets or other terminals (e.g., tablet, computer, etc.) in fig. 1) in the related art reports the accessed subscriber information to the unified controller through an Edge router (e.g., PE (provider Edge) 1, 2, 3 … … in fig. 1) of a network provider (i.e., a target network). Whether a terminal accessing a base station or a set top box accessing a home gateway, a multicast join request is sent to an edge router directly through an IGMP/MLD message.

Wherein IGMP is Internet Group Management Ptotocol, called internet group management protocol, and is a protocol responsible for IPV4 multicast member management in TCP/IP protocol family.

MLD (acronym Multicast Listener Discover) is a network protocol used in multicast technology. Is a multicast snoop discovery protocol. It is used for IPv6 routers to discover multicast listeners over their direct networking segments.

However, the related art has the following disadvantages: for the scenario that the user can only directly access the edge router, for the scenario that the multicast proxy is enabled, the multicast proxy device, not the actual user, can send a request to the edge router, and accurate user statistics information can not be obtained.

In view of the above problems, the present application proposes the following data statistical method.

FIG. 2 is a flow chart illustrating a method of data statistics according to an exemplary embodiment.

Referring to fig. 2, the data statistics method provided by the embodiment of the present disclosure may include the following steps.

In step S202, the first controller obtains a first multicast request number from a second controller in the target network, where the first multicast request number is a number of multicast receivers proxied by the multicast proxy obtained by the second controller from the multicast proxy.

The first controller and the second controller are controllers which are divided according to functions, and the first controller and the second controller can be any device in a target network, so that the disclosure is not limited. It is further understood that the first controller and the second controller may be one device or may be different devices, which the present disclosure is not limited to.

In some embodiments, the first controller may be one and the second controller may be one or more.

In some embodiments, the first controller may be a unified controller in fig. 1, and the second controller may be an access controller configured to receive multicast receiver number information uploaded by the multicast proxy apparatus.

The target network may be a local area network, a wide area network, or a local area network or a subnet in a wide area network, which is not limited by the present disclosure.

The multicast proxy may be a gateway (e.g., a home gateway), a network element in a target network (e.g., UPF (User Plane Function, user plane function)), etc., and the disclosure is not limited to multicast proxy.

Fig. 3 is a schematic diagram illustrating a multicast subscriber number statistics method according to an exemplary embodiment.

In some embodiments, the multicast proxy device may proxy the user device to initiate a multicast application request to the edge device of the target network, instead of the user device acting as a multicast receiver to receive information from the target network, and then send the received information to the multicast user of its proxy after receiving the information.

As shown in fig. 3, UPF1 may act as a multicast proxy device to initiate a multicast access request to an edge device of a target network by proxy N user devices, to proxy the N user devices as receivers to receive information from the target network, and then send the received information to a multicast user of the UPF1 proxy after receiving the information.

As shown in fig. 3, the home gateway 1 may act as a multicast proxy device to proxy N user devices to initiate a multicast access request to an edge device of a target network, to proxy the N user devices as receivers to receive information from the target network, and then send the received information to a multicast user proxied by the home gateway 1 after receiving the information.

In some embodiments, the multicast proxy apparatus may send the number of multicast user devices that it proxies to the second controller (e.g., the access controller). As shown in fig. 3, UPF1 as a multicast proxy device will send the number of multicast receivers that it proxies to the access controller, and home gateway 1 as a multicast proxy device will also send the number of multicast receivers that it proxies to the access controller.

In step S204, the first controller determines the multicast request number of the target network according to the first multicast request number.

In some embodiments, the first controller determines a number of multicast requests for the target network based on the first number of multicast requests for subsequent analysis and use. For example, the first multicast request numbers may be added to determine the multicast request numbers of the target bit target network, and for example, the pair multicast request numbers of the multicast groups may be added to determine the multicast request numbers of the multicast groups, respectively.

For the multicast proxy apparatus, a multicast join request is sent to a network provider as a receiver, and a multicast forwarding table is also maintained locally for the user. The present disclosure provides a channel (a southbound interface of a controller and a northbound interface of a multicast proxy device) through a second controller (a network controller) of an operator, which may be a user gateway or a user plane device of a mobile network, that can report information. For a specific multicast group, the multicast proxy device converts the number of users of the group in the multicast forwarding table into an interactive signaling, and reports the interactive signaling to the corresponding access controller (i.e. the second controller), and informs the controller (the second controller) that the controller is a proxy device and carries the number of users of the proxy. The corresponding access controller (i.e. the second controller) interacts with the unified controller (i.e. the first controller) to report the number of users proxied by the multicast proxy apparatus. The unified controller integrates the multicast user quantity summarized by all the access controllers, can obtain the user statistical information of a specific multicast group, and provides data support for subsequent service analysis and market planning.

The present disclosure proposes a method by which statistical information of multicast receivers on a multicast proxy device proxy can be collected by an access controller and synchronized to a unified controller for synchronization to a network provider. The method and the system can effectively utilize the advantages of flexible management and resource optimization of the multicast proxy, can ensure the accuracy of multicast service statistics, and are convenient for subsequent service optimization and popularization.

Fig. 4 is a flow chart illustrating a method of data statistics according to an exemplary embodiment.

Referring to fig. 4, the data statistics method provided by the embodiment of the present disclosure may include the following steps.

In step S402, the first controller obtains a first multicast request number from a second controller in the target network, where the first multicast request number is a number of multicast receivers proxied by the multicast proxy obtained by the second controller from the multicast proxy.

In step S404, the first controller obtains a second multicast request number from the edge device of the target network, where the second multicast request number is the multicast request number received by the edge device.

In some embodiments, the target network has user equipment that receives multicast messages directly from the target network in addition to some user equipment that receives multicast messages through the multicast proxy. As shown in fig. 4, the UPF and the home gateway 1 may act as proxy devices to proxy some user equipments to receive multicast messages from the target network, and some user equipments may directly join the multicast group (e.g. join the terminals of the anchor group through the home gateway 2 and the PE 3).

In some embodiments, the first controller may further obtain the number of multicast receivers (i.e., the second multicast request number) of all the direct access target networks from the edge devices of the target networks.

In step S406, the first controller determines the multicast request number of the target network according to the first multicast request number and the second multicast request number.

In some embodiments, the number of multicast requests for the target network may be determined based on the first number of multicast requests and the second number of multicast requests. For example, all of the first multicast request numbers and all of the second multicast request numbers may be added to determine the multicast request numbers of the target network.

For the multicast proxy apparatus, a multicast join request is sent to a network provider as a receiver, and a multicast forwarding table is also maintained locally for the user. The present disclosure provides a channel (a southbound interface of a controller and a northbound interface of a multicast proxy device) through a second controller (a network controller) of an operator, which may be a user gateway or a user plane device of a mobile network, that can report information. For a specific multicast group, the multicast proxy device converts the number of users of the group in the multicast forwarding table into an interactive signaling, and reports the interactive signaling to the corresponding access controller (i.e. the second controller), and informs the controller (the second controller) that the controller is a proxy device and carries the number of users of the proxy. The corresponding access controller (i.e. the second controller) interacts with the unified controller (i.e. the first controller) to report the number of users proxied by the multicast proxy apparatus. The unified controller integrates the multicast user quantity summarized by all access controllers and the multicast user quantity summarized by all edge devices, so that the user statistical information of a specific multicast group can be obtained, and data support is provided for subsequent service analysis and market planning.

Fig. 6 is a flow chart illustrating a method of data statistics according to an exemplary embodiment.

In some embodiments, the target network may include at least one second controller, where each second controller corresponds to a first multicast request number; the target network may include at least one edge device, wherein each edge device corresponds to a second number of multicast requests.

Referring to fig. 6, the data statistics method provided by the embodiment of the present disclosure may include the following steps.

In step S602, the first controller obtains a first multicast request number from a second controller in the target network, where the first multicast request number is a number of multicast receivers proxied by the multicast proxy obtained by the second controller from the multicast proxy.

In step S604, the first controller obtains a second multicast request number from the edge device of the target network, where the second multicast request number is the multicast request number received by the edge device.

Step S606 adds the respective first multicast request numbers to determine the proxy multicast receiver number.

Step S608, adds the respective second multicast request numbers to determine the number of independent multicast receivers.

Step S610, determining the number of multicast proxy apparatuses.

Step S612, determining the multicast request number according to the proxy multicast receiver number, the independent multicast receiver number and the multicast proxy device number.

In some embodiments, the number of multicast requests may be determined by subtracting the number of multicast proxy devices from the sum of the number of proxy multicast receivers and the number of independent multicast receivers.

According to the technical scheme provided by the embodiment, the multicast request number in the target network can be accurately determined according to the first multicast request number uploaded by the second controller and the second multicast request number uploaded by the edge device.

Fig. 7 is a flow chart illustrating a method of data statistics according to an exemplary embodiment.

In some embodiments, the second controller may include a first controller and a second controller, and the first multicast request number includes a first multicast request number and a second multicast request number.

Referring to fig. 7, the data statistics method provided by the embodiment of the present disclosure may include the following steps.

In step S702, the first controller obtains the multicast request number one from the controller one.

In some embodiments, the first controller may obtain the multicast request number one from the controller one.

The first controller obtains the multicast request quantity I from the controller I through a first signaling, wherein the first signaling comprises the identity of the controller I, the identification information of the multicast proxy equipment of the nano-tube, the multicast group, a multicast source and the quantity of multicast receivers of the nano-tube of the controller I.

In some embodiments, different controller protocols, the first signaling implementation may be different, requiring the following requirements to be met:

(1) A field representing the identity of the device, whether the network device or the controller is used for synchronizing information.

(2) A flag P (proxy) identifying the device that the access controller has managed to turn on the multicast proxy.

(3) Multicast group, multicast source, i.e. (S, G)/(G); the multicast user number of the proxy. The access device has managed a device that turns on the multicast proxy and counts the corresponding-1.

Wherein, S proxies the multicast source and G stands for multicast group.

(4) The update of the multicast statistics is performed periodically.

In some embodiments, the controller-the at least one multicast proxy device, the at least one multicast proxy component comprises a target multicast proxy component.

In some embodiments, before the first controller obtains the first multicast request number from the first controller, the following steps may be performed:

The controller firstly acquires the number of multicast receivers of the target multicast proxy equipment proxy from the target multicast proxy component through a second signaling, wherein the second signaling comprises the identity of the multicast proxy equipment, multicast proxy mark information, a multicast group, a multicast source and the number of multicast receivers of the target multicast proxy equipment proxy.

In some embodiments, the specific implementation of the second signaling may be different for different controller protocols, requiring the following requirements to be met:

(1) A field representing the identity of the device, the information network device used for synchronization, or the controller.

(2) The identification device turns on the flag P (proxy) of the multicast proxy.

(3) Multicast group, multicast source, i.e. (S, G)/(G); the multicast user number of the proxy.

(4) The update of the multicast statistics is performed periodically.

Fig. 8 is a schematic diagram illustrating one type of first signaling or second signaling according to an example embodiment.

As shown in fig. 8: the meaning of some of the parameters in the first signaling or the second signaling is as follows.

P, proxy, is the proxy flag. P=1 is an on multicast proxy and p=0 is an off multicast proxy.

R, role, r=0 is the network device, r=1 is the controller, r=2, 3 reserved.

Number of Receivers (NR), synchronized multicast statistics.

P=1, r=0, and reports proxy statistics information on behalf of the multicast proxy device, where NR is a proxy statistics value.

P=1, r=1, representing access controller synchronization statistics, NR is proxy statistics-proxy device number.

In step S704, the first controller obtains the multicast request number two from the second controller.

The process of the first controller obtaining the multicast request number two from the second controller is similar to the process of obtaining the multicast request number from the first controller, which is not described in detail in this disclosure.

In step S706, the first controller determines the first multicast request number according to the first multicast request number and the second multicast request number.

According to the technical scheme provided by the embodiment, the second controller can acquire the number of multicast users (namely the multicast request number) proxied by the multicast proxy equipment from the multicast proxy equipment through the first signaling, and the first controller can acquire the multicast request number from the plurality of second controllers through the second signaling and summarize the multicast request number in the plurality of second controllers so as to determine the multicast request number in the target network.

Fig. 9 is a flow chart illustrating a method of data statistics according to an exemplary embodiment.

In some embodiments, the signaling between the multicast proxy apparatus and the second controller may include a multicast group and a multicast source, and the signaling between the second controller and the first controller may also include a multicast group and a multicast source.

In some embodiments, the first multicast request number may include a target group request number one and the second multicast request number may include a target group request number two.

Then referring to fig. 9, the data statistics method provided by the embodiments of the present disclosure may include the following steps.

In step S902, the first controller obtains, from a second controller in the target network, a target group request number one corresponding to the target multicast group, where the target group request number one is the number of multicast receivers, for which the multicast proxy obtained by the second controller from the multicast proxy is a target multicast group proxy.

In step S904, the first controller obtains a target group request number two from the edge device of the target network, where the target group request number two is the multicast request number in the multicast group received by the edge device.

In step S906, the first controller determines the target multicast group request number in the target multicast group according to the target group request number one and the target group request number two.

According to the technical scheme provided by the embodiment, the first controller can group and count the multicast user quantity in the target network so as to analyze and use later.

The disclosure further provides a multicast user statistics method, and referring to the schematic diagram shown in fig. 5, the multicast user statistics method may include the following steps.

Step one: the user plane device UPF1 and the home gateway 1 start the multicast proxy function as a multicast provider to maintain the multicast forwarding table item locally. And sends a join request as a receiver to the multicast network edge router.

Step two: the UPF1 and the home gateway 1 which start the multicast proxy periodically report the user statistics information of the local proxy to the access controller, and inform the access controller that the access controller starts the multicast proxy, and each multicast group separates statistics. For example, for multicast (S1, G1), the access controller has managed 2 devices (e.g., UPF1 and home gateway 1) that turn on the multicast agent, where the number of users for the UPF1 agent is N and the number of users for the home gateway 1 agent is M. The number of users perceived by the access controller is n+m.

Step three: the access controller synchronizes the multicast proxy information to the unified controller and informs the unified controller that its nanotubes have been the device that opened the multicast proxy. In the second continuing step, since the proxy devices (such as UPF1 and home gateway 1) also serve as a receiver, the multicast statistics synchronized to the unified controller should be subtracted by the number of proxy devices, i.e., n+m-2 users, accordingly.

Step four: the unified controller synthesizes the statistical information reported by the edge devices (such as PE2 and PE 3) and the multicast proxy statistical information synchronized by the access controller, and calculates the total user statistical information of the multicast group, (N+M-2) +1 (PE 2 report) +2 (PE 3 report) =N+M+1. This information is either signalled to the multicast source or provided north to the corresponding application for further analysis and application.

According to the technical scheme, the multicast proxy equipment and the corresponding controller are synchronized in multi-stage statistical information, so that the deployment of the multicast proxy can be supported, and the corresponding multicast service statistical flow is perfected. The advantages of flexible management and resource optimization of the multicast proxy can be effectively utilized, meanwhile, the accuracy of multicast service statistics can be ensured, and the subsequent service optimization and popularization are facilitated. In addition, the technical scheme provided by the embodiment can be multiplexed and expanded based on the existing signaling, and can be organically combined with the multicast service statistical flow of the existing unopened multicast proxy.

Based on the same inventive concept, the embodiments of the present disclosure also provide a data statistics device, such as the following embodiments. Since the principle of solving the problem of the embodiment of the device is similar to that of the embodiment of the method, the implementation of the embodiment of the device can be referred to the implementation of the embodiment of the method, and the repetition is omitted.

Fig. 10 is a block diagram illustrating a data statistics apparatus according to an exemplary embodiment. Referring to fig. 10, a data statistics apparatus 1000 provided by an embodiment of the present disclosure may include: a first multicast request number acquisition module 1001 and a multicast request number determination module 1002.

The first multicast request number obtaining module 1001 may be configured to obtain, by a first controller, a first multicast request number from a second controller in a target network, where the first multicast request number is a number of multicast receivers that the second controller obtains from a multicast proxy agent; the multicast request number determining module 1002 may be configured to determine, by the first controller, a multicast request number of the target network according to the first multicast request number.

Here, it should be noted that the first multicast request number obtaining module 1001 and the multicast request number determining module 1002 correspond to S202 to S204 in the method embodiment, and the foregoing modules are the same as examples and application scenarios implemented by the corresponding steps, but are not limited to those disclosed in the foregoing method embodiment. It should be noted that the modules described above may be implemented as part of an apparatus in a computer system, such as a set of computer-executable instructions.

In some embodiments, the data statistics apparatus may further comprise: a second multicast request quantity acquisition module; the multicast request number determination module 1002 may include: and a multicast request number determining unit.

The second multicast request number obtaining module 1001 may be configured to obtain, by using a first controller, a second multicast request number from an edge device of a target network, where the second multicast request number is a multicast request number received by the edge device; the multicast request number determining unit may be configured to determine, by the first controller, a multicast request number of the target network according to the first multicast request number and the second multicast request number.

In some embodiments, the target network includes at least one second controller, wherein each second controller corresponds to a first multicast request number; the target network comprises at least one edge device, wherein each edge device corresponds to a second multicast request quantity; wherein the multicast request number determining unit may include: the device comprises a first addition subunit, a second addition subunit, a proxy device determining subunit and a multicast request quantity determining subunit.

Wherein the first summing subunit is operable to sum the respective first multicast request numbers to determine a proxy multicast receiver number; the second adding subunit may be configured to add respective second multicast request numbers to determine an independent multicast receiver number; the proxy device determination subunit may be configured to determine a number of multicast proxy devices; the multicast request number determination subunit may be configured to determine the multicast request number based on the proxy multicast recipient number, the independent multicast recipient number, and the number of multicast proxy devices.

In some embodiments, the multicast request number determination subunit may include: add and subtract grandchild units.

Wherein the add-subtract child unit may be configured to add the number of proxy multicast receivers to the number of independent multicast receivers and subtract the number of multicast proxy devices to determine the number of multicast requests.

In some embodiments, the second controller comprises a first controller and a second controller, and the first multicast request number comprises a first multicast request number and a second multicast request number; the first multicast request number obtaining module 1001 may include: the multicast request number-acquiring unit and the multicast request number-acquiring unit.

The first controller may be configured to obtain the first multicast request number from the first controller; the multicast request number and obtaining unit may be configured to obtain the multicast request number two from the second controller by the first controller, so as to determine the first multicast request number according to the multicast request number one and the multicast request number two.

In some embodiments, the multicast request number one acquisition unit may include: a first signaling acquisition subunit.

The first signaling obtaining subunit may be configured to obtain, by the first controller, a multicast request number one from the first controller through a first signaling, where the first signaling includes an identity of the first controller, identification information of a multicast proxy device of the multicast group, a multicast source, and a number of multicast receivers of the first nanotube of the controller.

In some embodiments, the controller-the at least one multicast proxy device, the at least one multicast proxy component comprises a target multicast proxy component; the data statistics device may further include a second signaling acquisition module.

The second signaling obtaining module may be configured to obtain, by the first controller, the number of multicast receivers of the target multicast proxy device proxy from the target multicast proxy component through the second signaling before the first controller obtains the number of multicast requests from the first controller, where the second signaling includes an identity of the multicast proxy device, multicast proxy flag information, a multicast group, a multicast source, and the number of multicast receivers of the target multicast proxy device proxy.

In some embodiments, the first multicast request number includes a target group request number one and the second multicast request number includes a target group request number two; the first multicast group request number obtaining module 1001 may include: a target group request number-determining unit; the second multicast request quantity obtaining module 1001 may include: a target group request number two determining unit; the multicast request number determining unit may include: the number of multicast requests determines the subunit.

The first controller may obtain, from a second controller in the target network, a first target group request number corresponding to the target multicast group, where the first target group request number is the number of multicast receivers, for which the multicast proxy device obtained from the multicast proxy device by the second controller is a target multicast group proxy; the second target group request number determining unit may be configured to obtain, by the first controller, a second target group request number from an edge device of the target network, where the second target group request number is a multicast request number in a multicast group received by the edge device; the multicast request number determining subunit may be configured to determine, by the first controller, a target multicast group request number in the target multicast group according to the target group request number one and the target group request number two.

Since each function of the apparatus 1000 is described in detail in the corresponding method embodiments, the disclosure is not repeated herein.

The modules and/or units and/or sub-units and/or grandchild units referred to in the embodiments of the present application may be implemented in software or in hardware. The described modules and/or units and/or sub-units and/or grandchild units may also be provided in the processor. Wherein the names of the modules and/or units and/or sub-units and/or grandchild units do not constitute a definition of the module and/or unit and/or sub-unit and/or grandchild unit itself in some cases.

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 application. 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.

Furthermore, the above-described figures are only schematic illustrations of processes included in the method according to the exemplary embodiments of the present disclosure, and are not intended to be limiting. It will be readily appreciated that the processes shown in the above figures do not indicate or limit the temporal order of these processes. In addition, it is also readily understood that these processes may be performed synchronously or asynchronously, for example, among a plurality of modules.

Fig. 11 shows a schematic structural diagram of an electronic device suitable for use in implementing embodiments of the present disclosure. It should be noted that the electronic device 1100 shown in fig. 11 is only an example, and should not impose any limitation on the functions and usage scope of the embodiments of the present disclosure.

As shown in fig. 11, the electronic device 1100 includes a Central Processing Unit (CPU) 1101 that can execute various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 1102 or a program loaded from a storage section 1108 into a Random Access Memory (RAM) 1103. In the RAM 1103, various programs and data necessary for the operation of the electronic device 1100 are also stored. The CPU 1101, ROM 1102, and RAM 1103 are connected to each other by a bus 1104. An input/output (I/O) interface 1105 is also connected to bus 1104.

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

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 storage medium, the computer program comprising program code for performing the method shown in the flowcharts. In such an embodiment, the computer program can be downloaded and installed from a network via the communication portion 1109, and/or installed from the removable media 1111. The above-described functions defined in the system of the present application are performed when the computer program is executed by a Central Processing Unit (CPU) 1101.

It should be noted that the computer readable storage 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, apparatus, or device, or a combination of any of the foregoing. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present application, however, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, with 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 storage medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable storage 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.

As another aspect, the present application also provides a computer-readable storage medium that may be contained in the apparatus described in the above embodiments; or may be present alone without being fitted into the device. The computer-readable storage medium carries one or more programs which, when executed by a device, cause the device to perform functions including: the first controller obtains a first multicast request quantity from a second controller in the target network, wherein the first multicast request quantity is the quantity of multicast receivers of the multicast proxy agent obtained from the multicast proxy by the second controller; the first controller determines the multicast request number of the target network according to the first multicast request number.

According to one aspect of the present application, 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.

From the above description of embodiments, those skilled in the art will readily appreciate that the example embodiments described herein may be implemented in software, or may be implemented in software in combination with the necessary hardware. Thus, aspects of the disclosed embodiments may be embodied in a software product, which may be stored on a non-volatile storage medium (may be a CD-ROM, a U-disk, a mobile hard disk, etc.), comprising instructions for causing a computing device (may be a personal computer, a server, a mobile terminal, or a smart device, etc.) to perform a method according to embodiments of the disclosure, e.g., one or more of the steps shown in fig. 2, 4, 6, 7, 9.

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 disclosure is not to be limited to the details of construction, the manner of drawing, or the manner of implementation, which has been set forth herein, but, on the contrary, is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims.

Claims (12)

1. A method of data statistics, comprising:

the method comprises the steps that a first controller obtains a first multicast request quantity from a second controller in a target network, wherein the first multicast request quantity is the quantity of multicast receivers of a multicast proxy agent, which is obtained from a multicast proxy device by the second controller;

the first controller determines the multicast request number of the target network according to the first multicast request number.

2. The method according to claim 1, wherein the method further comprises:

the first controller obtains a second multicast request quantity from the edge equipment of the target network, wherein the second multicast request quantity is the multicast request quantity received by the edge equipment;

wherein the first controller determines the multicast request number of the target network according to the first multicast request number, including:

the first controller determines the multicast request number of the target network according to the first multicast request number and the second multicast request number.

3. The method of claim 2, wherein the target network comprises at least one second controller, wherein each second controller corresponds to a first multicast request number; the target network comprises at least one edge device, wherein each edge device corresponds to a second multicast request quantity; wherein the first controller determines the multicast request number of the target network according to the first multicast request number and the second multicast request number, including:

summing the respective first multicast request numbers to determine a proxy multicast receiver number;

adding the respective second multicast request numbers to determine the number of independent multicast receivers;

determining the number of the multicast proxy apparatuses;

and determining the multicast request number according to the proxy multicast receiver number, the independent multicast receiver number and the multicast proxy equipment number.

4. The method of claim 3, wherein determining the number of multicast requests based on the number of proxy multicast recipients, the number of independent multicast recipients, and the number of multicast proxy devices comprises:

And subtracting the number of multicast proxy devices from the sum of the number of proxy multicast receivers and the number of independent multicast receivers to determine the number of multicast requests.

5. The method of claim 1, wherein the second controller comprises a first controller and a second controller, and wherein the first number of multicast requests comprises a first number of multicast requests and a second number of multicast requests; the first controller obtains a first multicast request quantity from a second controller in a target network, and the first controller comprises:

the first controller obtains the multicast request quantity I from the controller I;

the first controller obtains the multicast request quantity II from the controller II so as to determine the first multicast request quantity according to the multicast request quantity I and the multicast request quantity II.

6. The method of claim 5, wherein the first controller obtaining the first number of multicast requests from the first controller comprises:

the first controller obtains the multicast request quantity I from the controller I through a first signaling, wherein the first signaling comprises an identity of the controller I, identification information of a multicast proxy device of a nano tube, a multicast group, a multicast source and the quantity of multicast receivers of the nano tube of the controller I.

7. The method of claim 5, wherein the controller-nanotube at least one multicast proxy device, the at least one multicast proxy component comprising a target multicast proxy component; wherein before the first controller obtains the first multicast request number from the first controller, the method further comprises:

the controller firstly acquires the number of multicast receivers proxied by the target multicast proxy equipment from the target multicast proxy component through a second signaling, wherein the second signaling comprises the identity of the multicast proxy equipment, multicast proxy mark information, a multicast group, a multicast source and the number of multicast receivers proxied by the target multicast proxy equipment.

8. The method of claim 2, wherein the first number of multicast requests comprises a target group request number one and the second number of multicast requests comprises a target group request number two; wherein the first controller obtains a first multicast request number from a second controller in the target network, including:

the first controller obtains the first target group request quantity corresponding to the target multicast group from the second controller in the target network, wherein the first target group request quantity is the quantity of multicast receivers of which the multicast proxy obtained by the second controller from the multicast proxy is the target multicast group proxy;

The first controller obtains a second multicast request number from an edge device of the target network, where the second multicast request number is a multicast request number received by the edge device, and the method includes:

the first controller obtains the second target group request quantity from the edge equipment of the target network, wherein the second target group request quantity is the multicast request quantity in the multicast group received by the edge equipment;

wherein the first controller determines the multicast request number of the target network according to the first multicast request number and the second multicast request number, including:

the first controller determines the target multicast group request number in the target multicast group according to the target group request number I and the target group request number II.

9. A data statistics apparatus, comprising:

a first multicast request number obtaining module, configured to obtain, by a first controller, a first multicast request number from a second controller in a target network, where the first multicast request number is a number of multicast receivers of a multicast proxy agent obtained by the second controller from the multicast proxy device;

And the multicast request quantity determining module is used for determining the multicast request quantity of the target network according to the first multicast request quantity by the first controller.

10. An electronic device, comprising:

a memory; and

an electronic device coupled to the memory, the electronic device being adapted to perform the data statistics method of any of claims 1-8 based on instructions stored in the memory.

11. A computer readable storage medium having stored thereon a program which when executed by a processor implements a data statistics method as claimed in any of claims 1-8.

12. A computer program product comprising computer instructions stored in a computer readable storage medium, characterized in that the computer instructions, when executed by a processor, implement the method of any one of claims 1-8.